- Dillo-dev - lists.mailman3.com

Pending issues
by jcid＠dillo.org Nov. 18, 2008

Nov. 18, 2008

Hi there, For those of you that wrote me willing to join the project as developers, and to the older ones too ;), here's a pending list of simple matters that need patches. Just in case! 1.- Check the "pending issues" dillo thread in FLTK' site: http://fltk.org/newsgroups.php?gfltk.general+T (search for "dillo") there you'll find a few and some hints too. 2.- CLI From dillo1: $ dillo1 --help Usage: dillo [OPTIONS] [URL|FILE]... Options: -x, --xid XID Open first Dillo window in an existing GtkSocket which window ID is XID (decimal). -v, --version Display version info and exit. -h, --help Display this help text and exit. -f, --fullwindow Start in full window mode: hide address bar, navigation buttons, menu, and status bar. -l, --local Don't follow links for this URL(s). -g, -geometry GEO Set initial window position where GEO is <width>x<height>{+-}<x>{+-}<y> -D, --debug-rendering Draw additionaly several lines in a web page, representing its structure. For debugging. URL URL to browse. FILE Local FILE to vie We need to mimic this. The only complex point is XID option. We don't yet know how to do window embedding by XID with FLTK2. Asking in FLTK general may help. I hope this gets somebody started. /me goes back, to CSS. -- Cheers Jorge.-

6 24

RE: what dillo2 runs on.
by CHalbersma.12＠westminster-mo.edu Nov. 17, 2008

Nov. 17, 2008

I've been able to get dillo2 to compile and run on a Damn Small Linux box. Obviously you need to compile fltk2 first but dillo2 seems to run although it does have some troubles. As soon as I find them I hope to be able to post a DSL package. CRH On Mon, Aug 18, 2008 at 02:24:21AM +0000, corvid wrote: > I want to get the status of everything in order to update > http://www.dillo.org/Compatibility.html for dillo2. > > Linux x86 - works > DragonFlyBSD - works > > Linux x86-64 - Justus was and is making snapshots, but I don't know whether > he uses them much. > Solaris 10 - Justus reported that it was running, but I believe it was just > a quick test. > OSX - Jorge reports that it works but is currently flaky. > > *BSD - Some of the mailing list traffic in October was devoted to getting > them working. Presumably it would have been mentioned here if they > had stopped working since, but... > > other - no idea. > > Looking back at what I just wrote, let me clarify that I meant that > dillo2-on-osx is flaky, not that Jorge is flaky :) > Debian Linux m68k works (cvs 14 Nov 2008) -- Qne's mind, once stretched by a new idea, never regains its original dimensions. -Oliver Wendell Holmes

1 0

Strange mouse/keyboard issues
by james＠bsdgroup.org Nov. 15, 2008

Nov. 15, 2008

Hello everyone, I have two somewhat similar issues related to dillo and losing keyboard/mouse focus. This could be an issue with fltk2. The first involves mouse clicks registering on different buttons. When running e17 if you start dillo in one virtual screen then switch to another and then back again, when you a user tried to click the back button instead the forward/home button was highlighted. The problem was fixed by forcing the dillo window to redraw. The second issue involves running dillo with dwm in one tag then switching to another tag and then back again. This time keystrokes seem to get lost. To fix this problem I have to toggle the dwm meta key (in my case this is the windows key, but it could be ctrl or alt instead). Has anyone else seen similar issues? Thanks. -- James Turner BSD Group Consulting http://www.bsdgroup.org

2 1

more css progress
by Johannes.Hofmann＠gmx.de Nov. 13, 2008

Nov. 13, 2008

Hi, the dillo-css-prototype is now able to parse a user stylesheet from ~/.dillo/style.css if it exists. This allows to modify the appearance in various ways. Currently I have the following in my ~/.dillo/style.css: body {margin-left: 10mm; margin-top: 10mm; background-color: #F5F5F5;} :link {color: gray !important; text-decoration: none; font-weight: bolder; } :visited {color: olive !important; text-decoration: none; font-weight: bolder; } Note that I'm no designer so the result may hurt your eyes! Cheers, Johannes

1 0

css progress
by Johannes.Hofmann＠gmx.de Nov. 12, 2008

Nov. 12, 2008

Hi, I just pushed my latest changes to the css prototype repository. The css parser from dillo-0.8.0-css-3 is now integrated and working. The user agent style is parsed from a char buffer (see CssContext::buildUserAgentStyle() in css.cc). Of course the code is still full of bugs and missing stuff, but it shows that things basically work as expected. This is starting to be fun! Cheers, Johannes

1 0

the Http_must_use_proxy change in CVS
by corvid＠lavabit.com Nov. 11, 2008

Nov. 11, 2008

Is something missing? It gives me a warning because we're sending it a char* now.

2 1

Greetings! -- With Patches :-)
by list-jcr＠designtools.org Nov. 11, 2008

Nov. 11, 2008

Hi list, I guess the best way to show up on a development list is with patches, so I've attached two of them. The diffs were created against cvs with: $ cd /home/jcr/dillo-src/dillo2 $ cvs -d$CVS_DILLO diff -u There was no mention on the site about the preferred diff format, but since I found a few patches in the list archives using "universal" I figured it was the safest bet. Though I've read the docs on dillo.org about submitting bug reports first, and then patches, the first of the patches below is to a feature that has not yet been committed. The first is to fix an over-sight in the following post/patch posted to this mailing list: http://article.gmane.org/gmane.comp.web.dillo.devel/6248 The above patch does not take into consideration font size, so the result can be microscopic/unreadable fonts. I've added the code to scale the font in the same way as you scale other fonts in dillo. Though I've read enough of the dillo docs and code to grasp the basics of formatting, I'm unsure if my formatting of the continuation (split line) is "correct" according to your standards. There are other places in the dillo UI where font handling is still incorrect and can result in unreadable fonts. Some of this is the fault of fltk, since as far as I know there is no ~/.gtkrc equivalent to set defaults for the tool kit. With luck, I'll find and fix them. The second patch is for BUG #832 --If I read things correctly, I'm supposed to file a bug report first, assign it to myself, and then send in patches. Unfortunately, I screwed up pasting my email address in the "submitter" section due to the fact that dillo doesn't actually copy selected text in a form (i.e. with the select/paste of the plain old X Window System). If you want to correct the submitter on the bug to my email address, it would be appreciated. There was no way I could correct it myself. On all popup menus in dillo, you have a non-typical and non-functional "label" (or better said "title") on the displayed popup menu. This was my first adventute into fltk, but according to the fltk2 docs, if you set the "label" of the popup menu to NULL, the "label" will not be shown. You can do it one of two ways, (1) setting the lable to NULL in the instantiation of the class or (2) using the ->label() member function to set the label to NULL. I opted for the former because it's more clean than the latter. Though there were "Accelerator" key bindings in the labels (such as "&PAGE OPTIONS" to get enable win32 meun-ish "<ALT>-P" activation), they don't actually work since the popup menu type ("POPUP123") means they are completely hidden until activated by the mouse buttons. There is still a popup menu placement issue (annoyance) with the Bug Meter when running dillo in full screen (or to the bottom edge of your screen) but it seems to be caused by the fltk "remember last selected" option. It does not properly realize the bottom edge of the screen/window, so some popup menu options are off-screen and you need a mouse-wheel movement to access them. Anyhow, I hope this helps. Kind Regards, Jon Index: src/dillo.cc =================================================================== RCS file: /sfhome/cvs/dillo/dillo2/src/dillo.cc,v retrieving revision 1.15 diff -u -r1.15 dillo.cc --- src/dillo.cc 10 Oct 2008 20:39:34 -0000 1.15 +++ src/dillo.cc 9 Nov 2008 19:43:45 -0000 @@ -21,9 +21,10 @@ #include <stdio.h> #include <unistd.h> #include <stdlib.h> +#include <math.h> /* for rint() */ #include <time.h> #include <signal.h> - +#include <fltk/Font.h> #include <fltk/Window.h> #include <fltk/TabGroup.h> #include <fltk/run.h> @@ -108,6 +109,16 @@ // WORKAROUND: sometimes the default pager triggers redraw storms fltk::TabGroup::default_pager(fltk::PAGER_SHRINK); + // Fix UI Fonts + fltk::Font *dfont = fltk::font(prefs.vw_fontname, 0); + if (dfont) { + fltk::Widget::default_style->textfont(dfont); + fltk::Widget::default_style->textsize( + (int) rint(14.0 * prefs.font_factor)); + fltk::Widget::default_style->labelfont(dfont); + } + + // Create a new UI/bw pair BrowserWindow *bw = a_UIcmd_browser_window_new(0, 0, NULL); Index: src/menu.cc =================================================================== RCS file: /sfhome/cvs/dillo/dillo2/src/menu.cc,v retrieving revision 1.23 diff -u -r1.23 menu.cc --- src/menu.cc 22 Oct 2008 18:05:38 -0000 1.23 +++ src/menu.cc 9 Nov 2008 19:43:46 -0000 @@ -308,7 +308,7 @@ if (!pm) { Item *i; - pm = new PopupMenu(0,0,0,0,"&PAGE OPTIONS"); + pm = new PopupMenu(0,0,0,0,NULL); pm->begin(); i = new Item("View page Source"); i->callback(Menu_view_page_source_cb); @@ -360,7 +360,7 @@ popup_url = a_Url_dup(url); if (!pm) { Item *i; - pm = new PopupMenu(0,0,0,0,"&LINK OPTIONS"); + pm = new PopupMenu(0,0,0,0,NULL); //pm->callback(Menu_link_cb, url); pm->begin(); i = new Item("Open Link in New Window"); @@ -404,7 +404,7 @@ if (!pm) { Item *i; - pm = new PopupMenu(0,0,0,0,"&IMAGE OPTIONS"); + pm = new PopupMenu(0,0,0,0,NULL); pm->begin(); i = new Item("Isolate Image"); i->callback(Menu_open_url_cb); @@ -478,10 +478,10 @@ new Divider(); i = new Item("Exit Dillo", ALT+'q', filemenu_cb, (void*)"ed"); pm->type(PopupMenu::POPUP123); + pm->label(wid->visible() ? NULL : "File"); pm->end(); } - pm->label(wid->visible() ? NULL : "File"); a_Timeout_add(0.0, Menu_popup_cb2, (void *)pm); } @@ -498,7 +498,7 @@ popup_url = a_Url_dup(url); if (!pm) { Item *i; - pm = new PopupMenu(0,0,0,0,"&BUG METER OPTIONS"); + pm = new PopupMenu(0,0,0,0,NULL); pm->begin(); i = new Item("Validate URL with W3C"); i->callback(Menu_bugmeter_validate_w3c_cb); @@ -536,9 +536,9 @@ dFree(history_list); if (direction == -1) { - pm = new PopupMenu(0,0,0,0, "&PREVIOUS PAGES"); + pm = new PopupMenu(0,0,0,0,NULL); } else { - pm = new PopupMenu(0,0,0,0, "&FOLLOWING PAGES"); + pm = new PopupMenu(0,0,0,0,NULL); } // Get a list of URLs for this popup

3 9

Re: patch: middle-click submits in new window/tab
by jcid＠dillo.org Nov. 10, 2008

Nov. 10, 2008

On Mon, Oct 20, 2008 at 02:49:41PM +0000, corvid wrote: > I could say that it was for the sake of consistency with link behavior, > but really it was because it seemed like a dilloishly simple way > to get the equivalent of pages-remember-form-data. The consistency part is a strong argument. Also interesting is the way we can have a workaround to remember form data, before a more usual way of handling it is implemented. > > (But: who will ever discover that it exists or recognize what it > makes possible?) It may be stated in the FAQ. > 1) fltkui: it might be better to stuff all of the button event stuff > into a bag like fltkviewbase/layout do with EventButton. It certainly > looks nicer having something like a shift mask hidden away in a nice > tidy box, but I wasn't sure that it was actually worth doing. Hmm, I'd say if it's going to be a definitive patch, it's worth the effort. > 2) form: carrying around buttonNo+shifted for a long time > is not pleasing, but oh well. Agreed. Now that Johannes is interested in implementing FORM "memory", I'd say it can be stored in an URL/form-data array. I haven't checked how other browsers (e.g. FF) solve the problem of privacy (aka. when it's desirable to remember data), but most probably a quick look will shed some light. BTW, I can't compile the patch here because: make[2]: Entering directory `/home/jcid/C/Dillo/d2/dillo2-cur/test' form.cc: In member function 'void form::Form::addButtonResource(const char*, dw::core::ui::ButtonResource*, const char*)': form.cc:241: error: cannot allocate an object of abstract type 'form::Form::FormClickedReceiver' form.hh:124: note: because the following virtual functions are pure within 'form::Form::FormClickedReceiver': ../dw/ui.hh:338: note: virtual void dw::core::ui::ButtonResource::ClickedReceiver::clicked(dw::core::ui::ButtonReso urce*, int, int) make[2]: *** [form.o] Error 1 make[2]: Leaving directory `/home/jcid/C/Dillo/d2/dillo2-cur/test' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jcid/C/Dillo/d2/dillo2-cur' BTW2: * The patch changes from "Activate" to "Clicked" signal. * It also seems to change the logic in DilloHtmlInput::activate() - it makes me wonder whether pressing enter on other form widgets may submit. Anyway, it'd be good if you can coordinate with Johannes and decide what approach to take, and send a new patch for it. I'd prefer Johannes to keep working in the CSS front, and you to make the definitive patch, but this is for you guys to decide. -- Cheers Jorge.-

3 3

patch: prefs.vw_fontname as fltk ui's default font
by corvid＠lavabit.com Nov. 10, 2008

Nov. 10, 2008

I was changing the font in a few more places that can take arbitrary user text -- and then having to change it for neighbouring things so that the difference isn't too jarring -- and I reached the point where it seemed like it may be best just to change the font for everything.

3 4

patch: click elsewhere on page, fltk widget loses focus
by corvid＠lavabit.com Nov. 10, 2008

Nov. 10, 2008

{my usual dw disclaimer}, but it's been working just fine so far.

3 2