Thanks again for the replies Bernard and Richard. I have learned a lot in these
conversations. In my LC coding life I have not had to use an SQL database or
JSON, and as I have my work cut out just getting to understand iOS development
and all that it implies (including non-technical stuff like
one can even store fields that contain returns - replace them with an
'invisible' character such as vertical tab and each record will be one
line. Tab-delimited text is so much easier to deal with - the text chunking
commands you already know work great - and are very fast.
On 24 January 2012 11:5
> Ken - ever helpful! I'm sorry I grumbled about not getting replies. That's
> just stupid, given that everyone on this list is busy, and it's bad manners
> too. Anyway your reply (which I haven't quoted in full) shows me how to get
> round my specific issues, so I see that it can be done: what
Graham Samuel wrote:
> However the real reason that I'm trying to go down the XML route is
> that I need this data to persist and I don't want the overhead of
> storing it in a stack rather than just keeping a trivial amount of
> text which furthermore could be easily examined/edited by non-LC
>
Thanks for the replies:
Bob - I know about the 'host of commands' and I've done a lot of worked
examples with them. It's the fact that LiveCode is happy with XML that was a
factor in making me think of using it - that and the fact that, for my
purposes, all the data could be saved in a triviall
You could also consider using JSON instead of XML. Particularly since
we have 2 libraries around which convert LiveCode arrays to JSON and
vice-versa. JSON is known as "the fat-free xml". I don't think
either format is paritcularly easy to scan by the naked eye. One
library is by Andre, the oth
> If you're using my script-only stsXMLLibrary, you'd do this:
>
> put "/root/employees" into tRootNode -- makes it easier to work with
> put stsXML_LoadData(tMyXML) into tDocID
> put stsXML_AppendChild(tDocID & tRootNode,"ELEM","employee") into tNewNodeID
> get stsXML_SetAttribute(tNewNodeI
On Jan 23, 2012, at 10:34 AM, Graham Samuel wrote:
> Pete - thanks for your reply (the only one so far - are there no XML users on
> the list??).
Sorry, Graham… was a bit busy before to respond.
> I notice that people tend to use employee lists and the like; but so far I
> haven't found a ve
Doesn't Livecode have a complete XML Library? I just searched for XML in the
dictionary and came up with a host of commands. I bet studying these would shed
some light on what needs to be done. Also, perhaps looking at a simple XML file
would benefit you. Many Apple prefs files are XML I think.
Pete - thanks for your reply (the only one so far - are there no XML users on
the list??). I understand that arrays would do the job, since the array
structure in LC can be extended at will rather than having to be declared
before use, although I'm not sure about a structure where some 'nodes' w
Graham-
Sunday, January 22, 2012, 6:45:40 AM, you wrote:
> For no special reason I have never used XML, either in LiveCode
> or anywhere else. Now I'm scripting an app that calls for a tiny
> database containing a number of similarly structured records
> (probably not more than 50), with all the
Hi Graham,
I'll say upfront that I'm not familiar with XML so I'm really suggesting an
alternative rather than answering your question.
Have you thought about using LC arrays rather than XML for this? LC arrays
are lightning fast to access and I think would work great for a small
dataset like thi
Graham,
Without giving away any trade secrets, could you describe where the data is
stored and how it will be displayed?
Mike
--- On Sun, 1/22/12, Graham Samuel wrote:
From: Graham Samuel
Subject: Navigating XML in LiveCode
To: use-livecode@lists.runrev.com
Date: Sunday, January 22, 2012, 8
13 matches
Mail list logo
