I think it mostly depends on the presentation model you want to implement and not so much on the kind of relationship of your entities You could present your model in many ways:
Lesson Plan: grid ->drill down to see lessons -> drill more to see topics Lesson Plan: page -> lessons as links -> topics as links in the linked lessons pages Lesson Plan: nav bar -> lessons as tabs -> topics as content (links list or whatever) Of course you could mix and much or do pretty anything you want. I would suggest deciding on the presentation in a more specific way and then start to think how you can translate that to weblocks. You dont model abstract relationships with Weblocks (and any web framework), you implement presentational models. . I really would like to be able to answer more specifically to you. I am not an experienced user of neither lisp or weblocks. Maybe others have more specific information. I think you will find many code snippets here for parts of "presentational models" and "interaction patterns" people have tried to bring to life with weblocks. E.g authentication, or presenting grid data with many tweaks. Also the contrib of the source contain real gems especially as concepts or ideas for solutions to misc problems. Vassilis. -- You received this message because you are subscribed to the Google Groups "weblocks" group. To view this discussion on the web visit https://groups.google.com/d/msg/weblocks/-/0JbPbz0m0mkJ. 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.
