This is very intriguing!
How would you recommend incorporating a (pseudo?) database into an
OpenBD Local package?
Al
On 12/19/2011 2:01 AM, Alan Williamson (aw2.0 cloud experts) wrote:
Good morning,
We're excited to make available an exciting new way to package up your
OpenBD apps. We are calling it
OpenBD Local
You can read more about it here and download it:
http://openbd.org/local/
This is a new way for you to package up your OpenBD Web App and have
it run locally on a users desktop, complete with a system-tray icon
for launching it. It ships with everything your users need,
including an embedded JRE and Jetty. You just supply your OpenBD web
app.
Our dear friend Mats has been testing for us and gone much further and
developed a complete installation script for Windows using the
Nullsoft Scriptable package. You can read more about how to do this
at the OpenBD Manual prepared by Mats
http://openbd.org/manual/?/local_nsis
So what does this mean?
In a nutshell, it allows you to package up webapps that maybe are
filling a specific niche or requirement. Because you can restrict you
webapp to just the local desktop machine you can do things for the
user that wouldn't normally be possible from a remote server. For
example, imagine building a system to index all specific files on a
users desktop and offer up a rich webapp to manage this (MP3 player
comes to mind). Another use is specific utilities that you may
want to give certain users to run.
Or even better, a very quick way for people to try our yourself
beautiful software without all the hassle of installing Java, Jetty
and OpenBD. Just download and run.
We believe in getting OpenBD into the hands of as many people as
possible and negating all the headaches normally associated with such
a deployment.
Let us know what you think,
alan
--
online documentation: http://openbd.org/manual/
google+ hints/tips: https://plus.google.com/115990347459711259462
http://groups.google.com/group/openbd?hl=en
