| 1 |
Michael Curtis Napier wrote: |
| 2 |
|
| 3 |
>However, the layout was voted on and chosen in advance of |
| 4 |
>the markup creation. |
| 5 |
> |
| 6 |
Yes of cource the voted design should be mimiced as close as possible, |
| 7 |
not suggesting we shouldn't :) |
| 8 |
I often have a graphical conceptimage as target too, but such images are |
| 9 |
static and usually only provided in "1 resolution" so getting good |
| 10 |
behaviour across different res & fontprefs is still something that is |
| 11 |
mostly left to the markup coder. |
| 12 |
|
| 13 |
>Once I get a testing backend up and running we can start actual work on |
| 14 |
>the templates and finalize the layout. For now we need to concentrate |
| 15 |
>on a *general* layout so we have something to follow. |
| 16 |
> |
| 17 |
> |
| 18 |
Understood, still we are discussing quite detiled things eg like exactly |
| 19 |
how code sections should look like on the news listing. It makes a lot |
| 20 |
of difference for what things you can suggest (& even implement in the |
| 21 |
mockup site) if you are eg locked into an underlying TABLE-structure vs |
| 22 |
if you have the full bag of tricks of true liquid CSS layout to play with. |
| 23 |
|
| 24 |
So whatever way you look at it, the underlying markup itself plays a |
| 25 |
major role for layout and IMO it's thus not desiarable to compleatly |
| 26 |
eliminate discussing markup at the same time as layout. In fact it might |
| 27 |
be outright detimental to the final resoult to compleatly ignore markup |
| 28 |
even at this early stage. |
| 29 |
|
| 30 |
Anyway, this is just my opionion based on my personal experiences, so |
| 31 |
feel free to ignore me :) |
| 32 |
|
| 33 |
Regards / SH |
| 34 |
-- |
| 35 |
www-redesign@g.o mailing list |
Archives