PHP effort :)

This would break many existing projects.

However, notice what the Create() function is doing:

It's calling $this->CreateHtml().

So, if you just need the html code, why not just:

$myFck = $fck->CreateHtml();

Then you can stick $myFck wherever you want on the page.

Since the CreateHtml function already does what you require, it would be redundant to have Create do the same thing.

HTH

/serializer

serializer wrote:This would break many existing projects.

I don't think that anyone should expect the V3 NOT to break existing projects.

However... maybe V3 could have a simple example of how to implement a FCKeditor global namespace object that could "behind-the-scene" change settings in the V3 global namespace? Just a thought to have existing sites quickly use V3 features... if possible.

JohnF wrote:
I don't think that anyone should expect the V3 NOT to break existing projects.

True, but I think a default unmodified installation of the editor should be upgradeable to v3 with little or no changes. The change suggested here would have broken most PHP projects, for no perceivable gain (since the CreateHtml function already exists and acheives the desired purpose). Breaking changes should at least be carefully considered! Of course, if the name changes, that would break everything, and perhaps your suggestion could be used to implement a compatibility mode for sites currently on v2+...

serializer wrote: for no perceivable gain (since the CreateHtml function already exists and acheives the desired purpose).

Exactly.
Creating another alias for an existing function and at the same time breaking most of the existing integration systems doesn't seem a wise move unless there is a strong reason to do the change.

@azertyuio, just use CreateHtml, it is there for it.

@others, by default, things may be broken. But, one of my ideas is providing a "backward compatibility pack", which would be a set of files that (try) to make the 2.x integration syntax work with V3.