Project DescriptionJiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...
Online demo
http://www.jiffycms.net/demo/default.aspx
Please note that Jiffycms.Net.Toolkit is GPL licensed, which means its free to use while meeting the GPL requirements. If closed source license is more appropriate for your current project, we also offer closed source licensing. You may check out our closed source licenses here :
http://www.jiffycms.net/closedsource.aspxFor screenshots, scroll to the bottom of the page :-)
Update:
09/01/2010 jiffycms is now on twitter
http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.
Installation Requirements :The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details :
http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspxThere is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has
no dependency on and you should be fine. Make sure you meet this requirement.
Simple howto- For Visual Studio 2005 development environment users :You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.
If the above doesn't work, here's a second method :
Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.
Registering the custom httpHandler :The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :
add the following entry under the path Configuration/httpHandlers section for IIS6 :
<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />
For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :
<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />
for details, reference the following article :
http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx If you need help, post on our forum
http://www.jiffycms.net/forum/default.aspxQuick start introduction tutorialshttp://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspxhttp://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspxA quick preview of designtime features supported in VS.NEThttp://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx Jiffycms HTML Editor V1.0 Quick linksProject homepage
http://www.jiffycms.net/default.aspxTutorials
http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)
Blog
http://www.jiffycms.net/article/technical-blog.aspxPost on the support forum below for questions you may haveSupport forum
http://www.jiffycms.net/forum/default.aspx screen shots
Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments
