What's the one senseful thing to do if you live anywhere remotely near a pub called "The Rhino"? Exactly, you go there to talk about
and the wonderful things you can do with it on the server-side thanks to
. For example, you can do this at
The Rhino in Toronto
Kristan "Krispy" Uccello
Ajax Pub Nite
is February 11, 2007 at 7pm in Toronto at The Rhino.
If you live at the other end of the world, I'm sure
Maksim Lin's talk on Web Development with Helma
would be another excellent opportunity for Rhino chatter. I assume that takes place somewhere in Melbourne, Australia, but the exact place and time is yet to be announced.
Then there would be another chance at the
OpenExpo in Berne
, Switzerland, where I'll be presenting the Helma project on the 12th and 13th of March 2008.
And if you are at
this week, I won't mind talking about Helma there either :-)
It is basically Mozilla running behind Apache on the server-side, extended with the server-side functionality you would expect, like reading/writing files, db access and other external communication. But since the server-side runs inside a full fledged browser environment, with not only the DOM but CSS and all the client-side js functionality, including XMLHTTP requests and the whole bit, you can really work on both sides with less mental switching.
Maybe sometimes it really helps to see both the client-side and server-sider code together like this, without the need to switch between separate files for views and controls. That's something to keep in mind for Jhino. With the older versions of Openmocha you always had the server-side and client-side code together on one page when using the web-based editor. With Jhino we currently lost that. So, this is one good argument to bring back a gui editor where one can see all the properties and behaviors of a Mocha object at a glance.
I'm not sure how often it will really make sense to run the code on both the client and server side. I hope we will come up with some interesting use cases for this, because the idea is intriguing!
A new and experimental core for a complete rewrite of Openmocha.
The soft-coding allows modifications and development work from the
"inside" of the running web application. The behavior of the web
application can be changed in ways that closely relates to the
hierarchical content structure of the resulting website, without
the need to "hard-code" these changes in code files.
Every content object becomes "sovereign" and can define its own
behavior, overriding what it would inherit from the hard-coded
prototypes or from other soft-coded objects higher up in the
content structure hierarchy.
The e4xd objectengine leverages naming conventions for hard-coded
filenames and soft-coded object property names to overlay the
hard-coded and soft-coded properties and methods and determine
the behavior of an object at runtime.
Internally, these conventions follow the existing ones of the Helma
framework, but expand that philosophy, adding additional conventions
and accomodating to the needs of the soft-coding environment.
The jhino sub-project provides a base application scaffold for the
soft-coding environment. It leverages the e4xd object engine and adds
an additional layer of conventions, resulting in a basic scaffold
for a working base application with CRUD type functionality and
access control. Basically, jhino already provides a fully working
soft-coding environment, but requires the standard Helma development
tools such as the shell and inspector to do the actual "soft-coding".
of Helma and Rhino. In the case of Rhino, e4xd depends on the JOMP
patch and Helma needs to be modified to do the additional file suffix
mapping required by e4xd.
create an admin account at http://localhost:8080/exampleapp/register
copy the authentication code to the server.properties file
login at http://localhost:8080/exampleapp/login
Prerequisites and System Requirements
To run OpenMocha a Java Virtual Machine 1.4 or better is required.
For FreeBSD and other operating systems with ports collection you may
install a JRE or JDK from the ports collection. For Windows, Linux and
Solaris you can get a Java runtime or development kit from
http://java.sun.com/j2se/downloads/. If you are on Mac OS X then you
already have a Java runtime that will work well with OpenMocha.
While you can integrate OpenMocha with other tools such as Apache
and MySQL, you do not have to. OpenMocha is pre-configured to be
deployed on its own and comes with a built-in object oriented
database and web server.
Getting started with OpenMocha
On the e4xd.org site, you should be able to find a working build to
download and simply start with ./start.sh
For FreeBSD, Linux, Solaris, Mac OS X and other Unix flavors, start
the Helma framework by invoking ./start.sh from the command line. On
Windows, invoke start.bat instead.
If the java command can not be found, make sure the JAVA_HOME
environment variable is set to the location of your Java installation.
With Helma running, you should be able to connect using your
browser and the URL http://127.0.0.1:8080/ or http://localhost:8080/
To initialize the setup, complete the user registration form
at http://127.0.0.1:8080/exampleapp/register and follow the
instructions to copy the security information into the
server.properties file. You may then login to your new OpenMocha
server via http://127.0.0.1:8080/exampleapp/login and start
configuring and deploying your web applications.
Installing jhino modules in a existing Helma setup
In addition to the full openmocha build, there is also a build that
contains only the jhino modules and patched jar files, in order to
add jhino to your own helma install. You would need to replace the
helma.jar and rhino.jar in your Helma install with the patched
versions. The "objectengine" and "jhino" modules are expected
to be placed in Helma's modules directory and the exampleapp would
normally go into Helma's apps directory. You could then start the
example app from your manage application or add it to the
apps.properties file to have it start automatically.
Other than what you find on the (possibly not yet existing) e4xd.org
website, the best places to get in touch are the openmocha mailing
list and google group or the
#firstname.lastname@example.org IRC channel
Over the past days, I did some experimenting with the JOMP patch for Rhino and the mapping of additional filename extensions to HopObject properties. I probably took it a bit to far and made the list of supported file suffixes to long, even introducing duplicates, but I would like to propose supporting additional filename based conventions for Helma 1.7.
Here is what I added for my experiments:
foo.macro --> becomes a hobj.foo_macro function with "params" as first argument
foo.get --> becomes a hobj.foo_action_get function
foo.post --> becomes a hobj.foo_action_post function
foo.put --> becomes a hobj.foo_action_put function
foo.delete --> becomes a hobj.foo_action_delete function
foo.e4x --> becomes a hobj.foo_e4x xml object
foo.json --> becomes a hobj.foo_json js object
Then I also needed a mapping that would not be generally useful, but only interesting in the context of my experiments:
foo.control --> becomes a hobj.foo_control function with "view" as first argument
And on top of all that, I added some duplicates:
foo.view --> the same as foo.skin
foo.action --> the same as foo.hac
Maybe instead of adding direct built-in support for additional filename conventions to Helma, we could instead add functionality that would make it easy to script/configure such additional conventions as needed.
Besides a few new features, like the newly added res.resetBuffer() method and the ability to name type.properties files after their prototype, this update brings bug fixes in many different areas. See the
for the detailed list of fixes.
The new 1.6.1 version of Helma also includes an updated version of Rhino, with some E4X related fixes. The new packages now also include the
From the comments on
the slashdot posting
... tieTYT tells an anecdote about what AOL did to Netscape:
[...]one of the things they did was realize that pop-up blocking was one of the new cool things for browsers to have. But the marketing team stepped in and said, "Hold on just a second. We can't have the browser blocking OUR pop-ups." So they added rule to block all pop-ups except those that came from the netscape web page.
The netscape homepage happened to have a pop-up on it and of course, this is the default home page of the browser. When you initially ran netscape, first thing you saw was a pop-up and the page behind it claiming, "New Feature: pop-up blocker".
You can't escape bad karma. What AOL does to Netscape, Time Warner tends to do to AOL. We'll see.
Your email address:
The "Decentralize" Newsletter
Exchanging ideas for building a
decentralized fabric of society.
Making true democracy work on a larger
scale while decentralizing "everything",
benefiting from local diversity and
global synergies at the same time.