Stefan,
I totally hear and understand you. I was really excited about MTASC and
FLAMES a while back, but it seemed I spent more time tweaking the system
than I did actual development on projects. Well, maybe not "more time", but
the ratio was not good enough. I'm back to mostly using the Flash IDE as a
compiler. But FlashDevelop has given me hope for MTASC. If they get the -mx
param into the project build, it might work out well for me.

Keith 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Richter
> Sent: Tuesday, December 27, 2005 3:06 PM
> To: 'Open Source Flash Mailing List'
> Subject: Re: [osflash] FlashDevelop: Project build and -mx parameter
> 
> Maybe I will need to revisit some of the Osflash tools (as I 
> am sure they have improved greatly) but my experience a few 
> months ago using Eclipse and MTASC (and Flashout) was that 
> (after a painful setup process which took me through some 
> obscure update routines) I tried to compile an ARP based 
> project (which compiled fine in the IDE) and it threw a 
> gazillion errors, some of which where related to the mx packages.
> Frankly I am not that much of a pro that I worry about 
> 'errors' in Macromedia's code. Their component framework 
> works for me (most of the time) and I have not got the skills 
> nor the time to rewrite or fix it.
> 
> I didn't have time to dig deeper so I compiled using Flash 
> even though I would prefer using MTASC as it would be a lot quicker.
> I am not saying that this is a big deal (and for most people 
> here it isn't as you seem to tweak everything until it works) 
> but I would expect that many developers would drop some of 
> the open source tools (for the time being at
> least) simply because they 'appear' to prevent a working app 
> from compiling.
> 
> If I need to work on another machine tomorrow and it has 
> Flash installed then I want to be able to check out my 
> project and work on it, no matter what tools I have used on 
> my office PC. Right now I am not sure I could do that using 
> an open source setup. If I am wrong then please tell me so 
> and I will reinstall MTASC and Flashdevelop first thing 
> tomorrow morning.
> 
> I don't want to sound too harsh but having to do any kind of 
> hoop-jumping exercise just because I have used the MM 
> components in my existing project then that isn't a very good 
> workflow (especially so if you are new to open source flash) 
> and it is an area that needs to be improved.
> 
> Remember this comes from someone who has spent 2 days until 
> FAME was fully up and running (granted, at the time there 
> wasn't much documentation around so it would be quicker now) 
> so you can't say I haven't tried... 
> 
> Stefan
> 
> 
>   
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Keith Peters
> > Sent: 27 December 2005 18:08
> > To: 'Open Source Flash Mailing List'
> > Subject: Re: [osflash] FlashDevelop: Project build and -mx parameter
> > 
> > That makes sense, theoretically. I assume the patch only 
> adds types, 
> > fixes local var issues, etc. per definition of
> > refactoring: improving the internal structure of the code without 
> > changing the external behavior.
> > Still makes me wary though.
> > 
> > Keith
> > 
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Marcelo 
> de Moraes 
> > > Serpa
> > > Sent: Tuesday, December 27, 2005 11:04 AM
> > > To: Open Source Flash Mailing List
> > > Subject: Re: [osflash] FlashDevelop: Project build and 
> -mx parameter
> > > 
> > > I may be wrong, but I don´t see any big differences on yours 
> > > application´s code when you use the patched classes as 
> the patch is 
> > > only intended to make them compile with MTASC.
> > 
> > 
> > _______________________________________________
> > osflash mailing list
> > [email protected]
> > http://osflash.org/mailman/listinfo/osflash_osflash.org
> > 
> 
> 
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
> 
> 


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to