Re: [cssed-devel] Edit menu and HIG
Brought to you by:
iagorubio
Menu
▾
▴
Re: [cssed-devel] Edit menu and HIG
|
From: <mic...@ea...> - 2004-03-19 08:00:14
|
Le 18 mars 2004, =E0 17:13, Iago Rubio a =E9crit : > On Wed, 2004-03-17 at 00:25, Mich=E8le Garoche wrote: > > So if you want some cheap surfing lessons this summer, just send me a > mail and take a travel to Spain ;) =A1No me digas! > >>>> Maybe a button too for >>>>> display/hide panels (bottom and lateral). And shortcuts in the = menu >>>>> for show/hide line numbers, wrap/unwrap lines, show/hide >>>>> autocompletion, fold/unfold. :-) >>> >>> We must elabotare what buttons will be taken out the toolbar and = what >>> we >>> will put into ;) >>> >>> Or, What about a secondary toolbar ? >> Yes, that was I was thinking about a second toolbar for specialized >> tasks: > > That's a good idea. > > First we must change the menus to see what can be taken out the =20 > toolbar. > > Reading the HIG I've found the following templates: > > View > Toolbar <- is this ok ? > ------------- > Zoom in > Zoom out > Normal Size I don't know for gnome, but Mac is as is: View Anything specific to the application --------------- Show/Hide Toolbar Customize Toolbar In fact the Show toolbar menu item turns into Hide toolbar menu item =20 when the toolbar is shown and vice-versa. The customize toolbar display a form when you can drag and drop icons =20= from the form to the toolbar. At the beginning you have default buttons =20= in the toolbar, then you can add/remove them (all available buttons are =20= in the form). I don't know if we can implement this in cssed, but it's =20= very handy. Apple defines the view menu as <http://developer.apple.com/documentation/UserExperience/Conceptual/=20 OSXHIGuidelines/index.html>: [quote] The View menu provides commands that affect what users see in a window. =20= In the Finder, for example, the View menu contains commands for =20 displaying windows as columns, icons, or lists. Commands for showing, =20= hiding, and customizing a toolbar belong in the View menu. Create a =20 View menu for these commands even if your application doesn=92t need to =20= have other commands in the View menu. Show/Hide Toolbar should appear =20= right above Customize Toolbar. Avoid using the View menu to display utility windows (such as tool =20 palettes); use the Window menu instead. [/quote] So, for example, anything in Panel menu belongs to View menu as it =20 affects what the user views and applies to the whole application, =20 contrary to what is in document menu which is specific to a document =20 (not the whole application). View Show footer panel Hide footer panel Show side panel Hide side panel -------------- Toolbar But better is: View Footer panel (with a case to check) Side panel (with a case to check) -------------- Toolbar (with a case to check) Customize toolbar (if implemented) For zoom, etc: Format Change font (this one taken out from Document menu) or just Fonts ----------------- Normal Zoom in Zoom out Again, definition from Apple: [quote] If your application provides functions for formatting text, you can =20 include a Format menu as a top-level menu or as a submenu of the Edit =20= menu. It may be appropriate to group some items that are in the Format =20= menu into submenus, such as Font, Text, or Style. [/quote] As the edit menu is long enough, it is more appropriate to use a Format =20= menu. > > Bookmarks > Add Bookmark > Delete Bookmark > --------------- > Next bookmark > Previous Bookmark > > Go <- Is this ok ?? > Previous page > Next Page > -------------- > First Page > Last Page We should be consistent between menus (Next before Previous), so: Go Next page Previous page ---------- First page Last page I'll guess you mean document here? > > //////////////////////// > > Will be taken out the toolbar: > > Zoom in (Bigger font size) > Zoom out (Smaller font size) > Normal Size (Default font size) > =09 > Any other ?? None that I can think of. > > Ah! ... and, How does it fit with the MacOsX HIG (if any) ? Answers above. > > What to add to the second toolbar ? > > Any idea ? View line numbers, View lines wrapped, Enable autocompletion, Fold all, =20= Unfold all The above ones could go into first toolbar. Those ones into second toolbar: some main dialogs: border all dialog, font dialog, color dialog, margin =20= all dialog, padding all dialog Then: selector wizard, color wizard Then: scan selector, doc info, clean, validate > >> For the next one, it would be great if we can open a second window >> (i.e. a second instance of cssed), as in bluefish to allow comparison >> side by side. Just an idea. > > A spliter window ? > To divide a document window in two views of the same document ? No, from my experience, it's difficult for the user to deal with. But a =20= second instance of cssed where you can open another of even the same =20 document. Say you want to use an already existing style sheet to build =20= another one. That's the behaviour you obtain in bluefish when clicking =20= the new window item in file menu. Then, you can easily copy, drag and drop and so on. And just to make the document menu more pleasant to view: Document View line numbers View line endings View white spaces View lines wrapped --------------- Enable autocompletion Enable folding -------------- Set EOL mode Folding Hightlighting or even better: Document Line numbers (with a case to check) Line endings (idem) White spaces (idem) Wrap lines (idem) --------------- Autocompletion Folding Fold all Unfold all -------------- Set EOL mode Hightlighting And by the way, we need a close document in File menu: File New Open --------- Close Close all (eventually) Save Save as ___________ Quit Wouah, I would not have thought, I wrote so much :-) Mich=E8le <http://micmacfr.homeunix.org> |
