- Dillo-dev - lists.mailman3.com

Questions about beta testing

by waltdnes＠waltdnes.org

Hi all; I joined the list recently. It's been a long time since I last ran beta software consistently. Ironically, it was the Phoenix browser beta (later to become Firebird, and then Firefox). I was unhappy about how bloated the major browser had become, and I wanted a lightweight browser. It looks like I've come full circle. Iam not a C programmer. I'm a "power user" instead. I remember about extracting the tarball, going into its directory and then executing... ./configure --with-various-options && make && make install ...but that's about all. Like the subject says, I have some questions 1) I assume that all files that go into /usr/whatever in a normal install under a package manager, will end up in /usr/local/whatever if I build from the tarball. Is that correct? 2) How do I uninstall the program? Or can I simply install new versions over top of old ones? 3) Can I assume that the configure defaults are the reverse of the options? E.g. if the "configure" file has... --enable-ssl Enable ssl, https (ALPHA CODE) --enable-ipv6 Build with support for IPv6 --disable-cookies Don't compile support for cookies --disable-png Disable support for PNG images ...then are the defaults --disable-ssl --disable-ipv6 --enable-cookies --enable-png ? Which one is the default here? Hopefully the "enable" version. --disable-dependency-tracking speeds up one-time build --enable-dependency-tracking do not reject slow dependency extractors 4) I run Gentoo linux, in 64-bit mode on an Intel i3. The first 4 statements in my /etc/make.conf are... CFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe" CXXFLAGS="${CFLAGS}" CHOST="x86_64-pc-linux-gnu" MAKEOPTS="-j1" I believe that CFLAGS and CXXFLAGS are read directly by gcc. Is CHOST used outside of Gentoo's package-management? And how do I pass MAKEOPTS to make? Yes, I know that "-j1" slows down the build process slightly. But the final binary is just as fast. And the first time you waste a couple of hours on mysterious failures during the build process, you lose all the time you "saved" with a higher "-j" value. I see it every so often on the Gentoo mailing list. Here is what I'm looking at to automate the build process... #!/bin/bash export CFLAGS="-O2 -march=native -mfpmath=sse -fomit-frame-pointer -pipe" export CXXFLAGS="${CFLAGS}" ./configure --enable-ssl && make && make install Any comments? -- Walter Dnes <waltdnes(a)waltdnes.org>

July 27, 2011

are we officially at feature freeze yet?

by jcid＠dillo.org

On Tue, Jul 26, 2011 at 11:23:49PM +0000, corvid wrote: > > 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. Yeah, it's probably a good idea. (something like the clear URL button). -- Cheers Jorge.-

July 27, 2011

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