>I'd like to work with you to make sure the web content is migrated to our 
>site. Otherwise, thanks for the help and the code!

Absolutely. Just let me know what content you would like.

I do still plan on working on FlexUnit here some, however, I also think it 
would be good to document the things I was planning to work on next so the team 
here can make decisions.

As I mentioned previously, one of the things that was actually significantly 
impacting our architecture (in a bad way) was the need to stay compatible with 
the way Flash Builder was calling us. If we could break that compatibility, the 
whole architecture would be much cleaner. This would fix a number of small 
issues around spark and mx compatibility. The other big issue I was working on 
was trying to move the test running into its own application domain.

One problem is that the test runner and tests could impact each other. 
Obviously not ideal but it became a much bigger problem in the era when we had 
mx projects, mx+spark projects and just spark projects.

So, some cleanup to the CI (where all outstanding bugs exist), the application 
domain issue, and fixing the test runner so that everything didn't have to be 
static (flash builder issue) were the first on my wish list.

Mike


On Jun 12, 2013 11:20 AM, "Michael A. Labriola" < labri...@digitalprimates.net> 
wrote:

> As code is here now, etc. I am going to begin taking the external 
> build server down. Eventually the website should also be downed and 
> all traffic redirect here.
>
> Any issues or concerns?
> Mike
>
>
> digital primates (r)
>
> Michael Labriola
> labri...@digitalprimates.net<mailto:labri...@digitalprimates.net>
>
> tel:  +1.773.693.7800 x206
> fax: +1.773.409.9251
>

Reply via email to