Hai people,
Love this CMS. Better than the others I've tried. You know what I would find really cool? If the {edit} function would be something like http://tool-man.org/examples/edit-in-place.html , or is this idea allready mentioned somewhere here?
Bye,
Gier
Edit in place
-
gier
Re: Edit in place
Well, I just mean that it would be cool if there was something like http://24ways.org/advent/edit-in-place-with-ajax implemented in the system.
If the editor wants to edit a page, he logs in, goes to view site, goes to the prefered page and can edit it when he just double clicks on the text he wants to change.
I thought that the {content} tag was the closest example of what is now in the system to make it easy for a editor to change text.
This would make the system perfect for me.
Greets
If the editor wants to edit a page, he logs in, goes to view site, goes to the prefered page and can edit it when he just double clicks on the text he wants to change.
I thought that the {content} tag was the closest example of what is now in the system to make it easy for a editor to change text.
This would make the system perfect for me.
Greets
-
jelle
Re: Edit in place
As usual, this does appear not to work in my konqueror browser, so no support from me 
I can be wrong, but i think that changing the behaviour of the webpage to anything other then a webpage as the user knows it is not the way to go.
Double clicking a page is not expected behaviour (and a ugly windows trick to increase carpal tunnel syndrome). If there are no clues you can edit it, The user will blindly click on everything, just to see if it is editable. If you decide to have a visual clue after all (like a button 'edit this') then there is no good reason why that button should not lead to editable version of the page.
However It would be nice if there was a button/link at the bottom of every page or content block that returned a page with an editor with the content text in place of the original block (so no metadata and other whistles and bells) If that button would not appear for unknown users might be a nice extra feature, but is not strictly neccesary.
I guess this would be doable, the editable page would just need to use the same template as the content was in and replace the content with an editor or textarea.
should this be put past the 1.0 release or is it that easy to implement it may come before that time?
I can be wrong, but i think that changing the behaviour of the webpage to anything other then a webpage as the user knows it is not the way to go.
Double clicking a page is not expected behaviour (and a ugly windows trick to increase carpal tunnel syndrome). If there are no clues you can edit it, The user will blindly click on everything, just to see if it is editable. If you decide to have a visual clue after all (like a button 'edit this') then there is no good reason why that button should not lead to editable version of the page.
However It would be nice if there was a button/link at the bottom of every page or content block that returned a page with an editor with the content text in place of the original block (so no metadata and other whistles and bells) If that button would not appear for unknown users might be a nice extra feature, but is not strictly neccesary.
I guess this would be doable, the editable page would just need to use the same template as the content was in and replace the content with an editor or textarea.
should this be put past the 1.0 release or is it that easy to implement it may come before that time?
