Why pyDS is not suitable for Wego?

PyDS is cool with it's mimic of Radio Userland in a very simple and open way. If Dave Winner opened his Radio Userland and Mania years ago, maybe the tool has become a real name in today's software industry.

However, PyDS, is not perfect enough for wego architecture. Wego is as same as PyDS as an open personal knowledge management tool. However, Wego is designed for more open architecture for future extensions. PyDS merges all interface and business logic, thus it's somewhat difficult to update the code and make extension. Although Georg Bauer abstracts a tool service from PyDS, the programming pattern has to be rigid to follow many rules in "PyDS" way. So I think it's not easy to program based on PyDS, even the ToolServer Georg made later on.

The Wego architecture is a multi-tier architecture. We will seperate interface layer and business logic layer, even (virtual) data access layer. The model will be prototyped soon to see if it's workable and implementable with considering other factors(e.g. Python capability).

Wego implementation

Wego idea was generated as early as in late 2003. However, it was too far from implementation that time. It's based on Isaac's theory on "Knowledge Space". The two dimensions of knowledge are time and location, which forms the space all human knowledge can be mapped with.

Later on, I found Python, the scripting language, can be well applied to "Wego" vision. It's platform and neutral and always evolved from world wide community. Thus I eventually decided to use python to prototype Wego. As I'm a python beginner, I'm so curious any other python developers can join if they share the same vision. However, I'm so disappointed that there are few real developers in China who can both take advantage of programming capability and share the same vision. Many developers would rather to dive into the language and programming skills than real usage of good stuffs. So I have to practise "learning by doing" by myself.

"Wego" seems very simple on it's architecture that we can describe in a few words. It's a NEW type of applciation theme that I believe it's the trend in the future---- Desktop Server. It runs as a local web application and provide different kinds of local service for personal knowledge management, also can be easily published to public space(many new type of social softwares, e.g., Weblog, Social Bookmarks, Social Albugm, Wiki-based collaboration, etc.). Thus it's more personal than those public/hosting service, while also loosely connected each other. We can put more and more modules to support different functions involved both private and public, as well the channels between them.

Ok, the meta idea is here, I'm working on programming now. Anyway, I'm still hoping more and more involvement to this fantastic tool that will be benefitial to each one of us.