On Tue, Apr 21, 2009 at 09:01:46AM +0200, Hofmann Johannes wrote:
On Tue, Apr 21, 2009 at 07:48:11AM +0200, Hofmann Johannes wrote:
On Mon, Apr 20, 2009 at 05:10:41PM -0400, Jorge Arellano Cid wrote:
Hi there,
It'd be very good if we can complete these points for the 2.1 release. Listed in no particular order:
1.- Dw documentation: online and as tarball. We have good docs. but to generate them there's a need to have: doxygen, graphviz, dot, latex and friends. That's why having it online and as a tarball is a good idea. 2.- Mapcity segfault In www.mapcity.cl playing with the "Tipo Calle" while the page is loading makes dillo segfault. If "Remote CSS" is disabled, it doesn't happen (also OK in dillo-2.0). 3.- New web site design We have a new banner and after finding a good color palette it may be ready to renew the site before 2.1 is announced. 4.- Debian/Ubuntu packages (after 2.1 final is ready) 5.- Update "8 years" page (it's nine) Yes, I should have done it already... 6.- Configurable key bindings. I'm reviewing this with Tim. Hopefully it will make it into the 2.1 release. 7.- Memory usage statistics Scott has posted some data on this, in another thread. I'll answer there.
I'd be working on 5, 6 and 3. Volunteers please assign yourselves to the pending points.
I will check 2.
Ok, I can reproduce it now with
trickle -d 15 dillo
trickle (http://monkey.org/~marius/pages/?page=trickle) is really cool for debugging!
The problem is the repush caused by the arriving CSS stylesheet. It deletes all form widgets and recreates them later. I guess I can fix the segfault somehow, but there is a fundamental problem if the user starts to fill in a form and then the repush deletes all his data :(
I currently see these options:
1. Disable forms while CSS stylesheets are pending. 2. Disable the repush once the user started to fill in forms. 3. Save form data in memory and restore it after repush. This could also be used to restore form data when going back to a forms page.
Opinions?
To implement what we had with dillo1: This is, inactive forms until the full form is loaded. Adding the restriction of pending stylesheets too (like in 1). This can solve the problem easily, and work even better when we add a maximum-simultaneous-connections to the server parameter in the future. -- Cheers Jorge.-