Given that I had only just learnt VB.Net there are a few bits that I’m not terribly proud of, but its mostly alright. It is written in VB.Net for the MS .Net framework 1.1. It should be possible to compile it for the Mono framework without too much difficulty which will give you a cross platform version.

Please note that I did put a fair amount of work into this app so please give credit where credit is due if you re-use any of the code.

You can download the source code directly, or from my downloads page where you will also find links to my other available downloads.

Disclaimer: Please note that I am not responsible for any damage to any computer system as a result of software source code or any other media that is downloaded from my website. Every effort has been made to ensure that all downloads are virus free and that no malicious code is included in downloads but it is the responsiblity of the end users to ensure that what they are downloading is safe for use on their computer system.

Whilst this in itself isn’t too interesting, some of the information in the entry is interesting. Firstly, the MWF (Microsoft Windows Forms) project for Mono is now up to 98% complete. Most of the basic controls are now complete.

The second interesting piece of information is that you can now get a Live CD for mono. The CD is freely available as an ISO which can be downloaded directly via HTTP or via BitTorrent (see www.mono-live.com).

The upshot of all this is that hopefully MojaviBuilder will now run under Mono. I have downloaded the ISO via BitTorrent which I’ll burn to CD when I get home and then have a go and running MojaviBuilder. If it does run then I’ll know I can go continue developing MojaviBuilder in .NET 1.1 safe in the knowledge that I can be run under Windows, Linux, and MacOS.

Unfortunately the free account from CVSDude only allows for one developer account per project. They do, however, say that non-commercial projects can get free account upgrades, so I’ve sent them an email asking for extra accounts, I didn’t, however, ask for extra storage space as I would like to keep the source code to MojaviBuilder tight so I’m going to try to stick to the 2Mb limit.

I sent the request at about 11am GMT and I haven’t heard anything back yet, which isn’t really suprising as CVSDude is run out of Australia. In the mean time, does anyone know of any good free Subversion hosting? I don’t get paid for developing MojaviBuilder so I don’t have a lot of money to pay for things like Subversion hosting accounts.

Then if any developers wish to get the source code to make a port to Java, etc. or anyone wishes to make chanegs then they can request an account from me to allow them access to the code.

I must point out that this is only an idea. Please also bear in mind that I will be paying for this out of my own pocket. If you feel strong that I should go ahead with this idea then please leave a comment.

Last night, howver, I managed (in #develop) to create a simple notepad editor based on the texteditor in #develop and have it highlight my PHP code. The PHP language definition file still leaves a lot to be desired but it is progress none the less… watch this space for more info.

Mojavi 3.0.0-DEV is the Mojavi framework for PHP 5. According to Sean:

The latest stable version is 2.0.0. Because of the request for a PHP 5.0 compatible version of Mojavi, development has been started on Mojavi 3.0. Mojavi 3.0 will take full advantage of PHP 5.0’s new object-oriented features and will be developed in the 3.0.0 branch.

I guess I’ll have to start work now on making sure that MojaviBuilder can generate Mojavi 3 compliant class files. Maybe this would be a good time to get MojaviBuilder 2 back on track after putting it on the back shelf for a while.

The syntax highlighter seems to work fine with the amount of code that I’ve got in my templates, but put too much code in and the performance seems to lag a bit.

The entry fields on the right hand side are (in order):

• Action Name: The name of the action (no spaces please).
• Default view: The view to be returned by the getDefaultView() function in the action class.
• Request Methods: What types of data transmittion will be accepted by this action.
• Secure Action: Does this action require the users to be authenticated.
• Require Privilege: Does the user require a special privilege
• Privilege Name: The name of the required privilege
• Namespace: The namespace that the privilege resides in.
• Views: The view files to be generated. This should at least contain the default view.
• Custom Validation: Whether the validate() function should be added to the action class
• Register Validators: Whether the registerValidators() function should be added to the action class.
• Handle Errors: Whether handleError() function should be addedto the action class. This is only required if Customer Validation or Register Validators is checked.

The main window also has several menus:

• File:
  • New Project
  • Open Project
  • Save Project
  • Close
• Project:
  • Name: the name of the project.
  • Path: the path for file generation. Currently this is the module folder.
  • Version: Which verison of Mojavi to generate files for (1 or 2)
  • Generate Files: Generate output files.
• Help
  • About

The project files are saved as *.moj files. If you must know, the are just XML files which wrap up the data for the project and the actions and therefore you could manually edit the files with a text editor is you so wish.

At some point I shall make a Schema file available but not just yet.

Warning: File generation is on Mojavi Builder releases 2, 3 and 3.1 is a destructive process. Any existing files and folders in the file generation path WILL be destroyed. This has been removed in Mojavi Builder release 4. See below for more information.

For news and updates about Mojavi Builder releases please check my main site www [dot] GrinGod [dot] com.

A mojavi application is based around the idea of “actions”. An action may have several Views associated with it one of which is used to render the final output based on any data received from the user.

For example, your application may have a “Login” action. You will therefore need to create a LoginAction.class.php file which will contain a php class called LoginAction. This action may specify that is no user input is received then the LoginView_input.class.php should be loaded to generate the output. Otherwise, if data is reveiced and is is correct the the file LoginView_success.class.php is load or, if the data is incorrect, then the file LoginView_error.class.php is loaded.

As you can see, this already requires four files to be generated and thats not including the HTML template files to generate the HTML output or any other required view. As an example, at work I have just created a very simple mojavi application which has required 57 class files to be generated.

The idea behind this tool is to automate as much of the file and code generation as possible. This tool allows you to create a project (at this stage a project is equivalent to a Mojavi application module), create actions for the project, specify the generic details of each action, and specify which views will be required by each action.

• Project Management
1. Modules
2. Actiosn
3. Views
4. Code Directory
5. Mojavi Version
• Template Management
1. Template Versions
2. Code Customisation (Syntax highlight editor)

The bad news for those of you that don’t run WIndows is that I will be continuing development in VB.NET. The reasons for this are that (1) I know VB.NET and (2) I don’t have the time to spend on writing and supporting it in any other language.

I will try to keep the components that I use to the standard Microsoft ones in the hope that when Mono goes GUI it will be able to support MojaviBuilder, but beyond that I can’t promise anything.

If you have any strong feelings as to what should be included/excluded from MojaviBuilder 2 please leave a comment and I’ll see what I can do.