XML Developer Tip
(Receive this column in your inbox,
click Edit your Profile to subscribe.)
Want Windows results? Try Bindows
If you want to build Web applications that look and feel like Windows as much as possible, you've got two basic options:
- Jump onto the .NET bandwagon, and work within the Microsoft APIs and development framework.
- Pick a third-party alternative, and hope for the most Windows-like results.
Given those options, why might an XML developer prefer the latter rather than the former? Answers vary from individual to individual, but often boil down to matters of expense (the cost of Windows servers and development tools is not trivial), complexity (a serious investment of time and effort is required to master the tools and APIs in the .NET environment sufficiently to do top-notch, commercial-grade work), or politics (for some, jumping on the Microsoft bandwagon is no big deal; for others, it's viewed as a form of selling out or of "dancing with the Devil").
If you find yourself in the third-party faction, no matter why, you'll be pleased to learn that a nice toolset and API collection called Bindows is available. Among other things, Bindows offers a reasonably complete and comprehensive set of GUI widgets and controls that look enough like their Windows counterparts to work for most developers seeking to leverage that well-known and widely used interface. For a quick look-see jump over to www.i-see.net/bindows/ and check out the samples linked to the home page.
The advantages of Bindows are naby: It's relatively compact; it imposes little processing overhead on clients or servers (its developers call it "zero footprint" code); and it provides broad, useful functionality without making developers climb a huge learning curve. The disadvantages include a short track record, some reports of problems and instabilities (which probably relates to its short product life), and licensing terms that are somewhat vague and mysterious (one must e-mail the developer for details, a circumstance not exactly calculated to promote serious interest among those looking for transparent terms and an easy, straightforward business relationship).
Does this mean I think Bindows is ready for heavy-duty, prime-time use? Probably not yet. Does this mean I think Bindows is nothing more than a curiousity? Definitely not. For one thing, it demonstrates the continuing power of well-conceived alternatives to Microsoft technologies. For another thing—more important to my admittedly XML-centric view of the world—it makes a compelling demonstration of how XML can drive potent, complex development tools, and support equally capable applications.
About the Author
Ed Tittel is a 20-plus year veteran of the computing industry, who's worked as a programmer, manager, systems engineer, instructor, writer, trainer, and consultant. He's also the series editor of Que Certification's Exam Cram 2 and Training Guide series, and writes and teaches regularly on Web markup languages and related topics.
For More Information:
- Looking for free research? Browse our comprehensive White Papers section by topic, author or keyword.
- Are you tired of technospeak? The Web Services Advisor column uses plain talk and avoids the hype.
- For insightful opinion and commentary from today's industry leaders, read our Guest Commentary columns.
- Hey Codeheads! Start benefiting from these time-saving XML Developer Tips and .NET Developer Tips.
- Visit our huge Best Web Links for Web Services collection for the freshest editor-selected resources.
- Visit Ask the Experts for answers to your Web services, SOAP, WSDL, XML, .NET, Java and EAI questions.
- Choking on the alphabet soup of industry acronyms? Visit our helpful Glossary for the latest industry lingo.
- Couldn't attend one of our Webcasts? Don't miss out. Visit our archive to watch at your own convenience.
- Discuss this article, voice your opinion or talk with your peers in the SearchWebServices Discussion Forums.