headers
Hannes Wallnoefer | 1 Jun 10:44
Picon
Gravatar

Re: Multiple embedded databases per helma app

Hi Chris,

On 5/31/05, Chris Zumbrunn <chris <at> zumbrunn.com> wrote:
> Is there by any chance any way to provide a helma app with more than
> one embedded db?

No, this is currently not possible.

> Wouldn't that be nice?

Maybe, but there are some obstacles. For instance, it is currently not
possible to reference a HopObject across embedded DBs for the reason
that DB keuys do not carry any information as to which db they belong
to. Maybe this is a bug that should be fixed.

Hannes

> chris <at> czv.com  +41 329 41 41 41
> Chris Zumbrunn Ventures - http://www.czv.com/
> Internet Application Technology - Reduced to the Maximum
> 
>
Permalink | Reply | 2 comments |
headers
Chris Zumbrunn | 1 Jun 11:58
Gravatar

Re: Re: Multiple embedded databases per helma app

On Jun 1, 2005, at 10:44 AM, Hannes Wallnoefer wrote:

> Hi Chris,
>
> On 5/31/05, Chris Zumbrunn <chris <at> zumbrunn.com> wrote:
>> Is there by any chance any way to provide a helma app with more than
>> one embedded db?
>
> No, this is currently not possible.
>
>> Wouldn't that be nice?
>
> Maybe, but there are some obstacles. For instance, it is currently not
> possible to reference a HopObject across embedded DBs for the reason
> that DB keuys do not carry any information as to which db they belong
> to. Maybe this is a bug that should be fixed.

Just brainstorming....

root2 = new XmlDB('db/myotherdb'); // returns the root object of the 
second db
root.add(root2); // adds the root object of the second db as a child of 
the default root object

If I understand you correctly, a problem is that storageName in DbKey 
is currently always null for the embedded db and helma would need a 
"DbMapping" not just for the relational databases? Also, I guess 
currently helma checks whether storageName is null in order to  
differentiate between embedded and relational, which wouldn't work 
anymore.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Chris Zumbrunn | 1 Jun 12:08
Gravatar

Re: Re: Multiple embedded databases per helma app

On Jun 1, 2005, at 11:58 AM, Chris Zumbrunn wrote:

> Just brainstorming....
>
> root2 = new XmlDB('db/myotherdb'); // returns the root object of the 
> second db
> root.add(root2); // adds the root object of the second db as a child 
> of the default root object

root._id and root2._id would both be 0.

(...still just brainstorming, obviously ;)

/czv
Permalink | Reply | 0 comments |
headers
Chris Zumbrunn | 13 Jun 16:47
Gravatar

Baby steps towards Javascript heaven

Just wanted to give a quick update regarding my Mocha/Helma plans...

Since I've shared some thoughts about using Helma as the base for Mocha 
projects over a year ago, I've ported parts of my existing Mocha Engine 
to Helma and gained some real world experience with how the two 
concepts fit together. I learned a lot about "the Helma way" of doing 
things (I hope), which was an overwhelmingly positive experience.

While I at first implemented things the Mocha way, I often later 
realized that there already was an elegant Helma way of solving the 
same problem. For the most part I now appreciate even those aspects of 
Helma that I originally saw more critical.

As a result of that evolution, the ideas for a Helma based Mocha 
framework changed quite a lot. First the framework grew to resemble the 
old Mocha engine, then I experimented with "the Helma way" and trimmed 
it down until there was hardly any code left. I now started with a new 
approach ("OpenMocha") that I believe to be an interesting blend 
between "the Mocha way" and "the Helma way". I'll release a first build 
as soon as I have the core concept in a working state.

Due to the Ajax-hype and the resulting openness of web developers 
towards more complex javascript coding, there might be renewed interest 
in "our way" of building web apps. When I imagine a blend of 
Helma/OpenMocha/Chopper[1]/Prototype[2], I see the line between 
server-side and client-side fading and I see "Javascript heaven".

I'm not sure how Gobi fits into this picture, since Gobi is less about 
putting a framework in Javascripters hands and more about putting the 
power of Helma in the hands of the Non-Javascripters. Does this
(Continue reading)

Permalink | Reply | 4 comments |
headers
Hannes Wallnoefer | 16 Jun 11:40
Picon
Gravatar

Re: Baby steps towards Javascript heaven

Hi Chris,

On 6/13/05, Chris Zumbrunn <chris <at> zumbrunn.com> wrote:
> Just wanted to give a quick update regarding my Mocha/Helma plans...
> 
> Since I've shared some thoughts about using Helma as the base for Mocha
> projects over a year ago, I've ported parts of my existing Mocha Engine
> to Helma and gained some real world experience with how the two
> concepts fit together. I learned a lot about "the Helma way" of doing
> things (I hope), which was an overwhelmingly positive experience.
> 
> While I at first implemented things the Mocha way, I often later
> realized that there already was an elegant Helma way of solving the
> same problem. For the most part I now appreciate even those aspects of
> Helma that I originally saw more critical.
> 
> As a result of that evolution, the ideas for a Helma based Mocha
> framework changed quite a lot. First the framework grew to resemble the
> old Mocha engine, then I experimented with "the Helma way" and trimmed
> it down until there was hardly any code left. I now started with a new
> approach ("OpenMocha") that I believe to be an interesting blend
> between "the Mocha way" and "the Helma way". I'll release a first build
> as soon as I have the core concept in a working state.

That sounds all very interesting. Looking forward to see OpenMocha!

> Due to the Ajax-hype and the resulting openness of web developers
> towards more complex javascript coding, there might be renewed interest
> in "our way" of building web apps. When I imagine a blend of
> Helma/OpenMocha/Chopper[1]/Prototype[2], I see the line between
(Continue reading)

Permalink | Reply | 3 comments |
headers
Chris Zumbrunn | 16 Jun 12:05
Gravatar

Re: Baby steps towards Javascript heaven

On Jun 16, 2005, at 11:40 AM, Hannes Wallnoefer wrote:

>> Due to the Ajax-hype and the resulting openness of web developers
>> towards more complex javascript coding, there might be renewed 
>> interest
>> in "our way" of building web apps. When I imagine a blend of
>> Helma/OpenMocha/Chopper[1]/Prototype[2], I see the line between
>> server-side and client-side fading and I see "Javascript heaven".
>
> I have a similar view on this. I didn't know Prototype. Looks
> interesting. How is this related to Ruby or Ruby on Rails?

From: http://dev.conio.net/repos/prototype/doc/files/README.html

"Prototype is a Javascript library that aims to ease development of 
dynamic web applications. Its development is driven heavily by the Ruby 
on Rails framework, but it can be used in any environment."

/czv
Permalink | Reply | 2 comments |
headers
Chris Zumbrunn | 16 Jun 12:08
Gravatar

Inheriting and overriding Mocha Objects based on prototypes vs aspects

One of the core concepts of OpenMocha is that you can override 
"business logic" and skins at any point in your content hierarchy. I 
currently have code in OpenMocha that takes care of this based on 
inheriting object properties. Nicer and "more Helma like" would be if 
this could be based on the prototype inheritance instead.  I wonder if 
there already is a way in Helma to do this that I am not thinking of.

For example...

http://mymochasite.com/page1/page2/page3/edit

Let's say I want to override the edit action (or certain subroutines 
called by the action) of page3 and optionally of any pages page3 
contains .

I could dynamically generate a new prototype "Page_page3" that extends 
Page and convert page3 to the new prototype and optionally all the 
children it contains as well, unless these children already have a 
custom prototype, in which case they would be changed to extend from 
"Page_page3" instead of from "Page".

Alternatively to the prototype based approach, I could implement this 
using Aspects, which is what I'm favoring right now and I'm playing 
with the Aspects related code that was added last year.

Any thoughts, ideas? Am I duplicating something that already exists in 
the present Helma universe?

chris <at> czv.com  +41 329 41 41 41
Chris Zumbrunn Ventures - http://www.czv.com/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hannes Wallnoefer | 16 Jun 12:54
Picon
Gravatar

Re: Baby steps towards Javascript heaven

On 6/16/05, Chris Zumbrunn <chris <at> zumbrunn.com> wrote:
> On Jun 16, 2005, at 11:40 AM, Hannes Wallnoefer wrote:
> 
> >> Due to the Ajax-hype and the resulting openness of web developers
> >> towards more complex javascript coding, there might be renewed
> >> interest
> >> in "our way" of building web apps. When I imagine a blend of
> >> Helma/OpenMocha/Chopper[1]/Prototype[2], I see the line between
> >> server-side and client-side fading and I see "Javascript heaven".
> >
> > I have a similar view on this. I didn't know Prototype. Looks
> > interesting. How is this related to Ruby or Ruby on Rails?
> 
> From: http://dev.conio.net/repos/prototype/doc/files/README.html
> 
> "Prototype is a Javascript library that aims to ease development of
> dynamic web applications. Its development is driven heavily by the Ruby
> on Rails framework, but it can be used in any environment."

Surfing your site, I just came across Rico which looks even better to
me (well, it has demos online so you can actually see what it does):

http://openrico.org/home.page
http://openrico.org/demos.page
http://openrico.org/about.page

Hannes

> /czv
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Chris Zumbrunn | 16 Jun 13:11
Gravatar

Re: Baby steps towards Javascript heaven

On Jun 16, 2005, at 12:54 PM, Hannes Wallnoefer wrote:

> On 6/16/05, Chris Zumbrunn <chris <at> zumbrunn.com> wrote:
>> On Jun 16, 2005, at 11:40 AM, Hannes Wallnoefer wrote:
>>
>>>> Due to the Ajax-hype and the resulting openness of web developers
>>>> towards more complex javascript coding, there might be renewed
>>>> interest
>>>> in "our way" of building web apps. When I imagine a blend of
>>>> Helma/OpenMocha/Chopper[1]/Prototype[2], I see the line between
>>>> server-side and client-side fading and I see "Javascript heaven".
>>>
>>> I have a similar view on this. I didn't know Prototype. Looks
>>> interesting. How is this related to Ruby or Ruby on Rails?
>>
>> From: http://dev.conio.net/repos/prototype/doc/files/README.html
>>
>> "Prototype is a Javascript library that aims to ease development of
>> dynamic web applications. Its development is driven heavily by the 
>> Ruby
>> on Rails framework, but it can be used in any environment."
>
> Surfing your site, I just came across Rico which looks even better to
> me (well, it has demos online so you can actually see what it does):
>
> http://openrico.org/home.page
> http://openrico.org/demos.page
> http://openrico.org/about.page

Yes, I'm including Rico in OpenMocha, actually. Within the OpenMocha
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Alexandrow | 21 Jun 16:43
Picon

troubles with jimi image processing

hi list,

i currently encounter two problems when trying to rotate an image in helma 
(they might be related to each other, but i can't tell).

1st)

function test_action() {
   var f = new Helma.File("d:\\processed.jpg");
   if (f.exists()) f.remove();
   f.close();

   var img = new Helma.Image("d:\\test.jpg");
   var filters = Packages.com.sun.jimi.core.filters;
   var rotator = new filters.Rotate(45);
   var processed = new Helma.Image(img, rotator);
   processed.saveAs("d:\\processed.jpg");
   res.write("done");
}

the above code is almost identical to an example i found on helma.org 
(http://helma.org/stories/47854/). the problem here is, that 
Helma.Image(img, rotator) won't take img as parameter and throws 
"java.lang.RuntimeException: Error loading image".

2nd)

function jimi_action() {
   var f = new Helma.File("d:\\processed.jpg");
   if (f.exists()) f.remove();
(Continue reading)

Permalink | Reply | 3 comments |

Gmane