Another one to look at is: http://tinymce.moxiecode.com/
On 21/05/06, Pete Jordan <[EMAIL PROTECTED]> wrote:
> Pete Ruckelshaus wrote:
>
> > Really? Is that in the documentation somewhere, or can you provide a
> > code sample? Also, any idea if it's possible to specify the image
> > file upload path dynamically? I'm building a simple blog app and want
> > to allow users to upload to their own directories.
>
> I'm not going to promise any sort of useful details here because I know,
> from past experience, that I'm not going to find the time to package
> code up in a form in which it can be usefully shared (I owe apologies to
> people here and elsewhere for promises unfulfilled in the past).
>
> Anyhow, that said (and with the added proviso that due to tuit shortage
> we're still working on RC2 here), I really don't see where the issues
> lie with toolbar customisation: you can define as many toolbar sets as
> you like in fckconfig.js and both the supplied custom tag and CFC allow
> you to select the things per editor instance.
>
> For image upload directories, you'll have to get your hands dirty to an
> extent. I've pretty much rewritten the connectors from scratch here as
> we've integrated fckeditor into our (mod_perl/PerlMagick based) image
> auto resizing and processing code, so our code isn't likely to be of
> much direct use to you, but the connectors are where you'll need to delve.
>
> The standard (Application|Server).userFilesPath base isn't a lot of use.
> We've recoded that to (1) pick up userFilesPath more flexibly - we check
> Request, Session, Application, Client and Server in that order - and (2)
> allow userFilesPath to be a hash, keyed on connector type ('File',
> 'Image' &c) so different media can live in entirely different places.
>
> If that doesn't give you enough flexibility, then you're likely into
> more significant hacking - passing paths into the fckeditor js code and
> back out to the connectors in the xmlhttprequest. It's not rocket
> science, but you'll need to spend a bit of time sussing out how the
> protocols work as standard first. We've not needed to do this, but
> having crawled through the relevant code for other reasons, I don't
> think it would be difficult.
>
> --
> Regards,
>
> Pete Jordan
> Horus Web Engineering Ltd
> http://www.webhorus.net/
> phone: +44 1275 543971
> mobile: +44 7973 725120
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241113
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
