I am currently working on a new version of the TinyMCE module and came across the following questions:
a) Version number: at the moment the version of the module is 1.2. The version of TinyMCE in the new module will be 2.0.5.1. So, which number should the new module become? 1.3? 2.0.5.1? 2? Is there a policy?
b) A large part of the module are the languages (about 2/3) and therefore, the module will be quite large (about 1.8MB zip). Should I try to split the package in two or more parts, i.e. base package (with english) and language(s) package(s)?
Module Policy?
Re: Module Policy?
a. It's left up to the module developer. You can tie it with the tinymce version number, but then you're stuck if you need to bug fix just the module. As long as it's higher, the CMSMS module upgrade procedure will work.
b. Again, up to the module developer. I can see an advantage to splitting it up, but then again, a good majority of the CMSMS userbase uses other languages. You could just be making it harder on them.
Can't wait to see the finished product. We need some new (well, redone) WYSIWYG choices out there.
b. Again, up to the module developer. I can see an advantage to splitting it up, but then again, a good majority of the CMSMS userbase uses other languages. You could just be making it harder on them.
Can't wait to see the finished product. We need some new (well, redone) WYSIWYG choices out there.
