Dialog boxes are not safe workflow. Browsers and computers still crash accidentally and deliberately. Somebody will bypass any interface-based process.
The 1.3 specifications include no locks. Globally distributed applications cannot have any locking. Two people edit on one server, another is editing on another server, and a third is editing a local repository while disconnected from the network. Lenya cannot mature while using that obsolete paradigm. While trying to adapt Kupu to this requirement, I developed a "virtual:" protocol. The VirtualModule, VirtualTransformer, and VirtualSourceFactory classes are in the 1.3 branch, but may disappear if no new need is found. While documents can be cached and edited in memory, the documents are saved to a virtual ID. This is similar to Flow Continuations with the additional functionality that these documents are also accessible to XMAP operations: <map:generate src="virtual:..." />. I could not decide when or how to clear the cache for forgotten documents: 1 hour? 24 hours? When a certain quantity of memory is used? I finally realized the algorithm was broken. After discarding Kupu, I researched other editors. Some had the same issues. Others may have licensing issues. The final choice was Xinha, a fork of HTMLArea. License is a BSD -- free for any use as well as license is included (which I need to add to the 1.3 licenses folder.) I have already customized for XHTML, need to fix a bug (adds extra fields to submission), need to add Lenya-1.3-specific link handling functions, and will improve the look later. HTH, solprovider On 10/6/07, Jürgen Ragaller <[EMAIL PROTECTED]> wrote: > Good evening, Jörn > Am Oct 6, 2007 um 21:33 schrieb Joern Nettingsmeier: > > Jürgen Ragaller wrote: > >> Hi > >> From our last weeks editor teaching event we received two > >> feedbacks regarding tinyMCE: > >> 1) If a user navigates away, the page remains locked and changes > >> made in tinymce are lost - this leads to frequent use of force > >> checkin... > >> 2) the german name of the Submit Button is «Einreichen» - > >> identical to the workflow name; should rather be save («Sichern») > >> For 1) I suggest to add the tinymce plugin «autosave» to > >> tiny_config.js (a popup is shown when the user navigates away - it > >> has the option to save or cancel (just as it is done in bitflux). > >> For 2) I'd suggest to use «Save» > >> WDYT? > > just a quick ACK - thanks for the feedback. > > i'll see if i can look into this tomorrow, but no promises. > > what kind of warning do you want? > > something like this?: > > "you are trying to navigate away from a page you are currently > > editing. your changes will be lost if you proceed. [return to > > editor] [abandon changes]" > The autosave plugin has a message pretty similar to the one you > wrote: "The changes you made will be lost if you navigate away from > this page." > But the problem with a simple "OK" is: no checkin is invoked (yet) so > the user was warned about the loss of work but the result is still a > locked page. > I think it would be better to either not allow a user to navigate > away from the page at all but rather force the user to use the Save > or Cancel buttons (display just a warning with a ok button); OR If it > is allowed to navigate away, a cancel event has to be invoked to > unlock the page. > The luxury version would be a window featuring 3 Options: 1) cancel > (nothing happens, user stays in editor ) 2) discard changes (unlock > document and go to the requested page) 3) save changes (save changes > and go to the requested page). > I think the autosave plugin shows how it could be done. > Thanks, Jörn > > regards, > > jörn > > jörn nettingsmeier --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
