Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Material to getting start #29

Open
nkint opened this issue Dec 4, 2015 · 3 comments
Open

Material to getting start #29

nkint opened this issue Dec 4, 2015 · 3 comments

Comments

@nkint
Copy link

nkint commented Dec 4, 2015

Hi!
Sorry, I understand that this is not the right place where to ask this.
I'm a big fan of processing.org and toxiclibs but I'm a little bit bored about java as a language itself.

So here is a question: is there any tutorial or getting started or any other kind of advice to use thi.ng?

@hlolli
Copy link

hlolli commented Apr 1, 2016

It would be nice if a slack channel was created for thi.ng. I'm also a beginner and want to learn more and have sometimes questions. But I just ask here then; for svg/path, how do I use is, as string or map?
(svg/path {:M "150 0" :L "75 200 225 200 Z"} {:fill "green"})
or
(svg/path "M 150 0 L 75 200 225 200 Z" {:fill "green"})

Neither seems to work.

@postspectacular
Copy link
Member

Hi @hlolli - I personally don't like slack due to its way too truncated history. we're using http://gitter.im/thi-ng/geom, which has unlimited history and is also linked to from the main readme... There're currently ~30 users and I try to reply as often as I can (mostly within a few hours).

As for your SVG question. The whole point of the SVG ns is to avoid having to work directly with the SVG internals. The fns provided all work seamlessly with the geom types and I'd really recommend reading the source code and looking at the various examples.

hth! (if not, see you on the chat :) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants