- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]dillo rendering redesign version 3

by Diego Sáenz

Very thanks for the fast answer. And thanks for the interesting features in new rendering. Diego / DarkSpirit . El Mon, 30 Aug 2004 20:07:39 +0200 Sebastian Geerken <s.geerken(a)ping.de> escribio: > On Mon, Aug 30, Diego S?enz wrote: > > Hi. I have some problems with rendering redesigns. They all versions crash just after run them. > > > > [...] > > See the attached mail, this should solve the problem. Will be fixed in > the next release, in a few days or so. > > Sebastian >

Sept. 1, 2004

[Dillo-dev]anyone plans to port dillo to gtk+-directfb-2.0?

by Calvin Yu

I'm porting dillo to gtk+-directfb-2.0. By now I have done some work and created new binary. But there are still some critical problems. If there are some persons who are dealing with similar work, we can share and exchange the experence. :)

Sept. 1, 2004

Re: [Dillo-dev]dillo rendering redesign version 3

by Sebastian Geerken

On Mon, Aug 30, Diego S?enz wrote: > Hi. I have some problems with rendering redesigns. They all versions crash just after run them. > > [...] See the attached mail, this should solve the problem. Will be fixed in the next release, in a few days or so. Sebastian

Aug. 30, 2004

Re: [Dillo-dev]dillo rendering redesign version 3

by Diego Sáenz

Hi. I have some problems with rendering redesigns. They all versions crash just after run them. Here gdb bt Starting program: /tmp/dillo-0.8.3-pre-dw-redesign-3/src/dw-test Allocation = (273, 478), vadj[0x808d318] = (0 - 478 - 100). Allocation = (273, 478), vadj[0x8094eb0] = (0 - 478 - 100). Program received signal SIGSEGV, Segmentation fault. 0x4019497e in g_slist_last () from /usr/lib/libglib-1.2.so.0 (gdb) bt #0 0x4019497e in g_slist_last () from /usr/lib/libglib-1.2.so.0 #1 0x401945f9 in g_slist_append () from /usr/lib/libglib-1.2.so.0 #2 0x0805a4ba in Dw_gtk_platform_add_idle (platform_ptr=0x8098be8, idle_func=0x80517c4 <Dw_render_layout_draw_resize_idle>) at dw_gtk_platform.c:127 #3 0x08051afa in Dw_render_layout_queue_resize (layout=0x809a4a8) at dw_render.c:936 #4 0x08054980 in p_Dw_widget_queue_resize (widget=0x80a4498, ref=0, extremes_changed=0) at dw_widget.c:1187 #5 0x080578d9 in Dw_page_set_width (widget=0x80a4498, width=277) at dw_page.c:680 #6 0x08053a7e in p_Dw_widget_set_width (widget=0x80a4498, width=277) at dw_widget.c:318 #7 0x08050d79 in a_Dw_render_layout_add_dw (layout=0x809a4a8, widget=0x80a4498) at dw_render.c:135 #8 0x0804f894 in main (argc=1, argv=0xbffffb04) at dw_test.c:287 It do not crash if i comment lines 90-95 and 127 in dw_gtk_platform.c but then it works bad. i unknown if this is a library versions problem. I am use Debian testing $ldd /tmp/dillo-0.8.3-pre-dw-redesign-3/src/dw-test libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x40028000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x40146000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x40179000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x4017c000) libdl.so.2 => /lib/libdl.so.2 (0x4019e000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x401a1000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401a9000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401b7000) libm.so.6 => /lib/libm.so.6 (0x4027e000) libc.so.6 => /lib/libc.so.6 (0x402a0000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) I hoppe this will be usefull. Greatings for the work in dillo and sory for my english. DarkSpirit/Diego El Mon, 30 Aug 2004 08:00:35 +0200 Sebastian Geerken <s.geerken(a)ping.de> escribio: > Hi, > > the newest version of the rendering abstraction prototype (at > <http://www.dillo.org/misc_files/dillo-0.8.3-pre-dw-redesign-3.tar.gz>) > does not contain anything fundamentally new, but features an > interesting application of the new design, a preview window. Just > press the mouse button on the button in the lower right corner of the > right viewport. > > Sebastian > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Aug. 30, 2004

[Dillo-dev]dillo rendering redesign version 3

by Sebastian Geerken

Hi, the newest version of the rendering abstraction prototype (at <http://www.dillo.org/misc_files/dillo-0.8.3-pre-dw-redesign-3.tar.gz>) does not contain anything fundamentally new, but features an interesting application of the new design, a preview window. Just press the mouse button on the button in the lower right corner of the right viewport. Sebastian

Aug. 30, 2004

[Dillo-dev]dillo rendering redesign version 2

by Sebastian Geerken

Hi, a new version of the rendering abstraction prototype can be downloaded at <http://www.dillo.org/misc_files/dillo-0.8.3-pre-dw-redesign-2.tar.gz>. The new version adds images, which are in the Gtk+ version realized with GdkRGB, we'll have to see how this is done in FLTK. Sebastian

Aug. 28, 2004

Re: [Dillo-dev]Porting dillo to another UI toolkit

by Sebastian Geerken

Hi, a prototype of the rendering abstraction can be downlaoded from <http://www.dillo.org/misc_files/dillo-0.8.3-pre-dw-redesign-1.tar.gz>. There are some notes in README-port in the tarball, which should describe anything you need for a port. This is very incomplete and buggy, but some may already take a look at it, and start writing an equally incomplete and buggy ported version. Of course, it may change, there will be additional methods to implement, but the existing part of the platform-specific definitions should be pretty stable. Sebastian

Aug. 25, 2004

[Dillo-dev]Invoke application upon clicking a link

by huy

Hello all, I would like to be able to click on a link and invoke a local executable. As you might already know, this is similar to the activeX IE or the shell model in mozilla. And this is for a quick and dirty demo, so security isn't an issue. Is there a way I can do this with dillo (short of modifying the source code). The HTML will be on the local machine too. Thanks all Huy

Aug. 21, 2004

[Dillo-dev]Porting dillo to another UI toolkit

by Sebastian Geerken

Hi, I intended to post this a bit later, not before some usable code is available, but I changed my opinion, it may be useful to outline, how porting will happen. The most complex part is certainly Dw, since it is tightly bound to Gtk+. By all means, I want to prevent, that there exist different versions of Dw, with different features (e.g., when the development of the Gtk+ version continues, while the FLTK version is developed), which are hard to integrate. For this reason (and others), I'm currently working on a redesign of Dw, which will make Dw toolkit independant. This is not the single goal of this redesign, it will also make some other features possible, e.g. a preview window, in which the whole page may be seen with reduced size, also, it will make reusage of Dw within graphical plugins possibel, and some more. (Actually, the idea for this design is already older, except the platform independency, but this was simple to add.) I'll soon (within a week or so) post the first usable version of it, which will only include a small program to test Dw, not dillo itself, the integration into dillo will be done later. However, it will already make it possible to start with the porting work. A documentation, which changes should remain small, is already attached. As for the actual port, the following steps should be done: 1. Realize the test program, but for another UI toolkit. This will still have to include Gtk+, because of the Gtk+ object model, but the new toolkit should be in control over the event processing. (Furthermore, GLib will, in this phase, still be needed.) What is needed for this step: (i) an implementation of DwRenderPlatform and DwRenderView, and (ii) ports of the modules Dw_style and Dw_tooltip. These will perhaps also be abstracted, see DwRender.txt for details. The rest should not be touched, if this should become necessary, this is a bug. The changes in Dw_style and Dw_tooltip should not be too hard, and these modules will not change much in the near future, so this simple approach for porting is reasonable in this case. The experiences made on this should be interesting, if the design of Dw_style and Dw_tooltip should be enhanced, as described as an idea in the attached document. 2. The second step (regarding Dw) should be to get rid of Gtk+ and GLib. Since a port to FLTK is planned, it makes sense to port the C code to C++, this would also make the code cleaner, since dealing with classes and interfaces in C (with the Gtk+ model) is quite fiddly. Details of this step have still to be clarified, but the features, GLib and Gtk+ provides, should be relatively easily replaced. Notice also, that I plan to make an own library of Dw (at least the core of it), most of it has already been finished, but the release has been delayed, because I assign a greater priority to the dillo project. For the rest of the port, I do not have any plans, but AFAIS, I see far less problems as for Dw. Sebastian

Aug. 20, 2004

Re: [Dillo-dev]why must FLTK?

by higuita

Hi On Fri, 6 Aug 2004 15:18:05 +0800, "Calvin Yu" <yuzenghui(a)people.com.cn> wrote: > The FAQ tells me that the developers are planning to port GUI to FLTK. > Who is so kind to tell me any alternatives? > I hear FLTK is very complex and not stable. the dillo dev team decide for fltk because the tests with gtk2 show that is too slower and heavier than gtk1, specially taking in account the size of all the gtk2 libs fltk was finishing the new version that would allow the use of unicode and is very light and fast its the goal of dillo to be the lightest and fastest browser possible, being secure, cross platform and as much standard complete as possible > If we port GUI to gtk+-directfb, we don't need X server any more. > It would save a lot of resources. could help the small devices, but also would make dillo useless for normal PCs, with X running also, many of the device builders can do this already if they want but the big issue about gkt2 is its size, footprint and slowness compared with gtk1 and fltk and how it affects dillo, not the presence of X11 cya higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Aug. 20, 2004