on 22/1/01 20:37, jbv at [EMAIL PROTECTED] wrote:

Hi jbv,

> Hello list,
> 
> I just spent some time checking Valentina for Metacard
> and must confess that I'm quite impressed. This thing
> could fit very well for a couple of projects I have pending
> right now...
> 
> But I have a couple of questions, especially regarding
> memory management. When saving a Metacard stack
> as a standalone, about 2.5 Mb (basically the Metatalk
> interpreter) are added to the stack.
> Valentina for Metacard is an XCMD, so I guess that to
> be fully operational it has to be added to the ressource
> fork of the stack, which should add another 600 Kb (the
> exact figure skips my mind right now) to the stack, right ?
> And is it the same for the Windoze version ?

on windows VXCMD will be always as separate DLL about 700KB.

On MAC we have include into VXCMD archive AddLib utility,
which allow you join shared lib "Valentina Engine" into resource fork.
Or you also can work with separate shared lib.

Also, note that database engine can require many RAM for big database, so
you need assign on MAC in finder GetInfo dialog more RAM for you final
standalone app.


> And what about the Valentina files (data, indexes...) ?
> Does the XCMD access them on the HD, or is there
> any benefit / possibility to upload them in RAM ?

By tests Valentina work with disk based fields faster than some RAM-based
databases (we have such user which come to Valentina).

You don't need do any efforts on putting of files to RAM,
Valentina has excellent cache system.

> Last but not least : is there somewhere any exhaustive
> list of all XCMDs available for Metacard (I'm especially
> interested in those running on Mac AND Win) ?
> 
> Thanks.
> 
> JB

-- 
Best regards,
Ruslan Zasukhin

-------------------------
Paradigma.

e-mail: [EMAIL PROTECTED]
web   : http://www.paradigmasoft.com

To subscribe to the Valentina mail list
send a letter to [EMAIL PROTECTED]



Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to