-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can and should we use existing logo? #23
Comments
I think we can use it, but anyway I totally agree, we should create a new one. Sooo I've made some new ones :)
I've also uploaded a 300% sized version here: https://i.imgur.com/4cZIWyp.png If anybody else want to try creating some more ones, that would be great, and after a while we could choose the one we like most :) |
I agree about changing the logo, that would be good to prevent confusion between the two projects. I quite like 1, 2 and 3, as they still have some link with the smiley-like Aseprite logo, while being clearly different. |
I would go for 1. |
Since the general feeling seems to be that the new icons should have some link to the old Aseprite ones, I used #1 to create all the icons and made a pull request ;) |
I'm not sure if we want to change the file icons. There are two options:
|
@JosefKuchar I fear I don't fully understand your last comment ^^U Didn't you suggested the logo/icon change? I think changing the logo/icon is a good idea, that way if somebody has both programs installed (s)he will know if the default program associated with .ase files is Aseprite or Libresprite. Are you now having second thoughts? Is there any drawback that I missed out? :S And about the file extensions, (probably we sould talk about it in another thread, but) I think that we should try to keep the compatibility/file extension. If there will not be any differencies between the file types that LibreSprite will be using and the Aseprite ones (remember that rigt now there isn't anybody actively developing LibreSprite), and Aseprite is keeping backwards compatibility (as it has been doing until now) I think that changing it from .ase to a new extension would be confusing and unnecesary. |
That sounds ok |
This is another thing related to rebranding. Can we use existing (aseprite) logo? Even if we could i think we should create a new one.
The text was updated successfully, but these errors were encountered: