Issue 107486

Summary: UNO AWT based tree-Control -> Base form tree-control
Product: Base Reporter: denis0 <denis0.ru>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOO310m19   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description denis0 2009-12-07 09:59:11 UTC
We are very need a OOo Base control to access to hierarchical data (like
site-tree, file-tree, categories hierarchy, etc). 

UNO AWT based tree-Control can be added only in dialog, not in form. And it
require a lot of code to connect to data source. This is not decision for everyone.

That`s could be fine: select tree control from panel, put it in form, select
source_name, id, parent_id and title on control`s "properties"-"data source"
page and just use the result.

Some conventions can make an interface easier. For example: 
first field: title, second field: id, fird field: parent_id

Then we`ll need only table name in tree-control settings.

P.S. sorry for my broken english :-/
Comment 1 bigandy 2009-12-07 11:56:34 UTC
I need too
it is too worthless to obtain hierarchies from common controls
Comment 2 marc.neumann 2009-12-08 09:40:10 UTC
reassign to the requirements team
Comment 3 chrysten 2010-03-30 03:09:26 UTC
while it is a noble idea - the complexity of the properties interface for a tree
control is different than almost all other form controls. for example, one can
not simply assign a data source and depend upon field index conventions. why? in
truth, each >level< of a tree control needs a datasource/result set to use as a
feed. in addition, each level needs master-child relationship (keys/links
whatever your favourite terminology) between itself and the parent level and
between itself and the child level.  it might be helpful to think of the data
model of a tree as a set of nested subforms.
Comment 4 denis0 2010-09-17 13:28:33 UTC
Dear, chrysten

I think it`s quiet simply. 

1) Basic table of whole tree = just a list!

2) UNO AWT based tree-Control should use this list and transform it into tree
object. And visualing it too.

3) Parent, siblings, childs, status of record (hide|unhide) has this control.
But you need only curent selected record to use it with subforms and other controls.

Optimization is the second step. After alpha realise.

>it might be helpful to think of the data model of a tree as a set of nested
subforms.
It`s a wrong way, imho. It`s just special dropdown list.