Open GoogleCodeExporter opened 8 years ago
There're no real tutorials available as such, but all packages come with quite
a few
demos (some small, others bit more complex). I've also recently launched a blog
at
http://toxiclibs.org and been posting a few code snippets there too (and will
continue to do so, as time allows).
Original comment by toxmeister
on 7 Mar 2010 at 10:53
Well I downloaded a package and tried to run a .pde file and it said "toxi" was
missing. So even when I downloaded audioutils and tried to run examples I
immediately ran into issues. I'm sure you are busy with more important things,
but
it would be great to have something for beginners.
thanks
jason
Original comment by jva...@gmail.com
on 8 Mar 2010 at 4:12
Okay, point taken. But in that case I'd also recommend to read the supplied
README
file, which comes with each package. Toxiclibs is actually a collection of
different
libraries and even though none of them have any *external* dependencies, all
packages
rely on functionality provided by the toxiclibscore package, which you can also
download from the same list as audioutils et al.
I've made a note to give the architectural overview doc more priority, but hope
this
helps for now...
Original comment by toxmeister
on 8 Mar 2010 at 5:44
All dig into that as well. I think just showing a screencast from download to
run
would be an easy thing for you to do in the mean time.
I'll keep at is.
thanks
Original comment by jva...@gmail.com
on 8 Mar 2010 at 5:49
I guess that was my point. I did download the main tile "toxiclibs complete"
and was
still getting errors.
Original comment by jva...@gmail.com
on 14 Mar 2010 at 2:52
You need to make it MUCH more clear that the source from
hg clone http://hg.postspectacular.com/toxiclibs
does NOT contain the libraries. This should not be on the front page of the hg
site.
As a new user but experienced programmer, I was confused by the README.txt
files statement
'first drop the entire "toxiclibscore" folder into the "libraries" folder'
when of course there is no "toxiclibscore" folder. I just spent 1/2 hour on
this.
Original comment by rrm...@gmail.com
on 23 Nov 2010 at 6:04
Hi rrmutt,
sorry that wasn't clear to you and I'll add a development tutorial to the wiki
soon. The readme files you're referring to are bundled with the binary versions
and not meant for working with the source version. In future, please also DON'T
use this Google Code repo/issue tracker anymore, since over here is purely for
archiving reasons. The new wiki & issue tracker are all over here:
http://hg.postspectacular.com/toxiclibs
(See note over here too: http://code.google.com/p/toxiclibs/ )
Original comment by toxmeister
on 23 Nov 2010 at 11:08
Original issue reported on code.google.com by
jva...@gmail.com
on 7 Mar 2010 at 4:52