Nitrogen ++ ChicagoBoss , ChicagoBoss ++ Nitrogen

[radek.j...@gmail.com]

Hi all,

why not combine the dev efforts for Nitrogen and ChicagoBoss and blend them into a yet better alternative for web development in erlang?

(i know, i know that's how a) flaming wars start b) usually yet another halfready framework forks ... still this is erlang world with wiser ppl involved;)

I'm not sure how active the dev. of Nitrogen really is but some of its concepts (comet-process-pools, erlang => html mapping, the custom-controls/actions system f.e.) would be definitively great to see reused. On the other hand storage and template handling plus the funky reactive processes, well that's what makes ChicagoBoss shine imho.

(both have tons of other important features ofc.)

But I want it all in one framework! /sniff ;)

Was this discussed already? Opinions? Alternatives?  Any roadmaps?

Thanks in advance

cheers

Radek

[Evan Miller]

Hi Radek,

This is something I was interested in a while back, even came up with
a name I liked ("Boss in Space!!"). But while I like Nitrogen's Comet
capabilities, I don't think all the wf:wire stuff and style of HTML
generation will play well with CB. In general I dislike client-side
magic (JS generation etc), so I'm not too keen on doing a direct
integration with Nitrogen. But BossDB is an standalone project now
(https://github.com/evanmiller/boss_db), so you should be able to plug
it into Nitrogen pretty easily to get a nice storage layer with
Nitrogen's reactive capabilities.

--
Evan Miller
http://www.evanmiller.org/

[Ben G.]

I thought nitrogen was dead?

[Juan Jose Comellas]

BTW, I tried to used BossDB as a standalone project, but getting the compilation of models to happen automatically was a bit complicated. BossDB relies on the rebar plugin that is present in the ChicagoBoss project for this. Has anybody been able to use BossDB successfully in a separate project?

[Evan Miller]

I don't think BossDB relies on any CB rebar plug-ins; it's just that
the API is file-oriented, not project- or directory-oriented, so it
will take a little work to integrate into other projects. "Automatic"
compilation depends on your project. In CB it means that code is
recompiled on each request, but other projects might need
re-compilation according to some other logic. So you're on your own
for recompiling, but that's how it should be.

Evan

[rland...@gmail.com]

I should note that this was cross-posted to the Nitrogen list and that there's a parallel discussion going on there, including a reply from Jesse Gumm, Nitrogen's current maintainer:

https://groups.google.com/group/nitrogenweb/browse_thread/thread/59607c25e6b35e5b

Rodrigo

[Konstantin Nikiforov]

Nitrogen still alive?

> its concepts (comet-process-pools, erlang => html mapping, the
> custom-controls/actions system f.e.) would be definitively great to
> see reused

Its concepts - is a bicycle reinventing. Autogenerated JS calls is
one of the most ugly things i ever seen. For example, if
your site is not yet-another-home-page, and you want to use some
non-nintogen-js-code, you should write a new action module instead of
just writing this non-standart js into /static/js/my.js.


В Wed, 30 May 2012 11:28:16 -0700 (PDT)
radek.j...@gmail.com пишет:

[Florent Gallaire]

I played with Nitrogen this last days. It's an incredible, awesome work.
As said before, it's a very different of CB. It's not a clean MVC
framework but all about magical autogeneration of JS (Ajax and Comet).
For some people, as me, who absolutly doesn't want write JS, it's a must have !

Nitrogen hasn't routing system nor ORM so it could be really improved
by an integration in CB : routing system + BossDB and specialy the
asynchronous (as Nitrogen) BossNews.

The only integration to do is to switch from the Nitrogen template
language to erlydtl.

This could be a very interesting option to have the Nitrogen power
inside a clean CB integration (instead of a Nitrogen + webmachine +
BossDB + erlydtl hack).

Best regards

Florent

--
FLOSS Engineer & Lawyer

[Konstantin Nikiforov]

В Fri, 14 Sep 2012 14:53:15 +0200
Florent Gallaire <fgal...@gmail.com> пишет:

> webmachine

Too complex and overloaded for just a web-site.


> Nitrogen + webmachine + erlydtl

= zotonic


> magical autogeneration of JS

JS-autogeneration - is a toy. You can play with it, play a lot.
But when a concrete project come, you will need to write a
project-specific JS-code. And here is a problem: autogenerated JS is
too primitive for project and unmergeable with
yours-project-specific-js-code.

In zotonic case, you will write an so-called "actions" -
one-function erl-modules, that generates small pieces of js-code. This
is very ugly: pieces of js-code will be generated in undefined order,
somehow called on client, etc. In other side, web-developer MUST know
erlang to write JS-program (sic!).

No, thanks.