Dan Shafer wrote: > I've spent the last few days looking intently at both Django and TG. I > haven't yet built anything useful in either, but i've poked at them enough > that I think I'm beginning to see through the fog, however dimly. > > 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. > > 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?
I've done AJAX with Struts on Tomcat :) My point is that AJAX, you can do it with good old CGI if you want. You tried Prototype library? It doesn't matter really whether it's Django or TG or RoR or Servlets or ISAPI or what have you. It's so easy. > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Shafer, Information Product Consultant and Author > http://www.shafermedia.com > l > > ------=_Part_2906_27102895.1154542946098 > Content-Type: text/html; charset=ISO-8859-1 > X-Google-AttachSize: 1333 > > I've spent the last few days looking intently at both Django and TG. I > haven't yet built anything useful in either, but i've poked at them > enough that I think I'm beginning to see through the fog, however dimly.<br> > <br> > 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.<br><br> > 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? > <br clear="all"><br>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan > Shafer, Information Product Consultant and Author<br><a > href="http://www.shafermedia.com";>http://www.shafermedia.com</a><br>l<br> > > ------=_Part_2906_27102895.1154542946098-- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
