1. Origins

2. Vexi 1.0

3. Vexi 2.0

4. Vexi 3.0

5. Companies Using Vexi

6. Contributors
    Current  Inactive 

7. References

8. External links

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.

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

External links

• {{Official website|http://vexi.sourceforge.net/}}

• Wiener Neustadt (titular see)
• Wiener Neustadt World War II bombings
• Wiener Neustadt WWII bombings
• Wiener Neustaedter Kanal
• Wiener Neustädter Kanal
• Wiener Neustädter Lokomotivfabrik
• Wiener oboe
• Wiener Oper
• Wiener Peaks
• Wiener-Rogers Law Library
• Wiener's 1/f theorem
• Wiener's attack
• Wiener sausage
• Wiener SC
• Wiener schnitzel
• Wiener Schule der Architektur
• Wiener Secession
• Wiener series
• Wieners (film)
• Wiener Singakademie
• Wiener Singverein
• Wiener SK
• Wieners (movie)
• Wiener Sportclub
• Wiener Sportklub