Editable regions

Hi Nike,

I'm glad to see someone else picking up on this requirement. Any ideas would be appreciated, and we are certainly willing to pay anyone that comes up with a suitable solution. Is anyone in touch with the creator, maybe he can give us a heads up on the effort, or we can pool some funds to get this feature created. It is definitly necessary and possible. Lets do it!

Jon

It is possible - this guy managed it: http://www.neo-cms.net/en/

Sadly he wont give back the source code he says he paid for a redistribution licence.

I did some work on this last year but had to abandon it due to pressures of work.

I'd got to a point where I was overloading the onKeyDown event handler and then using the DOM to go up through the parent elements looking for a comment tag defining the start of an editable area.

Keydown is only one of many events that need overloading through.

I was hoping to get back onto the feature after christmas.

I don't see anything special in that CMS, it's just a page with an editor embedded in the middle. You can do it with a plain FCKeditor installation and without any special coding.

Yeah that's not protected areas as such, it's more of a disconnected toolbar. The uneditable bits are not in the editor window itself.

Quite nifty, but I find in place editing CMS's to be quite limiting. If all you do is pages in a predictable structure, then it's fine. Want to store any more structured content and you're screwed.

Hi All,

I am in a position where I need to either prove or disprove that we can extend the FCK editor to have exactly this functionality, although in the opposite manner:

I.e.

1. The overall content within the FCK editor area is to be editable with the exception of any sections contained within <fixedRegion></fixedRegion> (or some other XML) tags

2. If a user selects any text within the fixedRegion, the entire region becomes selected

3. If a user tries to backspace or delete the fixedRegion, they are either prevented from doing so, or a confirm message is launched (i.e. need to intercept any events which would delete the region)

4. If the user double-clicks on the region, a dialog for editing the region is launched

Alfonso, you might be interested to note that I work for Acxiom Digital (formerly Digital Impact). I am looking at your plug-ins you wrote for DI right now as they have some of the characteristics I noted above. I would hope to get all the functionality we require without modifying the source JS if possible. If you have any guidance I would be grateful.

I'd like to share my results with the community if I can successfully accomplish the above.

Thanks for any help,
Matt

Hi Matt

If I remember correctly almost all your points were done in the plugins that I created, except for number 3. You should start by checking carefully the behavior after all those changes and see what more do you need, at first don't be afraid to get deep into the core because the things that you want aren't easy.

After you manage to get your desired behavior you can try to put everything in a plugin, but I remember that for example the calls to execCommand should be disabled if the user has selected a non-editable area, and so you'll need to do quite a lot of changes from your plugin (but that's the beauty of javascript, it's possible to override the functions of an object from outside)

Regards.

Matt,

I believe that pretty much all your requirements can be met. I added a simple document tracking capability to FCKeditor that performs very similar functions: it intercepts keystrokes and determines its behavior based on the surrounding tags (font or strike tags, in this case); it changes the selection region depending on which tags were selected; it does not modify any source code. You can find the source and a demo page at https://vmacs.vmth.ucdavis.edu/userpage ... ngDemo.zip

Ed