> Michael wrote: "If you want to use the TaskFrame as the place to dock > everything, I > think every TaskFrameProxy will become a dockable of your TaskFrame, and > you'll have to find another name for what is actually called a TaskFrame > (ie a frame containing a LayerView, a LayerNamePanel...), and, if > possible, consider there may be several of those components in your main > TaskFrame" > > I'm not sure if I quite understand this. I do want the TaskFrame to be > the parent window in the docking window tree. It will contain all of > the other windows related to the task. Right now, a lot of these > windows are added as internal frames. I don't know that I need to > change the name of the TaskFrame class. It will still be an internal > frame used to display a LayerViewPanel and a LayerNamePanel. > You're right, you don't need. I was talking about a component inside your TaskFrame and made of a LayerViewPanel + a LayerNamePanel (what the actual TaskFrame is). But you don't need that. You can consider that your TaskFrame is directly composed of one (or several) LayerViewPanel, a LayerNamePanel, one or several ViewAttributeFrames... Hope it makes more sense.
Michaël ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
