Skip to main content
johndaigle
Legend
May 17, 2007
Question

Lots of goodies seen at the Adobe RoboHelp STC sneak peeks

  • May 17, 2007
  • 20 replies
  • 5182 views
In three different sessions at the STC conference in Minneapolis I saw pre-beta demonstrations of RoboHelp "next". Certainly there's a mind-boggling number of new features. But more than that, Adobe has spent a lot of time listening to authors about ways to make their workflow easier. The presentations were made by Akshay Madan, Adobe Product Manager for RoboHelp. He and his team have obviously been busy! Here's a recap:

1. What struck me right away was a multiple document interface (MDI). You can work nicely among any number of topics that are open and displayed in tabs. I'm glad to see that they are not planning to throw the baby out with the bathwater. The popular and friendly Word-like WYSIWYG editor is still central to the main work area. You still feel like a writer and not a coder (no offense to programmers).

2. At the same time, the UI is more modern and cleanly laid out. There are also customizeable toolbars and "pods" that can be moved around and configured the way the author works. These configurations can be given a name so for example, an author can have a layout for authoring sessions and one for editing sessions.

3. These movable panels or pods are handy, but I also like that you can quickly return to "factory defaults" in case the layout becomes too fragmented.

4. No <kadov> tags! These much-maligned tags are often used by competitors to bad-mouth RoboHelp. Well, they'll have to come up with something else because I saw nice clean, color-customizable code behind the WYSIWYG editor.

5. There is also Unicode and double-byte support for something like 34 different languages including Asian and Eastern European characters.

6. For single sourcing, the author can create multiple TOCs and name them so that they are easy to use when generating output for different audiences (or for print vs. online).

7. Help for translators: Because of MDI, a translator can have an English topic open in a pane side-by-side with a Japanese topic for easier comparison and editing. Languages can also be mixed. So, I can have Japanese, Greek or any number of words or phrases mixed within a topic. The same is true for the TOC, Index of keywords or Glossary of terms and definitions.

8. Snippets of HTML code make it easy to have chunks of text and graphics saved for re-use. For example a logo graphic and copyright statement can be saved and placed in multiple topics. If you change the logo or text in the snippet, the changes are populated wherever the snippet has been placed (kind of like RoboHelp 6's User Defined Variables on steroids).

9. Breadcrumbs offer a nice touch for the user experience with links that show the user where they are in the heirarchy of topics.

10. Searching in WebHelp/Flashhelp: When searching, the "hit" terms are highlighted in a color of the author's choosing. This can easily be turned off by the user as well.

11. Much improved Framemaker MIF support. Matthew Stern was at STC and was impressed. "You can import a MIF file directly into RoboHelp and everything is retained: variables, graphics (including Flash and Acrobat 3D files), and conditional text."

12. There is support for MS Vista and Office 2007 including the new XML-based .docx format, (though this was not yet enabled in the pre-alpha build I saw.)

13. Better Screen capture manipulation within topics.

14. Adobe representatives also said there would be news posted on the Adobe TechComm Blog with invitations to sign up for the beta program when it gets underway.

After using RoboHelp since 1992, I get caught up in the feature race like everyone else. But, as Vivek Jain, Group Product Manager for RoboHelp said, features are not the only thing that define innovation. Rather he says, "Quality is innovation."

This should put a rest to the "RoboHelp is dead" garbage.

As a user and instructor since 1992 it was very satisfying and exciting to see these sneak peeks and that Adobe is not only bringing RoboHelp back to life, but making it a central piece of the suite of applications that make up the Technical Communications (RoboHelp, Framemaker, Captivate and Acrobat).

Sneaks peeks were also shown for Adobe Framemaker 8 and Adobe Captivate 3 as well. The sneak peeks were introduced with the usual caveats, such as,“The features presented during the Technology Sneak peek contain proof of concept features and features in the development pipeline. They are not final for the next release however we want to take this opportunity to show the general direction of where we are taking the products.” They also mentioned that while they cannot comment about release dates, they "expect to see new releases this year." However, from what I saw, this pre-alpha build looked stable and rich with the functionality I've outlined.

It's an exciting time for technical communicators!
John
Evergreen Online Learning, LLC
Evergreen, Colorado

    This topic has been closed for replies.

    20 replies

    August 28, 2007
    I missed this post in May but since subscribed to this forum, so thanks to js for "reviving" the thread. Thanks, John, for the list of features--I'm looking forward to trying out the next version when it is released. I'm thinking I'll use most of your 14 points when asking management for an upgrade.

    A comment on the RoboHelp-Flare contest: One of the reasons I didn't switch to Flare was that their campaign seemed more anti-RoboHelp than pro-Flare, and it came across pretty mean-spirited. (It's also strange to me that a bunch of developers--the RoboHelp-turned-Flare group--would tear down the product they brought to the point it was at before Adobe took it off the shelf...) The main reason I didn't switch was that Flare didn't have any features that made me sit back and say "Wow," and RoboHelp still allowed me to do some things that Flare didn't for all its improvements. It's looking to me like my decision to hide and watch what Adobe would do with RoboHelp was a good one.

    --Ben
    Peter Grainge
    Community Expert
    Community Expert
    August 28, 2007
    No further news on the date. You will be able to open projects from earlier versions. No reported problems on that from the beta testers.

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Inspiring
    August 28, 2007
    Is there an estimate on when RoboHelp 7 will be released?

    I found RoboHelp had been updated around July and that 7 would be release by the end of the year.
    So to verify the obvious, RoboHelp 7 will be able to open RoboHlep HTML x5.0.2 files.
    johndaigle
    Legend
    August 28, 2007
    Hi, js.
    Can't say too much more than "by the end of the year". My coy way of responding is that back in May I saw a very stable build demonstrated in public at the STC conference in Minneapolis. That suggests to me that it will be sooner rather than later. Sorry nobody knows for sure. Rest assured. We will shout it from the rooftops here on the Forums when it is announced.

    As to your question about opening RoboHelp X5 in the new RoboHelp 7, absolutely! Most older versions are converted "on the fly" when you open an .MPJ or .XPJ project file. However, once converted, you can't go back without a bit of hassle.
    Thanx
    john
    John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
    Participant
    June 21, 2007
    Thank you for the summary.

    Was there any talk of supporting Eclipse help format?

    Rhonda
    Inspiring
    June 5, 2007
    Hi John,
    Thanks for this report. All seems to moving in the right direction in terms of features for RoboHelp Office.
    I don't know if you remember but I and the network admin where I work had posted a bunch of threads in the RoboEngine section of this forum reporting a series of failures of RoboHelp Server 6 (for some reason, they "disappeared" from the forum, really pi**ed off about this, there was a lot of info there). Well due to these problems, we had to revert back to the previous version of RoboEngine. This previous version does support load balancing and the webserver part of the application does not crash when more than two users are connecte to the help system.
    You had mentionned that you would touch a word to Adobe about this at the STC convention? Any news on this? Any information on future developments for RH Server 7 to make it more robust and support load balancing?
    Thanks!
    Chris
    June 5, 2007
    Chris,

    If you go into your profile in Personal options, you can set the number of days back that you want to display threads. You should find the threads you posted.

    Hope this helps,

    Brian
    Gravenstein
    Inspiring
    May 31, 2007
    Thanks, John! That was very helpful.

    Was there any mention of further changes to RoboSource Control? I am just starting to investigate RoboSource Control 3 now, so I don't know what additional features I'd want, but I'm sure curious about what might be in the works.

    And I'm happy about the demise of kadov tags. Mostly they're harmless, but in some particular instances of our help they cause javascript errors. I won't be sorry to see that disappear.

    Cheers,
    G
    johndaigle
    Legend
    June 1, 2007
    Hey LaKisha1 and Gravenstein
    Hooray for snippets! As far as RoboSourceControl 3 updates, that was not mentioned one way or the other at the STC sneak peek. I'm thinking there would not be anything major because it is so new. I set it up with the free MS SQL Server Express and it works quite well, even on my laptop. It is definitely more stable and has many more features than the old version which used the fragile Access database as the default.

    Matthew Ellison has an article on the new version on the Adobe Developer Network
    Getting started with RoboSource Control 3 in RoboHelp 6

    Fortunately the GUI has not radically changed so my article on the older version might also be of help to those just getting started. It kind of picks up where Matthew's article leaves off.
    Sharing One RoboHelp Project Among Multiple Authors
    Give it a try
    John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
    LaKisha1
    Inspiring
    May 29, 2007
    Thanks soooo much for the report! I'm particularly happy to hear that we'll most likely be able to save and reuse code snippets. I've often wondered why Macromedia’s Dreamweaver allowed you to save and reuse HTML code snippets, and then Macromedia acquired RoboHelp but they didn’t quickly add this tremendously helpful feature to RoboHelp!!!
    Inspiring
    May 29, 2007
    What we are seeing is an "arms race" between Adobe and MadCap in terms of the features they offer in RoboHelp and Flare. This can only be good for the customer.
    May 24, 2007
    Hi all,

    That certainly looks like a promising list of possible enhancements. :-)

    I've been putting off switching to Flare for a few reasons (for me, the user friendliness of the editor doesn't appeal) and have been hoping that Adobe would pick up on RoboHelp and develop it further.

    RoboHelp's ease of use just seems to allow me to concentrate more on creating content and that has always been its major advantage.

    Maybe I'm just getting lazy, and I know all software has its foibles, but spending time fighting with an editor to get the output to look and behave how I want is not where I want to be. Even the great RoboHelp kadov debate doesn't bother me so long as the output works, but, if they can get rid of proprietary tags so the code is more compliant - brilliant.

    The X6 release came across as a first step but not necessarily a needed upgrade - the stuff they're talking about for the next release looks much more promising, and definitely feels like a reason to hang on with RoboHelp a while longer.

    By the way, does anyone know if the X6 version still strips out meta tags from source when you produce output files? The feature list of X6 didn't prompt me to upgrade immediately, but X5 gives me a world of hurts with metatags, and that could actually be something that could get me to shell out some dosh for the X6 version rather than wait for what looks like a major new release.

    Sorry for being lazy and not installing the trial to see, but I'm a bit tight on project time so if anyone knows I'd really appreciate it. Thanks.

    PS - something that made me laugh out loud this morning:

    "One of the most interesting requests from customers at the STC Conference Minneapolis was for a migration path from Flare to RoboHelp. Clearly, some of the customers, who had migrated from RoboHelp to Flare, want to come back to RoboHelp."
    http://blogs.adobe.com/techcomm/robohelp

    The MadCap people seem very helpful, but some of their marketing comes across as too pushy, so that blog really made me smile. Maybe Adobe are almost 'too'big', but with the new release talk, it looks like things might be about to get interesting again.
    :-)

    Cheers

    Karl
    Peter Grainge
    Community Expert
    Community Expert
    May 23, 2007
    Leon

    Well as you've mentioned it...

    What I have asked for is:

    1] Stop the false reporting of links from the parent to any child project.

    2] Make it easier to create cross project links. Stop them being reported as external.

    3] In merged FlashHelp, don't strip out the cross project links! Yup if the target is not found when generating, RoboHelp says this target does not exist and ever so helpfully corrects the link to <a href>. It may not exist in the source but it does in the output, I know what I am doing, don't mess with MY code.

    I know there are some differences between our languages but I think the word you were looking for when talking about merged projects in Flare was maltreatment!

    Not following you on "Advanced help..." in the last paragraph.

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.