Hi Wolfgang, thanks for the extensive feedback, I'l address the single points below.
In general, you have quite a few things which directly qualify as a bug, so I'd like to ask to to submit them in IssueZilla. At one time, they have to be in IZ, anyway, and you, who you know how to reproduce, are probably the best choice to submit them :) > May be the targets differ, the inventor looks on RC10, a user on the > functionality of Base, Calc ... as whole. As not-insider I can't > decide what belongs to the DB engine and what to the Base chassis. That's why I asked to just throw all your observations at me here in the list :) > 1.2 Too big (Impressiv :-)) ): Uses too match place of my > sreen! > 4 buttons (like toolbar), a selector and preview is > enough. > Tasks??? ->Use 3 buttons; Help text after 4s is usual > and enough. 'Description' is not consistent with other > tools. There's pro's and con's for this, and probably hard to find a solution which everybody likes. > 1.3 Default names: Add a prefix to 'Forms' and 'Reports' > like F_myDB, R_myDB and shorten the Query-myDB > accordingly (need less nerves to anwer the question > 'Are you shure you want to delete myDB) Uh. I personally wouldn't like this default prefix. Obviously you have another opinion :). Again, hard to find something which fits all. But feel free to submit an RFE (request for enhancement) in IssueZilla. Honestly, though, it would be P4, and may take some time until somebody looks at it .... > 1.4 Msg 'xx' has been modified. Do you want to save your > changes? > is usefull after a change but tedious leaving a tool > without any change. Then it's a bug. If you can reproduce this, please submit an issue in IZ. Note, however, than even things like changing a column width in the table data view is (rightfully) considered a change, since such things are stored in the .odb file, too. > > 2. Table Design: > 2.1 Selector 'Entry required' too > big: he masks the 'Length' field below. Not sure what you mean with "masks" > 2.2 Can't save Autovalue(BigInt)='Y', my setting changes to > 'No' during 'Save' IssueZilla is your friend :) > 2.3 'Table.Create View' not necessary, it's a Query without > conditions. Don't get you here, sorry. > 2.4 Meaning of 'Length' using different Integers? > Says nothing about the usable range! Uhoh, just tried the help, it's really not useful here :( It's the number of digits, so in some sense, it's about the usable range. > 2.5 Your user sees a thing that looks like a table, is a > one dimensional table, therefore provide all the usual > tools to manipulate the table: > Allow to move a field up/down, insert fields (empty or > out of a multiselection) between existing fields, allow > the change of types and constraints. > Warn and show the user what will happen (text cutted > or numbers out of range) during rearrangement of the > DB but do not say, he should restart his work from > scratch. Not sure what you mean with the last sentence. In general: Yes, the table design is unfortunately somewhat old-fashioned, the list of things to be improved would be rather long ... Parts of the problems result from our demand to support very different backends with the same UI, so from time to time, we have to stick to the least common denominator. Amonst others, this means that moving rows (i.e. moving columns in the table) is not possible, since too little DBs support this. > 2.6 'Copy Table' No feedback! The question is, is the copy > made or have we only a crash? If it were a crash, you would notice :) > Present the 'Copy table' immediately or say 'sorry'. > But the function itself is strange, it should be > implemented as 'Copy' like Delete, Rename, Edit see > below "Copy" is the very same as "Copy" in any other application. It copies the selection (in our case: a table object) into the clipboard. You wouldn't expect a feedback in Writer, if you Copy some text, would you? > 2.7 'Copy Table' GUI absurd: Copying a DB to itself is not > a desire, expected ist an selector for the source and > also for one the destination. I disagree, I often copy tables within the same DB. Also, see above: The semantics of "Copy" is simply "copy to clipboard". You're free to "Paste" in the destination database :) > 3. Queries: > 3.1 ... > 3.2 .... have to track this separately > 3.4 This Relation does not work: > .... > 3.5 Deleting multiple selected Queries: Question: Are you > ... Ehm. Please submit those in IZ. > 3.6 A profi uses for data input a query rather then a > form, because there is more overview and it is faster: > A lot of text can be found and copied to the new > record. But this is not possible, the implementation > does'nt allow to copy more then one field: > MsgBox 'Try to insert null into a non-nullable > column... > eeh? Could you say: 'Record uncomplete' and set the > cursor to the delinquent? > Correct behavior: Block only, if the curor is below > the current row or after 'Save the current record' There's an issue that the copy behaviour in the query/table data view is, ehm, sub-optimal. > 4. Forms > 4.1 Working on Forms, then selecting Tables: Icon 'Forms' > keeps highlighted, but the table names are shown. > Confusing. Sounds like a bug, but never saw anything like this myself :( > 4.2 A MemoField comes out as an ordinary textfield(infinite > long). Not usable: Expect a Box with sliders and > not a 65k string without <CR>, "comes out"? > 4.3 Using the Query 3.4 (reduced to 1 relation) to build a > Form: BOTH fields displays numbers, no one is replaced > with text. Don't get you here completely, please submit an issue and describe in detail what you're doing, what happens, and what you expect to happen. > 4.4 The toolbar below is to small, usable for developers, > not for practical use. Hmm. It's the usual toolbar size, isn't it? If you don't like it: - Set "Navigation" to "none" in the form properties - insert a "navigation bar" control into the form - set the properties "Icon size" property to "Large" > Provide an extra element to display 'Record xx of xxx' can be reached with the "navigation bar" control, too > and enable the keyboard buttons Up/Down, Page up/down, > Pos and End to navigate, use <CR> to create a new > record! Again a suggestion where probably half of the users would love it, and the others would hate it :). Feel free to submit an RFE. I am not sure about the <CR>, but the others might make sense. > 5. Reports (an early stage, not a tool for producing) Yes :(. Real reports are on the post-2.0 agenda. > 5.1 Redesign with Delete then Wizard to Create Report? Effectively, yes. There are other, manual, cumbersome means to redesign parts of the document, though. > 5.2 Select a fancy design (lj) and get a right > justified table? You remind me that I wanted to submit an issue for this strange behaviour long ago ... > 5.4 NEED as template a Calc NOT a Writer Document, provide > an selector! Don't get you here. > ReTest my Issues: > ... won't go over them in detail here, that's what IZ is for :), but good to see that some of them improved. Thanks & Ciao Frank -- - Frank Sch�nheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
