HyperXTalk 0.9.6 released

HyperXTalk Release Notes

0.9.6

2 Likes

How feature-complete is this expected to be? Is it worth reporting at this stage that that the button in Prefs that lets me change where I store extensions isn’t working?

We’re a long way from feature complete, so report everything you find please.

1 Like

I made a GitHub issue for it

1 Like

Thank you.

I would have fixed it but it seems gRevDevelop doesn’t work as it used to as a flag to allow IDE stacks to appear in the browser.

Don’t open an issue in that just yet - I may be mistaken. And even if that turns out to be the case, we may want to take the opportunity to update the name of that global.

I’ll report back after I’ve poked around more, and the issue you did file will help as it’ll allows me to use my own tools now easily. Thanks again for the quick response.

I view the IDE in the Project Browser all day, it’s how I edit the IDE for dark mode (sometimes I have to use CotEditor because I bork the IDE so it doesn’t load :wink: )

Yeah, there’s likely a GUI control for that. I’ve just rarely used their tools, loading my own UI for getting around more quickly (which explains why I have the unusual habit of making the first thing I do after installing an IDE to change the location of the Extensions folder to use the one I sync across my systems).

But we still have the underlying mechanism to consider as time permits, historically the gRevDevelop global. It stopped making sense after their name change, and the sooner we update that global name the better.

Maybe simply gHyperXTalkDevelop?

There is so much “rev” in the IDE that it’s going to take a long time to change over everything. I use the prefix “HXT” for code and variables.

1 Like

Maybe we should call it RevolutionTalk right away, stay with the “rev” and see how many households of xTalk aficionados get raided then (at least in the U.S.) :wink:

1 Like

The ones that are used exclusively within the IDE are low priorities.

Then again, I’m not sure more than a dozen of us ever used gRevDevelop from the Message Box, so maybe that’s an equally low priority.

I never even heard of gRevDevelop so not sure it’s a “hot” topic :slight_smile:

1 Like

Secret sauce, full recipe here:

Could be useful for debugging HyperXTalk issues though, this is correct.

The engine has priority, this is also true. Still sadly we would need to make the whole package work correctly. No user at whatever level will want to start wondering when something goes wrong “Hm, is it a bug in the engine or just in the IDE?”, or will say “Oh, it is just the IDE, so that’s ok”.

Yes, we will get everything fixed up, so long as there is a bug report about it :slight_smile:

ToolGuy, this may be our call. She can do everything, but my C++ sucks. We can script. Perhaps we should, so she can focus on the stuff she does uniquely well.

I hear the call well. :smiley: I have been contributing from start whatever possible and will keep it this way. Yet I am not sure if I should seriously touch the IDE, rather encourage the long-time spelunkers for this. Reasons on request.

There are lots of ways to help out:

  • work on the website, no coding needed
  • help with the IDE, some scripting involved
  • submit bug reports (we want a polished IDE)
  • submit feature requests
  • help with documentation of building
  • just testing the builds

Re-reading this thread, it is an interesting issue though, on the other hand it is prompted by your special way to bend the IDE (or even weasel out of it), might be hard to reproduce for others. We have a yak shave first in finding out why the gRevDevelop stuff does not work. Correct? I do not even have hardware here to test the current build. :frowning:

I’m trying to get it to compile on Windows. Might be a couple of days still

1 Like

This one is right up my alley, and such a low priority that it can fit my unpredictable schedule.

Emily-Elizabeth, if you want to assign that bug report to me that’ll be one small thing off your plate.

1 Like