- Dillo-dev - lists.mailman3.com

Re: Broken links on www-site

by jcid＠dillo.org

On Tue, Aug 19, 2008 at 07:58:06PM +0300, Henri Salo wrote: > On Tue, Aug 19, 2008 at 12:21:56PM -0400, Jorge Arellano Cid wrote: > > Good, if you want to help us, welcome aboard! > > > > Please give a read to the just updated: > > > > http://www.dillo.org/8years.html > > > > and update the wiki. In case of doubt, just ask. > > > > BTW, corvid is about to patch that page along these lines: > > > > Jorge.- > > I have been lurking around in mailing lists for a while if you haven't > already noticed so I have read that link already. It was written this morning! > I have also tested > some patches, but I didn't have anything to say about those. I don't > actually like Wiki{pedia,media} anymore, but I can do exception for > Dillo-project. :-) > For you information there are users who would like test dillo2 using > snapshots from CVS. Should we make proper builds and guides for them? No. I'd prefer them to test the next release. Once it's made, packages are welcomed. -- Cheers Jorge.-

Aug. 19, 2008

a list of what dillo2 runs on

by jcid＠dillo.org

On Tue, Aug 19, 2008 at 03:28:33PM +0000, corvid wrote: > Jorge wrote: > > BTW, I just wrote and updated the "8 years" page: > > > > http://www.dillo.org/8years.html > > from the above: > ] Our users will surely enjoy this new release as it will give them the same > ] things they're accustomed plus antialiasing, smaller footprint, less > ] dependencies, better table rendering, bugfixes, improved GUI, ... In brief, > ] a better dillo. > > Surely they will enjoy UTF-8, plus the ability to read text in whatever charset > their native language uses, plus gzip content encoding, plus the ability to > load individual images on demand... :) Sure! Please add it in the page. -- Cheers Jorge.-

Aug. 19, 2008

a list of what dillo2 runs on

by corvid＠lavabit.com

Jorge wrote: > BTW, I just wrote and updated the "8 years" page: > > http://www.dillo.org/8years.html from the above: ] Our users will surely enjoy this new release as it will give them the same ] things they're accustomed plus antialiasing, smaller footprint, less ] dependencies, better table rendering, bugfixes, improved GUI, ... In brief, ] a better dillo. Surely they will enjoy UTF-8, plus the ability to read text in whatever charset their native language uses, plus gzip content encoding, plus the ability to load individual images on demand... :)

Aug. 19, 2008

a list of what dillo2 runs on

by jcid＠dillo.org

On Tue, Aug 19, 2008 at 01:36:34AM +0000, corvid wrote: > All right, I came up with: > > * Dillo is a > <a href='http://www.dillo.org/Compatibility.html'>multi-platform</a> > graphical web browser known for its speed and small size. > * Dillo is written in C and C++. > * Dillo is based on <a href='http://www.fltk.org'>FLTK2</a>, the Fast Light > ToolKit. > * Dillo is free software made available under the terms of the GNU General > Public License. > * Dillo strives to be friendly both to users and developers. > * Dillo helps web authors to comply with web standards by using the > <a href='http://www.dillo.org/help/bug_meter.html'>bug meter</a>. OK. (please state GPL3). BTW, I just wrote and updated the "8 years" page: http://www.dillo.org/8years.html -- Cheers Jorge.-

Aug. 19, 2008

a list of what dillo2 runs on

by jcid＠dillo.org

On Mon, Aug 18, 2008 at 05:31:57PM +0000, corvid wrote: > Jorge wrote: > > BTW, after the WearLab outage I decided to postpone the > > release for late september or so. It's necessary to update > > the website before the code is released. > > Do you think it's time yet to update the parts of What is Dillo on the > main page that have changed (and rip out the Dillo is frozen), or > should that wait until release is very close? Now that you mention it, I believe making it gradually looks like a good idea. Just stick a note that we're updating the site for the next release (late Sep or early Aug), and let's work on it. -- Cheers Jorge.-

Aug. 18, 2008

a list of what dillo2 runs on

by corvid＠lavabit.com

Jorge wrote: > BTW, after the WearLab outage I decided to postpone the > release for late september or so. It's necessary to update > the website before the code is released. Do you think it's time yet to update the parts of What is Dillo on the main page that have changed (and rip out the Dillo is frozen), or should that wait until release is very close?

Aug. 18, 2008

a list of what dillo2 runs on

by jcid＠dillo.org

On Mon, Aug 18, 2008 at 02:24:21AM +0000, corvid wrote: > I want to get the status of everything in order to update > http://www.dillo.org/Compatibility.html for dillo2. Great. BTW, after the WearLab outage I decided to postpone the release for late september or so. It's necessary to update the website before the code is released. > > Linux x86 - works > DragonFlyBSD - works > > Linux x86-64 - Justus was and is making snapshots, but I don't know whether > he uses them much. I'm using 64bit GNU/Linux on an amd64 and it works flawlessly. > Solaris 10 - Justus reported that it was running, but I believe it was just > a quick test. > OSX - Jorge reports that it works but is currently flaky. Yes. On Aug 28 I'll have access once again to that machine to test Johannes' no-double-buffer suggestion. > *BSD - Some of the mailing list traffic in October was devoted to getting > them working. Presumably it would have been mentioned here if they > had stopped working since, but... > > other - no idea. > > Looking back at what I just wrote, let me clarify that I meant that > dillo2-on-osx is flaky, not that Jorge is flaky :) I hope you're right! ;-) -- Cheers Jorge.-

Aug. 18, 2008

towards a consistent UI

by Johannes.Hofmann＠gmx.de

Hi, -------- Original-Nachricht -------- > Datum: Mon, 11 Aug 2008 12:59:32 -0400 > Von: Jorge Arellano Cid <jcid(a)dillo.org> > An: dillo-dev(a)dillo.org > Betreff: Re: [Dillo-dev] towards a consistent UI > 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. I think the flicker can be avoided, but that won't stop the content from "jumping" in the fullscreen case. > > > 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. Agreed > > > 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. > Yes maybe. I will try that when I have time. > > 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. I think the advantage of a menu bar is that it's easily visible, what functionality is available. Advanced users will probabely use shortcuts. But you are right. I forgot about the context menus. The link and image menu only makes sense as a context menu. > > > 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. Ok. > > > * 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). > I was looking for a way to make the ordering configurable too. > > * 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! ;-) > Or a plugin, that presents a HTML page with search forms? I'm not sure myself :-) > > > * 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. > Yes, I was also thinking about reintroducing the dialog in this case. Cheers, Johannes -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx

Aug. 18, 2008

a list of what dillo2 runs on

by corvid＠lavabit.com

I want to get the status of everything in order to update http://www.dillo.org/Compatibility.html for dillo2. Linux x86 - works DragonFlyBSD - works Linux x86-64 - Justus was and is making snapshots, but I don't know whether he uses them much. Solaris 10 - Justus reported that it was running, but I believe it was just a quick test. OSX - Jorge reports that it works but is currently flaky. *BSD - Some of the mailing list traffic in October was devoted to getting them working. Presumably it would have been mentioned here if they had stopped working since, but... other - no idea. Looking back at what I just wrote, let me clarify that I meant that dillo2-on-osx is flaky, not that Jorge is flaky :)

Aug. 18, 2008

Dillo in OSX

by Johannes.Hofmann＠gmx.de

-------- Original-Nachricht -------- > Datum: Thu, 14 Aug 2008 15:23:08 -0400 > Von: Jorge Arellano Cid <jcid(a)dillo.org> > An: dillo-dev(a)dillo.org > Betreff: Re: [Dillo-dev] Dillo in OSX > 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. You may try with double buffering disabled. If I remember correctly, there is still an unresolved OSX issue in the fltk code used for double buffering. Cheers, Johannes -- Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? Der Eine f?r Alle: http://www.gmx.net/de/go/messenger03

Aug. 15, 2008