On Oct 14, 2008, at 5:06 PM, J. Landman Gay wrote:
-= JB =- wrote:
Many things can be done very fast because it is already being
done. Integrating it all can
not be that hard unless they are trying to rewrite it in a
different language and make it do
what is already being done with transcript.
Yup, that's the deal. The current "table" field in Rev's property
inspector is just a regular field with some scripts in it. The
functionality is faked. It's a sophisticated effort but is saddled,
by its nature, with limitations.
What others are talking about is an honest to goodness table object
implemented in the engine. Writing a new object for three operating
systems using a low-level language is, as you mentioned, a huge
undertaking. But if RR wants to have a real table, then that's what
they'd need to do.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
It seems to me that with a small amount of team work the current
table field
can be improved by leaps and bounds and then they can rewrite it in the
future if needed and slowly implement different features.
-=>JB<=-
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
