> > > > Vanilla sao won't be responsive because the GTK client is not > responsive. >
If you follow this line of thought, GTK client doesn't work on iOS, then sao should not work on iOS either? > But I guess that splitting the stylesheet in two parts, one > implementing the default behavior ; another one implemeting the > responsive stuffs is possible, isn't it? > Not with the current view.js since it produces <table>'s (which is probably very fine for tree views, but not for form views concerning the current matter). Hence this poc to replace form.container element with <div>. Now of course, out of the box div's won't look like the gtk client's forms, they need to be applied a grid system. I guess you could dev your own grid system to prevent it to be responsive, but that would probably be a lot of work. Or you could use an existing grid system (like bootstrap or something else) but then... well, it would be responsive out of the box Adding extra javascript to replace the tables by div's would not be a viable solution to me either since it would increase the cpu usage even more which was one of my 2 concerns when opening this thread. > If so then people that want this behavior will have the opportunity to > modify index.html in order to "import" this part of the stylesheet > (just like NaNtic does in order to customize the look of sao). > A separate index.html is fine, esay to manage (index.html is pretty thin), now in this case it would involve a separate view.js also which would be a lot harder to maintain (re-apply patch on every release if lucky or rewrite for every release). This is why I said I would only keep on this if I received tryton's (or at least sao's) dev team approval support. > >
