Hi Martin, I'm glad you like it. I was just discussing this with Markus who requested the narrower fixed layout, so I don't want to write it again, so here is the conversation. About the examples, we can add horizontal scroll bar, example is here: http://fatra.cnr.ncsu.edu/temporal-grass-workshop/#time-series-registration-and-visualization
On Tue, Sep 23, 2014 at 2:18 PM, Vaclav Petras <[email protected]> wrote: > ...He wishes back the large screen support... > > > This is why originally I did not included this style to the new CSS (CSS > for workshop). The problem is that we don't know what is the right > solution. You were using the term large screen support for div with fixed > size to not spread over the whole screen, now you are saying that large > screen support is to actually use the screen width. > > The other problem is that the layout is not small enough in small windows, > I for example use website one left half (or <1/2) of the screen and working > on the other. I hit this issue no latter then on the workshop. > > >> especially since the >> landing page with the overview needs to be scrolled now (see >> screenshot). >> >> The overview is of course special and it is the biggest problem and we > really cannot, or don't want, to have different layout/style/header for the > special pages. Here the situation might be improved by reducing the intro > text to one sentence and a More... link which would go to the bottom where > would be a full intro. Perhaps we should do this in any case. > > >> To make everybody happy, I wonder if there is a way to make the layout >> width limitation somehow switchable (essentially: div container on and >> off)? >> >> This is quite challenging. You need JavaScript for this which we are not > currently using. But what is worse, you don't want the user to switch it > every time, he or she opens a new page or returns the manual, so you need > cookies. To use the cookies, you should tell the user what you are doing > and offer to opt-out. HTML5 Local Storage might be a bit better but we are > not using HTML5 yet, so I'm not sure if we want to go this way. (But I hope > we will switch to HTML5 eventually, the question is if to use also > JavaScript.) Some things (support for smaller screens, not user settings) > can be also achieved by CSS3 but again, it is not what we are using now. > > Current TOC is made for the original full width layout, so there is no > problem with it besides that it is unnecessary to hide it when it is on > empty background on standard and wider screens. > > We can simply remove the width constrain now or leave it there and try to > improve the pages where it is an issue (if the change makes sense also for > the original layout). > > What about getting some feedback on grass-user? > On Wed, Sep 24, 2014 at 2:51 PM, Martin Landa <[email protected]> wrote: > 2014-09-24 20:42 GMT+02:00 Martin Landa <[email protected]>: > > width on the page, it seems to be too narrow [1] to me compared to > > look eg. at [1] where some of examples overflow the border. > > Martin > > [1] http://grass.osgeo.org/grass71/manuals/v.in.ascii.html > > -- > Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev >
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
