Comments on: Swiz 0.6.2 with Flex 4 support

By: Sönke

Sönke — Mon, 21 Dec 2009 11:04:36 +0000

Jesse, thanks for your feedback but I would ask you to write this to the Swiz mailinglist so all Swiz users can follow up.

By: Jesse Lundberg

Jesse Lundberg — Mon, 21 Dec 2009 05:15:14 +0000

First, thanks for contributing to a terrific framework! I’ve had the opportunity to test-drive a variety of them on various projects, and have found this one to be the most practical so far. I’m looking forward to using the 1.0 alpha rewrite I just pulled from GitHub in production.

In the interim (I’m using 0.6.4), I find myself caught up in the same problem Erik described with the recent Flex 4 nightly builds, and was wondering if anyone has a fix for this issue. I’m currently frozen to the 4.0.0.1230 build because of it.

Any suggestions would be most appreciated.

By: Erik Reedstrom

Erik Reedstrom — Mon, 07 Dec 2009 22:51:32 +0000

I switched over to the latest nightly build, currently 4.0.0.12589, and noticed that the [Autowire] tags in the views are no longer auto-wiring.

There is no dispatch of an event for addedToStage, so handleAutowireEvent is never being fired. This works in the current milestone version, 4.0.0.10485.

By: Dwong

Dwong — Thu, 29 Oct 2009 08:17:44 +0000

Just wanted to add to this insightful blog that I’ve found a way to, in a sense, have the initialize() in IInitializingBean in the view.

Since mxml bindings work with Autowiring beans, all you do is inject some bean into your view and listen to that via mxml tag. I haven’t found a way to add this binding in actionscript – it appears that adding it too early or too late causes the binding to not occur, and thus no “notification” on the view-side that Swiz has finished auto-wiring.

By: John Yanarella

John Yanarella — Sun, 12 Jul 2009 00:53:47 +0000

That should have read: “…when autowiring* to a particular property in an injected bean…”

By: John Yanarella

John Yanarella — Sun, 12 Jul 2009 00:52:24 +0000

Spoke with Chris and Ben earlier this week about making the necessary changes to support automatic bindings for non-primitives as well. For standard [Autowire] statements, it makes sense to only inject the requested instance at initialization. However, when binding to a particular property in an injected bean, it makes sense to always establish the binding as those properties may change over time. In my particular use case, I was implementing the PresentationModel pattern and using autowire-by-property to inject and observe properties in a PresentationModel from a Model bean. The automatic bindings provide a very elegant solution for synchronizing changes made to the Model back to the PresentationModel.

Chris made the changes on his local snapshot of the code – hope to see this change rolled into the next release.

By: Sönke

Sönke — Thu, 09 Jul 2009 17:01:05 +0000

Hi Jason,
the example is:
[Bindable]
[Autowire( bean="appModel", property="activeView", twoWay="true" )]
public var activeView:int;

So activeView is an int meaning a primitive and no object. So when the view holding this property is added to the stage Swiz injects the value appModel.activeView into the activeView property. Now when you would change the value activeView without twoWay=”true” appModel.activeView would not be changed and when set to true it will be changed because a ChangeWatcher acts behind the scenes.

However, this only applies to primitives.

By: Jason Chen

Jason Chen — Thu, 09 Jul 2009 14:45:44 +0000

Hi, I am kind of confused about the “twoWay” attribute. I have been using Java/SpringFramework for the past 4,5 years and I know that if it’s a singleton bean, there is only one set of values in a single instance of bean. All the other objects are only holding a “reference” to that bean. If one bean holder changes the value in the bean, then the value will be changed for all the other bean with the same reference (i.e. ), so it’s always “twoWay” in Java/Spring. How is it different from the Swiz in Flex? Can someone explain a little bit more details? Should we make the “twoWay” the default behavior? When a bean is “Autowired”, the AS object should only hold a reference to that bean if it’s an object, isn’t it? Then when the data got modified, next time when the same AS object got injected to a view, should the value be there? I am hoping it’s not “copying” the value into a new object in the view. It should be just a “reference”, right? Or it doesn’t work that way in actionscript?

By: Sönke

Sönke — Thu, 18 Jun 2009 19:12:07 +0000

drop me a mail and I can send it to you (soenke.rohde gmail com).
btw: you only need this to compile swiz itself and not for any projects you do with swiz. then you only have to download the swc and put it into the libs directory.

By: flashvnn

flashvnn — Thu, 18 Jun 2009 17:43:20 +0000

humn, i downloaded and install standalone but still get problem, can you make simple demo and share your project with configure?

Thank