There’s a nice summary of one2edit functionality on creativepro.com today.
Adobe’s Leandro Reis published a nice article on his blog about global publishing with Adobe DPS. He gives one2edit a nice mention as a tool to be used for collaborative editing and translation of Adobe InDesign documents.
The article contains a lot of useful information as a starting point for anyone looking to deliver localized documents on tablets, as well as a number of links useful to anyone creating InDesign documents in multiple languages:
The linguistic capabilities of InDesign are well documented in the product’s help pages, and in articles written by various InDesign experts. Below are some language-specific topics that can assist in the creation of multilingual content in InDesign:
I highly recommend giving this article a look.
“The real challenge moving forward will be to combat the misinformation and confusion that an announcement like this brings.” – Lee Brimelow, Adobe Systems
Adobe’s announcement regarding their discontinuation of development of Flash Player for browsers on mobile devices created much fear, uncertainty and doubt (FUD) for all their enterprise customers who have invested in Flex and AIR for solution development. The announcement didn’t need to do that. Adobe could have been more proactive in communicating their strategy in a way that anticipated these fears, and enterprise developers and customers could have also paid closer attention to what Adobe actually announced rather than reflexively hitting the panic button.
Given Adobe’s track record of pulling the plug on projects and products, this kind of response is understandably Pavlovian by now, but–now that the dust has had a chance to settle–enterprise developers and customers can calm down and actually be encouraged by Adobe’s strategy and investments in the area of its web application platforms.
Adobe has explicitly committed to ongoing focus and support for Flash-based application development for both mobile devices and enterprise solutions, because FLEX and AIR are far more robust tools for building applications than HTML5 is now, and will be for many years.
Recently, Adobe announced that it is no longer going to be actively developing the Flash Player for mobile devices.
Adobe has seen that Flash is not going to be the way forward in the mobile device market. With this in mind, Adobe made the aforementioned announcement to say that it was now going to correctly address its position in the mobile market. This part of the announcement was quite clear.
However, Adobe neglected to clearly state that its strategy involving Flash for non-mobile devices was not going to change. With the Flash player installed on a staggering 99% of Internet-enabled computers, Adobe may have assumed that it was clear that they had no need to change the existing strategy in this space.
Furthermore, the statements that Adobe did make regarding the non-mobile Flash player – statements at which we shall look in a moment – were drowned out by the (incorrect) sound bite upon which everyone focused, i.e. that Adobe was abandoning Flash. It is this lack of clarity that has led to fear, uncertainty and doubt within the industry about the future of the Flash player for desktops.
Let me state here and now that the future of the Flash player for enterprise desktop applications, such as one2edit, is in no danger.
In this blog post, I will first allay your fears with Adobe’s own words on this matter, followed by explaining why Adobe would decide to follow this strategy.
In the original announcement by Adobe, Danny Winokur, the Vice President and General Manager of Interactive Development at Adobe, states that Adobe “will no longer continue to develop Flash Player in the browser to work with new mobile device configurations”.
This statement is specifically about mobile devices because, in the following paragraphs, Danny states that “These changes will allow us to…innovate with Flash where it can have most impact for the industry”, followed by “We are already working on Flash Player 12” and “We are super excited about the next generations of HTML5 and Flash”.
Admittedly, the wording that surrounds these statements is somewhat confusing, so Adobe was forced to clarify on a number of these issues.
We shall now look at a blog post by Mike Chambers, the principal product manager for developer relations for the Flash Platform at Adobe. This blog post, entitled “Clarifications on Flash Player for Mobile Browsers, the Flash Platform, and the Future of Flash”, sheds more light on the situation.
In the section entitled “Flash Player for Desktop Browsers”, Mike states:
“We feel that Flash continues to play a vital role of enabling features and functionality on the web that are not otherwise possible. As such, we have a long-term commitment to the Flash Player on desktops, and are actively working on the next Flash Player version.”
“Adobe will continue to support applications built with Flex, as well as all future versions of the SDK running in PC browsers with Adobe Flash Player”
Once again, this is reinforcing the fact that the desktop version of the Adobe Flash player will continue to be developed by Adobe for the foreseeable future.
So, the message is now clear – the future of the Adobe Flash player for desktops is guaranteed by Adobe.
When you’re showing off your new smartphone, you don’t open the web browser. No, you open an app. Sure, a browser might allow you to check your web email, but a dedicated email app is far more useful and user friendly.
What I’m saying is that, for more complex operations, apps are what users want on their mobile devices, not a browser-based solution. Adobe Flex and Adobe Air give developers a method of building one application for multiple platforms.
However, for simpler operations, such as streaming a video from a web page, users do not want to switch from browser to app and back again. In this case, the two options for browser developers were:
1. Use the mobile device Flash player
2. Support HTML5, a future standard that will run inside the browser
Add to this the fact that the mobile device Flash player is rather clunky and slow, and we have a clear winner in the “simple operations within a mobile browser” category.
Adobe has decided to focus on the future of simple operations within a mobile browser, HTML5, in lieu of a mobile Flash player.
The word “simple” is key here. Desktop enterprise applications are far more complex than even mobile device apps. For example, one2edit is not a simple program aimed at the mobile device market. It is a complex cross-platform desktop application, the needs of which HTML5 cannot meet. In fact, there are a very large number of companies using Flash for enterprise applications. For this reason alone, there is still a need for the Flash player on the desktop, and Adobe has said that it will cater to this need.
“…just to be clear, this announcement pertains to the browser plug-in on mobile devices only. The Flash browser plug-in on the desktop remains important and viable and even critical for many use cases, and we’ve publicly committed to adding value and features and functionality to better address just these use cases”
This means that, for the foreseeable future, there will be a platform on which one2edit can run. Flash, and therefore one2edit, is not dead.
Adobe has recently announced that it will be donating the Flex source code to the open source community, via Apache, for further development. This is good news and should not be feared.
Flex Becomes More Flexible
Adobe Flex has been open source for some time now, but it was being maintained by Adobe. This meant that Adobe was responsible for Flex’s roadmap, releases, updates, bug fixes, etc. By donating Flex to the Apache Software Foundation, bugs can be fixed and features added by developers as needs arise, without needing to resort to contacting Adobe and reporting the bug/requesting the feature.
“[Adobe knows] that the technology landscape for application development is rapidly changing and [Adobe’s] customers want more direct control over the underlying technologies they use.”
This means that, in the future, Flex will become a more agile and innovative tool for developers. It means that 1io’s developers can tweak Flex to help with future features and development of one2edit.
Adobe’s Continued Commitment to Flex
“Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility.”
This underlines the fact that Adobe is not “giving up” on Flex as some rumours have stated.
By giving the open source community control over Flex’s roadmap, the tool can flourish, with new features coming from the community and not being controlled from within Adobe. This will open up the tool to far more innovation than has been the case until now.
How This Affects one2edit’s Customers
You, the customer, should be excited about this turn of events. One2edit’s developers sure are.
Why? Well, for one thing, because one2edit is written with Flex, the code base can be used to develop native apps for iOS and Android using Adobe Air. This opens up exciting new possibilities for one2edit companion products. We currently have an app under development that will allow the reviewing of one2edit documents using a tablet device.
It must be stressed, however, that the custom HTML-based interfaces that have been, and will continue to be, built for one2edit are in no way affected by this. The need for creating mobile apps via Flex for use on Adobe Air is one that only our developers feel. The standard one2edit Webservice API is still fully functional and has not been changed in any way by this.
The Future of Flex
“Adobe will continue to support applications built with Flex”.
This means that one2edit, which is written with Flex, will continue to be supported by the Flash player indefinitely.
In conclusion, Flex being given to the open source community by Adobe only has positive knock-on effects. It will lead to increased innovation and the faster, more secure development of applications.
Here’s an example of how easy it is to learn to use one2edit’s online InDesign document editing features. This is an actual training video produced by DHL for users of its Ad Integrator web application. Ad Integrator enables users to create ads using live, online Adobe InDesign templates. It takes less than 5 minutes for the narrator to walk a new user through the editor features enabled in DHL’s implementation of one2edit.
This fully automated ad creation workflow portal for DHL’s intranet was implemented in just 6 weeks by Brand Implementation Group (BIG), 1io (with one2edit as the leading web application), and Quickcut/Adstream (dynamic layout adaptation, printer specific profiled PDF delivery, etc). This system is now being used to create ads in 73 countries, and demonstrates the power of one2edit’s APIs that enable the standard product to be integrated into large scale enterprise solutions like DHL’s.
Meet one2edit and the 1io UK staff at mediaPro show in London, UK, November 1-2 2011.
We’re located at booth A40 and will present version 3.6 of one2edit®. one2edit® is a browser-based workflow solution for the online editing, translation and review of live Adobe® InDesign® documents.
At mediaPro, 1io will be showing the live, rights managed, WYSIWYG editing of Adobe InDesign documents in a web browser, as well as how the system can be applied to create powerful, more efficient enterprise brand management solutions.
mediaPro 2011 is a free-to-attend exhibition and seminar program about delivering effective integrated communications across digital, social and print media for marketers, brand managers, agencies and the media.
What is one2edit? It’s the best way to edit Adobe InDesign documents in a web browser. You don’t have to train your team on InDesign and InCopy. You don’t have to trust that they won’t ruin your brand identity by modifying elements they’re not supposed to. You can save lots of time and money by letting one2edit manage your documents and workflows, and enable all your editors, translators and reviewers do their work in an easy-to-use, WYSIWYG web browser interface. If you’re a printer or a developer, one2edit’s RESTful web services APIs enable you to integrate it with DAM/MAM and production systems to create custom web-to-print applications for your internal or external customers. To get an end-to-end demo of one2edit, fill out our contact form here.
1io will be showing one2edit 3.5 (and maybe some new functionality) and answering your questions a the Marcom show in Amsterdam.
1io shows one2edit at the web2print event W2P 2011 in Veenendaal on April, 14th.
Meet our product specialists Alex van Eesteren and Tim Cole.
Read more about the event here!