Hi Mark, > > Is this also a friend of yours? If so, is there any chance you could > > get hold of the build directory for me? I'd like to work on this over > > the weekend if I can. > > Yes, he's a friend of mine, too, but getting hold of the build > directory would be difficult. He's a designer, his collaboration in > this consists of having given Dan physical access to an old Mac of his > to set the root password, and to switch it on when Dan calls him. He's > often out of town, that's why Mac builds sometimes are delayed > somewhat... > > Frankly, I don't know anything about Macs (or C++), so it would be > difficult even if I had the time to go there, sorry.
Fair enough. I actually have swfmill compiling now having taken all the static flags out of the Makefile, so I can carry on regardless. > However, another housemate said Dan planned to return tomorrow night, > so I'll try to remember to tell him to contact you. I think he'll be > quite happy somebody who knows C++ is willing to contribute. :) I've been wanting to help out with swfmill for a while, but as always I couldn't find the time until recently (probably driven by my need for ImportAssets2 support). > *But*, if you want to get started already, I'll let you in to some > inner workings of swfmill I happen to know about and that might make > implementing new tags much easier, and would give you something to > work on until Dan can help: > You probably have noticed already that he is a big fan of xslt. Some > tags need additional work, but most of the reader/writer code for the > individual tags is actually generated out of an XML description of > them. I don't have any specs, but I poked around a bit in the sources > via trac, and found the directory where they are in: > > http://mirror1.cvsdude.com/trac/osflash/swfmill/browser/tags/swfmill-0.2.6/src/xsl?rev=117 > > If you look at source.xml, you'll find the definition of the tags > (there could be others somewhere, though). It looks like you could > fairly easily figure out how that XML dialect works if you compare > them to the specs. That way you could get started writing the XML for > tags you would like to have, and maybe, if they aren't some of those > nasty ones, the C++ code could be generated out of that description. > > That should accelerate the process significantly... Pretty smart, huh? :) Yeah, that is smart. We use XSLT extensively at work (our CMS is build around it) so I shouldn't have too many problems poking around here. Thanks for the help Mark! Cheers, Steve -- Steve Webster http://dynamicflash.com _______________________________________________ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
