[izpack-devel] TreePacksPanel

[Vladimir Ralev]

Yes, it's missing one </pack>. I am sorry. I am not nesting the packs. I 
was thinking about nesting, but keeping them linear allows easier 
migration and compatibility with the flat PacksPanels. It's worth 
reconsidering, but it needs more planning. The parent attrbitue was also 
easier to implement.

Scott Plante написа:
> Hi,
>
>   Sorry for the late reply--I just got back. I see it's all checked in
> now. It looks really great. One thing that occurred to me is: Wouldn't
> it be more natural to nest the pack elements to model the hierarchy,
> rather than use the parent tag? Perhaps you are nesting the pack
> elements--your example seems to be missing one </pack> unless I'm losing
> my mind. If you *are* nesting your pack elements, what's the purpose of
> the parent element?
>
> e.g.
>   <pack name="Seam" id="Seam"
>          installGroups="default"
>          group="Core"
>          required="no">
>       <description></description>
>       <pack name="Documentation" id="seam-docs"
>              installGroups="default"
>              group="Core"
>              required="no" parent="Seam">
>           <description></description>
>       </pack>   
>       <pack name="Samples" id="seam-samples"
>              installGroups="default"
>              group="Core"
>              required="no" parent="Seam">
>           <description></description>
>       </pack>   
>       <pack name="Seam generator" id="seam-gen"
>              installGroups="default"
>              group="Core"
>              required="no" parent="Seam">
>           <description></description>
>       </pack>
>   </pack>
>
> Is it just so you can switch back to the flat (normal) packs panel
> without changing the xml file?
>
> Scott
>
> Vladimir Ralev wrote:
>   
>> Hi guys,
>>
>> I am working on a hierarchical pack selection panel. I am not
>> committing it to the official repo since i'd like to get some feedback
>> first.
>>
>> So, here is a sample root node declaration:
>>      <pack name="Seam" id="Seam"
>>          installGroups="default"
>>          group="Core"
>>          required="no">
>>      <description></description>
>>      <pack name="Documentation" id="seam-docs"
>>          installGroups="default"
>>          group="Core"
>>          required="no" parent="Seam">
>>      <description></description>
>>    </pack>    <pack name="Samples" id="seam-samples"
>>          installGroups="default"
>>          group="Core"
>>          required="no" parent="Seam">
>>      <description></description>
>>    </pack>    <pack name="Seam generator" id="seam-gen"
>>          installGroups="default"
>>          group="Core"
>>          required="no" parent="Seam">
>>      <description></description>
>>    </pack>
>> Note the parent attribute of the packs, which specifies the parent
>> node. If it's null the node is top-level. It works perfectly fine with
>> flat pack structures (no tree). I am attaching a screenshot. You can
>> see a fully selected node and a partially selected node, the
>> dependency logic is the same as the normal packs panel, in fact if
>> uses the flat PacksModel to resolve dependencies (with rules and
>> everything). The click logic is correct - when all childs are
>> deselected the parent is deselected too and vice versa. I am trying to
>> find some nice way to show the pack size of each pack in the tree
>> (like the flat packs panel) and i have to wire some more model values.
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> izpack-devel mailing list
>> izpack-devel at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/izpack-devel
>>   
>>     
>
>