The Future

The plans for Version 2 look really promising. I'm really really really looking forward to the widget for choosing already uploaded pictures on imagefields, cause the lack of it currently hinders me on using imagefields anywhere. I wonder how you will do the upload though? Will IB know that it was called from imagefield and not create an image node for new uploads?

IB is really sweet. Is there any chance of compatibility with the WYSIWYG API module in the future?

Sorry I just realized someone else already asked that and you answered it here: http://drupal.org/node/351537

I'm glad to hear you are planning to support it in the future! Thanks!

What a great module! The only two things i'm missing is:

• Ability to manage the images in folders
• Ability to delete images

Thanks for your work with this.

Best regards,

Thomas Kulvik
Ny Media AS
www.nymedia.no
+47 920 28 082

Great plan Starnox, looking forward for 6.x-2-beta1 ;)

Seems very cool Starnox ! Is that an ImageField or an Image node on the screenshot ?

would be so cool to be able to browse files folders as IMCE module, instead of browse image nodes only

cool module! I am really waiting for version2 :)

Subscribe....

Imagefield will handle the uploading hopefully and will just store the images in the files table. IB will then just look for images.

It'd be good to start moving in this direction to get ready for Drupal 7. It seems that we're moving away from the "image is a node" paradigm used by Image module, since in Drupal 6 we've made all files managed in the files table (it's no longer just for upload.module) and in Drupal 7 we'll have all the flexibility of hook_file(). Plus image.module may be at the end of it's life in Drupal 7 anyway, so it'd be good to start moving away from it as a dependency. See #371374: Add ImageCache UI Core.

Cant wait for this.

What would it take to allow this module to browse and include images from a service like FLIKR. That option would just set this module above and beyond everything else.

The FLICKR allows sites to link to images via their API

Why does in IE 7 image browser open in new window? Please help me fix this trouble.

In all browsers such as Opera FireFox window opens in pop up and fixed size. In IE opens in full new window.

Starnox,

Nice! Looks good. Ideally it would be awesome if one could search from within FCK for a tag or keyword which will pull up and display a list of images from various users on Flickr.

idea
http://developer.yahoo.com/yui/examples/editor/flickr_editor.html

Wow! Thats sooo what I was looking for? How can one bring that functionality into Drupal?

Is it too hard to make this module work with BUEditor?

Hi Starnox thanks for realy great module. I just have a question, when are you planning to release current dev version as a regular release. I realy like the posibility to link the image (build in the dev version), but on other hand I would like to avoid using dev version in production system. Have you any plan for that?

That's I can really imagine. Just let me insure myself, is current dev version ok for production system? As I understand other discussions, it could be. Thanks and wish you happy "post moving house time" :-)).

Thanks Starnox!

What V2 versions are currently functional on the Dev?

Okies no worries, thanks for the update. Will look forward to the release.

Love your module -- just not a fan of the image.module and would love to see filefield integration.

Subscribe....

For the feature "Helper module / ImageField integration for browsing previously uploaded files in ImageBrowser when filling in an Image field." maybe some work can be taken from the new module FileField Sources and some features could be added into that module instead of ImageBrowser ?

@Starnox you mentionned here that you plan to support WYSIWYG API in 2.x but on the roadmap you write about FCKEditor ?

For those interested in Imagefield with WYSIWYG editors I've created this wiki page.

I'm really interested in getting the V2 UI improvements imported into Imagebrowser. The current -beta version has a less than ideal UI when it comes to choosing imagecache / image-resize options. Same goes for URL's and Alignment, which is essentially what I use imagebrowser for.

Ideally I'd like those drop downs I see in the V2 screenshots added to the current version. This would increase the usability of IB 10 fold and I would no longer have to explain it to each client, as it's pretty straight forward after that.

Also I'd like to see the "alignment" changed from to . breaks XHTML strict and is not very customizable from CSS. I'd like the option to choose which classes are added for my client sites, as sometimes "float-left" isn't appropriate for someones content.

Ideally these changes could be ported into the current stable version of IB as I assume they would be greatly welcomes and I can't really wait for a new version to come out with FCK 1.3-GOLD (unless that's happening in like 1 week).

Imagebrowser is by far my favourite IB in Drupal. Keep up the good work.

Starnox, there's a beginning of the WYSIWYG API doc here. But so far it's incomplete and WYSIWYG API itself has a lot to progress. I think the best it can do is load a dialog in a popup. There's nothing in the doc for this, we need to look at img_assist code. No modal dialog for the moment I think.

Anyway thanks for the answer, so from what I undestand IB2 should work with FCK and maybe IB3 will work with WYSIWYG API.

By the way what do you mean with FCK 1.3 GOLD ? FKCeditor 6.x-1.3 is out since 2009-Mar-19 so what is this "GOLD" release ?

Thanks for the advice and all your hard work on this module. By far my favourite solution for images in posts.

I've done some fiddling around with fckeditor.config.js specifically relating to "Style" plugin. This plugin creates a drop down in FCKEditor of styles which you can configure in another XML configuration file. Works a lot like FontFormat and can actually be used to replace that plugin (which I believe it should do and be enabled by default).

I think this would be a good way to apply the last missing piece of the Image browser puzzle which is easily aligning images in the post in a XHTML+CSS complaint yet configurable manor.

If you're interested in playing with this plugin, it's included, but not enabled with FCKEditor by default. To enable it, you need to edit your fckeditor.config.js 's FCKConfig.ToolbarSet to include "Style" plugin. Then you can configure the styles which show up in the drop down by editing the fckeditor/fckstyles.xml

- Support for browsing all images in the Drupal files db (this means images from the 'Image' module and FileField / ImageField uploads or even file attachments).

This is great! I've been wanting to build Image Browser integration for FileField Sources but the dependency on Image module (and only FCKeditor) were pretty significant barriers. However, the *ultimate* solution in my opinion would be to make Image Browser Views-based (starting with a "File" type of view). FileField Sources can only reference images that have been uploaded by FileField/ImageField for security, so some ability to restrict the list of files to those alone is needed for that purpose.

You might look at how IMCE handles file browsing, basically making it a swappable method. The path always starts at "/", then the file-browsing method can return any list of files at "/", so it doesn't even need to be tied to the filesystem at all. Using that approach another module could make the browsing Views-based, Taxonomy-based, filter out file types that aren't supported, or any other number of methods for listing files.

From this plan it sounds as if Imagebrowser is going to be the exact tool I'm searching for! Hope you get your plans realised. It will sure be great. Thanks for your work!

it looks so amazing... :)
hope it will be soon ;-)

good job, Starnox

Keep it up Starnox and thank you for all your hard work on Image Browser.

Its looking good Star... Any idea when a dev release will come out? the 15ths my birthday so maybe you should aim for that :) .

:) Sounds good, I guess my birthday present will just have to wait, ha.

Keep up the good work.

It doesn't sound good, when I saw the video, I thought it will be in next few days (max 1-2 weeks, definitely no months :) but there is no another option how be patient and wait when starnox will be have some free time and enjoy to finish it.

That day will be The Day

Thanks for your great work
Igor
http://www.somvprahe.sk

Excellent job Starnox! Finally a great Image uploading tool in Drupal which is user friendly and looks decent.

Any chance of compatibility with Wysiwyg 6.x-2.0 modules, so you can insert the images using image browser by clicking on the insert picture icon from the FCKeditor toolbar or other wysiwyg editors?

I tried it via FCKeditor via Wysiwyg 6.x-2.0 and it didn't work. Seems you have to install FCKeditor explicitly.

Thanks,
Raj

Lab,

You should prolly check out: http://drupal.org/node/351537

#51 is awesome. Could you post a dev version please?

I think that starnox is enjoying that his module is so awesome and that there are so many people who are waiting for it, and he wants to publish it so awesome, bugless abd fullfeatured as possible :) so i am nor sure if your calling for dev version will be have a success :)

Nice job, I'd like to see the possibility of using files descriptions as captions, too !

That looks so good... I'm very excited about this next version.

I have a slight concern that perhaps you can clarify. It it my understanding that in the future you are intending to not require Image Browser to require the Image module directly, but will make it more general to work with perhaps any node type that I may have created that has an CCK ImageField? This would be great.

My concern is on the constant mention of removing FCK Editor integration. I suppose this is okay, as long as certain things are kept in mind: If users now have the option of the standard image insert icon on the FCK toolbar or the Image Browser button that is fine, what I don't want to happen is for the user to have to browse using the IB button, but for example not have the same options you would on the built-in image button so after they insert the image they have to select it and press the "other" image button to fill in some more advanced options (like setting a style sheet, or making the link open in a new window or same window). My main concern would be that the Image Browser button be able to automatically handle the most common of these options like like linking the inserted image (which may be a thumbnail) to the node for that image or to a larger version of the image, and controlling if the link comes up in a new window or not. This way most users could use just the IB button and get what they want, and an advanced user could always go with the other button to add further customization to the inserted image such as setting style sheet classes or whatever.

Hope I am being clear. From what I've seen looks like things will be improving for the better.

Is there any way to get back to the first screen they user gets when they select the image. So they could change the float easily? Seems like they would have to erase the class name. Or if they wanted to change it they would have to remove the whole image and re set it. Sorry if i'm i missed something its late i should goto bed.
Edit: oh great module by the way. Boss would love this. maybe throw a donation to further it along.

This is perhaps the most promising image browser/uploader for inline images I've seen. I can't wait for WYSIWYG API support so that I won't need to have FCKEditor to run it!

simple,easy to use, and powerfull

I just looked at the 2.x demo and Wow! It's exactly what I'm looking for. I hadn't paid any attention to this module before because of the dependency on image (I use imagefield). And now it sounds like the fckeditor requirement will be going away? I use BUEditor, and would love to replace the image button with this. I am a little concerned about the image node type issue, though, as I do have such a type with content in it. Also, I'm wondering about images in an imagefield attached to the same node where you are using IB. Can it handle that? So still some questions and not ready to take the leap, yet, but I have to say I'm very impressed with the demo. Adding an image should be easy since it is often something done by end users, and this is looking really good.

Michelle

Michelle,

Here is some work that has been done to use this w/ a cck field: http://drupal.org/node/507242 . But it was worked on for v1. Also, I'm not sure if it attaches the image to the same node's cck field.

Hi Starnox

I want to let you know that there is a new documentation for wysiwyg api, maybe it will be ok for you.
http://drupal.org/node/372826#comment-1903492

have a nice day
Igor

I love this module and have used it since it first came out. Really terrific work.

One thing that occurred to me while using it is that it would be really useful if IB could optionally grab the node body of the image, as well as the image itself. Why? So that you could use the image's node body as the content source for a caption. (Wrap the whole thing in a floating div, and you could place images and captions anywhere in the body of the node you're working on. Sort of like nodereference, but with fine-grained WYSIWYG control.)

From what I've seen, there is no really simple way to do this in Drupal, and to me it's one of the big pieces of the puzzle still missing. Sure, there are plenty of ways to add images and captions, but there's no easy way to control Exactly where the image will appear in the body of the text, while allowing full editing of the associated caption.*

IB should be a natural to do this, since you're already using D's image node system. Plus, this sort of functionality *has* to be done in the WYSIWYG layer--there's no alternative. In the meantime, you'd have all the benefits of using the image system (searchability, fine control over body styling--in this case caption-- styling, etc.)

*There's an existing module that uses the alt (or title?) tag together with jquery to generate a caption. --although I think that's kind of hack-y and ultimately limiting. We need fine control over the caption -- including the ability to add links and text styling, which is just not doable with the jquery solution.

Another good news for Imagebrowser 2.x, CKeditor isfinal already. Www.ckeditor.com
will be great to see it work together with imagebrowser.

That does look really nice. I've always hated WYSIWYG but they're finally getting to the point where I'd consider using one. I'm really wavering between this and http://drupal.org/project/filefield_insert for my site. I'm hoping to get the relaunch live in October so will be interesting to see where IB is at that point when I need to decide.

Michelle

That's ok. I haven't gotten to implementing image handling in my site, yet, anyway. And I've also pretty much decided on fielfield_insert. No offense to IB; I just really don't have a need to reuse images so I think FFI is better for my intended workflow.

Michelle

This module its brilliant and works flawlessly & completely without the image module, be nice to have a file browser just like it.

ckeditor kicks ass! The resizable body pop-up editor and so much more .. only thing stopping me from using it is that your modules not in it yet.
http://drupal.org/project/ckeditor

There is an issue over there tho, someone is vying to depreciate the "individual" fckeditor/ckeditor modules in favor of the wysiwyg api. I was wondering what your take on this was? ...where image browser goes I go .. lol.

I am looking for the "Edit" button in V2.
At the moment the upload process is a bit confusing if image module is enable. Although the Image Browser does not depend on image module anymore. (I know that's because backwards compatibility.)
Image Browser V2 should not create an image node. I think it's better just upload an image like an cck upload image file. That's easier to handle the image file in the Image Browser. You can delete or just replace the old image file. It's independent from the image module, that always create a node and the different image sizes.