Hi,

I'm back from my hometown and want to give some more information about the next extended table version I am working on.

Maybe you saw the screenshot I posted last week? If not, see the related news below. On that screenshot you can see the first steps on the way to backend editing. The big goal is to edit the most things inside the backend form. If I reach this goal, he wizard is only needed for very special attributes that are not used very often. I do this, to make the extension much more user-friendly. (I know it isn't yet.)

For realize that, a lot of enhancements are needed. At this time, I'm worling on an implementation of fixed attributes. That means that an administrator can set fixed attributes. A small example. You want that the table has a border of 1 but you don't want that the editors can change this value. This is not possible now. If you want assign an attribute to the table it is editable in the wizard. This has a technical background and so I couldn't change that. In the next version, an administrator can define the attribute "border" as fixed with the value 1 and the table will allways have the borderwith 1. The editor never has the chance to change that.

If you say now, "Hey, what is with attributes like align, who are available in mor than one tag? I don't want to fix all attributes!". No problem, the attributes can be fixed globally or explicite for a single cell, row or whatever.

The fixed attributes feature is also the base for the next feature. Tabletemplates! What the hack does this mean? Imagine the following situation... You have a lot of products. For every product you have a datasheet. In most cases the datasheet should all look the same. With the current table version you have to define the header and the footer for every single table. With the new tabletemplates this approach will become obsolete. You define a base template which is used for all tables. The editors just have to insert the values. In best case, they only have to insert numbers, which can be done directly in the backendform.

Another use case is alternating format. If you have long tables, the administrator can realize an alternation of every second row within the template. For sure, it won't be limited to alternating evers second row! This is just an example. ;)

I hope this sounds interesting to you and you give me some feedback!?

Best regards and stay tuned,

Thomas