Chrisi Skin in RH2020

[Mike.Walsh.0]

Does anyone know if the Chrisi skin can be used in RH 2020? This is a skin we have used with webhelp for many years, but it does not seem to be available in RH 2020. When I try to add an HTML5 skin, Chrisi is not one of the skins available. If I use the Skin Import function and navigate to my RH2017 project in the !SkinSubFolder!/Chrisi folder, chrisi.skn is not recognized because the import function is looking for only skz and slz files.

[Peter Grainge]

Chrisi is almost certainly the name your predecessor gave whichever skin was used. Also it was a webhelp skin and both 2019 New UI and 2020 only offer frameless and responsive skins. You will need to select one of the skins offered.

I recommend frameless as that is where development will be focussed going forward. Frameless/Responsive skins change their layout as the window size changes whereas webhelp skins do not. That means they adapt to suit tablet devices better. In both the newer types you can deselect responsiveness so that they behave like webhelp if you prefer.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Mike.Walsh.0]

Peter: I generated frameless help, but the performance was so slow I couldn't seriously consider distributing it. I was running it in a browser directly from my hard drive. I also tried it on another laptop in our organization, and the results were just as bad. Click a link and it would take many seconds for the page to appear, and the Contents took even longer.

[Jeff_Coatsworth]

That sounds like some aggressive anti-virus at work

[Peter Grainge]

Try the RoboHelp Tour Introduction (grainge.org) on my site. Is your project responding significantly slower? What you are describing does not sound normal as no one would be able to use it and that's not the case.

Is a new responsive skin different?

As Jeff suggests, it does look like something in your environment Can you put the output on a stick and run it at home to compare.

Also how does the About RoboHelp sample project respond? That's a known quantity and it works fine.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Mike.Walsh.0]

Peter: I tried the frameless help on my personal laptop, and the results were just as bad -- very slow. The TOC on the left was the main drag. The ResponsiveHTML5/webhelp I generate is not slow at all. Also, I did view the Robohelp Tour on your site, and the performace was perfectly fine. Very quick response.

[Peter Grainge]

Something is not right here. Can you share the project? If you can, then see the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.

I am assuming the help is not on a publicly available server.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Peter Grainge]

Opening the help locally on my machine, it took three seconds from double clicking the index.htm file to see the TOC. However, the TOC is a nightmare to use so something is wrong.

Try creating an additional TOC using Auto-Create. The structure will be nothing like what you want but the idea is to quickly see if that makes a difference.

If it does, then you will need to look at your TOC. First though let me know if Auto-Create makes a difference.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Mike.Walsh.0]

Peter: I created an additional TOC using Auto-Create, and it made no difference in the frameless output. Still very slow. By the way, this is a very large and old project (800 topics) that has had numerous authors over the years. So I wonder if the size is a problem for frameless. Also, I find the Topic List view to also be terribly slow in the new UI. Almost completely useless. (I'm thinking that I should open a new thread just for that.)

I also created frameless output with the EmployeeCare RH2017 sample project, and the performance is fine.

[Peter Grainge]

I still believe this is a project issue as every other project is OK when you have tried them.

800 topics is not large in itself. I found with Classic hitting around 4,000 topics started hitting some performance issues but not intolerable. I have seen others with an exceptional number of images cause performance issues.

Let me look at your project again, hopefully tomorrow.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Peter Grainge]

The problem is related to your index. If you deselect that in the preset, the TOC is lightning fast. I will see if I can find out why that should be.

I also noticed you have turned off responsiveness in the skin. Curious as to why?

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Mike.Walsh.0]

Peter: I see what you mean. I generated frameless without the index, and the TOC is suddenly very fast. Also, I turned off the Responsive option in the skin because I believe our system is used only on laptops/desktops and not on tablets and phones. Plus, I thought it would simplify the output -- that is, one less thing that could go wrong.

[Vivek Kumar · Accepted solution]

Hi Mike,

My apology for the trouble. This was a bug and has been resolved in update 4 which is still few weeks away. If you want to try out then we can enroll you in the beta program if you are interested.

Thanks,

Vivek