Erlang gui tools

CRUD Operations. Object Modeling. C Sharp. Creating Objects. Reading Objects. Updating Objects. Deleting Objects. Content Types. Using MapReduce. Using Secondary Indexes. Using Commit Hooks. Creating Search Schemas. Searching with Data Types. Implementing a Document Store. Custom Extractors. Conflict Resolution. Data Types. Application Guide. Replication Properties. Write Once. Advanced MapReduce.

Cluster Metadata. Client Libraries. Backend API. Get Bucket Properties. Set Bucket Properties. Reset Bucket Properties. List Buckets. List Keys. Fetch Object. Store Object. Delete Object. List Resources. Search Query. Search Index Info. Fetch Search Index. Store Search Index. Delete Search Index. Fetch Search Schema. Store Search Schema. Link Walking. Take a user interface struct and compile it to the XML format understood by the Qt form builder.

TODO: make this automagic as a optional build step. Also, apply patches to produced proxy files. Skip to content. Star Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats 30 commits. Failed to load latest commit information. View code. Be aware that building UI can take some time. It takes around 1 minute on stock MacBook plus dependencies download for the first time.

Second time dependencies will be cached. To setup a Mnesia cluster, start several Erlang nodes with unique names e. Videos from those experiments were posted on YouTube. You can also start the tool as a regular Erlang release and connect to its console to debug the tool itself. We are recomending yarn for that. Now, application can be found at localhost and will be listening for messages from localhost where you have to have erlangpl running.

Although erlangpl-ui is written in React we belive in Elm's power. Do you expect the function to be called only a few times? Do you expect the function arguments to be large? Do you expect the process to exist, or will it be created after starting tracing? Do you expect the function not to crash?

Do you expect the process not to be scheduled out between two function calls? Do you expect the garbage collection to be quick? These are some questions that you can answer by using tracing, but if your expectations are far off from the truth, then the performance characteristics of tracing can cause some headaches.

If the function is called many times, instead of every once in a while, you need an automatic mechanism that stops the tracing before it causes any problems, or trace into a file with wrapping in place. In this case, you need to capture the crash by setting the right trace flags. These are considerations you should make before starting the trace, it might be your only chance for a rare case to collect evidence. You can also use tracing to understand the code better. It might not seem to be intuitive, but in this case, I still recommend you try to form and prove a theory of system behaviour.

Remember, Elixir and Erlang applications are built with resiliency in mind. Some errors are expected and not necessarily reported by the application. Catching these cases might be more difficult than anticipated.

There are many tracing tools out there. Yes, even for Elixir. The tracing facilities are built into the VM, so Elixir developers have a harder time to translate their code to the one the BEAM understands.

This is a price paid for the nice and efficient syntax, but in reality, it is not that far off. A good starting point is rexbug which is a wrapper for Redbug.

It not only gives a convenient interface to use with Elixir it translates the Elixir syntax to Erlang, and calls Redbug , but it also provides a lot of safeguards to protect us from making a big mistake and prevents the trace messages overloading the node.

It is also possible to gather the trace entries from more than one node if we have a distributed application. Imagine a cluster where a certain function is executed on a random node as a means of load balancing. You can log into one node, start the tracer there and see what is happening regardless of which node executes it. Although the matching syntax of rexbug is convenient and easy to use, sometimes it is necessary to fine tune the tracer for better performance or safer operation.

In this case, dbg comes to the rescue.