Search results for "plugin" - Dillo-dev

hyphenation in dillo

by sgeerken＠dillo.org

On Wed, Nov 07, corvid wrote: > 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." So "pre-wrap" can be broken. Fixed. Sebastian

12 years

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). > > That can explain it. Well, then your patch might have a chance, if it's not really a socket issue. I'll give it a try later tonight. > > > 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). > > Yes, I found it in FLTK2. It turns out fl_wait in FLTK2 (in src/osx/run.cxx) is a complex function, while the equivalent incomplete function in 1.3 only a couple of lines. I think it's best let FLTK guys handle it. -- > 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

Re: [Dillo-dev] dillo-0.7.3-rc2

by Sebastian Geerken

On Sat, Aug 02, Jorge Arellano Cid wrote: > 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! Sorry, this patch was incomplete. I tried to extract the actual code changes, without some new debugging messages, but ommitted some things. The current CVS (which has now also the new debugging messages) contains now the complete changes. > 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! :). Jorge, I've not yet tagged the code, please do so when uploading the 0.8.0 code. Sebastian

21 years, 3 months

Re: [Dillo-dev] Proposal: United Dillo

by Indan Zupancic

Hello, In reply to Jyri Jokinen: > I'm not really qualified but that has never stopped me before eather. Sure you are, you're a user. > You want to get rid of dpid in favor of library plugins and make dillo > execute as one process only. I'm right this far? Well, yes, but the first part is a more personal issue, executing Dillo as one process only is the main purpose (plugins can be still seperated processes of course, but it's only not necessary anymore). > 20+ browsing windows spirited away. > > How many times has this happened with Mozilla, M-Firebird or just > about any other web browser? How much did you swear after it? Maybe I'm just lucky, but it only happened with a certain browser on another OS, but then it took the whole OS down with it, so... I see your point though, but it practically means that it should never crash, and if it doesn't, we won't hear you complain, right? :) > Right now I practically allways launch a new dillo when i need a new > browser window. It's just so much nicer when all those 50 or more > windows I often have open don't go at one blow if something bad happens. I did a little test, I compared the memory usage between opening new Dillo's and opening just new windows, both opened the splash screen. I opened 50 new Dillo's and 20 new windows (20 because I had to load the splash screen manually, and the memory usage is constant anyway). I used top and the total used memory numbers. One Dillo was already running (used to open new windows and precache stuff). Results: 1369 k/Dillo versus 795 k/window. This means that a new Dillo uses 1.7 times more memory than a new window. Considering that Dillo is meant to be able to run on computers with little ram, it isn't such bad idea to in some way optimize for it a bit. And as you said, you almost always open a new Dillo, so wouldn't it be nice if you open a new window when it's possible. In other words, if you have a nice old pc with 4 mb ram free you can open 3 extra Dillo's, or 5 extra windows. Your choice. But you say you often have 50 windows open, which need 75 mb ram, so I guess ram isn't an issue for you. >> What do you think about it? > > I think it's the stupidest idea since browser tabs. (*) Thanks for your (honest and to the point) oppinion, but really, 50 windows open, and you hate tabs? I have fluxbox, with tabs, so I can manage 50 open windows easily, but how do you do that without any tabs? In reply to Frank Gevaerts: Different displays is indeed an issue. It is easy to open a new Dillo when the display is different, but that means it should be possible to run multiple Dillo's at the same time. Adding the fact that some people would like to have it as an option, this means that Dillo can't rely on being the only one running, and thus undoing one of the biggest advantages. :( Is it possible to open a new window on another display as program? If so, it would be very easy to solve the multiple display problem. Thanks for the feedback, Indan

20 years, 11 months

Re: [Dillo-dev]New developer info

by Wim De Smet

Hi, I hope everyone will excuse me for posting in the same thread but it kind of seemed appropiate given the subject. I've also been playing around with dillo and I met Jorge and Sebastian at FOSDEM this year. Been lurking on the list for a while since I've got lots going on and didn't really have time. But as soon as I turn in my last exam this month I'd be happy to help out here or there. I was thinking about doing some simple kind of plugin to get started (are there any you want to work on?), but I'm fascinated with parsers and how they work, though I might not be very good at writing them, I'd be interested in working on that later on. Unfortunately my C skills aren't very good but I've got the basics and I also know lots of java (pretty useless here I guess :), some C++, and have experience scripting in shells and python. cheers, Wim

19 years, 5 months

Dillo + Partial Javascript Support

by 4winter＠informatik.uni-hamburg.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 alsa F wrote: > Rather than somebody trying to get full Javascript suport for Dillo, I was thinking along the lines of partial Javascript support. The bare minimum would be to access websites that use Javascript to allow logins to forums etc. If any more functionality could be added so that for example social network sites like facebook or bebo then that would be great.On a personal note, I don't mind the lack of CSS when displaying pages on Dillo due to the small screen size of the minibook so any Javascript concerning that is not necessary. There are several free ecmascript interpreters available, choosing one of them and putting it into a dillo plugin is the easy part. But in order to be useful the script needs the ability to manipulate the page content. And designing that part right is hard... Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkndo70ACgkQoPmwNWhsaZYfHgCeIIA+fSBS9AZJTk93OeAUpIiG OIAAn38AnWLOAm1BgrHjKWkLLkexgIvM =USWg -----END PGP SIGNATURE-----

15 years, 7 months

Re: [Dillo-dev]Viewing HTTP Headers with DPI

by Jorge Arellano Cid

On Wed, Jun 08, 2005 at 06:31:18AM +0800, Russell J. Wood wrote: > On Tue, Jun 07, 2005 at 05:13:11PM -0400, Jorge Arellano Cid wrote: > > On Sun, Jun 05, 2005 at 12:17:20PM +0800, Russell J. Wood wrote: > > > Hi all, > > > > > > Is it possible to view all request/response headers using DPI? > > > > That depends on the specific dpi. Please explain it further. > > Well, it's not for a specific DPI, I would like to know if it's possible to > get that information using DPI as if it is, I would like to write a plugin to > do it. > > It's just I didn't see much in the documentation about getting that information. Currently, dpip is not providing a dpi-command to request dillo for that info. Now, it can be done in a quite similar way that the cookies dpi (currently on testing) does. BTW, what for? (if not under NDA of course :) -- Cheers Jorge.-

19 years, 5 months

[Dillo-dev]Preparing the dillo-0.8.5 release.

by Jorge Arellano Cid

Hi there! A long time since the last post right? Well, don't worry, as always, a silent dillo-dev list means lots of stuff going on behind the scenes! I'm preparing the dillo-0.8.5 tarball now. This will hopefully be the last GTK1-based dillo to be released, as the next one will be FLTK2-based. The plan is to show a strong protoype in Dijon at the LSM 2005, and have it shortly thereafter ready for public consumption (after a play/test/fix/stabilize cycle on dillo-dev). Back to dillo-0.8.5: this release is mainly a bug-fix release. The final touches were just uploaded to current CVS. Please download it, test, and report back to the list on how it works. This will help me to make the tarball and release it ASAP. As currently I'm working on three source trees, getting rid of this one will certainly relieve my workload. The second tree is a rewrite of the plugin stuff under a cleaner design that's to be included in the FLTK2-tree. -- Cheers Jorge.-

19 years, 5 months

IPv6 and HTTPS (Re: release candidate for dillo-3.0.2)

by Johannes.Hofmann＠gmx.de

On Sat, Dec 03, 2011 at 09:23:41PM +0000, corvid wrote: > Axel wrote: > > IPv6 and HTTPS seem both to work independently, but HTTPS over IPv6 > > does not work. An example host would be the IPv6-only reachable server > > at https://jumper.deuxchevaux.org/. (Submitted to the bug database as > > bug #1023.) > > > > The same host with just HTTP (http://jumper.deuxchevaux.org/) works > > fine as well as does a randomly chosen (IPv4 :-) HTTPS website. > > > > OTOH with 3.0.1 it looks very similar and doesn't work either with > > IPv6 + HTTPS, so I think it's "just" a bug in Dillo, but not a > > regression in 3.0.2. :-) > > Is anyone in a sufficiently IPv6-ed environment that they can dig into > this at some point? I doubt it's worth making the current experimental HTTPS plugin IPv6 ready. We will need a more robust HTTPS solution at some point. Cheers, Johannes

12 years, 11 months

Re: [Dillo-dev] Re: Some news...

by Diego Sáenz

I have see the dpi code and think that it is a very good approach. Only one think: how do you integrate a plug-in without patch dillo? I known that dpi is not finished, but i am impatient. If the PIs can add menu entries to dillo menus it can be easy to start/call a PI when a menu entrie is clicked and the PI can ask some dillo state(like url below the mouse) or open a save dialog or etc using a dpi tag. A cfg file can asociate prefix(ftp://), sufix(.swf) and menu entries with PIs. It can be modified on PI install or be generated. There must be some code for dinamics menus in dillo for history yet. About PIs that render to a zone in a web page it can be done like Sylpheed-claws integrate dillo in it(GTK X sockets or something that i think). I hope to help something even if nobody ask. Diego. El Mon, 7 Jul 2003 15:35:30 -0400 (CLT) Jorge Arellano Cid <jcid(a)softhome.net> escribio: > > Hi! > > > > > This has been a very busy week. I didn't anticipate how much > > work the dpid (dpi daemon) integration could take. Don't panic > > though!, the code that binds it all is running (to some extent) > > in my machine. The time consuming problem is that while making > > the integration, a lot of design matters spring in, and they take > > a lot of time to solve. > > > > The good news is that it all starts to shape into a more clear > > design (the code is still hackish at parts, but it is clear what, > > where and how to fix it). > > > > While working the gory details of it, I realized it'd be a good > > idea to make the 0.7.3 release with what we have now (plus a > > little bug fix we're working on with Sebastian). That way, > > there'll be less pressure on us while polishing the new dpid > > implementation, and hey!, it's been a long time since our last > > release. > > > > I'll keep the CVS free of the dpid code until the 0.7.3 release > > is done. For the meanwhile, I'll provide a tarball to the new > > code. (and if I can't wrap the new code before Monday, I'll > > provide a link to the latest dpid testing tarball I have). > > > First, the final code for the 0.7.3 is on the CVS (unless you > find a bug in it). It will be released by Wednesday, so please > give it a hard test today and tomorrow! > > With regard to 0.8.0-pre (aka dillo with dpid), here's the good > news: > > * Finally I have a tarball that does bookmarks and downloads > with dpid (using wget)! It can handle multiple plugins and is > working smoothly. > > I want to add one more plugin (at least) and update the > documentation before commiting it to the CVS (after releasing > 0.7.3 of course). > > For those very interested in studying it, please review: > > http://dillo.org/download/dpid4.tgz > > (not my tarball but the dpid testing suite itself) > > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

21 years, 4 months

Dillo-dev search results for query "plugin"