Hi

Could be done to run imagebrowser window right aftert click on some fckeditor button?
Currently you have to click on fckeditor filebrowser button and then again click on upload button, it is not ideal.
E.g. Imageassist module has own FCKEditor button and after click on it ImageAssist window appears.

Or maybe if there could be options check/uncheck behaviour to run imagebrowser from filebrowser or exactly after the first click.

Probably will be need to add into imagebrowser option to choose alignment "float left/right/none" but I think that this is only one thing what is usable from filebrowser window.
If it will be interesting for you - I did a survey and nobody of my users use filebrowser options (some of they use alignment), they want to open "that window for selecting/uploading image", then upload/click it, and finally click on it and see it inside their article.

Please tell me what you tihink about it.
Thanks
Igorik
http://www.somvprahe.sk

CommentFileSizeAuthor
#28 Screen shot 2009-10-20 at 21.40.56.png170.93 KBjdelaune
#28 Screen shot 2009-10-20 at 21.40.47.png47.3 KBjdelaune

Comments

jdelaune’s picture

jdelaune commented
Status: Active » Postponed

I know it can be annoying to go through the FCKeditor file browser, and one of my unreleased dev's of IB did have alignment options. However I won't be going down this route until the WYSIWYG API has been finalised as I just don't have the time to integrate it extensively.

Cheers

jdelaune’s picture

jdelaune commented
Title: run imagebrowser without fckeditor filebrowser » Other WYSIWYG Editor support & WYSIWYG API integration

If you want to use ImageBrowser in other WYSIWYG Editors then you will have to wait until v2 of ImageBrowser. v2 will use the WYSIWYG API to integration into all WYSIWYG Editors. However I'm waiting for the API to stabilise before I start work. At present I have no timeframe for v2.

Thanks,
~Jordan

igorik’s picture

igorik commented

Starnox, thanks for the info, when it will be done, it will be done and for sure it will be great and I will be pleased for that moment :)

igorik’s picture

igorik commented

just a try, maybe the case how img_assist is working with wysiwyg api will be helpfull (or similar).

igorik’s picture

igorik commented

Hi, maybe this will be interesting for you: ;-)

From February 1, 2009 - cvs message for wysiwyg api
by sun, quicksketch:

"Rewrote editor plugin API. The new plugin API allows Drupal modules to expose editor plugins for ANY editor without implementing editor-specific dcode. Major milestone for better content-editing in Drupal.
WELCOME to the next generation of content-editing in Drupal! 8)"

http://drupal.org/node/319363

perandre’s picture

perandre commented

This is great! Image Browser + WYSIWYG API will be smooth! Subscribing.

pvhee’s picture

pvhee commented

interesting to hear more about WYSIWYG API integration, subscribing.

that0n3guy’s picture

that0n3guy commented

Oh yeah.. subscribing.
I've been watching this module for a while, I think I'll start using it when it goes wysiwyg api for sure :).

dddave’s picture

dddave commented

subscribing

dnewkerk’s picture

dnewkerk commented

Subscribing to keep up on the latest news about this :)

j0rd’s picture

j0rd commented

subscribing. i need an image uploader which doesn't suck for drupal.

So far they all do. Curious to try this one, but currently can't as no WYSiWYG integration.

nerissa’s picture

nerissa commented

Subscribing - would love to see this work with WYSIWYG API too!

Suzy’s picture

Suzy commented

subscribing too..

lal2017’s picture

lal2017 commented

Drupals Image uploader capability has been pathetically poor. The need for a Wysiwyg to include image upload capabilities is pretty rudimentry, and should really be part of the core. Unfortunately Image Browser does not work from Drupal Wysiwyg API. Trying to get to this simple stage of having Wysiwyg and decent file upload capabilities integrated has been a real total pain. Would it be pushing it to ask if Image Browser can upload Multiple files?

Otherwise, I have used the demo and it looks cool. Just need to get the integration right.

Docc’s picture

Docc commented

subscribe, still looking for a good image browser for Drupal. This one is dead sexy. Just needs to support the Wysiwyg API.

Frico’s picture

Frico commented

subscribing too..

physiotek’s picture

physiotek commented

i second lal2017's comment.

jdelaune’s picture

jdelaune commented

In the ideal world this is what would happen:

- Files are treated as objects of their own in Drupal Core (Not sure if this is happening in D7 but it needs to happen soon!).
- Then we can work on a file browser module which ties into filefield and WYSIWYG editors.

As for WYSIWYG API support, I haven't looked at it for a while but when someone writes some documentation for it then I will update IB. Last time I looked it seemed I had to write integration support for every WYSIWYG editor in WYSIWYG API which didn't seem like much of an API to me.

If someone wants to lend a hand or funding to get this happening then I will do it.

danyalejandro is working on CCK support for IB which is looking very promising. Once we have both of these sorted then IB will be a great solution for all involved.

Then just bring on better file support in Drupal Core.

scroogie’s picture

scroogie commented

Yes, it's happening for D7.
The File API is already in: http://api.drupal.org/api/group/file/7
For Upload / File Field look here: http://drupal.org/project/file

Sadly, Drupal 7 is still far away, and I guess Views for D7 even further...

Anonymous’s picture

Anonymous (not verified) commented

Subscribing.

CKEditor looks good too, so really waiting for CKEditor, Wysiwyg API and ImageBrowser V2 with ImageCache.

(And if we could integrate with ImageField as well, then!!!)

redijedi’s picture

redijedi commented

subscribing

igorik’s picture

igorik commented

Yes, it will be great to have CKeditor together with Imagebrowser.
Ckeditor is final already.

Anonymous’s picture

Anonymous (not verified) commented

subscribing

david1409’s picture

david1409 commented

I'm in, would love to see Image Browser and WYSIWYG working together, please.

Subscribing.

jdelaune’s picture

jdelaune commented
Version: 6.x-1.x-dev » 6.x-2.x-dev

Once we get CKeditor support in WYSIWYG API I'll do my best to get ImageBrowser working with it.

Flying Drupalist’s picture

Flying Drupalist commented

CKeditor has been completed for WYSIWYG API.

Is now the time?

jdelaune’s picture

jdelaune commented

Yes don't worry i've seen it as well. Now is the time I start work on integration. But documentation is very light for both WYSIWYG API and CKeditor so we will see how far I get.

jdelaune’s picture

jdelaune commented
StatusFileSize
new Screen shot 2009-10-20 at 21.40.47.png47.3 KB
new Screen shot 2009-10-20 at 21.40.56.png170.93 KB

Getting there... probably won't be ready for a while as there is still a lot to do and I have very limited time at the moment.

Flying Drupalist’s picture

Flying Drupalist commented

Fantastic, thank you.

CinemaSaville’s picture

CinemaSaville commented

Great news. I too would love to see this working. Thanks, Starnox.

jdelaune’s picture

jdelaune commented

Having quite a lot of trouble with this. It's ok for converting [ibimage] tags to and from. It's ok for inserting images. But it can't convert inserted images into [ibimage] tags for storing for some strange reason. I'll fiddle for a few more days and if I can't get it working I'll chuck the question over to the wysiwyg camp.

jdelaune’s picture

jdelaune commented
Title: Other WYSIWYG Editor support & WYSIWYG API integration » WYSIWYG API support coming
Status: Postponed » Needs work

So i'm currently creating a WYSIWYG API plugin for IB. I have to say I've gained great respect for the WYSIWYG API project, it really does make my life easier for writing plugins.

Lots of testing will be needed however. At the moment I've only done testing in Safari 4 on Mac OS 10.6.

What does WYSIWYG API support mean? Well it means you can now use IB in the following editors:

  • CKeditor
  • TinyMCE
  • FCKeditor (non-webkit based browser)

I'll be testing more editors over the coming days and should have something for everyone to test soon.

scroogie’s picture

scroogie commented

Great! Looking forward to the prototype.

Anonymous’s picture

Anonymous (not verified) commented

That's an absolutely great news !

jdelaune’s picture

jdelaune commented
Title: WYSIWYG API support coming » Add WYSIWYG API support
Assigned: Unassigned » jdelaune
Status: Needs work » Fixed

WYSIWYG API support is coming in next 6.x-2.x-dev version to get released later on tonight.

Adds Image Browser support to any WYSIWYG editors that support Drupal pulgins via WYSIWYG API. Currently editors include: CKeditor, FCKeditor (minus webkit browsers) & TinyMCE.

You can choose to use the current FCKeditor plugin which has full support for all browsers including Safari and Chrome.

Feel free to open new issues with any problems you face. Be sure to read the new documentation on upgrade/install.

Docc’s picture

Docc commented

Finally, awesome!

mshepherd’s picture

mshepherd commented

I just wanted to be among the 1st to say thanks for this awesome module! I've been keeping an eye out for WYSIWYG API / IMAGECACHE support & now it's arrived, I installed straight away and it worked 1st time. No problems so far. I'll keep monitoring it and will certainly report any issues I find.

This has to be the way forward for Drupal image support. So simple & like it says in the tin, beautiful!

My sincere thanks!

pfx75’s picture

pfx75 commented
Component: Code » User interface

don't work on ubuntu with firefox...
can't modify WYSIWYG profile because in the form it is impossible to open "buttom and plugin" to select the "Image Browser".
thanks

dddave’s picture

dddave commented

@pfx75

Please open a new issue for this bug.

This issue here is a fixed feature request.

jdelaune’s picture

jdelaune commented

@pfx75 sounds more like a bug with the WYSIWYG module. I suggest asking there.

brant’s picture

brant commented

Thanks for all the good work! Somewhat of a n00b, I've been experimenting with using Image Browser with the WYSIWYG API/FCKEditor. Things seem to work pretty well, but once I choose an image with File Browser, any properties/styles I set on it using the FCKEditor image properties dialog or resize handles don't stick at save time (even though things look right in the editor window before save). Also tried using Image Resize Filter, but that doesn't work either - presumably due to the same underlying issue. Are these issues intentional/expected or am I approaching/configuring things incorrectly? Thanks for any advice!

dddave’s picture

dddave commented

@41
Please see my comment at #39

And on a sidenote: This may be a case of improperly configured input formats.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.