English
Deutsch
Español
Français
Forums/General knowledge/Suggestion Box
PlannedDoneNot planned
add cross-product sideloading
Shane Fellows
suggested this on June 22, 2011 11:27 am
For all of us who use multiple products from intothedarkroom!
If we could identify the location of a flaunt set in vend, then vend could use that same set to display images. This would save uploading time and also server space.
Comments
because of the way our products are built, they cannot share images across one another. that said, sideloading may be an option. would that help?
YES! Sideloading would be a huge step in the right direction, and would definitely save time!
The key is saving on server space- although most hosting services say that they allow "unlimited" hosting, they still have caps. Maybe there would be a way to change how the product is built? I am thinking more along the lines of how wordpress has an overall file library that you can pull from for varying applications. I know, I ask a lot of you guys but it is because I BELIEVE in you! ;)
Yes please this would be incredibly helpful. I think you guys make great products which is why I have several of them (web, blog, vend, flaunt) to run my photography biz and time first and foremost and then space would be saved if we can pull from one library and not have to re-upload the same images a second or third time into the separate products.
ok, i am marking this as planned -- tentatively mind you -- and it will be a sideload copy. the biggest issue in sharing.single upload is our dedication to not allow non-obvious breakage.
let's say if you "shared" a set of images from flaunt to vend and then you wanted to delete an image or add an image to the flaunt image list. does it delete it from the vend lineup? error dialogs? local copies of deleted files? sounds exhausting.
so i think if we do this, we'll do it so it pulls a copy of the files, so that each set can be modified/added to without affecting the other in ways you might not anticipate.
this certainly won't save on server space (and with vend, that really isn't a goal of the product. we clearly state you should have unlimited storage/it's own server), but it will save on time -- especially for those of you who share and proof the same images between these two products.
so i'm renaming the suggestion "add cross-product sideloading" and setting it to planned.
Great Michael. To continue on with this topic, how about designing it to allow you to manually sync from a source library to a destination library with the choice of source and destination free to be selected by the user? This way, we can have total control of what libraries to sync in any direction. This way we can get a copy to another product's library and from there, we can do whatever we want to it without affecting the others? Even better, it would be awesome if you can re-sync with the option of being able to choose the blot post library, flaunt set, or vend set. I'd pay extra for this feature just to have this kind of work reduced. It just makes sense. I know vend dimensions are 1000pixels either direction then the WP template we use is set to max of 970width so the dimensions being about the same is another reason this would be nice! I think it would raise your game as a company and your products to a whole new level with this kind of functionality.
Michael
yeah, I just see this as where the industry is going... one upload of all images to a library server, then draw from that server for all of your display needs. The more our flaunt, vend, blogs, and sites can make that process integrated, the better.
Michael- I see what you mean about the mess that could be made if you make changes from the individual applications. In Wordpress, if you delete an original image from the media library without deleting it from a blog post, the displayed image just doesn't show up (not broken). So maybe there is a way to write a code that says "if original is not found, do not display image". Really, the key would be to have a separate media library that you manage the original files from, then have the various applications link into that server using the image path. That way you could add or delete images from each application without affecting the others. You're right, storage is probably less of an issue than I'm making it out to be, and I do believe that wp makes multiple copies of images to serve different size applications (like thumbnails for instance). The single upload thing isn't a unique idea at this point either: Pictage/Shootq are doing a similar thing with Nimbus , and Showit is starting to go in that direction with PASS. Gotta keep an eye out for what my competition might be using ;)
Michael, Shane -- thanks for your feedback!
Single upload, in the opinion of this developer, is a bad idea. I think wordpress is a great example of how bad it can get when you try to make a do-everything-for-everyone media library. it's the reason why we built blogshow -- just to combat that sucker!! and wordpress is a global platform built by hundreds of intelligent minds -- and it's a monstrosity. uploading and inserting 30 images in wordpress = nightmare. uploading and inserting 30 images in blogshow = as easy as it gets.
so, i think we're gonna take it one step at a time. and we'll start with sideloading. let's see how that goes. if you;ve been with us for a while, you know we're always trying to maximize the ease of use and the power of the platform -- its not an easy thing to do, and we're trying to be diligent about it.
I agree! Blogshow is rad.. using it on a new site of ours, and it is working out really well. You guys know what you're doing and I'm sure you'll figure out something that works better than we could have imagined :)