Re: Improving the LiveCode release notes

[J. Landman Gay]

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 everything is in pdf format.
That would be great. Maybe the team could give you the original documents 
before they were made into PDFs? 
-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[J. Landman Gay]

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
>> anything?
>
>Well, *I* do, but maybe it's just me. 
I read them too just to check the progess, so there's at least two of us. 
-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[J. Landman Gay]

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 dictionary or 
which release introduced it. 

This may be too large a scope for inclusion in the IDE but it would be nice to 
have a website or somewhere with an inclusive search. Richard has collected all 
the release notes at LiveCode Journal but that still requires opening each file 
and searching it separately. 

On December 15, 2015 3:20:17 AM CST, Peter TB Brett  
wrote:
>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!
>
>I've added a feature request here:
>
>http://quality.livecode.com/show_bug.cgi?id=16604
>
>Peter

-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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 Fraser's note a while back, but haven't gotten around to 
fiddling with the build files.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter Haworth]

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 with Monte that the whole section on Platform Support,
Installation, etc should be in a separate document with the release notes
only documenting any changes that apply to that document.

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 (or having a separate Widgets Guide), which
is where the Widget information should be.

Having said all that, I think LC8 is not a typical release since there have
been so many DP releases and presumably there'll be RC releases too before
we're done.

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 everything is in pdf format.

Pete
lcSQL Software 
Home of lcStackBrowser  and
SQLiteAdmin 

On Tue, Dec 15, 2015 at 9:16 AM, 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
>> anything?
>>
>
> Well, *I* do, but maybe it's just me. When we do weekly releases at work I
> do the same for historical tracking. Otherwise it's really hard to query a
> bug-tracking tool (I'm talking at you, bugzilla) to get a list of the bugs
> that were fixed/features added for a given release. If a bug that was fixed
> in a previous release pops up again in a later one, I can go back in the
> release notes and see when it was fixed, and that narrows the window for
> finding the code changes. But if I'm the only one who cares about this
> stuff then I'm ok with dropping the sections from the release notes.
>
> --
>  Mark Wieder
>  ahsoftw...@gmail.com
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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 db will be the hard part
since I
think everything is in pdf format.

That would be great. Maybe the team could give you the original
documents before they were made into PDFs?


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 release note documents.


Ideally, the information about in which release each piece of LiveCode 
Script syntax was last updated should actually just be in the dictionary 
entry itself and should be searchable through the dictionary interface.


   Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit! 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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 do the same for historical tracking. Otherwise it's really hard to 
query a bug-tracking tool (I'm talking at you, bugzilla) to get a list 
of the bugs that were fixed/features added for a given release. If a bug 
that was fixed in a previous release pops up again in a later one, I can 
go back in the release notes and see when it was fixed, and that narrows 
the window for finding the code changes. But if I'm the only one who 
cares about this stuff then I'm ok with dropping the sections from the 
release notes.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[J. Landman Gay]

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 release note documents.
>
>Ideally, the information about in which release each piece of LiveCode 
>Script syntax was last updated should actually just be in the
>dictionary 
>entry itself and should be searchable through the dictionary interface.

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. A searchable 
database of all release notes would solve that, since we could enter a more 
generic string to search on. 

I also find that the release notes, at least earlier ones, contain more 
extensive explanations of new syntax and changes than the short synopsis 
provided in the dictionary. That's very helpful. 
-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter Haworth]

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:
>
> 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 (or having a separate Widgets Guide), which
>> is where the Widget information should be.
>>
>
> There's already a separate widgets guide, which contains all of the
> explanatory information from the release notes, in more detail, and much
> more besides.  It's available in the "Guides" tab of the dictionary stack
> -- you're looking for the "Extending LiveCode" guide.  The bits on widgets
> in the release notes are just a summary (for people who haven't used LC8
> before) and info on what's changed since earlier developer preview releases
> (for people who have).
>
> BTW, Ali has done some work today on improving the layout and
> accessibility of the guides in the IDE.
>
>  Peter
>
> --
> Dr Peter Brett 
> LiveCode Open Source Team
>
> LiveCode on reddit! 
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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 (or having a separate Widgets Guide), 
which

is where the Widget information should be.


There's already a separate widgets guide, which contains all of the 
explanatory information from the release notes, in more detail, and much 
more besides.  It's available in the "Guides" tab of the dictionary 
stack -- you're looking for the "Extending LiveCode" guide.  The bits on 
widgets in the release notes are just a summary (for people who haven't 
used LC8 before) and info on what's changed since earlier developer 
preview releases (for people who have).


BTW, Ali has done some work today on improving the layout and 
accessibility of the guides in the IDE.


 Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit! 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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!


I've added a feature request here:

http://quality.livecode.com/show_bug.cgi?id=16604

   Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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 the LiveCode release notes more informative and helpful.


The release notes mention Raspberry Pi, but it's been a while (April)
since there was a release for the pi, and there's never been an 8.0
release for that platform.


Heh, it is a bit misleading.  We *support* rPi, but we don't build for
it!  As I understand it, we intend to start releasing rPi-compatible
linux-arv6hf builds before LiveCode 8.0.0 final release.


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 :-(

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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
lists?


Good plan.

How useful are those sections?  Does anyone actually rely on them for 
anything?


The majority of the "dictionary changes" appear to be, "Fix some 
formatting" or "Tweak some grammar" rather than any change to the actual 
behaviour of the syntax.


  Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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 and helpful.


The release notes mention Raspberry Pi, but it's been a while (April)
since there was a release for the pi, and there's never been an 8.0
release for that platform.


Heh, it is a bit misleading.  We *support* rPi, but we don't build for 
it!  As I understand it, we intend to start releasing rPi-compatible 
linux-arv6hf builds before LiveCode 8.0.0 final release.


Fraser has a pull request that tweaks the build configuration files to 
make it easier to build for rPi. 
https://github.com/livecode/livecode/pull/3398


I need to set up a build worker for rPi on our CI system... maybe after 
I deal with the release notes.


   Peter :-)

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Dave Kilroy]

Peter, the extra info and up to date info on Xcode and Android in the DP11
release notes are great :)

In general, the DP11 release notes are already a big improvement on earlier
versions

Dave


Peter TB Brett wrote
> 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-asked question is which version of xTools is needed for iOS
>> deployment.
> 
> Is the info in the "Platform Support: iOS" section of the 8.0.0-dp-11 
> release notes not enough?  What else should be in there?
> 
>   Peter
> 
> -- 
> Dr Peter Brett 

> peter.brett@

> 
> LiveCode Open Source Team
> 
> LiveCode on reddit: https://reddit.com/r/livecode
> 
> ___
> use-livecode mailing list

> use-livecode@.runrev

> 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://runtime-revolution.278305.n4.nabble.com/Improving-the-LiveCode-release-notes-tp4699500p4699537.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Monte Goulding]

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, Peter TB Brett  wrote:
> 
> Our release notes aren't generated from the git log, for various reasons -- 
> often git commit log comments are not written with the end user of the 
> software as the intended reader.  And of course rewriting the git log for 
> every LiveCode 8 git commit would be perhaps too resource-intensive a task. 
> ;-)

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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-asked question is which version of xTools is needed for iOS
deployment.


Is the info in the "Platform Support: iOS" section of the 8.0.0-dp-11 
release notes not enough?  What else should be in there?


 Peter

--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter TB Brett]

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 


Basically I think the above could be resolved and things simplified in general 
if the installation guide is a separate file. Maybe even a separate file per 
platform.


Yes, I want to make the installation guide separate, but I'm not sure 
that I'll be able to do that in time for LiveCode 8.


Actually, for the server, I'd rather write a "Server Deployment" guide 
to live in the IDE (and on a currently hypothetical 
automatically-updated documentation website).  The actual *installation* 
of LiveCode server is very straightforward, but integrating it into 
Apache / nginx / (insert HTTP server here) is entirely another order of 
magnitude of difficulty.



A loong time ago I had fun with git on a rainy weekend and came up with a web 
app that was intended to be a github/bitbucket service hook. Here’s what it 
pumped out:

http://ecove.on-rev.com/mergext.com/notes.html 


Actually it’s markdown files that are pumped out and the above page is rentered 
by flatdoc http://ricostacruz.com/flatdoc/

I even registered git-v.info but I never got around to deploying it after 
realising the server resources required could blow out quite rapidly. I’ve 
still got the code though it probably needs some extra work to handle the 
multiple notes directories and multiple development branches that the repo now 
has. The basic idea was that people could see exactly which version a change 
was made in and link to the commit and bug report and also see what is upcoming 
on a release branch and on the development frontier.

Anyway, I’m positive you know how to get the notes out of git in the same way I 
did here I just thought you might be interested to see the format and how live 
updates to the notes via a service hook could be used to let people know what’s 
on the way etc.


Our release notes aren't generated from the git log, for various reasons 
-- often git commit log comments are not written with the end user of 
the software as the intended reader.  And of course rewriting the git 
log for every LiveCode 8 git commit would be perhaps too 
resource-intensive a task. ;-)


 Peter


--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Richard Gaskin]

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 Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter M. Brigham]

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 everything is in pdf format.

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. The front end could be an LC stack, 
with multiple options to display all notes, just the ones for the latest 
update, notes for a specific version, or notes related to a specific feature, 
or...

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Peter M. Brigham]

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?

Easier for Edinburgh to update a database? Then the stack is always up to date, 
just access the DB if online, or access a downloaded copy if offline. Data 
separate from UI, right?

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Pyyhtiä Christer]

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.  Believing that every developer has sufficient bandwidth 
available, this web site should replace the IDE embedded dictionary.

These should be fairly easy to be maintained by RR.

Ideally, the User / Reference manual could also base on wiki.


Christer Pyyhtiä
MindCrea Ltd
Mobile: +358-400-410216
Skype:  christerp1
chris...@mindcrea.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[[-hh]]

> 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/livecode
[3] Link to QC http://quality.livecode.com/
[4] progressState of LC Builder is 
[5] progressState of HTML5 builder is 
[6] progressState of other features  is 
[7] Health and Wealth of LC-team is  and 

The big development steps/improvements are and will be
described better in LC blogs and articles(TWIL) anyway.
By the above they'll attract better attention.

So you are ready in ten minutes to start with setting up
a build worker for RaspberryPi.

Just launch your rockets for that, please! :-))
And don't forget to invite Fraser for this trip.

Hermann

p.s. You'll win also this 'test engine':
Test a stack in the IDE on RaspberryPiB --- the speed is very
close to that you can await for a HTML standalone for a medium
fast machine (or vice versa).


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Richard Gaskin]

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 needed for iOS 
deployment.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Monte Goulding]

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 resolved and things simplified in general 
if the installation guide is a separate file. Maybe even a separate file per 
platform.

A loong time ago I had fun with git on a rainy weekend and came up with a web 
app that was intended to be a github/bitbucket service hook. Here’s what it 
pumped out:

http://ecove.on-rev.com/mergext.com/notes.html 


Actually it’s markdown files that are pumped out and the above page is rentered 
by flatdoc http://ricostacruz.com/flatdoc/

I even registered git-v.info but I never got around to deploying it after 
realising the server resources required could blow out quite rapidly. I’ve 
still got the code though it probably needs some extra work to handle the 
multiple notes directories and multiple development branches that the repo now 
has. The basic idea was that people could see exactly which version a change 
was made in and link to the commit and bug report and also see what is upcoming 
on a release branch and on the development frontier. 

Anyway, I’m positive you know how to get the notes out of git in the same way I 
did here I just thought you might be interested to see the format and how live 
updates to the notes via a service hook could be used to let people know what’s 
on the way etc.

Cheers

Monte

> On 15 Dec 2015, at 4: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.
> 
> * What's good about the current LiveCode release notes?
> * How can we make them better?
> * What additional information would be helpful to include?
> * What can be removed or abbreviated to make them more concise?
> 
> For example, here are the LiveCode 8.0.0-dp-11 release notes:
> 
> http://downloads.livecode.com/livecode/8_0_0/LiveCodeNotes-8_0_0_dp_11.pdf
> 
> Please reply and let me know your thoughts -- or feel free to e-mail me 
> off-list.
> 
> Peter
> 
> 
> -- 
> Dr Peter Brett 
> LiveCode Open Source Team
> 
> LiveCode on reddit: https://reddit.com/r/livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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 idea to have the Android 
section have a link to






which are better step-by-step instructions. I can't vouch for the pc or 
mac versions, but I just updated the linux instructions the other day.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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 Raspberry Pi, but it's been a while (April) 
since there was a release for the pi, and there's never been an 8.0 
release for that platform.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Mark Wieder]

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 was proposed and never 
followed through on.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Improving the LiveCode release notes

[Peter TB Brett]

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 make them better?
* What additional information would be helpful to include?
* What can be removed or abbreviated to make them more concise?

For example, here are the LiveCode 8.0.0-dp-11 release notes:

http://downloads.livecode.com/livecode/8_0_0/LiveCodeNotes-8_0_0_dp_11.pdf

Please reply and let me know your thoughts -- or feel free to e-mail me 
off-list.


 Peter


--
Dr Peter Brett 
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[David Bovill]

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!)
>
> 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 make them better?
> * What additional information would be helpful to include?
> * What can be removed or abbreviated to make them more concise?
>
> For example, here are the LiveCode 8.0.0-dp-11 release notes:
>
> http://downloads.livecode.com/livecode/8_0_0/LiveCodeNotes-8_0_0_dp_11.pdf
>
> Please reply and let me know your thoughts -- or feel free to e-mail me
> off-list.
>
>  Peter
>
>
> --
> Dr Peter Brett 
> LiveCode Open Source Team
>
> LiveCode on reddit: https://reddit.com/r/livecode
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Improving the LiveCode release notes

[Ali Lloyd]

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 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 was proposed and never
> followed through on.
>
> --
>   Mark Wieder
>   ahsoftw...@gmail.com
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode