Pending Review
Last Updated: 19 Jan 2017 14:07 by evb
Imported User
Created on: 06 Feb 2013 20:49
Category: Editor
Type: Feature Request
3
Make imagebrowser.transport.imageUrl and imagebrowser.transport.thumbnailUrl consistant with the other transport properties.
I want to use the ImageBrowser with services that perform the requested operations.. I've got my transport.read, transport.create, transport.destroy services created just fine and everything works.

However, the imageUrl and thumbnailUrl properties leave me baffled.


So transport.thumbnailUrl hard-codes a ?path={url} to whatever url you give it ... this seems like a major hack. I want to use a REST service with the generation of the thumbnail and I need to supply additional query string parameters, but the current implementation precludes doing so.

At least imageUrl lets me pass in a function or a parameterized string, but imageUrl ALWAYS tacks on the current relative path. The images that I'm using get stored in a DB by the service, so doing so makes no sense.

Both these properties should have the same abilities as the create,read, and destroy -- let me control what is passed in explicitly.
1 comment
evb
Posted on: 19 Jan 2017 14:07
And making the imageUrl and thumbnailUrl like the other transport properties will allow to set an antiforgery token in the headers when you need that.