I can see some validity to that argument. On the other hand, since Pivot has
another means of data binding that is better suited to the use case you
describe, I think it makes sense to leave the namespace binding feature as-is
and see how it ends up being used. What you describe could easily be
On Mon, 19 Jul 2010, Greg Brown wrote:
What about properties of properties of objects---like
${obj.prop.subprop}? If the "obj.prop" value changes, do the binding
listeners get notified?
No, because those listeners have indicated that the property they care
about is "subprop". They don't nec
>>> What about properties of properties of objects---like ${obj.prop.subprop}?
>>> If the "obj.prop" value changes, do the binding listeners get notified?
>>
>> No, because those listeners have indicated that the property they care about
>> is "subprop". They don't necessarily know or care that
On Fri, 16 Jul 2010, Greg Brown wrote:
I've finally had a chance to take a good look at this. This looks fine
for the use case it covers, that is, properties of objects which
observe some kind of event listener design (don't know the details).
What about properties of properties of objects---
> I've finally had a chance to take a good look at this. This looks fine for
> the use case it covers, that is, properties of objects which observe some
> kind of event listener design (don't know the details). What about
> properties of properties of objects---like ${obj.prop.subprop}? If th
I've finally had a chance to take a good look at this. This looks fine
for the use case it covers, that is, properties of objects which observe
some kind of event listener design (don't know the details). What about
properties of properties of objects---like ${obj.prop.subprop}? If the
"obj.
I moved it to the tutorials project:
http://svn.apache.org/repos/asf/pivot/trunk/tutorials/src/org/apache/pivot/tutorials/databinding/property_binding.bxml
http://svn.apache.org/repos/asf/pivot/trunk/tutorials/src/org/apache/pivot/tutorials/databinding/PropertyBinding.java
On Jul 14, 2010, at 12:
Greg,
I get a 404 when I go to the source code URL. Can you check it please?
Michael
On Fri, 9 Jul 2010, Greg Brown wrote:
Hi all,
This feature is now complete. BXMLSerializer now supports dynamic namespace
binding via the syntax I suggested in my earlier email. You can see a demo here:
Namespace bindings are evaluated after all object references have been defined,
so there is no order dependency. This facilitates the two-way binding shown in
the demo.
You apply bindings manually in code using an instance of NamespaceBinding, or
you can do it in BXML as described below. See th
Looks good.
When is the binding evaluated? If I have an include in my bxml file and the
object with the binding expression is buried in a few layers of component
(border wrapping a boxpane wrapping a label) will the binding pickup the
objects defined in the include file? Do I have to make sure
Hi all,
This feature is now complete. BXMLSerializer now supports dynamic namespace
binding via the syntax I suggested in my earlier email. You can see a demo here:
http://ixnay.biz/pivot-demos/namespace-binding.html
The source code is here:
http://svn.apache.org/repos/asf/pivot/trunk/dem
FYI, I have just checked in initial support for this feature. I haven't hooked
it in to BXMLSerializer yet, but you can see it in action here:
http://svn.apache.org/repos/asf/pivot/trunk/demos/src/org/apache/pivot/demos/binding/
On Jul 5, 2010, at 3:45 PM, Greg Brown wrote:
> Another question
I've been working on a prototype but it's a big job and I've got "real"
work to do. I've implemented an annotation and an annotation processor
that creates a property change dispatcher for an annotated property
through bytecode enhancement of a setter. It doesn't use reflection and
it support
13 matches
Mail list logo
