sfUJSPlugin used sfPJSPlugin, which used a hack to handle JavaScript templates. This hack didn't scale, since JavaScript Actions could not be cached.
So I stopped the development of sfUJSPlugin until 1.1 is released. In symfony 1.1 and include_dynamic_javascript(), PJS are natively supported and in a cleaner way, so PJS become a viable solution. François 2008/6/30 Jonathan Franks <[EMAIL PROTECTED]>: > > Some time ago, there was a bit of a buzz on the user list about > sfUJSPlugin and I wondered if we were gonna see a move towards a system > that separated the markup and the behaviour in symfony 1.1. > > Well it looks like this isn't gonna happen and sfUJSPlugin development > seems to have stopped - It hasn't had a commit for 3 months and nothing > serious seems to have changed for almost a year. Perhaps this is because > it is simply ready to use but its status is still beta and to provide a > full replacement to the built in helpers, it would need to support > visual effects. > > Anyway, I'm wondering what the future for javascript in symfony is?? I > like the idea of sfUJSPlugin and using jQuery, but if prototype is gonna > remain the heart of javascript in symfony, then I'm inclined to stick > with the built in helpers. > > Regards // Jonathan > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
