Comments on: The Flex Code-Behind Pattern http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/ Looking at the world of media: from music to RIA. Mon, 23 Nov 2009 08:39:09 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Jovica Aleksic http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-944 Jovica Aleksic Fri, 09 Oct 2009 12:19:05 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-944 <p>We are also using the code-behind approach in a large project, and I am quite happy with it too. It reminds me of PHP Smarty template engine, where you would write the logic in a php file, and the layout in a tpl file, where you would use html tags with variables in curly brackets, just as you do in Flex. </p> <p>The only "problem" I encountered with this approach is that you definitely always have to define a layout in MXML and copy-paste markup there, even if you could basically use most of the layout and components from another MXML file. So, say you have two quite similar components, in logic as well as in layout, just one of them has some button and some checkbox extra. You will extends the base class and add the two variables for checkbox and button, but for the MXML, you will have to copy all the markup, and additionally put the checkbox and button in there. Still, this is far better than workarounds like this one: http://loopmode.de/host/flex/ExtendedMxmlComponenentTest/ExtendedMxmlComponentTest.html http://loopmode.de/host/flex/ExtendedMxmlComponenentTest2/ExtendedMxmlComponentTest.html (it was a reply to a question of how to extends MXML-only components, replacing children)</p> <p>So, we use our base classes for all kinds of logic and extending, and in the end, the component always receives an own Layout definition in form of a MXML class. Would be fine if we could mix the approach of my example links with the code-behind approach, but I can't think of a way at the moment.</p> We are also using the code-behind approach in a large project, and I am quite happy with it too. It reminds me of PHP Smarty template engine, where you would write the logic in a php file, and the layout in a tpl file, where you would use html tags with variables in curly brackets, just as you do in Flex.

The only “problem” I encountered with this approach is that you definitely always have to define a layout in MXML and copy-paste markup there, even if you could basically use most of the layout and components from another MXML file. So, say you have two quite similar components, in logic as well as in layout, just one of them has some button and some checkbox extra. You will extends the base class and add the two variables for checkbox and button, but for the MXML, you will have to copy all the markup, and additionally put the checkbox and button in there. Still, this is far better than workarounds like this one: http://loopmode.de/host/flex/ExtendedMxmlComponenentTest/ExtendedMxmlComponentTest.html http://loopmode.de/host/flex/ExtendedMxmlComponenentTest2/ExtendedMxmlComponentTest.html (it was a reply to a question of how to extends MXML-only components, replacing children)

So, we use our base classes for all kinds of logic and extending, and in the end, the component always receives an own Layout definition in form of a MXML class. Would be fine if we could mix the approach of my example links with the code-behind approach, but I can’t think of a way at the moment.

]]> By: Jonathan http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-923 Jonathan Sat, 26 Sep 2009 01:49:18 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-923 <p>So, when you defined your package name I believe that you've made a typo. Shouldn't it read "com.vivisectingmedia.demo"? Good example this helped me a lot. Thanks!</p> So, when you defined your package name I believe that you’ve made a typo. Shouldn’t it read “com.vivisectingmedia.demo”? Good example this helped me a lot. Thanks!

]]> By: James Polanco http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-921 James Polanco Fri, 25 Sep 2009 05:19:56 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-921 <p>artigat1, Sorry for the late reply... catching up on a serious backlog of work.</p> <p>If you are checking back I would be curious to hear more about what you are trying to do. Are you trying to create objects via ActionScript and then set properties via MXML?</p> <p>I don't think that will be possible since the MXML is causing the compiler to create the instances you define.</p> <p>Now, if you are talking about using states to manipulate objects you create, that should be possible, as long as you expose the property on the backing class as a public [Bindable] value. Then you can access this via MXML and call setProperty or such.</p> <p>To offer any more help I would need to see more concrete examples...</p> artigat1, Sorry for the late reply… catching up on a serious backlog of work.

If you are checking back I would be curious to hear more about what you are trying to do. Are you trying to create objects via ActionScript and then set properties via MXML?

I don’t think that will be possible since the MXML is causing the compiler to create the instances you define.

Now, if you are talking about using states to manipulate objects you create, that should be possible, as long as you expose the property on the backing class as a public [Bindable] value. Then you can access this via MXML and call setProperty or such.

To offer any more help I would need to see more concrete examples…

]]> By: James Polanco http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-920 James Polanco Fri, 25 Sep 2009 05:14:42 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-920 <p>rdeman, That should not be the case, we use the code behind for the root Application MXML file for all our projects and setting the width, height and framerate for the application in the MXML works fine.</p> <p>Are you overriding these with compiler statements? In the backing ActionScript? I would look for other causes that would block these values from being set via the MXML because the code-behind shouldn't disable this.</p> rdeman, That should not be the case, we use the code behind for the root Application MXML file for all our projects and setting the width, height and framerate for the application in the MXML works fine.

Are you overriding these with compiler statements? In the backing ActionScript? I would look for other causes that would block these values from being set via the MXML because the code-behind shouldn’t disable this.

]]> By: rdeman http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-919 rdeman Thu, 24 Sep 2009 14:38:00 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-919 <p>Very nice introduction to the Code Behind pattern in Flex. 1 question: setting the width, height framerate, etc. do no longer work in the MXML main file :-/</p> Very nice introduction to the Code Behind pattern in Flex. 1 question: setting the width, height framerate, etc. do no longer work in the MXML main file :-/

]]> By: artigat1 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-897 artigat1 Wed, 05 Aug 2009 10:47:16 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-897 <p>I like the idea of this code behind a lot. One problem I seem to be having though is creating a new instance of an object in actionscript code and then trying to set elements within the mxml for that object. <br><br>It seems that I need to add the object before I can change any of the elements or properties. Is that correct? The project I'm working on requires a number of objects to be set in memory ready to be added when required. This might include setting the text of a label, but also it's position or styles or any number of other things. <br><br>I've tried moving the super.initialize() into the constructor, but that doesn't seem to work. Have you encountered this problem before?</p> I like the idea of this code behind a lot. One problem I seem to be having though is creating a new instance of an object in actionscript code and then trying to set elements within the mxml for that object.

It seems that I need to add the object before I can change any of the elements or properties. Is that correct? The project I'm working on requires a number of objects to be set in memory ready to be added when required. This might include setting the text of a label, but also it's position or styles or any number of other things.

I've tried moving the super.initialize() into the constructor, but that doesn't seem to work. Have you encountered this problem before?

]]> By: J2EE Code Behind for Flex / Actionscript Developers « timshaya http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-885 J2EE Code Behind for Flex / Actionscript Developers « timshaya Wed, 22 Apr 2009 19:23:59 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-885 <p>[...] J2EE Code Behind for Flex / Actionscript Developers Just re-stumbled upon Ted Patrick’s post on using the Code Behind technique in Flex with Actionscript. Ted wrote about how he used it in .NET and in Flex. There’re more explanations of Code Behind here and here. [...]</p> [...] J2EE Code Behind for Flex / Actionscript Developers Just re-stumbled upon Ted Patrick’s post on using the Code Behind technique in Flex with Actionscript. Ted wrote about how he used it in .NET and in Flex. There’re more explanations of Code Behind here and here. [...]

]]> By: Emre Selen http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-804 Emre Selen Sat, 18 Oct 2008 08:55:57 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-804 <p>That was just the case I was wondering about. Thanks a lot. Nice and simple. Just on point.</p> That was just the case I was wondering about. Thanks a lot. Nice and simple. Just on point.

]]> By: Rafael Santos http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-795 Rafael Santos Fri, 29 Aug 2008 12:22:14 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-795 <p>Fantastic article..... Good straight forward information.... Direct and compact....<br>It helped me understand more about how Flex/AS works and how this interaction should be handled....<br>Thanks</p> Fantastic article….. Good straight forward information…. Direct and compact….
It helped me understand more about how Flex/AS works and how this interaction should be handled….
Thanks

]]> By: James http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/comment-page-1/#comment-777 James Tue, 29 Apr 2008 14:11:09 +0000 http://blog.vivisectingmedia.com/2008/04/the-flex-code-behind-pattern/#comment-777 <p>I am glad this helped clear up some of the pitfalls. When we first adopted this pattern on the project Webnesto is referring to in his comment, we would definitely had some challenges with the initial implementation. I have a feeling I missed a few other less common pitfalls we stumbled upon during the that project and other ones I have have used it on. At this point it has become more second nature, so what was once an "workaround" is now just how I code. If you, or anyone else, has some issues or questions about the pattern please let me know and I will reply and/or update the post with recommendations.</p> I am glad this helped clear up some of the pitfalls. When we first adopted this pattern on the project Webnesto is referring to in his comment, we would definitely had some challenges with the initial implementation. I have a feeling I missed a few other less common pitfalls we stumbled upon during the that project and other ones I have have used it on. At this point it has become more second nature, so what was once an “workaround” is now just how I code. If you, or anyone else, has some issues or questions about the pattern please let me know and I will reply and/or update the post with recommendations.

]]>