Search
Sort Score
Result 10 results
Languages All
Labels All
Results 11 - 20 of 355 for

notes,

(0.1 sec)

  1. Migration Notes | Documentation

    Why to migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Annotation for Java since version 19.8: The Annotator class introduced as a single entry point to manage the document annotating process to any supported file format (instead of AnnotationImageHandler class in previous versions). The overall rendering speed improved dramatically by saving rendered page as soon as it was rendered, not when all pages list were rendered....Why to migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Annotation for Java since version 19.8: The Annotator class introduced as a single entry point to manage the document annotating process to any supported file format (instead of AnnotationImageHandler class in previous versions). The overall rendering speed improved dramatically by saving rendered page as soon as it was rendered, not when all pages list were rendered.

    docs.groupdocs.com/annotation/java/migration-no...
    more..

  2. Migration Notes | Documentation

    Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Watermark for Java since version 20.1: Watermarker class is introduced as a single entry point to manage watermarks in the document (instead of Documentclass from previous versions). Adding watermarks was unified for all supported document formats. Product architecture was redesigned from scratch in order to simplify passing options to manage watermarks. Document information and preview generation procedures were simplified....Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Watermark for Java since version 20.1: Watermarker class is introduced as a single entry point to manage watermarks in the document (instead of Documentclass from previous versions). Adding watermarks was unified for all supported document formats. Product architecture was redesigned from scratch in order to simplify passing options to manage watermarks. Document information and preview generation procedures were simplified.

    docs.groupdocs.com/watermark/java/migration-notes/
    more..

  3. Migration notes | Documentation

    Why to migrate Here are the key reasons to use the new updated API provided by GroupDocs.Watermark for .NET since version 19.5: The Watermarker class is introduced as a single entry point to manage watermarks in the document (instead of Document class from previous versions). Adding watermarks was unified for all supported document formats. Product architecture was redesigned from scratch in order to simplify passing options to manage watermarks. Document information and preview generation procedures were simplified....Why to migrate Here are the key reasons to use the new updated API provided by GroupDocs.Watermark for .NET since version 19.5: The Watermarker class is introduced as a single entry point to manage watermarks in the document (instead of Document class from previous versions). Adding watermarks was unified for all supported document formats. Product architecture was redesigned from scratch in order to simplify passing options to manage watermarks. Document information and preview generation procedures were simplified.

    docs.groupdocs.com/watermark/net/migration-notes/
    more..

  4. Migration Notes | Documentation

    Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Parser for Java since version 19.11: Parser class is introduced as a single entry point to extract data from the document. Data extraction was unified for all data types. The overall document related classes were unified to common. Product architecture was redesigned from scratch in order to simplify passing options and classes to manipulate data....Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Parser for Java since version 19.11: Parser class is introduced as a single entry point to extract data from the document. Data extraction was unified for all data types. The overall document related classes were unified to common. Product architecture was redesigned from scratch in order to simplify passing options and classes to manipulate data.

    docs.groupdocs.com/parser/java/migration-notes/
    more..

  5. Migration Notes | Documentation

    How to migrate from earlier versions of GroupDocs.Conversion for .NET...How to migrate from earlier versions of GroupDocs.Conversion for .NET

    docs.groupdocs.com/conversion/net/migration-notes/
    more..

  6. Migration notes | Documentation

    How to migrate from earlier versions of GroupDocs.Conversion for Java...How to migrate from earlier versions of GroupDocs.Conversion for Java

    docs.groupdocs.com/conversion/java/migration-no...
    more..

  7. Migration Notes | Documentation

    Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Redaction for Java since version 19.6: Redactor class introduced as a single entry point to manage the document redaction process (instead of Documentclass from previous versions). Methods redactWith() of the Document class were replaced with similar apply() methods in Redactor class. Method Document.save(OutputStream, SaveOptions) was replaced with Redactor.save(OutputStream, RasterizationOptions). Constructor LoadOptions(DocumentFormatConfiguration) was removed....Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Redaction for Java since version 19.6: Redactor class introduced as a single entry point to manage the document redaction process (instead of Documentclass from previous versions). Methods redactWith() of the Document class were replaced with similar apply() methods in Redactor class. Method Document.save(OutputStream, SaveOptions) was replaced with Redactor.save(OutputStream, RasterizationOptions). Constructor LoadOptions(DocumentFormatConfiguration) was removed.

    docs.groupdocs.com/redaction/java/migration-notes/
    more..

  8. Migration Notes | Documentation

    Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Redaction for .NET since version 19.9: Redactor class introduced as a single entry point to manage the document redaction process (instead of Documentclass from previous versions). Methods RedactWith() of the Document class were replaced with similar Apply() methods in Redactor class. Method Document.Save(Stream, SaveOptions) was replaced with Redactor.Save(Stream, RasterizationOptions). Constructor LoadOptions(DocumentFormatConfiguration) was removed....Why To Migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Redaction for .NET since version 19.9: Redactor class introduced as a single entry point to manage the document redaction process (instead of Documentclass from previous versions). Methods RedactWith() of the Document class were replaced with similar Apply() methods in Redactor class. Method Document.Save(Stream, SaveOptions) was replaced with Redactor.Save(Stream, RasterizationOptions). Constructor LoadOptions(DocumentFormatConfiguration) was removed.

    docs.groupdocs.com/redaction/net/migration-notes/
    more..

  9. Migration Notes | Documentation

    How to migrate from earlier versions of GroupDocs.Merger for Java...How to migrate from earlier versions of GroupDocs.Merger for Java

    docs.groupdocs.com/merger/java/migration-notes/
    more..

  10. Migration Notes | Documentation

    Why to migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Annotation for .NET since version 19.8: The Annotator class introduced as a single entry point to manage the document annotating process to any supported file format (instead of AnnotationImageHandler class in previous versions). The overall rendering speed improved dramatically by saving rendered page as soon as it was rendered, not when all pages list were rendered....Why to migrate? Here are the key reasons to use the new updated API provided by GroupDocs.Annotation for .NET since version 19.8: The Annotator class introduced as a single entry point to manage the document annotating process to any supported file format (instead of AnnotationImageHandler class in previous versions). The overall rendering speed improved dramatically by saving rendered page as soon as it was rendered, not when all pages list were rendered.

    docs.groupdocs.com/annotation/net/migration-notes/
    more..