ideas on new quickedit

so i really like concrete5.com quickedit feature. it would be tough to do the exact thing in modx, but i think we could get close.

Here’s my idea:
- plugin onWebPagePreRender (i think)
: check for SESSION val edit mode
: if edit mode is true
: if user has ability to edit docs, chunks, then run regex for chunks, [*content-items*]
: wrap each item with some syntax <!-- editable docid: 45 placeholder: content --> html <!-- end editable --> (something like this)
: have javascript do it’s thing similar to other edit in places.

Do you think this would work?
it would:
1. hide all this jazz from everyone but people who can edit
2. shouldnt affect frontend loading for regular visitors since the regex only runs if you’re a manager

I think that you have described how QuickEdit works already. The thing to do would be to rewrite the logic part of QE to use edit-in-place rather than in a popup window when possible.

Quote from: dev_cw at Jan 31, 2009, 06:59 AM

I think that you have described how QuickEdit works already. The thing to do would be to rewrite the logic part of QE to use edit-in-place rather than in a popup window when possible.

i agree ! inline editing for input text field (like this : http://dev.justinmaier.com/inlineEdit/) would be a wonderful alternative to quick edit !

The catch with inline editing is that it will not load an RTE. For me that is great, but for clients it may be no good. Is there a way to load an RTE in place? Does any CMS do that?

I really like the way Concrete5 does it!

It’s great how they have done that bar on top of the site when you are logged in, it doesn’t look as geeky as Quickedit is in modx.

i think this’ll be done and hope to collaborate with folks here. Ill just call it QE 2 for discussion purposes.

i think the differences between QE and QE 2 are:
- you have an edit mode and a normal mode
edit mode shows edit in place
normal mode just shows the top bar with a button to go into edit mode

of course c5 has versionable pages and we dont have that now. something to consider.

The items I would like to see editable are:
- TVs
- Chunks
- Snippets (in 2.5)

For snippets, it would be great to parse out the &parameters to create input fields!! (in a 2.5)

What other considerations am I missing? or what do ya’ll think.

I am awful at regex. So id love some help from a regex guy (anyone is better than me).

Why regex? For Revo you have property sets that can be accessed for snippets, plugins, etc.

I’d question the logic in giving end-users access to snippets, that seems more like a power user or developer task. Accessing the content + TVs (though maybe not all of them) + Chunks certainly makes sense though.

a lot of times i have snippets in parts of the content (tho i try to keep them out).

if we could parse the parameters and have an input for each, that’d be cool. but its not a deal breaker and down the road if at all. let’s throw that out for now.

Why regex? won’t we need to find all tvs, chunks in the pre-output? how else are we going to get the items and make them inline-editable?

Quote from: ChuckTrukk at Feb 01, 2009, 10:42 AM

a lot of times i have snippets in parts of the content (tho i try to keep them out).

The whole point of the parser is to allow parsing of any Elements represented by a tag; this is ultimately an issue of the security model, and that should be addressed separately (i.e. allowing certain users rights to edit certain kinds of elements or specific elements). You should not have to keep any kind of element tag outside of the editable content.

Quote from: ChuckTrukk at Feb 01, 2009, 10:42 AM

if we could parse the parameters and have an input for each, that’d be cool. but its not a deal breaker and down the road if at all. let’s throw that out for now.

Why regex? won’t we need to find all tvs, chunks in the pre-output? how else are we going to get the items and make them inline-editable?

modParser provides all the methods you need to do so, including collecting element tags and parsing property strings, all without a single regex expression.

inline editing can be interesting only for basic field.. if you have a drop down tv or something else (like rte) you cannot use this method to edit or you can but it will be tricky to code... Maybe im wrong but actually if a modal window was used (like c5) instead of the popup in QE.. that’s would be a good deal for a v2. Adding an Edit chunks features would be great too.