My idea is simply to have everything available as quickly as possible, i don't think any options are more than 2 clicks away from the user.
I've considered that the generation of the package and saving/opening template could simply be in the File menu instead of on the interface but there's still some place left for it if others would prefer button for it.
As for the Submit to CF, this is far from being final in anyway. There's a lot to figure out regarding how to deal with the psarc upload to a third party site and it will also heavily depends on how the toolkit and CF can interact.
I voluntarily get rid of the volume options for the track as i considered this would be better if done automatically by analyzing the song file itself according to previous discussion on the subject which shouldn't be impossible to do at all.
The pitch shift idea is not something i'm so sure about, it would be somewhat interesting but there's a heavy question of implementation of that.
Note that the arrangement and tone display is just something i had with the software i used for this design as i though it was space efficient and clear enough for user to deal with but anything that can do the same kind of job is fine by me.
There's still a lot to think about regarding all the other function the toolkit does integrate at the moment but i wanted to concentrate on what really matters to me as a charter (i don't recall the last time i used something that isn't part of that mockup).
Anyway, there's no pressure to change anything. It's just a thought that i had and wanted to build something clear to present it to all the dev and to be able to talk about it efficiently.
I hope you'll consider the ideas and i'm available to discuss and adjust this mockup according to everyone input so that we can make the toolkit better for everyone.
So here is what i put together from what i thought would be interesting : https://imgur.com/LKJvTD3
My idea is simply to have everything available as quickly as possible, i don't think any options are more than 2 clicks away from the user. I've considered that the generation of the package and saving/opening template could simply be in the File menu instead of on the interface but there's still some place left for it if others would prefer button for it.
As for the Submit to CF, this is far from being final in anyway. There's a lot to figure out regarding how to deal with the psarc upload to a third party site and it will also heavily depends on how the toolkit and CF can interact.
I voluntarily get rid of the volume options for the track as i considered this would be better if done automatically by analyzing the song file itself according to previous discussion on the subject which shouldn't be impossible to do at all.
The pitch shift idea is not something i'm so sure about, it would be somewhat interesting but there's a heavy question of implementation of that.
Note that the arrangement and tone display is just something i had with the software i used for this design as i though it was space efficient and clear enough for user to deal with but anything that can do the same kind of job is fine by me.
There's still a lot to think about regarding all the other function the toolkit does integrate at the moment but i wanted to concentrate on what really matters to me as a charter (i don't recall the last time i used something that isn't part of that mockup).
Anyway, there's no pressure to change anything. It's just a thought that i had and wanted to build something clear to present it to all the dev and to be able to talk about it efficiently.
I hope you'll consider the ideas and i'm available to discuss and adjust this mockup according to everyone input so that we can make the toolkit better for everyone.