Hi Augustus, Thank you for your detailed introduction, and it is very important to our team. Our team and I will do some discussion later, but I think we could not contribute in every aspects. I believe my colleagues who interest the ToDos will contact you directly:)
Best regards, Fang FangYaqiong [EMAIL PROTECTED] 2007-03-02 发件人： Augustus Saunders 发送时间： 2007-02-13 07:44:59 收件人： [email protected] 抄送： [EMAIL PROTECTED]; [EMAIL PROTECTED] 主题： (瑞星提示-此邮件可能是垃圾邮件)Flash export TODOs > Fang, I apologize for not responding sooner. I'm Augustus, and I'm more > familiar with the Flash export code than anybody else. Although, as > Christian pointed out, we have a much more evolved exporter that > supports OOo 1.1 level animations to a good degree, and many other > features not in the "ancient" code. My familiarity with the ancient code > is not very good anymore, but while the newer code is perhaps more > complicated, I think it is still a better starting point. There have > been enough bug fixes, infrastructure improvements and cleanups that you > surely don't want to repeat the effort! > > Anyway, there several things worth doing on the Flash exporter. The > glyph export you guys have been talking about seems like a reasonable > enough thing to do. There are a couple of other items that can be done > without diving into animations: > 1) This is really the most important task but requires some help from an > inside OOo engineer. The handling of the Meta-File format is not 100% > correct, in particular clipping (bounding) areas are not handled > correctly 100% of the time. Apparently, though, there is no > documentation of the Meta-File format, which is why we need some inside > help. Also, the meta-file does not contain some information about text > elements, for example what level paragraph (ie indentation) it is (if I > recall correctly). This is the source of layout anomalies. > 2) Dynamic text for things like page numbers still don't work. > 3) ActionButtons use the bounding box for the hit-area, which is not > correct. Although I don't know if this functionality is exposed in OOo, > it would be nice to offer a browser style "Back" and "Next" (to go to > previously viewed rather than sequentially previous). > 4) A somewhat more substantial, but very worthwhile, task is port the > whole thing over to use the Transform SWF library. I have CC'ed the > author of that library on this email. I told him before that we were > looking to use his library in the next version, and he expressed a > willingness to improve the library in case of any shortcomings. > Transform is already 10x better than what we have though. His Describe > program is an invaluable program when working on this stuff, go download > it now! http://flagstonesoftware.com. Trying to learn how flash itself > works at a low level is a waste of time, in my opinion. Just rely on the > libraries already written. > > When it comes to the animation system, some things are harder than > others, and I would recommend pursuing the easy stuff before trying to > rewrite the whole thing. Personally, I think the "Effect Options" are a > good place to start, followed by motion paths, some exit animations, and > some simple emphasis effects. The hard part here is understanding the > internal OOo structures and how SMIL works to describe the animations > and options. > > If you are interested in working on any of these things, let me know, > and I can help you understand how the code is structured and where to > start etc. Cheers- > > Augustus > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
