Re: Kupu: default cursor position and tables
Guido Wesdorp <[email protected]>
| Newsgroups | gmane.comp.web.zope.silva.devel |
|---|---|
| Message-ID | <[email protected]> |
Samuel Schluep wrote: > Hello Developers > > Please note some problems I encounterd, when editing with Kupu: > > DEFAULT CURSOR POSITION WHEN KUPU OPENS > > 1. Opening Kupu will position the cursor at the beginning of the > title. For me this is annoying, because I tend to start editing right > ahead - just into the title. It would be nice if Kupu would position > the cursor on the first line after the title. > > 2. To edit a new document with Kupu you have to add a new line: this > means (1) you have to position the cursor at the end of the title, (2) > press enter (which adds two rows), (3) delete one of the two rows. > From my point of view, these three actions are superfluous and make > the users life harder. > Good point, I'll try to fix it. > TABLES > > 1. Kupu adds a blank to every cell. When the user clicks the cell to > enter new data, the cursor is placed after the space and the user > tends to enter some text right there. The cell contents will start > with a space, which is annoying - especially if the line wraps on > multiple lines. The user has to delete all spaces manually. > Unfortunately if I don't place a non-breaking space in the table cells they aren't rendered: the HTML specs state that a table cell must have some content to be valid. This is especially annoying in edit mode, I'll try to find a way to at least select the nbsp when one goes into a cell so if (s)he starts typing the nbsp would be overwritten rightaway (or something similar). > 2. If 'subparagraph' is assigned to table cell (or to the text in a > table cell) the assignment can not be changed back to plain or another > type. > That's weird. I'll check it out. > 3. It would be nice if table cells could span across multiple columns, > to make headings for multipe columns. > /me coughs Actually we had partial support for colspan and rowspan, but besides the fact that it's *very* hard to code, Silva doesn't support them. Perhaps it will in the future, but I guess that would be a discussion on its own. > WINDOW SIZE > > 1. The Kupu editor space should adapt to the size of the browser > window (width does this already, height not). Nice to have. > This is pretty hard to achieve actually, I've spend quite some time to get that to work already, but so far to no avail. I'll try again later though. Cheers, Guido