[erlang-questions] Developing killer / open source apps

Jon Watte <>
Sat Aug 6 01:21:59 CEST 2011


In my opinion, there exists exactly one user interface library: HTML5.
That library comes with the CSS3 way of skinning, and the Canvas way of
doing procedural drawing, and the JavaScript way of adding UI interaction.
We've used Firfox as our UI toolkit for years (using C++/Python as the app
languages), and it works great. These days, better choices probably are
Berkelium or Chromium or maybe plain WebKit.
A binding between JavaScript and Erlang, and/or between the HTML DOM and
Erlang messages, would be pretty cool for user-facing things.

Sincerely,

jw


--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.



On Fri, Aug 5, 2011 at 12:04 PM, Daniel Goertzen
<>wrote:

> How about interfacing Erlang to the Qt UI library?
>
> I don't mean a convential binding like wxErlang or PyQt, but components to
> facilitate message passing between Erlang and a Qt port program or NIF
> thread running a Qt message loop.
>
> Qt has relatively recently introduced QML, which is basically a fancy GUI
> designer that lets you incorporate javascript.  The application development
> model is that the GUI is written in QML/javascript, and the underlying
> application logic is in C++ (very Web 2.0-ish).  Now instead of writing C++,
> you have your QML/javascript talk to the "ErQt" object which passes messages
> to/from Erlang, and Erlang implements the application logic.
>
> Conceivably one could create a single Qt port executable, driver, or NIF
> library that could run any number of QML/javascript programs.  Creating a
> GUI for Erlang would involve using the native Qt tools for authoring QML and
> javascript, and implementing your comm protocol on both the javascript and
> Erlang sides.  Your QML/javascript GUI would run on the standard Qt port
> exectable...no additional C++ compiling required.
>
> Now QML is currently only available for mobile devices, but the Qt folks
> have stated that they will port it to the desktop and this will become the
> preferred way to develop desktop Qt apps.
>
> This project would likely involve more C++ than Erlang, so I'm not sure how
> you feel about that. ;)
>
> Cheers,
> Dan.
>
>
> On Mon, Aug 1, 2011 at 5:53 PM, Nick S <> wrote:
>
>> I have just finished implementing a "professional" Erlang server, and with
>> time and enthusiasm in hand, I would like to start working on something
>> personal.
>> I must say, it has been really fun writing apps in OTP and see it
>> processing millions of messages without ever crashing...!
>>
>> Would appreciate some new ideas, that would be useful to community :)
>>
>> - XMPP, AMQP etc are already in market!
>>
>> - Any audio/video processing layer?
>>
>> - Any telecom related...?
>>
>> - Some standard protocol implementation?
>>
>> - Something new for next generation...? (Buzz words... cloud computing
>> etc..)
>>
>> _______________________________________________
>> erlang-questions mailing list
>> 
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>>
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110805/1d47f170/attachment.html>


More information about the erlang-questions mailing list