I am confused by this post as RoboHelp does not allow you to create AIR applications, it only allows you to create user help and deliver that as if it were an AIR application.
If you want to build AIR applications you need the AIR development tools. Go to Adobe's site and enter AIR into the search field.
See www.grainge.org for RoboHelp and Authoring tips
It is RoboHelp content which is then generated as 'Adobe AIR Application' output. It is one of the options for configuring the output, as per:
Yes, that’s true, but the locally-installed flavour of AIRHelp is a closed box – you really can’t get much under the hood like you can with your own created AIR apps. Adobe has the AIRHelp output locked down. You need to check out the developer community forum - http://forums.adobe.com/community/air
Thanks for the reply, Jeff - I will ask the question in the Air forum and repost here anything that looks interesting.
In the meantime... if anyone else has any experience adding a serial / licensing function to AIRHelp applications I would be *extremely* keen to hear from you.
Please do post here or send a direct message if you prefer.
I have seen your post in the AIR forum. There is no confusion here since you replied saying that the core of what you want to do is describe some business processes. That can be done using RoboHelp.
AIR Help, as explained, is created from RoboHelp which has a built in tool to package the HTML files as an AIR application. You do not have access to the tool to edit how it builds the help so you have to accept it as is. What Jeff is saying to you is that to deliver something similar you will have to create your own tool. I suspect that many hours went into what Adobe supply in RoboHelp so I wish you luck with that.
The other post you have created is, as Rick has pointed out, in the same forum as this. If you are going to create your own AIR application, you need to ask at http://forums.adobe.com/community/air
Your questions need to be about creating a new AIR app, not tinkering with the tool in RoboHelp. We would help you here if we could but no one has asked these questions since AIR Help was introduced. I do understand why you want to protect your work but I don't know of any way of doing it with RoboHelp. I guess you could create the AIR Help, assuming it allow you to attach what you want to attach, and then deliver it in one of the tools to which you refer. However, if any user has access to the AIR file itself, then they can distribute it if so minded.
See www.grainge.org for RoboHelp and Authoring tips
Because your ultimate purpose is to package your AIR Help as a commercial digital-rights-secured product, I'm thinking you might be served by contacting Scott Prentice, who has the most experience with this kind of specialized use.
His website is http://leximation.com/airhelp/
Scott is a very accessible chap and I think he would be happy to steer you in the right direction by emailing him from his site. I notice you also posted on HATT and Scott often chimes in on that board as well.
I presume you have also investigated the required digital signature to be able to distribute your AIR Help.
Extra FWIW: From your description, your project appears to be a standalone knowlegebase app as opposed to a Context Sensitive Help project attached to a companion AIR Application. If that ever the case, you may want to look at an example that is installed with Adobe RoboHelp 9 but is often overlooked. You'll find a Sample located along this path.
C:\Program Files (x86)\Adobe\Adobe RoboHelp 9\RoboHTML\Samples\en_US\Salesbuilder\AIR_Application_and_CSH_Help
To see it in action, you would install both:
The Salesbuilder RoboHelp Sample project itself has a topic specifically related to how CSH works in AIR Help.
Let us know how you make out.
Adobe Certified RoboHelp and Captivate Instructor
@Peter: thanks for your post.
One of the vendors sent me this message earlier:
If the files are Flex-based before the compile, then it would be possible, otherwise it doesn’t seem so, since the output of the compile is an AIR installer, not a module that could be loaded into a wrapper.
From what I have read from your post and others neither seems possible. If there really is no workaround then that is a huge disappointment as we have spent time, effort and money building the AIR application via RoboHelp and will have to start from scratch using an AIR developer (we have no in-house technical skills which is one of the reasons we chose RoboHelp as an authoring tool).
I have tried to post to the Adobe AIR forum but cannot for some reason... it is greyed out even though I can post to other forums. I will have to follow this up with the site administrator, whoever that is and however I am able to contact him.
Thanks again for your reply in any case.
@John: thanks for your post also.
Funnily enough I had a message from Scott via the HATT forum at about the same time you mentioned him on this forum. I have sent him an email in the (ever decreasing) hope that there may be *some* kind of workaround so that all the effort we have put into creating the RoboHelp-generated AIR application has not been in vain.
I am running RoboHelp 8 rather than 9 and so unfortunately don't have access to the files you mention. Do you think the CSH in AIR might offer some kind of solution?
Thanks again for taking the time to post.
Can whatever provides the protection run the AIR installer and then delete it?
Hi Peter - good question, I could ask the shortlisted vendors - but presumably that would need access to the underlying Flex/ActionScript coding in the first place... which is what the posts here on this thread say isn't possible?
The only other alternative the vendor has said is if the output can be configured to compile not as a complete installer but as a module.
I really need to look through this all again. Will do so on Sunday.
Much as this is an imperative for us, I do appreciate it's veering into the weekend:-)
Thanks for letting us know you will look at it again - have a good weekend in between now and then,
It's more about working from a phone right now.
Either way, just saying any and all help much appreciated - thanks.
Perhaps it's time to take stock of the requirement, what has been established and your options given where you are.
- You want protection against multiple installs.
- You don't want users to be able to copy and paste the content.
- Neither of those are built in to AIR Help.
- To build them in you would have to create your own AIR application as the RoboHelp code for creating the AIR installer is locked down. Confirmed by Scott Prentice on HATT.
- You do not have an house AIR developer.
Tackling Requirement 1 is going to require a developer to replicate what Adobe have done and add the extra requirement that the installer can only run once.
- Given the hours that Adobe put into this and with the resources at their disposal, I have to question the commercial viability of that.
- A customer could legitimately need to reinstall, for instance in the case of a hard drive failure.
Perhaps my earlier suggestion of finding someone who can wrap up the AIR file in something that deletes it after installation, thereby preventing a second installation, would be viable. You would need to investigate that and do it in a way the customer can get a fresh download where a further installation is legitimate.
Otherwise I think you need to be looking at a very different approach. Your problem is the same one that Adobe face. You will recall that when you installed RoboHelp you had to activate it. That authorises the use of RoboHelp on a specific machine. The licence authorises installation on a second machine and that has to be activated too. Attempt a third activation and you will get a polite refusal until you deactivate an earlier installation. What you need is a commercial organisation to supply your product in a similar way. The trouble there is your product is not an application in the same way as RoboHelp.
You could use the WebHelp output and apply password protection to your site but again you are going to require development skills. Even then, you are relying on your customers not to reveal the password and that sounds like a No No as you don't trust them not to copy and paste the information.
Copy and paste is difficult to prevent. There are tools for web sites that would likely work in webhelp but you also have to prevent screenshots being permitted. Ultimately, going to state secret espionage levels, how do you prevent someone taking a photo of the screen? It's more about making it difficult to do casually rather than making it impossible. A high brick wall around your house makes entry difficult and deters most from attempting entry, it does not make it impossible.
I am sorry this is all negative but the root problem is your approach was wrong given these requirements. Unless someone else has other ideas, I think you need some commercial consultancy for information on how to get this idea off the ground and that is way beyond what this forum offers. Perhaps you could approach Scott Prentice at http://www.leximation.com for such assistance but I think it would be on a fee paying basis. Scott is a very knowledgeable person in many areas and he is very approachable.
See www.grainge.org for RoboHelp and Authoring tips
Thanks for taking the time to revisit my post and give me your thoughts.
It's definitely an issue of our own making: our intial research didn't go much further into establishing that (a) RoboHelp generated an Adobe AIR application and (b) licensing options were available for that. We now understand that the underlying code cannot be tinkered with to allow for third party software license systems to be added in in the usual way.
I have been in direct contact with Scott over the weekend about whether, how and how much it would cost to rebuild the whole thing using standard AIR development tools rather than RoboHelp.
Before that - however - we believe there may be a very satisfactory workaround that would work in the following way:
1. RoboHelp generates the .air installer packager from which we can extract an unprotected instance of the app as a .exe file
2. Use an installer program (something akin to Inno Setup) that runs the software activation process upon first run, then simply checks the license is still valid on each run thereafter). The solution we are looking at also provides a way of managing lost licenses, change of machine etc.
There is obviously more to it than that and we haven't confirmed that it'll work but - theoretically - it looks like there might be a workable solution before going for a rebuild. I will post the final results if there is interest.
All the best,