This looks like a very useful package. Unfortunately, the documentation seems to be sparse, and this really hinders the package's adoption by the open source community.
For instance, there is another request for guidelines on how to build a module. The 'final answer' is that "There is no developer guide for the Community Edition at this time." And the topic is dropped.
Another example is AJAX Client Development. The client object tree is extensive (and again, largely undocumented). But nowhere is there any guidance on how to make a change. If, by chance, one should happen to find the object that you want to change, merely changing the object accomplishes nothing. Somehow you have to use the scripts in the '/build' directory. Again, this is completely undocumented - what scripts to call, what variables they'll accept or require, if any, etc.
Right now, I have a need for a Asset Management System, but Calem won't fit the need, as I need to incorporate the ability to track the data of and report on multiple customers, provide security between the customers and need different custom forms to limit the data presented in a view to specific roles. The last item basically requires that I have multiple views of the same form, which as far as I can tell, can't be done. Without the ability to develop on a new branch, Calem is a non-starter.
And without documentation, any development will take at least 3 times as long as it should.
Any help you can provide on these topics would be greatly appreciated.
Thank you,
Rob
