Re: [agilewiki-wiki] room for more pictures

[Hanif Babazadeh\(CPU\) <han...@gm...>]

Bill,
Therefore I guess I should learn more about the project.
Maybe AW is not a simple virtual Wiki. Then, we should find an
UNDERSTANDABLE way to introduce what it is!
It is a mail server, it is an infobase, it is an application server, it is a
learning project, and most importantly, it still tends to remain a WiKi!!!
Maybe it is a complicated project. Maybe it is simple.
I don't know. Just let me consume some time to understand it and then, I'll
write my understanding about the whole idea.
Maybe if it was a commerical product, we couldn't even sell a single license
of it. Maybe it is just another revolution in the 21st century, information
technology age!
Personally, I think I have not consumed enough time to know what it is. I'm
sorry, it's my fault.
Just gimme some time, and I'll write back. I don't promise very soon, but I
promise that I'll write my experience.
 
regards,
-H

  _____  

From: agi...@li...
[mailto:agi...@li...] On Behalf Of Bill La
Forge
Sent: Tuesday, August 29, 2006 9:18
To: General discussion
Subject: Re: [agilewiki-wiki] room for more pictures


Hanif,

I love to toss out code! But the swing interface is important.

Sometimes you want to run applications locally. Sometimes the data is very
private. And laptops are not always connected.

Remember that this is a general knowledge repository, not just a wiki.
Previously it was (and will again be) an email client. Also in the past
there were facilities for coordinating data (sharing) between infobases, so
you could work locally and then dialup once a day and swap changes.

Now I'll also note that the Swing client and Servlet client are both very
very small. Everything is done in the same process as the infobase--keeps it
very fast and flexible. And note also that the back end doesn't even know
the kind of client it is working with. The interface is XML, which can be
very magical... when done right.

Bill

Hanif Babazadeh(CPU) wrote: 

Indeed it is an advanced feature, but sometimes, we -developers- consume 80%
of our precious time on a feature that's hardly used in 20% of times.
A Wiki is an online thing. This question always pops in my mind that why a
customer should need to run a local Wiki? ANd even if someone does, do we
need to complicate all the interface and design to fulfill that rare use?
Please don't make me wring. I'm just asking what I don't know. I mean "is
that swing interface important?"
 
thanks,
H