[mtasc] Image linker?

[Ricci Adams]

My impression from the thread was that the focus was on an open-source 
solution.

If this is not the case, and one is only looking to get rid of the 
Flash IDE, then KineticFusion is probably a fine choice.

Is RVML licensed in such a way that open-source applications could use 
it freely?  If so, then there is no need to reinvent the wheel and it 
should be considered.

On a side note, I checked out the svg2swf utility that Zahari 
mentioned.  If the entire SWF file format can be represented in SVG, 
then this is probably the way to go.  Such a utility would allow one to 
choose from a variety of SVG editors already in existence.  Then the 
master application would use svg2swf and mtasc to do the one-shot 
creation of the SWF file.  (Note: I'm assuming that people would be 
willing to modify svg2swf.  I would love to help, but I would first 
have to beef up my Perl chops a bit *grin* ).

Ricci Adams

ricci at ricciadams.com
ricci at musictheory.net
AIM: RicciAdams
http://www.ricciadams.com/
http://www.musictheory.net/

On Mar 7, 2005, at 7:01 PM, Alex Bradley wrote:

> Sometimes I feel like I'm living in a bubble! FLX already exists - 
> it's called RVML and is already available in KineticFusion, and it's 
> commercially supported. We support SWF compilation from XML, SWF 
> decompilation to XML, dynamic multimedia linkage, AS 1.0 and AS2.0 
> support with both embedded ActionScript, #included ActionScript, and 
> external classes with fast caching, configurable error reporting, 
> output to SWF4, 5, 6, 7 - basically complete lossless coverage of the 
> entire Flash format. And when AS4X comes out, we'll support that too!
>
> To my knowledge, anyone who's ever had a problem with KineticFusion 
> has received immediate support so if there's something you don't like 
> about the application, why not let us know - it's a win-win, surely?
>
> Hmmm.... :-(
>
> Alex
>
>
> Ricci Adams wrote:
>
>> I think that a one-stop tool is everybody's end goal.  I also think 
>> that we all want to be able to edit some code, click one button or 
>> run one command, and out pops an swf.
>>
>> I propose that a common XML definition be made which would take the 
>> place of .fla files.  For the remainder of this letter, I shall refer 
>> to it as FLX (Flash XML), although it could be called anything.
>>
>> FLX would basically define all of your movieclips, their linkage 
>> properties, the stage, various shapes, etc.  Since it would be an 
>> documented standard, people could develop multiple visual editors and 
>> utilities which operated on FLX files.  You could also have a fla2flx 
>> converter for migrating old projects (although since .FLA is a closed 
>> format, this would probably be difficult).
>>
>> Next, you would have a command line program called flx2swf or 
>> something similar.  Its job would be converting the XML-based FLX to 
>> valid SWF.
>>
>> You then have a master program (swfc?) that calls both flx2swf and 
>> mtasc.  It would know that any graphical data in FLX format is 
>> handled by flx2swf, any source code gets passed through mtasc.  As 
>> long as flx2swf and mtasc have well defined interfaces, swfc could 
>> alternate between the two at will (thus, handling Actionscript 
>> attached to a specific instance of a movieclip, which the Flash IDE 
>> allows you to do, although I don't like it *grin*).
>>
>> I think that this way, everybody wins.  There is a standard 
>> definition for flash-based graphics, each utility is specialized for 
>> a unique task, and the new user would have a single command to learn 
>> (more advanced users could make their own scripts or customize their 
>> own IDE and call each component separate).
>>
>> - Ricci
>>
>>
>
> --
> MTASC : no more coffee break while compiling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2430 bytes
Desc: not available
Url : http://lists.motion-twin.com/pipermail/mtasc/attachments/20050307/deabecb1/smime-0006.bin