Helma NG now in main svn repository

[Hannes Wallnoefer-2]

Hi all,

I just imported the last revision of Helma NG into a new top level
directory in the Helma main svn:

svn:
https://dev.helma.org/svn/helma-ng/trunk/
trac:
https://dev.helma.org/trac/helma/browser/helma-ng/trunk

Unfortunately, svn switch does not seem to be able to change the host
part of a svn url, so I guess you'll have to check out a fresh copy.

Btw, check out the new skin rendering stuff in the demo app. I really
like the skin inheritance thing - it really unleashes the power of
subskins. Would be great to get some feedback on this.

best,
Hannes
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev

[Maksim Lin-3]

On 4/29/08, Maksim Lin <maks@...> wrote:

> Hi Hannes,
>
> The helma-ng development looks very interesting, good to see it up and
> running again. Even though I'm originally a Java programmer, I think
> being able to implement much more of helma within js will hopefully open
> it up to a bigger dev community of contributors.
>
> The new skin "inheritance" matches the development pattern I've been
> using for a while now: having "wrapper" skins contain a macro for
> res.data.body into which I would put the results of renderAsString for
> different pages. S thumbs up from me with for that.
> I'm not likely to be implementing an alternative rendering framework, so
>  I can't comment much on the new callback approach, but from a user
> point of view, I'm very happy to see that the new implementation seems
> backward compatible with current skin usage.
> And with subskins, personally I havn't used subskins that much so far as
> I think they may be a bit confusing for non-programmers but I can see
> how they work well with skin inheritance as you hav ein the demo code.
>
> For my part, I'm having a go at a simple persistence layer for NG using
> the JSAdapter and "almsot native" JS object rather then host HopObjects,
> so having the automatic JSAdapter for moduel scopes is proving handy
> though I'm still working out some problems with my code so I dont have
> anything to post yet.
>
> One other thing is that I've been using current helma/File.js module
> quite well with NG (just by removing the "global.helma..." code check at
> the start and  "helma.lib..." and the end of the file so perhaps it
> could be added to ng's svn repo next? as its a rather handy module :-)
>
> thanks,
> Maks.
>
>

_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev

[Hannes Wallnoefer-2]

Hi Maks,

thanks for the feedback.

2008/4/30 Maksim Lin <maks@...>:
> On 4/29/08, Maksim Lin <maks@...> wrote:
>  > Hi Hannes,
>  >
>  > The helma-ng development looks very interesting, good to see it up and
>  > running again. Even though I'm originally a Java programmer, I think
>  > being able to implement much more of helma within js will hopefully open
>  > it up to a bigger dev community of contributors.

Yes, that's one of the positive effects I expect. One other really
nice thing is that writing modules is much more fluid than
implementing stuff in java - you just edit, reload, and the change is
there.

>  > The new skin "inheritance" matches the development pattern I've been
>  > using for a while now: having "wrapper" skins contain a macro for
>  > res.data.body into which I would put the results of renderAsString for
>  > different pages. S thumbs up from me with for that.
>  > I'm not likely to be implementing an alternative rendering framework, so
>  >  I can't comment much on the new callback approach, but from a user
>  > point of view, I'm very happy to see that the new implementation seems
>  > backward compatible with current skin usage.

I don't really think it is backwards compatible, actually - at least
not 100%. But it's not really meant to be a final API, more a working
prototype.

>  > And with subskins, personally I havn't used subskins that much so far as
>  > I think they may be a bit confusing for non-programmers but I can see
>  > how they work well with skin inheritance as you hav ein the demo code.

I think the skin extension stuff is really nice, and it complements
subskins perfectly. Finally a simple way to deal with the page/content
stuff.

One thing that's still missing in ng is macro filter support. <% foo | bar %>.

>  > For my part, I'm having a go at a simple persistence layer for NG using
>  > the JSAdapter and "almsot native" JS object rather then host HopObjects,
>  > so having the automatic JSAdapter for moduel scopes is proving handy
>  > though I'm still working out some problems with my code so I dont have
>  > anything to post yet.
>  >
>  > One other thing is that I've been using current helma/File.js module
>  > quite well with NG (just by removing the "global.helma..." code check at
>  > the start and  "helma.lib..." and the end of the file so perhaps it
>  > could be added to ng's svn repo next? as its a rather handy module :-)

Ok, I'll add it next. Generally, It's quite simple to move modules
from helma 1 to ng. Mostly the only thing required is to remove the
namespace code and convert the import statements.

best,
hannes

>  > thanks,
>  > Maks.
>  >
>  >
>  _______________________________________________
>  Helma-dev mailing list
>  Helma-dev@...
>  http://helma.org/mailman/listinfo/helma-dev
>
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev