Comments for Mattes Groeger

Comment on Review: Logging with Trazzle by Tom Villeneuve

Tom Villeneuve — Sun, 25 Dec 2011 05:50:14 +0000

concerning zz_inspect() … the reason why you were not able to use zz_inspect() is because the plugin “Inspector” is not included in Trazzle and is only accessible from the source (not compiled). It is always available on nesium’s github and the xcode project should compile without any errors.

Comment on Context-aware Tasks by Mattes

Mattes — Sat, 17 Sep 2011 08:45:48 +0000

Hi Chris,

sorry for the delay. My answers in order:

1) I wouldn’t know how to determent it unless you use something like a singleton. I think dependency injection is better in this case.

2) Good catch. I didn’t check this yet but you might be right.

3) Very good ideas! Thanks for sharing

Comment on Context-aware Tasks by Chris

Chris — Wed, 07 Sep 2011 12:59:00 +0000

Sorry, I was referring to the fact the I couldn’t find IContextProvider in 2.4. It’s working now that I added in the interface IContextProvider.

Is it possible for SequentialContextTaskGroup to determine the context instead of explicitly injecting it?

Also, shouldn’t the error function in AbstractContextTask also be overridden to clean up the context?

And for beginners, I think if would be best for doStartContext to throw an error if hasn’t been overridden with a message saying that doStartContext needs to be overridden and that doStart needs to be made ‘final’ to prevent people from overridding it.

Comment on Context-aware Tasks by Mattes

Mattes — Tue, 06 Sep 2011 19:11:41 +0000

Thanks Chris for your feedback. I added the IContextProvider interface to the blog post. This was really forgotten.

Regarding your Parsley 2.4 question. I don’t know any reason why it should not run with 2.4. Do you get an error? We have it running with 2.4-M2 which is not the final version. But we had other reasons for this.

Comment on Context-aware Tasks by Chris

Chris — Tue, 06 Sep 2011 07:39:57 +0000

This doesn’t work as you seem to be using 2.3 of Parsley and you haven’t defined the IContextProvider interface. I’m trying to get this working with Parsley 2.4.

Comment on Icon Badge for Windows by Mattes

Mattes — Tue, 09 Aug 2011 18:08:12 +0000

Hi eBuildy,

thanks for your feedback!

You can find the SWC as part of the downloadable zip on google code:
http://code.google.com/p/air-icon-badge/downloads/detail?name=air-icon-badge-0.1.zip

I fixed the link within the article. If you have still trouble please let me know.

Cheers

Comment on Icon Badge for Windows by eBuildy

eBuildy — Tue, 09 Aug 2011 16:01:33 +0000

Hi Mattes,

Great article, and thanks for a such good quality of code, just a question, I cannot find the TrayIconBadge SWC, where is it ?

Cheers

Comment on Context-aware Tasks by Mattes

Mattes — Wed, 03 Aug 2011 19:07:04 +0000

@adi Glad I could help. Thanks for the feedback!

Comment on Context-aware Tasks by adi b

adi b — Wed, 03 Aug 2011 14:57:14 +0000

Awesome article. I was looking into integrating Tasks into a project today and ran into the same issue with accessing the Context in a clean manner. We’re going to use these classes with full credit for your work. Many thanks!

Comment on Strong typed constants by erik

erik — Thu, 07 Jul 2011 12:27:38 +0000

The updated version using the EnumEnforcer class seems not to work (anymore). First I thought it had something to do with an update to the Flex SDK, but later on it seems that it also doesn’t work with Flex 3.6. You’ll get a runtime error as soon as you reference one of the static public props of the Direction class;

Error with Flex SDK 3.6.0.16.99
Exception fault: TypeError: Error #1115: Direction.as$202::EnumEnforcer is not a constructor.

Error with Flex SDK 4.1.0.1607
Exception fault: TypeError: Error #1115: CalculationOperator.as$168::EnumEnforcer is not a constructor.

Error with Flex SDK 4.5.1.2132
Exception fault: TypeError: Error #1007: Instantiation attempted on a non-constructor.

Think it’s got something to do with the EnumEnforcer class being in the same file and not being properly initiated. When moving it into its own file, it works again, but that kind of beats the purpose.