It used to be called Hive; now it’s Solar, the “Simple Object Library and Application Repository” for PHP5. This is only a development release. You can pick up the PEAR tarball here:
http://solarphp.com/Solar-0.0.2.tgz
No real documentation yet, but you can read the auto-generated API reference here:
Next set of tasks is to get the Solar_Cell_Bugs component working properly, and I can write up a quick app to do bug tracking. Also need a mailing list, and need to set up YaWiki installation for real documentation (although Solar will have a wiki component of its own, and at that point it can be self-hosted / autonomous / internally-dependent / eat its own dog food / whatever).
Revision control is going through Subversion now instead of CVS, provided by the kind folks at TextDrive, who are the web hosts for solarphp.com as well. For $12/month, it’s a sweet deal; my thanks to Ryan King for pointing them out.
hive was a cooler name, imo :)
Agreed, but it was taken. Oh well, such is life. At least nobody can say of it now that the Hive is full of bugs. ;-)
Speaking of a mailing list, I’m sure you noticed that you can do mailing lists with TextDrive.
Also, a minor note on the package…. in Solar_Base, the apiversion() function is not up-to-date. It would probably be easier to keep this in like by using a replacement in the package.xml, rather than trying to do it by hand.
Damn, this is good news. Solar! Bask in its glory. Am now translating a book on geology and the Earth in space, so when I saw the word “solar”, I had to check back with this site, and there was an early Solar release!
Yay. Its rays shine upon us.
How will Solar handle the locale thing? I saw there were methods and things for it, and an interesting â€en_US” file. Speculation is rife, hopes are high.
I know I can fix the Swedish locale, if you shoot some info my way.
Duh… what I meant is: I can supply translation and that sort of thing.
Hi, Ryan — You said, concerning the apiVersion() method, “It would probably be easier to keep this in like by using a replacement in the package.xml, rather than trying to do it by hand.” You are absolutely right. I need to figure out how to do the replacement stuff with Greg’s work on the new package.xml format. Any pointers?
Hi, Olle — the localization code works like this. The Solar_Base class takes a parameter called ‘locale’ that points to a directory. In that directory, you have the various PHP-array locale files (e.g, ‘en_US.php’ and ‘es.php’ and whatever else). Calling the locale($key) method for any class derived from Solar_Base loads up the proper locale file, then returns the string associated with the $key request. If there’s no locale file, it falls back to the Solar/Locale directory and the language keys therein.