#4117 closed task (fixed)
BorderLayout: implement
Reported by: | bill | Owned by: | Adam Peller |
---|---|---|---|
Priority: | high | Milestone: | 1.1 |
Component: | Dijit | Version: | 0.9 |
Keywords: | bordercontainer | Cc: | |
Blocked By: | Blocking: |
Description
Implement BorderLayout? widget (similar to EXT's BorderLayout? or Swing's BorderLayout? class), with markup like LayoutContainer? but only allowing five children (north, south, east, west, center), and having [optional] sliders between them.
If we get this working then can deprecate SplitContainer? and LayoutContainer?.
Change History (38)
comment:1 Changed 12 years ago by
Owner: | set to Adam Peller |
---|
comment:2 Changed 12 years ago by
Priority: | normal → high |
---|
comment:3 Changed 12 years ago by
Status: | new → assigned |
---|
comment:4 Changed 12 years ago by
comment:5 Changed 12 years ago by
comment:7 Changed 12 years ago by
(In [11622]) First stab at splitters for dojox.layout.BorderContainer?. Refs #4117, #4374
comment:8 follow-up: 9 Changed 12 years ago by
can you replace splitcontainer with borderlayout even if you implement splitter for it? a splitter can contain more than 2 panes, but if we are using borderlayout, you can only have up to 5 children (in fact, if you want to have a splitter, only 3 out of 5 can be used, depending on the orientation of the splitter)
so I don't think we can replace splitcontainer with this, or am I missing something?
comment:9 Changed 12 years ago by
Replying to liucougar:
can you replace splitcontainer with borderlayout even if you implement splitter for it? a splitter can contain more than 2 panes, but if we are using borderlayout, you can only have up to 5 children (in fact, if you want to have a splitter, only 3 out of 5 can be used, depending on the orientation of the splitter)
Right... so first off, this would be a new class, not an API-compatible replacement for either BorderLayout? or SplitContainer?. It would not handle more than three panels / two splitters in a row, nor would it handle the case where you want to distribute space equally, though you could approximate either of these with the right measurements or nesting of controls. I think we'll either need a Row/ColumnLayout? set of widgets, or perhaps we can find a way to make the splitter generic enough that you can just layer it on any panel?
But don't think 3 or less is the common case and that this will be "good enough" for now?
comment:10 Changed 12 years ago by
comment:11 Changed 12 years ago by
Keywords: | bordercontainer added |
---|
comment:12 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [12153]) merge newlayout branch [11995] through [12150]. Includes new BorderContainer? and updated tests, themeTester, and mail demo. Fixes #4117
comment:13 Changed 12 years ago by
(In [12154]) Create quirk version of themeTester. Try out percentages for BorderContainer? panel dimensions. Refs #4117
comment:14 Changed 12 years ago by
comment:15 Changed 12 years ago by
comment:16 Changed 12 years ago by
comment:19 Changed 12 years ago by
comment:21 Changed 12 years ago by
(In [12300]) Forgot to remove old dojox.layout.BorderContainer? code. Refs #4117
comment:22 Changed 12 years ago by
(In [12301]) Forgot to remove old dojox.layout.BorderContainer? code. Refs #4117
comment:23 Changed 12 years ago by
comment:24 Changed 12 years ago by
comment:25 Changed 12 years ago by
comment:26 Changed 12 years ago by
comment:27 Changed 12 years ago by
comment:29 Changed 12 years ago by
comment:30 Changed 12 years ago by
comment:31 Changed 12 years ago by
comment:32 Changed 12 years ago by
comment:33 Changed 12 years ago by
(In [12496]) recompute bounds for splitters when parent BorderContainer? changes size. Refs #4117 !strict
comment:34 Changed 12 years ago by
comment:35 Changed 12 years ago by
comment:36 Changed 12 years ago by
(In [12602]) break out var block so ShrinkSafe? can have at it. Refs #4117
(In [10678]) Initial drop of BorderContainer?. Putting in dojox as experimental, for now. Refs #4117