Coolite Forums / Coolite Toolkit / Release Notes

[quote]NOTE The full project source history is also available to Support Subscription holders with access to SVN via the /tags/ directory.[/quote]

Version 0.8.0 - BREAKING CHANGES

geoffrey.mcgill — Tue, 21 Apr 2009 20:13:51 GMT

Renamed .Load() Method on PanelBase.cs to .LoadContent(). The original .Load() Method had improperly overrode the native ASP.NET WebControl .Load Event/Method.

The .loadContent() function was also added to the client-side API.

All functionality remains unchanged other than the renaming of the Method.

Related: http://www.coolite.com/forums/Topic11334-16-1.aspx
Renamed client-side API function .clearLoadedContent() to .clearContent().

Example (Old)

[code]Panel1.clearLoadedContent();[/code]

Example (New)

[code]Panel1.clearContent();[/code]
Removed the .Disable() and .Enable() Methods from Component.cs, which will affect most controls. The functions were redundant and developers should just continue to set the .Disabled property.

Example (Old)

[code]Panel1.Disable();[/code]

Example (New)

[code]Panel1.Disabled = true;[/code]
The ScriptManager.getCurrent() Method has been renamed to ScriptMangaer.getInstance().

Example (Old)

[code]ScriptManager.GetCurrent(page);[/code]

Example (New)

[code]ScriptManager.GetInstance(page);[/code]

Version 0.7.0 - BREAKING CHANGES

geoffrey.mcgill — Tue, 14 Oct 2008 08:36:02 GMT

Renamed <Content> to <Body>, see http://coolite.com/forums/Topic3059-7-1.aspx
The .AutoLoad property has been enhanced to now require a LoadConfig object, see http://www.coolite.com/forums/Topic5610-7-1.aspx

Example (Old)

[code]<ext:Panel
ID="Panel1"
runat="server"
Title="Parent"
Height="200"
AutoLoad="Child.aspx"
/>[/code]

Example (New)

[code]<ext:Panel
ID="Panel1"
runat="server"
Title="Parent"
Height="200">
<AutoLoad Url="Child.aspx" />
</ext:Panel>[/code]

The change also affects the .AutoLoadIFrame property.

Example(Old)

[code]<ext:Panel
ID="Panel1"
runat="server"
Title="Parent"
Height="200"
AutoLoadIFrame="http://www.google.com/"
/>[/code]

Example (New)

[code]<ext:Panel
ID="Panel1"
runat="server"
Title="Parent"
Height="200">
<AutoLoad Url="http://www.google.com/" Mode="IFrame" />
</ext:Panel>[/code]
The <ext:ComboBox> OnItemChange event/property has been renamed to OnValueChanged.

Other than the renaming, the OnValueChanged property remains pretty much untouched. As before, the event will fire when the ComboBox losses focus (onBlur) if the value has changed. This functions very similar to the "OnTextChanged" event of the <asp:TextBox>.

Example (Old)

[code]<script runat="server">
protected void ComboBox1_Changed(object sender, EventArgs e)
{
// something here...
}
</script>

<ext:ComboBox
ID="ComboBox1"
runat="server"
Width="200"
AutoPostBack="true"
OnItemChanged="ComboBox1_Changed"
/>[/code]

Example (New)

[code]<script runat="server">
protected void ComboBox1_Changed(object sender, EventArgs e)
{
// something here...
}
</script>

<ext:ComboBox
ID="ComboBox1"
runat="server"
Width="200"
AutoPostBack="true"
OnValueChanged="ComboBox1_Changed"
/>[/code]
The <UserParams> property of an AjaxEvent was renamed to <ExtraParams>.
The AjaxRespone.MakeAnswer() Method was renamed to AjaxResponse.Write(). See items #3 and #4 below as well. With all revisions combined, AjaxResponse.Write() is now Response.Write().
The AjaxEvent EnableViewState (boolean) property was changed to ViewStateMode (enum). Possible values include:
a. Default
b. Exclude
c. Include

If the AjaxEvent Type="Submit", the ViewState is updated on the server-side, although by default this new ViewState is not returned back to the client in the Response. If you require ViewState to be persisted between AjaxEvents, please set ViewStateMode="Include".

Example

[code]<ext:Button ID="Button1" runat="server" Text="Click Me">
<AjaxEvents>
<Click OnEvent="Button1_Click" ViewStateMode="Include" />
</AjaxEvents>
</ext:Button>[/code]

The ViewStateMode can also be set at the Page level by setting AjaxViewStateMode="Include" on the ScriptManager.

Example

[code]<ext:ScriptManager ID="ScriptManager1" runat="server" AjaxViewStateMode="Include" />[/code]

The AjaxViewStateMode property can be set at the Session level.

Example

[code]Session["Coolite.AjaxViewStateMode"][/code]

The AjaxViewStateMode can be set at the Application level.

Example

[code]Application["Coolite.AjaxViewStateMode"][/code]

The AjaxViewStateMode can also be set in Application wide from within the web.config.

Example

[code]<?xml version="1.0"?>
<configuration>
<configSections>
<section name="coolite" type="Coolite.Web.UI.GlobalConfig" requirePermission="false" />
</configSections>
<coolite ajaxViewStateMode="Include" />
</configuration>[/code]
The previous "AjaxResponse" class has been renamed to "Response". Functionality unchanged.
The previous "ResponseObject" class has been renamed to "AjaxResponse".
The <ext:Store> BeforeAjaxPostBackEventArgs was renmaed to BeforeAjaxEventArgs.
The <ext:Store> AfterAjaxPostBackEventArgs renamed to AfterAjaxEventArgs.

2008-10-02 [RELEASE 0.6.0]

geoffrey.mcgill — Tue, 14 Oct 2008 07:54:01 GMT

Version 0.6.0 released.

Version 0.6.0 - BREAKING CHANGES

geoffrey.mcgill — Mon, 01 Sep 2008 15:32:09 GMT

The Enum type of window.TriggerEvent property has changed from TriggerEvent to HtmlEvent.

Example (Old)
[code]Window1.TriggerEvent = TrigerEvent.Click;[/code]
Example (New)

[code]Window1.TriggerEvent = HtmlEvent.Click;[/code]
The markup syntax has not changed.

Example

[code]<ext:Window runat="server" TriggerEvent="Click" />[/code]
Several new html events added including:

i. Abort
ii. Submit
iii. Unload
The default value for the window.CloseAction property has changed from CloseAction.Close to CloseAction.Hide. Now by default Windows will not be destroyed when closed.

In general, developers should not have to change their existing project source code. If the property is explicitly being set to CloseAction.Hide, then that property can be removed, but is optional.
The TokenID format has changed from "{ControlID}" to "#{ControlID}".

Example (Old)

[code]<Listeners>
<Click Handler="{Panel1}.expand();" />
</Listeners>[/code]
Example (New)

[code]<Listeners>
<Click Handler="#{Panel1}.expand();" />
</Listeners>[/code]
The TokenID will be parsed and replaced with the .ClientID of the control it references. All Coolite Toolkit controls are instantiated client-side using their .ClientID. The .ClientID may be different than the controls .ID property if the control is rendered within an INamingContainer control such as a MasterPage.
The <ext:Hidden> and <ext:ScriptManager> "Hide" property have been renamed to "HideInDesign". The "HideInDesign" property will hide the control when Visual Studio is in Design-Mode. The property has no affect on any runtime rendering of the control.

The "Hide" was renamed to avoid confusion with the "Hidden" property and the .Hide() Method, both of which "hide" the control when rendered in the browser.

If the control is "hidden" at runtime, it's still available in the DOM just as through it was not hidden. Any JavaScript run against a hidden control will continue to work as expected and no JavaScript error will be thrown. The control is still there... it's just "hidden", kind of like "The Invisble Man".
The .ActiveTab property has changed.

In previous versions the .ActiveTab property was an 'int' type, but has now been changed to a type of 'Tab'.

The following sample demonstrates how to set the ActiveTabIndex in markup.

Example (old)

[code]<ext:TabPanel
ID="TabPanel1"
runat="server"
ActiveTab="1"
Title="Title">[/code]
Example (new)

[code]<ext:TabPanel
ID="TabPanel1"
runat="server"
ActiveTabIndex="1"
Title="Title">[/code]
The new .ActiveTabIndex property has been added to replace the previous .ActiveTab functionality.

The .ActiveTab property is now used in code-behind to programatically get/set an instance of the active tab.
The <ext:Window> .TriggerElement property has been removed.

Please "show" the Window by using the <Listeners> or <AjaxEvents> on the launching element/control.

Example (Listener)

[code]<ext:Button ID="Button1" runat="server" Text="Show Window">
<Listeners>
<Click Handler="Window1.show()" />
</Listeners>
</ext:Button>[/code]
Example (AjaxEvent)

[code]<script runat="server">
protected void Button_Click(object sender, AjaxEventArgs e)
{
this.Window1.Show();
}
</script>

<ext:Button ID="Button1" runat="server" Text="Show Window">
<AjaxEvents>
<Click OnEvent="Button1_Click" />
</AjaxEvents>
</ext:Button>[/code]
The <ext:Window> .TriggerEvent property has been removed.

See above #6. Now any Listener or AjaxEvent from any element/component can "trigger" an event to fire.
The default value of the <ext:Button> .AutoPostBack property has been changed from "true" to "false".

In Visual Studio DesignMode, double clicking on the <ext:Button> will automatically wire up the "OnClick" event handler, but as with other postback enabled controls, such as <asp:TextBox>, the developer will now have to explicitly set the .AutoPostBack property to "true".

Please see the following forum post for more information, see http://coolite.com/forums/FindPost2044.aspx

2008-07-07 [Revision #101, Version 0.6.0]

geoffrey.mcgill — Mon, 07 Jul 2008 06:18:04 GMT

Fixed bug in DateField where the input field would not clear properly if the SelectedDate was set to DateTime.MinValue or if the .Clear() Method was called.

Fix involved using the .SetRawValue() Method only if the SelectedDate was Null/Empty (.IsNull).
Added support for Panel.Tools property.

The following demonstrates how to add a user defined "Toggle" Tool to Collapse/Expand the Panel. This would reproduce the same functionality as setting the .Collapsible property to "true".

Example

[code]<Tools>
<ext:Tool Type="Toggle" Handler="panel.toggleCollapse();" />
</Tools>[/code]

The following example demonstrates adding a "Help" Tool. When the Help Tool is clicked, the Handler property is executed and the content of a <ext:Window> control is updated then the Window is shown.

Example

[code]<Tools>
<ext:Tool Type="Help" Qtip="Click for Help"
Handler="{Window1}.body.update(String.format(msgTemplate, panel.title));
{Window1}.show();"
/>
</Tools>[/code]

In the above code sample, within the Handler property, a control token ({Window1}) is used. The server-side ID of the Window is wrapped with curly-braces {}. The ID is then converted to the .ClientID at runtime.

The .ClientID may be different than the .ID at runtime if the control is nested within a INamingContainer control such as a MasterPage.

2008-07-07 [RELEASE 0.5.4]

geoffrey.mcgill — Mon, 07 Jul 2008 06:13:44 GMT

[Revision #100]

Created new version 0.5.4 release.
Applied design-time bug fix from Revision #80 to build 0.5.4.

Fixed bug in WebControl.cs where .ScriptManager property was causing a Design-time exception which crashed VS and VWD.
Fixed bug in TextField where if .Text property was set to an empty string (""), the input field would not clear. The same or similar fix was also applied to TextArea, NumberField and DateField.

2008-07-04 [Revision #96, Version 0.6.0]

geoffrey.mcgill — Fri, 04 Jul 2008 23:08:17 GMT

Updated ext-all.css to use version 2.1. Previously was mistakenly using v2.0.2.
Fixed bug in Store where if .Data property was set and AutoLoad="true" a JavaScript error was thrown. Now if Data is not null, AutoLoad is set to "false".
Added new GridPanel sample to demonstrate connecting directly to a .xml file. See \Coolite.Sandbox\GridPanel\XmlReader\Direct.aspx
Renamed JavaScriptExtDateTimeJsonConverter class to CtorDateTimeJsonConverter.
Renamed RegexCheckJsonConverter to RegexJsonConverter.
Renamed JavaScriptDateTimeJsonConverter to CtorDateTimeJsonConverter.

Example

[code]// returns new Date(2008, 7, 4, 18, 55, 18)[/code]
Added ISODateTimeJsonConverter which formats Json DateTime objects without the millisecond format specifier.

Example

[code]// returns "2008-04-12T12:53:25Z"[/code]
Added JSONDateTimeJsonConverter which formats DateTime objects using the "yyyy-MM-dd'T'HH:mm:ss" pattern. The "server-time" is returned. The DateTime object is not converted to UTC. Please use ISODateTimeJsonConverter if UTC is required.

No timezone information is added to the converted string.

This is now the default DateTimeConverter if using the Coolite.Ext.Web.JSON.Serialize Method.

Example

[code]// returns "2008-04-12T12:53:25"[/code]
Changed RecordField.DateFormat to use .NET format specifier syntax.

See http://code.google.com/p/datejs/wiki/FormatSpecifiers for good comparison of difference between .NET/Java and PHP/Unix date and time format specifier syntax.
Set RecordField.DateFormat to return "yyyy-MM-dd'T'HH:mm:ss" pattern if .Type is "Date" and no DateFormat is set. The Data must be serialized using the Coolite.Ext.Web.JSON.Serialize Method. Otherwise the DateFormat may need to be set.

Example (Old)

[code]<ext:RecordField Name="Availability" Type="Date" DateFormat="Y-m-dTh:i:s" />[/code]

Example (New)

[code]<ext:RecordField Name="Availability" Type="Date" />[/code]
Added .Plugins property to Component. The Plugins property accepts an object or array of Plugin controls that will provide custom functionality for this component. The only requirement for a valid plugin is that it contain an init method that accepts a reference of type Ext.Component. When a component is created, if any plugins are available, the component will call the init method on each plugin, passing a reference to itself. Each plugin can then call methods or respond to events on the component as needed to provide its functionality.

The following example demonstrates adding a Plugin to a Component using markup syntax.

Example

[code]<Plugins>
<ux:TabCloseMenu ID="TabCloseMenu1" runat="server" />
</Plugins>[/code]

The following example demonstrates adding a GenericPlugin to a Component using markup syntax. The GenericPlugin provides a convenient wrapper to ease adding a Plugin to a Component.

Example

[code]<Plugins>
<ext:GenericPlugin
runat="server"
InstanceOf="Ext.ux.TabCloseMenu"
Path="~/Plugins/TabCloseMenu.js"
/>
</Plugins>[/code]

The InstanceOf property is used by the Plugin to create a "new" JavaScript instance of the Plugin.

Example

[code]// If InstanceOf property is set with the following.
InstanceOf="Ext.ux.TabCloseMenu"

// The constructor will be set as follows
new Ext.ux.TabCloseMenu()[/code]

The Path property is used to set the src attribute of the <script> element. The <script> element is rendered in sequence with the other included <script> elements.

Relative, Absolute, Virtual, Application root and remote paths are valid values.

Example

[code]// Relative
"../Plugins/TabCloseMenu.js"

// Absolute
"Plugins/TabCloseMenu.js"

// Virtual
"/Plugins/TabCloseMenu.js"

// Application Root
"~/Plugins/TabCloseMenu.js"

// Remote
"http://www.example.com/Plugins/TabCloseMenu.js"[/code]

The following example demonstrates adding a GenericPlugin from code-behind.

Example

[code]this.TabPanel1.Plugins.Add(
new GenericPlugin(
"Ext.ux.TabCloseMenu",
"~/Plugins/TabCloseMenu.js"));[/code]

To create a custom Plugin control, your class must inherit from the Coolite.Ext.Web.Plugin class.

The following demonstrates creating the TabCloseMenu Plugin.

Example

[code]using System.ComponentModel;
using System.Web.UI;
using Coolite.Ext.Web;

namespace Coolite.Ext.UX
{
[InstanceOf("Ext.ux.TabCloseMenu")]
[ClientScript(typeof(TabCloseMenu), "Coolite.Ext.UX.TabCloseMenu.TabCloseMenu.js")]
[ToolboxData("<{0}:TabCloseMenu runat=\"server\" />")]
[Description("Very simple plugin for adding a close context menu to tabs")]
public class TabCloseMenu : Plugin { }
}[/code]

The InstanceOfAttribute can be set instead of the InstanceOf property. If both are set, the InstanceOf property will be used. If neither is set, an ArgumentException is thrown.

The ClientScriptAttribute provides the Embedded Resource path to the required JavaScript file. Please ensure the file is marked as "Embedded Resource". To mark the file as an Embedded Resource, within Visual Studio, right-click on the file, select Properties, then set the "Build Action" to "Embedded Resource".
Added new PagingMemoryProxy. Now if <ext:PagingToolBar> is added to GridPanel, the GridPanel will automatically enable Paging of the client-side data.

See Coolite\Sandbox\GridPanel\MemoryProxy\PagingSortingMemoryData.aspx

2008-06-25 [Revision #80, Version 0.6.0]

geoffrey.mcgill — Fri, 27 Jun 2008 21:40:03 GMT

Fixed bug in WebControl.cs where .ScriptManager property was causing a Design-time exception which crashed VS and VWD.
Added support for ArrayReader in Store. Serializes into an Object[].
Fixed bug with GridPanel.LoadMask where LoadMask was not serializing properly in the ClientConfig script.
Added .AddBeforeClientInitScript(string script) and .AddAfterClientInitScript(string script) Methods to WebControl.cs. The two methods enable JavaScript/strings to be inserted immediately before and after the ClientInitScript for instance of this control.
Added two GridPanel samples which create either an Object[] array of Data or a Json object from a generic List<> of objects. The Data is sent inline to the GridPanel and all sorting is performed client-side.

Samples located in Coolite.Sandbox\GridPanel\
Removed Coolite.Doodle Website project.
Added Coolite.Examples Web Application project
Change Coolite.Sandbox Website project to a Web Application project.

2008-06-25 [Revision #73, Version 0.6.0]

geoffrey.mcgill — Wed, 25 Jun 2008 14:37:55 GMT

Changed GridPanel Renderer property to use new Renderer type.

The following example demonstrates setting a custom Handler to check if a boolean value is 'true', then return 'Yes' or 'No'. The Handler is automatically wrapped in a function(){} template and the Column arguments are passed into the function.

Example

[code]<ext:Column Header="Indoor?" DataIndex="Indoor" Sortable="true">
<Renderer Handler="return (value) ? 'Yes':'No';" />
</ext:Column>[/code]

// arguments
// "value", "metadata", "record", "rowIndex", "colIndex", "store"

The following example demonstrates setting a custom function. The function is rendered as a raw value and no formatting is applied.

Example

[code]<ext:Column Header="Availability" DataIndex="Availability">
<Renderer Fn="Ext.util.Format.dateRenderer('Y-m-d')" />
</ext:Column>[/code]

The following example demonstrates setting one of the Renderer helper Formats. The Renderer helper Format are a list of pre-defined list of functions which wrap common formatting functionality.

Example

[code]<ext:Column Header="Price" DataIndex="Price" Sortable="true">
<Renderer Format="UsMoney" />
</ext:Column>[/code]

Other Format types include:

None,
Capitalize,
Date,
DateRenderer,
DefaultValue,
Ellipsis,
FileSize,
HtmlDecode,
LowerCase,
StripScripts,
StripTags,
Substr,
Trim,
Undef,
Uppercase,
UsMoney

The following example demonstrates setting the Ellipsis Format and passing an extra argument to trim the description at 50 characters.

Example

[code]<ext:Column Header="Description" DataIndex="description" Width="150">
<Renderer Format="Ellipsis" FormatArgs="50" />
</ext:Column>[/code]

2008-06-25 [Revision #61, Version 0.6.0]

geoffrey.mcgill — Wed, 25 Jun 2008 14:34:23 GMT

Added "display:none;" to the Window Container <div> style. This avoids a momentary 'flash' of <Content> on initial Page_Load.

The style was added using the ContainerStyleAttribute.

Example

[code][ContainerStyle("display:none;")][/code].
Moved OnBeforeClientInit and OnAfterClientInit Events to Observable.cs from Component.cs. Now requires an Observable type instead of Component type as parameter.
Integrated GridPanel and Store working into project.

2008-06-24 [Revision #60, Version 0.6.0]

geoffrey.mcgill — Tue, 24 Jun 2008 01:21:40 GMT

Added 0.5.3 tag to SVN.
Changed Build# to 0.6.0.
Updated Copyright and date stamps.
Added WindowUnload Listener to <ext:ScriptManager>.

The following sample demonstrates setting the WindowUnload Listener which checks to see if either "Tab1" or "Tab3" is active before allowing the browser window to close or refresh. If "Tab2" is the activeTab, then the user will not be prompt to confirm.

Example

[code]<ext:ScriptManager ID="ScriptManager1" runat="server">
<Listeners>
<WindowUnload Handler="
var id = {TabPanel1}.getActiveTab().id;
return (id == 'Tab1' || id == 'Tab3');
" />
</Listeners>
</ext:ScriptManager>

<ext:TabPanel ID="TabPanel1" runat="server" ActiveTab="0" Height="300">
<Tabs>
<ext:Tab ID="Tab1" runat="server" Title="Tab 1" Html="Tab 1" />
<ext:Tab ID="Tab2" runat="server" Title="Tab 2" Html="Tab 2" />
<ext:Tab ID="Tab3" runat="server" Title="Tab 3" Html="Tab 3" />
</Tabs>
</ext:TabPanel>[/code]

Return 'true' to prompt the message, or 'false' to cancel the unload.

The WindowUnload Listener is not native to Ext. We've added only as a convenience wrapper.
Added WindowUnloadMsg Property to ScriptManager. The WindowUnloadMsg property is used as the extra text message to prompt to the user only when the <WindowUnload> Listener is set.

The following sample will prompt the user before they refresh or close the browser window.

Example

[code]<ext:ScriptManager
ID="ScriptManager1"
runat="server"
WindowUnloadMsg="Your data will not be saved!">
<Listeners>
<WindowUnload Handler="return true;" />
</Listeners>
</ext:ScriptManager>[/code]

2008-06-23 [RELEASE 0.5.3]

geoffrey.mcgill — Mon, 23 Jun 2008 06:41:09 GMT

Version 0.5.3 released.

2008-06-23 [Revision #58, Version 0.5.3]

geoffrey.mcgill — Mon, 23 Jun 2008 06:38:44 GMT

Changed the call to the SweepControls Method from Page_Load to Page_LoadComplete. This changed fixed a bug a where if controls were added during Page_Load, they the SweepControls Method did not get called because the life-cycle had already passed.
Added support for adding Layout controls within a <asp:Content> area of a MasterPage.

For example, in a MasterPage you define a <ext:ViewPort> within a <Center> region. In the Center region you add a <ext:Panel> and within that Panel you add your <asp:ContentPlaceHolder>. Now in the child page which uses this MasterPage, you can now add a <ext:FitLayout>.

Example

Define the following in your ViewPort MasterPage.

[code]<ext:BorderLayout runat="server">
<Center>
<ext:Panel runat="server" Title="Center">
<Content>
<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server" />
</Content>
</ext:Panel>
</Center>
</ext:BorderLayout>[/code]

Then in the child you can add the following.

[code]<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<ext:FitLayout ID="FitLayout1" runat="server">
<ext:Panel ID="Panel1" runat="server" Title="Inner Panel" />
</ext:FitLayout>
</asp:Content>[/code]

2008-06-22 [Revision #57, Version 0.5.2]

geoffrey.mcgill — Mon, 23 Jun 2008 06:36:11 GMT

Added support to <ext:Button> so client-side validation is fired if using asp: Validator controls. Previously only server-side validation would fire.
Update copyright date stamp and revision# to version 0.5.3.
Added .Regions property to BorderLayout. Returns a List of regions.

2008-06-18 [Revision #44, Version 0.5.1]

geoffrey.mcgill — Mon, 23 Jun 2008 06:31:53 GMT

Updated copyright date stamp.
Moved intellisense.js to new Coolite/coolite/intellisense.js.
Fixed bug in WebControl.Render where the characters \t,
and \r were being removed, but the regex to remove those chars was too greedy. Now no chars are removed. Makes html source less formatted and not as pretty. Will have to revisit with a better solution later.
Fixed bug in Listener.Hander where if the Hander string started with a token and included more that just a token (eg. {Panel}.getSize()), the regex to parse the tokens into their correct .ClientID was failing.
Fixed bug where ScriptManager.RenderScripts and ScriptManager.RenderStyles were not correctly creating the local path if set to "File".

Version 0.5.2 - BREAKING CHANGES

geoffrey.mcgill — Sun, 15 Jun 2008 02:11:27 GMT

Renamed the "HorizontalAnchor" and "VerticalAnchor" properties of AnchorLayout to just "Horizontal" and "Vertical".

Example (Old)

[code]<ext:Anchor HorizontalAnchor="100%" VerticalAnchor="100%">[/code]

Example (New)

[code]<ext:Anchor Horizontal="100%" Vertical="100%">[/code]

Version 0.5 - BREAKING CHANGES

geoffrey.mcgill — Sun, 11 May 2008 23:11:46 GMT

Renamed Assembly from Coolite.Web.UI to Coolite.Ext.Web. The new main dll is now Coolite.Ext.Web.dll.

The Page @Register statement must be updated.

Example (Old)

[code]<%@ Register Assembly="Coolite.Web.UI" Namespace="Coolite.Web.UI" TagPrefix="cool" %>[/code]

Example (New)

[code]<%@ Register Assembly="Coolite.Ext.Web" Namespace="Coolite.Ext.Web" TagPrefix="ext" %>[/code]

If you added the tagPrefix to the Web.config...

Example (Old)

[code]<pages>
<controls>
<add tagPrefix="cool" namespace="Coolite.Web.UI" assembly="Coolite.Web.UI"/>
</controls>
</pages>[/code]

Example (New)

[code]<pages>
<controls>
<add tagPrefix="ext" namespace="Coolite.Ext.Web" assembly="Coolite.Ext.Web"/>
</controls>
</pages>[/code]

Rename Toolbox extension from <cool: to <ext:

Example (Old)

[code]<cool:Window runat="server" id="Window1" />[/code]

Example (New)

[code]<ext:Window runat="server" id="Window1" />[/code]

Renamed all "ClientEvents" properties to "Listeners".

Example (Old)

[code]<cool:Window ID="Window1" runat="server">
<ClientEvents>
<Show Handler="Ext.emptyFn" />
</ClientEvents>
</ext:Window>[/code]

Example (New)

[code]<ext:Window ID="Window1" runat="server">
<Listeners>
<Show Handler="Ext.emptyFn" />
</Listeners>
</ext:Window>[/code]

Added convenience functionality to Listener "Hander" property so wrapping custom event handler logic with JavaScript 'function' is no longer required.

Example

[code]// Old
<Resize Handler="function(el){console.log(el.getSize());}" />

// New
<Resize Handler="console.log(el.getSize());" />[/code]

By default, the .Handler property will wrap it's value with the proper 'function' syntax and pass the correct arguments for each event. Each argument is listed in the ExtJS documentation (Resize Sample) and will be available from Intellisense.

Changed Window "AutoShow" property to "ShowOnLoad". The ShowOnLoad property is 'true' by default.

To not show the Window automatically on Page load, please set the ShowOnLoad property to 'false'

Example (Old)

[code]<cool:Window runat="server" id="Window1" AutoShow="true" />[/code]

Example (New)

[code]<ext:Window runat="server" id="Window1" /> // Show Window on Page load
<ext:Window runat="server" id="Window1" Showonload="False" /> // Do not show Window on Page load[/code]

Changed Window "Center" property to "CenterOnLoad". The CenterOnLoad property is 'true' by default and will center the Window in the viewport on initial Page load.

Example (Old)

[code]<cool:Window runat="server" id="Window1" Center="true" />[/code]

Example (New)

[code]<ext:Window runat="server" id="Window1" /> // Center Window on Page load
<ext:Window runat="server" id="Window1" Centeronload="False" /> // Do not center Window on Page load[/code]

Renamed TextBox control to TextField.

Example (Old)

[code]<cool:TextBox runat="server" id="TextBox1" />[/code]

Example (New)

[code]<ext:TextField runat="server" id="TextField1" />[/code]

Renamed DatePicker control to DateField.

Example (Old)

[code]<cool: DatePicker runat="server" id="DatePicker1" />[/code]

Example (New)

[code]<ext: DateField runat="server" id="DateField1" />[/code]

Renamed Calendar control to DatePicker.

Example (Old)

[code]<cool:Calendar runat="server" id="Calendar1" />[/code]

Example (New)

[code]<ext: DatePicker runat="server" id="DatePicker1" />[/code]

Renamed CheckBox control to Checkbox (<-- notice lowercase 'b').

Example (Old)

[code]<cool:CheckBox runat="server" id="CheckBox1" />[/code]

Example (New)

[code]<ext:Checkbox runat="server" id="Checkbox1" />[/code]

Renamed HiddenField control to Hidden.

Example (Old)

[code]<cool:HiddenField runat="server" id="HiddenField1" />[/code]

Example (New)

[code]<ext:Hidden runat="server" id="Hidden1" />[/code]

Renamed NumberTextBox control to NumberField.

Example (Old)

[code]<cool:NumberTextBox runat="server" id="NumberTextBox1" />[/code]

Example (New)

[code]<ext:NumberField runat="server" id="NumberField1" />[/code]

Renamed RadioButton control to Radio.

Example (Old)

[code]<cool:RadioButton runat="server" id="RadioButton1" />[/code]

Example (New)

[code]<ext:Radio runat="server" id="Radio1" />[/code]

Version 0.4.0

geoffrey.mcgill — Sun, 30 Mar 2008 21:20:32 GMT

New <cool:TabPanel> control. See new TabPanel examples online at http://www.coolite.com/examples/
New <cool:Button> control.
Automatic GZip compression. By default all the resource files (.js, .css, he file "over-the-wire" by appimages) are GZip compressed. This reduces the size of trox 70%.
Automatic "Clean" resource urls. By default all the resource files are pulled from the Assembly as Embedded Resources. The auto generated urls are typically very long and very ugly. As of version 0.4, the WebResource urls which point to these Embedded Resources have been cleaned up.

Example (Standard)

[code]<script type="text/javascript"src="/Coolite.Web.UI.Testing/WebResource.axd?d=Ei4DLpf5Q4IAsNNjdlZgzE0LNteuoPg9VFzsfQvldaiiUan0pyLkVOdQCZJwzqhqT1lCoscVI2J1pYPMIFS7mhhLy_9Ct4036wu4mfvO46P8yOQNjyqOvVS-puvFUxML0&t=633425029074531250"></script>[/code]

Example (Clean)

[code]<script type="text/javascript" src="/cool/extjs/ext-all/js/cool.axd"></script>[/code]
Added extra options for setting the Global Config properties. Now the following Global Config properties can be set in the web.config, as Application variables, as Session variables or at the Page level by setting properties on the ScriptManager.
1. CleanResourceUrl
2. ScriptAdapter
3. RenderScripts
4. RenderStyles
5. ResourcePath
6. ScriptMode
7. Theme
8. GZip
The following forum post details each option. See http://www.coolite.com/forums/Topic112-4-1.aspx.
A big pile of bug fixes.