Hi naveman, As far as I know, the ajaxify() will execute a JavaScript response if its content-type is "text/javascript". As for embedded JavaScript code (in <script></script>) in the response, I think it is evaluated when the response type is text/html, but I'm not 100% sure. You'll have to test it and refer to the jquery documentation on the ajax() function (http://docs.jquery.com/Ajax#.24.ajax.28_properties_.29). If there is a need for an evolution of the plugin to make it work, I will do it without problem.
As for CSS, if you don't want to use UJS_change_style(), I guess you'll have to write your own plug-in... François -----Message d'origine----- De : symfony-users@googlegroups.com [mailto:[EMAIL PROTECTED] De la part de naveman Envoyé : dimanche 1 avril 2007 17:56 À : symfony users Objet : [symfony-users] Re: jquery for symfony Hi, I like the sfUJSPlugin too, and i already structured my templates the way that now they look very firm and readable i structured them in this way : <!-- HELPERs --> <?php use_helper("...");?> <!-- STYLEs / Layout--> <style> ... </style> <!-- HTML / Content --> <div id="..."> ... </div> <!-- JAVASCRIPT / Behaviour - UJS ist included as standard helper--> <?php UJS("jQuery('...').Draggable({containment: 'parent',handle: 'div.positionHandle'})");?> As you see, I use the jQuery-plugin "Interface" too, like prototype/ scriptaculous But I have still two questions - Does the ajaxify-functions support javascript-evaluation in the ajax-response ??? If yes, how is it handled ? - Wouldn't it be nice to have the observer-pattern too for CSS ? so you can work completely on components and templates in a whole and write even the style-properties directly into it, but collect them in one (or different) css.php files Cheers Navid On 27 Feb., 21:03, Dustin Whittle <[EMAIL PROTECTED]> wrote: > Francois, > > This is excellent! Exactly what I was looking for. Great work! I look > forward to seeing this plugin grow as I absolutely think this is the > way to go. With such clean separation that MVC provides, to me it only > make sense to follow this separation in the template between the > markup and behavior. I will help where I can, but the next few weeks > are extremely busy. > > Cheers, > > Dustin > > ? wrote: > > Hi Dustin, > > > I just committed a proof-of-concept plugin introducing a new syntax > > for JavaScript helpers with the purpose of unobstrusiveness. The > > JavaScript library used is jQuery, but it could as well be Prototype. > > >http://www.symfony-project.com/trac/wiki/sfUJSPlugin > > > The plugin is young, but comments are welcome. > > > Cheers, > > > Fran?ois > > > -----Message d'origine----- > > De : symfony-users@googlegroups.com > > [mailto:[EMAIL PROTECTED] > > De la part de Dustin Whittle > > Envoy? : vendredi 23 f?vrier 2007 10:26 ? : > > symfony-users@googlegroups.com Objet : [symfony-users] Re: jquery > > for symfony > > > Francois, > > > You are completely correct. After reviewing the actual pquery > > implementation, it is no better then the current prototype > > implementation. I jumped the gun on mentioning this, with out really > > looking into the implementation. I assumed it was done correctly, as > > jquery is intended to be implemented via a behavior pattern. > > Actually, after a more thorough review of actual implementation, I > > completely agree the approach pquery takes to implementing jquery is completely backwards. > > > I guess I was trying to convey that a similar behavior based > > approach like Dan Webb's lowpro for rail's would make a great plugin for symfony. > > Which is what I thought this had potential for, but I stand corrected. > > > - Dustin > > > Francois Zaninotto wrote: > > >> IMHO, the great advantage of using JQuery is switch to a real > >> behaviour system (for which you don't really need helper, it can be > >> full JavaScript > >> code) for browser interactions. That's not what this library does. > > >> In fact, it takes the same (wrong) approach to using JavaScript in > >> a web application as the original rails helpers. It's obstrusive > >> and mixes the server and client logic (what's the point of an ID() function?). > > >> But hey, if you want to use JQuery instead of Prototype to do > >> exactly the same thing, this library might be what you need. > > >> (my 2c) > > >> -----Message d'origine----- > >> De : symfony-users@googlegroups.com > >> [mailto:[EMAIL PROTECTED] > >> De la part de Dustin Whittle > >> Envoy : vendredi 23 f vrier 2007 08:26 : > >> symfony-users@googlegroups.com Objet : [symfony-users] jquery for > >> symfony > > >> All, > > >> In case no one has noticed, some one has built a nifty set of rails > >> inspired helpers for the jquery framework. > > >>http://www.ngcoders.com/php/pquery-php-and-jquery/ > > >> One of the biggest advantages of jquery over prototype is the > >> behavior based design the provide clean unobtrusive javascript. > > >> **This could/should be ported to helpers with and packaged as a > >> plugin for anyone who has the time** > > >> Any takers? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
