On Wed, 2014-03-05 at 16:03 +0100, Sergi Almacellas Abellana wrote:>
> > > intended and the interface renders on larger screens as it renders on > > the gtk client AND renders on smaller screens as it does in pda mode, > For me this is the objective :P > > the codereview replacing tables by div's would be included in sao > I will prefer div's (as are better customizable by ccs) but don't mind > if it's done by tables and it works. > > Ultimately any and all markup can be manipulated by CSS equally well. The difference in terms of CSS for table vs. div vs. dl/dt etc. are default behaviours. Since div elements are generic blocks the default behaviour is minimal but you can always force any element to be the same kind of block if you really wanted to. My preference is to go with what is the most "semantically correct", so if you are working with a tabular view of data then use tables. If you are working with tree view use lists. I put navigation in a nav element. Top of a form would be a header, bottom of a form would be footer. If you have a form with sections/tabs use section. I try to relegate div to just what doesn't have a standard tag that makes sense. It is still my opinion that there should be separate "sao" and "sao-lite" that can be independently called depending on what the user wants. auto-detect is poor practice in my opinion because it is never 100% right (I have a tablet that I would prefer to see full view but often get punted to mobile view, and the odd website on my phone with a 12cm full HD screen goes to full view when I'd rather have mobile because a few sites just check resolution). Again, responsive doesn't just mean mobile--there is an audience for a reduced-function client on the desktop that is not a GTK-Tryton work-alike nearly as much as there is a demand for a web clone of the Tryton GTK client.
