Ah ok, so you're not actually going for this project as a student? In that
case, how about suggesting the project on the ideas page
<https://github.com/JuliaLang/julialang.github.com/blob/master/soc/ideas-page.md>
?

On Mon, 14 Mar 2016 at 12:24 Uwe Fechner <[email protected]> wrote:

> Well, I am not an expert on QML, but as far as I understand, QML is mainly
> for writing GUIs, whereas
> the QT library contains a lot of functions for a lot of other tasks.
>
> What Julia is missing is mainly an easy to use GUI toolkit, and QML could
> play that role.
>
> Implementing a Julia - QML binding sound not so difficult as there is
> already a C binding.
>
> I do not understand the following sentence:
>
> "Being able to build Qt interface directly from Julia without the need of
>  the anaconda
> would be a great advantage for Julia users."
>
> If you would write a QML wrapper for the C binding, the C/ C++ code from
> the C wrapper
> would still need to be compiled included in the package in some way
> (binutils). So there
> would still be a dependency on C/C++ code (pre-compiled or not), that is
> always a little
> bit difficult to install and to maintain.
>
> Sounds like a great project!
>
>
> Uwe
>
>
>
>
> On Monday, March 14, 2016 at 11:04:02 AM UTC+1, Maurice Diamantini wrote:
>
>> My interest in QML/Qt5 is limited as a user which is looking for a
>> reliable multi-platform toolbox for building gui applications (with
>> native menu, open and save box...).
>>
>> There is the old designes Tk-8.6 which works everywere. But Julia
>> seams only to install Tk8.5.
>>
>> Gtk is not (yet) really multi-platform although it claims to.
>> It is very promising... for years, much like the D language before
>> Go and Julia appear.
>> Also there is no much example on the github page.
>>
>> So Qt5 would be the best solution (true multi-platform GUI, full feature
>> and very good documentation).
>> But Qt5 is a C++ code and even with the Cxx.jl package, I guess there
>> is much time before someone (Tom ;-) has time to build such an interface.
>> Also The library should be maintained.
>>
>> In the meantime, I thought a QML binding would be easier to do (not by
>> me :) and above all easier to maintained because most features are
>> available in QML and there has no need  (I think) to have its Julia
>> associated method.
>>
>> Can someone who know QML confirm that?
>> Also what feature are provided by Qt5 which are not available with QML?
>>
>> Regard,
>> -- Maurice
>>
>> Le 13 mars 2016 à 18:33, Mike Innes <[email protected]> a écrit :
>>
>> > Hey Maurice,
>> >
>> > Glad to see your interest in this project! I don't know a lot about
>> this area personally, but you might be able to learn more about the
>> approaches and issues involved by looking at Gtk.jl, which is a fairly
>> complete effort in a similar area. Other than that, a simple protoype might
>> help us to evaluate the idea.
>> >
>> > I'd be interested in your take on the relative pros and cons of
>> wrapping Qt5 wholesale vs. taking the QML approach you've described.
>> >
>> > Cheers,
>> > Mike
>> >
>>
> > On Fri, 11 Mar 2016 at 15:35 Maurice Diamantini <[email protected]>
>> wrote:
>> > While trying to find some Qt5 binding for Julia, I only found the Qt5
>> startup projet from Tom Breloff https://github.com/tbreloff/Qt5.jl which
>> is intended to bind the full feature from Qt5. This is a huge task and will
>> take some time.
>> >
>> > So I wonder if there is some interest for a QML binding which would
>> allows Julia code to display simple QML file (with callback to Julia
>> methods!).
>> >
>> > I just found a git repository about two QML library which could serve
>> as a basis  and as an example:
>> >
>> >
>> >         • https://github.com/seanchas116/libqmlbind A C library for
>> creating QML bindings for other languages easily
>> >         • https://github.com/seanchas116/ruby-qml a Ruby binding for
>> QML which uses libqmlbind
>> >
>> > Being able to build Qt interface directly from Julia without the need
>> of  the anaconda would be a great advantage for Julia users.
>> >
>> > That seems to be a true Julia GSOC candidate project (i.e. which could
>> not be affected to another language...)
>> >
>> > Regard,
>> >
>> > -- Maurice
>> >
>> >
>>
>>

Reply via email to