The EULA permits others to download the Aseprite source code, compile it, and use it for personal purposes, but forbids its redistribution to third parties. On the 1st of September 2016, the main developer, David Capello, wrote a post on the Aseprite Devblog explaining this change. This license was kept until August 2016 with version v1.1.8, when the developers switched to a EULA, thus making the software proprietary. I'm thinking several approaches to color pickers (as people are requesting more like this one ), one possibility I'm thinking of is to include scripts to add customized color pickers (e.g.Aseprite, formerly known as Allegro Sprite Editor, had its first release in 2001 as a free software project under the GPLv2 license. Maybe I'm not seeing the features I want in it though?) If I program a HSV style wheel that lets you drag the hue on an outside circle and select the saturation and value on the inner part, should I push that code upstream (is there any interest?)Ībout this one, sure, you can contribute with pull requests, anyway that specific color picker sounds quite similar to the color tint/tone/shade picker: (Well at the very least, I don't like it's implementation. Originally posted by 一人ぼっちじゃない、いつだって:Last question is, I'm used to much more robust color wheels and I think the current one is rather useless. timeline) have their drawing code in their specific file inside the src/app/ui/ directory. Most of the interesting code is here: but each special app widget (e.g. (Originally there were no skin.xml at all, but then I started moving hard-coded parts to this xml, it was (is) a progressive effort which still needs some work to do (I've a "to do" item to improve the skin code.)) In a future "best case", I'd love to have an easy way to define objects in a CSS-like way and all dimensions/colors should be in the skin.xml Well, there are several issues: adjusting bounds in skin.xml will work for some cases (most cases), but there are hard-coded dimensions in the UI yet. If I were to make my own high resolution sheet (say 4k or something) and properly define the bounds of objects in skin.xml, would aesprite automatically size and reoginize elements or would I have to update UI code to handle proper scaling? If not, could I get a simple explination of how the UI system works and the associated source files? The skin appears to be a renderered bitmap with an associated sheet and skin.xml. Originally posted by 一人ぼっちじゃない、いつだって:I actually have 3 questions. Maybe I'm not seeing the features I want in it though?) If I program a HSV style wheel that lets you drag the hue on an outside circle and select the saturation and value on the inner part, should I push that code upstream (is there any interest?) Last question is, I'm used to much more robust color wheels and I think the current one is rather useless. Does that mean aesprite doesn't properly handle bitmap fonts and just expects all text to be contained in 8x8 boxes? I would imaging changing that would be easy, but if all the UI expects that size and doesn't handle it dynamically. Second, for text rendering all I see is a "font.png" with no associated data file. I would even prefer Graphics Gale Windows 98 theme over this :P I don't like retro UI in my work programs. This is a program that interest me, as it has much better features than Pyxel Edit and also offers source, but where I do not really agree with this program is the UI decisions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |