Guys, Once again I want to thank you for the appreciation you have for Dillo as a project. Now, if you read my original message again, you'll find:
Sebastian made a huge effort too. Having a job and developing a web browser is a very demanding task, and he did even more than that. I highly respect the man.
In Germany we decided with him to keep the Dillo FLTK2 closed until we both agreed to release.
and
From some time ago I think it would be good to release the new code. I have emailed several times with no answer.
In fact, I think it was more or less 6 months ago, after some emails with Andrew Tanenbaum, who finally helped me to see that it was a good time to release the code again. Since then, I've tried to contact Sebastian to agree on this. -- On the technical part:
But Dillo need to evolve to support features only existents in modern browsers as i18n, javascript, https, tabs, flash (gnash), etc.
- i18n : this was the main reason for choosing FLTK2 (utf-8). - https: I started this plugin and also wish it can be improved (later Garrett Kajmowicz helped a lot with this). - tabs : I also want Dillo to have TABs. It may take to much time until WM TABs support is as good as internal TABS. I designed a Dillo FLTK2 UI where this is easy to add (one of these days I may code it up... :-) - flash: This depends on a external interpreter. I have no problem in making the hooks. - javascript: This also depends on a external VM, and a supporting framework. It can be done but requires time. I'm not opposed as long as it can be disabled/enabled because it comes with severe security/privacy risks. - CSS : All of us want this! Sebastian made a huge and accurate work to make the CSS model a part of the internal widget structures. We only need to hook the parser. We even showed a prototype in France 2005 at LSM Again, once released, the code will not improve alone, it needs dedicated developers/supporters willing to put their part in order to make the vision we share happen. <<Long life to Dillo!>> -- Cheers Jorge.- PS: For those willing to take our word at face value, I want to state that it was never our intention to sell the code to proprietary hands. BTW, we never did.