Tickets :: Comment on [#7285] Proposal for new Horde_Text

* Your Email Address
* Spam protection	Enter the letters below: .__..___.__ .__ __. [__][__ [ __[ __(__ \| \|[___[_./[_./.__)
Comment	> Hello there, > > > > Sorry for the long delay, I am terrible at responding atm. The > package itself isn't dead. It's rather stalled for the moment as we > are currently overhauling our forum enigne completely. Part of this > is moving away from the "let's concatenate strings and hope > everything validates in the end" in favour of a more sane "use dom > xml from the very beginning" aproach. This will also effect the > BBCode parser. > > > > As for Horde_Image: It has been one of the design goals of this > package to provide everything it needs itself, if necessary. This > will most likely change as well. My current plan is to make the image > processing part entirely optional (as in: This feature will be > available if certain external packages are available). The feature > set won't change much. One fo the last feedbacks I received concerned > routing external links through anonymizers as anonym.to, which would > be a cool feature IMHO. > > > > PHPUnit is part of our new set of build tools (as is Phing), so you > can expect a lot of PHPUnit tests as well. All in all, I'd say there > won't be a new version before February (likely close to March).
Attachment
Watch this ticket