webwork-devel

[Webwork-devel] next release features, requirements

[<ma...@sm...>]

I wanted to initiate a discussion for next release
features, requirements people feel are important for
WW. I hope collectively, we can come up with a good
list which we can prioritize and delegate. So here goes.

Documentation
1. Better velocity documentation

Enhancements
1. More velocity macros, etc.
2. WML tags
3. XHTML tags

Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks?
how well does WW scale?
4. Logging - overhaul debug statements to use proper
logging levels - debug, info, etc.
5. Nightly builds

Incorporating new view technologies
1. Flash
2. Apache Axis?

-Matt

[Webwork-devel] RE: [Webwork-user] next release features, requirements

[Rick S. <rs...@mb...>]

> From: On Behalf Of ma...@sm...
> Sent: Tuesday, April 02, 2002 3:52 PM
> Subject: [Webwork-user] next release features, requirements
> 
> 3. XHTML tags

I think making the WW's output xhtml compliant would be an excellent
step. I've been developing all my sites to transitional currently. I've
developed a few sites strict as well, and if this would make all WW
would output to xhtml, it would make developing a web app to be viewable
by all xhtml compliant devices a minor chore. I don't know if I'd be too
concerned with WML right off the bat. From what I can see, not too many
people (at least the ones I know ;)) are using it. Most new cell phones
or PDA's understand simple xhtml, so I'd probably add in xhtml support
first.

> 3. Instrument/profile code - where is our bottlenecks?
> how well does WW scale?

I'd love to help out with this if needed. 

> Incorporating new view technologies
> 1. Flash

Sounds interesting... Where I work, the designers are crazy about Flash.
A lot of the new devices coming out have a flash player for them. This
would be an excellent way to get WW into those shops...

> 2. Apache Axis?

Again, sounds intriguing. 


Rick

[Webwork-devel] revised - next release features/requirements

[Matt B. <ma...@sm...>]

So here is a revised list of possible next release feature/requirements
based on what people have posted. Other ideas?

 Documentation
 1. Better velocity documentation
 2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example containing all the goodies
(commands, aliases, hierarchical aspects etc.) and describing the main
differences between them.
 3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties)

 Enhancements
 1. More velocity macros, etc.
 2. WML tags
 3. XHTML tags (possible move our existing tags to be XHTML compliant)
 4. Chain actions

 Misc
 1. Bug list
 2. Feature list
 3. Instrument/profile code - where is our bottlenecks? how well does WW
scale?
 4. Logging - overhaul debug statements to use proper logging levels -
debug, info, etc.
 5. Nightly builds

 Incorporating new view technologies
 1. Flash
 2. Apache Axis (SOAP)?

 -Matt
>
>
>
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>
>

[Webwork-devel] Re: [Webwork-user] revised - next release features/requirements

[Philipp M. <me...@me...>]

On Wed, Apr 03, 2002 at 08:04:16PM -0600, Matt Baldree wrote:

>  Enhancements
>  1. More velocity macros, etc.
>  2. WML tags
>  3. XHTML tags (possible move our existing tags to be XHTML compliant)
>  4. Chain actions

The XSLT view stuff should be enhanced slightly to be really useful. We
need some XSLT java extension for URL-escaping and so on. I don't know
if I'll have the time but I don't want to give up the XSLT thingy. So
is their anybody except me using it? Huh?

-billy.

-- 
Meisterbohne       Söflinger Straße 100          Tel: +49-731-399 499-0
   eLösungen       89077 Ulm                     Fax: +49-731-399 499-0

Re: [Webwork-devel] Re: [Webwork-user] revised - next release features/requirements

[Mike Cannon-B. <mi...@at...>]

Might I make a suggestion that I think should go to the top of the list...

FileAttachments! AttachmentAware! FileUploadAware!

Whatever we want to call it ;)

(At the moment to do file uploads you have to use JSP or a servlet - which
is the only area of our app we can't use webwork - which stinks ;))

Cheers,
Mike

PS The ClientAction documentation and SOAPAction didn't make the list either
;)

On 5/4/02 12:15 AM, "Philipp Meier" (me...@me...) penned the
words:

> On Wed, Apr 03, 2002 at 08:04:16PM -0600, Matt Baldree wrote:
> 
>>  Enhancements
>>  1. More velocity macros, etc.
>>  2. WML tags
>>  3. XHTML tags (possible move our existing tags to be XHTML compliant)
>>  4. Chain actions
> 
> The XSLT view stuff should be enhanced slightly to be really useful. We
> need some XSLT java extension for URL-escaping and so on. I don't know
> if I'll have the time but I don't want to give up the XSLT thingy. So
> is their anybody except me using it? Huh?
> 
> -billy.

Re: [Webwork-devel] Re: [Webwork-user] revised - next releasefeatures/requirements

[Justen S. <js...@we...>]

+1
----- Original Message -----
From: "Mike Cannon-Brookes" <mi...@at...>
To: "Philipp Meier" <me...@me...>; "Matt Baldree"
<ma...@sm...>
Cc: <web...@li...>;
<web...@li...>
Sent: Thursday, April 04, 2002 4:42 PM
Subject: Re: [Webwork-devel] Re: [Webwork-user] revised - next
releasefeatures/requirements


> Might I make a suggestion that I think should go to the top of the list...
>
> FileAttachments! AttachmentAware! FileUploadAware!
>
> Whatever we want to call it ;)
>
> (At the moment to do file uploads you have to use JSP or a servlet - which
> is the only area of our app we can't use webwork - which stinks ;))
>
> Cheers,
> Mike
>
> PS The ClientAction documentation and SOAPAction didn't make the list
either
> ;)
>
> On 5/4/02 12:15 AM, "Philipp Meier" (me...@me...) penned the
> words:
>
> > On Wed, Apr 03, 2002 at 08:04:16PM -0600, Matt Baldree wrote:
> >
> >>  Enhancements
> >>  1. More velocity macros, etc.
> >>  2. WML tags
> >>  3. XHTML tags (possible move our existing tags to be XHTML compliant)
> >>  4. Chain actions
> >
> > The XSLT view stuff should be enhanced slightly to be really useful. We
> > need some XSLT java extension for URL-escaping and so on. I don't know
> > if I'll have the time but I don't want to give up the XSLT thingy. So
> > is their anybody except me using it? Huh?
> >
> > -billy.
>
>
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>

Re: [Webwork-devel] Re: [Webwork-user] revised - next release features/requirements

[Rickard <ri...@mi...>]

Philipp Meier wrote:

>> Enhancements
>> 1. More velocity macros, etc.
>> 2. WML tags
>> 3. XHTML tags (possible move our existing tags to be XHTML compliant)
>> 4. Chain actions
>=20
> The XSLT view stuff should be enhanced slightly to be really useful. We
> need some XSLT java extension for URL-escaping and so on. I don't know
> if I'll have the time but I don't want to give up the XSLT thingy. So
> is their anybody except me using it? Huh?

It's tough at the top you know ;-)

/Rickard

--=20
Rickard =D6berg

[Webwork-devel] DRAFT 3 - next release features/requirements

[Matt B. <ma...@sm...>]

3rd draft of possible next release feature/requirements based on what people
have posted. Right now these are candidate ideas. Once we have a good list,
we can repost for inclusion/exclusion/prioritization, etc.

Other ideas?

Documentation
1. Better velocity documentation
2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example containing all the goodies
(commands, aliases, hierarchical aspects etc.) and describing the main
differences between them.
3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties)
4. Client Action documentation

Enhancements
1. More velocity macros, etc.
2. WML tags
3. XHTML tags (possible move our existing tags to be XHTML compliant)
4. VXML tags
5. Ability to chain actions
6. XSLT should be enhanced slightly to be really useful. We need some XSLT
java extension for URL-escaping and so on.
7. Ability to receive multi-part content - AttachmentAware?

Examples/Tests
1. More Swing/Client side examples

Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks? how well does WW
scale?
4. Logging - overhaul debug statements to use proper logging levels - debug,
info, etc.
5. Nightly builds

Incorporating new view technologies
1. Flash
2. Apache Axis (SOAP)

-Matt

Re: [Webwork-devel] DRAFT 3 - next release features/requirements

[Rickard <ri...@dr...>]

Matt Baldree wrote:

> 3rd draft of possible next release feature/requirements based on what people
> have posted. Right now these are candidate ideas. Once we have a good list,
> we can repost for inclusion/exclusion/prioritization, etc.
> 
> Other ideas?


Somewhere down the line we should investigate supporting JavaServerFaces 
(looks trivial) and the new standard tag library. I've also been 
thinking about maybe refactoring the dispatcher so that it separates the 
HTTP-specific parts from the purely WW-specific parts, in order to more 
easily have more dispatchers.

Also, people have been complaining that it's not possible to have 
multiple servlet dispatchers in a web app. I'm not quite sure why one 
would want that, but there ya go. Maybe someone can enlighten me.

Some have also complained that the action description is "monolithic", 
i.e. it's not possible to describe actions in multiple files. AFAICT 
this is not entirely true since one can put partial configs in 
XML-snippets and use entities in a actions.xml to reference them. 
Haven't tried it though.

Moving more towards an XML-based configuration scheme may be a good 
idea. Not sure though, since XML would make it much much more verbose.

/Rickard

-- 
Rickard Öberg

[Webwork-devel] DRAFT 4 - next release features/requirements

[Matt B. <ma...@sm...>]

4th draft of possible next release feature/requirements based on what people
have posted. I've also listed the person that requested the
feature/requirement based on memory. Could be wrong? Looks like we have a
pretty good list. I'll wait for revisions and then I propose that my next
post be for inclusion/exclusion/prioritization.

 Documentation
1. Better velocity documentation (Matt)
2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example containing all the goodies
(commands, aliases, hierarchical aspects etc.) and describing the main
differences between them. (Paolo)
3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties) (Paolo)
4. Client Action documentation (Mike)
5. Splitting documentation into a RedBook and a reference. (Peter)

 Enhancements
1. More velocity macros, etc. (Matt)
2. WML tags (Matt)
3. XHTML tags (possible move our existing tags to be XHTML compliant) (Matt)
4. VXML tags (Matt)
5. Ability to chain actions (Pat)
6. XSLT should be enhanced slightly to be really useful. We need some XSLT
java extension for URL-escaping and so on. (Billy)
7. Ability to receive multi-part content - AttachmentAware? (Mike)
8. Ability to reuse the same action - i.e.
I've also got a SessionActionFactory that I built a while back that will
reuse the same action by saving it and pulling it from the session, which
makes things like multi-page forms easy, because you don't have to keep
passing the data along as hidden fields, etc. (Jason)
9. Support for Java Server Faces (Rickard)
10. Support for Java Standard Tag Library (Rickard)
11. Support for Portlet API (Rickard)
12. Ability to have more than one servlet dispatcher (need more info)
(Rickard)
13. Revaluate the standard configuration scheme (Rickard)
14. Management console - some configuration tool would be nice. (Low)
15. Security model/framework (Low)

 Examples/Tests
1. More Swing/Client side examples (Pat)

 Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks? how well does WW
scale? (Matt)
4. Logging - overhaul debug statements to use proper logging levels - debug,
info, etc.(Matt)
5. Nightly builds (Matt)
6. Tool integration - DreamWeaver integration for the ui tag. (Low)

 Incorporating new view technologies
1. Flash (Rickard)
2. Apache Axis (SOAP) (Matt)

 -Matt

[Webwork-devel] Re: features request: reloadable Actions/Beans

[Bill B. <bi...@pr...>]

Hello,

Here's another enhancement suggestion: Reloadable Actions and Beans.

I'm working on a project now interfacing WW with a third party
application.  However, it takes a long time for the web app to restart
after making changes to Actions or Beans.  So it would be nice if it were
possible if Actions and Beans were reloadable.

Another, similar enhancement would be to support reloading the action and
view mappings without a restart.

-Bill

ma...@sm... wrote:
> 
> I wanted to initiate a discussion for next release
> features, requirements people feel are important for
> WW. I hope collectively, we can come up with a good
> list which we can prioritize and delegate. So here goes.