A "Snippet palette" where devs can define a piece of markup, give it a label and hereby make this snippet easily available to users of the Visual Editor. Those users will see a list of snippet titles, typically titled like "Flash movie", "YouTube movie", "Image gallery", "Table for prices" (devs control this).
A snippet can be inserted into the Visual Editor content at the caret position via "Insert | Feature", this invoke the selection list.
Snippets can be xhtml blocks (like a prepared table, with class's, th's etc. already done) and function markup with some or all params pre-specified. In function situations, if any required params need to get a value, the function call editor dialog is popped.
Packages should also be able to easily introduce snippets when installed.
UPDATE: Rather than being flat xml documents snippet sources could be C1 Functions that return markup (XhtmlDocument etc.). When a user choose to insert a snippet - and the source C1 Function has parameters - we pop a "fill in the blanks" dialog where user can override values (like changing a heading text, selecting a specific image, choosing a variant). The function then execute and the resulting markup is inserted. This should enable end-users to realize the desired result in a more structured view (as opposed to pure visual editing) and should allow for more advanced snippets (example is a image parameter, where user select image and the result contains the final resize/crop image url). Idea via @napernik .
Comments: ** Comment from web user: jaouw85 **
A snippet can be inserted into the Visual Editor content at the caret position via "Insert | Feature", this invoke the selection list.
Snippets can be xhtml blocks (like a prepared table, with class's, th's etc. already done) and function markup with some or all params pre-specified. In function situations, if any required params need to get a value, the function call editor dialog is popped.
Packages should also be able to easily introduce snippets when installed.
UPDATE: Rather than being flat xml documents snippet sources could be C1 Functions that return markup (XhtmlDocument etc.). When a user choose to insert a snippet - and the source C1 Function has parameters - we pop a "fill in the blanks" dialog where user can override values (like changing a heading text, selecting a specific image, choosing a variant). The function then execute and the resulting markup is inserted. This should enable end-users to realize the desired result in a more structured view (as opposed to pure visual editing) and should allow for more advanced snippets (example is a image parameter, where user select image and the result contains the final resize/crop image url). Idea via @napernik .
Comments: ** Comment from web user: jaouw85 **
Main complain of our customers. Hope there will be a solution for this soon