From j.peters at valentina-db.de Mon Jul 5 07:30:26 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Mon Jul 5 00:30:33 2004 Subject: [ANN] Development snapshot 1.0a60 Message-ID: <35190.62.154.199.179.1089005426.squirrel@webmail3.server-einstellung.de> Hi all, you can download version 1.0a60 (Win) from http://www.valentina-db.de/en/downloads/downvstd.shtml The Mac build will be available tomorrow. This version fixes several bugs which could cause crashes when accessing data on Valentina Server. It contains now all new icons for all buttons. You can now pass a complete path to a valentina database on the command line. This enables you to associate .vdb files with vStudio. The handling of encrypted databases has been improved. The Data browser can now show related tables. (tables linked with ObjectPtr-fields) This currently only works for local databases - support for Server databases will be added later. If you click on a record in the top browser then the related browser will show all records linked with it. Please note that not all funcionality is implemented now. But as you can see the Data browser in vStudio will have the same features as the one in VAPP. As usual please report any bugs, crashes. -- Best regards, Jochen Peters PIIT GmbH -------------------------- http://www.valentina-db.de From rwingate at visual-book.com Mon Jul 5 10:36:47 2004 From: rwingate at visual-book.com (Rob Wingate) Date: Mon Jul 5 09:36:59 2004 Subject: [ANN] Development snapshot 1.0a60 References: <35190.62.154.199.179.1089005426.squirrel@webmail3.server-einstellung.de> Message-ID: <006601c4629d$83bcc2f0$4c00a8c0@vbp.visualbook.com> Jochen, Thank you for build a60. In Column View, I can right-click the icon that represents my machine, and get the following popup list: __________________ | MY MACHINE NAME | |_________________| |_________________| | Close | |_________________| | New Database... | | Open Database...| |_________________| I always use this popup list to open and close my databases. The problem is, when I right-click the icon in List View, no popup appears. Is it difficult to wire the same menu to that icon? Thanks, Rob From sunshine at public.kherson.ua Mon Jul 5 17:42:23 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon Jul 5 09:42:48 2004 Subject: a60: BUG: CreateField, is not flushed Message-ID: Hi Jochen, I have made table and 2 fileds, then seat and think. Then DEMO dialog. Finish app. Open db and ops, I do not have tables and fields. I think that after Create table and a field you should add Flush(). -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Mon Jul 5 17:44:40 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon Jul 5 09:44:47 2004 Subject: a60: adding of records Message-ID: Hi Jochen, In the data browser we click button + You show new window with input layout. I enter values, press SAVE then window is closed and record is added. Good. But if I want add many records, I assume we need click in new window the button +. I assume this must save record, clean edit fields for next record. This not works. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Mon Jul 5 17:48:22 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon Jul 5 09:48:27 2004 Subject: a60: new related browsers Message-ID: Hi Jochen, 1) to see it working a man must create 2 tables linked by ObjectPtr. smart. 2) I see that you show RecID field. Valentina did not show it. I think this can be made a option. 3) I see that you allow edit ObjectPtr field. VAPP did not allow do that. To avoid entering of WRONG value which NOT point to any record. in Valentina 2.0 we have add protection from such mistakes. Valentina 1.x did not have protection on this. 4) I see that you have made column "x", but it not works yes. Right? -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Mon Jul 5 17:49:06 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon Jul 5 09:49:11 2004 Subject: a60: icon's mask is not ideal Message-ID: Hi Jochen I see that yellow icon of Table is not ideal. It has some garbage pixels around. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From j.peters at valentina-db.de Mon Jul 5 17:52:47 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Mon Jul 5 10:53:02 2004 Subject: [ANN] Development snapshot 1.0a60 In-Reply-To: <006601c4629d$83bcc2f0$4c00a8c0@vbp.visualbook.com> References: <35190.62.154.199.179.1089005426.squirrel@webmail3.server-einstellung.de> <006601c4629d$83bcc2f0$4c00a8c0@vbp.visualbook.com> Message-ID: <5C6ABD54-CE9B-11D8-B5E1-000A959F6B0C@valentina-db.de> Hi Rob, > Thank you for build a60. > > In Column View, I can right-click the icon that represents my machine, > and > get the following popup list: > > __________________ > | MY MACHINE NAME | > |_________________| > |_________________| > | Close | > |_________________| > | New Database... | > | Open Database...| > |_________________| > > I always use this popup list to open and close my databases. The > problem is, > when I right-click the icon in List View, no popup appears. Is it > difficult > to wire the same menu to that icon? No problem. I will add this for the next build. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Mon Jul 5 17:53:19 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Mon Jul 5 10:53:33 2004 Subject: a60: BUG: CreateField, is not flushed In-Reply-To: References: Message-ID: <6FD74968-CE9B-11D8-B5E1-000A959F6B0C@valentina-db.de> Hi Ruslan, > I have made table and 2 fileds, then seat and think. > Then DEMO dialog. Finish app. > > Open db and ops, I do not have tables and fields. > > I think that after Create table and a field you should add Flush(). Yes, of course! I will add it... -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Mon Jul 5 17:54:21 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Mon Jul 5 10:54:34 2004 Subject: a60: adding of records In-Reply-To: References: Message-ID: <9487A75E-CE9B-11D8-B5E1-000A959F6B0C@valentina-db.de> Hi Ruslan, > In the data browser we click button + > > You show new window with input layout. > I enter values, press SAVE then window is closed and record is > added. > Good. > > But if I want add many records, I assume we need click in new > window the > button +. I assume this must save record, clean edit fields for > next record. This not works. Yes - right. This must be added. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Mon Jul 5 17:56:51 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Mon Jul 5 10:56:56 2004 Subject: a60: new related browsers In-Reply-To: References: Message-ID: Hi Ruslan, > 1) to see it working a man must create 2 tables linked by ObjectPtr. > smart. Yes. > > > 2) I see that you show RecID field. Valentina did not show it. > I think this can be made a option. > > 3) I see that you allow edit ObjectPtr field. > VAPP did not allow do that. To avoid entering of WRONG value which > NOT point to any record. I have added RecID and editing of ObjectPtr for testing purpose only! It was very handy when developing the related browser. Of course it is no problem to hide the RecID and make ObjectPtr read-only. But before that i must finish the "x" column! > > in Valentina 2.0 we have add protection from such mistakes. > Valentina 1.x did not have protection on this. > > > 4) I see that you have made column "x", but it not works yes. Right? Yes - not ready, yet. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Thu Jul 8 18:05:39 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 8 11:05:52 2004 Subject: [ANN] Development snapshot for Mac Message-ID: Hi all, i have just uploaded a development snapshot of the Mac version (1.0a61) I call this a development snapshot because it is based on a completly new version of the underlying wx library. Because of this there are several issues with font sizes and sizes in general which will be fixed soon - so do not care about that. What you can see is that we get now more native controls - for example the divider between main and related browser in the data browser is now a native control. And - more Mac specific features are now supported - for example the property inspector now has a brush metal background.... The next public release will contain a complete functional related browser - supporting all set operations as it was in VAPP! I will soon finish this task. After that i will switch to unicode to integrate the new 2.0 valentina engine. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From martin at kinetix.co.uk Fri Jul 9 13:13:31 2004 From: martin at kinetix.co.uk (Martin Wright) Date: Fri Jul 9 07:15:16 2004 Subject: WIN 1.0a60 close all error In-Reply-To: Message-ID: <20040709121509.9B43F17641A@edison.macserve.net> Hi With the latest version of vStudio 1.0a60 (and previous versions) it crashes when I 'close all' after working on a Vserver database. After the crash I can no longer connect with vStudio. I have to restart the Vserver service. Also, in the recent server folder, all connections show the IP address. If I have several services running on the same IP I can't see which connection is which. It would be nice to be able to rename the connections or include the port number in the connection name. Martin From j.peters at valentina-db.de Fri Jul 9 17:16:28 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Fri Jul 9 10:16:44 2004 Subject: WIN 1.0a60 close all error In-Reply-To: <20040709121509.9B43F17641A@edison.macserve.net> References: <20040709121509.9B43F17641A@edison.macserve.net> Message-ID: Hi Martin! > With the latest version of vStudio 1.0a60 (and previous versions) it > crashes > when I 'close all' after working on a Vserver database. > After the crash I can no longer connect with vStudio. I have to > restart the > Vserver service. Ahh - ok - i will fix that. > > Also, in the recent server folder, all connections show the IP > address. If I > have several services running on the same IP I can't see which > connection is > which. It would be nice to be able to rename the connections or > include the > port number in the connection name. Yes - good point Martin - i will include the port-number. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From sunshine at public.kherson.ua Sat Jul 10 20:55:08 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Sat Jul 10 12:55:23 2004 Subject: Valentina Studio In-Reply-To: <00f801c465fb$38c55670$7f00a8c0@aslan> Message-ID: On 7/10/04 12:25 AM, "Elia Morling" wrote: > Hi, > I get kernel error 351 whenever starting the application. Any ideas? > The first time it ran without troubles. Elia, Pleas note that Valentina studio develop Jochen Peters. You should ask questions regarding Valentina Studio on its list I think link to VS site you will find from our home page www.paradigmasoft.com and here you will find how to subscribe to their list. -------- kFBL_CorruptedVarChar = 351, Hmm, how you can get corrupted VarChar. Jochen? Elia, Please try trash preferences of Valentina Studio. I think problem there. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From j.peters at valentina-db.de Sat Jul 10 20:00:56 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Sat Jul 10 13:01:12 2004 Subject: Valentina Studio In-Reply-To: References: Message-ID: <176F78A9-D29B-11D8-9C7D-000A959F6B0C@valentina-db.de> Hi Elia, i also think that problem comes from vsPrefsDB - try to find folder with that name on your PC and trash it completly. Am 10.07.2004 um 19:55 schrieb Ruslan Zasukhin: > On 7/10/04 12:25 AM, "Elia Morling" wrote: > >> Hi, >> I get kernel error 351 whenever starting the application. Any ideas? >> The first time it ran without troubles. > > Elia, > > Pleas note that Valentina studio develop Jochen Peters. > > You should ask questions regarding Valentina Studio on its list > > I think link to VS site you will find from our home page > www.paradigmasoft.com and here you will find how to subscribe to their > list. > > > > -------- > kFBL_CorruptedVarChar = 351, > > > Hmm, how you can get corrupted VarChar. > Jochen? > > Elia, > > Please try trash preferences of Valentina Studio. > I think problem there. > > > -- > Best regards, > Ruslan Zasukhin [ I feel the need...the need for speed ] > ------------------------------------------------------------- > e-mail: ruslan@paradigmasoft.com > web: http://www.paradigmasoft.com > > To subscribe to the Valentina mail list go to: > http://lists.macserve.net/mailman/listinfo/valentina > ------------------------------------------------------------- > > _______________________________________________ > Valentina-studio mailing list > Valentina-studio@lists.macserve.net > http://lists.macserve.net/mailman/listinfo/valentina-studio > > -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Thu Jul 15 20:49:47 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 15 13:50:32 2004 Subject: [ANN] Valentina Studio Admin 1.0a62 Message-ID: Hi all, you can download version 1.0a62 for both, Mac and Win, from http://www.valentina-db.de/en/downloads/downvstd.shtml Additional to many bugfixes it now includes a new related browser as in VAPP: Now works: - mark records in the main browser with "1", "2" and checkmark - Related browser shows: all records (linked ones are marked) only linked records (all marked) only free records (none marked) - All Set operations are working - Linking of records with single click in related browser - Unlinking of records with single click. Please note that the related browser is currently only available for local databases. It will start to work for server databases also when the client SDK will get the necessary API for this. Don't care about the GUI issues on the Mac side - i have not fixed them, yet. This is the last NON unicode build of vStudio - i will now switch to Unicode to integrate the new 2.0 engine. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From sunshine at public.kherson.ua Thu Jul 15 22:09:24 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 15 14:09:38 2004 Subject: [ANN] Valentina Studio Admin 1.0a62 In-Reply-To: Message-ID: On 7/15/04 9:49 PM, "Jochen Peters" wrote: > Hi all, > > you can download version 1.0a62 for both, Mac and Win, from > > http://www.valentina-db.de/en/downloads/downvstd.shtml > > Additional to many bugfixes it now includes a new related browser > as in VAPP: > > Now works: > - mark records in the main browser with "1", "2" and checkmark > - Related browser shows: > all records (linked ones are marked) > only linked records (all marked) > only free records (none marked) > - All Set operations are working > - Linking of records with single click in related browser > - Unlinking of records with single click. Jochen, You still have some VAPP missing features. 1) in VAPP when I click/select any record in TOP browser, Then new selected record always is marked as "1". So I click record -> see linked I click other record -> see its linked. In a62 now when I click COLUM "*" then yes, I see linked, But if I click other record then nothing changes. The prev record still is marked as "1" This is not comfortable. 2) in VAPP was special menu with commands as Mark All Unmark All ------------------ Other bugs 3) when we open by "+" the input dialog and enter new values, then only SAVE button work. button "+" in this dialog erase edit fields, but nothing add into tables. btw, after erase of fields, the first edit field should get focus. 4) ENTER on numeric keyboard should work as "Add Record and continue" I.e. It must work as "+" button in this input dialog. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From j.peters at valentina-db.de Thu Jul 15 21:21:10 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 15 14:21:17 2004 Subject: [ANN] Valentina Studio Admin 1.0a62 In-Reply-To: References: Message-ID: <21200C26-D694-11D8-B111-000A959F6B0C@valentina-db.de> Hi Ruslan, > You still have some VAPP missing features. > > > 1) in VAPP when I click/select any record in TOP browser, > Then new selected record always is marked as "1". > > So I click record -> see linked > I click other record -> see its linked. > > In a62 now when I click COLUM "*" then yes, I see linked, > But if I click other record then nothing changes. > The prev record still is marked as "1" Yes - marked selection only changes when you click in the first column - but this is easy to change. > > This is not comfortable. Ok - i will change that. > > > 2) in VAPP was special menu with commands as > > Mark All > Unmark All Correct - must be added. > > > ------------------ > Other bugs > > > 3) when we open by "+" the input dialog and enter new values, > then only SAVE button work. So - cancel do not work? I must check. > > button "+" in this dialog erase edit fields, but nothing add into > tables. Hhmm - i guess this is a refresh problem.. > btw, after erase of fields, the first edit field should get focus. Agree. > > 4) ENTER on numeric keyboard should work as "Add Record and continue" > I.e. It must work as "+" button in this input dialog. Ok. -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From sunshine at public.kherson.ua Thu Jul 15 22:38:18 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 15 14:38:30 2004 Subject: [ANN] Valentina Studio Admin 1.0a62 In-Reply-To: <21200C26-D694-11D8-B111-000A959F6B0C@valentina-db.de> Message-ID: On 7/15/04 10:21 PM, "Jochen Peters" wrote: > Hi Ruslan, > >> You still have some VAPP missing features. >> >> >> 1) in VAPP when I click/select any record in TOP browser, >> Then new selected record always is marked as "1". >> >> So I click record -> see linked >> I click other record -> see its linked. >> >> In a62 now when I click COLUM "*" then yes, I see linked, >> But if I click other record then nothing changes. >> The prev record still is marked as "1" > Yes - marked selection only changes when you click in the first column > - but > this is easy to change. >> >> This is not comfortable. > Ok - i will change that. And I can run in top table using narrow down or up keys. This select next/prev record in TOP browser, And should show linked records. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Thu Jul 15 22:40:12 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 15 14:40:18 2004 Subject: [ANN] Valentina Studio Admin 1.0a62 In-Reply-To: <21200C26-D694-11D8-B111-000A959F6B0C@valentina-db.de> Message-ID: On 7/15/04 10:21 PM, "Jochen Peters" wrote: >> ------------------ >> Other bugs >> >> >> 3) when we open by "+" the input dialog and enter new values, >> then only SAVE button work. > So - cancel do not work? I must check. I mean not Cancel, but button "+" >> button "+" in this dialog erase edit fields, but nothing add into >> tables. > Hhmm - i guess this is a refresh problem.. No it seems this is not refresh. I have open input dialog, I have try to add few records using "+" button. Then press SAVE button, and only last in table, And it have RecID = 1. So the prev records was simply not stored into table. >> btw, after erase of fields, the first edit field should get focus. > Agree. > >> >> 4) ENTER on numeric keyboard should work as "Add Record and continue" >> I.e. It must work as "+" button in this input dialog. > Ok. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From j.peters at valentina-db.de Thu Jul 29 20:33:55 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 13:34:04 2004 Subject: Fwd: Version 2 Message-ID: > 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@paradigmasoft.com > web: http://www.paradigmasoft.com > > To subscribe to the Valentina mail list go to: > http://lists.macserve.net/mailman/listinfo/valentina > ------------------------------------------------------------- > From j.peters at valentina-db.de Thu Jul 29 20:52:50 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 13:52:55 2004 Subject: Version 2 In-Reply-To: References: Message-ID: <7D56294E-E190-11D8-8C6E-000A959F6B0C@valentina-db.de> Hi Ruslan, >> 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 - very simple approach is that vStudio will guess that the structure of the database will be the same (for the trashed and the new db). AND: vStudio can safely IGNORE (or delete) preferences that makes no sense any more (for example the column width's of a deleted table) We are talking about non critical preferences here! So ignoring or deleting preferences is a safe operation... > > Well, this can be implemented as idea of STYLES in PageMaker/inDesign! This goes one step further! And yes! It is a good idea! > > >> 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. Yes! We will simply have one more file - for example with extension .gui. There is NO NEED for V4MD or V4RB developers to distribute this file with their solution! This is another advantage. > > Or you mean that Valentina Studio should maintain own single file to > keep > prefs for all dbs it have open? I think NO. 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 Exactly! > > 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 ? Yes - exactly! I think 4D and Omnis are using the same approach. > >> 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 Yes - but at least the Mac version of the kernel can put all requested files into single Package! This is the Mac way! (This is comparable to the 9.x variant to store everything in one physical file - which is a much weaker approach..) > >> So - what you think? > > I think you should right now forward this letter to Valentina Studio > list > and beta list for discussion. :-) Done :-) One more point: Later we will be able to store Scripts and "Application Logic" using vStudio. It is always a good idea to seperate this stuff from the data! Thinking about the future: In future versions of vStudio we wil have scripts which builds simple database applications using vStudio. If we will store these logic into the database itself we will soon get in trouble in case of updates... Having the "logic" (Scripts and preferences) in a seperate file the user only have to replace this .gui file... -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From rwingate at visual-book.com Thu Jul 29 14:58:34 2004 From: rwingate at visual-book.com (Rob Wingate) Date: Thu Jul 29 13:58:48 2004 Subject: Version 2 References: Message-ID: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com> Jochen and Ruslan, Since I use Valentina every day, and since column widths were mentioned, here's my opinion: Any off-the-shelf database program that allows the developer to view tables in a visual format maintains column-width settings for those tables. IOW, if I open my "Customers" table, the column widths are formatted how I left them last time. When I open my "Transactions" table, it must have its own column settings, and cannot use some global width setting. To me, this is obvious and expected behavior. Each table, and certainly each database, must retain its own settings. If it does not, it's not a useful program to see one's data visually. I could not justify purchasing that software. Also, for the database programs I use (Access, FileMaker, etc), I never need to trash my prefs. I have only done during VS beta, and after VS is released, I would expect to never need to do it. I believe MS Access solves this issue by adding a non-visible table to each database, in which settings are stored (I could be wrong). So the .gui file sounds like an interesting idea for VS. But I would expect the Valentina engine itself to not require them. I would not expect to deliver .gui files to my client. Thanks, Rob ----- Original Message ----- From: "Jochen Peters" To: Sent: Thursday, July 29, 2004 2:33 PM Subject: Fwd: Version 2 > 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@paradigmasoft.com > web: http://www.paradigmasoft.com > > To subscribe to the Valentina mail list go to: > http://lists.macserve.net/mailman/listinfo/valentina > ------------------------------------------------------------- > _______________________________________________ Valentina-studio mailing list Valentina-studio@lists.macserve.net http://lists.macserve.net/mailman/listinfo/valentina-studio From j.peters at valentina-db.de Thu Jul 29 21:08:37 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 14:08:44 2004 Subject: Version 2 In-Reply-To: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com> References: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com> Message-ID: Hi Rob, > Since I use Valentina every day, and since column widths were > mentioned, > here's my opinion: > > Any off-the-shelf database program that allows the developer to view > tables > in a visual format maintains column-width settings for those tables. Agree! > > IOW, if I open my "Customers" table, the column widths are formatted > how I > left them last time. Correct! > > When I open my "Transactions" table, it must have its own column > settings, > and cannot use some global width setting. > > To me, this is obvious and expected behavior. Each table, and > certainly each > database, must retain its own settings. If it does not, it's not a > useful > program to see one's data visually. I could not justify purchasing that > software. Yes Rob - the important point for this discussion is WHERE to store this kind of preferences! > > Also, for the database programs I use (Access, FileMaker, etc), I > never need > to trash my prefs. I have only done during VS beta, and after VS is > released, I would expect to never need to do it. Yes - of course. During the VS beta cycle it makes no much sense to update the prefs db - in a release build this will be completly different! > > I believe MS Access solves this issue by adding a non-visible table to > each > database, in which settings are stored (I could be wrong). maybe - yes. And i do not like that approach! But note: You CANNOT open access databases with other applications than Access!!! This is completly different from Valentina where you can have V4RB, V4MD or C++ applications using the same database! And some of them does NOT NEED this info! > > So the .gui file sounds like an interesting idea for VS. But I would > expect > the Valentina engine itself to not require them. I would not expect to > deliver .gui files to my client. Absolutly right!!! This is ONE advantage! You do not have to deliver this file to your clients - keeping your database as small as possible! > > -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From gregkowalski at earthlink.net Thu Jul 29 15:21:46 2004 From: gregkowalski at earthlink.net (Gregory Kowalski) Date: Thu Jul 29 14:21:14 2004 Subject: Import question In-Reply-To: <20040505171548.C710A11599A@edison.macserve.net> References: <20040505171548.C710A11599A@edison.macserve.net> Message-ID: <8828D2E5-E194-11D8-950F-000393DAB46A@earthlink.net> Hello, I would like to know what the procedure is for importing data in a txt file. I have no problems doing it with the Valentina app, but have had no success with Studio. I have version 1.0a62 Here is what I do: 1. I create the fields 2. I hit "import" 3. The wizard opens 4.I choose ASCII file 5. I brows to the txt file (tab delimited). The data appears in the window on the right. Funny thing is that the columns have no names. 6. I hit "next" then "Finish" and... nothing... The db is still empty. Thanks for your help greg From rwingate at visual-book.com Thu Jul 29 15:21:46 2004 From: rwingate at visual-book.com (Rob Wingate) Date: Thu Jul 29 14:21:57 2004 Subject: Version 2 References: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com> Message-ID: <00ee01c475a1$4d692f60$4c00a8c0@vbp.visualbook.com> Jochen, > the important point for this discussion is WHERE to > store this kind of preferences! Right. And a definite benefit of not storing settings in a non-visible table is not unnecessarily bloating the db size. Why not add a "Preferences" folder at the vStudio root level, for storing .gui files? Personally, I wouldn't care if VS didn't maintain and clean up the contents of such a folder; that's my own responsibility. File sizes for .gui files would be negligible anyway. If db prefs are to be stored outside the db itself (which I agree is a good idea), it makes more sense to me to locate those prefs inside the vStudio folder instead of in the User's folder. , Rob From rwingate at visual-book.com Thu Jul 29 15:27:44 2004 From: rwingate at visual-book.com (Rob Wingate) Date: Thu Jul 29 14:27:54 2004 Subject: Version 2 References: <7D56294E-E190-11D8-8C6E-000A959F6B0C@valentina-db.de> Message-ID: <010301c475a2$23d65fa0$4c00a8c0@vbp.visualbook.com> > There is NO NEED for V4MD or V4RB developers to > distribute this file with their solution! Glad to hear this. The separate file seems the best way to go in a multi-platform situation. Rob From j.peters at valentina-db.de Thu Jul 29 21:29:15 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 14:29:23 2004 Subject: Import question In-Reply-To: <8828D2E5-E194-11D8-950F-000393DAB46A@earthlink.net> References: <20040505171548.C710A11599A@edison.macserve.net> <8828D2E5-E194-11D8-950F-000393DAB46A@earthlink.net> Message-ID: <9424F108-E195-11D8-8C6E-000A959F6B0C@valentina-db.de> Hi Gregory, > > I would like to know what the procedure is for importing data in a txt > file. I have no problems doing it with the Valentina app, but have > had no success with Studio. > > I have version 1.0a62 > > Here is what I do: > > 1. I create the fields > 2. I hit "import" > 3. The wizard opens > 4.I choose ASCII file > 5. I brows to the txt file (tab delimited). The data appears in the > window on the right. Funny thing is that the columns have no names. > 6. I hit "next" then "Finish" and... nothing... The db is still empty. Well - this should generate an error! .-) You must DRAG the desired fields to the columns which are unnamed at the beginning! This way you can associate each field with it's column! -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Thu Jul 29 21:34:03 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 14:34:08 2004 Subject: Version 2 In-Reply-To: <00ee01c475a1$4d692f60$4c00a8c0@vbp.visualbook.com> References: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com> <00ee01c475a1$4d692f60$4c00a8c0@vbp.visualbook.com> Message-ID: <3FCD6A6C-E196-11D8-8C6E-000A959F6B0C@valentina-db.de> Hi Rob, >> the important point for this discussion is WHERE to >> store this kind of preferences! > > Right. And a definite benefit of not storing settings in a non-visible > table > is not unnecessarily bloating the db size. > > Why not add a "Preferences" folder at the vStudio root level, for > storing > .gui files? Hhmm - but when moving the db to a different computer you would have to search inside this maybe big preferences folder for the one file you will need for your db. Better to keep this file side by side with the .ind, .vdb files.. > > Personally, I wouldn't care if VS didn't maintain and clean up the > contents > of such a folder; that's my own responsibility. File sizes for .gui > files > would be negligible anyway. In future this files can grow if we will put more info into it. > > If db prefs are to be stored outside the db itself (which I agree is a > good > idea), it makes more sense to me to locate those prefs inside the > vStudio > folder instead of in the User's folder. I would prefer the folder where all other files (.vdb, .ind, .dat) are stored. What does others think? -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Thu Jul 29 21:34:43 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 14:34:48 2004 Subject: Version 2 In-Reply-To: <010301c475a2$23d65fa0$4c00a8c0@vbp.visualbook.com> References: <7D56294E-E190-11D8-8C6E-000A959F6B0C@valentina-db.de> <010301c475a2$23d65fa0$4c00a8c0@vbp.visualbook.com> Message-ID: <5786EFB8-E196-11D8-8C6E-000A959F6B0C@valentina-db.de> >> There is NO NEED for V4MD or V4RB developers to >> distribute this file with their solution! > > Glad to hear this. The separate file seems the best way to go in a > multi-platform situation. Yes. Absolutly. > > -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From rwingate at visual-book.com Thu Jul 29 15:54:36 2004 From: rwingate at visual-book.com (Rob Wingate) Date: Thu Jul 29 14:54:47 2004 Subject: Version 2 References: <00dc01c4759e$0fd97a90$4c00a8c0@vbp.visualbook.com><00ee01c475a1$4d692f60$4c00a8c0@vbp.visualbook.com> <3FCD6A6C-E196-11D8-8C6E-000A959F6B0C@valentina-db.de> Message-ID: <011501c475a5$e3903930$4c00a8c0@vbp.visualbook.com> Jochen, > but when moving the db to a different computer This didn't occur to me, because I do my development on one machine. If I did need to move them, I would understand the prefs would be lost. It's a good point -- developers may use dbs across multiple machines. Rob From j.peters at valentina-db.de Thu Jul 29 20:52:50 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Thu Jul 29 15:55:28 2004 Subject: Version 2 In-Reply-To: References: Message-ID: Hi Ruslan, >> 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 - very simple approach is that vStudio will guess that the structure of the database will be the same (for the trashed and the new db). AND: vStudio can safely IGNORE (or delete) preferences that makes no sense any more (for example the column width's of a deleted table) We are talking about non critical preferences here! So ignoring or deleting preferences is a safe operation... > > Well, this can be implemented as idea of STYLES in PageMaker/inDesign! This goes one step further! And yes! It is a good idea! > > >> 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. Yes! We will simply have one more file - for example with extension .gui. There is NO NEED for V4MD or V4RB developers to distribute this file with their solution! This is another advantage. > > Or you mean that Valentina Studio should maintain own single file to > keep > prefs for all dbs it have open? I think NO. 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 Exactly! > > 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 ? Yes - exactly! I think 4D and Omnis are using the same approach. > >> 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 Yes - but at least the Mac version of the kernel can put all requested files into single Package! This is the Mac way! (This is comparable to the 9.x variant to store everything in one physical file - which is a much weaker approach..) > >> So - what you think? > > I think you should right now forward this letter to Valentina Studio > list > and beta list for discussion. :-) Done :-) One more point: Later we will be able to store Scripts and "Application Logic" using vStudio. It is always a good idea to seperate this stuff from the data! Thinking about the future: In future versions of vStudio we wil have scripts which builds simple database applications using vStudio. If we will store these logic into the database itself we will soon get in trouble in case of updates... Having the "logic" (Scripts and preferences) in a seperate file the user only have to replace this .gui file... -- Best regards, Jochen Peters PIIT GmbH ------------------------------------ http://www.valentina-db.de From sunshine at public.kherson.ua Fri Jul 30 00:14:02 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 29 16:14:12 2004 Subject: Dbname.gui file for visual info Message-ID: Hi All, So Jochen say Having a seperate storage file (of course this will also be a Valentina database with a different extension) we do not have this disadvantages! 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! 2) We can save this preferences LOCALY for server database! (and of course the preference db can be also a server db, if needed!) 3) During development you can safely trash your db without loosing any preferences! 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. Now we have add: ----------- 5) .gui file is optional and it have sense only for Valentina Studio. V4RB/V4MD/... Develoepr do not need distribute It with their solutions. This file will never be created by V4RB/V4MD/... application. 6) .gui file have sense only for Valentina Studio. and it have sense only in conjuction with rest Valentina DB files. so it looks to be good idea, that this file must be created by Vstudio in the same folder where db is. 7) creation of this file must be on Vstudio. i.e. Valentina kernel do not know about this file, about this extension, ... ----------------- More ideas: 8) we can have for THE SAME database several different .gui files. this can be used to make solutions tuned for different groups of users. i.e. Data is data, and it is other question how we display them. 9) Jochen, it seems latest FileMaker was proud by their features in this area. May be there is sense for you to check it... ------------ ** I still do not see how you technically will be able link NOT DELETED .gui file to new db? What if new db is of different structure? How you will see that? What is difference only in one fields from 100? Already bad? Here many such small technical problems, Jochen. ---------- And the main, so it seems that if we go by this way, then you can do everything self? Yes? I must not put into engine nothing special for this file? And with 2.0 you have access to I_Volume so you can control self creation of Volume. And you can use even not relational tables, but simply one or few embedded files on that volume. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From gregkowalski at earthlink.net Thu Jul 29 17:28:36 2004 From: gregkowalski at earthlink.net (Gregory Kowalski) Date: Thu Jul 29 16:28:00 2004 Subject: Import problem In-Reply-To: <20040729205531.7DFBB1D800A@edison.macserve.net> References: <20040729205531.7DFBB1D800A@edison.macserve.net> Message-ID: <401B0230-E1A6-11D8-AE89-000393DAB46A@earthlink.net> Well, that's what i thought, but the dragging doesn't work! It kind of worked on the previous Studio I had, but it was always impossible to drag all the fields. I was hoping it was a bug that was fixed. Greg On Jul 29, 2004, at 4:55 PM, valentina-studio-request@lists.macserve.net wrote: > Hi Gregory, >> > >> I would like to know what the procedure is for importing data in a txt >> file. I have no problems doing it with the Valentina app, but have >> had no success with Studio. >> >> I have version 1.0a62 >> >> Here is what I do: >> >> 1. I create the fields >> 2. I hit "import" >> 3. The wizard opens >> 4.I choose ASCII file >> 5. I brows to the txt file (tab delimited). The data appears in the >> window on the right. Funny thing is that the columns have no names. >> 6. I hit "next" then "Finish" and... nothing... The db is still >> empty. > Well - this should generate an error! .-) > You must DRAG the desired fields to the columns which are unnamed at > the beginning! > This way you can associate each field with it's column! From elia at familjen.se Thu Jul 29 23:41:12 2004 From: elia at familjen.se (Elia Morling) Date: Thu Jul 29 16:41:21 2004 Subject: Compact & Defrag References: <20040729205531.7DFBB1D800A@edison.macserve.net> <401B0230-E1A6-11D8-AE89-000393DAB46A@earthlink.net> Message-ID: <000d01c475b4$c714d1d0$7f00a8c0@aslan> Any idea when the compact and defragment features will be added? I saw their places in the toolbar, but they didn't do anything for me. Elia From sunshine at public.kherson.ua Fri Jul 30 02:23:10 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 29 18:23:38 2004 Subject: Compact & Defrag In-Reply-To: <000d01c475b4$c714d1d0$7f00a8c0@aslan> Message-ID: On 7/30/04 12:41 AM, "Elia Morling" wrote: > Any idea when the compact and defragment features will be added? > I saw their places in the toolbar, but they didn't do anything for me. Hi Elia, I think that result of defragment() work you cannot see. Compact() should produce smaller files. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Fri Jul 30 02:24:24 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Thu Jul 29 18:25:06 2004 Subject: Compact & Defrag In-Reply-To: <000d01c475b4$c714d1d0$7f00a8c0@aslan> Message-ID: On 7/30/04 12:41 AM, "Elia Morling" wrote: > Any idea when the compact and defragment features will be added? > I saw their places in the toolbar, but they didn't do anything for me. Elia, Also can be that your db cannot be compacted, so you do not see difference. -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From j.peters at valentina-db.de Fri Jul 30 07:09:41 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Fri Jul 30 00:09:47 2004 Subject: Import problem In-Reply-To: <401B0230-E1A6-11D8-AE89-000393DAB46A@earthlink.net> References: <20040729205531.7DFBB1D800A@edison.macserve.net> <401B0230-E1A6-11D8-AE89-000393DAB46A@earthlink.net> Message-ID: <40846.62.154.199.179.1091164181.squirrel@webmail3.server-einstellung.de> Hi Greg, > Well, that's what i thought, but the dragging doesn't work! > > It kind of worked on the previous Studio I had, but it was always > impossible to drag all the fields. > > I was hoping it was a bug that was fixed. Ok - i will look into it and fix it for the next build. -- Best regards, Jochen Peters PIIT GmbH ------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Fri Jul 30 07:17:17 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Fri Jul 30 00:17:22 2004 Subject: Dbname.gui file for visual info In-Reply-To: References: Message-ID: <43452.62.154.199.179.1091164637.squirrel@webmail3.server-einstellung.de> > Having a seperate storage file (of course this will also be a Valentina > database with a different extension) we do not have this disadvantages! > 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! > 2) We can save this preferences LOCALY for server database! (and of course > the preference db can be also a server db, if needed!) > 3) During development you can safely trash your db without loosing any > preferences! > 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. > > > Now we have add: > > > ----------- > 5) .gui file is optional and it have sense only for Valentina Studio. > V4RB/V4MD/... Develoepr do not need distribute It with their > solutions. > This file will never be created by V4RB/V4MD/... application. Yes. > > > 6) .gui file have sense only for Valentina Studio. > and it have sense only in conjuction with rest Valentina DB files. > > so it looks to be good idea, that this file must be created by Vstudio > in the same folder where db is. Agree. > > > 7) creation of this file must be on Vstudio. > i.e. Valentina kernel do not know about this file, > about this extension, ... Yes, of course! > > > ----------------- > More ideas: > > 8) we can have for THE SAME database several different .gui files. > this can be used to make solutions tuned for different groups > of users. > > i.e. Data is data, > and it is other question how we display them. Good idea, yes! > > 9) Jochen, it seems latest FileMaker was proud by their features in this > area. May be there is sense for you to check it... I will have a look. > > > ------------ > ** I still do not see how you technically will be able link NOT DELETED > .gui > file to new db? > > What if new db is of different structure? > How you will see that? > What is difference only in one fields from 100? Already bad? > Here many such small technical problems, Jochen. Well - i must think about the technical solution, but i am sure that this is not a big problem. > ---------- > And the main, so it seems that if we go by this way, then you can do > everything self? Yes? Absolutly! > > I must not put into engine nothing special for this file? Exactly! > And with 2.0 you have access to I_Volume so you can control self creation > of > Volume. And you can use even not relational tables, but simply one or few > embedded files on that volume. Ahh - ok - i will study I_Volume.. -- Best regards, Jochen Peters PIIT GmbH ------------------------ http://www.valentina-db.de From j.peters at valentina-db.de Fri Jul 30 07:19:16 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Fri Jul 30 00:19:20 2004 Subject: Compact & Defrag In-Reply-To: <000d01c475b4$c714d1d0$7f00a8c0@aslan> References: <20040729205531.7DFBB1D800A@edison.macserve.net><401B0230-E1A6-11D8-AE89-000393DAB46A@earthlink.net> <000d01c475b4$c714d1d0$7f00a8c0@aslan> Message-ID: <44036.62.154.199.179.1091164756.squirrel@webmail3.server-einstellung.de> Hi Elia! > Any idea when the compact and defragment features will be added? > I saw their places in the toolbar, but they didn't do anything for me. They should work! I think i must only add a messagebox which tells something about the result. Ok - wil be added for the next build. -- Best regards, Jochen Peters PIIT GmbH ------------------------ http://www.valentina-db.de From sunshine at public.kherson.ua Fri Jul 30 08:44:47 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Fri Jul 30 00:44:55 2004 Subject: Dbname.gui file for visual info In-Reply-To: <43452.62.154.199.179.1091164637.squirrel@webmail3.server-einstellung.de> Message-ID: On 7/30/04 8:17 AM, "Jochen Peters" wrote: >> I must not put into engine nothing special for this file? > Exactly! >> And with 2.0 you have access to I_Volume so you can control self creation >> of >> Volume. And you can use even not relational tables, but simply one or few >> embedded files on that volume. > Ahh - ok - i will study I_Volume.. Although note, in Valentina 1.x you do not have access to Volume. But look! You even do not need that. If Valentina Studio will have both plugins for 1.x and 2.0 Then you always can do this gui file using 2.0 engine -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- From sunshine at public.kherson.ua Fri Jul 30 10:03:25 2004 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Fri Jul 30 02:03:33 2004 Subject: Dbname.gui file for visual info In-Reply-To: <43452.62.154.199.179.1091164637.squirrel@webmail3.server-einstellung.de> Message-ID: On 7/30/04 8:17 AM, "Jochen Peters" wrote: >> I must not put into engine nothing special for this file? > Exactly! >> And with 2.0 you have access to I_Volume so you can control self creation >> of >> Volume. And you can use even not relational tables, but simply one or few >> embedded files on that volume. > Ahh - ok - i will study I_Volume.. And usage of volume you can find in the FBL::DbStorage class -- Best regards, Ruslan Zasukhin [ I feel the need...the need for speed ] ------------------------------------------------------------- e-mail: ruslan@paradigmasoft.com web: http://www.paradigmasoft.com To subscribe to the Valentina mail list go to: http://lists.macserve.net/mailman/listinfo/valentina ------------------------------------------------------------- You From j.peters at valentina-db.de Fri Jul 30 11:12:55 2004 From: j.peters at valentina-db.de (Jochen Peters) Date: Fri Jul 30 04:13:03 2004 Subject: Dbname.gui file for visual info In-Reply-To: References: <43452.62.154.199.179.1091164637.squirrel@webmail3.server-einstellung.de> Message-ID: <41251.62.154.199.179.1091178775.squirrel@webmail3.server-einstellung.de> Hi Ruslan, > Although note, in Valentina 1.x you do not have access to Volume. > > But look! > > You even do not need that. > > If Valentina Studio will have both plugins for 1.x and 2.0 > Then you always can do this gui file using 2.0 engine Yes - currently i use the 1.x engine. I will change to 2.x for prefsdb and gui file later. > -- Best regards, Jochen Peters PIIT GmbH -------------------------- http://www.valentina-db.de