rbCMS - Web Site Builder

While playing around with the runWiki project, I seem to have accidentally invented the world's first CMS (Content Management System) built in Run BASIC. I'll pull in some documentation and put a demo site together a little later today. This could be just the ticket for RunBASICNet subscribers looking for a way to create a web site without having to code every line, div, and link in RB or HTML to make it work. Think of "WikiWriter Meets WikiPedia" and you'll get the (Run) BASIC idea. ::)

Sounds cool. Can't wait!

-Carl

Me, too! I'm having a gas, here, putting the site together. I just added a couple of features, like numbered and bulleted lists, embedded SPAN capability for formatting, special purpose DIVs, URL aliasing....

Will the source code be made available?

-Carl

Well, it's in Run BASIC, so it's kind of hard to keep the code secret if I want anyone else to use the program. Unless, of course, we make it part of the RunBASICNet package, and swear subscribers to secrecy! ::)

How about this? I'll make rbCMS open source, and produce a commercial program that can produce and display rbCMS-compatible files in the Windows environment, for standalone delivery of rbCMS files. Then I'll write import and export routines for rbCMS, for file transfer in and out of the RB environment. So then someone can use rbCMS to create and display the files on the web or network, and my magic program to package, deliver, and display rbCMS projects to standalone computers (offline). They can use rbCMS to write and/or collaborate on project authoring, then package the file for CDROM delivery. They can write a project in my magic program, and load it into rbCMS for delivery on the web, or as a project for standalone delivery in a "read-only" version of my magic program.

So now we would have a "killer application" for Run BASIC, with a commercial spin-off that supports Run BASIC without competing with Run BASIC! All I have to do is add "Import" and "Export" buttons to rbCMS, and maybe write a little code, and we'll be all seet to be acquired by Google! ::)

Well you can always release the source for a simple version with the basic features and develop a fancier version with the sources held privately.

-Carl

That's interesting! It would be nifty to have a way to develop and deliver RB apps with protected source. I can figure out how to do that with content files, with a little encryption, but don't know how to do it with .BAS files. Hmm.... Maybe a public/private encryption key, with a decrypter shell that takes the key and the encrypted source and feeds decrypted BAS source directly to the RB server for execution.... Or build a decrypter into the server itself, with an encrypter in the RB Personal environment.... It would make RB a stronger tool for business and education applications, wouldn't it?

I don't understand what you mean Jerry. What about Run BASIC is unsecure that you feel your source code is not private?

-Carl

If someone wants to install rbCMS on their RB site, I have to give them the source code to install as a project, I believe. So, there it is. If I install it for them, instead, on a runbasicnet.com account, the source is still available to the account owner via FTP.

In order to secure the code, I would have to eliminate FTP, lock access to the rbCMS project directory so the account own can't get in, and create a file uploader and manager in RB, and allow access to the account only through the RB IDE. That ain't such a stupid idea, I'm thinking, and it would make a good Starter package, with Developer package adding FTP access, so maybe I'll go ahead and do it that way. I could also set up a superRBserver whose projects lived in a private space but who has read/write privileges to sub-accounts, so accounts could use a project but couldn't edit it.

But that's kind of a "down the road" project. I've kind of got my hands full, at the moment, just establishing runbasicnet.com as a proof of concept. ::)

Ok. I thought you were saying that the source code running on a Run BASIC server is visible to the world, which is not the case (and not what you meant). So what you're dealing with is simply a matter of licensing, not of security per se.

-Carl

Yup, that's the case. It's like PHP -- the user can't access the code, and only sees the generated browser display. But to distribute (license) an application, you have to deliver the source.

I rewrote rbCMS to use text files (single file, multiple pages) instead of SQLite. Source files are more transportable, more easily backed up, and easier for multiple authors to handle for collaboration. I have to shake it out a bit, and add a bell and whistle or two, before posting it. Look for a running demo and request for beta testers by Monday. ::)

Perhaps text files are easier for novices to deal with, but SQLite database files are extremely easy to back up and transport, and they work across OSes.

Can't wait! :)

-Carl

I had some problems with SQLite, getting some munged text when coming out of textarea editor to SQLite and back. I figure to go open-source, so maybe someone else could smooth that out.

The part about using text files that I like is that you can use an external editor fi you want for your writing. That means you won't be mystifying your site visitors with jarring changes during development.

I'm sure folks are going to come up with some nifty additions and enhancements. I've added the last on my list, for the moment, (boilerplate includes and inline CSS capability) and am now using rbCMS to write its own docs and demos. Tomorrow we launch!