OpenXTalk Forums

-
Indeed, but those 'notelets' are not really very informative.

And where are those text files?

Aha: I found "revidelibrary.8.livecodescript" in /Contents/Tools/Toolset/libraries . . .

BUT that is going to mean NOTHING to an awful lot of people.

The process of growing mushrooms has intrigued people for ages, leading to misconceptions about their cultivation (ahem, like being grown in manure) and the mysterious dirt-like particles.

https://mushrooms.ca/the-dirt-on-mushrooms/

Now who would have thought about looking there?
- -
I do think it would be a very good thing if these documents could be 'brought to the surface' so that end-users could find them and read them.

Not sure what your point is with this.
If you click the 'update' button, it'll move stuff out of here as it needs anyway.
The next update (as mentioned, there are two), will put even more in there!

richmond62 wrote: ↑Sat Aug 17, 2024 1:01 pm I do think it would be a very good thing if these documents could be 'brought to the surface' so that end-users could find them and read them.

Um, why? They are part of the IDE files before they get moved to the right locations. Why would anyone want to tamper with stuff before they get moved? All that will do is break the update process.

Anyway, that update folder only contains a "what's new" note - the same one you get as per your first screenshot.

My point is that those text documents contain useful information like this:

Corrected the polygon sides (paint tool) menu in the tools stack. Re-added the Radius tool and menu in the tools stack (which was deleted from LCC 8.x)

Which most end-users are NOT going to see when those documents are BURIED in the file system.
- -
As those icons will, perhaps not be obvious to updaters, nor what their functionality is.

After all, your corrections/innovations ARE impressive.

AND THIS:
- -
is only visible for the duration of the upgrade process, and were it available somewhere more obvious than way down at the 'bottom of the treacle well' of the file structure it would make it easier to refer to later.

richmond62 wrote: ↑Sat Aug 17, 2024 1:29 pm My point is that those text documents contain useful information[...]which most end-users are NOT going to see when those documents are BURIED in the file system.

Please see screenshot above. That note is loaded into the stack when you click the 'what's changed' text, so not buried at all

so not buried at all

See subsequent note.

Not everyone is bothered from what I can tell, and are probably happy just to read the release notes on this site. I thought I'd detail what was changed in each update (purely for the curious), but most people would probably just click the 'Update' button.

Not everyone is bothered from what I can tell, and are probably happy just to read the release notes on this site. I thought I'd detail what was changed in each update, but most people would probably just click the 'Update' button.

I wonder how you worked that out.

Most software developers (including LiveCode) make quite a big 'song and dance' about their updates/upgrades what with PDF documents and so forth.

Some people may not be bothered, but some will be, and if you make any update/upgrade details OUT FRONT things will be easier when the fussy end-users come after you with red-hot pincers because there was some real or perceived problem.

And those release notes are NOT automatically accessible from the IDE: people have to actively go and locate them.

When I did that just now I found they had not been updated since 1 August, so there were no details of the most recent slew of upgrades.

These are only tiny little tweaks, nothing much to write home about - I mean, I'd like to be fixing bigger issues like in the engine... THAT would be worthy of a detailed writeup.

nothing much to write home about

Are you sure?

For all you know I just wrote about the changes to Mother.

richmond62 wrote: ↑Sat Aug 17, 2024 1:44 pm For all you know I just wrote about the changes to Mother.

I'm glad she's taking an interest.

In all seriousness though, I know what you mean - I don't have a github thing detailing what changes I've made, but I do keep a track of all the changes - past and present if people are interested (also it would mean that people can replicate all my changes or build OXT for themselves from scratch - if they wanted to assemble it themselves... if they enjoy "challenge-seeking" or feeling particularly sadomasochistic). I don't know why people would want to do that though, so it's why I've made it more and more of an automated process.

Edit: I've just added something regarding that. If you were to go into the Preferences, automatic updates - it can now load a summary of the last update (rather than anyone having to go looking for an update text file if they felt so inclined).
That should keep mother happy!

It conveys the idea that those who procrastinate or don't take action will not achieve anything.

Do you mean that perhaps the updates aren't happening as quickly as you'd like? I'm not sure what you mean...
I think these little changes I'm making are all very well, but I feel like it's just 'treading water' when we should be swimming lengths of the pool: without someone working on the C++ engine part, it's all a bit of a moot point.

I was just having a bit of fun as I felt that one or two people round these parts were taking things a bit too seriously.
- -
Re: Engines.

Could this be resolved by restoring the Release Notes.pdf to the Help menu? Terry

TerryL wrote: ↑Sat Aug 17, 2024 4:34 pm Could this be resolved by restoring the Release Notes.pdf to the Help menu? Terry

I only haven't included that in the help menu because the "release notes.pdf" is now out of date.
(and of course, where it's referenced in the user guide).
If I was to update these each time, that would be extra files to generate and extra downloads to do each time - I was just trying to keep things minimal.
I'll relink this PDF in the menu when I release 1.08 (when we have enough changes to actually justify it), and will update the "release notes.pdf" with the info from here. (might just be easier to have the IDE load that changes page though).

How about having a 'Release Notes' stack that is part of the IDE?

All you really have to do then is append changes each time to a scrolling list field.

Yes, that's an idea too... okay, leave it with me.

You covered their name but left their avatar. If the goal of covering the name was anonymity, that was undone by including the public-facing avatar.

Either way, why clog up this donated forum DB with images of at-best-specious value to the project?

Shared compute resources are a gift. Let's repay gifts with valuable contributions to the world.