Hi team, I've wrote a concept of how should look the compiler options in my point of view, and I've used instead a tree, a list of items (coresponding to tab names) and a search box. When you write keywords in search box some tabs will dissapear depends of which index keyword have inside them.
All properties dialogs will derive that form (so will be consistent against the options), still will let enogh options for developers to implement them as they wan. The container dialog should have the "power" to index all controls implied and searching will keep only pages that match the filter. The search option will greatly simplify looking for an less visible options. Anyway, that is work on progress, still don't know if I haven't break something. Hopefully in a week I can show a 99% work done. Indexing for now has bugs, but seems to me a viable option. P.S. For details I will offer an email to (more) interested persons, but I don't want to buggy everyone in that list about that. For sure if is accepted, will be for post 9.24 release feature. Ciprian -----Original Message----- From: Mattias Gaertner [mailto:[EMAIL PROTECTED] Sent: S 27.10.2007 17:05 To: [email protected] Subject: Re: [lazarus] Usability issues On Fri, 26 Oct 2007 14:42:35 +0300 "Ciprian Mustiata" <[EMAIL PROTECTED]> wrote: > - compiler options aren't a part of project options? Why? Probably > the options should be organized then in another format like some > tools use today: a logical tree with options and on the right the > options to change >Yes, but it would more complicated in code. >If you have question how to implement this just ask. > - view todo list: should not be in the view menu? Yes, I guess, all old reasons for the project menu are gone. > - Components item is the cleanest menu > > - Tools: the first dialog about custom tools is to heavy and in more > steps. Probably a list with tools in the left, and in the right the > plain dialog of add/edit dialog. To add one new item should be in one > step (having the option of adding or modify that command). Probably > the tools should be on top of Custom tools, because you want to have > minimalist step to get it. Feel free to improve it. > - Options: > - probably they should be merged in a single dialog with a tree on > the left, excluding Code tools defines editor, which from my point of > view should be put in the View or Tools menu, it does not belong to > the options place. But who knows!? The codetools defines are global settings (read: independent of projects and packages). It shows the project/package settings too, but you can not edit them. I got the feeling you prefer trees in general ;) Mattias _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
