[erlang-questions] framework for building interface
Jesse Gumm
gumm@REDACTED
Fri Oct 30 20:55:31 CET 2015
Oops, forgot to reply all.
---------- Forwarded message ----------
From: "Jesse Gumm" <gumm@REDACTED>
Date: Oct 30, 2015 2:54 PM
Subject: Re: [erlang-questions] framework for building interface
To: "Wes James" <comptekki@REDACTED>
Cc:
Nitrogen, being a largely front-end framework, certainly sounds like it'd
be a fit.
Showing and hiding elements on the page is a matter of calling
wf:wire(#show{}) or wf:wire(#hide{}) in a postback event. You can see a
simple version of this here: http://nitrogenproject.com/demos/effects
Feel free to plunk around with it, and if you have any questions, let me
know.
-Jesse
P.S. Sorry for the terseness, I'm typing on my phone.
--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm
On Oct 30, 2015 2:00 PM, "Wes James" <comptekki@REDACTED> wrote:
> With my esysman app ( https://github.com/comptekki/esysman ) I use manual
> piecing of erlang binary/text chunks in the cowboy application that uses a
> .hrl for config info to building the interface.
>
> Anyone know of an erlang framework that would help in building web pages
> where rooms (one tab on the page then several other tabs for the other
> rooms) could be accessed with a click on a tabbed menu at the top and each
> room has computers laid out on the screen. Right now, like I said, I'm
> doing that in loops inside the cowboy app. I'd like cowboy to serve the
> interface, but some other framework to help build the interface, since I'm
> not that great at the html5 stuff. Would nitrogen work? html5 framework
> for erlang - I guess you'd call it??
>
> Thanks,
>
> -wes
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20151030/4cb943b2/attachment.htm>
More information about the erlang-questions
mailing list