Search results for "plugin" - Dillo-dev

dillo-0.7.3-rc2

by Jorge Arellano Cid

Hi there! Today I was decided to upload 0.8.0-pre but found some problems with one plugin. At the same time Sebastian sent me a fix for the bug that delays 0.7.3 (very simple), so most probably our current CVS holds the final 0.7.3! Please give it a hard test. If everything goes fine, it'll be released by Tuesday or Wednesday. With regard to 0.8.0-pre, please expect it to be in CVS at announce time. I know I have delayed it a lot, but it comes with much more than what was anticipated (and I believe you'd prefer it to be working right! :). Cheers Jorge.- PS: Phil, Kelson: Please be prepared to upgrade your packages before 0.7.3 is announced. That is, if testing don't say otherwise! I'll let you know one or two days before the announcement.

21 years, 3 months

Re: [Dillo-dev]0.8.0 issue

by Andreas Schweitzer

Hi, > When I open Dillo up, if I try to open my bookmarks I get a hard lockup and have to 'xkill' dillo. > Anytime I try bookmarks after that, things work just fine. It is only the initial time when I open Dillo that I > have this issue. Anyone else have this issue? Yes - sounds very familar. BUT : lately it works here (for both FreeBSD 4.8-STABLE and 5.1-STABLE). There were issues with starting the dipd and/or bookmakrk plugin. Maybe there still is a race-condition. What you see when you start dillo a second time is that the dpi-system is already up and running. How fast is your machine ? And how busy is it ? Cheers Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198

20 years, 9 months

hyphenation in dillo

by corvid＠lavabit.com

Sebastian wrote: > On Mon, Sep 10, corvid wrote: > > I was looking at the src for http://distrowatch.com , and the > > source page is very wide -- wider than any lines, so far as I > > could see. > > There is one line, which is very long (number 54), but the current > release breaks this line into multiple ones. Can someone provide > details about the vsource plugin? The vsource page has <style type="text/css">PRE {white-space: pre-wrap} and the css2 spec says "If 'white-space' is set to 'pre' or 'pre-wrap', any sequence of spaces (U+0020) unbroken by an element boundary is treated as a sequence of non-breaking spaces. However, for 'pre-wrap', a line breaking opportunity exists at the end of the sequence."

12 years

Re: [Dillo-dev] dillo-0.8.6-rc1

by Jorge Arellano Cid

Hi Francis, Thanks for the good feedback. On Wed, Mar 22, 2006 at 09:21:21AM +0000, Francis Daly wrote: > On Tue, Mar 21, 2006 at 02:13:38PM -0400, Jorge Arellano Cid wrote: > > Hi there, > > > ... test and send feedback. > > Some minor thing that you might like to tidy before release: > > * ChangeLog has a few entries with a leading hyphen. Yes, this visually separates batches of patches by the same authors. > * ChangeLog says > > * Added dpi/downloads.cc (Default FLTK2-based GUI for downloads dpi). > and > * Made the downloads plugin dillo-cookie aware. > > It's only the *old* plugin which handles cookies. (And modifying the new > one to is more than just a two line addition, because the arguments are > counted in (I think) two other places.) But overall, it's no regression > from 0.8.5, so no problem. It just might be worth clarifying the > distinction. Ooops. This is a BUG! I'll clarify the distinction in rc2. > * README says > > Here's a list of some well known problems: > > * no FRAMES rendering > * no https -- read the FAQ to enable a protoype. > > while the code now defaults to https enabled. Change README or change > dpi/https.c > > If you choose to change README and you want to keep at least two problems, > you could mention "javascript" or "http authentication". But only if > you consider their absence a problem ;-) > > Leaving https enabled will get the code tested more, but will likely cause > a warning for each https: url accessed, unless the user's distribution > happens to store trusted root certs in /etc/ssl/certs. > > You can choose whether you want https.c polished more before being exposed > to the world. Possibly a note in README or FAQ saying "dillo reads root > certs from the directories /etc/ssl/certs or $HOME/.dillo/certs; they > should be named after the hash of the certificate subject name -- see > e.g. the openssl x509 documentation, '-hash' option for more information." Yes, this needs some fixes. I'll disable the https dpi as usual (it's too rough now, and it needs a conversion from dpi filter to dpi server too). Sending the users to dig the openssl x509 documentation is too much, and the https dpi hangs when there are concurrent https requests. As for the known problems, I'll add "http authentication". :-) > (Yes, I know, if I *really* cared, there'd be patches in this mail. But > I'm not sure if you're looking at releasing in a day or a week, and > think the things should be mentioned early so you can consider whether > you want to change any of them.) I think more or less one week. Until the release candidate is tested and not having new problems. -- Cheers Jorge.- PS: Your email reply was addressed to me, not to the list. (usually a MUA choice that needs a tweak)

18 years, 7 months

Re: [Dillo-dev]Using dillo on SourceForge

by Jeremy Henty

On Sat, Apr 09, 2005 at 07:20:46PM +0200, Andreas Kemnade wrote: > On Mon, 4 Apr 2005 20:34:55 +0100 > Jeremy Henty <jeremy(a)chaos.org.uk> wrote: > > > Is the SSL-enabled version of dillo-0.8.4 up to managing > > SourceForge accounts? ... > > You need some of these ssl-patches (with an older dillo) which do > not use the dpi interface Are you saying I need to check out a previous version of dillo and forward-port some patches? If so, which version and which patches? > As far as I understand, the https dpi plugin does not handle cookies > because the cookies do not find their way to cookies.c So you > probably have to wait for the cookies dpi. Hmm, what's the status of the cookies dpi? Thanks for your help. Cheers, Jeremy

19 years, 7 months

[Dillo-dev]Preparing the 0.8.1 release

by Jorge Arellano Cid

Hi guys, 0.8.1 is getting closer every day. It will feature what's currently in the CVS (basically the improved HTML bug detection and rendering). I'd love to be able to switch this dillo version from alpha to beta stable, but for that there's a lot of testing required. That is, the new parser (going to lots of sites and asserting there're no crashes), and the recently found problems with puppy linux and downloading and FTP (has anyone experienced trouble with these dillo plugins on their systems?). Please test our current CVS hardly, and tell us how it did. Thanks to Jim, who was the first one to send some feesback: > Wow! I can see a big improvement, lots of sites that rendered readably, > but 'iffy', are now much clearer and cleaner. Cheers Jorge.-

20 years, 6 months

dillo-2.2 has been released!

by corvid＠lavabit.com

Get it at http://www.dillo.org/download/dillo-2.2.tar.bz2 Some highlights of this release are: - a major overhaul of the cookies subsystem - a reimplementation of the Dillo Plugin (DPI) API - a configurable connection limit - various CSS improvements Anyone using cookies should definitely upgrade, as important security fixes were made in the process of rewriting the cookies module. Pretty much all of the changes that would be of interest to users are mentioned in the ChangeLog ( http://hg.dillo.org/dillo/file/tip/ChangeLog ) In configuration files: dillorc has new options http_max_conns and show_help, and the default for no_proxy has changed. keysrc has new options for save and for various motion commands. You can also use keysym values in the rules now. I think I have the website all updated except for the main page, and Jorge will do the freshmeat stuff.

14 years, 9 months

Re: [Dillo-dev] HTTPS support

by Andreas Kemnade

On Fri, 6 Jun 2003 01:42:25 +0300 (EEST) Madis Janson <madis(a)ats.cyber.ee> wrote: > > I wrote a http to https proxy and simple patch to make dillo to start this > up (when some https query is made) and forward https queries through unix > domain socket to the proxy. Server certificate chains verification is not > implemented (yet). > > It probably could be made into a dpi plugin in future, but currently dpi > seemed to lack some needed properties (like forwarding full http querys > with cookies to the proxy), which are used by the patch and proxy > interface. > Oh, yet another method to support ssl in dillo. Very interesting idea. I guess now it is time to find out which is the better one. Is there any ssl patch out there, which supports certificates? Greetings Andreas Kemnade

21 years, 5 months

Re: [Dillo-dev] Puppy Linux 0.9.1 has Dillo, works fine

by Garrett Kajmowicz

> Hi guys, > Just a comment because I started a thread a little while ago, that never > got resolved. > > The 0.8.x series of Puppy Linux had all the apps compiled against uClibc, > which saved about 1M but caused various compatibility problems. > One of those was the Dillo plugins not working right. > > That problem never got resolved, however it is now academic as far as Puppy > is concerned, as I recompiled everything against glibc, for Puppy 0.9.0 > (using Mandrake 9.2 as the host). That is too bad. My development system for Dillo is a chroot environment running off of uClibc. Regular glib and gtk were installed. If you are looking for a good distro to base your Linux distro off of, check out uwoody at www.uclibc.org - Garrett Kajmowicz

20 years, 4 months

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Fri, May 27, 2011 at 3:53 PM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Fri, May 27, 2011 at 03:25:32PM -0500, reza farivar wrote: > > On Fri, May 27, 2011 at 3:18 PM, Jorge Arellano Cid <jcid(a)dillo.org> > wrote: > > > > > On Fri, May 27, 2011 at 01:53:08PM -0500, reza farivar wrote: > > > > On Fri, May 27, 2011 at 12:46 PM, Benjamin Johnson < > > > obeythepenguin(a)gmail.com > > > > > wrote: > > > > > > > > > On Fri, 27 May 2011 13:38:43 -0400, reza farivar < > > > rf.opensource(a)gmail.com> > > > > > wrote: > > > > > > > > > > Yes. Well, the only plugin I could see is the save button on the > > > panel, > > > > >> and > > > > >> it can successfully navigate the filesystem and save a page > correctly. > > > > >> > > > > > > > > > > That one isn't a plugin, actually. Does the bookmarks button work? > > > > > > > > > > Yes, bookmarks work. (This is a bit of strange implementation of > > > bookmarks, > > > > no? took me a bit to find out difference of section and item) > > > > > > Good! > > > > > > If you can see the html page from the bookmarks, it means the > > > whole dpi framework is working on Mac; they communicate using > > > sockets. > > > > > > So it seems the main thing pending is socket support in fl_wait > > > for Mac (see my previous email). > > > > > > > Yes, I also think it's the source of this problem (see my other email). > > > > But what really perplexes me is that this happens only when I enter a URL > > manually. When I follow links from one page to another it never happens. > Are > > you guys using different (FLTK) functions when opening a new page or > > following a links (whether in the same tab or in a new tab)? > > No, but when you hit ENTER, FLTK has a chance to queue events > and zero-wait timeouts for the widget callback and necessary > stuff. OTOH, clicking a link goes another path (inside dillo). > > Can you point me to parts of code for either of these two code paths? Filename / line number should suffice. > > > And it seems that as Dillo "warms up" I get less of this problem... > > Timimg issues are moody. > e.g. Have you tried dillo listening a good mp3? :-) > > BTW, good you asked Manolo G. > (FWIW, FLTK2 has code for socket events in Mac). > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

13 years, 5 months

Dillo-dev search results for query "plugin"