FWIW given my complete newbie perspective, I have a couple of reactions.First, it is clear that the answer to my question that started this meandering thread is a resounding no. I sort of expected that would be the case, but I just wanted to be sure.
Second, there's only an advantage to adopting a
there is no problems in using scripts like:
http://www.dynamicdrive.com/dynamicindex17/indexb.html
In Django,TG,Pylons,Web.py,Whatever Framework :) No widgets required.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 8/3/06, Don Arbow <[EMAIL PROTECTED]> wrote:
> Check out this comparison of the six most "popular" (Dojo,
> Zimbra,Yahoo, Microsoft, Google, and Prototype), each has its own
> strengths and weaknesses:
Ehhh... I normally don't pimp my blog in here, but I don't think
that's the best review to
On 8/3/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> - what would we gain by having an 'official' javascript library?
Honestly? I think the only thing we gain is an end to people asking
"which JS library is the 'official' one for Django?" ;)
> so, is there something that django could do to make
On 8/3/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> I just came across this presentation:
> http://domscripting.com/presentations/xtech2006/
> which describes a new layer/methodolgy on how ajax should be implemented.
It's not really "new"; Jeremy's been advocating that, and smart people
have
I just came across this presentation: http://domscripting.com/presentations/xtech2006/which describes a new layer/methodolgy on how ajax should be implemented.I personally would think implementing something like this would be a step forwardand we could then argue about if mochikit or dojo or yui
James Bennett wrote:
> On 8/2/06, gabor <[EMAIL PROTECTED]> wrote:
>> django does not force you to use the django-templating-system (you can
>> use myghty/zope-tal/whatever instead), but it clearly recommends the
>> django-templating-system, and that's the system which is the most
>>
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
On Aug 2, 2006, at 3:28 PM, gabor wrote:
>
> the same way i would like to see a "recommended" javascript library.
Which, though, is the recommended one? Do I want lightweight, or
widget heaven? One that follows standards (or should I say
convention) or one that pushes the envelope? If I
On 8/2/06, gabor <[EMAIL PROTECTED]> wrote:
> django does not force you to use the django-templating-system (you can
> use myghty/zope-tal/whatever instead), but it clearly recommends the
> django-templating-system, and that's the system which is the most
>
On Thu, 2006-08-03 at 01:25 +0200, patrickk wrote:
> the django-user (in this case) IS the one who´s writing the code, of
> course.
I understand that a person can be both a user and a developer, but that
has nothing to do with what I wrote. My point was (and still is) that
how the admin
the django-user (in this case) IS the one who´s writing the code, of
course.
Am 03.08.2006 um 00:52 schrieb Malcolm Tredinnick:
>
> On Wed, 2006-08-02 at 21:45 +0200, patrickk wrote:
> [...]
>> 3. Unless I´m very much mistaken, there´s already some development
>> going on - in order to
On Wed, 2006-08-02 at 21:45 +0200, patrickk wrote:
[...]
> 3. Unless I´m very much mistaken, there´s already some development
> going on - in order to provide AJAX (Dojo) for the Admin-Interface.
> Since most of the django-users (I guess) will use the Admin-
> Interface, they probably won´t
James Bennett wrote:
> On 8/2/06, patrickk <[EMAIL PROTECTED]> wrote:
>> 3. Unless I´m very much mistaken, there´s already some development
>> going on - in order to provide AJAX (Dojo) for the Admin-Interface.
>> Since most of the django-users (I guess) will use the Admin-
>> Interface, they
On 8/3/06, Dan Shafer <[EMAIL PROTECTED]> wrote:
> 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
On 8/2/06, patrickk <[EMAIL PROTECTED]> wrote:
> 1. It´s about certainty (which is not so important if you´re certain
> about your js-toolkit; I´ve been playing around with different
> toolkits for about half a year - and I´m still not sure which ones
> better for me ...)
With all due respect,
agreement and contradiction ...
> * Write your view, and if it needs to respond to XMLHttpRequests, have
> it serialize the response to XML or JSON. The tools in
> django.core.serializers make this extremely easy -- simplejson is
> bundled, so you can dump pretty much any Python data structure
Frommy experience with TG and Django, which the TG side may be a bit
dated, the only upper hand that TG may have is that 1) TG includes
MochiKit and 2) in TG, you just change a decorator to get a jsonified
object from a controller rather than HTML. As others have chimed in,
including MochiKit is
On 8/2/06, Dan Shafer <[EMAIL PROTECTED]> wrote:
> 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
On 8/2/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> You'll have to wait for the second part to see the complete
> implementation, but he makes it look pretty easy so far.
Or just read the code in the example page :)
It's taking a bit longer than I'd anticipated to write up the full
exegesis, but
On 8/2/06, Dan Shafer <[EMAIL PROTECTED]> wrote:
> 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
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
It's not very hard to integrate AJAX into Django, it is a bit more
manual then TG (from what I've read). But with the AJAX frameworks out
there, writing the javascript is far from hard.
James has a blog article on AJAX and Django:
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
24 matches
Mail list logo
