Dillo's html rendering capabilities are what we should use for advanced forms. We don't want to duplicate the form widgets into a native-gtk version like mozilla does with xul. The pageflow, the forms, images etc ought to be in html, even if it's a dpi serving them. Having a login/password modal box seems to be what people are used to, so I can see why we'd like to have that. I can imagine dpis other than https needing a login/password box, but I'm not sure I can imagine that for non-login purposes. In any case, anything more complicated than one string, one or two text boxes with lables (possibly hidden for passwords) and 1 or 2 buttons certainly belongs to a dedicated html page the dpi would build. I could live with an intermediate html login page for https or any other dpi myself. Best, EG

-----Original Message----- From: dillo-dev-admin@auriga.wearlab.de [mailto:dillo-dev-admin@auriga.wearlab.de] On Behalf Of Garrett Kajmowicz Sent: Monday, July 12, 2004 3:26 PM To: dillo-dev@auriga.wearlab.de Subject: Re: [Dillo-dev]Plugin infrastructure

I just came up with two other dialog box types we might need:

A window with alterable caption/message text and either one or two text boxes with associated labels. One or both of the boxes should be able to be set in "password" mode.

I'm not sure if that counts as one or two, so I'm inflating my estimates to look more impressive :-)

- Garrett Kajmowicz

_______________________________________________ Dillo-dev mailing list Dillo-dev@lists.auriga.wearlab.de http://lists.auriga.wearlab.de/cgi-> bin/mailman/listinfo/dillo-dev