Referring to
https://groups.google.com/forum/#!topic ... Q2hUxwPFR0 ,
Dr Leonard Walletzky of Brno University in Czech Republic when using iDempiere and now Ninja for his classes, found a bug which is not a bug but a feature. You need not use D#Date Y#IsSumtin, Q#Qty if the prefix names already as such. Otherwise Ninja will parse it into D#D#DateSumtin.
Since he tested it via binary which i hardly do as i test fully from Eclipse source, while replicating his condition, I discovered a real bug that MField creation in the DocEvent validating of New MColumn and Changed MColumn doesn't work if the plugin is not refreshed each time. This is inconvenient and failure prone. So the best way is to bring such MField code into Ninja core process and i did that.
Enroute i made Ninja able to refresh changes to the Module Creator without falling back on previous backup for correcting mistakes such as 1. Column>Field.Name and 2.Adding DocAction structure to a freshly created model.
1. The Column>Field.Name can be changed repeatedly without concern of corruption because it is merely a change of the Window/Tab/Field.Name displayed without disturbing any column properties.
2. Basic model generation can be further regenerated with DocAction structure by checking the Workflow Structure box and then further for Kanban display. However such action cannot be reversed i.e. to delete back the additional properties. But you can hide its display in window and act as a basic model.
Next on my wish list is to make Ninja able to facilitate WebServices access to newly created data model on the fly.