> > I think there were several people interested in this in last TUB and > you can expect some help from NaN·tic. Not right now, but hopefully in > the near future, so for us a codereview would be great.
OK, I'll set up a codereview tomorow. I am a bit of a novice in the use of these frameworks as well, but I have > had a chance to play with both bootstrap and Foundation 5. So far I prefer > Foundation to bootstrap as it is a bit more "lightweight" and was optimized > for mobile-first (though it works quite well on responsive websites in > general). I used bootstrapfor this poc but there might be other better solutions. I guess though that css frameworks can be easily interverted once the generated HTML generates <div>'s instead of <table>'s Also, in the provided patch, I made direct use of bootstrap classes. If there is further develoment on this i guess it would be better to use new classes which would be defined using mixins, thus making css framework abstraction easier. And btw, bootstrap3 is "mobile first" too. using bootstrap could be a > step in the right direction even if we eventually see it is better to > have a sao-lite version, because both sao and sao-lite would share > most of the framework. I can't say I disagree with the "sao-lite" approach but sao has not even been released yet, so maybe it would be better to stick to one web-app for now and try to make it responsive the way it is before thinking about writing another version of it. Firstly screen resolution is not a reliable way to determine the nature of > a device on its own; my mobile has only as 12cm screen but the resolution > is full HD (1920x1080) and so you would have to query for other information > (pixel density, physical size...). Well, screen resolution is a start, I know there are ways to get all those other infos but I've never done it before, so I'll have to look into it
