Fwd: Version 2

[Jochen Peters]

> Hi Jochen,
>
>> Ruslan - one important point of vStudio development still left open 
>> from
>> one of our previous discussions is:
>> "Storing database preferences and vStudio related stuff"
>>
>> I REALLY RECOMMEND to think again about that!
>>
>> Let me recall:
>>
>> Your approach (and also my first approach) was to store all this stuff
>> INSIDE the Valentina database. (For example using System Tables)
>>
>> Let us discuss the Pro's and Contra's of this approach
>>
>> Pro's
>> ------
>>
>> 1) All stuff is safely inside the database - when the user moves the
>> database then he will still have all it's database preferences - like
>> for example the column width in the Databrowser.
>>
>> Well - i really see only this one advantage :-) Please let me know
>> if you see anymore.
>>
>> Contra's
>> --------
>>
>> 1) This approach does not work for other databases we can use with 
>> vStudio
>>  via ODBC.
>
> yes
>
>> 2) Developers often want's to trash their db to start a fresh one - 
>> with
>>  this approach all preferences will be lost, too. (Can be very bad
>>  if you have defined several individual columns widths for the
>>  databrowser.)
>
> But how you going relate later preferences of _deleted_ database
> To new one ?
>
> Well, this can be implemented as idea of STYLES in PageMaker/inDesign!
>
>
>> 3) This will also mean that vStudio will ALWAYS change a user's 
>> database
>>  writing own stuff into it! I think this is very bad idea!
>
> May be
>
>> Having a seperate storage file (of course this will also be a 
>> Valentina
>> database with a different extension) we do not have this 
>> disadvantages!
>
> One more file?   .gui ?  :-)
> Interesting idea.
>
> But note, in Valentina use CAN say that all files must be in one 
> physical.
>
>> I see only advantages for this approach:
>> 1) We do not touch a users database! We can even open a read-only 
>> database
>>  and are still able to save preferences!
>
> Yes.
>
> So do you mean that EACH Valentina db must get own such file?
> I think yes.
>
> Or you mean that Valentina Studio should maintain own single file to 
> keep
> prefs for all dbs it have open? I think NO.
>
>> 2) We can save this preferences LOCALY for server database! (and of 
>> course
>>  the preference db can be also a server db, if needed!)
>
> Yes.
>
>> 3) During development you can safely trash your db without loosing any
>>  preferences!
>
> This is not usual behavior for other Valentina files. But why not.
> So I have
>
>     db.vdb, db.dat, db.ind, db.gui
>
> I trash the first 4. Now I create new db with the same name,
> Valentina see that such file already exists in the folder and do not 
> erase
> .gui file. This is what you want ?
>
>> 4) We currently recommend to use several files for security reasons - 
>> so
>> it does not matter to have one more! AND: On Mac you can put all files
>> into
>> single PACKAGE (which i would RECOMMEND to implement for 2.x) - on 
>> Windows
>> you can store all files in single folder.
>
> Single folder can make developer and put db files there
>
>> So - what you think?
>
> I think you should right now forward this letter to Valentina Studio 
> list
> and beta list for discussion. :-)
>
>
> -- 
> Best regards,
> Ruslan Zasukhin      [ I feel the need...the need for speed ]
> -------------------------------------------------------------
> e-mail: ruslan at paradigmasoft.com
> web: http://www.paradigmasoft.com
>
> To subscribe to the Valentina mail list go to:
> http://lists.macserve.net/mailman/listinfo/valentina
> -------------------------------------------------------------
>