Re: [cssed-devel] Edit menu and HIG
Brought to you by:
iagorubio
Menu
▾
▴
Re: [cssed-devel] Edit menu and HIG
|
From: Iago R. <iag...@hi...> - 2004-03-20 16:44:35
|
On Fri, 2004-03-19 at 09:00, Mich=C3=A8le Garoche wrote: > Le 18 mars 2004, =C3=A0 17:13, Iago Rubio a =C3=A9crit : [snip] > > 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: >=20 > View > Anything specific to the application > --------------- > Show/Hide Toolbar > Customize Toolbar >=20 > In fact the Show toolbar menu item turns into Hide toolbar menu item =20 > when the toolbar is shown and vice-versa. Really close to the HIG. > 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. May be in the future we can make the toolbar configurable. Right now thre's not too much to configure on it ;) > Apple defines the view menu as > <http://developer.apple.com/documentation/UserExperience/Conceptual/ > OSXHIGuidelines/index.html>: >=20 [sniped quoted text] >=20 > 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). >=20 > View > Show footer panel > Hide footer panel > Show side panel > Hide side panel Yes it should be ok. > -------------- > Toolbar It's right now implemented in CVS. > But better is: > View > Footer panel (with a case to check) > Side panel (with a case to check) Hmmm ... yes should be. I'll wait a little to implement this, but It will be done in the future. Right now I don't want to bother with the panels state each time the menu is used, but it will be done in the next release. > -------------- > 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 >=20 > 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] >=20 > As the edit menu is long enough, it is more appropriate to use a Format =20 > menu. Not sure about that.=20 cssed doesn't format tex, itt just format the text's view. I mean that the "Format" menu can drive the user to think that the text itself will be saved with format ( as a RTF document, as example ) and it's not true in cssed. It always save plain text, with no format information. I suposse the "Format" menu deals with text formatting to be stored in a document, and the user should expect if he/she changes the font format and saves the documen,t the next time he/she will open it, it saves the format selected.=20 In cssed it's not true, as you're just changing the view's format, not the text. More opinions ?? > > > > 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: Yes, it's ok.=20 Will be more carefully with this ;) > Go > Next page > Previous page > ---------- > First page > Last page >=20 > I'll guess you mean document here? Yes. In fact I mean "tab" of the document's notebook. > > //////////////////////// > > > > 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. Ok, will take those out then. > > > > Ah! ... and, How does it fit with the MacOsX HIG (if any) ? > Answers above. Really well explained, thank you :) > > 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. >=20 > 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 aaaaargs ! All of them ? I'm sure we will need more than one extra toolbar ;) In Gtk the toolbar buttons are 24x24 pixels. So for those entries we need a toolbar .... really long :) > > > >> 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. Ok, good idea. It will depend on the ipc stuff, so I must try to put the ipc queue to work or take it out, after implement this. > And just to make the document menu more pleasant to view: >=20 > Document > View line numbers > View line endings > View white spaces > View lines wrapped > --------------- > Enable autocompletion > Enable folding > -------------- > Set EOL mode > Folding > Hightlighting >=20 > or even better: >=20 > 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 It's closer to this right now in CVS. > And by the way, we need a close document in File menu: >=20 > File > New > Open > --------- > Close > Close all (eventually) > Save > Save as > ___________ > Quit In the HIG the close menu is just above the quit menu entry. --------- Close Quit > Wouah, I would not have thought, I wrote so much :-) Yes, thanks. So much writting =3D so much help ;) Best regards --=20 Iago Rubio http://www.iagorubio.com =20 GPGkey pgp.rediris.es id 0x909BD4DD fingerprint =3D D18A B950 5F03 BB9A DD89 AA75 FEDF 1978 909B D4DD ********** iago.rubio(AT)hispalinux.es ********** =20 -------------------------------------------------- |
