Object Oriented Core Libraries

The 'Open Core' C++ Object Oriented Web development Library is free.

New: reference documentation to w3systems web libraries:  Documentation Here

I am a huge believer of the concept of intellectual property, but also think there's something to be said about sharing.  That said, this code should be considered under the MIT license model and not the GNU one.   I don't have the MIT legal notices in the code yet, (too busy) but will have them in soon.

I provide the C++ library source code as a courtesy to developers who build web based applications.   The library is called 'open' because it is freely available, and because it's based on open standards like C++, the W3C DHTML DOM and STL.   Its called 'core' because it's the basis for all of my systems. It's the component library we use for everything I do.

The web server code is written in C++.  Client browser code is object oriented JavaScript.   (I haven't linked in the client JavaScript code yet, but will soon!)  Both C++ and Javascript libraries are almost exclusively composed of objects.

If you download and use any of the libraries, please email me, and tell me about your experience with the code.

I have a couple of reasons for providing the code: I want people to use the code to augment W3Sytems consulting services. I also would like to have 'open core' C++ developers ready to help with ongoing projects.

Source and Documentation:

Open Core Webserver Library       Open Data Abstraction Library

Base 64 Encoding Code

ocCoder.h is a complete C++ source file for encoding and decoding base 64.

Client Side Javascript

     I have somewhat revamped functionality in the openDom.js class, specifically for generic event handling.  This is where IE and Netscape diverge quite a bit, and the standards don't help.   I have also added a method that creates a XMLHttpRequest object that handles the differences between Mozilla and IE.  This is useful for cross browser based AJAX style  programming.  openDom has other useful things like opacity settings, cookie abstraction and other stuff, all of which I will document.  Development overall on all of my code has gotten too far ahead of documentation, and I don't think this is going to be addressed completely anytime this year.

Thanks! David Mc

Key Design Considerations

All classes should be generic and adaptible.
Over time and use, the openCore library has become just that.
Keep generic and adaptible in mind as you design new classes.
Also - please consider sharing your classes with us - as it is to our mutual benefit to foster a sense of community among C++ developers.

Building the code

The code uses standard makefiles.
The unzipped files will create openCore and openData directories.
You should also build an additional directory structure that looks like this:

./include
./objects
./objects/pgSQL
./objects/mySQL