Augustus Saunders <[EMAIL PROTECTED]> writes: > There are 2 sides to this: 1) what is the "most optimal" solution, and > 2) what is the "most realistic" solution? The most optimal solution > involves creating an entire SMIL processing engine in ActionScript.
[...] > So we come around to the "realistic" solution. The realistic solution > is to expand upon the work already done and push it as far as it > goes. > Hi Augustus, well - your effort estimates appear reasonable, but from experience I can tell that the hacked-up solution will accumulate at least as much time poured into it over the years, as if we'd do it right up-front. At any rate, he who codes decides, so this is all my two cents worth of counsel. But maybe there's something inbetween full-blown, independently developed SMIL engine, and coincidental effect generation (yeah, that's what I call it - just import a PPT presentation, and see that Impress UI really has no clue either, about what specific effects are in there): the basic SMIL animations are few, and very simple in nature. Triggering them is event-based (either time, or other effects start/end, or user interaction). So, whipping up such a simplified engine should be possible in your two weeks time frame, and getting that broken-down SMIL is certainly possible with the existing c++ smil processing. > My rough guess is that we can get to about 90% compatibility without > substantial structural changes. > As I said, I doubt that with arbitrary PPT input. But certainly true for Impress 2.x generated input. Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
