Re: [Gusdev-gusdev] Struts documentation - objectives

[Steve F. <st...@pc...>]

I would like to add an objective:
  - an abstraction of form parameters.  Here at CBIL we have a system 
called CSP (originally "CBIL Style Police") which abstracts data types 
like Doubles, Enums, Trees.  It constructs the dialogue fragment to dump 
into a page, provides help text, and validates the input.


Adrian Roy Tivey wrote:

>Quoting Steve Fischer <sfi...@pc...>:
>
>...
>  
>
>>on the assumption that Struts will be a good framework for us, i would 
>>like to step back and ask us to state what our objectives are.  on our 
>>side, we are thinking that this will become the next version of the GUS 
>>Website Development Kit. 
>>If that is so, then here are some possible objectives that come to mind:
>> 1. work within the GUS build system
>> 2. creation of a default website (bravo on your effort here)
>> 3. all the session stuff we might need
>> 4. use of JSP to separate layout from content
>> 5. some kind of abstraction of query pages that allows us to separate 
>>the sql from layout considerations (and also the sql used to populate 
>>and or construct pulldowns
>> 6. some kind of abstraction to specify queries that are used to 
>>generate result pages
>> 7. support for the boolean and history modes
>>    
>>
>
>
>We had a similar list but I can't recall it at the moment. The only ones I
>remember not covered above are:
>8. Make it feasible for the curators to maintain their own pages for eg news
>9. Be able to integrate third-party services (for some definition of integrate)
>
>Adrian
>
>
>
>
>
>  
>