In the case of pythreejs, the traitlets code is generated by a spec file,
which was then used to generate other backends.

For the general case, the plan is to generate a JSON spec from the
reference implementation or from the JS frontend and check that language
backends support all properties.

S.

On Thu, Sep 6, 2018, 04:22 Christian Schafmeister <[email protected]>
wrote:

> Thank you very much!  We will take a look at these.
>
> I'm especially curious how you mimicked traitlets and how you plan to keep
> these up to date.
> The JavaScript code for these libraries continues to develop - it's a
> moving target to keep up with them.
>
> Best,
>
> Christian Schafmeister,
> Professor, Chemistry Department
> Temple University
>
> On Monday, September 3, 2018 at 6:01:35 PM UTC-4, Sylvain Corlay wrote:
>>
>> Hi Christian,
>>
>> (Responding on mailing list for the record even though we also connected
>> through other channels).
>>
>> In terms of language backends for Jupyter widgets, I should mention
>>
>>  - *xwidgets*, the C++ implementation of the Jupyter widgets protocol,
>> which includes all the controls from ipywidgets. Backends for bqplot
>> (xplot), ipyleaflet (xleaflet) and pythreejs (xthreejs) were built upon
>> xwidgets. These widget libraries can be used with the C++ kernel.
>>
>>    Here are a few binder links for trying out these libraries:
>>
>>    xeus-cling:
>> https://mybinder.org/v2/gh/QuantStack/xeus-cling/stable?filepath=notebooks/xcpp.ipynb
>> (general demo of xeus-cling)
>>    xwidgets:
>> https://mybinder.org/v2/gh/QuantStack/xwidgets/stable?filepath=notebooks/xwidgets.ipynb
>>    xleaflet:
>> https://mybinder.org/v2/gh/QuantStack/xleaflet/stable?filepath=notebooks
>>    xplot:
>> https://mybinder.org/v2/gh/QuantStack/xplot/stable?filepath=notebooks
>>
>>  - I should also mention the *beakerx*
>> <https://github.com/twosigma/beakerx> project, which includes kernels
>> and widget backends for multiple languages of the JVM world.
>>
>>  - The *Interact.jl* <https://github.com/JuliaGizmos/Interact.jl> project
>> enables a lot of the controls of the base ipywidgets package for the Julia
>> programming language.
>>
>> Best,
>>
>> Sylvain
>>
>> On Monday, September 3, 2018 at 9:42:44 PM UTC+2, Christian Schafmeister
>> wrote:
>>>
>>>
>>> We've ported several jupyter widgets to Common Lisp so that we can use
>>> jupyter widgets from our kernel written in Common Lisp.
>>> This has involved translating about 15,000 lines of Python into Common
>>> Lisp - and dealing with translating traitlets and multithreaded code.
>>>
>>> It's going to be a maintenance burden for us - but we have the basic
>>> jupyter widgets, nglview, and bqplot widgets ported.
>>>
>>> I haven't been able to find any but are there any other languages that
>>> have made this investment? Julia? R? Ruby?
>>>
>>> If so - I'm curious to see how you approached it.
>>>
>>> Best,
>>>
>>> Christian Schafmeister,
>>> Professor, Chemistry Department
>>> Temple University.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/d1736add-7806-40d3-8140-2632e930062c%40googlegroups.com
> <https://groups.google.com/d/msgid/jupyter/d1736add-7806-40d3-8140-2632e930062c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAK%3DPhk4X5yR_PA53LXHNz%3DBJ%3D1-RCtakiPYivwebPUe-QBDG5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to