4/16/2024 0 Comments Digicel flipbook onion skin colorOf course I hope you understand our intent is not to discourage you from working on the icons nor to make your life "harder", since like us you're volunteering your time to this project, but I hope you can see that we do have a procedure for how design & coding tasks are developed and integrated into Pencil2D, and simply making a PR without guiding your potential clients (project contributors & users) through a clear design pipeline that allows for proper review and that integrates with the Pencil2D pipeline, can eventually become harmful for the overall reception & acceptance of your proposals.Įither way thank you again for your time. This would help more contributors have a better idea of the changes overall as well as to avoid backtracking on designs that we might have missed previously. Once these updates have been discussed and partially approved then you can submit the svg's to the existing PR. I don't think it's an outrageous request to post screenshots of the icons both in isolation as well as how they look on the interface before committing, and for every update or batch you plan to commit you can post a comment with said screenshots to host a discussion on the specific icons batch. This unfortunately limits the amount of people that can provide an informed opinion if they don't even know how to compile the project. There are also extravagant features only available to animation software and those will require icons at some point too and those need to be developed from scratch as well.ĭon't get me wrong though, I agree that seeing the icons working in the app itself is an integral part of the design experience, but what about non-technical contributors? Since github has no SVG preview for commits or PR's we are forced to download them for individual review and re-compile the application everytime there's an icon modification on the interface. We would definitely like to see sketches, thought process and have a healthy discussion about the choices made for each icon. I'm not a programmer, I'm an animator and used to be a graphic designer, so I understand what you're trying to say about the importance of context and I believe the others do too, particularly for UI design, but making a PR at this stage unfortunately assumes your designs will be approved regardless of discussions, and disrupts the existing work pipeline that Pencil2D, and similar FOSS apps, follow for such tasks. This is a matter of adjusting one's workflow to an already established pipeline. ![]() To be fair, the particular issue at hand is not a matter of coding vs design. I don't know what is the best for coding a new feature but I don't think this approach works well with icon design. ![]() We certainly haven't changed most of the icons at the time, not because we "love" them, but because to be honest it is a demanding task and we had to allocate our time for other tasks while waiting to redesign the whole interface, icons included for a later version so everything could have a fresh take while being informed with all the new features that have been added over the years. ![]() First of all thank you for your consideration in the icon redesign. Furthermore, it's more efficient than doing it there because in PRs, you can see the changes I've made and compare it side by side with the files I've Hi. So, I think it's better to make an ongoing PR first where we all can compile the stuff ourself from the fork and see how it'd look in the actual app. You should interface and interact with it directly within the app to be able to see whether the design is good or bad (as I do in every step of doing this). To properly analyze and see how they go together, I can't just post the photos of icons here and let people judge it from there as it won't be sufficient in judging whether the icon is good or bad. That is how we usually do the development. I disagree, the pull request should be made when it's done, discussion about the designs should be made here, before the pull request is made. ![]() No, I mean, the cpp file or whatever that dicatet which icon goes where, the one which manages the UI. This list is made based on our master branch, which has a bunch of new icons compared to the version you're using.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |