search

xorcery / TableEditor

11 stars 8 forks source link

Use-case scenarios #3

Closed akeilox closed 9 years ago

akeilox commented 10 years ago

Hi Kevin

I am curious what would be the possible use-cases for this data-type. Beside the built-in table editor in tinymce, in which scenarios this property can be used? If the property provided on the same page/tab with tinymce, how can I explain to the user on how its different than the tinymce table editor. As you can tell I am trying to understand all the possible use-cases for it, not sure for instance if it can be used for creating email newsletter type table-based content. Or is it purely for data-table creation? cheers

kgiszewski commented 10 years ago

We and our clients have had a lot of frustration with editing the TinyMCE table editor.

Many of our clients need simple tabular data that behaves responsively. This datatype allows the editor to add custom styles to the table, columns and rows. Also there is a built-in property value converter and the output markup 100% customized.

akeilox commented 10 years ago

Thanks for the insight Kevin.

How do you go about integrating tinyMCE content and table editor together in one page in this case? As from my understanding the table editor property is managed outside the tinymce and user creates the table via the table-editor property outside the tinymce

kgiszewski commented 10 years ago

Ah! We use a 'block style' approach with Archetype (http://our.umbraco.org/projects/backoffice-extensions/archetype).

Essentially we wrap other property editors inside Archetype to allow the editor to rearrange the blocks.

Archetype allows for run-time editing of the position of data.

i.e. the editor can create this:

-RTE block -Table block

Then rearrange them and whatnot.

Archetype also allows for mapping a 'fieldset' to a partial view for easy template rendering.

akeilox commented 10 years ago

That sounds pretty cool! I need to learn more about how to create such feature. Curious, did you run into any performance issues (rte in archetype being slow) as I notice that using simple archetype with one textfield, one imagefield and one rte - the open/collapse and loading takes considerable time. Using 7.1.4