- Dillo-dev - lists.mailman3.com

modifier keys (Re: [Dillo-dev] Two bugs in the Dillo GUI (both Mac and ubuntu))

by corvid＠lavabit.com

I wrote: > Can anyone with windows keys verify that they don't set FL_META? > There _is_ code for: > > // For the first few years, there wasn't a good consensus on what the > // Windows keys should be mapped to for X11. So we need to help out a > // bit and map all variants to the same FLTK key... > switch (keysym) { > case XK_Meta_L: > case XK_Hyper_L: > case XK_Super_L: > keysym = FL_Meta_L; > break; > case XK_Meta_R: > case XK_Hyper_R: > case XK_Super_R: > keysym = FL_Meta_R; > break; > } > > and maybe there's something going on somewhere that I haven't noticed. > I ask because perhaps we'll want to open an STR to get FL_META set. I think I see what happens. On X (well, x.org, anyway), it apparently comes through for free as the Mod4Mask bit in XButtonEvent.state, so expecting to see the word 'meta' somewhere was no good.

Aug. 22, 2011

modifier keys (Re: [Dillo-dev] Two bugs in the Dillo GUI (both Mac and ubuntu))

by corvid＠lavabit.com

I wrote: > By the way, the only mention of FL_META in Fl_x.cxx is > > # ifdef __sgi > // get the meta key off PC keyboards: > if (fl_key_vector[18]&0x18) Fl::e_state |= FL_META; > # endif > > I'd assumed that, for FLTK under X, Meta was a synonym for Alt, > or maybe the windows keys or something (which I don't have). Can anyone with windows keys verify that they don't set FL_META? There _is_ code for: // For the first few years, there wasn't a good consensus on what the // Windows keys should be mapped to for X11. So we need to help out a // bit and map all variants to the same FLTK key... switch (keysym) { case XK_Meta_L: case XK_Hyper_L: case XK_Super_L: keysym = FL_Meta_L; break; case XK_Meta_R: case XK_Hyper_R: case XK_Super_R: keysym = FL_Meta_R; break; } and maybe there's something going on somewhere that I haven't noticed. I ask because perhaps we'll want to open an STR to get FL_META set.

Aug. 22, 2011

Two bugs in the Dillo GUI (both Mac and ubuntu)

by corvid＠lavabit.com

I wrote: > Back in June, reza wrote: > > 4. This one is more of a feature request. Like most Mac applications, the > > shortcuts should work with Command key instead of control key. (I know it's > > low priority, and I might give it a shot myself later on). > > I'm wondering whether it would be helpful to mention in keysrc that > meta = command, or would that already be known by (or at least exceedingly > obvious to) everyone using osx? By the way, the only mention of FL_META in Fl_x.cxx is # ifdef __sgi // get the meta key off PC keyboards: if (fl_key_vector[18]&0x18) Fl::e_state |= FL_META; # endif I'd assumed that, for FLTK under X, Meta was a synonym for Alt, or maybe the windows keys or something (which I don't have).

Aug. 22, 2011

Two bugs in the Dillo GUI (both Mac and ubuntu)

by corvid＠lavabit.com

Back in June, reza wrote: > 4. This one is more of a feature request. Like most Mac applications, the > shortcuts should work with Command key instead of control key. (I know it's > low priority, and I might give it a shot myself later on). I'm wondering whether it would be helpful to mention in keysrc that meta = command, or would that already be known by (or at least exceedingly obvious to) everyone using osx? BTW, 1.3 has #ifdef __APPLE__ # define FL_COMMAND FL_META ///< An alias for FL_CTRL on WIN32 and X11, or FL_META on MacOS X # define FL_CONTROL FL_CTRL ///< An alias for FL_META on WIN32 and X11, or FL_CTRL on MacOS X #else # define FL_COMMAND FL_CTRL ///< An alias for FL_CTRL on WIN32 and X11, or FL_META on MacOS X # define FL_CONTROL FL_META ///< An alias for FL_META on WIN32 and X11, or FL_CTRL on MacOS X #endif // __APPLE__ although I don't think this can do us any good in our circumstances.

Aug. 22, 2011

right_click_closes_tab

by corvid＠lavabit.com

dillorc has: # A mouse's middle click over a tab closes the Tab. # With mousewheel mouses, right click feels way better (set to YES). #right_click_closes_tab=NO I'm thinking that if the default is no and we start by talking about middle click, it would make the most sense to call it middle_click_closes_tab.

Aug. 22, 2011

Re: dillo close dialog and fluxbox on dual head

by higuita7＠yahoo.co.uk

Hi again >> if i do the same thing for all other dillo dialogs, like open >> file, search (title ask), etc , i fluxbox puts the window in the >> configured head. If i try to set the position and head, fluxbox puts the >> dialog in the right position, but in the wrong head. >How are you instructing fluxbox to do this? I can edit the ~/.fluxbox/apps and manually set things, or, a lot easier, right click on the dialog titlebar, select remember->head and save on close... and move it to the place where it should popup later and close the dialog. it will set the apps file with the correct data >Does xprop show any interesting differences between a choice5 window >and an ask window? Not really, the only difference is the *_name value, set to the respective title name. thanks 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. 22, 2011

http://mobile.wikipedia.org/

by rogerx.oss＠gmail.com

> On Sun, Aug 21, 2011 at 09:05:56PM +0000, corvid wrote: >Roger wrote: >> The following XML website seems to have problems within Dillo-fltk1.3: >> >> http://mobile.wikipedia.org/ > >The server sends it as "text/vnd.wap.wml". > >Using a firefox User-Agent header, I get ordinary html. > >If I just change the Accept header to show that I only want text/html, >text/plain, text/css, it...still sends me text/vnd.wap.wml. *sigh* > >(Sometimes everything about the web seems so screwed up in general that >I wonder what historical precedents there might be.) Ditto. -- Roger http://rogerx.freeshell.org/

Aug. 22, 2011

http://mobile.wikipedia.org/

by corvid＠lavabit.com

Roger wrote: > The following XML website seems to have problems within Dillo-fltk1.3: > > http://mobile.wikipedia.org/ The server sends it as "text/vnd.wap.wml". Using a firefox User-Agent header, I get ordinary html. If I just change the Accept header to show that I only want text/html, text/plain, text/css, it...still sends me text/vnd.wap.wml. *sigh* (Sometimes everything about the web seems so screwed up in general that I wonder what historical precedents there might be.)

Aug. 21, 2011

ping?

by corvid＠lavabit.com

Jorge wrote: > On Fri, Aug 19, 2011 at 03:23:58AM +0100, higuita wrote: > > > > ping? > > > > i can see my post and corvid replies in the archives, but i got neither > > of then in my email... is there some problem with the list? > > I received all the archived emails. Probably not a problem > in dillo-dev. In the archive, I see a msg that Roger wrote earlier today that I haven't received.

Aug. 21, 2011

Tab close button gets clobbered by tabs

by jcid＠dillo.org

Hi there, On Wed, Aug 17, 2011 at 09:44:16AM -0400, Jorge Arellano Cid wrote: > On Wed, Aug 10, 2011 at 05:31:38PM -0400, Jorge Arellano Cid wrote: > > On Tue, Aug 09, 2011 at 01:42:57AM +0000, corvid wrote: > > > Rob wrote: > > > > 2) From a practical standpoint, the old tabs seemed to behave a little > > > > nicer, in that they would adjust their size a little bit to show more > > > > of the title of the page opened in it. As it stands with Dillo 3, you > > > > can't see much of the title text before it gets an ellipsis. > > > > > > I, too, would prefer titles that were not so short and that didn't have > > > their descenders clipped. > > > > The attached code does this. I don't have much time now, so > > please give it a look. > > > > Maybe the main point is to decide how to code tab-overflow > > handling in a practical way (and to avoid complex code on the > > details/preferences, but having a few ;). > > Well, I haven't had much time these days, but gave it a try > anyway; Wow, this is full of details! [ ] tab overflow (code a handler) The idea is to have a tab overflow handler for the release. After sorting lots of details, the code I was making works, but adds lots of complexity for little gain, so I decided to try a different approach (adding all this stuff just before the release is too dangerous). Fortunately the second prototype works much better and is way simpler. I'll try to have it in the repo soon. If by some reason this doesn't happen by Aug 24, the release will roll without a polished tab overflow handler. > I hope to soon have something that works enough for the > release. In the meanwhile, the repo has had a good testing window > so the RC dance should be short. Please treat current repo as release candidate 1. -- Cheers Jorge.-

Aug. 21, 2011