Re: Improving the LiveCode release notes

On Dec 15, 2015, at 4:07 PM, Richard Gaskin wrote: > Peter M. Brigham wrote: > > I'm hardly a database expert, but it sounds as if a database of > > release notes with a flexible front end is the way to go. > > It's not like there are that many of them - why not roll them into a simple > stack?

Re: Improving the LiveCode release notes

Peter M. Brigham wrote: > I'm hardly a database expert, but it sounds as if a database of > release notes with a flexible front end is the way to go. It's not like there are that many of them - why not roll them into a simple stack? -- Richard Gaskin Fourth World Systems Software Design and

Re: Improving the LiveCode release notes

On Dec 15, 2015, at 12:33 PM, Peter Haworth wrote: > Going back to the search issue, I'd be willing to spend some time creating > a database and an LC app to query, sort and extract. Creating the DB and > the app won't be difficult, populating the db will be the hard part since I > think everythi

Re: Improving the LiveCode release notes

On 12/15/2015 01:00 AM, Peter TB Brett wrote: How about alphabetizing the Dictionary Additions and Dictionary Changes lists? Good plan. How useful are those sections? Does anyone actually rely on them for anything? Well, *I* do, but maybe it's just me. When we do weekly releases at work I

Re: Improving the LiveCode release notes

I guess this next thought would be dealt with if we had the search capability that's been mentioned but I'd prefer the release notes to be ordered primarily by the release (DP!, DP2, etc) and within that the various sections for that release (Engine Changes, IDE Changes, Bug Fixes, etc). I agree

Re: Improving the LiveCode release notes

On 12/15/2015 11:09 AM, J. Landman Gay wrote: Most of the entries do show the initial release date in the dictionary but the problem is that we often can't recall what term to look up. Also, bug fixes don't necessarily fall into that category and probably won't show up in the dictionary. -

Re: Improving the LiveCode release notes

I agree it would be great to have that info in the dictionary and searchable but I'm guessing that's not top of the priority list right now. You mentioned an HTML version of the release notes. I've only found pdf files for the release notes, is the html version available somewhere? Pete lcSQL Sof

Re: Improving the LiveCode release notes

Thanks, good to know. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Tue, Dec 15, 2015 at 10:52 AM, Peter TB Brett wrote: > On 2015-12-15 17:33, Peter Haworth wrote: > > Th

Re: Improving the LiveCode release notes

On December 15, 2015 12:48:20 PM CST, Peter TB Brett wrote: > >All of the inputs for the release notes are in the git repositories. >There's also a LiveCode Script stack that does all the processing, >starting from Markdown snippets, and ending up with the final Markdown, > >HTML and PDF relea

Re: Improving the LiveCode release notes

On 2015-12-15 17:33, Peter Haworth wrote: The LC8 Release notes also include several pages of information about widgets which I think should be in a separate document, referred to by the release notes where necessary. But then that gets into the whole issue of getting the User Guide updated (

Re: Improving the LiveCode release notes

On 2015-12-15 18:22, J. Landman Gay wrote: On December 15, 2015 11:33:31 AM CST, Peter Haworth wrote: Going back to the search issue, I'd be willing to spend some time creating a database and an LC app to query, sort and extract. Creating the DB and the app won't be difficult, populating the

Re: Improving the LiveCode release notes

On December 15, 2015 11:16:31 AM CST, Mark Wieder wrote: >On 12/15/2015 01:00 AM, Peter TB Brett wrote: > >>> How about alphabetizing the Dictionary Additions and Dictionary >Changes >>> lists? >> >> Good plan. >> >> How useful are those sections? Does anyone actually rely on them for >> anythin

Re: Improving the LiveCode release notes

On December 15, 2015 11:33:31 AM CST, Peter Haworth wrote: > >Going back to the search issue, I'd be willing to spend some time >creating >a database and an LC app to query, sort and extract. Creating the DB >and >the app won't be difficult, populating the db will be the hard part >since I >think

Re: Improving the LiveCode release notes

On 12/15/2015 01:28 AM, Peter TB Brett wrote: Embarrassingly, I spoke to some of the core dev team this morning, and it turns out that I am (very) incorrect about how difficult it will be to start releasing rPi builds again. Peter :-( Bummer. I saw Fras

Re: Improving the LiveCode release notes

The current release notes are already available in the IDE (at least through v7,) but I think what's being asked for is the ability to search all previous notes. I've had the same problem, where I remember a new feature or syntax has been introduced but I can't recall the name to look up in the

Re: Improving the LiveCode release notes

> Peter wrote: > I need to set up a build worker for rPi on our CI > system... maybe after I deal with the release notes. This forces me to add also an egoist wish: The release notes could be shortened to 6-7 short lines. [1] LC version ... released on [2] Link to GitHub https://github.com/live

Re: Improving the LiveCode release notes

The simplest way in my mind would be one User / Reference Manual, which includes any change from previous version (release note) with for example XML markup, e.g.: This is V8.1.1 stuff... Further, any examples for any function should include a hyperlink to a web page explaining the use. Bel

Re: Improving the LiveCode release notes

Yes, my code generates the full markdown release notes using added change notes files between release tags in the repo which is what I presume you are doing. Definitely don't want to use the commit messages. Particularly the bulk of mine ;-) Sent from my iPhone > On 15 Dec 2015, at 7:58 pm, Pe

Re: Improving the LiveCode release notes

On 15/12/2015 09:06, Peter TB Brett wrote: On 14/12/2015 18:13, Mark Wieder wrote: On 12/14/2015 09:46 AM, Peter TB Brett wrote: Hi all, I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make t

Re: Improving the LiveCode release notes

On 14/12/2015 18:31, David Bovill wrote: For me Release notes should be available in a searchable format in the IDE. I get pretty tired of digging through pdf's to find core information? We can definitely put them in the IDE somehow. The changes I'm working on also make it easier to do that!

Re: Improving the LiveCode release notes

> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode - "The difference between genius and stupidity is; genius has its limits." - Albert Einstein -- View this message in context: http:

Re: Improving the LiveCode release notes

On 14/12/2015 18:13, Mark Wieder wrote: On 12/14/2015 09:46 AM, Peter TB Brett wrote: Hi all, I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative a

Re: Improving the LiveCode release notes

On 14/12/2015 18:00, Mark Wieder wrote: On 12/14/2015 09:46 AM, Peter TB Brett wrote: I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. How about alphabetizing the Dictionary Additions and Dictionary Changes li

Re: Improving the LiveCode release notes

On 15/12/2015 01:00, Monte Goulding wrote: Hi Peter I’m not sure if you’ve seen this report of mine or if your review of the release notes includes a review of server notes or is desktop only. http://quality.livecode.com/show_bug.cgi?id=16350

Re: Improving the LiveCode release notes

On 15/12/2015 00:28, Richard Gaskin wrote: Peter TB Brett wrote: I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. A frequently-ask

Re: Improving the LiveCode release notes

Hi Peter I’m not sure if you’ve seen this report of mine or if your review of the release notes includes a review of server notes or is desktop only. http://quality.livecode.com/show_bug.cgi?id=16350 Basically I think the above could be resol

Re: Improving the LiveCode release notes

Peter TB Brett wrote: I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. A frequently-asked question is which version of xTools is ne

Re: Improving the LiveCode release notes

Nope, that's in there. The example should probably be changed though, as revTools is now a script-only stack in a subdirectory and therefore doesn't need the .8 On Mon, Dec 14, 2015 at 6:42 PM Mark Wieder wrote: > On 12/14/2015 09:46 AM, Peter TB Brett wrote: > > > I'd really appreciate some fee

Re: Improving the LiveCode release notes

On 12/14/2015 09:46 AM, Peter TB Brett wrote: I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. I suggest dropping the section titled "IDE stacfiles named with version. (8.0.0-dp-1)". It seems like an idea that w

Re: Improving the LiveCode release notes

For me Release notes should be available in a searchable format in the IDE. I get pretty tired of digging through pdf's to find core information? On Monday, 14 December 2015, Peter TB Brett wrote: > Hi all, > > I'm currently working on the LiveCode 8 release notes (in preparation for > RC 1!) >

Re: Improving the LiveCode release notes

On 12/14/2015 09:46 AM, Peter TB Brett wrote: I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. The release notes say that jdk-6 is required for Android support. Are you sure that's not jdk-7? It might be a good

Re: Improving the LiveCode release notes

On 12/14/2015 09:46 AM, Peter TB Brett wrote: Hi all, I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. The release notes mention R

Re: Improving the LiveCode release notes

On 12/14/2015 09:46 AM, Peter TB Brett wrote: I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. How about alphabetizing the Dictionary Additions and Dictionary Changes lists? -- Mark Wieder ahsoftw...@gmail.c

Improving the LiveCode release notes

Hi all, I'm currently working on the LiveCode 8 release notes (in preparation for RC 1!) I'd really appreciate some feedback to help me understand how we can make the LiveCode release notes more informative and helpful. * What's good about the current LiveCode release notes? * How can we ma