|
| |
User Groups : Forums : SiteExperts :
Dynamic HTML
:  |  Column-spanning Portlets?
I didn't expect that I wasn't able to Google this up quickly.
Has anyone ever seen portlets that can have some of the portlets span across columns ?
Here's to visualize the behavior I'm trying to describe.
| | |
Portlet C BEFORE: Drag this to the top | | | | Portlet C AFTER: Dropping it here | | | | | | |
Of course, I don't expect a flat-out source-code-attached solution from here. I'm just asking for some pointers or links to whether or not this has been done and witnessed.
I'm fine with both flavors of vanilla JavaScript or jQuery.
I might start this thing from scratch, or base it on some library, but it would be most assuring if I could know beforehand that this has been done and not just a proof of concept.
Most portlets I see out there have a DIV structure where the top-most level of DIV behaves as columns. While on the other hand, what I initially have in mind is the top-most level of DIV that are just plain rows, and within each rows is a second level of column DIVs. Yet, in a row that has a spanning portlet, there would be no column DIVs, hence, the portlet spans to the fullest width. I'm not even sure if existing libraries could handle such a structure.Started By Terry Young on Jun 11, 2009 at 9:38:51 AM
This message has been edited. | | | 7 Response(s) | Reply |
Earlier Replies | Replies 6 to 7 of 7 | Later Replies
Goto Page: 1 | | bod1467 on Jun 12, 2009 at 1:00:35 AM (# 6)
This message has been edited.That's somewhat like iGoogle, but I don't think they have column-spanning portlets. (At least, not what I've seen).
What about using TABLES with colspan and rowspan? ;-)
/gets coat
Terry Young on Jun 17, 2009 at 9:39:36 AM (# 7)To think of it, a TABLE (as a master container for portlets) does sound better, doesn't it?
I mean, when the user drags and move it before or after another "row" (not yet dropped), I would just need to use insertRow and assign the cells height (to visibly indicate the drop target), and all the other rows below would simply shift as is, because of the inserted row. If such a table container is absent, I would then have to deal with all other DIV's positioning (I think...).
I would just need colspan, and no need for rowspan.
Each row would either have two cells, or just one cell with colspan="2". No two same type of rows would follow one after another (i.e. always alternate rows). This also means that any cell can have one or more portlets of the same type.
And only 50% width-ed portlets would be able to be dragged left/right/up/down, and these portlets are free-flow within the left/right cell. 100% width-ed portlets would only be able to be dragged up/down. Hence the need for colspan only.
It does sound feasible (and easier) this way.
Now, if only I had the extra spare time to make this toy... or the spare time to research jQuery to see if jQuery UI's draggable/droppable is already capable of this...
| Earlier Replies | Replies 6 to 7 of 7 | Later Replies
Goto Page: 1 |
To respond to a discussion, you must first logon.
If you are not registered, please register yourself to become a member of the SiteExperts.community.
|
