Closed jancborchardt closed 10 years ago
Ok. The example also uses a module named "images" though, so we would need to change that as well. Then all data that had been updated using the "images" example won't appear in the "pictures" example.
is there a reason it shouldn't be images? an image is a picture or a photo or an icon or whatever else...
On Sun, Apr 7, 2013 at 1:15 PM, Jan-Christoph Borchardt < notifications@github.com> wrote:
Did we agree that the module for pictures/images/photos/etc. should be called »pictures«? If so, then the images example at /example/images/ should probably a) use the pictures module instead of »images« and b) be renamed to »Pictures example« to make it clear.
cc @skddc https://github.com/skddc @vcuculo https://github.com/vcuculo
— Reply to this email directly or view it on GitHubhttps://github.com/remotestorage/remotestorage.js/issues/308 .
We discussed about this a bit (fun fact: the wikipedia page for »Picture« redirects to »Image«). Somehow »pictures« seems more human to me, as that is more something you would say when talking to others, more than »images«. We wanted to ask a native speaker though, so @silverbucket what’s your call? :)
The point is simply that images/pictures/photos/screenshots/png/jpg/etc. should all be in one module. Regarding naming, we don’t have any particular preference (except I prefer »pictures« as stated above). We just need to settle on one for the module.
I was asking about that, and to me "images" is more generic as well (so this is what I think it should be).
yeah, picture is not really all encompassing. a picture implies an actual 'image of something' so.. an image of nothing much, would sound weird as being called a picture. "this is a picture of a fuzzy desktop background image"or a picture of 'red'...
On Mon, Apr 8, 2013 at 3:12 PM, Sebastian Kippe notifications@github.comwrote:
I was asking about that, and to me "images" is more generic as well.
— Reply to this email directly or view it on GitHubhttps://github.com/remotestorage/remotestorage.js/issues/308#issuecomment-16049326 .
Ok, so let’s call it »images« then. cc @nilclass
i still think it should be called "pictures", for a simple reason: the naming should not reflect the media type, but how the data is relevant to the user.
compare for instance "vcards" vs "contacts" or "text files" vs "documents".
if you say "my pictures" then you have an emotional relationship of property with them. "images" doesn't feel like you own them.
similarly we are also not calling the "music" module "sounds", even though, as you correctly state, images/sounds is more generic. that's exactly what makes them less meaningful. :)
we're talking about the valuable data of a user here, that's where the naming comes from. not from tables in a database.
I would agree with @michielbdejong . As a hint, Mac OS and Windows have "Pictures" folders in the home folder as well I think.
That's a straw man argument, as music is not all sounds (you wouldn't put sound effects in there) and contacts is actually contacts. Images is not the data type, but the content, and that means all images, not just pictures.
I have little opinion on whether "pictures" or "images" is better. But I think we should come to some decision soon, as there are multiple apps affected:
So, shall we put it for a vote? The tendency seems to be towards "pictures" - which would be great, because then we don't need to change anything (except for this example).
I pitched in with my $.02, and I also don't have particularly strong feelings either way, but I vote that Images is more correct, less annoying, and yeah. Better. :)
So, in case anyone was worried about it, I don't this anyone will revolt if we take the "safe" way and follow in the footsteps of Apple, Microsoft and Ubuntu. _cough_sheepcough ;)
On Thu, Apr 11, 2013 at 3:16 PM, Niklas Cathor notifications@github.comwrote:
I have little opinion on whether "pictures" or "images" is better. But I think we should come to some decision soon, as there are multiple apps affected:
- ghost (pull requesthttps://github.com/vcuculo/ghost-unhosted-webrtc/pull/10not merged yet)
- sharedy ("pictures" module is in master branch, but the deployed version https://sharedy.5apps.com/ still uses "sharedy")
- "pictures" gallery app (uses "pictures" module, but isn't deployed anywhere yet) So, shall we put it for a vote? The tendency seems to be towards "pictures" - which would be great, because then we don't need to change anything (except for this example).
— Reply to this email directly or view it on GitHubhttps://github.com/remotestorage/remotestorage.js/issues/308#issuecomment-16233563 .
err. "I don't think anyone will revolt" is what i meant to say.
On Thu, Apr 11, 2013 at 3:37 PM, Nick Jennings nick@silverbucket.netwrote:
I pitched in with my $.02, and I also don't have particularly strong feelings either way, but I vote that Images is more correct, less annoying, and yeah. Better. :)
So, in case anyone was worried about it, I don't this anyone will revolt if we take the "safe" way and follow in the footsteps of Apple, Microsoft and Ubuntu. _cough_sheepcough ;)
On Thu, Apr 11, 2013 at 3:16 PM, Niklas Cathor notifications@github.comwrote:
I have little opinion on whether "pictures" or "images" is better. But I think we should come to some decision soon, as there are multiple apps affected:
- ghost (pull requesthttps://github.com/vcuculo/ghost-unhosted-webrtc/pull/10not merged yet)
- sharedy ("pictures" module is in master branch, but the deployed version https://sharedy.5apps.com/ still uses "sharedy")
- "pictures" gallery app (uses "pictures" module, but isn't deployed anywhere yet) So, shall we put it for a vote? The tendency seems to be towards "pictures" - which would be great, because then we don't need to change anything (except for this example).
— Reply to this email directly or view it on GitHubhttps://github.com/remotestorage/remotestorage.js/issues/308#issuecomment-16233563 .
So let's keep it.
This example is not in the repo anymore (where did it go?), and the issue is outdated anyway. Closing it.
Did we agree that the module for pictures/images/photos/etc. should be called »pictures«? If so, then the images example at /example/images/ should probably a) use the pictures module instead of »images« and b) be renamed to »Pictures example« to make it clear.
cc @skddc @vcuculo