@bryanjos: How I should start app?
My code:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<script src="Elixir.App.js"></script>
<style>
h1 { text-align: center; }
</style>
<title>Example</title>
</head>
<body>
<h1>
Example
</h1>
<script>
Elixir.start(Elixir.Example, []); // like that?
</script>
</body>
</html>
&Example.start/2 is what I have missed, thanks 
I have more questions:
Do you support defining classes? I’m interested in: custom elements - it’s important for me.
Can I change JavaScript file name?
Do you support module and method docs?
How I can access other methods? Do I need to implement &start/2 method for every module? I currently have this:
Elixir.start(Elixir.Example, []);
Elixir.Example.__exports.hello();
Logger:** (RuntimeError) Module Logger not found
lib/elixir_script/translator/lexical_scope.ex:361: ElixirScript.Translator.LexicalScope.check_for_module_existence/2
lib/elixir_script/translator/lexical_scope.ex:314: ElixirScript.Translator.LexicalScope.add_require/2
lib/elixir_script/translator.ex:469: ElixirScript.Translator.do_translate/2
(elixir) lib/enum.ex:1325: Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
(elixir) lib/enum.ex:1325: Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
lib/elixir_script/translator/kernel/special_forms/block.ex:7: ElixirScript.Translator.Block.make_block/2
lib/elixir_script/translator/kernel/defmodule.ex:88: ElixirScript.Translator.Defmodule.translate_body/2
lib/elixir_script/translator/kernel/defmodule.ex:50: ElixirScript.Translator.Defmodule.process_module/3
There is no support for defining classes and that’s on purpose. But if someone can find an idiomatic Elixir way to add classes I am all for it. Even though Elixirscript can’t create classes, it can instantiate them with JS.new/2. I hardly ever use classes in JavaScript so it’s a low priority for me.
You can’t change the output name now, but it is something that can be allowed now. I can make an issue to update the output parameter to allow for that.
Does not support method and module docs. I don’t see a reason to since this is a compile target.
start/2 is meant to be the “main” or entrypoint of your Elixirscript application. If you want to other modules outside of the Elixirscript scope then yes you would have to define start on them. or call __load(Elixir) directly or the module to load it and get an object returned with the functions defined on it.
Not all of the standard library is supported yet, but Logger may be a simple one to add. I’ll make an issue for it.
Imagine that you prefer to use Elixir, but want to create a JavaScript library. As you know API docs are really useful for other developers.
The problem is that you already have it in docs in section called Completed Modules:
Completed Modules
so I thought that I can use it already. What about create a Logger backend - is it a good way for you?
Good point 
I’ll update the docs. There used to be an implementation in the earlier days but since I started implementing the standard library in elixir I never added one back.
You could write a simple Macro that creates Module with some info, for example in module attributes.
defjsclass MyModuleName, :main do
# shortcut for define variable getter
defjsvariable :variable_name, :get
# shortcut for define another variable getter and setter
defjsvariable :another_variable_name, :both
def main do
# ...
end
end
that should be visible like:
defmodule MyModuleName do
@elixir_script_class_constructor_method_name :main
@elixir_script_is_class true
# shortcut for define variable getter
defjsvariable :variable_name, :get
# shortcut for define another variable getter and setter
defjsvariable :another_variable_name, :both
def main do
# ...
end
end
Haha, this one is good. However after longer time working with Elixir, for me there is not such need to want OOP back 