- Dillo-dev - lists.mailman3.com

patch: make image inputs less of a special case
by corvid＠lavabit.com Sept. 1, 2008

Sept. 1, 2008

- have the complex button resource remember its click x,y. - just use the Activate signal instead of Clicked - don't have to carry x,y through so much of the form code. - use appendValues instead of that special case in buildQueryData. (Jorge: I have another version of the form action url display patch, but this jumped ahead of it somehow)

2 1

init_rawdatabuffer is slow.
by corvid＠lavabit.com Sept. 1, 2008

Sept. 1, 2008

That's the code that paints the stripes that you see initially in images. Here's what gprof said when I loaded a 2 meg jpeg: Each sample counts as 0.01 seconds. % cumulative self self total time seconds seconds calls ms/call ms/call name 34.76 0.57 0.57 1 570.00 570.00 dw::fltk::init_rawdatabuffer(int, int, int, int, unsigned char 26.83 1.01 0.44 1536 0.29 0.29 dw::fltk::FltkImgbuf::copyRow(int, unsigned char const*) 25.00 1.42 0.41 379 1.08 1.08 dStr_insert_l 7.32 1.54 0.12 rgb_to_565d(unsigned char const*, unsigned char*, int, int) 0.61 1.55 0.01 7759 0.00 0.00 lout::container::untyped::Iterator::hasNext() .. If I take out the init_rawdatabuffer() call and put in a bzero() instead, I get: Each sample counts as 0.01 seconds. % cumulative self self total time seconds seconds calls ms/call ms/call name 51.43 0.54 0.54 1536 0.35 0.36 dw::fltk::FltkImgbuf::copyRow(int, unsigned char const*) 34.29 0.90 0.36 373 0.97 0.97 dStr_insert_l 5.71 0.96 0.06 rgb_to_565d(unsigned char const*, unsigned char*, int, int) 1.90 0.98 0.02 a_Image_imgbuf_new 0.95 0.99 0.01 10868 0.00 0.00 lout::container::untyped::Collection0::AbstractIterator::unref() .. Any objections, then, to having pictures start out black instead of striped?

3 2

Bugtrack DB updated
by jcid＠dillo.org Aug. 30, 2008

Aug. 30, 2008

Hi, The Bugtrack DB was updated for dillo2 too. -- Cheers Jorge.-

2 9

web site partial update
by jcid＠dillo.org Aug. 28, 2008

Aug. 28, 2008

Hi, With a view to prepare our next dillo2 release, the web site has been partially updated. From the links column, these sections: Developers, Users, Related and "Hosted at" are up to date. Even the downloadable alternative icons work, and pages were bug-meter validated too. BTW, what version number should we give to dillo2? 2.0 seems like a good candidate. -- Cheers Jorge.-

2 1

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