Horde

Dear folks, I am very pleased to announce: The Sesha Inventory application is ready for Horde 5 and it is in good shape. Sesha is a simple inventory keeping application which originally developed by Bo Daley and Andrew Coleman on Horde 3. The product ... [More] was never officially released but it went into production at several sites. Sesha release cycle can now start together with the Horde 5 Alpha release cycle. Sesha inventory can be configured to hold any number of stock categories with any number and type of attributes. Like the original version, Sesha for Horde 5 can provide its stock categories as ticket queues for the horde ticketing application whups. There are a lot of plans and ideas for upcoming versions but for this time the focus was on finishing a releasable product.There are no surprises for existing users of Horde 3 based sesha. Most work happened invisibly under the hood: The Horde_Template library was exchanged by new Horde_View code A migration script for database was added Users can keep their original Horde 3 Sesha tables and data. The sql backend driver was completely reworked into a driver based on the Horde_Rdo ORM library The new Driver Api provides enhanced search capabilities but the current frontend doesn’t make use of it. I do not plan to add any features to the classic view but start working on an Ajax view once the Horde 5 Redesign is completed. This may ship with Sesha 1.1 later on. Object oriented code has replaced complicated hashes in many places The Horde Rdo library is the new work horse inside Sesha. Rdo means Rampage Data Objects and is a lightweight ORM layer by Horde founder Chuck Hagenbuch. It maps database tables to PHP Objects. This is similar to the ActiveRecord pattern. Each database row can be turned into one Rdo item. For Sesha and another – non-public – software project, some enhancements went into the Rdo library for Horde 5: Rdo now provides a caching factory or root object which speeds up creation of mapper objects Methods for add, removing or checking many-to-many relations have been added A number of edge case bugs have been fixed I think the Horde 5 release cycle will start with alpha1 releases sometime in May. I know we’re a little late but it’s worth the wait. That said, I welcome any early testing or updates of the language files. Provided everything works as expected, Sesha will be shipped with Horde 5 for OpenSUSE 12.2 [Less]

Dear folks, I am very pleased to announce: The Sesha Inventory application is ready for Horde 5 and it is in good shape. Sesha is a simple inventory keeping application which originally developed by Bo Daley and Andrew Coleman on Horde 3. The product ... [More] was never officially released but it went into production at several sites. Sesha release cycle can now start together with the Horde 5 Alpha release cycle. Sesha inventory can be configured to hold any number of stock categories with any number and type of attributes. Like the original version, Sesha for Horde 5 can provide its stock categories as ticket queues for the horde ticketing application whups. There are a lot of plans and ideas for upcoming versions but for this time the focus was on finishing a releasable product.There are no surprises for existing users of Horde 3 based sesha. Most work happened invisibly under the hood: The Horde_Template library was exchanged by new Horde_View code A migration script for database was added Users can keep their original Horde 3 Sesha tables and data. The sql backend driver was completely reworked into a driver based on the Horde_Rdo ORM library The new Driver Api provides enhanced search capabilities but the current frontend doesn’t make use of it. I do not plan to add any features to the classic view but start working on an Ajax view once the Horde 5 Redesign is completed. This may ship with Sesha 1.1 later on. Object oriented code has replaced complicated hashes in many places The Horde Rdo library is the new work horse inside Sesha. Rdo means Rampage Data Objects and is a lightweight ORM layer by Horde founder Chuck Hagenbuch. It maps database tables to PHP Objects. This is similar to the ActiveRecord pattern. Each database row can be turned into one Rdo item. For Sesha and another – non-public – software project, some enhancements went into the Rdo library for Horde 5: Rdo now provides a caching factory or root object which speeds up creation of mapper objects Methods for add, removing or checking many-to-many relations have been added A number of edge case bugs have been fixed I think the Horde 5 release cycle will start with alpha1 releases sometime in May. I know we’re a little late but it’s worth the wait. That said, I welcome any early testing or updates of the language files. Provided everything works as expected, Sesha will be shipped with Horde 5 for OpenSUSE 12.2 [Less]

Dear folks, I am very pleased to announce: The Sesha Inventory application is ready for Horde 5 and it is in good shape. Sesha is a simple inventory keeping application which originally developed by Bo Daley and Andrew Coleman on Horde 3. The product ... [More] was never officially released but it went into production at several sites. Sesha release cycle can now start together with the Horde 5 Alpha release cycle. Sesha inventory can be configured to hold any number of stock categories with any number and type of attributes. Like the original version, Sesha for Horde 5 can provide its stock categories as ticket queues for the horde ticketing application whups. There are a lot of plans and ideas for upcoming versions but for this time the focus was on finishing a releasable product.There are no surprises for existing users of Horde 3 based sesha. Most work happened invisibly under the hood: The Horde_Template library was exchanged by new Horde_View code A migration script for database was added Users can keep their original Horde 3 Sesha tables and data. The sql backend driver was completely reworked into a driver based on the Horde_Rdo ORM library The new Driver Api provides enhanced search capabilities but the current frontend doesn’t make use of it. I do not plan to add any features to the classic view but start working on an Ajax view once the Horde 5 Redesign is completed. This may ship with Sesha 1.1 later on. Object oriented code has replaced complicated hashes in many places The Horde Rdo library is the new work horse inside Sesha. Rdo means Rampage Data Objects and is a lightweight ORM layer by Horde founder Chuck Hagenbuch. It maps database tables to PHP Objects. This is similar to the ActiveRecord pattern. Each database row can be turned into one Rdo item. For Sesha and another – non-public – software project, some enhancements went into the Rdo library for Horde 5: Rdo now provides a caching factory or root object which speeds up creation of mapper objects Methods for add, removing or checking many-to-many relations have been added A number of edge case bugs have been fixed I think the Horde 5 release cycle will start with alpha1 releases sometime in May. I know we’re a little late but it’s worth the wait. That said, I welcome any early testing or updates of the language files. Provided everything works as expected, Sesha will be shipped with Horde 5 for OpenSUSE 12.2 [Less]

Here at CeBIT we support our friendly neighbor project with a constant and vital support of gummy bears. As anyone knows these sweet animals can make the difference between one line of brilliant code and a dreadful spaghetti mess. Thus it is ... [More] probably hard to deny that this fruitful collaboration turned Horde into one of the biggest KDE sponsors. That being said: KDE, I'm already here, breakfast is ready ;) Beside having fun in the open source area the second day was already packed with people here at CeBIT. We had plenty of Horde users which provided kind feedback. Some of them we could surprise with features they didn't know about. Others were happy to hear that "GPL" really means that they can use the software and modify it without being harassed with a lawsuit afterwards. We had Horde newbies as well as free software newbies. Explaining how free software can result in a revenue was the easy part. Explaining why we have no strong interest in a product for obfuscating our code so that there is a decent protection against people trying to find security holes was ... sigh ... harder. The most fascinating thing was a company that installed Horde and wants to run it from -25°C to 65°C - like putting Horde to the extreme. There were other extremes involved and I omit the details but it is always fascinating what people do with free software. [Less]

Here at CeBIT we support our friendly neighbor project with a constant and vital support of gummy bears. As anyone knows these sweet animals can make the difference between one line of brilliant code and a dreadful spaghetti mess. Thus it is ... [More] probably hard to deny that this fruitful collaboration turned Horde into one of the biggest KDE sponsors. That being said: KDE, I'm already here, breakfast is ready ;) Beside having fun in the open source area the second day was already packed with people here at CeBIT. We had plenty of Horde users which provided kind feedback. Some of them we could surprise with features they didn't know about. Others were happy to hear that "GPL" really means that they can use the software and modify it without being harassed with a lawsuit afterwards. We had Horde newbies as well as free software newbies. Explaining how free software can result in a revenue was the easy part. Explaining why we have no strong interest in a product for obfuscating our code so that there is a decent protection against people trying to find security holes was ... sigh ... harder. The most fascinating thing was a company that installed Horde and wants to run it from -25°C to 65°C - like putting Horde to the extreme. There were other extremes involved and I omit the details but it is always fascinating what people do with free software. [Less]

Wonderful start at CeBIT yesterday. Meeting people with an interest in Horde face-to-face is a refreshing alternative to the work behind the screen at home or at work. The positive feedback helps tremendously in building up energy. The most ... [More] important part yesterday was talking to well known contacts, chatting about the progress of some projects which will hopefully result in a few interesting feature additions to Horde during this year. I also visited ownCloud at their Univention booth to chat a bit about integrating the tool with a webmailer. And last but not least it is always fun seeing Jan in person. Nothing against having a "distributed" type of project with people scattered in Germany and US. But it would be so much fun having all of you guys here. Can't really wait for the next hackathon ;) [Less]

Wonderful start at CeBIT yesterday. Meeting people with an interest in Horde face-to-face is a refreshing alternative to the work behind the screen at home or at work. The positive feedback helps tremendously in building up energy. The most ... [More] important part yesterday was talking to well known contacts, chatting about the progress of some projects which will hopefully result in a few interesting feature additions to Horde during this year. I also visited ownCloud at their Univention booth to chat a bit about integrating the tool with a webmailer. And last but not least it is always fun seeing Jan in person. Nothing against having a "distributed" type of project with people scattered in Germany and US. But it would be so much fun having all of you guys here. Can't really wait for the next hackathon ;) [Less]

When installing horde to a custom pear location, you need to run the pear of your custom location, not the system pear with the custom location’s config. So the steps would be: 1  mkdir /srv/horde 2  pear config-create /srv/horde/ ... [More] /srv/horde/pear.conf 3  pear -c /srv/horde/pear.conf install PEAR as the install docs say but then: 4 /srv/horde/pear/pear -c /srv/horde/pear.conf channel-discover pear.horde.org 5 /srv/horde/pear/pear -c /srv/horde/pear.conf run-scripts horde/Horde_Role 6 /srv/horde/pear/pear -c /srv/horde/pear.conf install --alldeps horde/groupware Otherwise running the Horde_Role script will fail saying config-set (horde_dir, /srv/horde/, user) failed, channel pear.php.net This was experienced on SLES11SP1, SLES11SP2 and openSUSE Factory. I did not test this for any debian based products yet. [Less]

When installing horde to a custom pear location, you need to run the pear of your custom location, not the system pear with the custom location’s config. So the steps would be: 1  mkdir /srv/horde 2  pear config-create /srv/horde/ ... [More] /srv/horde/pear.conf 3  pear -c /srv/horde/pear.conf install PEAR as the install docs say but then: 4 /srv/horde/pear/pear -c /srv/horde/pear.conf channel-discover pear.horde.org 5 /srv/horde/pear/pear -c /srv/horde/pear.conf run-scripts horde/Horde_Role 6 /srv/horde/pear/pear -c /srv/horde/pear.conf install --alldeps horde/groupware Otherwise running the Horde_Role script will fail saying config-set (horde_dir, /srv/horde/, user) failed, channel pear.php.net This was experienced on SLES11SP1, SLES11SP2 and openSUSE Factory. I did not test this for any debian based products yet. [Less]

When installing horde to a custom pear location, you need to run the pear of your custom location, not the system pear with the custom location’s config. So the steps would be: 1  mkdir /srv/horde 2  pear config-create /srv/horde/ ... [More] /srv/horde/pear.conf 3  pear -c /srv/horde/pear.conf install PEAR as the install docs say but then: 4 /srv/horde/pear/pear -c /srv/horde/pear.conf channel-discover pear.horde.org 5 /srv/horde/pear/pear -c /srv/horde/pear.conf run-scripts horde/Horde_Role 6 /srv/horde/pear/pear -c /srv/horde/pear.conf install --alldeps horde/groupware Otherwise running the Horde_Role script will fail saying config-set (horde_dir, /srv/horde/, user) failed, channel pear.php.net This was experienced on SLES11SP1, SLES11SP2 and openSUSE Factory. I did not test this for any debian based products yet. [Less]