[isf-wifidog] basic auth server.
max.horvath at freenet.de
Ven 9 Sep 11:34:08 EDT 2005
Here are my 2 short cents regarding to the portal ...
> Well, the code is much more object oriented now, which improved
> separation a
> lot. Defining splash-only hotspots (hotspots with no login page), and
> defining custom urls to redirect to instead of the portal is also
> However, administering your auth server still depends on the
> default UI
> (altough you can have a custom CSS).
> Wrapping a different portal system around the current auth server
> would not be
> very difficult, and could be standardised with a minimum of
> I would however be interested to know what you want in a portal
> system that
> the current one doesn't provide and that could not be integrated to
> We made a herculean effort to make just about everything visually
> defined by
> the CSS. I admit that there is work left in modularising toolbar
> handling in the code, but other than that we don't really see what
> be integrated. I do understand however that it may not be obvious
> right now
> to someone digging in the code WHERE they are supposed to plug into.
> We most probably missed several use cases, but we would like to
> know them so
> we can continue to improve. Especially right now since we are in
> the middle
> of a partial rewrite, and the UI for the login and portal
> interfaces haven't
> been revised yet.
It would be great to be able to use custom templates or classes. In
most cases this would mean to have no work in applying the CVS
It's great that everything visually is defined by CSS - the only
thing to be added should be an administration panel where you could
decide which blocks should be displayed and in which order they
should be displayed. In this case the portal would be fully
More information about the WiFiDog