Michael DeHaan wrote:
Michael DeHaan wrote:
I'm currently fixing up the get fields infrastructure, to simply things and keep from having hundreds of lines of sprawl in each file if i can. This was honestly stuff I wanted to look at for 2.0, but I think we need to contain the complexity before it gets to be too much.
I'll also try to get these features working for images and repos, and also the CLI.
I will probably be removing the concept of "order" among other things.
Anyway, it is probably not a good time to be working on the above, for fear merging will become "interesting".
Fair warning.
--Michael _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
This was meant for -devel too.
Everybody likes extra email though, so it's all good :)
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
I've decided to reduce boilerplate a bit more since I can't see a point in dual maintaining field definitions.
So most likely this affects the clear functions and to/from datastruct.
Webapp may be briefly broken by this but it's worth it in the long haul.
Fortunately many of the fields in get_fields() won't be needed if we just do a lot of those things in CSS, so I don't see it being terribly complicated.
--Michael