XML made simple   
Home   Support   Contact  

Home
Products
Downloads
Purchase
Support
Articles
   xml to edi 850
   xml schema editor
   xml editor
Introduction
Chapter 2
Chapter 3
Chapter 4
Conclusion

Chapter 4: The Wet Stone for XML Developers

We have seen somewhat the reasoning behind the creation of such an application, a need in the market for a simple yet powerful XML text editor. We have also seen the evolution of this need, as well as the evolution from a previous application, xmlArchitect. Now, we shall take a small look into the evolution of it's name.

Naming xmlHack

SysOnyx Inc. has a tradition for naming their applications after unique sounding professions, professions that do what the application tries accomplishes, but in a different field. Architects create the designs for buildings, whereas xmlArchitect aides the XML Developer in creating the design (or schema) of an XML document. Cartographers are professional map makers, and xmlCartographer is a tool specifically designed to help the XML Mapper through stylesheets.

When it became evident that an XML editor was going to be created, the question of what to name it arose. Working with the concept that the editor was to be simple (geared for text editing), but powerful (lots of nifty, optional XML features), quick and efficient, we started banding around different ideas. xmlEditor was almost immediately thrown out, since it was too plain and obvious. We like naming our products with interesting, unique names. The idea that the editor was to manage XML files was brought up, along with the names of xmlSteward, xmlGateway, and xmlPortal. This however seemed to imply that the application did a lot more than we really intended it to do. The concept that this may become SysOnyx's flagship product was also tossed up for discussion, and so the idea of xmlLapidary was thought of, a lapidary being someone who works with and/or polishes gems and precious stones. This would be a direct reference to the "Onyx" part of SysOnyx. Even the development codename was discussed and even tested, but due to the intense feedback from users, the opted to pick a different name.

None of these names and ideas really jumped out and grabbed our attention though. Then xmlHack was suggested.

We thought about it from both the "hacker" angle, as well as the "sword" hack 'n slash angle. This product is a gritty product, it's not fluffy, it's something a warrior would use to fight his way through hordes of baddies. xmlHack looked more and more like the name of choice. Then of course we had to consider the fact that "xmlhack" is already used in the XML community today as www.xmlhack.com. It's a great website run by the O'Reilly guys that reports on XML related news. Will there be some confusion between xmlHack and xmlhack.com? We think not. One is a great news website, the other is a great text editor.

<- Return Continue ->