Vexi Contents Origins Vexi 1.0 Vexi 2.0 Vexi 3.0 Companies Using Vexi Contributors References External...


User interface markup languages


InternetXUL
































The Vexi Platform
Developer(s) Vexi developers
Operating system Cross-platform
Platform Java
Type Internet Software Development
License
GPL and LGPL
Website vexi.sourceforge.net


The Vexi project is an international effort to create an easy-to-use platform for the development and delivery of Internet application interfaces outside of the standard browser stack. It has similarities with XUL but runs on top of the Java stack, making it browser independent.




Contents






  • 1 Origins


  • 2 Vexi 1.0


  • 3 Vexi 2.0


  • 4 Vexi 3.0


  • 5 Companies Using Vexi


  • 6 Contributors


    • 6.1 Current


    • 6.2 Inactive




  • 7 References


  • 8 External links





Origins


Sometime in late 2001, Adam Megacz[1] released the XWT[2] project as open source software. XWT eventually evolved into the Ibex project as the technology underpinning the project got overhauled and enhanced, but the upheaval would eventually lead to discontent among contributors upset at the extended development period of several years without a stable release. Eventually, in April 2004, core contributor David Crawshaw called[3] for a stable release to avoid a fork, which Adam declined[4] instead encouraging the fork as he felt community pressure was compromising technical decision making.



Vexi 1.0


In April 2004, announcements of Vexi began to appear, and a project website became available on the since-defunct www.vexi.org domain. The initial principal goal of the Vexi project was to create a stable release based on the XWT/Ibex technology stack. Whilst Vexi 1.0 was never officially declared, there were several releases and by late 2005 there was a stable version but it omitted many of the new Ibex technologies.



Vexi 2.0


Vexi 2.0 development focused on integrating these, but they presented problems including incompleteness, severe bugginess, and unreliability under load, making a Vexi 2.0 release look less likely as time went on. There was never an official Vexi 2.0 release.



Vexi 3.0


In 2007 the principal developers of Vexi - now brothers Charles[5] and Michael Goodwin - announced their intentions[6] to break with the 2.0 platform API and overhaul it using the lessons they learned, refining the Ibex technology stack to replace the problematic parts. This new version, tentatively called Vexi 3.0, arrived at feature completeness in 2009 and is stable.


Vexi is still under active development.[7]



Companies Using Vexi


Vexi is in production use by several companies around the globe.


Companies currently specialise in developing Vexi applications:




  • Web Enable IT (UK) with their software Emanate


  • Achievement Focused Technology, Inc. (US)


  • Health Care Systems Corporation (US) with their software HCare1



Contributors



Current



  • Charles Goodwin (Core layout and widget development)

  • Michael Goodwin (New core development)

  • Jeff Buhrt (Core debugging)



Inactive



  • Adam Megacz (Original author of XWT/Ibex)

  • Brian Alliet (Major core contributor)

  • David Crawshaw (Major core contributor)

  • Tupshin Harper (Core network code)

  • Adam Andrews (Core and widget debugging)



References




  1. ^ Personal website of Adam Megacz


  2. ^ Legacy website for XWT


  3. ^ http://article.gmane.org/gmane.comp.java.xwt.core/4313


  4. ^ http://article.gmane.org/gmane.comp.java.xwt.core/4331


  5. ^ Personal website for Charles Goodwin


  6. ^ http://article.gmane.org/gmane.comp.java.vexi.core/650


  7. ^ Project analysis at Ohloh.net



External links


  • Official website



Popular posts from this blog

Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...