Jiffycms.Net.Toolkit V1.0.9.9

Rating: No reviews yet
Downloads: 423
Released: Dec 27, 2009
Updated: Dec 27, 2009 by jiffycms
Dev status: Stable Help Icon

Recommended Download

Application Jiffycms.Net.Toolkit - Binaries (This is all you need)
application, 2199K, uploaded Dec 27, 2009 - 147 downloads

Other Available Downloads

Application Jiffycms.Net.Toolkit - Sourcecode
application, 4243K, uploaded Dec 27, 2009 - 72 downloads
Example Jiffycms.Net.Toolkit - Examples download (Get this too, helpful)
example, 13277K, uploaded Dec 27, 2009 - 86 downloads
Example Jiffycms.Net.Toolkit - Themes (You don't really need this)
example, 435K, uploaded Dec 27, 2009 - 60 downloads
Source Code Dictionaries
source code, 20842K, uploaded Dec 27, 2009 - 58 downloads

Release Notes

A merry christmas and a happy new year to all.

Major Release. This release adds two new controls, the ColorPicker and Media Frame, minified js (half the size now), several bug fixes, code refactored etc etc

Unfortunately the enhancements to the imagepicker, the addition of mediaframe and the new colorpicker has forced me to make some breaking changes. Why? Simply because some of these controls
like the imagepicker/mediaframe for instance have taken a life of their own and are quite complex. In order to give you all full flexibility in what you can do, I cannot just expose the few properties manually from the editor as I was doing in earlier versions.

Instead the best solution is to expose these controls as sub controls. This also* means in future versions, as more functionality is added, you should get it automatically.


Deprecated properties :
--------------------
ImageBrowserEnabled
ImageUploadEnabled
ImageUploadingMessage
ImageUploadDesignerLoadingMessage
ImageBrowserLoadingMessage
ImageDesignerLoadingMessage
EnableImageGalleryViewState (This property is gone for good. It's pointless)
ImageGalleryNode

Now you may set these directly on the new EmbeddedImagePicker property eg:

Previously :
Editor1.ImageGalleryNode.ChildNodes.Add(new ImagePickerTreeNode("img.gif", "path/to/image/img.gif"));

Now :
Editor1.EmbeddedImagePicker.ImageGalleryNode.ChildNodes.Add(new ImagePickerTreeNode("img.gif", "path/to/image/img.gif"));


UpdateProgressBackgroundColor
UpdateProgressTransparency
RetryRequestMessage
RetryRequestButtonText
AbortRequestButtonText
CancelButtonText
ButtonCssClass

Now you may set these directly on the new EmbeddedUpdatePanelProgress property

If in earlier versions you subscribed to a clientside event handler,
the signature has changed to include the sender too. Now all handlers include the sender as the first argument. This means if you subscribed to a clientside event handler such as say :
<cc1:ImagePicker .. OnClientOkButton="ImagePicker1_ImageSelected" ....></cc1:ImagePicker>

and duly added the clientside handler for this event eg :

function ImagePicker1_ImageSelected(args) {}

this has changed to this :

function ImagePicker1_ImageSelected(sender, args) {}

note that the above has the sender as the first argument. The sender in the above example returns a reference to the imagepicker object. This is now the pattern used throughout.


ProgressbarStyle(All controls expose an EmbeddedUpdatePanelProgress property. Set directly on this property)
ProgressbarMessageStyle(All controls expose an EmbeddedUpdatePanelProgress property. Set directly on this property)

EnableViewStateForStyles property is deprecated. Viewstate is already restricted and minimized by default.

CleanupMsWordMarkup property is deprecated in favor of AutoCleanupMsWordMarkup
MinimizeViewState - Deprecated

ClientSideColorMouseOver (deprecated, all clientside events regarding color picker are now exposed directly on EmbeddedColorPicker)
ClientSideColorMouseOut (deprecated, all clientside events regarding color picker are now exposed directly on EmbeddedColorPicker)

we are using verbose json for all properties now. In previous versions, while json was used, it was not json to full potential, to put it bluntly, while the previous solution had a more compact rendering, it weren't really easily readable. we now pass a much more verbose json string to properties. specifically when passing toolbars, tabs, dictionaries etc. This allows easy maintainence, promotes readability and allows us to move forward with new features.

Reviews for this release

No reviews yet for this release.