On Fri, Apr 23, 2010 at 01:18, George Hunt <georgejh...@gmail.com> wrote: > No, I don't think it is a widget, gtk problem -- since I could change the > CSS to correct the problem. > > I wrote a javascript fragment: > > document.write('width:' + window.screen.width + " height:" + > window.screen.height); > > On XO1.0 I got a response: "width:840 height:634" and on XO1.5 I got > "width:1200 height:900" > > If this is a known situation, and it is desired for some good reason, I'm > sure people like me can live with it. Otherwise I think the rendering > engine on 1.0 and 1.5 should come up with similar defaults -- and > considering our installed base-- it should be compatible 800x600. > > Persuant to Seth's suggestion, I've discovered that it is possible to write > CSS using percentages rather than absolute pixel dimensions, and circumvent > haveing to make a decision in javascript based upon reported screen > dimension, and load separate CSS pages. > > Somebody has cleaned up the webview widget. I'm having to work around a > problem in build 802 that is fixed in F11 -- In the earlier build the widget > controled it's own visibility by doing 'self.web_view.get_toplevel().hide()' > which made it much more difficult to incorporate in at activity that wanted > to use other widgets as well. > > Who's maintaining Hulahop/webview?
As per http://wiki.sugarlabs.org/go/Development_Team/Release/Modules#hulahop hulahop is unmaintained, any help is welcome. Regards, Tomeu > George > > > On Thu, Apr 22, 2010 at 1:39 PM, Tomeu Vizoso <to...@tomeuvizoso.net> wrote: >> >> On Mon, Apr 19, 2010 at 04:27, George Hunt <georgejh...@gmail.com> wrote: >> > Hi again, >> > >> > My activity uses Hulahop Browser for its help system. The default >> > browser >> > on the XO`1.0 seems set up for 800x600. The CSS width specs on the >> > functioning HELP activity add up to 800 px wide and everything works out >> > ok. >> > >> > But on F11 XO1.5, the same help activity only renders about 2/3 full >> > screen. >> > And I'm experiencing similar problems rendering my help pages between >> > 1.0 >> > and 1.5. >> > >> > On F11, I believe the default screen width sensed by the xulrunner >> > engine is >> > the 1200x900, the actual screen size. >> > >> > I'm pretty sure there's a way to ask the gecko engine to render on a >> > 800x600 >> > screen, or alternatively to ask gecko on the XO1.0 to render on a >> > 1200x900 >> > surface. >> > >> > But I don't know XUL well and I feel I'd be wasting my time learning >> > about >> > how to set up gecko, if someone already knows how to solve this one. >> > I'd be >> > willing to modify HELP activity, once we I find an acceptable solution. >> >> Hmm, is the problem that the html content doesn't cover the whole >> hulahop area, or that the hulahop widget doesn't fill the whole >> screen? >> >> If the former, it's a matter of html. If the latter, hulahop is a >> normal gtk widget and you should use the gtk api to make what you >> want. Hulahop should behave the same as a gtk.Button in this regard, >> >> HTH, >> >> Tomeu >> >> > George >> > >> > _______________________________________________ >> > Devel mailing list >> > Devel@lists.laptop.org >> > http://lists.laptop.org/listinfo/devel >> > >> > > > _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel