silva-2.2: comments
Marc Petitmermet <[email protected]> Sun, 31 May 2009 22:55:31 +0200
| Newsgroups | gmane.comp.web.zope.silva.devel |
|---|---|
| Message-ID | <[email protected]> |
uploading image: why do i have to browse again for the image when i forgot to enter the required title? smi image: the image assets are represented with the icon "silvafile.png" instead of the icon "silvaimage.gif" (why the mixed image formats?). smi consistency: why didn't you replace the big buttons in the kupu image tool for the image reference with the same/similar buttons like in the link tool? it's very nicely done there with the buttons on the left and right of the input field. the same applies for "link to:" field. edit link reference...: i was a little surprised about what happened when clicking on this new icon in the kupu link tool. sometimes we have long urls/paths and it is not that easy to fix those because of the need of horizontal scrolling. so i expected that this button opens up a larger link field that would help me in this situation. but instead it opened up the silva document where it linked to. therefore, could you please rename the tool tip from "edit link reference..." to "edit linked reference...". small detail but the two character change makes the description correct. edit link(ed) reference...: is it possible to have the button "edit link(ed) reference..." disabled from the beginning for not valid relative silva references? currently, it gets disabled after the user has clicked on it, that's too late and useless because the next time the cursor is on the same link the button is enabled again. warning message: what is the definition of "valid relative silva references"? what about "valid absolute silva references", won't they be edited? don't you mean local and external references here? lookup users.../groups admin...: i think since silva-2.1 (i don't know about 2.0) the "lookup users..."/"groups admin..." buttons have been moved away from their boxes on the right side to the top left side of the smi. i miss them at their old locations, it was much more convenient. export to open document (odt): nice that this feature is now built in. i had quite good experience with https://viewvc.infrae.com/svn/silva2odt/ by dave kuhlmann. this built in export has still a few issues like missing images, list styling, export of complete branches. user settings: is it possible to have the languages somehow sorted? regards, marc