![]() 25th April 2018 - Developer untruths discovered! In this rant I am just proposing an alternative path for the Xwidget engine that probably would have led to success and the widespread adoption of a tool that the world does actually need but still doesn't quite have.įirst Encounters of an Xwidget kind - RainWidgetsUpdate 4. ![]() However, the very poor editing environment, the lack of any documentation whatsoever and the buggy implementation of APIs, coupled with a complete lack of support/updates for many years led to its failure to be adopted as the desktop javascript rendering engine of choice. It almost achieved this by building a very decent graphical GUI where a developer could compose and animate widgets and combining this with the embedding of a javascript rendering engine into one Windows desktop tool. Xwidget had the potential to be a rather nice widget IDE and widgeting environment allowing easy widget development and putting javascript programs on the desktop. ![]() ![]() What Xwidget could have been.What Xwidget could have been and how it should have succeeded? Just a short rant this time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |