search

avose / CardCloud

Web users share a virtual simulation of physical cards.
MIT License
1 stars 0 forks source link

Image Rights #3

Open avose opened 10 years ago

avose commented 10 years ago

I placed some starter images in the repo from the web, just as some stubs/placeholders. These should be removed... someone should either trash them, as the deck file can support URI-encoded images (make the users use their own images / image server), or some default images could be put up by us if we take some pictures of our own cards, yes?

jefflarkin commented 10 years ago

I vote for the user providing an image url as part of deck creation. Then we don't have to host anything or worry about copyright. Wizards has the image of every card available online. We could provide a search to make creation easier if we want, there's lots of sites out there that seem to search the mtg database and link to the images.

avose commented 10 years ago

Done; the user supplies a URL. We'll just be sure to support the URI embedded images and we'll be good to go. I'll remove the images from the repo shortly...

avose commented 10 years ago

Now that the URI with embedded images is fixed, this isn't so much of a problem; I removed all the card images except for the back...we need to still handle that sometime.. The felt table-top image is actually free to use personal or commercial, so the only rights issue left is the card back.

avose commented 10 years ago

So.. how to hanlde the card backs?? Make the very first line of the deck file be a URL/URI to an image for the deck back? I guess we could do that. How complex does this deck file need to be? Should we have a dedicated talk about the deck file, or just incrementally work on things as we go? I guess I could just add a little deck header real quick with a little info like card backs, etc...