Many Cards Versus One Card and a List Field

Mikey mikeythek at gmail.com
Tue Jan 15 14:22:06 EST 2008


Russell,
I'm kind of late replying to this comment (re your dismay).

I understand your frustration, and I agree with you.  RR has lots of
warts, and this is one of them.  I have not been able to use it as my
primary development tool because I develop mainly database-centric
applications, and RR's implementation of the HC paradigm isn't what I
expected, either.

HOWEVER, RR's ODBC routines are simple to use and are quick.  The
ability to hack RR is rare in development tools.  I was able to write
a general purpose ODBC front-end including list and individual record
form layouts in almost no time at all, which was cool, and I was able
to implement interface features that RR was missing (such as
splitters) very quickly and with very little effort.

So, yep, it needs work.  Yep, it's buggy.  Nope, it isn't perfect, and
yep, it would be better if the card paradigm was more in line with HC.

But, for the time being it appears that it should work ok for you, and
when your needs outgrow it, it looks like it will be pretty easy to
write some front-end scripts that will substitute a database back end
for RR's native card format, but not sacrifice your effort.


I will repeat here yet again that the fact that we can't hack RR
commands makes the previous action more difficult, but it is what it
is, and it is certainly easier to hack in general than HC ever was.



More information about the use-livecode mailing list