Re: [ANN} LiveCode List Processor - Version 1

On 03/26/2016 08:48 AM, Peter W A Wood wrote: The save and load functions aren't there, though. In the sense that they are totally missing or you feel they are insufficient? In the sense that they weren't in the script. But now I see you've pushed a new commit. -- Mark Wieder

Re: [ANN} LiveCode List Processor - Version 1

Mark > On 26 Mar 2016, at 23:13, Mark Wieder wrote: > > On 03/25/2016 11:21 PM, Peter W A Wood wrote: >> I have found time to complete version 1 of my LiveCode List Processor. You >> can find it at https://github.com/PeterWAWood/LiveCode-ListProcessor > > Nicely done.

Re: [ANN} LiveCode List Processor - Version 1

On 03/25/2016 11:21 PM, Peter W A Wood wrote: I have found time to complete version 1 of my LiveCode List Processor. You can find it at https://github.com/PeterWAWood/LiveCode-ListProcessor Nicely done. The save and load functions aren't there, though. -- Mark Wieder ahsoftw...@gmail.com

[ANN} LiveCode List Processor - Version 1

I have found time to complete version 1 of my LiveCode List Processor. You can find it at https://github.com/PeterWAWood/LiveCode-ListProcessor Many of you may be wondering why I bothered to write it when LiveCode’s built-in list processing (of delimited strings) is very good. The main reason

Re: [ANN] LiveCode List Processor

On 2015-10-14 06:44, Richard Gaskin wrote: I'm not so sure. At first I was, but after Mark and Mark explained how common the ? convention is elsewhere I'm inclined to think that the most important thing is that the library works as *you* want it to, and if others learn a thing or two along the

Re: [ANN] LiveCode List Processor

Thanks for the explanation Monte > On 14 Oct 2015, at 08:33, Monte Goulding wrote: > > It’s a confusing topic. See the is really operator for more info. Under the > hood they are stored in the most efficient way they can be but it often > depends on the last

Re: [ANN] LiveCode List Processor

Peter W A Wood wrote: >> Richard Gaskin > >> Aside from MetaCard I've seen almost no other scripting language >> but Rebol that wholeheartedly embraced the concept of delivering >> applications over the wire. ... > If only Carl had found a partner whose marketing prowess was the > equal of his

Re: [ANN] LiveCode List Processor

I’ve added a few more “easy” functions today - append, copy, empty?, head, head?, poke, tail and tail?. The List Processor’s API is documented at https://github.com/PeterWAWood/LiveCode-ListProcessor Regards Peter

Re: [ANN] LiveCode List Processor

Peter W A Wood wrote: > Again, I am influenced by Rebol. I've not used Rebol, but have read much of its documentation at various points over the years. Carl Sassenrath is an interesting thinker, and his language reflects some very unusual and intriguing concepts. Aside from MetaCard I've

Re: [ANN] LiveCode List Processor

Richard > Richard Gaskin wrote: > > I've not used Rebol, but have read much of its documentation at various > points over the years. Carl Sassenrath is an interesting thinker, and his > language reflects some very unusual and intriguing concepts. > > Aside from

Re: [ANN] LiveCode List Processor

> On 14 Oct 2015, at 11:27 am, Peter W A Wood wrote: > > As I understand, LiveCode has very few types, mainly everything is a string > except for arrays and (maybe) objects. (I say maybe as my knowledge of > LiveCode is insufficient in the area of how Objects are

Re: [ANN] LiveCode List Processor

What I do is load all (or blocks) of the data all at once, put it into a data grid, then navigate through the records in the data grid. I trap selectionChanged in the datagrid to populate the detail fields on the form. I have an edit bar for creating new, editing existing and deleting existing

Re: [ANN] LiveCode List Processor

Peter W A Wood wrote: > LiveCode chunking is great for handling lists but, as far as I > can tell, is missing forward and backward navigation through > lists. I decided to write a few simple functions to come up > with such a mechanism. > > I suspect that there may be an existing way to navigate

Re: [ANN] LiveCode List Processor

Mark Waddingham wrote: On 2015-10-12 18:41, Richard Gaskin wrote: That looks like Builder rather than Script, no? No - this is definitely a LiveCode Script library... It implements a data-type on top of an LCS array very much like the LCB 'List' type. What threw me was a function with the

Re: [ANN] LiveCode List Processor

On 2015-10-12 19:46, Richard Gaskin wrote: I've never seen question marks in handler names in any xTalk I've ever used, so I figured perhaps it might be something specific to Builder. It's a standard convention in some languages (Scheme springs to mind) to indicate a 'predicate' - a function

Re: [ANN] LiveCode List Processor

On 2015-10-12 18:41, Richard Gaskin wrote: That looks like Builder rather than Script, no? No - this is definitely a LiveCode Script library... It implements a data-type on top of an LCS array very much like the LCB 'List' type. (Such 'proper lists' - aka dense integer numerically-keyed

Re: [ANN] LiveCode List Processor

Peter W A Wood writes: > Perhaps you would be kind enough to let me know of existing ways to > achieve what this small library does before I spent more time developing it? Nicely done. I submitted a PR to keep things moving along. Aside from folks having to reinvent list

Re: [ANN] LiveCode List Processor

Mark Waddingham writes: > To be fair '?' poses less of a problem in this regard than '.' - in > terms of limiting future options that have been discussed at length in > the past ;) I use '?' suffixes all the time in Ruby code, so from my perspective... yes, it's definitely

Re: [ANN] LiveCode List Processor

Mark Wieder wrote: > Peter W A Wood writes: > >> Perhaps you would be kind enough to let me know of existing ways >> to achieve what this small library does before I spent more time >> developing it? > > Nicely done. I submitted a PR to keep things moving along. > Aside from folks having to

Re: [ANN] LiveCode List Processor

Richard Gaskin writes: > Given the simplicity of chunk expressions, is that needed? Absolutely. LiveCode doesn't without additional complexity support singly- or doubly-linked listed of arbitrary objects. -- Mark Wieder ahsoftw...@gmail.com

Re: [ANN] LiveCode List Processor

Never mind objects; we could restate it as "LC has no way to handle lists of arbitrary chunks of data". Your phrase " ... simple matter of ... return-delimited chunk ..." hides the the real issue: what if the chunks of data might contain 'return's ? You can find another character

Re: [ANN] LiveCode List Processor

Alex Tweedly wrote: > Never mind objects; we could restate it as "LC has no way to > handle lists of arbitrary chunks of data". > > Your phrase " ... simple matter of ... return-delimited chunk ..." > hides the the real issue: > what if the chunks of data might contain 'return's ? For

Fwd: [ANN] LiveCode List Processor

Bob > On 12 Oct 2015, at 23:29, Bob Sneidar > wrote: > > What I do is load all (or blocks) of the data all at once, put it into a data > grid, then navigate through the records in the data grid. I trap > selectionChanged in

Re: [ANN] LiveCode List Processor

Mark Wieder wrote: > Richard Gaskin writes: > >> Given the simplicity of chunk expressions, is that needed? > > Absolutely. LiveCode doesn't without additional complexity support > singly- or doubly-linked listed of arbitrary objects. I realize extra code is needed to implement linked lists of

Re: [ANN] LiveCode List Processor

Mark > On 13 Oct 2015, at 01:32, Mark Waddingham wrote: > > On 2015-10-12 18:41, Richard Gaskin wrote: >> That looks like Builder rather than Script, no? > > No - this is definitely a LiveCode Script library... It implements a > data-type on top of an LCS array very much

Re: [ANN] LiveCode List Processor

Kay > On 13 Oct 2015, at 11:36, Kay C Lan wrote: > > On Tue, Oct 13, 2015 at 7:49 AM, Richard Gaskin > wrote: > >> >> Peter's original problem statement was: >> >> LiveCode chunking is great for handling lists but, as far >> as I can

Re: [ANN] LiveCode List Processor

Mark > On 13 Oct 2015, at 04:01, Mark Wieder wrote: > > Peter W A Wood writes: > >> Perhaps you would be kind enough to let me know of existing ways to >> achieve what this small library does before I spent more time developing it? > > Nicely done. I

Re: [ANN] LiveCode List Processor

Mark > On 13 Oct 2015, at 01:58, Mark Waddingham wrote: > > On 2015-10-12 19:46, Richard Gaskin wrote: >> I've never seen question marks in handler names in any xTalk I've ever >> used, so I figured perhaps it might be something specific to Builder. > > It's a standard

Re: [ANN] LiveCode List Processor

+1 On Mon, Oct 12, 2015, 8:36 PM Kay C Lan wrote: > On Tue, Oct 13, 2015 at 7:49 AM, Richard Gaskin < > ambassa...@fourthworld.com> > wrote: > > > > > Peter's original problem statement was: > > > >LiveCode chunking is great for handling lists but, as far > >as

Re: [ANN] LiveCode List Processor

On Tue, Oct 13, 2015 at 7:49 AM, Richard Gaskin wrote: > > Peter's original problem statement was: > >LiveCode chunking is great for handling lists but, as far >as I can tell, is missing forward and backward navigation >through lists. Actually the

[ANN] LiveCode List Processor

I decided to convert a small card-based database stack to a “proper” database using SQLite. I immediately missed the next/previous card navigation features which were ideal for browsing the small database. LiveCode chunking is great for handling lists but, as far as I can tell, is missing