Spicefactory

sitron · Joined: 03 Jul 2009 Posts: 23

Hello!
i put up 2 _very_ basic examples using Parsley 2.0. The first one is using Flex (with the nice flex view wiring feature) and the second one is a pureAS project (ie: not flex).
Both examples are really useless but show a way (among others i guess) of creating a simple MVC structure with Parsley.
http://www.sitronnier.com/blog/parsley-2-basic-flex-example
http://www.sitronnier.com/blog/parsley-2-basic-flash-example
(view source enabled)

Jens, if you have 2 minutes and want to double-check that they are not completely wrong...
Just hope it can help people that feel a bit lost after reading the -fantastic btw- manual...

Jens Halm · Posted: Thu Jul 09, 2009 12:05 pm Post subject:

Thanks a lot. Will have a look at them this evening.
_________________
Jens Halm
Spicefactory

darscan · Joined: 12 Jul 2009 Posts: 5

Hello Sitron, Jens

I've just started looking into Parsley; I must say, version 2 is looking pretty awesome! I'm still reading the Developer Manual, but the approach seems very much in line with something I've been developing / thinking about called RobotLegs (concepts from PureMVC, but built on Dependency Injection).

Sitron, I've had a quick skim through your two examples. Thanks for putting them together. To make the examples more portable (and hence easier for others to download and import), I would suggest removing references to local folders in your Build Path, and using the SWC folder (libs) instead.

Jens, I would love to know what you think of these examples. Approach, structure, best practice. IE, are these valid, recommended ways to build applications using Parsley?

Many thanks. Excited to find Parsley.. can't wait to get stuck in properly!

Jens Halm · Posted: Mon Jul 13, 2009 2:41 pm Post subject:

Ok, finally found the time to look at these examples. I think they work quite well as a basic example for a minimal setup using the two major features of Parsley (dependency injection and messaging).

I'd have one suggestion for an improvement though: Like already discussed in another thread there usually is no need to push some kind of application-ready event from the outside to the objects living in the container. There are metadata tags for the object lifecycle ([PostConstruct] and [PreDestroy]) which you can use instead. So I would change this:

sitron · Joined: 03 Jul 2009 Posts: 23

Darscan, Jens thanks for your comments.
i updated the flex example so that it uses the [PostConstruct] metadata, works like a charm. tx.
obviously i wanted to do the same for the flash example... which was a bit trickier as the view is added to the stage after the context is parsed, so "postconstruct" has already happened. Fixed it using a Added_to_stage event listener to get the initial data.
thanks again.

sitron · Joined: 03 Jul 2009 Posts: 23

oh! and as of the possibility to use event class in the [MessageHandler] instead of binding to a string property... even though i see it as a cool feature, i don't know... i guess i m just used to string constants...
defining an event class with just 1 constant is meaningless in this case, but i usually end up with a few constants per event class.