This is my first commit, so feel free to comment in any way.
For my purposes, it was an issue that it was hard to manage (i.e. create, add etc..) properties on individual nodes. Here is a very simple interim solution to this problem.
-Renamed graffeine-conf.js to graffeine-client-conf.js to minimize
confusion
-In graffeine-client-conf.js, the entry "Graffeine.conf.editFields" now
lists fields that will always be displayed when editing a node. This
makes it much easier to, say, maintain an actor or film database with
consistency.
TODO: In the future, the editFields list should probably be dependent on the object type that the editor identifies.
Hi!
This is my first commit, so feel free to comment in any way.
For my purposes, it was an issue that it was hard to manage (i.e. create, add etc..) properties on individual nodes. Here is a very simple interim solution to this problem.
-Renamed graffeine-conf.js to graffeine-client-conf.js to minimize confusion -In graffeine-client-conf.js, the entry "Graffeine.conf.editFields" now lists fields that will always be displayed when editing a node. This makes it much easier to, say, maintain an actor or film database with consistency.
TODO: In the future, the editFields list should probably be dependent on the object type that the editor identifies.