I have not dug into Pierre's sample files, but when you specify
<element extends="rife/template/print.xml">
<property name="name">menu</property>
is this essentially the same as specifying something like
<element
implementation="com.uwyn.rife.engine.elements.PrintTemplate">
<property name="template_name">menu</property>
No it's not, since when you extend you do several things:
* you hide away the implementation
* you get everything in that element declaration (inputs, output,
exist, submissions, ...)
* that base element implementation can update according to new
features and al the declaration elements and the implementation will
be updated in your element too
I ask because this is (IMHO) a fundamental distinction which
is not (or was not) clearly made in the documentation. That
is to say, a page which needs to have hyperlinks generated
for exits, but which does not otherwise require a processing
backend written in Java, is easy to define -- but it does
require a reference to a specific named functionality (print
template) that is presupplied by Rife.
I wonder if there is a way to auto-detect and auto-implement
this, for example that an element declaration like this:
<element type="html" implementation="myapp.menu">
would automatically use the print-template functionality.
Exits would be declared in the usual way.
I don't understand what you're getting at, sorry. Can you explain
this a bit better?
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
