Delighted!
I expect to be wrapping up classifiers this weekend. After that the
focus shifts to usibility in all forms--documentation, user interface
and sample applications.
So I am very interested in what everyone things is worth keeping and
what should be changed or dropped like a 3-week old fish.
I also need to hear what is hard for a newbie and any suggestions on how
to fix it. Remember, you're only a newbie once, so the time you can help
most in that area is now, not later.
Now the database seems pretty solid, but I have my concerns about the
commands. One area which I think is particularly week is the delay
between starting a command and when a form starts executing. In that
time changes can occur and I believe the forms make a lot of
assumptions. Its ok for now, but not reliable in the long run.
But mostly I am more worried right now about making the GUI less
repulsive and enabling programmers to write applications. There are some
truely wonderful things happening in AgileWiki--it has enormous
potential--but to realize any of that potential there is a lot that
needs to be cleaned up and worked out.
So Suresh, I need your help, and the help of everyone else as well.
Bill
Suresh Nadarajan wrote:
> Hi,
>
> This is Suresh.
>
> I am so happy to join this project. and i am proud to be one amoung you.
>
> My details:
>
> Name: Suresh N.
> work: Chief Architect & Managing Director .
> S-APPSYS.
> Edu: Bcom.,MCA
> Skill set: java, Swings, J2EE, C,C++ with network programming.
>
> Projects:
> Currently i am working as a Chief Architect. And i have
> developed and managed more than 20 commercial products in Java swings
> & J2EE.
|
