I’m currently evaluating Aspose.Slides for Java, using it in a Laravel (PHP) application via JavaBridge. I’ve successfully integrated the JavaBridge and deployed the aspose-slides-25.4-jdk16.jar (temporary license) into my Tomcat instance. Basic features like loading and exporting .pptx files to HTML are working well.
However, I noticed that certain methods documented under HtmlOptions — specifically:
setAnimateTransitions(boolean)
setAnimateShapes(boolean)
setIncludeAnimation(boolean)
…are not available in the JAR I’m using. When I call these methods, I get:
This is despite the fact that these methods are listed in your Aspose.Slides for Java API documentation.
Can you please clarify:
Are these methods actually available in Aspose.Slides for Java, or only in the .NET version?
If they are available, which version of the Java JAR do I need to use to access them?
Are they excluded from the temporary license, or is this a limitation of the jdk16 classifier build?
Is there a version or license combination that fully supports exporting PowerPoint to HTML with animations via Java?
I’d appreciate any clarification you can provide — this will help us determine whether we can rely on the Java-based integration for our animated PowerPoint conversion needs.
Can you please specify the version of Aspose.Slides for Java you are currently using and confirm if you have checked the latest documentation for any updates regarding the methods in question?
I’ve also enumerated the available methods using reflection via JavaBridge, and only a minimal subset (e.g., getSlidesLayoutOptions) is visible on the HtmlOptions object.
Can you confirm:
Are these animation-related methods expected to be available in Aspose.Slides for Java 25.4?
If so, is there a build (e.g., full version, different classifier, or newer version) where they are definitely included?
Is it possible that these methods are only available in the .NET edition, despite appearing in the PHP for Java documentation?
Thank you again — I’d really appreciate clarification so we can decide whether to proceed with the Java integration or shift to an alternative.
@ChristianVoss,
Thank you for posting the questions. Could you please clarify where you found the setIncludeAnimation method? The Aspose.Slides APIs do not contain it.
You’re absolutely right — upon reviewing it again, I realize that setIncludeAnimation() was mentioned in several forum discussions and example code snippets, but it does not appear in the official Java API documentation. That was my mistake — I appreciate the correction.
To summarize where I stand:
I confirmed that methods like setAnimateTransitions() and setAnimateShapes() do appear in the PHP for Java documentation, specifically at:
However, those methods are not found via reflection in the actual HtmlOptions class from the aspose-slides-25.4-jdk16.jar I’m using.
@ChristianVoss,
Thank you for the clarification. Both the setAnimateTransitions and setAnimateShapes methods are present in the Html5Options class in Aspose.Slides for PHP via Java API.
Also, I executed the following code example:
$htmlOptions = new Html5Options();
$htmlOptions->setAnimateTransitions(true);
$htmlOptions->setAnimateShapes(true);
$presentation = new Presentation();
$presentation->save("output.html", SaveFormat::Html5, $htmlOptions);
$presentation->dispose();
It completed successfully without any errors. Please check the issue carefully again.
Thanks so much for your help — I really appreciate your detailed guidance.
Just to follow up: everything is working now using Html5Options and SaveFormat::Html5. The key issue was that I was mistakenly trying to apply setAnimateTransitions() and similar methods to the HtmlOptions class, instead of Html5Options. After switching to the correct class and removing the unsupported setHtmlFormatter() call, the export worked as expected.
That said, I’ve noticed that only the first animation effect per shape seems to be applied in the exported HTML5. For example, if a shape has multiple animations (e.g. “fade in” followed by “fade out”), only the first one runs in the browser.
Could you please confirm:
Is this a known limitation — that only one animation per shape is supported in the HTML5 export?
Is there a list or documentation page that outlines which animation types are supported when exporting to HTML5 using Html5Options?
Thanks again for your support — your answers helped me get the export working smoothly in a Laravel-based setup using JavaBridge.
As far as I know, there is no limit on the number of animations per shape when exporting a presentation to HTML5. Could you please share a sample presentation showing the problem you encountered?
I’ve asked our development team for a list of animations supported when converting presentations to HTML5. I will provide it to you as soon as I receive it.
Thank you very much for the clarification and for checking with the development team.
You’re absolutely right — I initially assumed this might be a limitation because in my test export, only the first animation per shape was being played in the HTML5 output. That led me to suspect there might be a one-animation-per-shape restriction.
To illustrate the issue clearly, I’ve attached both the PowerPoint presentation and the corresponding HTML5 export generated using Html5Options. In the presentation, you’ll see multiple animations applied to a single shape, but in the HTML output, only the first one seems to play.
Looking forward to your feedback — and to the list of supported animation types when it becomes available.
@ChristianVoss,
Thank you for the sample presentation file. I’ve reproduced the problem with playing the shape animations when converting the presentation to an HTML document.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SLIDESPHP-100
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Thank you very much for reproducing the issue and for opening the internal ticket — I really appreciate your support and transparency.
I’ll keep an eye on the ticket’s progress and look forward to hearing back when a fix becomes available. In the meantime, I’ll consider possible workarounds for our current use case.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.