Changes between Version 6 and Version 7 of Documentation/Customise


Ignore:
Timestamp:
01/12/07 14:21:59 (11 years ago)
Author:
ray
Comment:

changed reference to htmlarea.js

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/Customise

    v6 v7  
    44There is almost always more than just one way of doing things, and where possible alternatives will be described too. 
    55 
    6 The recommended way of customising Xinha is to either create a new file which contains your config changes or to make them on the page containing the <textarea> itself, rather than opening up htmlarea.js and making changes directly there. This is because when bugs are corrected and new features implemented, the release will include new versions of files such as htmlarea.js and your changes will be lost when you upgrade. 
     6The recommended way of customising Xinha is to either create a new file which contains your config changes or to make them on the page containing the <textarea> itself, rather than opening up !XinhaCore.js and making changes directly there. This is because when bugs are corrected and new features implemented, the release will include new versions of files such as !XinhaCore.js and your changes will be lost when you upgrade. 
    77 
    88For the purpose of this documentation we will say the config changes are either in a file called "my_config.js" or included in the page directly (preferably in the <head></head> section) as shown in the NewbieGuide - either way is fine. We will also assume that you have the basic code in place as shown in the NewbieGuide - that is, the code commented with the STEPS 1 - 5 as it will sometimes matter where your new config options are placed.