This would be nice. And of course it could have a prefix:
<!--V 'ELEMENT:FRIEND:com.uwyn.rife.widgets.CalendarWidget'/-->
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 anything else (flowlinks, datalinks, etc.), so it is a rather
narrow ground to be integrated. And as is done currently, a named
exit
in the template could be bound in the sitemap to a destination
Element.
So maybe even a Calendar widget could have some well-integrated exits.
(Or am I full of balonie ?)
Nope that's totally correct, and a widget (since it's an element)
could still have any kind of site-structure related declaration.
So ... how about a Rife widget for an in-browser editor like Mozile
or BXE ? :-D
That's already possible, just write an element for it and it'll also
be a widget later. I would prefer TinyMCE though ;-)
--
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
