- Dillo-dev - lists.mailman3.com

start on image maps (dw-part)

by Johannes.Hofmann＠gmx.de

Hi, just to let you know, I just started with client side image maps (the dw-part). Below is an initial implementation of ImageMapsList. This is not yet ready at all, but perhaps someone might want have a look. Cheers, Johannes diff -r 877bbc03146b -r ebc6de688732 dw/image.cc --- a/dw/image.cc Thu Apr 17 22:14:42 2008 +0200 +++ b/dw/image.cc Mon Apr 21 21:03:51 2008 +0200 @@ -25,12 +25,44 @@ namespace dw { +ImageMapsList::ImageMap::ImageMap () +{ + shapesAndLinks = new container::typed::List <ShapeAndLink> (true); +} + +void ImageMapsList::ImageMap::add (core::Shape *shape, int link) { + ShapeAndLink *shapeAndLink = new ShapeAndLink (); + shapeAndLink->shape = shape; + shapeAndLink->link = link; + shapesAndLinks->append (shapeAndLink); +} + +int ImageMapsList::ImageMap::link (int x, int y) { + container::typed::Iterator <ShapeAndLink> it; + int link = -1; + + for (it = shapesAndLinks->iterator (); it.hasNext (); ) { + ShapeAndLink *shapeAndLink = it.getNext (); + + if (shapeAndLink->shape->isPointWithin (x, y)) { + link = shapeAndLink->link; + break; + } + } + + return link; +} + ImageMapsList::ImageMapsList () { + imageMaps = new container::typed::HashTable <object::Object, ImageMap> + (true, true); + currentMap = NULL; } ImageMapsList::~ImageMapsList () { + delete imageMaps; } /** @@ -42,6 +74,8 @@ ImageMapsList::~ImageMapsList () */ void ImageMapsList::startNewMap (object::Object *key) { + currentMap = new ImageMap (); + imageMaps->put (key, currentMap); } /** @@ -52,6 +86,7 @@ void ImageMapsList::startNewMap (object: */ void ImageMapsList::addShapeToCurrentMap (core::Shape *shape, int link) { + currentMap->add (shape, link); } // ---------------------------------------------------------------------- diff -r 877bbc03146b -r ebc6de688732 dw/image.hh --- a/dw/image.hh Thu Apr 17 22:14:42 2008 +0200 +++ b/dw/image.hh Mon Apr 21 21:03:51 2008 +0200 @@ -22,6 +22,27 @@ namespace dw { */ class ImageMapsList { +private: + class ImageMap: public object::Object { + private: + class ShapeAndLink: public object::Object { + public: + core::Shape *shape; + int link; + }; + + container::typed::List <ShapeAndLink> *shapesAndLinks; + public: + ImageMap (); + ~ImageMap (); + + void add (core::Shape *shape, int link); + int link (int x, int y); + }; + + container::typed::HashTable <object::Object, ImageMap> *imageMaps; + ImageMap *currentMap; + public: ImageMapsList (); ~ImageMapsList ();

April 21, 2008

Future of dillo2

by Johannes.Hofmann＠gmx.de

On Mon, Apr 21, 2008 at 06:32:52PM +0000, corvid wrote: > Johannes wrote: > > What is still missing for an official release apart from image maps? > > For one thing, I think text search needs to work for phrases. Yes, and <Esc> should consistently close dialogs... But that's just a minor issue. > > > I think, if we can then manage to get CSS support in, we will get > > many new users. I personally don't need TABS. > > Yes, if I look around on the web for discussion about dillo, it's mostly > "it's fast, but it's useless because it can't do CSS." > > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

April 21, 2008

Future of dillo2

by corvid＠lavabit.com

Johannes wrote: > What is still missing for an official release apart from image maps? For one thing, I think text search needs to work for phrases. > I think, if we can then manage to get CSS support in, we will get > many new users. I personally don't need TABS. Yes, if I look around on the web for discussion about dillo, it's mostly "it's fast, but it's useless because it can't do CSS."

April 21, 2008

Future of dillo2

by Johannes.Hofmann＠gmx.de

On Mon, Apr 21, 2008 at 03:39:50PM +0000, corvid wrote: > I think the very first thing is to update the main dillo.org > page so that visitors will know that dillo shows signs of life. > > (or, wait, second. After all, there are patches that need reviewing :) > I agree. We should update the front page and make it a bit more optimistic :-). What is still missing for an official release apart from image maps? A problematic thing is that there are no official fltk2 packages for many distributions - or has that changed recently? I think, if we can then manage to get CSS support in, we will get many new users. I personally don't need TABS. Cheers, Johannes

April 21, 2008

Future of dillo2

by corvid＠lavabit.com

I think the very first thing is to update the main dillo.org page so that visitors will know that dillo shows signs of life. (or, wait, second. After all, there are patches that need reviewing :)

April 21, 2008

Future of dillo2

by jcid＠dillo.org

Hi there, This question: > What do you think of reviving use of the bug tracker > for the various little things that are easy to forget about? brings about a bigger topic: the future of dillo2. The goals of the project are: 1.- The democratization of internet information access 2.- Personal security and privacy 3.- High software efficiency I believe the key to achieving them are: a.- A larger development team. b.- A user community finding it useful. The vitality and development pace of the project are highly related to a). Point b), has been strong in the past; this is: judging from the received email feedback: http://www.dillo.org/emails.txt and from some surveys like: > On Sat, Aug 25, 2007 at 03:28:55AM +0200, Diego . wrote: > > DesktopLinux.com has published the results of its anual (desktop)linux poll > > The interesting thing is in the 3rd question: Which web browsers do you > > frequently use on your Linux desktop(s)? > > > > > http://www.desktoplinux.com/cgi-bin/survey/survey.cgi?view=archive&id=08132… > > > > The interesting thing is that a frozen project have enough users to win > > over 3 fully developed browsers :) (optimistic without cure) Point a) is key because it directly relates to the pace with which we pursue the moving target of Web browsing. Point b) is very important because if we end up with a browser that only a few people are willing to use, there's no point in it besides personal motivations. So: * Objective 1, is the result of a) and b). * Objective 2, needs the work of a). * Objective 3, is mainly achieved! How do we do it? i. - Increase the development team by adding 6+ new developers. ii.- Getting more involved with other projects. We could: * Attract new developers with a dillo2 release, leveraging the excellent documentation that we have. * Planning for CSS, floating objects and TABS. (this are important features to a nice browsing experience) * Coordinate with FLTK2, DSL (Damn small linux) and other lightweight distros, Debian installer team, MINIX3, etc. I don't want to miss the opportunity to thank the team for the excellent work during these months. Without you dillo2 wouldn't be so close to a release. Now, we need to plan, grow the number of developers, and bring dillo2 closer to its goals. These are just my views on the subject. Please share your thoughts, ideas and plans in this thread, so we can agree on a plan for the future. -- Cheers Jorge.-

April 20, 2008

Good news from fltk!

by jcid＠dillo.org

On Thu, Apr 17, 2008 at 05:28:34PM +0200, Johannes Hofmann wrote: > On Thu, Apr 17, 2008 at 08:53:23AM -0400, Jorge Arellano Cid wrote: > > On Tue, Apr 15, 2008 at 09:18:23PM +0200, Johannes Hofmann wrote: > > > Hi Jorge, > > > > > > On Tue, Apr 15, 2008 at 02:38:35PM -0400, Jorge Arellano Cid wrote: > > > > Hi Johannes, > > > > > > > > On Tue, Apr 08, 2008 at 05:01:41PM +0200, Johannes Hofmann wrote: > > > > > Hi Jeremy, > > > > > > > > > > On Tue, Apr 08, 2008 at 07:35:25AM +0100, Jeremy Henty wrote: > > > > > > > > > > > > On Sat, Apr 05, 2008 at 05:01:52PM +0200, Johannes Hofmann wrote: > > > > > > > > > > > > > Attached is a patch that enables double buffering for partial screen > > > > > > > redraws (this is where the flickering is most annoying). You will > > > > > > > need at least version r6079 of fltk2 to test. > > > > > > > > > > > > OK, I've upgraded to the latest FLTK2 snapshot (r6087) and your patch > > > > > > (fixed version). Looks OK so far. Any tests I should run? > > > > > > > > > > Mostly I would be interested whether it still feels fast. And any > > > > > regressions you observe, of course... > > > > > > > > I found something that looks like a bug in double buffering > > > > (it doesn't happen with the previous code). > > > > > > > > If you: > > > > > > > > - ./dillo-fltk about:splash > > > > - scroll down 1 or 2 inches. > > > > - browse to another URL. > > > > - press right mouse button over Back button and return to > > > > the first page. > > > > > > > > You'll end looking to the page through a window artifact in the > > > > control panel. i.e. The page rendering seems to start from below > > > > the control PANEL. > > > > > > > > Please give it a look. > > > > > > Patch 1 should fix the problem. > > > > Good! > > > > Committed. > > > > > > > > The second patch removes the push_clip() / pop_clip() pair that is no > > > longer necessary with double buffering (we only copy the needed > > > rectangle from the backBuffer anyway). > > > It might result in artifacts when running with > > > --disable-doublebuffer however. So I'm not sure if you want to > > > commit that part. > > > > I'd commit bracketed as: > > > > #ifdef NO_DOUBLEBUFFER > > push_clip (viewRect); > > #endif > > > > [Drawing code here...] > > > > > > #ifdef NO_DOUBLEBUFFER > > push_clip (viewRect); > > #endif > > > > > > Would it be OK? > > Yes, of course. Committed. -- Cheers Jorge.-

April 19, 2008

Collapsing whitespace

by Johannes.Hofmann＠gmx.de

On Thu, Apr 17, 2008 at 04:18:52PM -0400, Jorge Arellano Cid wrote: > Hi, > > Just submitted a patch I wanted to make long ago. It deals with > collapsing whitespace. Here's one example: > > http://www.w3.org/TR/REC-html40/intro/sgmltut.html#h-3.2.1 > > BTW, I also changed the bool_t to "unsigned char". Please test > whether it compiles cleanly. Compiles fine here (no warnings). Cheers, Johannes

April 17, 2008

Collapsing whitespace

by jcid＠dillo.org

Hi, Just submitted a patch I wanted to make long ago. It deals with collapsing whitespace. Here's one example: http://www.w3.org/TR/REC-html40/intro/sgmltut.html#h-3.2.1 BTW, I also changed the bool_t to "unsigned char". Please test whether it compiles cleanly. -- Cheers Jorge.-

April 17, 2008

Good news from fltk!

by Johannes.Hofmann＠gmx.de

On Thu, Apr 17, 2008 at 08:53:23AM -0400, Jorge Arellano Cid wrote: > On Tue, Apr 15, 2008 at 09:18:23PM +0200, Johannes Hofmann wrote: > > Hi Jorge, > > > > On Tue, Apr 15, 2008 at 02:38:35PM -0400, Jorge Arellano Cid wrote: > > > Hi Johannes, > > > > > > On Tue, Apr 08, 2008 at 05:01:41PM +0200, Johannes Hofmann wrote: > > > > Hi Jeremy, > > > > > > > > On Tue, Apr 08, 2008 at 07:35:25AM +0100, Jeremy Henty wrote: > > > > > > > > > > On Sat, Apr 05, 2008 at 05:01:52PM +0200, Johannes Hofmann wrote: > > > > > > > > > > > Attached is a patch that enables double buffering for partial screen > > > > > > redraws (this is where the flickering is most annoying). You will > > > > > > need at least version r6079 of fltk2 to test. > > > > > > > > > > OK, I've upgraded to the latest FLTK2 snapshot (r6087) and your patch > > > > > (fixed version). Looks OK so far. Any tests I should run? > > > > > > > > Mostly I would be interested whether it still feels fast. And any > > > > regressions you observe, of course... > > > > > > I found something that looks like a bug in double buffering > > > (it doesn't happen with the previous code). > > > > > > If you: > > > > > > - ./dillo-fltk about:splash > > > - scroll down 1 or 2 inches. > > > - browse to another URL. > > > - press right mouse button over Back button and return to > > > the first page. > > > > > > You'll end looking to the page through a window artifact in the > > > control panel. i.e. The page rendering seems to start from below > > > the control PANEL. > > > > > > Please give it a look. > > > > Patch 1 should fix the problem. > > Good! > > Committed. > > > > > The second patch removes the push_clip() / pop_clip() pair that is no > > longer necessary with double buffering (we only copy the needed > > rectangle from the backBuffer anyway). > > It might result in artifacts when running with > > --disable-doublebuffer however. So I'm not sure if you want to > > commit that part. > > I'd commit bracketed as: > > #ifdef NO_DOUBLEBUFFER > push_clip (viewRect); > #endif > > [Drawing code here...] > > > #ifdef NO_DOUBLEBUFFER > push_clip (viewRect); > #endif > > > Would it be OK? Yes, of course. Cheers, Johannes

April 17, 2008