- Dillo-dev - lists.mailman3.com

patch: make prefs.c and dillorc2 consistent
by corvid＠lavabit.com Aug. 26, 2008

Aug. 26, 2008

The proposal here is to have everything commented out in the rc by default, and show what the default settings are so that people don't have to spend as much time experimenting when they want to configure their nifty superbrowser. When resolving inconsistencies, I generally picked the rc setting when uncommented, and the prefs one otherwise. Figured it would be a fair approximation of what Jorge might accept... Also, I remember Jorge once saying that maybe it should be named dillo2rc instead of dillorc2. I think so too.

2 4

Re: patch: disallow textarea/button inside select
by jcid＠dillo.org Aug. 25, 2008

Aug. 25, 2008

On Sun, Aug 24, 2008 at 01:25:02AM +0000, corvid wrote: > Putting aside the Stash one for something easy > (with Stash, the html file is like 90K, and it > seems like touching any of it makes the crashing > stop, so...), I find that textarea or button inside > select is bad because close_select assumes that > current input is a select. > > An alternative would be to make close_select > check the current input, but then other > controls aren't supposed to be inside it anyway... > > I feel like we already had this bug and fixed it, > but I must be thinking of whatever specifically made > us add the IN_SELECT test to open_input. We may find a canonical way to implement this constraints in the future (e.g. only OPTION|OPTGROUP in SELECT), maybe inside Html_process_tag()... Committed... -- Cheers Jorge.-

1 0

a list of what dillo2 runs on
by jcid＠dillo.org Aug. 25, 2008

Aug. 25, 2008

On Tue, Aug 19, 2008 at 08:22:54PM +0000, corvid wrote: > > The key is to be informative and that page construction > > and updating is a breeze to do. > > > > > Is it officially obsolete, or should parts of Current Plans > > > migrate over there eventually? > > > > I agree that "current plans" fits the goal better. If you can > > think of a _simple_ way to make it better, go ahead. > > > > This is, in principle I agree that removing the achieved goals > > link, and favouring "Current Plans" improves the site. Now, if we > > find a simple way to keep "Current Plans" up to date and not > > bloated, better. > > I haven't been able to think of anything good... in order to > at least have something, though, how about if I add a link like > "Goals reached since last update" to the bottom of achieved goals, > pointing to current plans? > (where they get migrated over hopefully whenever a release is made, > or at least when they are so old that they can no longer be ignored...) ... or we may switch to this scheme: [Current Plans] // as it is [Changelog Highlights] // for last release [Changelog] // full changelog This looks simple to maintain and understand. (removing achieved goals). -- Cheers Jorge.-

1 0

Problem compiling on FreeBSD
by christopher.illies＠ki.se Aug. 25, 2008

Aug. 25, 2008

Hi, on FreeBSD-7.0-STABLE, fltk-2.0.r6149 from ports I get the following error while compiling the newest dillo from CVS: > cd dw2-cur; ./autogen.sh && ./configure && make aclocal found autoheader found autoconf found automake found [Checks passed] Generating... /usr/local/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE /usr/local/share/aclocal/audiofile.m4:12: run info '(automake)Extending aclocal' /usr/local/share/aclocal/audiofile.m4:12: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal autoheader-2.62: error: AC_CONFIG_HEADERS not found in configure.in checking build system type... i386-unknown-freebsd7.0 [...] 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/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -O2 -fno-strict-aliasing -pipe -I/usr/local/include -Wno-non-virtual-dtor -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -MT libDw_fltk_a-fltkflatview.o -MD -MP -MF .deps/libDw_fltk_a-fltkflatview.Tpo -c -o libDw_fltk_a-fltkflatview.o `test -f 'fltkflatview.cc' || echo './'`fltkflatview.cc In file included from fltkflatview.hh:9, from fltkflatview.cc:23: fltkviewbase.hh:25: error: 'time_t' does not name a type fltkviewbase.hh:26: error: 'time_t' does not name a type *** Error code 1 Stop in /home/chris/Storage/Programming/dillo/dw2-cur/dw. *** Error code 1 Stop in /home/chris/Storage/Programming/dillo/dw2-cur. Christopher

2 3

Linksys NSLU2 ARM XScale success report [FWD: Dillo f15 Compatibility List dillo2]
by corvid＠lavabit.com Aug. 25, 2008

Aug. 25, 2008

Holger Paradies wrote: > Hello > succesfully compiled and running dillo2 > cvs20080825 > -build_triplet = armv5tel-unknown-linux-gnu > on linksys-nslu2 266MHZ 32MB RAM > (native build) > debian-lenny_arm gcc version 4.3.1 (Debian 4.3.1-2) > kernel 2.6.25-2-ixp4xx > > and running via ssh -X > > > also success on Debian-Etch x86 > > Greetings Holger

1 0

Re: Broken links on www-site
by jcid＠dillo.org Aug. 19, 2008

Aug. 19, 2008

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.-

1 0

a list of what dillo2 runs on
by jcid＠dillo.org Aug. 19, 2008

Aug. 19, 2008

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.-

2 2

towards a consistent UI
by Johannes.Hofmann＠gmx.de Aug. 18, 2008

Aug. 18, 2008

Hi, I really like the way Ctrl-l now just selects the current URL in normal mode avoiding a dialog window. 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. Do we really want to kill all uses of dialog windows? We still have "Search the Web" anyway. Also the location of the "IMG ON/OFF" button seems a bit arbitrary. 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. * All shortcuts are configurable. * No more img on/off button. One can use a menubar entry or keyboard shortcut instead. * The "Search the Web" button should be just as all the other buttons ("Back", "Forw" ...) and be configurable of course. Perhaps a single config option like: panel_buttons="back, forw, home, reload, save, stop, book" * The "HTML bugs" button in the status bar is ok. It shows the bug-state of the current page. * "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. * In fullscreen mode "Ctrl-l" opens a dialog window again. Any better solution? Cheers, Johannes

2 2

Dillo in OSX
by higuita7＠yahoo.co.uk Aug. 15, 2008

Aug. 15, 2008

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

4 4

Please help me on this...
by jcid＠dillo.org Aug. 14, 2008

Aug. 14, 2008

Hi there, Looking to a future dillo2 release for the public, I was wondering about the main drive behind dillo2. I mean, in this years of Facebook, WebKit, Flash, propietary video codecs, etc. what's the main point behind dillo2? From the objectives: 1.- The democratization of internet information access. 2.- Personal security and privacy. 3.- High software efficiency. The first one is interesting to analyze along the lines that dillo allows to search for tons of information spread through the Internet using low HW requirements and low bandwidth as a dialup. This is reassuring as dillo efectively enables information access to any person under such constraints. The second one is partly attained by not writing to HD and by a non-existent scripting support. The third one is the one to brag about. ;-) Since some time, the thought that enabling dillo2 as a help browser could also bring local information (i.e. in HD) closer to the user came as a powerful one. Having an app. that pops-up in a second and that's quick, responsive and easy to use is certainly a strong drive for a person in search of information (that's why I'd like to see it inside Debian as a help system). In the near future, I'd like to have CSS and proper floating text rendering (DIV element), plus an API as a help browser. There're countries where paying Universitary studies is the state's burden. If a citizen doesn't want to study there, it's a choice. I think the same may happen with dillo, once people know about it, they can choose to use it or not. While thinking about it, these comments surprised me: "Slashdot | What Do You Want On Future Browsers?" http://tech.slashdot.org/article.pl?sid=08/06/30/1845201 (yes, give them a read!) (They're talking from a full featured Firefox basis. I don't know how may of them would like to use something like dillo) Behind a project like ours, there're two communities: developers and users. The main factor to push forward the project is developers and their motivations (in a commercial environment what pushes the development is the money invested and the profit margins/strategy sought). That's why I'm asking you to help me with your views, needs visions on the future of dillo2 these days. With regard to the user community, I'd love to have some feedback from them, but I guess we need to release dillo2 first! :-) -- Cheers Jorge.-

4 4