|
»
»
»
« Return to Thread: Helma NG now in main svn repository
Re: Helma NG now in main svn repository
by Hannes Wallnoefer-2
::
Rate this Message:
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
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
« Return to Thread: Helma NG now in main svn repository
| Free Forum Powered by Nabble | Forum Help |