OCKit Stages
Last Updated on Friday, 12 November 2010 08:43 Written by aoirthoir Friday, 12 November 2010 08:36
The OCKit is planned in stages. It’s taking a long time to put together, because there is a lot to put together, trying to get all of the pieces right.
Stage 1: OCKit4Web.
This is a version of OpenCOBOL and company, entirely as a hosted solution. So persons will be able to sign up for free. They will receive a shell account from me. They’ll then have a console in GNU/Linux to compile and test OpenCOBOL programs. If the tests that DamonH is doing turn out well, the entire interface may even be Web based. This version will have a great focus on Web App production.
Stage 2: OCKitVM.
This is a version of OpenCOBOL a guest inside a VirtualBox virtual machine (VM henceforth). Initially it will be Debian or Ubuntu [server] based. In the future other VMs might follow (BSD, Fedora, Suse, Puppy Linux etc). Due to licensing restrictions we will never be able to distribute a VM with Windows or Mac as the guest operating system. But the VMs we distribute will run on Windows, Mac and anywhere else VirtualBox runs.
VirtualBox allows many useful features to allow OpenCOBOL inside a VM and apps compiled inside that VM to seem as if they are runing native. The two primary features are Seamless Windows and the fact that the Guest can communicate with the Host. So now output from STDIN, STDOUT, STDERR and others, can be routed both ways.
OCKitVM will allow us to distribute a version of OpenCOBOL and company (see below) that doesn’t really require native installs. So it will “just work” regardless of the operating system if runs in. So long as VirtualBox just works that is.
Stage 3: OCKitNative.
This version will be a native install for various operating systems. The first release of OCKitNative will be Ubuntu/Debian based. Fedora, BSD, OpenSolaris, Windows, Mac and others will follow.
This is the largest undertaking because it requires a lot of testing and answering a lot of questions. Do we install OpenCOBOL to compile with VisualC? A freeware C compiler? GCC? If VisualC for instance, then we have to get a license for VisualC so we can test properly (I don’t break software licenses). Because this is the largest of the jobs, it’s also last on the list. The original idea for OCKit didn’t even entail a native install, just an “instant on” virtual machine distribution. But demand for native installs means that eventually we’ll need to create them. To do so we need volunteers. 
A note: Most of the conversation regarding OCKit will be taking place at http://add1tocobol.com. I have a plethora of tools there (more coming) that will allow me to track the OCKit varieties development, set roadmaps, tasks, follow bug reports and more there, that this forum doesn’t really offer us.
Link for this blog post at add1tocobol.com: http://add1tocobol.com/blog/2010/11/12/ockit-stages/
This content is published under the Attribution-Share Alike 3.0 Unported license.
As Aoirthoir said I am currently working on a couple of proof of concepts. Both are going excellent.
1) Compiler web interface. You will be able to compile and test run your code from this interface. The prototype is finished and is working well.
2) OCEditor. I am currently working on an In Browser Editor for OpenCOBOL. Once completed the Compiler Web Interface will be integrated in for a robust OC IDE where you will be able to edit, compile, and test your code online.
I will make a formal post when things are along far enough that you will actually be able to see it all working.
Please feel free to email me with any questions or pop into the chat room. I am there most usually during the week and most weekends.
Yes… who works not on (better) OC editor. VI is nice, Browser Editor also, but I need an IDE (!) – and now I work on Eclipse port.
Nerger, danke! We’d love to see and host your results at the site. Just let us know.