Hi Jason, > I hadn't really intended to use the CCE I thought it was just a more > complex way of doing the same thing. I have found so more information on it > all at ftp://ftp-eng.cobalt.com/pub/developer/TechNotes/SSDK.pdf and I will > have a good read up tomorrow.
Yeah, I know that guide. It's not entirely worthless, but it's my firm believe that it was written by Sun Cobalt with the full intention in mind to discourage people from diving into CCE/Sausalito. Like they *had* to release some sort of documentation to make a big client happy, but didn't want anyone really going for it. So it starts with some basic stuff, like what the GUI is about and throws in some nice schematics, which rather look like a sales blurb. Then, after 30 pages of nonsense it goes into great detail explaining classes and their syntax for 15 pages or so, but that information is thrown at the reader in rapid fire succession without examples to really comprehend it or make use of it. CCE and Sausalito are briefly explained, too, but even where it goes into detail it eventually is misleading a bit, if not intentionally wrong. Hell, the SDK explains even how to build PKGs, but anyone doing it "their" way would be crazy, as it's really the most outlandish way to do it. So all in all and from a programmers point of view I rated the SDK as a waste of time and I don't think you'll find anyone who says: "I learned CCE/Sausalito thanks to that guide". > I might just finish of the raqbackup gui using a few handlers that directly > edit the script and then once that is complete try playing with the CCE. That's a good idea. There are ways imagineable to integrate into the GUI without using CCE to store information. If you just read from a config file and need to write back to it, then storing the stuff in CCE prior to or even after writing is a waste of time. I'd rather let the applicationHandler.php write a temporary file with all info in it an then just use a handler to move the tempfile to the propper places and change permissions and ownerships of it (and restart the services if need be). Like with all programming: There is more than one way to do it. > At the moment I see the future of the raqs as limited as more and more time > is being spent developing new distros/guis and less and less on the raq > platform. I'm gonna be sticking with raqs for several years even if its not > my current ones and I know there must be other people in the same > situation. And eventually there'll be only a few people supporting the blue > boxes and by then I want to know mine inside out so I can keep it going > just a bit longer before I have to make the inevitable change! Same here. With BlueQuartz around it is finally viable again to develop software for Sausalito, as it will run (with or without some modifications) on a couple of appliances. Like the BlueQuartz, RaQ550, Qube3, TLAS1HE, TLAS1WG, Argon, RaQdevil, etc. -- With best regards, Michael Stauber _______________________________________________ Cobaltfacts site list [email protected] http://list.cobaltfacts.com/mailman/listinfo.cgi/cobaltfacts
