Dillo-dev

Download

By thread

dillo-dev@mailman3.com

4 participants
11704 messages

Re: CSS loading, part 1

by Johannes.Hofmann＠gmx.de

Hi Jorge, On Fri, Dec 19, 2008 at 03:37:28PM -0300, Jorge Arellano Cid wrote: > Hi Johannes, > > The attached patch does better than the current way, it has > more consistency betweeen what's shown the first time and after > back and forward (at least with my test set). > > Please test it and apply to the css-proto tree. Thanks! Pushed to css-prototpe. > > I don't know what's to be done when multiple stylesheets are > specified, like in this site: http://www.lacuarta.cl. Are they > all supposed to be loaded? If that's the case, I'd like to load > them all and after that, make a single repush instead of one per > arrival. Yes, all stylesheets with a matching media type have to be loaded. I noticed a regression on http://src.opensolaris.org/source/ Maybe it's because now only one stylesheet is loaded? I agree that having just a single repush is probabely better. I don't yet fully understand the new logic and the difference to corvid's approach. Are the style changes in css.cc and css.hh intentional? Generally it would be good to keep whitespace only changes in separate commits. That simplifies reviewing and the search for faulty changesets. BTW. "hg bisect" is a fanatastic tool for that! (similar stuff exists for git too of course). > > If that scheme is implemented, then it'd be simple to extend > the code to parse this case: > > <style type="text/css" media="all"> > @import url('/style.css'); > </style> > > > BTW, it's a very nice feeling to see CSS working. Yes it's fun! Cheers, Johannes

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by Johannes.Hofmann＠gmx.de

On Fri, Dec 19, 2008 at 04:51:21PM -0300, Jorge Arellano Cid wrote: > On Fri, Dec 19, 2008 at 08:38:22PM +0100, Johannes Hofmann wrote: > > On Fri, Dec 19, 2008 at 03:50:56PM -0300, Jorge Arellano Cid wrote: > > > On Fri, Dec 19, 2008 at 06:55:07PM +0100, Johannes Hofmann wrote: > > > > On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > > > > > > > > > I was revising the autoconf docs and noticed that make rules should > > > > > prefix all sources with $(srcdir) to support separate builds[1]. We > > > > > don't do this, so here's a patch. > > > > > > > > Commited! (to http://freehg.org/u/dillo/main) > > > > @Jorge: I hope that's ok for you. > > > > > > Oh, sorry, I thought it was to css-prototype. > > > It was main dillo. > > > > Yeah, non-CSS changes should go into the main repository. They will > > end up in the css-prototype via the regular merges. > > That way we can avoid unnecessary merge conflicts. > > OK. > > BTW, did you try the CSS loading patch I sent you? I'm currently testing it. It's fun seeing CSS partly working isn't it? Cheers, Johannes

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by jcid＠dillo.org

On Fri, Dec 19, 2008 at 08:38:22PM +0100, Johannes Hofmann wrote: > On Fri, Dec 19, 2008 at 03:50:56PM -0300, Jorge Arellano Cid wrote: > > On Fri, Dec 19, 2008 at 06:55:07PM +0100, Johannes Hofmann wrote: > > > On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > > > > > > > I was revising the autoconf docs and noticed that make rules should > > > > prefix all sources with $(srcdir) to support separate builds[1]. We > > > > don't do this, so here's a patch. > > > > > > Commited! (to http://freehg.org/u/dillo/main) > > > @Jorge: I hope that's ok for you. > > > > Oh, sorry, I thought it was to css-prototype. > > It was main dillo. > > Yeah, non-CSS changes should go into the main repository. They will > end up in the css-prototype via the regular merges. > That way we can avoid unnecessary merge conflicts. OK. BTW, did you try the CSS loading patch I sent you? -- Cheers Jorge.-

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by Johannes.Hofmann＠gmx.de

On Fri, Dec 19, 2008 at 03:50:56PM -0300, Jorge Arellano Cid wrote: > On Fri, Dec 19, 2008 at 06:55:07PM +0100, Johannes Hofmann wrote: > > On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > > > > > I was revising the autoconf docs and noticed that make rules should > > > prefix all sources with $(srcdir) to support separate builds[1]. We > > > don't do this, so here's a patch. > > > > Commited! (to http://freehg.org/u/dillo/main) > > @Jorge: I hope that's ok for you. > > Oh, sorry, I thought it was to css-prototype. > It was main dillo. Yeah, non-CSS changes should go into the main repository. They will end up in the css-prototype via the regular merges. That way we can avoid unnecessary merge conflicts. Cheers, Johannes

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by jcid＠dillo.org

On Fri, Dec 19, 2008 at 06:55:07PM +0100, Johannes Hofmann wrote: > On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > > > I was revising the autoconf docs and noticed that make rules should > > prefix all sources with $(srcdir) to support separate builds[1]. We > > don't do this, so here's a patch. > > Commited! (to http://freehg.org/u/dillo/main) > @Jorge: I hope that's ok for you. Oh, sorry, I thought it was to css-prototype. It was main dillo. No problem! -- Cheers Jorge.-

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by jcid＠dillo.org

On Fri, Dec 19, 2008 at 06:55:07PM +0100, Johannes Hofmann wrote: > On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > > > I was revising the autoconf docs and noticed that make rules should > > prefix all sources with $(srcdir) to support separate builds[1]. We > > don't do this, so here's a patch. > > Commited! (to http://freehg.org/u/dillo/main) > @Jorge: I hope that's ok for you. No problem, I'll commit it too. -- Cheers Jorge.-

Dec. 19, 2008

[patch]: use $(srcdir) in Make rules

by Johannes.Hofmann＠gmx.de

On Wed, Dec 17, 2008 at 06:40:24PM +0000, Jeremy Henty wrote: > > I was revising the autoconf docs and noticed that make rules should > prefix all sources with $(srcdir) to support separate builds[1]. We > don't do this, so here's a patch. Commited! (to http://freehg.org/u/dillo/main) @Jorge: I hope that's ok for you. > > (Patch generated with Mercurial Queues, BTW.) Cool. As a result your name shows up properly in the history ;-) Cheers, Johannes

Dec. 19, 2008

revision control and other project infrastructure

by jcid＠dillo.org

On Wed, Dec 17, 2008 at 02:54:35AM -0700, Scott Scriven wrote: > Hello. Hi! > I noticed some recent messages about revision control and > possibly switching to a DVCS. This makes me happy. :) Yes, we're trying hg these days. > So, I was wondering about general project infrastructure... > things like bug trackers, todo lists, mailing lists, help forums, > release management, news, patch queues and code review, code > repositories, etc. Thanks for the QA job. Please bear in mind that most of the features are not there not because we don't want them but for lack of manpower. Although there're also a few ones rejected out of experience. > What I've found so far is the following: > > dillo.org: > - general project info > - release tarballs > - bug list > - FAQ Note, the bug track is not only a list, progress status is shown there as a percentage. Discussion is meant to happen in the mailing list. Another big asset of the project is the excellent doxygen documentation of Dillo Widget (the internal widget set). e.g. (from the main directory): doxygen cd html dillo index.html Just give it some browsing! As a matter of fact, with your review, it's clear to me that we need to communicate this better... > auriga.wearlab.de: > - mailing lists > - cvs > > freshmeat.net: release announcements > > freenode: IRC (inactive?) Yes, inactive. We may log in to discuss lively between developers, if the need arises. So far email has been enough for a year. > http://misc.andi.de1.cc/dillo/ : Packaging for Debian, Ubuntu, Openmoko > > http://www.hyperborea.org/software/dillo/ : Packaging for Red Hat > > http://freehg.org/u/dillo/css-prototype : Prototype CSS branch http://freehg.org/u/dillo/main/ (I'm yet to update the web site, and BTW, just today I got a time window to work on dillo again. I'm borrowing time from the high-priority CSS stylesheet loading to write these lines :) > > Is that about right? Did I miss anything? The current Plans page: http://www.dillo.org/Plans.html It shows in broad lines, what we're doing. More coarse grained than the bugtracker. With regard to a users forum, we once had dillo-users, but in the end it only served as a SPAM repository. I agree that requiring user subscription to ask a simple question is a stopper for lots of users. Maybe an online form, with a human-being test that forwards to dillo-dev can be a good compromise. Good ideas are welcomed. Sometimes we don't have the time to implement them, and that's the problem. Help is highly appreciated. -- Cheers Jorge.-

Dec. 18, 2008

revision control and other project infrastructure

by akemnade＠tzi.de

Hi, On Wed, 17 Dec 2008 02:54:35 -0700 Scott Scriven <dillo-dev(a)toykeeper.net> wrote: > Hello. > > I noticed some recent messages about revision control and > possibly switching to a DVCS. This makes me happy. :) > > So, I was wondering about general project infrastructure... > things like bug trackers, todo lists, mailing lists, help forums, > release management, news, patch queues and code review, code > repositories, etc. > > What I've found so far is the following: > > dillo.org: > - general project info > - release tarballs > - bug list > - FAQ > > auriga.wearlab.de: > - mailing lists > - cvs > just to mention: both are on the same host. you can also use for example cvs -z3 -d:pserver:anonymous@dillo.org:/sfhome/cvs/dillo There is also a forum functionality which is disabled at the moment. Greetings Andreas Kemnade

Dec. 17, 2008

revision control and other project infrastructure

by dillo-dev＠toykeeper.net

* corvid <corvid(a)lavabit.com> wrote: > Right, I didn't mean to imply a forum at the same place as the > repository. Scott mentioned user forums earlier in the msg, > and it caught my eye. Heh, I mean any general sort of way to communicate -- probably not something like phpBB. I was thinking more of a public place to ask questions and get answers... sort of like a living FAQ with email notifications. > 2) ask Jorge directly -- and of course he's busy. Dillo's site does have "email me" in a lot of places. :) > Then again, I see there was a dillo-users list which apparently > just got spam. Mailing lists can be pretty inconvenient sometimes. They're fine for extended or ongoing discussion, but they tend to turn away the people who only have one or two questions... and they tend to have a lot of noise -- spam, or discussions not everyone cares about. -- Scott

Dec. 17, 2008

Jump to page: