Category Archives: Blog

Your blog category

adobe acrobat versions

Variations of PDF Products from Adobe

Leave a reply

Here’s a comparison of Adobe Reader, Adobe Acrobat Standard, and Adobe Acrobat Pro versions of pdf software offerings:

FeatureAdobe ReaderAdobe Acrobat StandardAdobe Acrobat Pro
View, print, share, comment on PDFsYesYesYes
Edit text and images in a PDFNoYesYes
Create, fill, sign, send formsBasicYesYes
Collect signaturesNoYesYes
Send bulk e-signature requestsNoYesYes
Create standout documentsNoYesYes
Admin tools to manage teamsNoNoYes
Convert documents to/from PDFNoYesYes
Advanced PDF features (e.g., redaction)NoNoYes
Security (password protection)NoYesYes
Cloud StorageLimitedYesYes
Access anywhere (desktop, mobile, web)YesYesYes
Customer supportLimitedYesYes
TutorialsYesYesYes
  • Adobe Reader: This is a free application for viewing, printing, and annotating PDFs. It is often know as the Adobe Acrobat free version. It’s available on desktop and mobile platforms. However, it lacks the advanced features found in the Standard and Pro versions, like extensive editing capabilities, advanced security, and administrative tools​​.
  • Adobe Acrobat Standard: This version offers more functionality than Adobe Reader, including the ability to edit text and images within PDFs, convert documents to and from PDF format, and more advanced form features. It’s tailored for personal or small business use, where the need for advanced document management and security is lower than in larger organizations​​.
  • Adobe Acrobat Pro: This is the most feature-rich version of Acrobat, designed for professional and business use. It includes all the features of Acrobat Standard, plus additional tools for editing scanned documents, comparing PDF files, redacting sensitive information, creating web forms, and collecting payments. It also offers advanced e-signature features and the ability to send bulk e-signature requests. Acrobat Pro provides the most comprehensive PDF solution for complex document management needs and complies with industry-specific standards​​​​.
  • Adobe Acrobat Teams: The same as the pro version but with addtional Admin tools to manage teams

These distinctions help users and organizations decide which version best fits their needs, balancing functionality with cost. Adobe’s pdf software offerings cater to a wide range of use cases, from basic PDF viewing and commenting with Reader to comprehensive document management and security with Acrobat Pro.

History of Aldus/Adobe PageMaker

Leave a reply

Taking a look at the history of Aldus/Adobe PageMaker means revisiting one of the initial desktop publishing software programs. This major player paved the way for the revolutionary impact of Adobe InDesign on the industry. Let’s delve into its version timeline, tracing its development from Aldus Corporation to its ultimate versions released by Adobe.

Version Features and Improvements
PageMaker 1.0 (1985) Launched by Aldus Corporation for the Macintosh, introducing the concept of desktop publishing.
PageMaker 2.0 (1987) Introduced for IBM PCs, expanding the desktop publishing revolution to the Windows platform.
PageMaker 3.0 (1988) Enhanced text and graphics handling, including support for PostScript printers, which solidified its use in professional settings.
PageMaker 4.0 (1990) Improved layout and design features, making it easier for users to produce sophisticated documents.
PageMaker 5.0 (1993) Added features like story editor, booklet printing, and improved typography controls, catering to higher-end publishing needs. PDF support first added in the European version.
PageMaker 6.0 (1995) Introduced new templates, tools for color separation, and support for plug-ins, enhancing its versatility in desktop publishing. PDF Export.
PageMaker 6.5 (1996) Improved support for PDF and HTML formats, enabling users to prepare documents for the web and digital distribution.
PageMaker 7.0 (2001) Last major release, added integrated Adobe PDF export features, and improved support for importing/exporting files from other Adobe apps.

The evolution of Aldus PageMaker mirrors the early era of desktop publishing, when the primary goal was to empower individuals to create and share documents on their computers. Its purchase by Adobe and eventual replacement with InDesign symbolized the conclusion of one era and the start of a new phase in digital design and publishing. PageMaker established the foundation for the advanced features and functionality that InDesign would later bring to the publishing industry.

Associated Links

PDF – The Evolution of the Portable Document Format : A Historical Perspective

History of PDF

Adobe InDesign History

Leave a reply

During the 1990 parallel development was being done in Seattle for a replacement for Aldus PageMaker. Initially it was going to be named PageMaker Pro, but during development it had the code name k2 and internally within Aldus it also had the nickname “Quark Killer”. The main competitor and standard in the Desktop publishing arena was Quark Express (hence the nickname). The team working on this project was quite small and PageMaker was still the main product in development. In the mid-90s Adobe and Aldus merged and one of the main new developments in PageMaker 6 followed by PageMaker 6.5 was the integration between PageMaker and Adobe Acrobat which had just been released with the Export PDF feature.

Below is a table outlining the successive releases of Adobe InDesign and some of the main features for each release. The idea over all of this time was to have a product that mainly comprised of plug-ins with a relatively small executable. InDesign and InCopy are basically the same base product but with a different set of plug-ins as are InDesign Server and the desktop version of InDesign.

VersionFeatures and Improvements
InDesign 1.0 (1999)Initial launch introducing a new era in digital publishing.
InDesign 1.5 (2000)Improved productivity and compatibility, support for more languages.
InDesign CS (2003, v3.0)Integration into Adobe’s Creative Suite, enhancing interoperability with Photoshop, Illustrator, and Acrobat.
InDesign CS2 (2005, v4.0)Object Styles, Adobe Bridge integration, better PDF and XML export options.
InDesign CS3 (2007, v5.0)Transparency effects, table styles, improved text and typography control.
InDesign CS4 (2008, v6.0)Support for interactive documents, GREP find/replace, conditional text, and cross-references.
InDesign CS5 (2010, v7.0)Enhanced interactive document capabilities, new layers panel, span/split columns feature.
InDesign CS5.5 (2011, v7.5)Focus on digital publishing, especially for tablets, with features for interactive eBooks and improved ePub export.
InDesign CS6 (2012, v8.0)Alternate layouts, Liquid Layout, content collector tools. Last version before Adobe Creative Cloud transition.
InDesign CC (2013, v9.0)Transition to a subscription-based model as part of Adobe Creative Cloud, bringing regular updates and cloud-based features.
InDesign CC 2014 (v10.0)Improved packaging, EPUB enhancements, simplified hyperlinks.
InDesign CC 2015 (v11.0)Paragraph Shading, Graphic Cells for tables, updates to Adobe Publish Online service.
InDesign CC 2017 (v12.0)OpenType enhancements, better footnote placement, scalability options.
InDesign CC 2018 (v13.0)Endnotes, paragraph borders, object height and width styles, improved export to HTML.
InDesign CC 2019 (v14.0)Improved user experience with layout adjustments, PDF accessibility enhancements, Content-Aware Fit introduction.
InDesign 2020 (v15.0)Support for SVG import, variable fonts, automatic layout adjustment.
InDesign 2021 (v16.0)Performance improvements, Share for Review, enhancements to subject-aware text wrap.
InDesign 2022 (v17.0)Introduction of improved collaboration tools and user interface enhancements, performance improvements, new and enhanced typography features, accessibility improvements.
InDesign 2023 (v18.0)Enhanced Collaboration Tools, Performance Improvements, Typography and Font Enhancements, Accessibility Improvements.
InDesign 2024 (v19.0)AI-Powered Features, Improved User Interface, Advanced Integration with Creative Cloud, Sustainability and Eco-conscious Design.

Associated Links

History of Aldus/Adobe PageMaker

Adobe InDesign Software Development Solutions Plugins & Tools

InDesign CC 2024 – New features

Design Better Add-Ons for Adobe Express with Our UX Guidelines

Leave a reply

Design Better Add-Ons for Adobe Express with Our UX Guidelines

Introduction

Adobe Express is a powerful tool that allows users to edit photos, create designs, and enhance their creativity. With its wide range of features and functionalities, Adobe Express offers a great platform for designers and developers to create add-ons that can further enhance the user experience.

In this article, we will provide you with some UX guidelines that will help you design better add-ons for Adobe Express. These guidelines will ensure that your add-ons are user-friendly, visually appealing, and seamlessly integrate with the existing functionalities of Adobe Express.

Adobe have a set of controls that greatly help in providing the developer interfaces in the Spectrum UXP which is used with the JavaScript Developer Framework, UXP (Unified Extensibility Platform).

1. Understand the User’s Workflow

Before you start designing an add-on for Adobe Express, it is crucial to understand the user’s workflow. Take the time to analyze how users interact with the tool, what tasks they commonly perform, and what pain points they may encounter.

By gaining a deep understanding of the user’s workflow, you can design add-ons that seamlessly fit into their existing processes and provide value without disrupting their creative flow.

2. Keep it Simple and Intuitive

Simplicity and intuitiveness are key when designing add-ons for Adobe Express. Users should be able to easily understand how to use your add-on without any confusion or frustration.

Avoid cluttering the interface with unnecessary elements. Keep the design clean and minimalistic, focusing on the core functionality of the add-on. Use clear and concise language in your instructions and tooltips to guide users through the process.

3. Consistency is Key

Consistency is crucial when designing add-ons for Adobe Express. Your add-on should adhere to the overall design language and branding of Adobe Express to provide a seamless user experience.

Ensure that the colors, typography, and iconography used in your add-on align with the existing design patterns of Adobe Express. Consistency will not only make your add-on visually appealing but also make it easier for users to navigate and understand.

4. Optimize Performance

Add-ons should not compromise the performance of Adobe Express. Users expect a smooth and fast experience when using the tool, and your add-on should not cause any lag or delays.

Optimize your add-on’s code to ensure efficient performance. Minimize unnecessary network requests, optimize image loading, and avoid any memory leaks or performance bottlenecks. Test your add-on thoroughly to ensure it does not impact the overall performance of Adobe Express.

5. Provide Customization Options

Users love customization options that allow them to personalize their experience. Provide users with the ability to customize your add-on according to their preferences.

Allow users to adjust settings, change themes, or customize the interface to suit their needs. This level of customization will make your add-on more versatile and appealing to a wider range of users.

6. Seek User Feedback

Feedback from users is invaluable when designing add-ons for Adobe Express. Regularly seek feedback from your users to understand their pain points, suggestions, and ideas for improvement.

Consider implementing user feedback into future updates of your add-on. This will not only enhance the user experience but also build trust and loyalty among your user base.

Conclusion

Designing better add-ons for Adobe Express requires a deep understanding of the user’s workflow, a focus on simplicity and intuitiveness, consistency with the overall design language, optimized performance, customization options, and regular user feedback.

By following these UX guidelines, you can create add-ons that seamlessly integrate with Adobe Express and enhance the user experience for all its users. Remember, the key is to design add-ons that provide value, improve efficiency, and make the creative process more enjoyable for Adobe Express users.

Associated Links

Why Custom Software Solutions Are Key to Business Efficiency

The Way We Do Software Development

Adobe XD End of Life

Leave a reply

Adobe XD no Longer to be Supported

As of early 2024, Adobe has confirmed that it will not be investing further in Adobe XD, its vector design tool used for web and mobile app development. 

This decision comes after Adobe’s attempt to acquire Figma, a competing design tool, was blocked by regulatory scrutiny. 

Adobe XD is currently in maintenance mode, which means the company will continue to support existing customers by addressing bugs and updating any security or privacy needs but will not develop new features or push the product further. 

Adobe has also confirmed that XD is no longer being sold as a single application to new customers and has no plans for further investment in the product.

Additionally, Adobe has mentioned that XD will continue to be available as part of the Creative Cloud All Apps subscription for existing users, although it is no longer available for purchase as a single application. This means that while current users will continue to receive support, the focus on innovation and new features for XD has ceased, and the product will not be a priority for Adobe moving forward.

This situation has led to discussions within the design community about the future of UX/UI design tools and whether users should start considering migration to alternative platforms like Figma or Sketch. The community expresses concern over the lack of clarity on Adobe XD’s future and how it impacts their workflow and integration with other Adobe products.

For teams deeply integrated with Adobe XD, this news may necessitate reevaluating their design toolchain, considering other options that continue to receive active development and support.

Other Links

Adobe Unified Extensibility Platform (UXP)

Author:

Michael Peters – mpeters@creativeaddonshub.com

https://creativeaddonshub.com

What next?

If you are interested in discussing our consultancy and software development services further then please send an email to info@creativeaddonshub.com by clicking the button below:
Click Here

ExtendScript

Leave a reply

Adobe ExtendScript: Applications, Usage, and Limitations

Adobe’s ExtendScript is a robust scripting language based on JavaScript, enabling automation, customization, and extension of Adobe’s Creative Cloud applications. This powerful tool allows developers and designers to streamline their workflows, create custom functionalities, and automate repetitive tasks. This blog post explores the applications supporting ExtendScript, its uses within these applications, the JavaScript version it’s based on, its limitations, and its utility in plugins. We’ll also provide examples and source code snippets to illustrate the scripting in action.

Supported Applications

ExtendScript is primarily used with Adobe applications, offering a versatile range of possibilities for automation and customization. Key Adobe applications supporting it include:

  • Adobe Photoshop: Automate tasks, create custom scripts for image processing, and more.
  • Adobe Illustrator: Generate scripts for automating drawing tasks, batch processing, and custom tool creation.
  • Adobe InDesign: Automate layout designs, text formatting, and streamline publishing workflows.
  • Adobe Premiere Pro: Customize video editing workflows, automate sequences, and effects.
  • Adobe After Effects: Create scripts for animation, automate effects, and manage compositions.

Utilization in Applications

Each Adobe application utilizes ExtendScript in unique ways, catering to the specific needs of the software’s functionality:

ExtendScript in Adobe Photoshop

In Photoshop, a script can automate complex imaging processes, batch process images, and customize user interactions. For example, a script can automate the process of resizing a batch of images:

				
					var folder = Folder.selectDialog("Select a folder");
var files = folder.getFiles("*.jpg");

for (var i = 0; i < files.length; i++) {
  var file = files[i];
  open(file);

  // Resize image
  activeDocument.resizeImage(800, 600, 72, ResampleMethod.BICUBIC);

  // Save and close
  var saveOptions = new JPEGSaveOptions();
  saveOptions.quality = 8;
  activeDocument.saveAs(file, saveOptions, true, Extension.LOWERCASE);
  activeDocument.close();
}

In Adobe Illustrator

In Illustrator, ExtendScript can create custom shapes, manage document layers, and automate design tasks. Here’s an example of creating a simple rectangle with ExtendScript:

				
					var doc = app.documents.add();
var layer = doc.layers[0];
var rect = layer.pathItems.rectangle(100, 100, 200, 100);
rect.fillColor = new RGBColor();
rect.fillColor.red = 255;
rect.fillColor.green = 0;
rect.fillColor.blue = 0;

In Adobe InDesign

ExtendScript in InDesign can automate layout creation, style application, and batch processing of documents. For instance, applying a paragraph style to text:

				
					var doc = app.activeDocument;
var textFrames = doc.textFrames;
if (textFrames.length > 0) {
  var textFrame = textFrames[0];
  textFrame.texts[0].appliedParagraphStyle = doc.paragraphStyles.item("Heading 1");
}

ExtendScript in Adobe Premiere Pro & After Effects

In Premiere Pro and After Effects, ExtendScript allows for automation of editing tasks, effects, and compositions. For example, in After Effects, a script can automate the creation of a composition:

				
					var comp = app.project.items.addComp("New Composition", 1920, 1080, 1, 30, 30);
comp.openInViewer();

JavaScript Version and Limitations

ExtendScript is based on an older version of JavaScript (ECMAScript 3), which introduces some limitations compared to modern JavaScript standards. Consequently, these limitations include the lack of support for newer syntax and features introduced in ES6 and beyond, such as let/const, arrow functions, promises, and async/await. Despite these limitations, it provides a robust API specific to Adobe applications, offering deep integration and control over software functionalities.

Enhanced Use in Plugins: A Dive into ExtendScript within CEP Extensions

ExtendScript’s utility transcends simple script execution within Adobe applications—it serves as the backbone for developing more complex, feature-rich plugins through Adobe’s Common Extensibility Platform (CEP). CEP allows for the creation of extensions that can interact deeply with Adobe Creative Cloud applications, offering a blend of HTML5, CSS, JavaScript, and ExtendScript to create rich, user-friendly interfaces and functionalities.

Understanding CEP Extensions

CEP extensions are essentially web applications that run inside Adobe applications, enabling developers to create sophisticated, non-modal dialog boxes and panels using standard web technologies. These extensions can then call ExtendScript code to perform tasks within the host application, bridging the gap between modern web technologies and the extensive automation capabilities of ExtendScript.

Integration with ExtendScript

The integration of ExtendScript within CEP extensions is facilitated through a scripting bridge, allowing JavaScript code running within the CEP extension to execute ExtendScript code within the context of the host application. This hybrid approach leverages the best of both worlds: the modern capabilities and user experience of web technologies, and it’s deep application-specific scripting capabilities.

Example: A Photoshop CEP Extension

Consider a Photoshop CEP extension designed to automate the process of applying a series of filters and adjustments to a selection of images. The extension could use HTML and CSS to provide a user-friendly interface for selecting filters and adjustments, while JavaScript manages the application logic and interactions. When it comes to applying the selected operations to images, the extension would execute ExtendScript code to automate Photoshop tasks.

Here’s a simplified example of how such an extension might invoke ExtendScript code:

				
					// JavaScript function within the CEP extension
function applyFiltersToImage(imagePath, filters) {
  var script = `
    var file = new File("${imagePath}");
    app.open(file);
    
    // Example of applying a blur filter
    app.activeDocument.artLayers[0].applyGaussianBlur(${filters.blurAmount});
    
    // Save and close the document
    var saveOptions = new JPEGSaveOptions();
    saveOptions.quality = 8;
    app.activeDocument.saveAs(file, saveOptions, true, Extension.LOWERCASE);
    app.activeDocument.close();
  `;

  // Execute the ExtendScript code
  csInterface.evalScript(script, function(result) {
    console.log('Filters applied successfully');
  });
}

In this example, csInterface.evalScript() is used to execute ExtendScript code from within the JavaScript context of the CEP extension. This method allows for passing ExtendScript code as a string to be executed within the host application (Photoshop, in this case), enabling the extension to perform complex tasks like opening an image, applying filters, and saving the document.

Conclusion on Using ExtendScript in Plugins

The integration of ExtendScript within CEP extensions has long provided a powerful means to enhance the capabilities of Adobe plugins, combining the depth of application-specific scripting with the user experience of modern web technologies. However, it’s important to note the evolving landscape of Adobe extension development, particularly with the introduction of the Unified Extensibility Platform (UXP). UXP is gradually replacing CEP and ExtendScript in certain Adobe applications, aiming to offer a more modern, efficient, and secure way to develop plugins and extensions.

Unified Extensibility Platform (UXP)

UXP provides a new standard for developing extensions across Adobe Creative Cloud. It leverages contemporary web technologies without the need for ExtendScript. Despite this shift, ExtendScript and CEP continue to hold significant value for applications where UXP support is either emerging or not yet fully implemented. Both provide a way of combing user interfaces and in-application functionality. For developers and creative professionals, this transition period involves adapting to new tools and workflows, while also leveraging the established power of ExtendScript within CEP for applications where it remains supported.

As Adobe continues to expand UXP’s capabilities and application support, the role of ExtendScript and CEP may diminish in favor of this newer, more unified platform. Nevertheless, the legacy and impact of ExtendScript in automating and extending Adobe applications will remain a critical chapter in the history of creative software development, providing a foundation from which future innovations will continue to build.

The shift from ExtendScript and CEP to UXP in Adobe Creative Cloud marks a pivotal evolution in plugin development, embracing modern web technologies for a more efficient, secure development process. While UXP’s adoption progresses, with support in Photoshop and emerging use in InDesign, ExtendScript remains vital for applications like Illustrator, where UXP is not yet integrated. This transition period is crucial for developers to leverage both the legacy power of ExtendScript and the innovative potential of UXP, ensuring a seamless adaptation to Adobe’s evolving platform ecosystem.

The Extendscript Toolkit

The ExtendScript Toolkit, now deprecated in favor of the VS Code Debugger, served as an interactive development and testing environment for ExtendScript across Adobe’s JavaScript-enabled applications. It featured a syntax-highlighting text editor, Unicode support, and a JavaScript debugger for step-through debugging, data inspection, and breakpoint management. Despite its deprecation, the toolkit’s documentation remains available for legacy reference, especially noting that it won’t work on 64-bit-only versions of macOS. For more details, visit JavaScript Tools Guide CC documentation.

The VS Code Debugger is the official method for debugging ExtendScript following the deprecation of the ExtendScript Toolkit by Adobe, partly due to macOS dropping support for 32-bit apps. 

Other Links:

Author:

Michael Peters
mpeters@creativeaddonshub.com

https://creativeaddonshub.com

What next?

If you are interested in discussing our consultancy and software development services further then please send an email to info@creativeaddonshub.com by clicking the button below:
Click Here