I only made one library for Rev up to now. The UI to use the library is not really well made. As I am now thinking of making a second one, I am also thinking what went wrong with the UI of “docsLib by BvG”, and what approach would be best this time.
In rev, there are quite a few ways to store data, and to access them:
- files
- custom properties
- parameters
- fields
In “docsLib by BvG”, I used lots of custom properties. Most of those where also mirrored with parameters one could send to the handlers.
Similarly there are different ways to execute code, or trigger it:
- functions
- commands
- setting a custom property
- send (as opposed to code being in use/frontscript/backscript)
There where few commands, which mostly created custom properties as a result of running.
Last time, there was a problem with the way properties where ignored when parameters where used. Mostly this was because the parameters would replace the properties this time, but next time there was no parameter specified, the property would be used. This time, I’ll try to use custom properties as settings, and additionally parameters. So this time around, parameters will automatically set the properties. In addition, there’ll be fields, which will be automatically set too.
Also, last time the properties weren’t well understood, so I’ll add handlers just for managing properties this time around. Of course there needs to be a more thorough documentation this time around.
I hope that people will understand this approach better, so that my future libraries get more often used then my current offer.