I've been passionate about building software since I got my first computer as a kid - A Sinclair ZX-81 with 2k of ram. I started working on what has turned out to be my life's work in 1996, which was an OO framework based around the ideas from UML and Design Patterns. The 90s were an excited time for the OO development community, which somehow seems lost to the excitement of web development and fast money from internet ventures.
Over the last 14 years I've been expanding that OO Framework, which I now call the Syrinx Web Application Framework (SWAF), though it isnt just for web app development. I've been fortunate to be able to rewrite and refine the framework for various large US corporations and in 2006 I moved from the United States to the Philippines in hopes of building up a small development team to help build serious applications on top of SWAF. The OO design and architecture of SWAF has progressed from C++ on OS/2 and Microsoft COM, to Web sphere Java and now .NET C#.
Im a big believer in building a framework that isolates an application's business logic from technology libraries that seem to be changing faster and faster each day. I dont like feeling like a pawn in the games played by the big technology companies as they try to be the latest and greatest above their competitors. If you've ever been frustrated by a technology company dropping one API for another, forcing you to rewrite your app or get left behind on old technology, you know what I mean. SWAF is somewhat of a defense mechanism against those types of changes. You can use the latest and greatest, but keep it out of your core business logic so you're not rewriting that each time you change to a new GUI or database API.
Over the last 4 years we've been building up the Syrinx Community Server (Syrinx CS) product, which is a web app and windows app foundation that we use for our client projects. We made SWAF and Syrinx CS open source projects because:
- We wanted to make sure our corporate clients knew the code base being used for their application was completely available to them after the project was completed.
- We felt that we could help other developers with a solid OO framework and app building environment that was robust. By growing the developer base of the product we use with our own clients, we could all help each other with finding bugs and enhancing the features available.
If you'd like to read some of my technical issue blogs, you can find it at:http://syrinx.ph/Blogs/Matt.aspx
If you'd like to see more about the Syrinx Web App Framework (SWAF), we've got some decent docs at:http://syrinx.ph/swaf.aspx
If you'd like to learn more about Syrinx Community Server (Syrinx CS), you can read about some of its features at:http://syrinx.ph/Community.aspx