[Helma-user] accessing type.properties

[Breton Slivka]

FYI, I played with it for a little while, and it just needs one magic
little "bump"

Once you've written a new type.properties (via the setProperty
function), you need to call the update() function to make helma read it
in.  Example:

 app.getPrototype("Artwork").getDbMapping().update();

And then your dynamica changes will be seen by helma.


-----Original Message-----
From: helma-user-bounces at helma.org [mailto:helma-user-bounces at helma.org]
On Behalf Of Breton Slivka
Sent: Thursday, 3 July 2008 1:39 PM
To: Helma User Mailing List
Subject: Re: [Helma-user] accessing type.properties

It's a brand spanking new idea, so nothing is tested yet. Not by me at
least. But it certainly is worth looking more into this. I'll do what I
can. My associate Maks has also taken interest in my invention, so I
imagine he'll be looking into it as well.


 

-----Original Message-----
From: helma-user-bounces at helma.org [mailto:helma-user-bounces at helma.org]
On Behalf Of Joshua Paine
Sent: Thursday, 3 July 2008 1:32 PM
To: Helma User Mailing List
Subject: Re: [Helma-user] accessing type.properties

Breton Slivka wrote:
> You know what else you can do? You can set it programatically.

I saw those methods when I was investigating this, but didn't think to
try anything with them. (Maybe 'cause type.properties never really
bothered me?)

> I immediately set out to write an example of replacing type.properties

> with an Object Literal in javascript.

Is this tested and working? Does it work for all properties, even
_extends? Since helma will see and use changes to types while running
already, I guess this should work. Would love to hear from Hannes that
this won't cause lots of expensive cache invalidations that wouldn't
happen otherwise.

Really cool, though. And now that the possibility of controlling
type.properties from script appears, I begin to think of some things I'd
do with it.


I was going to reply with my discovery that you can put arbitrary named
values in type.properties, and if you start with _ and they're not magic
helma ones, they won't affect anything. So it'd be easy to specify the
order there--still a bit of repeating oneself, but all in one place at
least. This is a lot more interesting, though, and suggests ways to
optionally put more metadata into the [script version of] type
properties to get better forms for minimal effort.
_______________________________________________
Helma-user mailing list
Helma-user at helma.org
http://helma.org/mailman/listinfo/helma-user


Breton Slivka
Assistant Multimedia Systems Developer

National Gallery of Victoria
180 St Kilda Road Melbourne Vic 3004 Australia
Telephone: +61 3 8620 2348
Fax: +61 3 8620 2555
ngv.vic.gov.au

Keep informed of the latest NGV exhibitions, special events and programs
at The Ian Potter Centre: NGV Australia and NGV International by
subscribing to NGV at RT, the NGV's free e-newsletter.

DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for helma-user at helma.org. If you are
not the named addressee you should not disseminate, copy or alter this
email. WARNING: Although National Gallery of Victoria has taken
reasonable precautions to ensure no viruses are present in this email,
the organisation cannot accept responsibility for any loss or damage
arising from the use of this email or attachment.
_______________________________________________
Helma-user mailing list
Helma-user at helma.org
http://helma.org/mailman/listinfo/helma-user