This is great!
Chuck Lib
Lib Chuck
Lib chUCK
LICK
LUCK
CKlib
I think we should use git/github.
We could call it NORRIS...
-mike
On Thu, Jan 29, 2009 at 5:26 PM, Rogan Carr
I also thought a tamer name would be Lib chUCK or LUCK. Depends on what vibe we want to send :)
Rogan
On Thu, Jan 29, 2009 at 4:21 PM, Michael Heuer
wrote: Nice, that is available at all the hosting sites. Not sure I would try lick.com or lick.org from work though. :)
michael
Rogan Carr
wrote: Hmm. Lib ChucK => LiCK?
On Thu, Jan 29, 2009 at 2:30 PM, Michael Heuer
wrote: I would also love to get my code off my box and out where others can use (and improve!) it. Git is fine with me. I have accounts on github and gitorious . . . we would just need a decent project name.
michael
On Thu, Jan 29, 2009 at 2:24 PM, Rogan Carr
wrote: I'd be happy to contribute. I have tons of libraries that I use. What if we made a CVS-like repository like we're doing for the chuck source code? I think it's git? (I haven't set it up yet.)
Rogan
On Thu, Jan 29, 2009 at 2:05 PM, mike clemow
wrote: Hey all,
I just posted some very primitive (pun intended) Iterator classes for arrays of Ints and Floats. (http://wiki.cs.princeton.edu/index.php/Chuck/Lib) I find them useful in certain situations. (I think Michael Heuer has some superior ArrayList / Iterator code somewhere.)
Now, I'm well aware that most of you have personal class libraries that you use to do your thing with Chuck (I do too). There are also collections of code out there focusing on specific domains (SMELT, etc). I wonder about all this code and whether or not there might be some willingness to curate (for lack of better word) a collection of library-like code that we might post somewhere--in some package that isn't code posted on a wiki.
It's not really a class library... it's not really package... it's more like a distribution. But I think that it would be really helpful and fun. There's something about posting code to the wiki that really makes me cringe. Documentation of code is really what wiki's are good for. I think that a downloadable collection with wiki documentation would be ideal. I know that this couldn't be any sort of rigorously designed library, but we could all incrementally contribute to something like this, which I think would be really sweet.
Is anyone into this idea? I'd be glad to set up the chuck/lib page on the wiki to this end and organize, if people are into it.
-Mike
-- http://michaelclemow.com http://semiotech.org _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users