Hi,
As we talked before, here is a version of FCKeditor.module that named as 5.x-2.x-dev.01. I include "01" so we are easy to manage any updating path, if u update this version then please mark as "02", and so on.

What are in this version?

  1. Based on FCKeditor 2.4.2
  2. Support user own folder for each users, i.e: files/u1, files/u2, etc.
  3. File Manager:
    a. browse, upload, and delete (based on roles!)
    b. max file size, file quota, allowed extension
    c. Allowed/Disallowed any file extension: .png, .bmp, .tgz. .zip, .swf, etc.
  4. Image Manipulation
    a. create thumbnail, proportional thumbnail
    b. default image properties (width, border, hspace, etc).
    c. maximum image width/height
  5. Table plugin: insert/delete/marge rows, insert/delete/merge colums, etc.
  6. Enable/disable editor for: block, content type, texarea id.
  7. Button sets per role: basic, compact, and complete.
  8. Slick interface
CommentFileSizeAuthor
fckeditor-5.x-2.x-dev.01.tgz_.patch31.42 KBdrupalnesia

Comments

ontwerpwerk’s picture

Status: Needs review » Closed (won't fix)

This is what the IMCE module already aims to do, lets not duplicate that effort.

drupalnesia’s picture

My idea:
- Provide an independent editor not depend on other module such as imce.
- Avoid manual configuration for file manager

The result:

  1. FCKeditor now can provide setting for: default image width, height, hspace, etc.
  2. IMCE.module can not provide hspace for example then we need to patch IMCE. With this built-in feature then we don't need to wait the patch from other module. Also, even you enable IMCE but the Quick Uploader still exist and caused error (I am using the LATEST Fckeditor, 2.4.2 version). In my test, there are another bugs on imce.module.
  3. FCKeditor now provide more scaling options
  4. On the next version of this patch, we can easy to provide more features: such as sub folder, image rendering, etc

Is it ok?

ontwerpwerk’s picture

at the moment I'm not providing another filebrowser, image module or asset manager because there are already many options (the defaultbrowser, the mcpuk browser, the quickupload and imce)

manual configuration is nessecary for the all but imce because it is an extra security problem if you enable those modules (they should not be used if your site is security sensitive)

the default image width and height settings should be handled in the filebrowser, image module or asset manager, not in the fckeditor.module

hspace is trivial, and should be handled by css, so if imce does not fix it for you you may fix it in your theme

scaling should again be handled by the filebrowser, image module or asset manager, not in the fckeditor

sub folders and image rendering should be handled by the filebrowser, image module, asset manager.. whatever and are not the primary function of the rich text editor

so, no it's not ok, but you are free to make a custom fckeditor module for your own sites that does all that

drupalnesia’s picture

at the moment I'm not providing another filebrowser, image module or asset manager because there are already many options (the defaultbrowser, the mcpuk browser, the quickupload and imce)

defaultbrowser, the mcpuk browser, the quickupload: overkill for new bie.
imce: need more improvements, more options and more integrated to fckeditor. imce also contain tinymce code.

I just release new version here: http://drupal-id.com/fckeditor_versi_drupal_id_com (this server located in Indonesia, if u have problem access, maybe too slow, please send me email so I can send you this version by email) called as fckeditor-5.x-2.x-dev.02.tgz.
What is new?
1. Support browsing on subfolder.
2. You can create subfolder and upload to them, i.e: files/u1/my_data/, files/u1/image/, etc.
3. File Upload and Create Folder only shown when users has properly access right.

Another feature that will be implemented:
- support skin chooser
- support enable/disable spelling checker and user can choose which spelling checker

My idea is not only provide Drupal users a fckeditor as is, but a solution to them to use fckeditor feature, such as: skin, spelling, image/file manager, etc. All without manual configuration and additional module as far as possible.
And use the latest fckeditor version.

BTW, is it oke to still use this name: fckeditor.module with 2.x name? Or should I create new name like fckeditor_plus.module to avoid any confuse for Drupal users?