I already pointed at MS Visual Studio , aka the .net environment
for asp pages or whatever its called now, but I know that they are
also working towards making AJAX easy, same with some other vendors.
In order to be working on something that has all the hype and will
not be oldfashioned when
Btw,
I already pointed at MS Visual Studio , aka the .net environment for asp
pages or whatever its called now, but I know that they are also working
towards making AJAX easy, same with some other vendors.
In order to be working on something that has all the hype and will not
be oldfashioned w
This would be nice. And of course it could have a prefix:
Sure, but tell me what you would use the prefix for besides
differentiation? If there's no other reason, a suffix would be more
consistent.
AFAICT currently HTML widgets are bound only to submission parameters,
not to anythi
Surely sendmail reeled when thusly spake Geert Bevin:
>
> >So are you thinking something like:
> >
> >
> >
> >and then the various inputs/outputs/submissions are detected?
>
> Something along those lines, yeah.
This would be nice. And of course it could have a prefix:
AFAICT currentl
So are you thinking something like:
and then the various inputs/outputs/submissions are detected?
Something along those lines, yeah. With optional declaration in the
site structure to expend the declaration with what is not possible to
specify in the class itself (flowlinks, datalinks, in
On 9/15/05, Geert Bevin <[EMAIL PROTECTED]> wrote:
>
> > Instead of
> > protected String validSchemas[] { "DocBook", "DITA", "XHTML" };
> > publicvoid setSchema(String s) { .. ]
> > publicString getSchema() { .. }
> >
> > I'd like to say something like
> >
> > @property("
Instead of
protected String validSchemas[] { "DocBook", "DITA", "XHTML" };
publicvoid setSchema(String s) { .. ]
publicString getSchema() { .. }
I'd like to say something like
@property("readwrite")
@enumerated("DocBook","DITA","XHTML")
@widget("combobox","edi
Surely sendmail reeled when thusly spake Geert Bevin:
>
> >You talk about using autodiscovery to detect forms variables
> >and forms processing methods, and I think that would be great.
> >I wonder if (for example) it would be useful if an Element
> >could use annotations to declare the forms varia
You mention annotations, and that is definitely the way
to go, to move from a procedural style to a declarative.
I note that Rife is using Constraints to implement (in
a JDK 1.4 context) what other frameworks are trying to
do now with 1.5 :)
Indeed :-)
The constraints have one huge benefit tho
You mention annotations, and that is definitely the way
to go, to move from a procedural style to a declarative.
I note that Rife is using Constraints to implement (in
a JDK 1.4 context) what other frameworks are trying to
do now with 1.5 :)
This is obvious I guess; all I want to say is that i
RIFE users list : questions"
Date: Thu, 15 Sep 2005 09:41:53 +0200
Subject: [Rife-users] Componentization at widget level
Hi,
I've been looking at component frameworks since a little while and it
seems that the major difference between RIFE and all the rest is that
RIFE focuses on com
Hi,
I've been looking at component frameworks since a little while and it
seems that the major difference between RIFE and all the rest is that
RIFE focuses on componentization and reuse of fragments (portlets),
pages and sites. Imho the site structure and embedded elements work
very well
12 matches
Mail list logo
