PDA

View Full Version : Coolite folder



scidec
Mar 03, 2008, 3:07 AM
Is there a way to declaratively state a virtual path to where the coolite folder is located in a site eg "~/controls/custom/coolite"?

geoffrey.mcgill
Mar 07, 2008, 12:33 AM
Hi scidec,

I apologize for the delay in getting you a working sample. At the moment pointing the ScriptManager to a Coolite/ExtJS folder location outside of the Embedded Resources is not possible, although I will update the code to include this feature within the next few days. Please expect a new build (v0.4.1) by 12-Mar-2008 which includes this functionality.

geoffrey.mcgill
Mar 20, 2008, 4:36 PM
We have released (http://www.ext.net/download/) the version 0.4.1 build.

The version 0.4.1 (or higher) build includes a new .ResourcePath property which points the controls to a location of the required resource files (.js, .css, images) if the RenderScripts and/or RenderStyles properties have been set to "File".

When you run the installer a "Coolite" folder is added to the following location on you machine.


[INSTALL DRIVE]:\Program Files\Coolite\Coolite.Web.UI - Version 0.4\Coolite


A shortcut to the Coolite folder is also added to your Windows Start menu if you use the installer.


Start > All Programs > Coolite > Coolite.Web.UI - Version 0.4 > Shortcut to Coolite Folder


The folder is also included with the manual installation package if you choose not to use the installer.

The folder contains all the required external resource files. You can manually add the folder to your Project by dragging/dropping the folder into your Project. The folder can be placed anywhere in your Project although by default the controls will look for the folder at the root of the Project.

The ResourcePath property is what instructs the controls as to where the files are located. By default the ResourcePath is set to "~/Coolite/". The Tilde (~) points to the Application Root of your Project. The ResourcePath property can also be set with a Virtual Root path ("/Coolite") or Relative Path ("../Coolite"). In general I would suggest sticking with the Application Root as it will work both locally (localhost) and after deployment to a remote server without having to change.

The ResourcePath property can be set at four different levels/locations within your Application. The following forum post (fourth post in thread) details each of these four options. See http://forums.ext.net/showthread.php?threadid=112-4-1.aspx

If you would like to NOT use the Embedded Resource files, the following steps outline how.

<LI>Add (drag/drop) the "Coolite" folder into the root of you Web Project/Site.</LI>
<LI>Set the RenderScripts property to "File".</LI>
<LI>Set the RenderStyles property to "File".</LI>The following code demonstrates how to set the ResourcePath property if you would like to move the Coolite folder to a different location, for example, inside a root "resources" folder.

Example


<cool:ScriptManager ID="ScriptManager1" runat="server" ResourcePath="~/resources/coolite/" />


NOTE As mentioned above, the ResourcePath property can be set in four different locations. See http://forums.ext.net/showthread.php?threadid=112-4-1.aspx

NOTE By default the Coolite Assembly will automatically perform GZip file compression on the resource files (.js, .css, images), but only if the RenderScripts and/or RenderStyles properties are marked as "Embedded". If you set to "File", automatic GZip compression will not be handled by the Coolite controls. GZip compression typically reduces the "over the wire" size of the resource files by 70%.

Hope this helps.