Stephen Compall <[email protected]> writes:
> Saikat Chakrabarti <[email protected]> writes:
>> I am still new to Weblocks and Lisp and was going through some of the
>> widget code to get a better sense of things.  One thing I was
>> wondering - why not make login a subclass of quickform (or maybe even
>> an instance of a quickform)?  It looks like it mostly just repeats all
>> the slots in a quickform and adds one extra one (on-login - which I'm
>> not sure why that can't be the same as on-success for a quickform).  I
>> am sure I am missing something though with my noob eyes.
>
> I think you are right.  Subclassing is the best choice, so that initargs
> propagate, and we can duplicate the defaults.  The main difference is in
> the accessor methods.  Who out there is currently using or defining
> methods on the various login-* accessor GFs?  I just checked hfsbo.com,
> and I didn't use any.

I tried to make use of the login widget, but could not and hacked my own
contraption, that I'm rather ashamed of. I believe this definitely needs
work, we should have a login widget that:

a) is complete, e.g. you plug it into your site and you're good to go,

b) does not assume it is a wall between two parts of the site, e.g. I
want a login widget to be displayed at all times or easily accessible
and once the user is logged in, the site just acts differently,

c) is capable of displaying a registration action link and if the user
successfully registers, completing the flow so that:

d) it can change into a user-info kind of widget, displaying the user's
information, and marking some other widgets as dirty.

My contraption does most of that, but it isn't pretty.

--J.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to