All, Hmm, I've never thought about directly embedding flex support into TG. What would this be like? My first thought might be similar to using kid/genshi to generate the ActionScript or mxml but I think the ActionScript should be compiled into swf's before using to deploy easier. We could use these tools as a front end but the power of the Flex Builder tool would be lost. I find that using Eclipse as the core development framework with pydev and Flex Builder are a very good environment (if you can live with restarting Eclipse due to memory and other issues I've yet to debug).
I've been very happy using TG with Flex. The general approach I've been using is treating TG as a web application server and launchpoint/container for the flex swfs. We've successfully done it out of the box with TG using JSON which requires a Flex module to parse right but works pretty well. I've also been using Kevin's TGWebServices add-on and have been using native HTTPService that way (WSDL works but is slower) - the Flex e4x stuff and getting it to bind the way I want was a bit annoying. I have had to do a few things I don't like with complex types like flatten to an xml string to make processing much easier on both sides. A common provider for both sides that allow more flexibility in the transport might be interesting or at least a best practices for the use of tools together, that said the JSON, SOAP, XML-RPC, HTTP battles have been so successful not sure we want to go there. Architectually, I like the separation of tools as it allows a clean division between the client (view) code and the server (model) code. The controller and business logic usually wind up split between things a little more than I like, particularly because with current web technologies I need to minimize the server network trips and allow more interactive control so the flex side handles a bit more of the logic processing on the client. My 1.5 cents, -Brandon On 7/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I think Flex support would be cool, but not being a flex guy, what > kind of 'extra' support is needed? > I played with the address book demo that was done a while back and it > seemed logical using JSON, what is the 'flex way' that would need > support built in? > > > > On Jul 5, 8:58 pm, SamFeltus <[EMAIL PROTECTED]> wrote: > > I think ya'll should consider building in support for ActionScript and > > Flex into TurboGears 2. HTML is a limited display technology for > > expressing audio visual ideas (obviously it is great for text). The > > upcoming open sourcing of the Flex technology opens up alot of > > opportunities to expand the expressive power of a web framework. > > > > TurboGears needs something to differentiate itself from a crowded > > playing field. > > > > Just two cents from the Peanut Gallery... > > > > Sam the Gardenerhttp://samfeltus.com/site_index.html > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
