On Jul 24, 2009, at 3:36 AM, BG wrote: > > OK, I will try to be specific from a newbie perspective. > > How does the Javascript menu work? > > I assume that you build a structure with HTML and then set the class > or id to something that JQuery will turn into a menu. I can easily > extend it, but I cannot easily find (in the code) what makes it tick. > Basically the relationship between the files web2py_ajax.html, > layout.html and menu.py could be explained.
I completely agree (except that it appears to be a CSS menu, not a JavaScript menu). My preference would be that base.css define a very simple menu, no frills, no scripting beyond basic appearance, and the fancy menu code be moved to a new menu.css that could (optionally) override the simple version. > > What to do with the generic files? > I know how what generic.html does, but I'm not sure about the rest. > Does generic.rss return, your site as feed (sounds unlikely) or should > you extend it. I searched and found this information: > http://www.web2py.com/AlterEgo/default/show/226 which gives me an > idea, but I'm still not sure. > > Why is there a menu.py file in the models section? > > I know that things in the model section will be run first, but that is > not entirely obvious. This whole business of putting non-model in models to take advantage of some magic evaluation order seems pretty hacky. I don't know what the pythonic way of doing this would be, but it's certainly far from explicit. To the general point, though, there are a lot of questions like this that arise for the first-time web2py developer that seem to be mainly a matter of lore, with hints available if you search hard enough--and figure out where to search. > > It seems that Crud is creating the forms for the table administration, > can you leave it if you don't need the administration? > > I realize that all the information is there, but it is somewhat hard > to find....google searches mainly returns hits to google groups. If > all the details of the default app was explained in one place I > suspect it would be extremely helpful to newbies and people who are > returning after a longer break. > > I suppose the reason why I bring all this up is that I looked at > Django before Web2Py. The learning curve of Django is very steep > compared to Web2Py, and I just don't wish (not that I have any say in > it) web2py to go in the same direction. IMHO if its too much work to > give a good overview of the default app then its too big as an > example. > > I don't want to make an issue of this (I still love web2py) so feel > free to take my statements "as is" and please don't feel obliged to > give comments. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
