Re: [Issue 14] (52) Get away from "table layout"

There is also a dev list: dev-64ivf2F2CKgWBrYXtHbyVwRtnQ8X5fEL@xxxxxxxxxxxxxxxx You need to be subscribed to it to be able to post.

Kenneth Wong wrote:

Er... if that's the "user" mailing list, then yep, I'm there too.  I'll make my next post over there when I've begun some of my tests into building a CSS oriented layout...

Ken.

On 7/28/05, Paul Hanchett <paul.hanchett-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:

Ken,

Are you  subscribed to the dev list?  That would be a better place to continue this discussion...

Paul

Kenneth Wong wrote:

There's definitely a lot of work involved but I think it's well worth
the effort.  And to top it off, I wouldn't mind taking a stab at it.
:)  Here were my initial thoughts...

I'm wondering whether or not we can reduce the number of template

files by using the <div> tags.  The <div> tags would be used to
logically seperate page elements much like how the template files are
being used right now.

Plug-ins would be responsible for spitting out HTML code surrounded by

a div tag with a specific ID.  The Layout of all the <div> tags would
be handled via a variety of CSS files (one for each different layout
on the website).

I think my plan of attack would be:
(1) Generate a layout via CSS with a menu down the left hand side,

main content on the right, a header and a footer.
(2) Modify the templates that control the header, menu, and footer to use CSS.

I should be able to do that without modifying any of the core PHP code
that makes up co-wiki.  If that works out alright, then I may try

tackling a couple of plugins.

With any luck, I'll be able to come up with some benchmarks in terms
of performance changes.

Any chance I can take a look at your work with cowiki/css? :)

Ken.

oh, and I'm *not* a CSS Guru... just a guy with some knowledge and a
hankering to try to use some of it. :)

On 7/28/05, Paul Hanchett 
<paul.hanchett-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
  

I've been looking at this.  The biggest problem I see is that there is a
*lot* of stuff to convert.  Generally speaking, all of our formatting is
done with the template files in the TPL directory.  Plugins should *not*

be generating their own HTML except by using a template themselves.

I have a start of coWiki using CSS.  It's rather a pleasure to work with
because the HTML is simpler but I'm not yet enough of a CSS guru to lay

stuff out without constantly rechecking my work.  :-)

Paul

lostwong-jqHnx1hy4Dsdnm+yROfE0A@xxxxxxxxxxxxxxxx wrote:


    

http://cowiki.tigris.org/issues/show_bug.cgi?id=14







------- Additional comments from lostwong-jqHnx1hy4Dsdnm+yROfE0A@xxxxxxxxxxxxxxxx Thu Jul 28 09:25:08 -0700 2005 -------
Some possible benefits of using CSS:


- graceful fallback to non-compliant/older-generation browsers
- should be easier to mantain cross-platform support
- possibly faster load times due to less code in the html and more of it in a
shared CSS stylesheet

- make it easier to create third party themes/templates for the wiki

I've noticed that there's html formatting code throughout a lot of the plugins
and   templates.  To make a fully themable system may require some re-working of

how the templates and plugins are structured and how they interact.



      

>