Re: <div>s based layout -- HTML 4.01 Strict

[Sameer Naik]

On Thursday 01 November 2007 1:10:45 pm Antenore Gatta wrote:
> On 11/1/07, Davi Leal <address@hidden> wrote:
> >
> > Antenore Gatta wrote:
> > > 1. Layout migration section by section.
> > >
> > > Identifying the sections and pages that will most benefit from the
> > > conversion will simplify the whole work.
> >
> > All the pages share the 'main' <table>s layout.
> >
> > > I think that as a good start we should focus our attention to the
> > content,
> > > fixing headings and paragraphs, removing <br> and <b> (search for <b>ad
> > and
> > > <br>eakfast ;-) , replacing where possible tables with div/lists,
> > paddings
> > > and margins.
> > > Cleaning the base html tags styles.
> >
> > Before uploading a modification to production we should check that
> > removing
> > <br>s, etc. do not break the look&feel.
> 
> 
> I agree, but it's absolutely important to don't deploy a completely restyled
> layout, follow my comments below.
> 
> I agree with you that smalls steps should be done when it is possible.
> 
> 
> Ok, we agree ;-)
> 
> Removing the use of <table>s at the heading, menu, and log-in box can be one
> > of such steps.  IMHO, experimenting just on a "Save as" copy of the HTML
> > code
> > of the home page is a good way to carry out this 'step'.
> >
> > When all be right on such 'experiment', we will be able to modify the
> > below
> > files, which are used to build all the pages. Inside such files is coded
> > the 'main' webapp layout:
> >
> >   Layer-0__Site_entry_point/templates/web_page.tpl
> >   Layer-0__Site_entry_point/templates/header.tpl
> >   Layer-0__Site_entry_point/templates/menu.tpl
> >   Layer-0__Site_entry_point/templates/log_out_box.tpl
> >   Layer-0__Site_entry_point/templates/log_in_box.tpl
> >   Layer-0__Site_entry_point/templates/content.tpl
> >
> > All the pages share such 'main' <table>s layout.
> >
> > P.S.: As a start, it is OK we send to this email list the work done on
> > the "Save as" copy of the HTML code. It is not needed modify the above
> > files.
> > That can be done later.
> 
> 
> I'm not completely agree, I'm thinking to a compromise.
> 
> 1. Save as HTML
> 2. Cleaning where possible the actual layout.
> 3. As soon as we will satisfy,
> 4. apply changes to templates

i developing the same layout from scratch. eliminates all the confusion.
the design is very modular and really simple to understand. i believe there 
would be no issues in integrating it with the backend.

i would soon be hosting it at my webserver,  so that you guys could check the 
progress of my work and maybe report bugs.
once  the first draft is complete and accepted we could move it into the 
project, integrate and work on enhancements.

> 
> again
> 
> 1. Save as HTML
> 2. from <table>s to <div>s layout
> 3. ...
> 4. ...
> 
> And again with the design and so on
> 
> 
> About the 'content' area of the pages, some have just <p> tags [1], others
> > have even nested <table>s [2].
> >
> >   [1] Layer-0__Site_entry_point/templates/FS_Business_Networks_content.tpl
> >   [2] Layer-0__Site_entry_point/templates/Qualifications_skills_form.tpl
> >
> >
> > I thought it would be good idea do not replace the content-area <table>s
> > which
> > are used to align form fields, because of I think we can not get the same
> > form layout using <div>s and CSS!  We can not get all cells right aligned,
> > as
> > it is for example at the JobOffer view? Isn't it?
> 
> 
> If not possible we can still use tables if we need to.
> In this case I think that will be possible.
> 
> I'm going to check and I'll give you a proper answer
> 
> > 2. Logical divisions of content.
> > >
> > > This should the second logical step. We should identify our pages for
> > > logical divisions of content.
> > > I mean something like:
> > >
> > >    - Main menu
> > >    - Login/registration menu
> > >    - Option/languages menu
> > >    - Headers and footers
> > >    - Content
> > >    - Related information
> > >    - Others...
> > >
> > > And start to replace these with divs and lists (ul) where possible
> > and/or
> > > fixing existing tables.
> >
> > IMHO the current webapp use already a more or less logical division. Note
> > the
> > files listed above. Anyway, maybe there is room to improvement. However
> > IMHO
> > the main problem is the HTML and CSS which is used at the already
> > identified
> > logical divisions, not the logical divisions theyself.
> 
> 
> Mine was not a critic about the current division, I think that the
> login/registration menu and the lang menu would be improved.
> 
> > 3. Look and feel.
> > >
> > > When the content will be more organized and clean we can start to think
> > > about the look.
> > >
> > >    - Colors.
> > >    - Header style.
> > >    - Menus positioning.
> > >    - and so on...
> >
> > Experimenting is always good! If we found something which we think
> > improves
> > the webapp we should use it.
> >
> > I like the current 'clean' menu and languages control positioning. But if
> > it
> > can be improved, better!  Obviously, we should not upload to production a
> > change which shows the webapp in a worse state.
> >
> 
> Always agree with you about deployment...
> 
> I think that the language menu it's not the best solution because:
> 
> - With <div> layout we can keep it on the right, but whit font resizing its
> position will change.
> - If you have a great number of languages the layout will be broken.
> 
> IMHO would be better to have a combo box or a menu with hidden elements
> (using css).
> 
> I just want to highlight the fact that mine was not a critic about the
> current layout!!! :-)
>