I would like to announce that I open sourced my hobby project, which I 
named Kite. Here is the demo <https://erkal.github.io/kite/>. Here is the 
source <https://github.com/erkal/kite>.

I am interested in visualising mathematical ideas, in particular, 
constructions, algorithms and games from the areas mathematical logic, 
combinatorics and theoretical computer science. 

My journey with Elm started 2 years ago with this question in Elm Discuss 
<https://groups.google.com/d/msg/elm-discuss/6nv1KkBs1a8/cCERU1eyYqIJ>.

I am not a developer and I am sure that my code has many problems. I would 
be very happy if you would take a look over the code and point out the 
wrong practices. 

I try to keep the number of libraries that I depend on as small as 
possible. I try to write my own small libraries which serve my own 
purposes. Some of them may be useful for your projects, too. There are two 
modules in Kite, of which I think that they may be useful in other contexts:

   - FileSystem 
   <https://github.com/erkal/kite/tree/master/kite-libraries/file-system> 
   can be used with any file type, not only for graphs. Say, you want to 
   implement something like the Atom text editor in Elm, you can use this 
   module.
   - PanAndZoom 
   <https://github.com/erkal/kite/tree/master/kite-libraries/svg-pan-and-zoom> 
   can be used for panning and zooming on SVG elements. I think that my code 
   organization for this module is bad. But I also couldn't find a better way. 
   I certainly need help here.

I am planning to add many functionalities to Kite. My gut feeling is that 
first I should simplify the basis infrastructure as much as possible before 
adding new features. Therefore, ideas about simplification are most 
welcome. But I would be happy for any kind comment or pull-request.

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to