June 2011 - Dillo-dev - lists.mailman3.com

Development schedule for version 1.3

by Johannes.Hofmann＠gmx.de

On Sun, Jun 05, 2011 at 08:08:15PM +0000, corvid wrote: > reza wrote: > > It seems that FLTK will release their final 1.3 version next week on June > > 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm > > asking is that as you know I'm preparing an installable Mac OS package, > > which I hope to go on dillo's download page (and hopefully introduce dillo > > to many non-developer users). So I'd like to know if we are just waiting on > > that final release of FLTK 1.3, or whether there are still open bugs > > remaining for our next release? > > Right now, I'm aware of: > > - the preferred font code in src/dillo.cc. > > The other day, I put a few minutes into setting, e.g., > FL_HELVETICA to prefs.font_sans_serif > FL_HELVETICA_BOLD to prefs.font_sans_serif " bold" > etc. > ..which seemed to be working for XFT but not with it disabled. Maybe the > latter wanted the -*-*-*-*-style strings, and I'd meant to ask Johannes > whether this was all the right direction to go in, anyway, since he'd done > the fonts work in dw/ for this port. I just committed something to get the preferred font stuff working on fltk-1.3. Please give it a try. Cheers, Johannes

June 6, 2011

Development schedule for version 1.3

by rf.opensource＠gmail.com

On Sun, Jun 5, 2011 at 3:08 PM, corvid <corvid(a)lavabit.com> wrote: > reza wrote: > > It seems that FLTK will release their final 1.3 version next week on June > > 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm > > asking is that as you know I'm preparing an installable Mac OS package, > > which I hope to go on dillo's download page (and hopefully introduce > dillo > > to many non-developer users). So I'd like to know if we are just waiting > on > > that final release of FLTK 1.3, or whether there are still open bugs > > remaining for our next release? > > Right now, I'm aware of: > > - the preferred font code in src/dillo.cc. > > The other day, I put a few minutes into setting, e.g., > FL_HELVETICA to prefs.font_sans_serif > FL_HELVETICA_BOLD to prefs.font_sans_serif " bold" > etc. > ..which seemed to be working for XFT but not with it disabled. Maybe the > latter wanted the -*-*-*-*-style strings, and I'd meant to ask Johannes > whether this was all the right direction to go in, anyway, since he'd done > the fonts work in dw/ for this port. > > - tab titles > > Just cosmetic issues of: They seem too short, the original title of, e.g., > ctab5, is suboptimal, and the ones without a title tag are initially blank. > > - Still missing is the -f command line option (used by claws). > > Jorge was waiting for something to do with FLTK before taking action there. > > > Do we have features/bugs for each milestone documented anywhere? http://www.dillo.org/Plans.html is a bit too high level. What comes after 1.3? P.S. Are we going to call Dillo with FLTK1.3 as Dillo3? One problem is that on the surface nothing has changed from Dillo2, so users will probably get confused. > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 5, 2011

Development schedule for version 1.3

by Johannes.Hofmann＠gmx.de

On Sun, Jun 05, 2011 at 08:08:15PM +0000, corvid wrote: > reza wrote: > > It seems that FLTK will release their final 1.3 version next week on June > > 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm > > asking is that as you know I'm preparing an installable Mac OS package, > > which I hope to go on dillo's download page (and hopefully introduce dillo > > to many non-developer users). So I'd like to know if we are just waiting on > > that final release of FLTK 1.3, or whether there are still open bugs > > remaining for our next release? > > Right now, I'm aware of: > > - the preferred font code in src/dillo.cc. > > The other day, I put a few minutes into setting, e.g., > FL_HELVETICA to prefs.font_sans_serif > FL_HELVETICA_BOLD to prefs.font_sans_serif " bold" > etc. > ..which seemed to be working for XFT but not with it disabled. Maybe the > latter wanted the -*-*-*-*-style strings, and I'd meant to ask Johannes > whether this was all the right direction to go in, anyway, since he'd done > the fonts work in dw/ for this port. I already played with using the Platform::fontExists() interface here, but it somehow didn't work immediately and I got distracted... I can take another look at it. Cheers, Johannes

June 5, 2011

Development schedule for version 1.3

by corvid＠lavabit.com

reza wrote: > It seems that FLTK will release their final 1.3 version next week on June > 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm > asking is that as you know I'm preparing an installable Mac OS package, > which I hope to go on dillo's download page (and hopefully introduce dillo > to many non-developer users). So I'd like to know if we are just waiting on > that final release of FLTK 1.3, or whether there are still open bugs > remaining for our next release? Right now, I'm aware of: - the preferred font code in src/dillo.cc. The other day, I put a few minutes into setting, e.g., FL_HELVETICA to prefs.font_sans_serif FL_HELVETICA_BOLD to prefs.font_sans_serif " bold" etc. ..which seemed to be working for XFT but not with it disabled. Maybe the latter wanted the -*-*-*-*-style strings, and I'd meant to ask Johannes whether this was all the right direction to go in, anyway, since he'd done the fonts work in dw/ for this port. - tab titles Just cosmetic issues of: They seem too short, the original title of, e.g., ctab5, is suboptimal, and the ones without a title tag are initially blank. - Still missing is the -f command line option (used by claws). Jorge was waiting for something to do with FLTK before taking action there.

June 5, 2011

Ignore a command line option (for Mac OS bundles)

by obeythepenguin＠gmail.com

On Sun, 05 Jun 2011 15:54:56 -0400, corvid <corvid(a)lavabit.com> wrote: > reza wrote: >> Now most of the plugins seem to work, at least bookmarks work fine. >> >> There is still a problem remaining though. In the target machine, I >> cannot >> open sites that require SSL (for example www.gmail.com, >> mail.yahoo.com) I'm >> not sure why it happens. Is there any library that helps in SSL >> connections >> that I forgot copying over? > > openssl? libssl and libcrypto (and Dillo needs to be compiled with --enable-ssl) ~Benjamin

June 5, 2011

Ignore a command line option (for Mac OS bundles)

by corvid＠lavabit.com

reza wrote: > Now most of the plugins seem to work, at least bookmarks work fine. > > There is still a problem remaining though. In the target machine, I cannot > open sites that require SSL (for example www.gmail.com, mail.yahoo.com) I'm > not sure why it happens. Is there any library that helps in SSL connections > that I forgot copying over? openssl?

June 5, 2011

Development schedule for version 1.3

by rf.opensource＠gmail.com

Hi guys, It seems that FLTK will release their final 1.3 version next week on June 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm asking is that as you know I'm preparing an installable Mac OS package, which I hope to go on dillo's download page (and hopefully introduce dillo to many non-developer users). So I'd like to know if we are just waiting on that final release of FLTK 1.3, or whether there are still open bugs remaining for our next release? Thanks, Reza

June 5, 2011

Ignore a command line option (for Mac OS bundles)

by rf.opensource＠gmail.com

On Sun, Jun 5, 2011 at 11:31 AM, corvid <corvid(a)lavabit.com> wrote: > > I could use a bit of advice though. In my preliminary experiments, > > I'm having a bit of problem with the dpi related dynamic libraries. > > I can get dillo to run on another machine with libpng, libjpeg and > > zlib copied over to /usr/local/lib, but none of the plugins work. I > > have copied the usr/local/lib/dillo folder too, and also > > /usr/local/bin/dpid and /usr/local/bin/dpic, but still the plugins > > do not work in the target system. Any files I forgot to copy over? > > How about dpidrc? > > > Thanks, yes it works. I had forgotten the following: /usr/local/etc/dillo/dillorc /usr/local/etc/dillo/dpidrc /usr/local/etc/dillo/ Now most of the plugins seem to work, at least bookmarks work fine. There is still a problem remaining though. In the target machine, I cannot open sites that require SSL (for example www.gmail.com, mail.yahoo.com) I'm not sure why it happens. Is there any library that helps in SSL connections that I forgot copying over? BTW, I tried following Makefile to see what happens for make install, but since it is autogenerated by autoconf it's a bit too complex to follow manually :(

June 5, 2011

Table::addCell() leak

by corvid＠lavabit.com

http://starurchin.org/dillo/valgrind/10ca58f617a0693638facdb40bcf319af1bdfc… has a leak at dw/table.cc:323, and I found a way to trigger it: <table border=2> <tr><td>first<td rowspan=2>tall<td>third <tr><td colspan=2>wide<td>last </table> Jorge, you might remember a little something about tables. Can we simply check children->get() before putting anything there, or do we have to fix things somewhere if part of a span is stolen away?

June 5, 2011

Ignore a command line option (for Mac OS bundles)

by rf.opensource＠gmail.com

On Sat, Jun 4, 2011 at 5:19 PM, corvid <corvid(a)lavabit.com> wrote: > reza wrote: > > I'm trying to create a Mac OS executable bundle for dillo. This will be > > immensely helpful in increasing the reach of dillo to Mac users, as > majority > > of them shudder and run away when they hear they have to download, > (compile > > and) install the following: > > > > 1. Xcode 3 (which is a 4GB download!) > > 2. FLTK > > 3. libjpeg > > 4. libpng > > 5. zlib > > > > I've so far managed to cross compile both 32 bit and 64 bit binaries of > > dillo (same with fltk, libjpeg, libpng, zlib), create a bundle (which > fixes > > the icon problem) and almost get it to run on another machine. I have a > > small problem however and can use some help. > > > > It turns out Mac OS passes a command line argument to applications when > it > > runs them as a bundle. The command line option is something like > > -psn_0_25790615, where the latter part of the number is different in each > > run. Dillo of course freaks out when it sees it, prints out the help text > > (correct usage and whatnot) and exits. > > > > Can you please add a case to the command line parsing code to ignore an > > option if it includes text "-psn_0"? I could give it a shot but chances > are > > I'll break something else. Something like this should work: > > > > if (string(argv[1]).find("-psn_") == 0) { > > _MSG("Apparently a mac bundle", 0); > > _MSG(argv[1], 0); > > //ignore this option and move to the next; > > > > (Code sample from > > > https://svn.janelia.org/penglab/projects/v3d/trunk/v3d_main/v3d/v3d_command… > ) > > Perhaps a relatively clean solution would be for you to have a wrapper -- > whatever the moral equivalent of a shell script might be under these > circumstances -- that removes the argument and then calls Dillo. > > > Unfortunately by the time the first executable of the bundle (my script) gets to run, the current working directory is somehow reset to /, and I don't know how to retrieve the runtime bundle directory. I still think that my suggested solution is an easier one to implement without wrestling with the Mac OS bundle execution policy, even though I concur your solution is more elegant. _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 5, 2011