It’s just data

wxAggie?

Ted Leung: The OSAF folks have posted a tentative release plan for a Chandler 0.1 release.

Looking at proposed features for Chandler, no obvious weblogging aspects (like RSS support) are immediately apparent to me. Other than that, it certainly looks to become a foundation for a aggregator to combine email content, instant messaging content, news, blogs, updated product information, etc all in a unified interface.

Looking at the technology, it looks like this will be based on wxWindows. The demo for this toolkit is very good. It looks to me like the built in wxHtmlWindow control would be sufficient for displaying content from RSS.

I wonder what it would take to build a RESTLog client or to port Aggie to this? This would enable the use of the ultraliberal RSS parser which would nicely address the regexable XML issues.

Any interest, Joe, others?

Interesting. Always looking for more reasons to do more Python.

Posted by joe at

I believe EFFnews is built on wxPython. http://effbot.org/zone/effbot-exe-index.htm

But on second reading, it does not appear to be open source. At least, I can not find the source. So never mind.

Posted by Mark at

Aggie already has an ultraliberal RSS parser. What would we gain by switching to Python?

Posted by Ziv Caspi at

Ziv: me. ;-)

Longer term, I want the RSS aggregator to be a tiny part of a larger picture (see above).

Note: there needs be no "switch". Both can coexist.

Posted by Sam Ruby at

WxAggie

Sam has some pointers to what the OSAF folks are planning. Sounds interesting, I've been looking for a good excuse to dig into Python some more....

Excerpt from Simon Fell at

I'm (obviously) interested in this.

Posted by Ted Leung at

Sam: Isn't the whole point of the componentization movement to allow components in different languages to work together?

One might ask why doesn't Aggie provide an API (COM, .NET. CORBA, SOAP, REST, whatever) accessible by your Python scripts. Indeed, now I ask myself the same question, and can come up with no good reason not to do it...

Posted by Ziv Caspi at

Componentization

Ziv Caspi: Isn't the whole point of the componentization movement to allow components in different languages to work together? A brief sketch on my thoughts on the subject: a process should manage its own state with transfers of state between ...

Pingback from Sam Ruby: Componentization

at

Add your comment