On 8/2/06, Dan Shafer <[EMAIL PROTECTED]> wrote: > > My plan for the next six months is to create 4-6 substantial Web > applications which will all be variations on a single theme. IOW, I > anticipate lots of code and component reuse. On this point, it at least > *seems* to me I'd be better served by Django than by TG, though I've asked > on that list for some reactions.
Can't speak on TG, but Django is definitely great at this. > The second major factor in my design is the need for AJAX componentry and > in that regard, at least, it *seems* TG has a strong upper hand, though it > could clearly be implemented with some effort in Django. Can anyone address > the degree of difficulty or level of effort involved in incorporating, say, > the YUI library, for example, into Django in a sufficiently seamless way > that I could Ajax-ify the components in my designs without jumping through > too many hoops? Or have I perhaps just missed something valuable in my > exploration of Django that suggests this isn't even a problem? You may want to take a look at James Bennett's most recent blog posting/tutorial, http://www.b-list.org/weblog/2006/07/31/django-tips-simple-ajax-example-part-1 He shows the steps you have to take, and even better for you, he uses YUI. You'll have to wait for the second part to see the complete implementation, but he makes it look pretty easy so far. Jay P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
