released chmsee not compatible with xulrunner-14

[GoogleCodeExporter]

Hi there,

I have reported this issue in the past. The released version of chmsee is not 
compatible with the just released version of xulrunner. Could you fix this?

I really appreciate your work. I'm not a programmer myself. I cannot code. But 
wouldn't it be possible to remove the gecko-max-version requirement from 
chmsee? Otherwise, new released xulrunner major versions will be automatically 
incompatible with chmsee.

Many thanks for your help and your excellent work,

Pablo Rodríguez

Original issue reported on code.google.com by google-c...@pragmata.tk on 25 Jul 2012 at 3:03

[GoogleCodeExporter]

The last version v1.99.12 is already compatible with xulrunner-14. I've tested 
it under Arch Linux with xulrunner-14.0.1. Could you paste the error message 
you encountered?

Xulrunner document say MaxVersion in appliaction.ini is optional:
https://developer.mozilla.org/en/XUL_Application_Packaging#The_.5BGecko.5D_secti
on
But if omit it, the default value is 1.* 

Thank you issue this again, I will take your advice to increase MaxVersion 
bigger.

Original comment by jungl...@gmail.com on 25 Jul 2012 at 4:13

• Changed state: InComplete

[GoogleCodeExporter]

Thanks for your reply.

The error message is the following:

$ chmsee 
Error: Platform version '14.0.1' is not compatible with
minVersion >= 9.0
maxVersion <= 13.*

But this is caused by the fact that Fedora is packaging an old version: 
chmsee-1.99-0.15.9.git36b4702.

BTW. Where is version 1.99.12 available. Only in git?

Thanks for your help,

Pablo

Original comment by google-c...@pragmata.tk on 26 Jul 2012 at 4:35

[GoogleCodeExporter]

Yes, the new version is only located on github.

You can get with:

$ git clone git://github.com/jungleji/chmsee.git

or download the tagged version:

https://github.com/jungleji/chmsee/tags

If you don't want build chmsee, you can simply change the maxVersion in exist 
chmsee application.ini.

Most of the time chmsee can load extracted old chm file, but I am not sure it 
will be OK opening a fresh chm file on different xulrunner runtime version.

Original comment by jungl...@gmail.com on 27 Jul 2012 at 8:08

[GoogleCodeExporter]

Clear all pre-2.0 issues

Original comment by jungl...@gmail.com on 18 Jan 2013 at 6:10

• Changed state: Done