The latest early access builds of EditLive! now make integrating even easier by automatically detecting the download directory and providing a default configuration file. Since the very first version of EditLive! the JavaScript instantiation code would include the two lines:

editlive.setDownloadDirectory("editlivejava/");
editlive.setConfigurationFile("editlivejava/sample_eljconfig");

However that's no longer needed as EditLive! will automatically detect the right URL to download it's resources from and if you don't specify a configuration file it will use the sample_eljconfig.xml configuration file.

You can of course continue to set the download directory and configuration file but you no longer need to. Below are some best practices to make the most of these latest changes:

• Don't set a download directory. It's simpler to leave EditLive! calculate the right URL and it avoids potential errors.
• If you don't need to make any changes to the configuration, don't set a configuration file and simply use the default. This avoids the potential for specifying the URL incorrectly and getting errors.
• If you do modify the configuration file, make a copy in a separate location and instruct EditLive! to use your version with setConfigurationFile or setConfigurationText. By making your own copy instead of modifying the sample, you remove the potential for overwriting your modifications when you upgrade EditLive!
• If possible, use setConfigurationText instead of setConfigurationFile to improve the editor start up time. With setConfigurationFile, EditLive! must wait while the configuration file downloads.

This entry is filed under Integrating EditLive!. You can follow any responses to this entry through the Atom feed. You can leave a response, or trackback from your own site.