>I think it is just OOP practice. Changing existing class (widget) would be wrong since class could be used somewhere else and >standard behaviour expected from it, not extended one. OK, that's much simpler than I imagined =]
Well,still on the login widget. It works fine: I can see it with the print-user-stats function. So how can I add a "register" widget? A widget that has simple form (sccaffolded from a users class, probably) for the user to input his e-mail and password. The widget must store this data, and the check-login function should be able to look it up. Could you show a simple skeleton of such code? (No need to implement every single detail: I still need to learn how to do it myself =] ) Thanks for all the support. > 2013/10/2 o_z <[email protected]> > > > среда, 2 октября 2013 г., 17:38:34 UTC+3 пользователь André Miranda > Moreira написал: > >> OK, so let's begin with some basic widgets usage. >> >> First, the login widget. >> In the Learning About Weblocks, there is gives an example usage of the >> login widget. Why does he creates a login-maybe subclass, inheriting the >> default login widget stuff? Since not much is added, couldn't he just use >> the existing widget? And beyond that: when would I want to do the same in a >> similar situation, using or creating anothe widget? >> > I think it is just OOP practice. Changing existing class (widget) would > be wrong since class could be used somewhere else and standard behaviour > expected from it, not extended one. > >> >> Next topic: view sccaffolding. >> In evanmorning's tutorial on making a blog app he creates two interfaces: >> an admin interface for inserting and editing posts and a blog interface for >> viewing the posts. The default gridedit is really nice, but I can't see >> clearly how to make modifications to the default. I believe that the best >> way to understand gridedit's usage is by reading the source, but the >> gridedit itself is a subclass of other widgets, etc. How it could be >> explained in a way that you don't need to translate the Lisp source to >> English, but the explanation would give me some clues on how it works, so >> that I can read the code and have a better understaning. >> > I'm just reading the code in such cases. > I'm not sure what you want to know, please give me some tips or show > another point of view. > >> >> I hope that's not too much =] >> >> >> >> 2013/10/2 o_z <[email protected]> >> >> >>> >>> среда, 2 октября 2013 г., 3:03:21 UTC+3 пользователь André Miranda >>> Moreira написал: >>> >>>> Wow, that was fast! >>>> >>>> Well that sounds good: learn Weblocks by "teaching" it. >>>> >>> I did not mean it but it is also a good idea. >>> There is not much feedback from users who try to learn Weblocks so I >>> don't know exactly which documentation parts need to be updated. >>> >>>> Since I'm not an expert user (yet), anything I make won't be a >>>> technicql in-depth guide. >>>> >>>> So what we're talking about here: as I develop my own skills on >>>> Weblock, I ask for help and write about it. So it'll focus in taking a >>>> developer from beginner to intermediate, right? >>>> >>>> Do you suggest any model? Something like the "Agile Development with >>>> Rails"? Or like the "Lisp Web Tales" (RESTAS)? A tutorial on building a >>>> relatively big app, while explaining Weblocks ideas? >>>> >>> I suggest just to collect information which was useful during learning >>> and to put it into documentation later. >>> "Useful information" can be in any problem we will help to solve for you. >>> >>>> I'll be glad to help. >>>> Em 01/10/2013 19:18, "o_z" <[email protected]> escreveu: >>>> >>>>> Hello fellow lisper. >>>>> You have faced one of the main Weblocks problems. And you can help to >>>>> solve it. >>>>> Yes, ask about the problems and I will be glad to help you when I have >>>>> time. >>>>> I have updated documentation recently but it is not enogh I think. >>>>> Another advice - don't use navigation widget, it has much bugs. If you >>>>> use it then don't expect continuations to work properly. >>>>> I have replacement for navigation which does not change urls but works >>>>> with continuations well. Navigation is one of the largest problems to >>>>> solve. >>>>> At this moment i suggest use Weblocks for admin interfaces and some >>>>> other framework (or just some code without widgets etc.) for other site >>>>> part for which urls are important. >>>>> >>>>> среда, 2 октября 2013 г., 1:04:06 UTC+3 пользователь André Miranda >>>>> Moreira написал: >>>>>> >>>>>> Hello, felow Lispers =] >>>>>> >>>>>> I'm trying to learn this wonderful piece of software that is Weblocks. >>>>>> I became fascinated with it not only because it uses Common Lisp, but >>>>>> also because I find the idea of using continuations to deal with >>>>>> stateless HTTP >>>>>> very good. >>>>>> >>>>>> I've done web development before (Ruby on Rails, obviously =] ) and >>>>>> I've been trying to make a nice app with weblocks, but after trying >>>>>> for almost two months I'm still unable develop much beyond the basics >>>>>> in the tutorials and examples. >>>>>> >>>>>> After reading the tutorials and the quickdocs API, I'd like to ask for >>>>>> a piece of advice: how could I become a (better) Weblocks developer? >>>>>> >>>>>> After this time with the framework I see that it's been carefully >>>>>> built, >>>>>> and I want to become proeficient using it. What would you suggest? >>>>>> Should I stick to try and error, and post here any problem I face? >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> André. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "weblocks" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to weblocks+u...@**googlegroups.com**. >>>>> To post to this group, send email to [email protected]. >>>>> >>>>> Visit this group at >>>>> http://groups.google.com/**group**/weblocks<http://groups.google.com/group/weblocks> >>>>> . >>>>> For more options, visit >>>>> https://groups.google.com/**grou**ps/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weblocks" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to weblocks+u...@**googlegroups.com. >>> To post to this group, send email to [email protected]. >>> Visit this group at >>> http://groups.google.com/**group/weblocks<http://groups.google.com/group/weblocks> >>> . >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "weblocks" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/weblocks. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "weblocks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/weblocks. For more options, visit https://groups.google.com/groups/opt_out.
