As they say on the CentOS forums, I'd like to update what I ended up doing 'for posterity'.
The view classes are working nicely for setting up initializations which are commonly used. Probably the best example of this is that I have a master view class which the other classes inherit from. In that class, I have functions which are used by all of the subclasses, and I also initialize some useful tools like a fatal_errors list, which opens it up for use throughout all of my other views. I also set some simple variables which used by almost every view function, such as self.context = context, and I do a logged in check. The view classes which inherit from the master class are all fairly specific for what they represent, and I expect that most of the AJAX functions will fit into each of those sections. For example, there is a form of entry_views.py which handles each form of the website for incoming users, and it also holds all of the ajax functions for those views. Then there is something like user_views.py which processes pages related to the users, and their respective ajax calls. As for the final point I raised in the previous post, I stopped caring if chunks of my project are portable or not, haha. But I'm doing what I mentioned which is creating objects in external classes which I import. Although I'm not making a forms class - I perform the form processing within the class which the form is related to, when an instance is initialized. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
