plans

One of the key aspects of solving the configuration management conundrum is identifying how to uniquely identify data between servers. To this end I propose implementing UUIDs in core for the identification of content, and to provide an API through which UUIDs can be generated and added use by contrib modules. While we are still talking through many big picture architectural issues, I think that it is possible to get moving on this and several other tasks to get the real work started. So here is my proposed game plan for this, created after some discussion with Dave Hall (skwashd) who has put a lot of work recently into porting the UUID module to D7.

Thanks to everyone who tried and tested the formbuilder module. While using it you would have noticed that the functionality of formbuilder is still limited to very simple forms and this is where the next plans come in.

I am here outlining plans that I could think of, If you find something which I stupidly missed out, please add it as a comment.

1. Add support for trees, parents etc.
2. Change the way in which the ordering of form widgets is done.(Right now it is done using weights but nedjo suggested that initial ordering should be better done through the order of elements in the $form array. So this has to be changed.)