Re: A Text file format for LiveCode

2013-10-07 Thread Monte Goulding
On 08/10/2013, at 12:02 PM, Alejandro Tejada wrote: > Monte Goulding wrote >> Alejandro Tejada wrote: >>> 1) Search and Replace terms in all the handlers >>> of all stacks. Notice that many developers have published >>> stacks to export stacks as text, but this is a one way >>> conversion. >> We

Re: A Text file format for LiveCode

2013-10-07 Thread Alejandro Tejada
Hi Monte, Monte Goulding wrote > Alejandro Tejada wrote: >> 1) Search and Replace terms in all the handlers >> of all stacks. Notice that many developers have published >> stacks to export stacks as text, but this is a one way >> conversion. > We already have that in the IDE. Only for stacks alr

Re: A Text file format for LiveCode

2013-10-07 Thread Monte Goulding
On 08/10/2013, at 6:43 AM, Alejandro Tejada wrote: > 1) Search and Replace terms in all the handlers > of all stacks. Notice that many developers have published > stacks to export stacks as text, but this is a one way > conversion. We already have that in the IDE. > > 2) Commenting code will be

Re: A Text file format for LiveCode

2013-10-07 Thread Monte Goulding
On 08/10/2013, at 1:32 AM, Mark Wilcox wrote: > So, if the lcVCS route can be made to work robustly then optimising for > coding rather than optimising for serialising for version control seems like > a pretty good tradeoff. Yes that's the direction I'm going... keep working with the very conv

Re: A Text file format for LiveCode

2013-10-07 Thread Monte Goulding
On 08/10/2013, at 12:18 AM, David Bovill wrote: > You can use folders. I structure things as follows - toplevel we have an > array based representation of stacks, under which you can choose to export > this to either XML, JSON or my preferred representation text and folder > based. You need to b

Re: A Text file format for LiveCode

2013-10-07 Thread Alejandro Tejada
Hi Monte, Monte Goulding wrote >> Text format will be useful in many ways, but not >> for storing or sending stacks in the web. > > What ways.. other than version control? I understand that using text files to edit stacks sounds awfully similar to the methods of Third Generation Languages of "E

Re: A Text file format for LiveCode

2013-10-07 Thread Mark Wilcox
coding rather than optimising for serialising for version control seems like a pretty good tradeoff. Mark From: David Bovill To: How to use LiveCode Sent: Monday, 7 October 2013, 14:18 Subject: Re: A Text file format for LiveCode On 6 October 2013 23:46, M

Re: A Text file format for LiveCode

2013-10-07 Thread David Bovill
On 6 October 2013 23:46, Monte Goulding wrote: > > On 07/10/2013, at 8:52 AM, Dr. Hawkins wrote: > > The format is probably pretty obvious, too . . . > > > > begin button myBtn > > owner: card buttonville of stack buttonland > > type: pushbutton > > label: "My Favorite button" > > loc: 823

Re: A Text file format for LiveCode

2013-10-06 Thread Monte Goulding
On 07/10/2013, at 11:47 AM, Alejandro Tejada wrote: > But if you compress the text file with gzip or zip or > any other compression scheme... > Which size does have the compressed file? The 6KB stackFile which is exported as text as 336KB comes back down to 70KB when zipped. > Text format will

Re: A Text file format for LiveCode

2013-10-06 Thread Alejandro Tejada
Hi Monte, But if you compress the text file with gzip or zip or any other compression scheme... Which size does have the compressed file? Text format will be useful in many ways, but not for storing or sending stacks in the web. Have a nice week! Al -- View this message in context: http://r

Re: A Text file format for LiveCode

2013-10-06 Thread Monte Goulding
On 07/10/2013, at 8:52 AM, Dr. Hawkins wrote: > The format is probably pretty obvious, too . . . > > begin button myBtn > owner: card buttonville of stack buttonland > type: pushbutton > label: "My Favorite button" > loc: 823, 445 > width: 92 > height: 39 > > script: > on mouseup

Re: A Text file format for LiveCode

2013-10-06 Thread Monte Goulding
On 07/10/2013, at 6:20 AM, Alejandro Tejada wrote: > If LiveCode Community had, for default, a text file format > for LiveCode stacks, How could this benefit developers > and the platform at large? > > http://newsletters.livecode.com/october/issue158/newsletter1.php > > Thanks in advance! Hi

Re: A Text file format for LiveCode

2013-10-06 Thread Dr. Hawkins
On Sun, Oct 6, 2013 at 12:20 PM, Alejandro Tejada wrote: > If LiveCode Community had, for default, a text file format > for LiveCode stacks, How could this benefit developers > and the platform at large? > > > The biggest thing w