I made http://www.dillo.org/FAQ.corvid.html The old FAQ is still at http://www.dillo.org/FAQ.html for now. So if you have comments/find mistakes/whatever....
On Thu, May 15, 2008 at 06:49:11PM +0000, corvid wrote:
I made http://www.dillo.org/FAQ.corvid.html The old FAQ is still at http://www.dillo.org/FAQ.html for now.
So if you have comments/find mistakes/whatever....
Yes.
Q: I have an addition to the FAQ/website. Whom do I contact?
Send all such additions, as well as general questions about the website, to the webmaster J?rgen Viksell. better to use dillo-dev instead nowadays?
Please try to contact J?rgen. If he doesn't answer, leave dillo-dev as the only contact until we find somebody else.
Q: Why isn't Dillo-0.8.x rendering some HTML entities (such as &euro)?
Please remove this question as it is specific to dillo1. The web site, and all its information should focuse in dillo2. BTW, it'd be good to state in the FAQ that dillo1 is unmaintained. Something like: Q: What's the state of dillo1 (dillo-0.8.x series)? dillo-0.8.x is unmaintained. It depends on an obsolete library and dillo2 has achieved and surpassed all it had to offer. [In the future we may add a link to the Changelog and to the Plans page]
Q: How do I use a different charset with Dillo? Internationalization and Localization (i18n & l10n)
FLTK port [...]
With regard to FLTK: s/FLTK/FLTK2/g in the whole FAQ. Several people write me saying they can't compile dillo2 with FLTK1! Let's try to avoid that misunderstanding. And in this particular case, we can re-word it like this: "Since dillo was ported to FLTK2, the UTF-8 character encoding is used internally. Dillo uses the iconv ..."
Q: How do I enable the https (SSL) support plugin for dillo?
Well, currently the CVS has it enabled, but it is definitely worth stating that it's a bare-bones plugin. Also, we can't make a release with HTTPS enabled until we solve the dialog spamming that happens on sites with multiple resources. This is, porting the https filter dpi plugin to a dpi server plugin. Before the release, something like: Q: What's the state of HTTPS support? First of all, beware that this is a prototype in alpha state. It will only provide for very basic web page retrievals, POST and GET. We need to port it internally fomr dpi filter to dpi server. If you want to help us to improve the plugin, please let us know! could do it.
Q: What's the status of the FLTK port?
I'd say something like: Code using the FLTK2 GUI toolkit was made publically available in September 2007, and progress has since accelerated. It has become the main development branch, and the GTK1 based dillo1 (0.8.x series) went unmantained. Dillo2 provides much more than the old one. Developers are encouraged to try it out. Users are advised to wait until a release is made. _Experienced_ users may try it out. [a link to the CVS page with build directions is needed here]
Q: Why does the page X.Y look strange?
It'd be good here to add something about the HTML bug meter: In the lower-right corner of Dillo you'll see a bug-shaped icon. Click on it to see the detected HTML errors. More info [add link to: http://www.dillo.org/help/bug_meter.html] That's it for me. Once done, let it be the new FAQ, and feel free to improve upon! -- Cheers Jorge.-
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what. BTW, I misspelled 'publicly' :(
On Fri, May 16, 2008 at 08:21:25PM +0000, corvid wrote:
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what.
They're not official, but good mnemonics! When there was GTK1 dillo only, there was no confusion. Currently the CVS is using dillo-fltk, but I'd much prefer to have a binary named "dillo2". Probably this is a good choice. Let's hear what dillo-dev people say. Here's the proposal: * call the new binary "dillo2", and refer to the old 0.8.x series as dillo1. -- Cheers Jorge.-
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jorge Arellano Cid wrote:
On Fri, May 16, 2008 at 08:21:25PM +0000, corvid wrote:
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what.
They're not official, but good mnemonics!
When there was GTK1 dillo only, there was no confusion. Currently the CVS is using dillo-fltk, but I'd much prefer to have a binary named "dillo2".
Probably this is a good choice. Let's hear what dillo-dev people say. Here's the proposal:
* call the new binary "dillo2", and refer to the old 0.8.x series as dillo1.
I think it's problematic to have a digit in the official name (or in the name of the binary) since people will think it's the version. I'd suggest something along these lines: * Dillo is the name of the brand * dillo2 is the codename for the fltk branch * for marketing reasons sell any snapshots / upcoming releases of that branch as the all new dillo version 2.x.y with tons of new features * the binary is called dillo (it's what people expect to type in to start the lightweight web browser thingie [at least I tried to run $PREFIX/bin/dillo a couple of times now...]) Justus - -- gpg key fingerprint: C82D 382A AB38 1A54 5290 19D6 A0F9 B035 686C 6996 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILf4BoPmwNWhsaZYRAor2AJ0U728787tvENHwVuxFW000e/DC/gCgpqZD JVaxk8o+/yROgKeKOapZlA4= =ym7X -----END PGP SIGNATURE-----
Justus wrote:
Jorge Arellano Cid wrote:
On Fri, May 16, 2008 at 08:21:25PM +0000, corvid wrote:
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what.
They're not official, but good mnemonics!
When there was GTK1 dillo only, there was no confusion. Currently the CVS is using dillo-fltk, but I'd much prefer to have a binary named "dillo2".
Probably this is a good choice. Let's hear what dillo-dev people say. Here's the proposal:
* call the new binary "dillo2", and refer to the old 0.8.x series as dillo1.
I think it's problematic to have a digit in the official name (or in the name of the binary) since people will think it's the version. I'd suggest something along these lines:
* Dillo is the name of the brand * dillo2 is the codename for the fltk branch * for marketing reasons sell any snapshots / upcoming releases of that branch as the all new dillo version 2.x.y with tons of new features * the binary is called dillo (it's what people expect to type in to start the lightweight web browser thingie [at least I tried to run $PREFIX/bin/dillo a couple of times now...])
I also prefer to have a binary named dillo. (and dillorc2 -> dillorc)
On Fri, May 16, 2008 at 09:54:06PM +0000, corvid wrote:
Justus wrote:
Jorge Arellano Cid wrote:
On Fri, May 16, 2008 at 08:21:25PM +0000, corvid wrote:
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what.
They're not official, but good mnemonics!
When there was GTK1 dillo only, there was no confusion. Currently the CVS is using dillo-fltk, but I'd much prefer to have a binary named "dillo2".
Probably this is a good choice. Let's hear what dillo-dev people say. Here's the proposal:
* call the new binary "dillo2", and refer to the old 0.8.x series as dillo1.
I think it's problematic to have a digit in the official name (or in the name of the binary) since people will think it's the version. I'd suggest something along these lines:
* Dillo is the name of the brand * dillo2 is the codename for the fltk branch * for marketing reasons sell any snapshots / upcoming releases of that branch as the all new dillo version 2.x.y with tons of new features * the binary is called dillo (it's what people expect to type in to start the lightweight web browser thingie [at least I tried to run $PREFIX/bin/dillo a couple of times now...])
I also prefer to have a binary named dillo.
OK.
[...] (and dillorc2 -> dillorc)
We need a way to distinguish among the rc for dillo1 and dillo2. Currently you can have both dillo1 and dillo2 installed, sharing cookies and bookmarks (because we have a single ~/.dillo directory). Ideas are welcomed, including dillorc2 -> dillo2rc :-) -- Cheers Jorge.-
Jorge wrote:
[...] (and dillorc2 -> dillorc)
We need a way to distinguish among the rc for dillo1 and dillo2.
Currently you can have both dillo1 and dillo2 installed, sharing cookies and bookmarks (because we have a single ~/.dillo directory).
Ideas are welcomed, including dillorc2 -> dillo2rc :-)
I was thinking that one was just a superset of the other, but that's because I forgot that the fonts would be different.
On Fri, May 16, 2008 at 11:34:57PM +0200, Justus Winter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jorge Arellano Cid wrote:
On Fri, May 16, 2008 at 08:21:25PM +0000, corvid wrote:
Are "dillo1" and "dillo2" official names? If so, I'll add in some text to make it clear what's what.
They're not official, but good mnemonics!
When there was GTK1 dillo only, there was no confusion. Currently the CVS is using dillo-fltk, but I'd much prefer to have a binary named "dillo2".
Probably this is a good choice. Let's hear what dillo-dev people say. Here's the proposal:
* call the new binary "dillo2", and refer to the old 0.8.x series as dillo1.
I think it's problematic to have a digit in the official name (or in the name of the binary) since people will think it's the version. I'd suggest something along these lines:
* Dillo is the name of the brand * dillo2 is the codename for the fltk branch * for marketing reasons sell any snapshots / upcoming releases of that branch as the all new dillo version 2.x.y with tons of new features * the binary is called dillo (it's what people expect to type in to start the lightweight web browser thingie [at least I tried to run $PREFIX/bin/dillo a couple of times now...])
Well, that's the canonical way of doing it (no pun intended). OK, let's do it that way then, and let's talk about "dillo2" in the FAQ. -- Cheers Jorge.-
On Fri, May 16, 2008 at 09:01:18PM +0000, corvid wrote:
Jorge wrote:
Please try to contact J?rgen. If he doesn't answer, leave dillo-dev as the only contact until we find somebody else.
His dillo address redirects to an address where I get User Unknown. I found a telia.com address, but that also gave me User Unknown.
The let's point to "dillo-dev" until somebody volunteers. ;) Although the problem of dillo-dev is that it needs subscription. -- Cheers Jorge.-
participants (3)
-
4winter＠informatik.uni-hamburg.de -
corvid＠lavabit.com -
jcid＠dillo.org