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 FangYaqiong wrote: > Hi Christian, > Thank you very much for your information. I am intrested in this topic and > agree with you that is better to contribute in a simple part to familiar with > the code first. Can you give me some advice in which task is suitable for me > to do at the very beginning? I am so thankful that you can guide me in this > part. I will have a look at the code of the flash export first. Any document > available in this topic? > > Regards, > Fang Yaqiong > > > > > FangYaqiong [EMAIL PROTECTED] > 2007-02-06 > Regards&Thanks! > Tel:010-5802-2828 Ext.693 > Beijing Redflag CH2000 Software Co., Ltd. > > > > 发件人： Christian Lippka > 发送时间： 2007-02-05 20:33:51 > 收件人： [email protected] > 抄送： > 主题： (瑞星提示-此邮件可能是垃圾邮件)Re: [graphics-dev] about the task"Enhancing an existing > FLASH export filter" > > Hi Fang, > > welcome to the team. To my knowledge there is no one actively > contributing to the flash export at the moment. > The biggest drawback currently is that there is no support > for transitions and animations. Also navigation could be > improved (f.e. going back one slide or having a slide navigation > bar somewhere). > There already is some animation code in the cvs, contributed > by A. Saunders. But this is based on the OOo 1.x animations. > For OOo 2.0 we switched to a smiled based animation system. > To add all of this I think it is time to make more use of > the flash scripting system. Unfortunately we have not yet a > developer with some experience in flash scripting. > If you want to start working on the flash export I would > suggest to start with something simple to make yourself > familiar with the code. > I recently added support for complex and rtl languages to > the flash export (OOo 2.2). The current solution has the > drawback that each glyph is saved as a separate polygon. > It should be easy to add a caching that reuses glyphs that > are already exported. Therefore reducing the file size for > complex and rtl languages. > If you like to start on that I will be happy to mentor you > on this topic. > > You find the code for the flash exporter in the filters > module under source/flash. > > Regards, > Christian > > > > FangYaqiong wrote: > >> hello all, >> I am FangYaqiong, a developer in Beijing Redflag CH2000 Software Co., >> Ltd. I am in the Redoffice team and working with ChengXiuzhi, Liyuan and >> Liutao.I am interested in the Graphics project and want to do some >> contribution. After read the todo list in OOo, I found the task "Enhancing >> an existing FLASH export filter". I want to know how is this task going now? >> Because I haven't received any information about this task in the mailing >> list. Who can give me some detailed information,such as the requirement, >> schedule, technical document and so on? Thank you very much!:) >> >> Regards, >> Yaqiong >> >> >> >> FangYaqiong [EMAIL PROTECTED] >> 2007-02-02 >> Regards&Thanks! >> Tel:010-5802-2828 Ext.693 >> Beijing Redflag CH2000 Software Co., Ltd. >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
