bitweaver
Wiki
wiki Home
List Pages
wiki Books
Orphan Pages
wiki Rankings
Photos
List Galleries
Forums
Browse forums
Files
List Galleries
Categories
List Categories
Sign In
Message Boards
»
05. Support - Themes and layout
Newest
Oldest
Threaded
5
10
20
50
100
All
Messages
Death to phpnuke columns
Post Reply
Arnaud HERVE
Joined: 25 Oct 2004
Death to phpnuke columns
Posted:28 Sep 2006 (13:35 UTC)
laetzer
Joined: 15 Mar 2004
Posted:29 Sep 2006 (08:52 UTC)
Arnaud HERVE
Joined: 25 Oct 2004
Posted:29 Sep 2006 (11:10 UTC)
lugie
Joined: 12 Jan 2006
Posted:04 Oct 2006 (02:51 UTC)
dspt
Joined: 10 Jan 2006
Posted:04 Oct 2006 (14:52 UTC)
Post Reply
Page 1 of 1
1
Post
Title
Login
If you are already registered, please enter your login credentials.
Your Name
Anonymous Post
Content Format
Tiki Wiki Syntax
Allow HTML
{quote format_guid="bbcode" comment_id="8099" user="dspt"}I advocated liquid designs before I saw them on wide screens and high resolutions. from the usability point the narrow newspaper-like columns of text are easier read (eye-scanned) and percepted on the screen then the wide ones. So now I stick to semi-liquid designs, with min and max width of the content area enforced the whole wrapping issue in CMS is rather complex, as it involves need for sustainable design in the situations with different columns longest. On static pages, referenced by topicstarter as "plain html created by novices", the structure of the page and the length of the columns is "given", while in CMS-generated page it's not constant. Designing for CMS means fitting random data into single design-frame which is a far more demanding task then designing for static content. So the "early" CMS (like the php-nuke) temlates *might* be considered as a step back in a design, but as a first responce to the more difficult goal. And we should remember, that php-nuke and alike "early" CMSes are totally table-driven, not CSS-driven. This "early" CMSes had set some design patterns, that are sometimes copied without thinking into CSS-driven templates. Anyway, "modern" CSS-driven (and sometimes even AJAX-driven) CMS design templates can wrap your content around modules and do whatever else. So I believe the issue we are discussing is *already* taken into account. Consider Bitweaver as such example.{/quote}
Recent Page Changes
welcome to bitweaver.org
Bitweaver Overview
ReleaseTwo Schema Changelog 2006
PressReleaseOne
Spider's Web
Press Release Two
BitcommercePackage
InfiniBand vs Ethernet Performance
InfiniBand for Dummies
Show More…