Rev Internal Data Structures

Sarah Reichelt sarah.reichelt at gmail.com
Tue Dec 20 22:09:31 EST 2005


Fields in a data stack that is hidden have almost the same access time
as custom properties, but they can be shown when necessary for easier
debugging.

Without being sure of your data structure, I would put each table in a
single field on it's own card. Then write functions to get & set this
data easily e.g. getTable, getCell, setTable, setCell. I wouldn't
recommend using Rev's tables as they are not very good yet, but you
can use a field with vertical & horizontal grids and tabstops to make
something similar, just handle the data editing yourself.

Fell free to ask again if you have any mroe questions.

Sarah


On 12/21/05, Lynch, Jonathan <bnz2 at cdc.gov> wrote:
> You'll get it going much much faster if you use custom properties rather
> than fields.
>
> I received an email from Sarah a while back that Revolution was
> perfectly
> capable of handling data through its own internal database structures
> (rather than have a newbie like myself work in mySQL).    I am primarily
> manipulating extensive tables of data, not unlike a huge spreadsheet
> with
> input from the user.
>
> Is this done by putting data in an invisible substack hundreds of
> fields,
> each containing a chain of data?
>
> I have gone through the Help section of Revolution but am not sure where
> to
> begin to familiarize myself with the internal data structure for naming
> conventions, etc.,
>
> Thanks,
> Michael
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the use-livecode mailing list