Too be fair, a good support of graphics transforms and operations are keys to allow the creation of beautifull GUI. This is not restricted to gaming platforms. If you want to implement the material design specifications for example, you need a good graphic transform support for animations, blending mode support for correct components overlay and so on. That is why I started implementing blending modes (= porter-duff) support in my fork (https://github.com/ramsestom/CodenameOne) and I also intend to support color transforms soon (as it is a really powerfull way to handle colored icons and images, that can automatically adapt to a theme, without having to transform them into fonts or to create multiple colored version of the same image...) You said improving the CN1 UI part is on your top priority list. Then, I really think you should start with a strong support of "basic" graphics operations as they are the basis of any UI. As, I would say, as talented as you can be, it is easier to build a beautifull furniture when you have the correct set of tools than with only a knife and a hammer... ;)
On Monday, September 24, 2018 at 6:28:52 AM UTC+2, Shai Almog wrote: > How many transforms would we need for a tool for app development? > As I said to you multiple times before we didn't design this as a gaming > platform. > -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discussions+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/f2107c10-d09c-4a7e-b140-d4d82a85fb80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
