Asp.net c# Web Part

I've never used web parts. How do they differ from web controls?

The current ASP.NET implementation is as a server control. If your implementation provides some new and useful functionality then maybe it could be included in the FCKeditor.NET package. I'd certainly be interested in seeing how you've done it, perhaps it could help with my ASP.NET AJAX woes!

How did you handle the resource files?

I have converted all the fckeditor files as embedded resources in my server control assembly but it does not find them, did you encounter this issue?

@pissed pat, It would be nice to take a look at your code. I would ask you to please open a ticket at our dev site, attaching your code to it.

@serializer, take a look at: http://msdn.microsoft.com/en-us/library/hhy9ewf1.aspx

mAuricio wrote:How did you handle the resource files?

I have converted all the fckeditor files as embedded resources in my server control assembly but it does not find them, did you encounter this issue?

The problem will be that various parts of fckeditor actually reference other javascript *and* other resource files. So each reference you have to replace with some ASP databinding tag (I can't remember exactly but there's a special format to use within embedded resources to create references to other resources.)

Because FCKeditor is such a huge project, it would be extremely difficuly to try and convert all potential references into WebResource.axd requests. That's why I never attempted it! (Although the idea did tempt me - an FCKeditor control containing the entire editor embedded in the .dll - I actually created just that for the editor I was using before FCK: http://www.randomdev.co.uk/View.aspx?item=3 and I'll dig out the source code if anyone's interested...)

There are various other issues with getting embedded resources to work properly, they're very sensitive to all kinds of things like the amount of daylight you give 'em, what type of music you play while you're handling them, and so on...

That's why the current FCKeditor.Net requires you to actually have an installation of fckeditor as well. It's just far far easier...

serializer wrote:Because FCKeditor is such a huge project, it would be extremely difficuly to try and convert all potential references into WebResource.axd requests. That's why I never attempted it!

Is it possible to have a JavaScript function that calculates the web resource name?

We could think about changes in the CKEditor API. All resources references could be replaced by a static function call (let's call it getUrl). We could have calls like getUrl( 'core/config.js' ) or getUrl( 'skins/default/editor.css' ) which are paths relative to the root of the editor code. I think it would be useful not only to make it possible to have WebResources with ASP.Net, but also in other cases.

I think I'll implement this feature in the JavaScript side in any case. But, will it help us in the WebResource stuff?

The WebResource URLs are generated server-side. However a WebResource file can contain references to other WebResources, using ASP tags. These get substituted when the resource is delivered to the client. You'd use a tag like this:

<%=WebResource("CKEditor.Dialogs.FileUpload.html")%>

And it gets replaced with the URL to that resource.

So it would be possible to output, say, a .js file with a hashtable just containing WebResource urls to every other required resource. It could get quite complex with all the other .html files used for dialogs - but definitely possible; so the entire editor could be packaged into a single .dll.

Thanks for the info. I'm considering this possibility. I'm implementing the getUrl stuff in any case, so the client will be ready for it.