[dev] Remove multi-column portal blocks?

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> A reason could be, at least for me, that German tends to have much
>> longer words than English. If I would have to put the weather block in
>> one column, I probably wouldn't get more than two columns in the
>> portal, currently I get three. Now, *that* is wasted space (for all
>> the other blocks), at least for me personally.
>
> Fair enough.

I played around with it a bit, and I guess the block could fit into  
one column, maybe with tweaking the layout a bit. But the comic block  
is much more a problem.

>> I thought about that earlier a few times, and my thoughts always got
>> stuck in that dilemma. I think the possibility to expand and shrink
>> blocks is what it makes Horde's portal superiour to others. You can
>> create much more flexible layouts. On the other hand, having
>> maintained the portal block code a few times in the past, I know what
>> a pita the code is. And it's definately not the most user friendly
>> interface either.
>
> What if we were to split the code into the current layout - a
> GridLayoutManager - and add a new driver, a ColumnLayoutManager? The
> disadvantage is that then we have two layouts to maintain, and it
> doesn't simplify anything. The advantage is that we can have the
> drag-n-drop for columns without sacrificing the possibility to use the
> current grid. And this sort of layout managing code could very easily
> be used to replace the current layout code in Giapeto or other
> CMS-like solutions.

This sounds like too much duplicate work. We really don't have the man  
power to maintain two variants of such complex code like the portal  
layout. We should agree on one solution, even if it doesn't fit  
everybody's needs. I like the drag and drop portals a lot, and if we  
find a solution for the comic strip, I'm all for it.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/