On 12/7/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote:
Jesse Kuhnert wrote:
> I was wondering that myself. Changing field observer to handle any
> field isn't a hard change. I'll have to do a little bit more painful
> stuff in the stringbuffer method extension point to determine if the
> object I'm working with is a IFormComponent or just an IComponent so
> that I can call the getClientId or getId method appropriately.
I insist we need a getUniqueId() method in IComponent for Tapestry 4.1 .
Did I say that before? hehehe :P
> I think at this point the name of the component would have to change
> as well. EventObserver? That seems deceptive because it's logic is
> tied directly to the form. FormEventObserver? If you can think of a
> good component name that descriptively says exactly what it does I
> think we'll be all set :) I'll be working on the Dialog stuff + the
> implementation changes for this in the meantime.
- AjaxFormSubmitter ?
- AjaxSubmitEvent ?
- AjaxSubmitObserver ?
a) I think the *submit* part of the component is important to consider.
Both the other components of its kind have this on their names:
AjaxLinkSubmit and AjaxSubmit.
b) Now, unless we integrate Ajax into Tapestry core I think the explicit
"Ajax" part is necessary too.
c) Is this really an observer? What's it observing ??? I think that
maybe the "Observer" part is misleading.
d) The tricky part is the "script" part. This isn't really only a single
'script' anymore. I think it's more of an invoker.
Ok... enough ranting... Maybe we can follow conventions. We have
AjaxSubmit and AjaxLinkSubmit. We could do this:
- AjaxEventSubmit
- AjaxHiddenSubmit
What do you think ?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
