Re: [AgileWiki] Second thoughts--highLow and simpleAccounting

[Bill la F. <bil...@su...>]

Hi Ed! From your response, it is clear that I didn't introduce the topic 
I was discussing.

AgileWiki (AW) has several thin clients (AwServlet, AwSwingClient, 
AwTextClient) and a big fat end, AwServer.
OK, AwServlet isn't really a client--that's the browser--but it is a 
thin mid-tier process all the same.

Now to put what I wrote in context, I was talking about AwServer, which 
is a Rolonic database and application server all rolled into one. Within 
this context (and you will find us Rolonic guys are always talking about 
context), the three files I was talking about are what pull the diverse 
parts of AwServer together. And they are key to extensibility or, 
perhaps a more common activity, installing applications.

As for JNLP files, I really do want to use Java Web Start. We already 
use RMI for communicating between the clients and the server. Indeed, 
the AwSwingClient download file comes pre-configured to access the 
backend running at agilewiki.org. Currently it is a pain because every 
time we change versions, everyone needs to download the updated client.

As for being the Swing Guy on this team, I'm not sure that's the right 
term. We've got a lot of developers with a wide range of experience and 
I'd like to see the community grow to be thousands rather than the high 
teens that it is now. I am hopeful that you will take a lead in working 
on the Swing client and be an active participant in related areas as 
well. I will help where I can, but in the long run I'd like to focus 
mostly on team building, documentation, architecture, and support.

Bill

Ed Tidwell wrote:

>Bill la Forge wrote:
>  
>
>>First, lets rename fields.txt, rolons.txt and commands.txt to 
>>AgileWiki3.fields, AgileWiki3.rolons and AgileWiki3.commands, but lets 
>>leave them where they are.
>>
>>Now lets also have the logic which processes these files also process 
>>all *.fields, *.rolons and *.commands files in the working directory. 
>>This way installation is only a matter of adding the application .jar 
>>file to the lib directory and adding the extension files to the working 
>>directory.
>>  
>>    
>>
>First, I'm really against giving it a .txt extension even if it is.  Why 
>advertise what is inside the container.  ;-)
>Second, shouldn't we have a simple M-V-C paradigm here where the model 
>is the data model?
>To me the client be it web or Swing is the view.  The controller is the 
>server processes that hook it all together.
>
>Swing isn't really that clean.  The Controller and View are both in the 
>Bean JComponent with the Model being somewhere else.   BTW  I'm suppose 
>to be the Swing guy on this team.  ;-)
>
>Speaking of that if the Swing and client JARS have a JNLP file to launch 
>them over HTTP then we just socket back to the server for shared 
>information.  The way Google Earth streams data to a 3D client comes to 
>mind but not everyone wants a really cool RICH GUI client.  I guess it 
>would be a FAT client if all of the worlds data came with the Google 
>Earth installation.  :-)
>
>Cheers,
>Ed
>
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Compstrm-wiki mailing list
>Com...@li...
>https://lists.sourceforge.net/lists/listinfo/compstrm-wiki
>  
>