David Geary wrote:
> Cedric's got some good ideas here, and I agree with someone else who said he should
>be
> a committer.
>
See proposal on STRUTS-DEV.
>
> Craig?
>
> david
>
Craig
>
> Cedric Dumoulin wrote:
>
> > Hi David, and everybody,
> >
> > I understand David's position, there i
Well, if there is no objections, I am ready to provide an implementation of my
suggestion for template screens (build on top of Templates).
If there is some comments, please let me know before I start.
Cedric
David Geary wrote:
> Cedric's got some good ideas here, and I agree with someo
Cedric's got some good ideas here, and I agree with someone else who said he should be
a committer.
Craig?
david
Cedric Dumoulin wrote:
> Hi David, and everybody,
>
> I understand David's position, there is a proverb which said "who go slowly go
> surely" ;-)
> But, please, don't forge
Hey, guys,
I have a good proposal: include Cerdic to struts developer team.
Cedric Dumoulin wrote:
> Hi David, and everybody,
>
> I understand David's position, there is a proverb which said "who go slowly go
> surely" ;-)
> But, please, don't forget that I have already work for a long ti
Hi David, and everybody,
I understand David's position, there is a proverb which said "who go slowly go
surely" ;-)
But, please, don't forget that I have already work for a long time on Components
proposal. A lot of peoples have tried them, and give positive feedback, as well as
improvemen
Hi David,
It maybe useful to study the portlet concept in
JetSpeed. I see your proposal and portlet essentially
different way to implement dynamic screen layout.
--- David Geary <[EMAIL PROTECTED]> wrote:
> I see template screens as a first step towards
> Cedric's Components. Template
> screen
On Wed, Feb 28, 2001 at 01:18:54PM -0700, David Geary wrote:
> I see template screens as a first step towards Cedric's Components. Template
> screens provide the foundation necessary for Components: Programmatically
> defining screens.
>
Slightly off-topic but relates to the template tags. I've
I see template screens as a first step towards Cedric's Components. Template
screens provide the foundation necessary for Components: Programmatically
defining screens.
The next step is adding support for defining screens from an XML file, whether
that's struts-config.xml or a separate file. Then
A kind of "screen configuration" (called instances) is proposed in
Components project, which can be seen as an extension of Templates.
Screens are defined in a configuration file. You can also have different
configuration files for different Locale : appropriate screens will be loaded
accord
Hi,
I think the screen configuration through a xml-file is made in Components
project (see for example,
componentInstances.xml file). It is very convenient. As you maybe know,
the project extends ActionServlet class.
Maya
David Geary wrote:
> Yes, that's a good idea, applicable for static screen
Yes, that's a good idea, applicable for static screens.
We should still allow for programmatic definitions, though. Servlets or
servlet filters are good candidates for creating dynamic screen
definitions.
david
Wong Kok Wai wrote:
> Is it possible to define the screen definition in the
> stru
Is it possible to define the screen definition in the
struts-config.xml? I think this will be more flexible.
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
Joel Regen wrote:
> David,
> Wouldn't it make sense to introduce a few attributes to the template tags
> that allow specification of values using references to beans? This idea is
> used extensively in the other struts tags. Look at the html:link tag, for
> example. It allows you to specify a
13 matches
Mail list logo
