eDriven.Gui 2.0 is released and is available in the Asset Store:
You can also grab a copy of the free (evaluation) version, which is fully functional (identical to the Asset Store version plus watermarks):
You’ll notice that I’ve removed noticeable watermarks from the editor (leaving only a single one) so you can now work with the evaluation version more smoothly.
eDriven.Gui v2.0 is in many ways rewritten from scratch. However, the majority of the API stays the same.
I’ll update the documentation ASAP. Meanwhile, I suggest to dive into the example code (it should be self – explanatory).
I’ll cover all the new features in the series of articles. Here’s just a quick list:
1. New styling system
The old “style-mapper” concept is replaced with more intuitive CSS-like styling concept.
Things are now pulled out directly from components (by reflection), so you don’t have to write style mappers for each and every component. You are only required to decorate your component with style metadata (containing style name, type and a default value).
Styles are edited in the single place, a component called “eDrivenStylesheet”.
And yes, stylesheets could basically work with any script (not only with eDriven.Gui components) and I’ll cover that in one of the following articles.
2. New skinning system
In the previous version it was pretty hard to separate the functionality from design, and changing the look and feel of the component was painful.
Now, the Flex-Spark type-of skinning has been adopted. You could write your own skin for each component (skinnable).
Skin is a class containing a presentation logic, and must obey some rules in order to communicate with component itself.
You can change the component skin on-the-fly if needed.
3. Workflow improvements
Many of things have been improved, such as (infamous) hierarchy/persistence problems, the lack of documentation (now there’s in-editor documentation for each component).
There are additional debugger windows (Hierarchy and Persistence windows) which will help you detect and solve problems.
4. Moving away from complex IMGUI features towards the next low-level rendering system (Unity sprite system?)
The Immediate Mode GUI has a number of buggy features, which motivated me to use only a small subset of them.
Some of the buggy features are scrollview, click propagation etc.
By moving the system away from IMGUI features, and using IMGUI just as a renderer, I believe it should not be a huge problem migrating eDriven to the next (3D, low draw-call) rendering system.
That’s because eDriven is actually a sprite arranger. It moves, resizes, changes Z-order and tweaks properties on sprites. It also creates and destroys them.
5. Data controls
Having data controls with renderers and data providers is a huge step forward for any GUI framework. I hope you’ll enjoy it.
Buy until Dec 31!
I’m giving a promo discount price of $125 instead of $200, until December 31!
By purchasing now, you are eligible for all the future versions of eDriven.Gui!
Enjoy playing with eDriven – many cool things to come!