Harald Wehr wrote:
Hi Vadim,
sorry for writing directly to you, but I did not get an answer to my posting to the developer list.
Well, you have to have a bit more patience.
I generally agree that image input handling should be present in this way or another in the Woody, but I currently do not keep all of the Woody in my head (plus, the usual time-factor) so it's hard for me to say are your suggestions good or not.
I can help you only with advice to make another attempt on the list; and file a patch to BugZilla with proposed solution. Somebody will take a look at it, sooner or later.
PS May be Sylvain or Bruno have a need for an image input and will do something about it :-)
;-)
Not yet, but since the need exists, why not adding it to Cocoon?
About the private classes, I think its finally a good thing they are private, as IMO they need a bit of refactoring: their fields are package accessible while their methods are private, and I don't like runtime classes (JXPathBindingBase) to have dependencies on build-time classes (JXPathBindingBuilderBase.CommonAttributes).
So, Harald, my suggestion is for you to wait a few days so that I refactor these classes and then provide the new widget.
Deal?
Sylvain (readying for a full-day Woody training tomorrow)
Vadim
As you were the latest one that modified something in JXPATHBindingBuilderBase in woody I try to get an answer to these questions. My mail is here:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107521429532253&w=2
Following snippet is a copy of that posting:
---------------------
In our forms we often have to handle input parameters from an image within a form. When the user clicks in an image the browser transfers parameters of the form img.x and img.y
To handle this we implemented an ImageWidget, that is able to store the value (the image name) and additionally the x and y value.
Now we try to develop a special binding, as we have to get access to some properties of the widget (x and y).
We therefore tried to inherit from JXpathBindingBuilderBase and JXPathBindingBase but access to class CommonAttributes is not allowed. Is this an intended feature of the binding framework?
With our own binding implementation we would like to benefit from the common attributes like load-enabled or save-enabled even if our class is in another package than the binding classes coming with woody.
-----------------------
Can you help me with this?
Harald
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
