- Dillo-dev - lists.mailman3.com

Javascript engine

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jorge Arellano Cid wrote: > Disclaimer: I'm a newbie on JavaScript. JavaScript is a very cool language. Don't believe anyone telling you otherwise ;) > Does anybody know about a lightweight javascript engine we > can use with dillo? > > From what I've seen, SEE (Simple ECMAScript Engine), looks > like a good candidate. This depends entirely on your criteria :) SEE spidermonkey google v8 sloc ~31000 ~91000 ~77000 language c c c++/c license bsd {m,g,lg}pl bsd 100000 objects / s 5.6 0.4 0.2 1000000 objects / s ? 3.3 1.3 Slocs counted via sloccount, tests run on my laptop (core2duo 1.6GHz) run multiple times and averaged using a quick glance. Test script for 1000000 objects attached. see-shell didn't complete the 1000000 object run within 5 minutes of burning my cpu so I killed it. And there are some more things to consider like feature completeness. The mozilla guys are doing some sexy stuff like E4X and JavaScript 1.7 comes with syntactic sugar like array comprehension. The SEE site specifies that they are JavaScript 1.5 compliant, and although it seems actively maintained (latest 3.0 snapshot is dated 2008-02-10) I am not sure if they can keep up with the latest developments. Googles V8 does some interesting tricks like avoiding costly property lookups and generating native machine code, but this reduces portability (not sure if code generation is necessary or an add-on). The site states that it runs on "Windows XP and Vista, Mac OS X 10.5 (Leopard), and Linux systems that use IA-32 or ARM". I built an 32bit executable on linux/x86_64 that worked fine. I would suggest to pick one engine based on the ease of embedding and to develop a clean interface for scripting languages while integrating the chosen engine into dillo. If this is doable (not sure it is, but one can hope) it should be relatively easy to use the very same interface for other implementations and or languages. How cool would it be to hand configure parameters like --with-language javascript:spidermonkey - --with-language lua --with-language python :) And who knows what the next big thing of the web 3.0 will be? Grusszeugs, Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI57OToPmwNWhsaZYRAhtDAJ41dDSliA6jcKSUhw+k2/OrhY1QTgCdFtAD BnM+CV8oujgZLHz7NjY9fqw= =D1fS -----END PGP SIGNATURE-----

Oct. 4, 2008

patch: print numeric addresses instead of pointer

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone :) while debugging ipv6 support I noticed that the debug output of Dns_server(..) was not very helpful since it printed the pointer to the address list instead of the addresses. The attached patch fixes this and also adds the function void a_DilloHost_to_String(DilloHost *host, char *dst, size_t size) to dns.{c,h}. Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI55iloPmwNWhsaZYRAmP9AJ4/6msoDF59IMdpzWh0dZQhIqFgEACcDbBC wiaiHuwdsbOhU8o0ViA7a6M= =m7XD -----END PGP SIGNATURE-----

Oct. 4, 2008

patch: fix dns to ipv6 resolution

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone :) I noticed that ipv6 support in dillo2 is somewhat broken. With this tiny patch hostnames are properly resolved to ipv6 addresses and browsing over ipv6 works fine but entering a numeric address does not. Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI55eXoPmwNWhsaZYRAoCbAJ41ZA66N5zDWetCia5r4OUZmLfwngCfc0WT i2J3z0qscSGR1tuitxAX254= =GJLN -----END PGP SIGNATURE-----

Oct. 4, 2008

patch: close windows from menubar

by jcid＠dillo.org

On Sat, Oct 04, 2008 at 12:37:34AM +0000, corvid wrote: > Jorge wrote: > > From: > > > > 1.- the mini_bug.xpm FLTK2 fix. > > 2.- the focused textarea callback issue. > > 3.- Alt-X crash in the menu. > > 4.- hardcoded 128 tabs. > > 5.- leaving-the-window nav_expecting problem. > > 6.- redraw storms (TabGroup pager) > > 7.- CTRL+q ALT+q don't work from File menu. > > > > We have: > > > > 1, 2) have patches (for FLTK), and we could wait for a new release > > or code workarounds for them in dillo. > > 3) Fixed > > 4) Easy to code a 128 limit in dillo and avoid the segfault. > > 5) Fixed. > > 6) Fixed. > > 7) FLTK problem, no patch yet. No CRASH with Dillo. > > Also I'm seeing that findbar problem. > Load a page. ^F to open the findbar. Click in the viewport. Try to click in > the findbar again. Can't type in it. (Works fine if you use ^F to return > to it, though.) Fixed in CVS. > > What do we do? > > > > a) Contact FLTK developers and wait for a patched release, then > > workaround the rest (if any) in dillo and release. > > b) Workaround in dillo and release. > > > > Comments? > > Trying to get them to fix bugs and apply those that Johannes has > given them is good, but at the same time I think I would act as if > nothing will come of it -- working around what can be worked around > easily and preparing for release. I'd hate to wait while nothing > happens...and nothing happens...and nothing continues to happen. > > And, if it becomes necessary, a patched FLTK2 snapshot can be placed > on dillo.org until they fix the official one. Could be. I'd like to provide a patched FLTK2 tarball from our site, just to keep workarounds out of dillo tree, but some people may want to try dillo2 with their distro-provided FLTK2. In that case we may provide a dillo2 tarball for our patched FLTK2, and also a dillo-workarounds patch for the official FLTK2. Anyway, it'd be good to ask the FLTK team... -- Cheers Jorge.-

Oct. 4, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Jorge wrote: > From: > > 1.- the mini_bug.xpm FLTK2 fix. > 2.- the focused textarea callback issue. > 3.- Alt-X crash in the menu. > 4.- hardcoded 128 tabs. > 5.- leaving-the-window nav_expecting problem. > 6.- redraw storms (TabGroup pager) > 7.- CTRL+q ALT+q don't work from File menu. > > We have: > > 1, 2) have patches (for FLTK), and we could wait for a new release > or code workarounds for them in dillo. > 3) Fixed > 4) Easy to code a 128 limit in dillo and avoid the segfault. > 5) Fixed. > 6) Fixed. > 7) FLTK problem, no patch yet. No CRASH with Dillo. Also I'm seeing that findbar problem. Load a page. ^F to open the findbar. Click in the viewport. Try to click in the findbar again. Can't type in it. (Works fine if you use ^F to return to it, though.) > What do we do? > > a) Contact FLTK developers and wait for a patched release, then > workaround the rest (if any) in dillo and release. > b) Workaround in dillo and release. > > Comments? Trying to get them to fix bugs and apply those that Johannes has given them is good, but at the same time I think I would act as if nothing will come of it -- working around what can be worked around easily and preparing for release. I'd hate to wait while nothing happens...and nothing happens...and nothing continues to happen. And, if it becomes necessary, a patched FLTK2 snapshot can be placed on dillo.org until they fix the official one.

Oct. 4, 2008

patch: fix the toggle button size

by corvid＠lavabit.com

If you try setting font_factor to 2, you will see that check/radio buttons are partly overwritten by their accompanying text. I hope there's a clever way to avoid the getFont() that I use in the patch.

Oct. 4, 2008

patch: close windows from menubar

by jcid＠dillo.org

On Fri, Oct 03, 2008 at 07:02:47PM +0000, corvid wrote: > Jorge wrote: > > On Fri, Oct 03, 2008 at 01:07:36PM -0400, Jorge Arellano Cid wrote: > > > Hi, > > > > > > Committed. > > > > > > On Thu, Oct 02, 2008 at 06:58:25PM +0000, corvid wrote: > > > > BTW, I notice that ctrl-Q and alt-Q, listed in the menu, don't do anything. > > > > > > Yeah. > > > Even MenuBar::handle() doesn't see them. > > > > Seems like an FLTK bug/feature. > > > > If you try ./menu in FLTK's test/ directory, the CTRL shortcuts > > for the "Edit" menu don't work. > > > > Time to ask or to STR? > > I see that if I uncomment the > // if (widget->active() && widget->test_shortcut(false)) { > // setitem(p, menu, item); > // lastkey = 0; > // goto EXECUTE; > // } > in MWindow::handle(int event) in Menu_popup.cxx, ctrl-Q and alt-Q work. OK, it's clear it was deactivated by some reason... From: 1.- the mini_bug.xpm FLTK2 fix. 2.- the focused textarea callback issue. 3.- Alt-X crash in the menu. 4.- hardcoded 128 tabs. 5.- leaving-the-window nav_expecting problem. 6.- redraw storms (TabGroup pager) 7.- CTRL+q ALT+q don't work from File menu. We have: 1, 2) have patches (for FLTK), and we could wait for a new release or code workarounds for them in dillo. 3) Fixed 4) Easy to code a 128 limit in dillo and avoid the segfault. 5) Fixed. 6) Fixed. 7) FLTK problem, no patch yet. No CRASH with Dillo. What do we do? a) Contact FLTK developers and wait for a patched release, then workaround the rest (if any) in dillo and release. b) Workaround in dillo and release. Comments? -- Cheers Jorge.-

Oct. 4, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Jorge wrote: > On Fri, Oct 03, 2008 at 01:07:36PM -0400, Jorge Arellano Cid wrote: > > Hi, > > > > Committed. > > > > On Thu, Oct 02, 2008 at 06:58:25PM +0000, corvid wrote: > > > BTW, I notice that ctrl-Q and alt-Q, listed in the menu, don't do anything. > > > > Yeah. > > Even MenuBar::handle() doesn't see them. > > Seems like an FLTK bug/feature. > > If you try ./menu in FLTK's test/ directory, the CTRL shortcuts > for the "Edit" menu don't work. > > Time to ask or to STR? I see that if I uncomment the // if (widget->active() && widget->test_shortcut(false)) { // setitem(p, menu, item); // lastkey = 0; // goto EXECUTE; // } in MWindow::handle(int event) in Menu_popup.cxx, ctrl-Q and alt-Q work.

Oct. 3, 2008

what crashes remain?

by jcid＠dillo.org

On Fri, Oct 03, 2008 at 06:32:50PM +0000, corvid wrote: > Jorge wrote: > > On Wed, Oct 01, 2008 at 10:47:45PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Wed, Oct 01, 2008 at 09:46:06PM +0000, corvid wrote: > > > > > Jorge wrote: > > > > > > On Wed, Oct 01, 2008 at 02:48:10PM +0000, corvid wrote: > > > > > > > Also, I found out why loading was sometimes randomly disabled (as mentioned > > > > > > > yesterday). You know how leaving the window sometimes causes an extra > > > > > > > Nav_open_url()? > > > > > > > > > > > > No, I don't know. > > > > > > How is it triggered? > > > > > > > > > > Really? I've gotten them often throughout this whole fltk era. > > > > > Taking out my fix, here's a breakpoint on Nav_open_url, > > > > > triggered by leaving the window: > > > > > > > > > > Breakpoint 1, Nav_open_url (bw=0x81b18e8, url=0x81c3998, offset=0) at nav.c:201 > > > > > 201 MSG("Nav_open_url: new url='%s'\n", URL_STR_(url)); > > > > > #0 Nav_open_url (bw=0x81b18e8, url=0x81c3998, offset=0) at nav.c:201 > > > > > #1 0x0805cd4d in a_Nav_push (bw=0x81b18e8, url=0x81c3998) at nav.c:350 > > > > > #2 0x080554ae in a_UIcmd_open_urlstr (vbw=0x81b18e8, urlstr=0x81c44b8 "http://www.dillo.org") at uicmd.cc:323 > > > > > #3 0x08053c12 in location_cb (wid=0x816c6a8, data=0x815c2d8) at ui.cc:245 > > > > > #4 0x08055fa7 in fltk::Widget::do_callback (this=0x816c6a8) at ../fltk/Widget.h:127 > > > > > #5 0x080e093c in call_pending_if_not (i=0x0) at run.cxx:804 > > > > > #6 0x080e124c in fltk::focus (o=0x0) at run.cxx:868 > > > > > #7 0x080e56f4 in fix_focus () at run.cxx:108 > > > > > #8 0x080e676f in fltk::handle () at x11/run.cxx:1603 > > > > > #9 0x080e7520 in do_queued_events () at x11/run.cxx:399 > > > > > #10 0x080e784c in fl_wait (time_to_wait=1.00000002e+20) at x11/run.cxx:459 > > > > > #11 0x080e78e7 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:463 > > > > > #12 0x080e79fe in fltk::run () at run.cxx:399 > > > > > #13 0x0804efab in main (argc=1, argv=0xbffffb34) at dillo.cc:127 > > > > > > > > From the bt it's clear it happens, But how do I trigger/reproduce it. > > > > I've tried moving the mouse pointer out of the window, focusing another > > > > window, etc. With no luck. > > > > > > The reliable way that I'm using > > > (haven't checked how many of these steps/precautions are strictly necessary) > > > - type an url into the Location CustInput and press enter. > > > - don't touch the mouse > > > - when the page has finished loading completely > > > - move the mouse out of the window > > > > > > In case there's some WM interaction, I have fvwm. > > > > OK, I can see the bug with fvwm. > > > > Please check the CVS code. > > It solves the problem here. > > It's working! Form inputs were also checked and FltkEntryResource::setText() calls value() which is a wrapper for text(). -- Cheers Jorge.-

Oct. 3, 2008

what crashes remain?

by corvid＠lavabit.com

Jorge wrote: > On Wed, Oct 01, 2008 at 10:47:45PM +0000, corvid wrote: > > Jorge wrote: > > > On Wed, Oct 01, 2008 at 09:46:06PM +0000, corvid wrote: > > > > Jorge wrote: > > > > > On Wed, Oct 01, 2008 at 02:48:10PM +0000, corvid wrote: > > > > > > Also, I found out why loading was sometimes randomly disabled (as mentioned > > > > > > yesterday). You know how leaving the window sometimes causes an extra > > > > > > Nav_open_url()? > > > > > > > > > > No, I don't know. > > > > > How is it triggered? > > > > > > > > Really? I've gotten them often throughout this whole fltk era. > > > > Taking out my fix, here's a breakpoint on Nav_open_url, > > > > triggered by leaving the window: > > > > > > > > Breakpoint 1, Nav_open_url (bw=0x81b18e8, url=0x81c3998, offset=0) at nav.c:201 > > > > 201 MSG("Nav_open_url: new url='%s'\n", URL_STR_(url)); > > > > #0 Nav_open_url (bw=0x81b18e8, url=0x81c3998, offset=0) at nav.c:201 > > > > #1 0x0805cd4d in a_Nav_push (bw=0x81b18e8, url=0x81c3998) at nav.c:350 > > > > #2 0x080554ae in a_UIcmd_open_urlstr (vbw=0x81b18e8, urlstr=0x81c44b8 "http://www.dillo.org") at uicmd.cc:323 > > > > #3 0x08053c12 in location_cb (wid=0x816c6a8, data=0x815c2d8) at ui.cc:245 > > > > #4 0x08055fa7 in fltk::Widget::do_callback (this=0x816c6a8) at ../fltk/Widget.h:127 > > > > #5 0x080e093c in call_pending_if_not (i=0x0) at run.cxx:804 > > > > #6 0x080e124c in fltk::focus (o=0x0) at run.cxx:868 > > > > #7 0x080e56f4 in fix_focus () at run.cxx:108 > > > > #8 0x080e676f in fltk::handle () at x11/run.cxx:1603 > > > > #9 0x080e7520 in do_queued_events () at x11/run.cxx:399 > > > > #10 0x080e784c in fl_wait (time_to_wait=1.00000002e+20) at x11/run.cxx:459 > > > > #11 0x080e78e7 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:463 > > > > #12 0x080e79fe in fltk::run () at run.cxx:399 > > > > #13 0x0804efab in main (argc=1, argv=0xbffffb34) at dillo.cc:127 > > > > > > From the bt it's clear it happens, But how do I trigger/reproduce it. > > > I've tried moving the mouse pointer out of the window, focusing another > > > window, etc. With no luck. > > > > The reliable way that I'm using > > (haven't checked how many of these steps/precautions are strictly necessary) > > - type an url into the Location CustInput and press enter. > > - don't touch the mouse > > - when the page has finished loading completely > > - move the mouse out of the window > > > > In case there's some WM interaction, I have fvwm. > > OK, I can see the bug with fvwm. > > Please check the CVS code. > It solves the problem here. It's working!

Oct. 3, 2008