- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] dillo chat in Logroño/La Rioja/Spain

by Diego .

Ok, but with FALSE (DwPage owns a button that owns the image) the button fail to draw the alt text when can not load the image and do not use width and height atributes of the html tag. Using your patch and seting the parameter to TRUE it use width, height and alt, but do not redraw alt text. Without your patch dillo segfaults if that parameter is true. Diego. 2006/12/2, Jorge Arellano Cid <jcid(a)dillo.org>: > > Hi Diego, > > On Fri, Dec 01, 2006 at 02:23:01AM +0100, Diego . wrote: > > Very thanks for the fast patch and the advices. > > One question ¿In Html_input_image why is the function Html_add_new_image > > called with the FALSE parameter? > > Quick answer: > > Because the image is embedded inside a button that's already > inside the DwPage. > > In other words: there's no need to add the image to the DwPage > because the button "owns" the image (think of an object), thus > only the button object needs to be added. > > -- > Cheers > Jorge.- >

Dec. 5, 2006

Re: [Dillo-dev] dillo chat in Logroño/La Rioja/Spain

by Jorge Arellano Cid

Hi Diego! On Wed, Nov 29, 2006 at 05:44:45PM +0100, Diego . wrote: > Hello. I am Diego Sáenz. I use this mail address now (I had mail problems > and lost some mails, but i have read them in the list archive). I am > associate of AULIR (Asociacion de Usuarios de GNU/Linux de La Rioja) a > spanish LUG and will give a chat about how to wrote dillo plug-ins. I will > explain a few the dillo internals too. There are not very much programers in > AULIR(one of them program anjelica.sourceforge.net) but i will try to wake > interest about dillo. > > Any advice for the chat? Yes, just try to put up the example code, and directions on how to run it in a web site a couple of days before the chat, and ask your audience to try the example prior to the chat. That way they can experiment and play with what you're going to explain instead of having to grasp it in abstract. Trying to get all the details of dpi without experimenting with it beforehand can be tough. > I will try to show a preferences plug in as example. > Is the bug #695 solved somewhere? No, but I made a quick hacky patch for you! :-) It's not as clean and tested as I'd like, but OTOH it would not surprise me if it ends being a good solution. Please send some feedback on how it works. > i think i will need to use it for a > feature of the plug in. Here you are: -------------------------------------------------------------------------- diff -pru dillo/src/html.c dillo-cur/src/html.c --- dillo/src/html.c 2006-04-08 08:16:46.000000000 -0400 +++ dillo-cur/src/html.c 2006-11-29 16:00:40.000000000 -0300 @@ -3717,10 +3717,19 @@ static DwWidget *Html_input_image(DilloH DilloUrl *url = NULL; DwStyle style_attrs; const char *attrbuf; + DwTooltip *tooltip; if ((attrbuf = Html_get_attr(html, tag, tagsize, "src")) && (url = Html_url_new(html, attrbuf, NULL, 0, 0, 0, 0))) { button = a_Dw_button_new (0, FALSE); + + /* add the tooltip to the button holding the image */ + if (prefs.show_tooltip && + (attrbuf = Html_get_attr(html, tag, tagsize, "title"))) { + tooltip = a_Dw_tooltip_new_no_ref(attrbuf); + HTML_SET_TOP_ATTR(html, x_tooltip, tooltip); + } + a_Dw_page_add_widget (DW_PAGE (html->dw), button, html->stack[html->stack_top].style); gtk_signal_connect(GTK_OBJECT(button), "clicked_at", @@ -3728,6 +3737,7 @@ static DwWidget *Html_input_image(DilloH a_Dw_button_set_sensitive(DW_BUTTON(button), FALSE); /* create new image and add it to the button */ + style_attrs = *html->stack[html->stack_top].style; if ((Image = Html_add_new_image(html, tag, tagsize, &style_attrs, FALSE))) { /* By suppressing the "image_pressed" signal, the events are sent -------------------------------------------------------------------------- > > ps: i hoppe that this do not seem spam* Just disable the HTML mail and spam filters will not frown on you. -- Cheers Jorge.-

Nov. 29, 2006

dillo chat in Logroño/La Rioja/Spain

by Diego .

Hello. I am Diego Sáenz. I use this mail address now (I had mail problems and lost some mails, but i have read them in the list archive). I am associate of AULIR (Asociacion de Usuarios de GNU/Linux de La Rioja) a spanish LUG and will give a chat about how to wrote dillo plug-ins. I will explain a few the dillo internals too. There are not very much programers in AULIR(one of them program anjelica.sourceforge.net) but i will try to wake interest about dillo. Any advice for the chat? I will try to show a preferences plug in as example. Is the bug #695 solved somewhere? i think i will need to use it for a feature of the plug in. Diego. ps: i hoppe that this do not seem spam* *

Nov. 29, 2006

Re: invalid (?) relative url resolve issue +patch

by Jorge Arellano Cid

Hi, On Wed, Nov 29, 2006 at 12:47:39AM +0100, Schilter Roland wrote: > Hello, > first of all, thanks for dillo :) ;) > I think I found a bug or at least, a misbehaviour that is handled in famous browsers differently. > I looked through the code and finally figured out where to change code to get the expected behaviour. > (Took some time though :p ) > > I need to mention that I didn't read the RFC2396 about URIs and I have the feeling that the implementation > in dillo may be according to specifications but nevertheless, i couldn't browse several sites... :) > > The problem is, if a `href' attribute of html-tag `a' starts only with a query (`?test') > then the path of the baseurl is only taken until the last slash: > > <a href="?test">test</a> while the baseurl being `www.example.com/example' > > this link will resolve to www.example.com/?test although I expected it to go to www.example.com/example?test Give a look to RFC-2396 C.1 Normal examples: base = http://a/b/c/d;p?q#f relative = ?y resolved => http://a/b/c/?y Dillo passes all those tests, including the abnormal section. Ah and we also test for these extra tests: http://www.ics.uci.edu/~fielding/url/test2.html http://www.ics.uci.edu/~fielding/url/test3.html http://www.ics.uci.edu/~fielding/url/test4.html http://www.ics.uci.edu/~fielding/url/test5.html HTH. -- Cheers Jorge.-

Nov. 29, 2006

Re: [Dillo-dev] The sound of silence

by Jorge Arellano Cid

Hi, On Mon, Nov 27, 2006 at 02:11:18AM +0200, Joonas Saarinen wrote: > Hello, > > It has been almost two months of silence on this list and I thought to > ask how are you doing? :) > > Anything new about the "Campaign to help Dillo survive"? Etc. This is a very appropiate question. :-) The campaign to help Dillo survive has not attracted new funders, and the donations amount near EUR 250. This clearly doesn't change a bit the project status. People in the embedded market want a small featured browser, but don't want to invest in it. This is: if we develop it they'll use it, but there's not much interest in funding the development. From a business perspective it makes sense. Investing in Dillo to make a full featured embedable web browser of it, is a three years plan (and who knows what the Web will look like in three years). Now if they only need an embedable web browser that evolves into a full-featured one. They could start deploying it in a year. This is a business opportunity indeed, but it depends on a company having a client demanding it; here using Dillo fits the bill. On the technical side, the port to FLTK2 is almost finished, and has been a surprisingly smooth transition, without surprises, going on as planned (except that we planned for some surprises!). OTOH development is progressing at very slow pace because we, the core developers, can't work full time on it, and spare time is scarce. From a community perspective, it's interesting to notice that there's a need for a lightweight web browser (Think of OLPC, firefox's users demands for less features and smaller footprint, help systems, a thin client for web apps., the embedded market: cell phones, PDAs etc). Now, if not enough users are willing to support development with money, the funding may only come from the business area, but business don't invest with regard to users' needs, but with regard to ROI. BTW, another source of funding is governments, but in seven years, not a single email has arrived from that source ;-). There we are. -- Cheers Jorge.-

Nov. 29, 2006

The sound of silence

by Joonas Saarinen

Hello, It has been almost two months of silence on this list and I thought to ask how are you doing? :) Anything new about the "Campaign to help Dillo survive"? Etc.

Nov. 27, 2006

Re: [Dillo-dev] Re: [Fwd: Dillo article precisions]

by Jorge Arellano Cid

Hi, On Wed, Oct 04, 2006 at 12:23:18PM -0600, Alan Carvalho de Assis wrote: > Hi Jorge, > I hope some company to sponsor Dillo soon. > > BTW, do you have some observation to be add in campaign's document? It has shaped very well! A few observations: * I'd put FLTK2 instead of FLTK FLTK1 is different and Dillo doesn't compile with it. * FLTK2 comes with text antialiasing and UTF8 A couple of features already working in dillo-fltk2! (this may be pointed up there) * For further information, and contact, please point them to my email address (jcid(a)dillo.org) > Do you think to contact the company which contacted you three years ago? Most probably yes. Although they're trying to "open source" their own platform, investing on a side technology is a good diversity safeguard they'll probably want to consider. -- Cheers Jorge.- PS: please don't CC' me. I do read dillo-dev!

Oct. 4, 2006

Re: [Dillo-dev] Re: [Fwd: Dillo article precisions]

by Alan Carvalho de Assis

Hi Jorge, I hope some company to sponsor Dillo soon. BTW, do you have some observation to be add in campaign's document? Do you think to contact the company which contacted you three years ago? Cheers, Alan

Oct. 4, 2006

Re: [Fwd: Dillo article precisions]

by Jorge Arellano Cid

Hi Henry, On Tue, Oct 03, 2006 at 02:30:33PM -0700, Henry Kingman wrote: > Hi Jorge, > > I tried to update our article with some of the details you sent. > > Thanks, and good luck with the Dillo project! I hope you find funding. Thanks for the corrections. One important precision: the dillo project needs at least two core developers working on it fulltime. Not only me. If there's only one person working full time on it, it's not enough to keep the pace of evolving technologies. That's what I meant when writing: > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. I find this paragraph misleading: "Alternatively, Cid says he will release the FLTK2 port if he finds enough funding to be able to continue working fulltime on the port himeself. He said, "Given the current situation, the best option seems to be to remain closed until funding happens." and it's not true. Please make the correction. -- Cheers Jorge.- > > -Henry > > cc: Rick, executive editor > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 > > > > > > > >-------- Original Message -------- > >Subject: Dillo article precisions > >Date: Tue, 3 Oct 2006 09:40:28 -0400 > >From: Jorge Arellano Cid <jcid(a)dillo.org> > >To: Rick Lehrbaum <rick(a)linuxdevices.com> > >CC: Dillo mailing list <dillo-dev(a)lists.auriga.wearlab.de> > > > >Hi Rick, > > > > It's being a long time since my last article at linuxdevices, > >receive my greetings from Chile! > > > > With regard to the new article: > > > > http://linuxdevices.com/news/NS4370323584.html > > > > It caught me by surprise. There was a thread in dillo-dev and > >some users suggested that campaign. I was commenting on gross > >factual mistakes in the wiki when it was announced that an > >article was live at linuxdevices. > > > > It's good to see our users' interest in keeping the project > >alive, so I'll comment the article here so you can correct and > >improve the article: > > > > > >>A project to create an ultra-lightweight web browser for use in > >>embedded devices and other resource-constrained hardware has > >>issued a plea for financial help. The Dillo Project says it needs > >>to find a corporate sponsor in order to add anti-aliased text, > >>CSS, Javascript, and internationalization/localization support. > > > > We've almost finished the port to FLTK2, and it already has > >anti-aliased text. (Dillo doesn't compile with FLTK1) > > > > FLTK2 uses UTF8 and provides antialiasing so it solves the > >problem of using GTK1 (this was one of the reasons for GTK1 to go > >GTK2). > > > > UTF8 also makes it easy to add i18n and l10n without breaking > >things inside the browser. > > > > I point this technical details because unofficial patches have > >been developed for antialiasing, i18n and l10n for GTK1. This is > >a good workaround but not a long term solution. > > > > > >> > >>(Click for larger screenshot of Dillo) > > > > Here you'll find a screenshot of dillo-fltk2: > > > > http://www.dillo.org/test/ph2.png > > > > (it shows antialiasing) > > > > > >> > >>Dillo is a very lightweight (about 350 KB) browser supporting a > >>subset of HTML, CGI, SSL, and cookies. > > > > And plugins. > > + Images (GIF, PNG and JPEG) > > > >> Dillo is not really > >>practical for browsing the modern Internet, due to missing > >>support for frames, CSS, Javascript, and other commonly used > >>standards and protocols. It also lacks support for anti-aliased > >>text, something even Linux desktop users have long taken for > >>granted, and appears to have only rudimentary HTML error handling > >>capabilities. > > > > The HTML error handling has improved a lot (the bug meter can > >atest that), but yes, error handling is not as advanced as with > >Firefox. > > > > Anyway, sometimes there're pages with a few hundred mistakes > >handled gracefully. ;-) > > > > > >>Nonetheless, Dillo is extremely fast and lightweight, using less > >>memory in some cases than popular text-based browsers such as > >>lynx. And, since it supports CGI, it could be useful as a > >>framework for simple device interfaces based on Web standards, > >>such as survey kiosks and other closed, "walled garden" > >>applications. > > > > BTW, the new Dillo with a statically linked FLTK2 is about > >820 Kilobytes. > > > >> > >>Additionally, Dillo is popular with web developers due to > >>excellent HTML error reporting. > > > > :-) > > > > > >> > >>Dillo is expected to gain support for anti-aliased text after its > >>development team completes a port to FLTK (fast light toolkit, > >>aka "fulltick"). > > > > [Already there, see above] > > > >> However, founder Jorge Arellano Cid appears > >>adamant that funding be located prior to release of his > >>nearly-complete FLTK port, according to a "save Dillo" campaign > >>page hosted here. > > > > True. > > > > The situation is this: there're two core developers. We need at > >least to be both working on Dillo full time (ideally three devs.) > >otherwise the project would lag behind the moving target that > >Internet browsing is. > > > > Sebastian (the other core developer) is employed fulltime in > >Germany so he has almost no time to Develop. I don't have funds > >to keep on working fulltime too, so if there're no funds the > >project will loose the main developers and their knowledge. > > > > With regard to releasing. That's what I've done for 6+ years > >with GTK1 and no funding happened ;-). > > > > If there were more interested developers in working with Dillo > >(lets say 6 serious and qualified people) I would consider > >releasing because the project could advance in that case. > > > > Believe it or not I asked in dillo-dev, and there was only one > >answer from a dev that could put 4 hours/week and that had no > >FLTK2 knowledge nor on Dillo internals. > > > > Given the current situation, the best option seems to remain > >closed until funding happens. > > > > > >> > >>Other ongoing Dillo development efforts reportedly include CSS > >>support (said to be "70 percent complete") and JavaScript > >>support, as well as additional internationalization (I18n) and > >>localization (l10n) features. > > > > I reported 70% on CSS. This is on the FLTK2 branch, not from > >external efforts. > > > > The interesting part is that we paved the way for all these in > >the newest branch, so now it's much easier to develop them over > >the new code base than with the old branch. > > > > A rough timeline estimation would be near 2 years to have the > >whole set: antialiasing, CSS, I18n, l10n, Frames, Tabs, SSL and > >good Javascript. > > > > We could make a release in 6 months and thenceforth go on > >incrementally adding features in any desired order (probably this > >would be up to the sponsors' needs). > > > > > >>Additional details about Dillo can be found on Dillo's official > >>funding presentations page. For additional background, be sure to > >>read Cid's 2002 introduction to the browser, here. > >> > >>The Dillo project previously sought funding in February of 2004, > >>and was successful in obtaining a one-time grant through the > >>Linux Fund. > > > > > > Thanks a lot for your time and commitment. > > > > > > > -- > Henry Kingman, senior editor > LinuxDevices.com > Ziff Davis Internet > 775 625-4547 >

Oct. 4, 2006

Re: [Dillo-dev] Dillo article precisions

by R.L. Horn

On Tue, 3 Oct 2006, Jorge Arellano Cid wrote: > Believe it or not I asked in dillo-dev, and there was only one answer > from a dev that could put 4 hours/week and that had no FLTK2 knowledge > nor on Dillo internals. I'd be willing to put some time in on the project. No FLTK2 experience, but it's yet another wretched event-driven-interface widget thing (yawediwt), so how hard can it be?

Oct. 3, 2006