Would something like www.xopus.org make this easier? You can edit the
XML directly in a WYSIWYG editor rendered using the XSD you're planning
to use for generating the HTML...
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 12:01 PM
T
Why not use IBM Bookmaster :) I wrote a whole manual with that once,
talk about painful!
On Wed, 2002-12-11 at 04:31, Joseph Ottinger wrote:
> How about using, oh, PF:Word then? That would rock and have a cool "gee,
> I'd forgotten that existed" factor. :)
>
> On Wed, 11 Dec 2002, Robert Nicholso
"Use my copy of JIRA. No - use mine!" ;)
Looks like we'll have to make JIRA in a maven-like fashion, where you can be aware of
all your components' bugs as well.
Kudos to the Xdoclet team - your logo looks great!
Cheers,
Scott
Aslak Hellesøy <[EMAIL PROTECTED]> wrote ..
> > -Original Me
I have spent 20 minutes making some changes for webwork. I have added a 2.0 release,
so you can start adding all your features for XWork.
I have moved a few trivial things into the 1.3 release, mostly things with patches
already attached to the issue.
You can see more info here:
http://jira
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Patrick Lightbody
> Sent: 11. desember 2002 18:44
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] Fix for webwork.module
>
>
> Herve,
> Can you open a case at http://jira.opensymphony.com with th
>> From what I understand, you have to drop
>> a NumberFormat object into the context.
>> Should this be done at startup of the
>> application?
>
> That's not even possible since a new context
> is created for each rendering.
In fact it is possible. Look at the simple example I attached to this
m
Herve,
Can you open a case at http://jira.opensymphony.com with this?
-Pat
- Original Message -
From: "Herve Tchepannou" <[EMAIL PROTECTED]>
To: "webwork" <[EMAIL PROTECTED]>
Sent: Friday, December 06, 2002 2:08 PM
Subject: [OS-webwork] Fix for webwork.module
> I found a that @webwork.
WebWork can't do complex objects like that, it just doesn't know how to
construct them. That is something I'm looking in to in the future, but no
promises.
WebWork can do something like this though:
and your action can have
setFoo(long[] foo) {
// this will be [1,2,3]
}
- Original Mess
Gotcha, makes sense. Maybe (in the future) we can have the same object work
in both cases. Ie: if there was no chain, just store the single object.
-Pat
- Original Message -
From: "Rickard Öberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 9:35 AM
Subjec
Patrick Lightbody wrote:
Couldn't you use the ActionResult handed back from GenericDispatcher
instead? It's basically the same thing, but has a bit more methods.
No, because this is used for RMI-type stuff, and I'm not that keen on
creating a List with just one item all the time. I'm rather per
Paola,
I'll be sure to get this in the 1.3 release. Can you email me the updates
directly (so I don't forget!).
-Pat
- Original Message -
From: "Vedovato Paolo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 9:18 AM
Subject: RE: [OS-webwork] 1.3 Release
>
Rickard,
My bad, that was me :)
Couldn't you use the ActionResult handed back from GenericDispatcher
instead? It's basically the same thing, but has a bit more methods.
-Pat
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 9:19 AM
Yes, let's just wait until the 1.3 release. I'll put the tags in CVS right
after the release, ok?
-Pat
- Original Message -
From: "Erik Beeson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 4:06 AM
Subject: Re: [OS-webwork] property tag and release 1.3
>
Hi List/ Eric
>PS. If you didn't see a change that you were looking for or expecting,
>please let the list know as it could have been overlooked or
>intentionally
>left out for XWork. I have started on a roadmap for XWork that
>I'll try to
>get up on the wiki today.
yup, I've posted an update of
Erik Beeson wrote:
Please checkout the latest CVS and give it a whirl. If it all looks good,
someone more adept than I can fire off the release asap.
I have a couple of changes I just committed:
* Refactored ClientServletDispatcher/ClientDispatcher to allow custom
ObjectInput/ObjectOutputStream
Blake Day wrote:
I'm actually thinking about using Velocity for some of my views. Could
anyone on the list comment on how simple things like number formatting is
accomplished? From what I understand, you have to drop a NumberFormat
object into the context. Should this be done at startup of the
I'm actually thinking about using Velocity for some of my views. Could
anyone on the list comment on how simple things like number formatting is
accomplished? From what I understand, you have to drop a NumberFormat
object into the context. Should this be done at startup of the application?
Than
You're right. I keep forgetting that we have to be careful with our words
:). Thanks for the other goodies.
Blake
- Original Message -
From: "boxed" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 11:42 AM
Subject: Re: [OS-webwork] property tag and release
The release was waiting on some updates I had yet to commit. They were:
WW-88: Add an id attribute to the tag
WW-79: PropertyTag shouldn't print when id is sepcify
These have both been fixed and the docs have been (slightly) updated to
reflect the change.
Please checkout the latest CVS and give
> Come on! What is the big deal? How will changing the tag names hurt
anyone?
> Why wait? They've already been coded.
Actually it's not about renaming, it's about adding three tags that each do
a single thing and deprecating property tag. This will break nothing and
will make the documentation a
Come on! What is the big deal? How will changing the tag names hurt anyone?
Why wait? They've already been coded.
Thanks boxed, by the way, for your work in coding them.
Blake
- Original Message -
From: "Erik Beeson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December
I think it was decided to leave the tag renaming until XWork?
--Erik
On Wed, 11 Dec 2002, boxed wrote:
> > I thought there was some agreement a while back that the Property Tag
> should
> > not print out the value if it has an id attribute, but the check for this
> > (BasicPropertyTag line 101)
> I thought there was some agreement a while back that the Property Tag
should
> not print out the value if it has an id attribute, but the check for this
> (BasicPropertyTag line 101) hasn't made it into the repository.
Could/should
> this be changed before the release of 1.3, if it is not too lat
Yes, the fix for this is sitting in my local copy of webwork, along with a
few previously discussed updates to URLTag. I'm working on finishing those
up and getting them in tonight (tuesday night). Expect a release on
Wednesday if everybody is happy with it.
--Erik
On Wed, 11 Dec 2002, Geoff Carr
Fellas-
I thought there was some agreement a while back that the Property Tag should
not print out the value if it has an id attribute, but the check for this
(BasicPropertyTag line 101) hasn't made it into the repository. Could/should
this be changed before the release of 1.3, if it is not too la
25 matches
Mail list logo
