Erlang term explorer. Pastebin type app which displays terms of any complexity straight from your erlang shell in web browser. No external deps (inets only).
CSS
82
1 commits
updated Oct 8, 2014
This app was created to fill the void in the data visualisation area. And to help you follow "know your data" paradigm. Basically it shows you your data in web browser via webserver listening to localhost.
tx:show(Term) and tx:show(Term, Title)
tx:redbug(Spec) and tx:redbug(Spec, Options)
redbug:start and capture events output, then store it in a
regular way as a browsable term.Add https://github.com/kvakvs/tx as your application dependency or download it
and compile manually. Run your application as usual. When you need to see things,
call tx:show(Term). in Erlang console or insert call to tx:show where you
need it. URL is returned from tx:show, and Erlang shell will display it. NOTE:
return value won't be displayed if you call tx:show in your code.
Application tx will be started automatically and web server will be opened on
your first call of tx:show/1. Alternatively run tx manually via: tx:start()..
Default port is 20000, and default host is localhost. You can set port to 0 in
tx.app.src, to start on random available port.
Simple demo: tx:show(application:which_applications()).
All sorts of terms in one: tx:show([<<123,32,1>>, <<1:1, 3:5, 45:7>>, <<"test\ttest">>, 123, 123.321, make_ref(), self(), erlang:ports(), fun()->ok end, {fun erlang:ports/0, 'test', "test"}, [{test, value1}, {fgsfds, 1000}], [1,2,3|{4, [5|test]}]]).
R17 maps example: tx:show(#{k1 => "test", k2 => 'test', k3 => 123, k4 => <<"test">>}).
Possible things to add of improve
1 commits
CSS
68.7%
Erlang
27.5%
JavaScript
3.8%
Erlang term explorer. Pastebin type app which displays terms of any complexity straight from your erlang shell in web browser. No external deps (inets only).
CSS
82
1 commits
updated Oct 8, 2014
This app was created to fill the void in the data visualisation area. And to help you follow "know your data" paradigm. Basically it shows you your data in web browser via webserver listening to localhost.
tx:show(Term) and tx:show(Term, Title)
tx:redbug(Spec) and tx:redbug(Spec, Options)
redbug:start and capture events output, then store it in a
regular way as a browsable term.Add https://github.com/kvakvs/tx as your application dependency or download it
and compile manually. Run your application as usual. When you need to see things,
call tx:show(Term). in Erlang console or insert call to tx:show where you
need it. URL is returned from tx:show, and Erlang shell will display it. NOTE:
return value won't be displayed if you call tx:show in your code.
Application tx will be started automatically and web server will be opened on
your first call of tx:show/1. Alternatively run tx manually via: tx:start()..
Default port is 20000, and default host is localhost. You can set port to 0 in
tx.app.src, to start on random available port.
Simple demo: tx:show(application:which_applications()).
All sorts of terms in one: tx:show([<<123,32,1>>, <<1:1, 3:5, 45:7>>, <<"test\ttest">>, 123, 123.321, make_ref(), self(), erlang:ports(), fun()->ok end, {fun erlang:ports/0, 'test', "test"}, [{test, value1}, {fgsfds, 1000}], [1,2,3|{4, [5|test]}]]).
R17 maps example: tx:show(#{k1 => "test", k2 => 'test', k3 => 123, k4 => <<"test">>}).
Possible things to add of improve
1 commits
CSS
68.7%
Erlang
27.5%
JavaScript
3.8%