New Home Page for AgileWiki
With the release going out today, the database is now fully scalable. Time for a home page which sports a feature list: http://agilewiki.sourceforge.net
Exploring Time as a dimension in Software Applications and further developments of the AgileWiki project, salted lightly with personal notes.
With the release going out today, the database is now fully scalable. Time for a home page which sports a feature list: http://agilewiki.sourceforge.net
I've just created a ning network for AgileWiki: http://agilewiki.ning.com/
Just completed a new section to the User Guide, Rolon Basics:
I've just added a new page to the wiki which I think you will enjoy. It may well be the ultimate disruptive technology. :-)
With most software projects, if you have N options/features, the order of complexity is on the order of 2**N. So long as N is small, things go well, but as you add options and features, the complexity quickly gets out of hand--integration then becomes a black art. In contrast, the complexity of this project is on the order of b+N, where b is the complexity of the base system. That b is a bit large, so it makes it hard to come up to speed, but as the project grows, the overall complexity is proportional to the number of options/plugins. This is an astonishing result.
We've started using Twitter on the AgileWiki project.
http://agilewiki.wiki.sourceforge.net/Identity
The renameChild command is working again.
Finally completed the operational theory of the element model. I do hope you find it helpful.
A comprehensive road map for Element Model and AgileWiki4 has been added to the home page. Inferencing, a mail client and versioning are included.
After a restless night I've decided not to do the design time thing. Two reasons:
Today I was working on configuration. Configuration is never easy, but in the Element Model it seemed extra difficult because it is spread across too many classes. Finally decided to make use of the JavaBean design time idea. Application logic should support its configuration.
New validate utility checks the integrity of a database.
The Element model has come a long way and release 9-11 is out.
http://agilewiki.wiki.sourceforge.net/
Release 5-3:
Fixed a critical bug introduced in 5-1 which prevented most sample programs from running.
http://agilewiki.wiki.sourceforge.net/GFrameManager
The element model now supports the development of fully decoupled Swing components. Layout can now be separated from behavior, making for a much more fluid architecture.
RsBrowse is replaced by GBrowse.
New samples package.
-New CommandStatusEvent for tracking command completion.
Any program can now be run using a generic Main.main.