- Dillo-dev - lists.mailman3.com

are we officially at feature freeze yet?

by jcid＠dillo.org

On Tue, Jul 26, 2011 at 10:37:40PM +0000, corvid wrote: > Jorge wrote: > > On Tue, Jul 26, 2011 at 07:48:18PM +0000, corvid wrote: > > > - moveToWidget(). Jorge has code for this. > > > > Yes, and it has worked OK for me. > > How does it behave in your tests? > > I haven't really been paying attention to it. > > > > - UI_TEMPORARILY_SHOW_PANELS > > > > What's the problem with it? > > (i.e. it current functionality looks OK to me, but I may not know > > the problem). > > I hide the panels, and then it's supposed to show them if I press ctrl-L > to type in the location bar, isn't it? Oh, now I see! I was testing with Ctrl-F ;-) -- Cheers Jorge.-

July 27, 2011

are we officially at feature freeze yet?

by corvid＠lavabit.com

Do you think the tabs should have a tooltip indicating that they can be closed with a click? Somehow it's hard for me to remember that that feature exists.

July 27, 2011

are we officially at feature freeze yet?

by corvid＠lavabit.com

Jorge wrote: > On Tue, Jul 26, 2011 at 07:48:18PM +0000, corvid wrote: > > - moveToWidget(). Jorge has code for this. > > Yes, and it has worked OK for me. > How does it behave in your tests? I haven't really been paying attention to it. > > - UI_TEMPORARILY_SHOW_PANELS > > What's the problem with it? > (i.e. it current functionality looks OK to me, but I may not know > the problem). I hide the panels, and then it's supposed to show them if I press ctrl-L to type in the location bar, isn't it?

July 27, 2011

are we officially at feature freeze yet?

by jcid＠dillo.org

On Tue, Jul 26, 2011 at 07:48:18PM +0000, corvid wrote: > are we officially at feature freeze yet? Not officially, but in a close enough state ;) > It would be nice just to make some fixes and get 3.0 out... > > Bugs: > > - moveToWidget(). Jorge has code for this. Yes, and it has worked OK for me. How does it behave in your tests? > - downloads dpi string escaping. Simple enough. Commit welcomed. ;) > - UI_TEMPORARILY_SHOW_PANELS What's the problem with it? (i.e. it current functionality looks OK to me, but I may not know the problem). > Not exactly important: > - the panel problems when resizing from very small. and - alt text wrapping (which looks like a nice feature) - remove large panel Maybe Johannes has some items too... -- Cheers Jorge.-

July 27, 2011

multiple search engines

by jcid＠dillo.org

On Tue, Jul 26, 2011 at 07:30:39PM +0000, corvid wrote: > Rogut??s wrote: > > What about less dialogs and better reuse of the location bar? > > One could define some engines in dillorc: > > search_g = google.com/search?q=%s > > search_yahoo = search.yahoo.com/?q=%s > > and type the keyword followed by a search string in the location bar: > > g some search string > > yahoo some search string > > Hmm, it _would_ be nice to be able to define location bar macros. It would be quite simple now that there's a PREFS_STRINGS type. e.g. search_macro="g http://google.com/search?q=%s" search_macro="yahoo http://search.yahoo.com/?q=%s" and it would please both CLI and GUI oriented users. -- Cheers Jorge.-

July 26, 2011

fltk-1.3 port merged into main repository

by Johannes.Hofmann＠gmx.de

Hi, now that we have the last fltk-2 based version out, the fltk-1.3 port has been merged into the main repository. >From now on please only commit to the main branch again. The temporary dillo_port1.3 repository will disappear soon. Let's polish dillo-3 and get a release out soon! Cheers, Johannes

July 26, 2011

are we officially at feature freeze yet?

by corvid＠lavabit.com

It would be nice just to make some fixes and get 3.0 out... Bugs: - moveToWidget(). Jorge has code for this. - downloads dpi string escaping. - UI_TEMPORARILY_SHOW_PANELS Not exactly important: - the panel problems when resizing from very small.

July 26, 2011

multiple search engines

by corvid＠lavabit.com

Rogut?s wrote: > What about less dialogs and better reuse of the location bar? > One could define some engines in dillorc: > search_g = google.com/search?q=%s > search_yahoo = search.yahoo.com/?q=%s > and type the keyword followed by a search string in the location bar: > g some search string > yahoo some search string Hmm, it _would_ be nice to be able to define location bar macros.

July 26, 2011

multiple search engines

by obeythepenguin＠gmail.com

On Tue, 26 Jul 2011 14:55:34 -0400, Rogut?s Sparnuotos <rogutes(a)googlemail.com> wrote: > What about less dialogs and better reuse of the location bar? > One could define some engines in dillorc: > search_g = google.com/search?q=%s > search_yahoo = search.yahoo.com/?q=%s > and type the keyword followed by a search string in the location bar: > g some search string > yahoo some search string > I've thought of adding something like that myself, actually. Opera does that, and it's the only way I search now. ~Benjamin

July 26, 2011

multiple search engines

by rogutes＠googlemail.com

corvid (2011-07-24 21:35): > > What if it was like: > > > Search [Fl_Choice] > > [Fl_Input] > > [Fl_Button] [Fl_Button] What about less dialogs and better reuse of the location bar? One could define some engines in dillorc: search_g = google.com/search?q=%s search_yahoo = search.yahoo.com/?q=%s and type the keyword followed by a search string in the location bar: g some search string yahoo some search string -- -- Rogut?s Sparnuotos

July 26, 2011