I'm transitioning from 1.5.1 - in my main bxml file I have:
<bxml:define>
<bxml:include bxml:id="lukeinit" src="/xml/lukeinit.bxml" />
</bxml:define>
lukeinit is a dialogue window that I pop up with various controls to
allow you to choose options for opening a lucene index.
Previously, in my code I could access controls from lukeinit using:
wtkxSerializer.get("lukeinit.componentId")
but that support appears to be gone now. Sounds like bindable is the
preferred path here - I had avoided it to start because the way I was
using was super simple to get going as I started prototyping.
- Mark
On 9/18/10 8:42 PM, Chris Bartlett wrote:
> Mark,
>
> What Pivot version are you transitioning from ? 1.4, 1.5 or 1.5.1?
> Could you post a small example of the WTKX/BXML files demonstrating
> the problem?
>
> I haven't played around with the BXMLSerializer namespace changes
> yet, but I'm sure Greg will be able to help you out.
>
> Chris
>
> On 19 September 2010 03:41, Mark Miller <[email protected]
> <mailto:[email protected]>> wrote:
>
> On 9/18/10 1:17 PM, Greg Brown wrote:
>> Since you are just starting development, I was actually going to
>> suggest that you consider using 2.0 for your app. It hasn't been
>> released yet, but the feature set is pretty stable at this point,
>> and there are quite a few enhancements that you may want to take
>> advantage of.
>
> So I've gone for this - and I jumped into a little more than I
> expected :)
>
> I've worked out most of the upgrade pains, but I'm stuck on one now
> -
>
> I was importing a dialogue wtkx file into a main wtkx file. To
> access the components in the dialogue box window, I used:
>
> wtkxSerializer.get("dialogueId.componentId").
>
> What's the best way to do this with 2.0? Now its a namespace map, and
> so this syntax doesn't work.
>
> I tried getting the dialogueId from the namespace map, and using
> getNamedComponent - but I was getting back null.
>
> Am I on the right track?
>
> - Mark
>
>
