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 18:30:38
|
On Sat, 2004-03-20 at 18:46, Mich=C3=A8le Garoche wrote: > Le 20 mars 2004, =C3=A0 17:43, Iago Rubio a =C3=A9crit : >=20 > >> The customize toolbar display a form when you can drag and drop icons > >> from the form to the toolbar. At the beginning you have default=20 > >> buttons > >> in the toolbar, then you can add/remove them (all available buttons=20 > >> are > >> in the form). I don't know if we can implement this in cssed, but it's > >> very handy. > > > > May be in the future we can make the toolbar configurable. Right now > > thre's not too much to configure on it ;) > I precise for the future: that is the user who decides which icon(s) he=20 > wants in the toolbar, he can remove all of them, just add one and two,=20 > stick with the default, add all, etc. So, from this (his) point of=20 > view, all is configurable. Ok. Will start to check this to be implemented then. > >> 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. > I've just updated from cvs, but this is not implemented, maybe cvs lags=20 > a bit, but zooms are implemented in view. I've just updated the project one hour ago, so almost sure is public cvs is not updated yet. > >> For zoom, etc: > >> Format > >> Change font (this one taken out from Document menu) or just Fonts > >> ----------------- > >> Normal > >> Zoom in > >> Zoom out > >> > >> As the edit menu is long enough, it is more appropriate to use a=20 > >> Format > >> menu. > > > > Not sure about that. > > > > 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=20 > > 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. > > > > In cssed it's not true, as you're just changing the view's format, not > > the text. > > > > More opinions ?? > Yes, you're right. It may be confusing, why not add it to the View=20 > menu, at the end. This way, the user cannot be confused. Ok. Will do it then. > > > >>> > >>> 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. > > > > Will be more carefully with this ;) > The bookmark menu does not exist right now, is not it? No. I'm thinking in it because the cssed bookmarks, are less than bookmarks. Are just session/document oriented markers. Will the user expect to have his bookmarks ready when he reopen the document ? If the name "bookmark" will make the user think those are permanent bookmarks, we must find other name. > > > >> Go > >> Next page > >> Previous page > >> ---------- > >> First page > >> Last page > >> > >> I'll guess you mean document here? > > > > > > Yes. > > > > In fact I mean "tab" of the document's notebook. > So why not: > Go > Next document > Previous document > ------ > First document > Last document >=20 > As from the user's point of view, they are documents (the tab of=20 > document's notebook is just a programer's thing). Ok. Will be this way then. > >>> What to add to the second toolbar ? > >>> > >>> Any idea ? > >> View line numbers, View lines wrapped, Enable autocompletion, Fold=20 > >> all, > >> 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,=20 > >> margin > >> 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 :) > What I mean here is take a few dialogs (the most used) and put them in=20 > toolbar. > For example: 5 icons for (border all dialog, font dialog, color dialog,=20 > margin all dialog, padding all dialog), 2 icons for wizards (selector=20 > and color), 4 icons for scan selector, doc info, clean, validate.=20 > Total: 11 icons. > At the time being, there are 16 icons in the toolbar, so that's less=20 > for the second toolbar. border all dialog font dialog color dialog margin all dialog padding all dialog -- selector wizards color wizards -- scan selector doc info clean output -- validate I will add also "validate and dump". The big problem here will be the art work. Will start to bild some icons, but don't expect beautifull ones :( Any other thing in/out the toolbars ? > >>>> 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=20 > >>>> comparison > >>>> side by side. Just an idea. [snip] > > > > Ok, good idea. It will depend on the ipc stuff, so I must try to put=20 > > the > > ipc queue to work or take it out, after implement this. > Don't forget that ipc queue does not work as is on Mac :-( Don't worry, I've got it in mind. Almost sure the ipc stuff will be aout the release. At least wainting to be more robust, and to know it it's useful. I've no positive reviews about that. > Oh I forgot to mention that the POTFILES.in is not accurate, the=20 > doc-scanner.c and .h files are missing in it. Thanks, will fix it. > And, please, don't forget=20 > to wait for the changes in PO files before you release. :-) Don't worry.=20 Before the release, ee'll get a freeze a one week waiting for the translations to be ready. I've got to change the manual and site also. In the manual, I'm going just to reflect the changes done in the interface, and describe the "doc scanner". Finally, is there a name for the "doc scanner" ? Proposals was: "Doc scanner" ( let it as is ) "Document summary" "Summary" "Digest" and I will add "Declarations browser" <- ugly "Styles browser" <- better, isn't it ? ;) ITHO shorter should be better. --=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 -------------------------------------------------- |
