Download
What started out as just adding a class to the Matrix has now turned into a full, OOP overhaul of the plugin.
![[Image: matrix1.png]](http://s4.postimg.org/fnchs4bnd/matrix1.png)
![[Image: matrix2.png]](http://s4.postimg.org/fr6b8dh4p/matrix2.png)
![[Image: matrix3.png]](http://s4.postimg.org/wmlg7dmux/matrix3.png)
![[Image: matrix4.png]](http://s4.postimg.org/fko0rjim1/matrix4.png)
![[Image: matrix5.png]](http://s4.postimg.org/mt48ukkqh/matrix5.png)
![[Image: matrix6.png]](http://s4.postimg.org/dk22kgbuh/matrix6.png)
Above is an example of the visual changes that have been made, using a dummy table called 'dummy.entries' (for a blog). In accordance with your suggestion shawn, admin forms can be generated by specifying the field's class (e.g. 'Metadata Window (Left)'). You can drag and drop the fields into the order that you want (as before), but from that same screen you can edit all of the field details. Then there is a link called 'form' which previews how the outputted form will look in the admin panel.
Also added are a few new field properties - default (for defining default content for fields when records are created) and class (which does what I explained above). 'Description' text also gets put as a placeholder in the field. In addition, record content such as textareas, textlong, wysiwyg...is saved using CDATA tags (so they don't require additional escaping).
Still ironing out the kinks in it, so there isn't a commit on github.
Above is an example of the visual changes that have been made, using a dummy table called 'dummy.entries' (for a blog). In accordance with your suggestion shawn, admin forms can be generated by specifying the field's class (e.g. 'Metadata Window (Left)'). You can drag and drop the fields into the order that you want (as before), but from that same screen you can edit all of the field details. Then there is a link called 'form' which previews how the outputted form will look in the admin panel.
Also added are a few new field properties - default (for defining default content for fields when records are created) and class (which does what I explained above). 'Description' text also gets put as a placeholder in the field. In addition, record content such as textareas, textlong, wysiwyg...is saved using CDATA tags (so they don't require additional escaping).
Still ironing out the kinks in it, so there isn't a commit on github.
