Hi,

   I'm able to reproduce the vector legend issue in a standard tree.  I 
modified the examples/tree/tree-legend.js in the following branch.  You 
can clone locally to test.
     https://github.com/adube/geoext2/tree/legendissues

   If anyone has any clue/hint...

Thanks,

Alexandre


On 12-08-07 01:39 PM, Alexandre Dubé wrote:
> Hi devs,
>
>     I've been working on the LayerTreeBuilder ux in the last couple
> days.  Here's the branch containing the code I have so far, plus an
> example :
>     https://github.com/adube/geoext2/tree/layertreebuilder
>
>     It requires more work to support everything its GeoExt 1 counterpart
> does.  In summary, I have issues with the LayerLegend components and
> migrating what I had that managed the checkboxes didn't work.
>
>     The rest is trivial and easy to do: tests, code comments, etc. I'll
> try to play around with the legend component issue a bit more to see if
> I can find what's causing it.
>
>     From the repository root directory, the example is located here :
>      examples/tree/tree-builder.html
>
>     Comments and hints about the issues would be really nice.
>
> Regards,
>
> Alexandre
>
>
> === More details ===
>
> +++ LayerLegend(s) issues +++
> The WmsLegend containers sometime show their content and sometime they
> don't.  For example, when expanding a container node, even if the layer
> isn't checked its legend can be displayed.  The opposite occurs
> sometimes too.  The VectorLegend containers never show their contents.
> When spying the dom, I can see the elements there, but they're not
> visible in the tree. Both these issues are demonstrated in the example.
>
> +++ No checkboxes for containers +++
> The containers currently don't have checkboxes at all. The code I used
> to support that in the GeoExt 1 version was borrowed from the MapFish
> layertree widget.  It managed the state of parent and children
> checkboxes when one was checked, as a 'tri state' checkbox tree would
> do.  It worked well with Ext3, not with Ext4. As of now, I left no trace
> of that code.  Ext4 had its tree components changed, so it would be
> better to redo that part entirely.  In my knowledge, trees don't support
> 'tri state' checkboxes in Ext4 yet, so I'm not sure what would be the
> best thing to do.
>
>
>
> On 12-07-29 05:33 PM, Phil Scadden wrote:
>> On 28/07/2012 6:21 a.m., Alexandre Dubé wrote:
>>>       I'd like to start a discussion regarding the UX for GeoExt2 as I
>>> would like to work on the unofficial GeoExt.ux.LayerTreeBuilder (still
>>> in a sandbox, only) for GeoExt2.
>> Alexandre - converting your ux on this is the only thing standing
>> between us mhttps://github.com/adube/geoext2/tree/layertreebuilderoving to 
>> geoext2! I am delighted you are working on it. I
>> was starting to looking resources on migrating it. Got a list of
>> suggestions on improvement too once that is done :-) ! I think this
>> extension is just fantastic - the main reason to use Geoext.
>>
>>
>> Notice: This email and any attachments are confidential. If received in 
>> error please destroy and immediately notify us. Do not copy or disclose the 
>> contents.
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://www.geoext.org/cgi-bin/mailman/listinfo/dev
>


-- 
Alexandre Dubé
Mapgears
www.mapgears.com

_______________________________________________
Dev mailing list
[email protected]
http://www.geoext.org/cgi-bin/mailman/listinfo/dev

Reply via email to