+++ Michael DeHaan [30/07/08 11:41 -0400]:
So, one issue right now is that system.rb is a bit confusing as it confuses "cobbler systems" with the idea of a "cobbler server", so I think this should probably be "server.rb".
To make it more Ruby-like, I'm going to refactor the code. Rather than the current model I sent out where I've just wrapped the XML-RPC APIs in Ruby, I'm going to have classes represent the various entities from Cobbler (Distro, Profile, System, etc.) and a common base that allows you to retrieve those individual elements from Cobbler. So, for that, the first pass would be to have: 1. a model containing all of this, named Cobbler, 2. a base class, Cobbler::Base, which will contain code for interacting generally with Cobbler, 3. each individual class, like Cobbler::Profile, will be able to retrieve itself, or sets of same, from Cobbler, 4. the classes will be "introspecty" enough to present their values as if they were attributes of the class itself. -- Darryl L. Pierce, Sr. Software Engineer Red Hat, Inc. - http://www.redhat.com/ oVirt - Virtual Machine Management - http://www.ovirt.org/ "What do you care what other people think, Mr. Feynman?"
pgpVr3xOI8RtP.pgp
Description: PGP signature
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
