Hi,

I did the same GridTree but with the Flash Components V2 and now I would like 
port my 
app to Flex. But I use another way, I put the datagrid immediately at the right 
side of the 
tree. This work fine and I think is a more ease solution, because your base is 
the tree and 
not the datagrid, then you can manage more ease the xml data and don't need to 
deal with 
itemrenderer in the datagrid, only the checkboxes in the tree.

Now, I'm really newbie with Flex and I can't get the length of the only visible 
items in the 
tree :(

Really stupid, but this is my first time with flex, I can't see nothing in the 
Tree and XML 
classes.

thanks in advance

Rafael



--- In flexcoders@yahoogroups.com, "jeremy lu" <[EMAIL PROTECTED]> wrote:
>
> well, just flip thru my gridtree component (http://tinyurl.com/grcfs)
> developed two months ago (which is still in a mess), it's around 2000 lines
> of code (after refactoring it three times) and lot of algorithm behind to
> handle following function:
> 
> addNode
> removeNode
> cutNode
> copyNode
> pasteNode
> indent/outdent code
> 
> I think the first methods Anatole mentioned will definitely be a b***h to
> tackel with, for the nature of List-based component is a little bit tricky
> then it looks (all the list items are dynamically generated and draw on the
> screen, this will cause some trouble)
> 
> I'm currently implementing gridtree using item renderer for the first
> column, it's pretty much the same work to extends gridbase and "inject" the
> tree grid code into it so the API would be more compatible, by using this
> method I could easily feed a non-xml structure (ie:resultset from java/php)
> to the component and let it draw the hierarchy and set indent/outdent of
> each node.
> 
> now I'm thinking maybe I should draw those lines and plus sign instead of a
> simple arrowhead, so it's more like VS2005  :-)
> 
> FYI, the component took a whole weekend for prototyping  and
> concept-proofing, *but*, it took almost one and a half month for debugging
> and refactoring to stablize the code and become really usable in the
> on-going product/project.
> 
> originally I want to open-source the component but later on this become one
> of my assigned  day-job project (so I can fulltime developing it with the
> approval of my employer), but anyway, I would love to answer any related
> questions.
> 
> jeremy.
> 
> 
> On 4/23/06, Anatole Tartakovsky <[EMAIL PROTECTED]> wrote:
> >
> > Depends on your requirements:
> > For generic case it is 3 step process:
> > 1. Wait for beta 3 that supposely comes with the source code.
> > 2. Study the code for data grid header, treeview, datagrid, etc
> > 3. Write your own code for the control inherited on the top of BaseGrid,
> > with automatic wrapper for the first column - 1500-2000 lines in total to
> > support generic case
> >
> > For quick and dirty :
> > Create first column as cell renderer. I believe I posted code in this
> > group for Flex 1.5 tree cell renderer that allowed to add nodes lines to
> > the regular tree - you just paint it within item - still about 200 lines of
> > code for core functionality, another 100 lines for cascade retrieve/grouped
> > sort on the header clicks, 2-3 days of work altogether
> >
> > Have not seen anything in the public domain, just few developed "for hire"
> > in consulting gigs.
> >
> > HTH,
> > Anatole
> >
>






--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/flexcoders/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to