> If not MatplotLib, could this become the Processing (and by extension 
OpenFrameworks, LibCinder) of Julia?

That's definitely more the direction I'd like to take (although with a very 
different approach).
I hope that it will enable us to create a nice platform for accelerated 
data processing in general. With FireRender 
<https://github.com/JuliaGraphics/FireRender.jl> as a backend it might also 
appeal to artists more!


@Josef, that's exactly the other concern!
You might have noted that I've written a backend for Gadfly 
<http://www.glvisualize.com/examples/compose/>. While Gadfly is not that 
slow, it's written in a way that it's really hard to apply the 
optimizations needed to display large data-set and it's even worse for 
animations.


Am Freitag, 26. Februar 2016 23:11:02 UTC+1 schrieb Simon Danisch:
>
> Hi
>
> this is the first release of GLVisualize.jl 
> <https://github.com/JuliaGL/GLVisualize.jl>, a 2D/3D visualization 
> library completely written in Julia and OpenGL.
>
> You can find some crude documentation on glvisualize.com 
> <http://www.glvisualize.com/>.
> I hope to improve the examples and the documentation in the coming weeks.
> The biggest problem for most people right now will be a slightly flaky 
> camera and missing guides and labels.
> This is being worked on! If someone beats me to the guide/axis creation, 
> I'd be very happy. This could be a fun project to get started with 
> GLVisualize.
> Please feel free to open any issue concerning missing documentation, 
> discrepancies <http://www.dict.cc/englisch-deutsch/discrepancies.html> and 
> bugs!
>
> Relation to GLPlot <https://github.com/SimonDanisch/GLPlot.jl>:
> GLPlot is now a thin wrapper for GLVisualize with a focus on plotting. 
> Since I concentrated mostly on finishing GLVisualize, it's a reeally thin 
> wrapper. 
> It basically just forwards all calls to GLVisualize, and adds a 
> boundingbox around the objects. 
> In the future, it should offer some basic UI, automatic creation of 
> axis/labels, screenshots and an alternative API that is more familiar to 
> people that are coming from other plotting libraries (e.g. functions like 
> surf, contourf, patches).
> If anyone has specific plans on how this could look like don't hesitate to 
> open issues and PR's!
>
> Outlook:
> I'd like to make GLVisualize more independent of the rendering backend by 
> using some backend agnostic geometry 
> <https://github.com/JuliaGeometry/GeometryTypes.jl/issues/46> 
> representation.
> This will make it easier to integrate backends like FireRender 
> <https://github.com/JuliaGraphics/FireRender.jl>, WebGL, Vulkan 
> <https://github.com/JuliaGPU/Vulkan.jl/tree/api> (why Vulkan 
> <http://randomfantasies.com/2016/02/why-im-betting-on-vulkan-and-julia/>), 
> or some text based backends like PDF/SVG.
>
> Furthermore, I'd like to improve the performance and interaction 
> possibilities.
>
> I have to thank the Julia Group for supporting me :) It's a pleasure to be 
> a part of the Julia community!
>
> I'm looking forward to the great visualizations you'll create!
>
> Best,
> Simon Danisch
>

Reply via email to