Rickard Öberg wrote:
Not with the same transparent syntax, since the Velocity templates use
the Velocity language. I.e. if you'd want to use the WW EL then you'd
have to delegate to WW explicitly, e.g. $stack.findValue("foo").
I personally use WW and Velocity almost exclusively, for three reaso
Aslak Hellesøy wrote:
I'm about to start a new project, and we have decided to use WebWork. I'd
like to hear what kind of view technology the WebWork users/developers
recommend. I'm hesitating between Velocity and JSP.
I prefer Velocity over JSP because it's quicker to use for development (no
nee
boxed wrote:
I have written a custom directory browsing view with webwork, and it works
fine now, but I discovered a rather annoying thing in webwork in the
proccess: ServletDispatchers getActionName() method is private. This forced
me to copy paste the entire code of this class into my directory
Toby,
Great stuff - I've added a link to it from the WebWork page on the wiki -
thanks!
Cheers,
Mike
On 10/12/02 2:40 PM, "Toby Hede" ([EMAIL PROTECTED]) penned the
words:
> Hi,
>
> I have been planning some documentation stuff as well, I started with a
> dummies guide:
>
> http://info-archit
Hi,
I have been planning some documentation stuff as well, I started with a
dummies guide:
http://info-architects.net/webwork/fundamentals-dummies.html
And I need to get working on some other areas as well.
Toby
> Ken,
>
> Agreed - we greatfully appreciate any improvements to the documentati
After 1.3, I plan to move the taglib code out of the taglibs into a
general helper package that the taglib will extend. In this way, adapting
to a new view would simply be a matter of writing the bridge from the view
to the helpers. Thoughts?
--Erik
On Tue, 10 Dec 2002, Mike Cannon-Brookes wrote
Ken,
Agreed - we greatfully appreciate any improvements to the documentation!
Perhaps the best way you (or anyone - it's really easy!) can help out is
just to start documenting things on the Wiki
(http://www.opensymphony.com:8668). Anyone can sign up and write some extra
pages of information.
Th
Aslak,
Having just written a book chapter on WebWork views, I'm quite au fait with
this situation! :)
The JSP views _are_ more advanced at the moment, but that's only because
none of the core developers has any Velocity projects or much Velocity
experience. There is no reason (from looking at Vel
> I'm about to start a new project, and we have decided
> to use WebWork. I'd like to hear what kind of view
> technology the WebWork users/developers recommend.
Good choice! I have used Velocity, but support for JSP is a way above
from what WebWork gives to Velocity users. I have since switched t
Welcome to the project and kudos on a very well
written introduction of yourself.
Looking *very* forward to your contributions.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---
Hello,
My name is Ken Egervari ('speek' as you might know
me in #java). I talked with boxed the other day about helping you
guys out with improving the documentation. After reading the
documentation for the first time, I noticed it could use some
clarifications here and there, more conci
Hi!
I'm about to start a new project, and we have decided to use WebWork. I'd
like to hear what kind of view technology the WebWork users/developers
recommend. I'm hesitating between Velocity and JSP.
I prefer Velocity over JSP because it's quicker to use for development (no
need to recompile as
12 matches
Mail list logo
