August 2008 - Dillo-dev - lists.mailman3.com

Dillo in OSX

by jcid＠dillo.org

On Thu, Aug 14, 2008 at 04:59:30PM +0000, corvid wrote: > I just remembered the bit in png.c that goes: > > /* Get and set gamma information. Beware: gamma correction 2.2 will > only work on PC's. todo: select screen gamma correction for other > platforms. */ > if (png_get_gAMA(png_ptr, info_ptr, &gamma)) > png_set_gamma(png_ptr, 2.2, gamma); > > Does that still need fixing up for OSX nowadays? I didn't notice anything strange when testing dillo2 native in OSX. Images looked quite normal. Has anyone else tried it? BTW, the GUI under OSX has quite a lot of glitches. Mainly related with canvas refresh calls being lost, selection being really weird and the "canvas" area stepping a bit over the button panel. -- Cheers Jorge.-

Aug. 14, 2008

Dillo in OSX

by corvid＠lavabit.com

I just remembered the bit in png.c that goes: /* Get and set gamma information. Beware: gamma correction 2.2 will only work on PC's. todo: select screen gamma correction for other platforms. */ if (png_get_gAMA(png_ptr, info_ptr, &gamma)) png_set_gamma(png_ptr, 2.2, gamma); Does that still need fixing up for OSX nowadays?

Aug. 14, 2008

Dillo in OSX

by jcid＠dillo.org

On Wed, Aug 13, 2008 at 03:51:46AM +0000, Daniel Mota Leite wrote: > Hi again > > Found the problem... had some old fltk includes in /usr/local > and was installing the cvs to /usr ... so dillo was mixing both > includes and breaking the compile. > > its fixed now, thanks for the help, specially Johannes :) FWIW, the latest CVS should compile without warnings on 64bit. (tested under xubuntu 8.04.1) -- Cheers Jorge.-

Aug. 13, 2008

Dillo in OSX

by higuita7＠yahoo.co.uk

Hi again Found the problem... had some old fltk includes in /usr/local and was installing the cvs to /usr ... so dillo was mixing both includes and breaking the compile. its fixed now, thanks for the help, specially Johannes :) higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Aug. 13, 2008

towards a consistent UI

by jcid＠dillo.org

Hi, Well here's my opinion on these UI points: On Mon, Aug 04, 2008 at 09:50:24PM +0200, Johannes Hofmann wrote: > Hi, > > I really like the way Ctrl-l now just selects the current > URL in normal mode avoiding a dialog window. Me too! > In fullscreen mode however, the short switch to normal mode to enter > the new URL requires a complete redraw of the page contents. > Also the contents "jumps" down for the time the location bar is > shown. This can be distracting. Find text also causes a redraw. Maybe avoiding the redraw in both cases is a good solution. Not of high priority unless really simple to implement. > Do we really want to kill all uses of dialog windows? We still have > "Search the Web" anyway. No. Some dialog windows are quite OK, and there's no need I can see to ban them. > Also the location of the "IMG ON/OFF" button seems a bit arbitrary. I like it where it is, but agree on that it may find a better place. Together with the other Panel buttons, my be. > How could a consistent user interface of dillo look like? > > Here is my proposal - just to start the discussion: > > * Everything is accessible via the menubar and via keyboard > shortcuts. The shortcuts are shown behind the menu entries. Currently the main model is context sensitive popups (right click). There're some things you can't get from them (e.g. Open File), but I see no point in duplicating the popup menus from the menu bar. About everything being accessible via keyboard shortcuts, I don't agree. I believe there are simpler ways. For instance if there's a shortcut for every popup menu entry, there's a need to remember a lot of shortcut/function pairs. Now if there's a shortcut to popup the context sensitive menu, and that menu is keyboard operable, IMHO that's easier to remember/use. If there's a frequently used operation inside a popup, it may have its own shortcut. > shortcuts are shown behind the menu entries. Agreed. > * All shortcuts are configurable. Agreed. > > * No more img on/off button. One can use a menubar entry or keyboard > shortcut instead. I prefer the button. It's more visible and gives feedback on its current status. Firefox has this functionality somewhere, and a few people know of it. > * The "Search the Web" button should be just as all the other > buttons ("Back", "Forw" ...) and be configurable of course. Agreed. With something like: search_url="<title>,<URL>" in dillorc2, with the first one being the default for instance. > Perhaps a single config option like: > panel_buttons="back, forw, home, reload, save, stop, book" I prefer the boolean way (current model). > * The "HTML bugs" button in the status bar is ok. > It shows the bug-state of the current page. Agreed! > * "Search the Web" opens the start page of the selected search > engine (e.g. google.com) and selects the search text field. > I'm not sure about that, but it avoids the dialog window and it makes > clear to which search engine the query is sent. > The additional page load for the empty search page is only > required once - then it's cached. NO! :-) I love avoiding the search page. e.g. with google. ...but, yes, I see there may be cases where the native HTML interface is preferred. Maybe a simple flag can help it: search_url="<title>,<URL>[,LoadPage]" Thus, with no flag, we get a dialog: .------------------------------, | Search with <title>: | | [_________________________] | | | | [Cancel] [OK] | '------------------------------' and with the "LoadPage" flag, the HTML page. This can be implemented quickly! ;-) > * In fullscreen mode "Ctrl-l" opens a dialog window again. Any > better solution? If the redraw can be avoided, could be, if not, the dialog may be OK. I haven't used this case too much so I don't *feel* the problem. -- Cheers Jorge.-

Aug. 11, 2008

Dillo in OSX

by Johannes.Hofmann＠gmx.de

-------- Original-Nachricht -------- > Datum: Mon, 11 Aug 2008 03:32:15 +0100 > Von: higuita <higuita(a)GMX.net> > An: "Johannes Hofmann" <Johannes.Hofmann(a)gmx.de> > Betreff: Re: [Dillo-dev] Dillo in OSX > Hi > > On Sun, 10 Aug 2008 11:36:08 +0200, "Johannes Hofmann" > <Johannes.Hofmann(a)gmx.de> wrote: > > Hm, maybe some stale fltk2 header files? > > i clean up the root dw2 folder and done a new cvs up && autogen.sh && > configure ... but still it failled > > > You could try to add -E to the failing g++ call above to check the > > preprocessed sources. > > in a command line, i added the -E and it build successful > (no error)... > if i force success on that g++ command, i can continue and > build dillo successful and dillo seems to work fine > > bad fltk install? broken compiler? > should i totally remove the dillo2 and do a totally new checkout? > > :) > > thanks in advance for the help I suspect it is somehow related to your fltk2 installation. Perhaps you have one from your distribution and a self compiled version at the same time? Johannes -- GMX Kostenlose Spiele: Einfach online spielen und Spa? haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/61691…

Aug. 11, 2008

Dillo in OSX

by higuita7＠yahoo.co.uk

Hi On Mon, 4 Aug 2008 18:50:17 -0400, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Great, committed. > I works, dillo2 runs native in Leopard > There are several glitches but it's quite a good start. 8-) humm... if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dw-testbed\" -DVERSION=\"0.0.43j\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UIO_H=1 -I. -I. -I/usr/local/include -I/usr/include/freetype2 -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -MT libDw_fltk_a-fltkmisc.o -MD -MP -MF ".deps/libDw_fltk_a-fltkmisc.Tpo" -c -o libDw_fltk_a-fltkmisc.o `test -f 'fltkmisc.cc' || echo './'`fltkmisc.cc; \ then mv -f ".deps/libDw_fltk_a-fltkmisc.Tpo" ".deps/libDw_fltk_a-fltkmisc.Po"; else rm -f ".deps/libDw_fltk_a-fltkmisc.Tpo"; exit 1; fi fltkmisc.cc: In function 'void dw::fltk::misc::warpPointer(int, int)': fltkmisc.cc:45: error: 'warp_mouse' is not a member of 'fltk' make[1]: *** [libDw_fltk_a-fltkmisc.o] Error 1 make[1]: Leaving directory `/home/higuita/build/dillo2/dw2/dw' make: *** [all-recursive] Error 1 i'm using the latest svn from fltk and from dillo... i'm using slamd64 (slackware 64bits) thanks higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Aug. 10, 2008

an example of page redraw problem when images load

by corvid＠lavabit.com

With automatic image loading turned off, if I go to http://genode.org/documentation/developer-resources/walk_through , page down to the [IMG] below "The launchpad application starter", and click on it, the space to the right of the image still contains remnants of the text that used to be there.

Aug. 9, 2008

Re: patch: form controls outside of forms

by jcid＠dillo.org

On Sun, Jul 20, 2008 at 07:38:56PM +0000, corvid wrote: > *remind* *remind* In absence of comment, I decided to commit it. -- Cheers Jorge.-

Aug. 6, 2008

Dillo in OSX

by jcid＠dillo.org

On Sun, Aug 03, 2008 at 07:52:56PM +0200, Johannes Hofmann wrote: > Hi Jorge, > > On Sun, Aug 03, 2008 at 01:30:01PM -0400, Jorge Arellano Cid wrote: > > Hi Johannes, > > > > When trying to compile dillo2 in OSX, FLTK2 compiles OK, > > dw's fltkviewbase.hh needs an time.h include and I get this > > error: > > > > isc.Tpo -c -o libDw_fltk_a-fltkmisc.o `test -f 'fltkmisc.cc' || echo > > './'`fltkmisc.cc > > fltkmisc.cc: In function 'int dw::fltk::misc::screenWidth()': > > fltkmisc.cc:34: error: 'xdisplay' is not a member of 'fltk' > > fltkmisc.cc:34: error: 'xscreen' is not a member of 'fltk' > > fltkmisc.cc:34: error: 'DisplayWidth' was not declared in this scope > > fltkmisc.cc: In function 'int dw::fltk::misc::screenHeight()': > > fltkmisc.cc:39: error: 'xdisplay' is not a member of 'fltk' > > fltkmisc.cc:39: error: 'xscreen' is not a member of 'fltk' > > fltkmisc.cc:39: error: 'DisplayHeight' was not declared in this scope > > fltkmisc.cc: In function 'void dw::fltk::misc::warpPointer(int, int)': > > fltkmisc.cc:44: error: 'xdisplay' is not a member of 'fltk' > > fltkmisc.cc:44: error: 'None' was not declared in this scope > > fltkmisc.cc:45: error: 'xdisplay' is not a member of 'fltk' > > fltkmisc.cc:45: error: 'xscreen' is not a member of 'fltk' > > fltkmisc.cc:45: error: 'RootWindow' was not declared in this scope > > fltkmisc.cc:46: error: 'XWarpPointer' was not declared in this scope > > make[1]: *** [libDw_fltk_a-fltkmisc.o] Error 1 > > make: *** [all-recursive] Error 1 > > > > Do you know the proper solution for this? > > Can you please try attached patch? It replaces X11 specific calls > with platform independent ones from fltk2. > They probabely didn't exist when fltkmisc.cc was coded. > Great, committed. I works, dillo2 runs native in Leopard! There are several glitches but it's quite a good start. 8-) -- Cheers Jorge.-

Aug. 5, 2008