Re: [chuck-dev] chuck-dev Digest, Vol 59, Issue 1

3 Feb 2012

      So, I made this change at one point:

https://github.com/clembie/mc_chuck_dev

Which was really a trivial little change involving a stubbed out but
unpopulated method in Object that allowed for a very powerful operation
when making generic handlers for things like UGens and other objects (see
example in README).  If I started mucking around with this stuff again, I'd
definitely prefer to fork from a git repo rather than CVS.

I've always wanted to be able to ask an object for the name of its super
class, for instance.

It would be really nice to get some documentation on the current
implementation of ChucK in order to facilitate this kind of community
experimentation.

Just dreaming here...

//mike

http://michaelclemow.com
http://semiotech.org

On Fri, Feb 3, 2012 at 9:55 AM, Remi Gillig  wrote:
...
This is truly great to see that many people interested ! I agree that
my own changes should not be in the main trunk but this is how I would
have done it if I forked the main chuck github project if there was
one. After that I could have made a pull request for my changes if the
original repository maintainers wanted to integrate my changes.
Anyway, this is all conditional and I would like some input from the
current SVN committers (Spencer Salazar and Ge Wang) if they could be
ready to make this change. Nowadays, all platforms supported by ChucK
have decent Git support and using Git in combination with GitHub
really can make wonders to an open source project like ChucK.
I hope this message will reach them. In the meantime, I will try to
keep my github in sync with the SVN one but I can't guarantee
anything.
As for contribution, if anyone is up for it, the current
CMakeLists.txt file only supports Windows (because I don't have
anything else setup) so it needs Linux and MacOSX support (at least
with default options). And maybe later add support for compilation
options (such as choose for HID support or not etc.).
Again, thanks for the feedback !
Cheers,
Remi Gillig.
...
Send chuck-dev mailing list submissions to
       chuck-dev@lists.cs.princeton.edu
To subscribe or unsubscribe via the World Wide Web, visit
       https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
or, via email, send a message with subject or body 'help' to
       chuck-dev-request@lists.cs.princeton.edu
You can reach the person managing the list at
       chuck-dev-owner@lists.cs.princeton.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of chuck-dev digest..."
Today's Topics:
1. ChucK GitHub (Remi Gillig)
  2. Re: ChucK GitHub (Colin Sullivan)
  3. Re: ChucK GitHub (Stephen Sinclair)
  4. Re: ChucK GitHub (Ricardo Fabbri)
  5. Re: ChucK GitHub (mike clemow)
---------- Forwarded message ----------
From: Remi Gillig 
To: chuck-dev@lists.cs.princeton.edu
Cc:
Date: Fri, 3 Feb 2012 00:50:54 +0100
Subject: [chuck-dev] ChucK GitHub
Hello all,
It's not that I don't like SVN but there are cool alternatives for
open source projects now. So I put ChucK on GitHub, I dream that you
would adopt this for future commits. The biggest advantage is the
"fork + pull" mechanic where someone can fork a project, do some
fixes, modifications, additions etc. and you can pull his changes into
the original repository. I know changing SCM is a big change in a
project but I had to go the mailing list archives to find the SVN URL
and I would love to see more contributions to ChucK.
Also a big change in many projects, is the change for the build
system. For Windows, the platform I'm originally interested in, I saw
that there were Visual 6 projects which is quite outdated. For the
benefit of everyone, I made a preliminary CMake build file which can
right now build ChucK on Visual Studio 2010 for example. CMake is a
bit like make but can generate projects for a number of platforms.
So, to summarize, I imported the SVN repository (revision 93) into
GitHub at this address : https://github.com/speps/chuck
My changes are already there, some minor fixes so that it builds on
Windows (without HID, DirectInput support was outdated, without OTF
server too. I did not want to be asked about Windows firewall for
ChucK). These options should be CMake options if anyone is up for it.
Anyway, I hope to hear from the developers community about a possible
switch over to GitHub which would be great for ChucK (I had to go the
mailing lists to realize that the latest version from the home page
dates from around 2009).
Cheers,
Remi Gillig.
---------- Forwarded message ----------
From: Colin Sullivan 
To: ChucK Developer Mailing List 
Cc:
Date: Thu, 2 Feb 2012 18:24:16 -0800
Subject: Re: [chuck-dev] ChucK GitHub
I am in support of this idea, but I think it may be a better idea to
keep the "master" branch representative of the official ChucK "trunk", and
keep any other commits in other branches until they are merged into ChucK
"officially".
Just my two cents.
----------
Colin Sullivan
On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig 
wrote:
...
Hello all,
It's not that I don't like SVN but there are cool alternatives for
open source projects now. So I put ChucK on GitHub, I dream that you
would adopt this for future commits. The biggest advantage is the
"fork + pull" mechanic where someone can fork a project, do some
fixes, modifications, additions etc. and you can pull his changes into
the original repository. I know changing SCM is a big change in a
project but I had to go the mailing list archives to find the SVN URL
and I would love to see more contributions to ChucK.
Also a big change in many projects, is the change for the build
system. For Windows, the platform I'm originally interested in, I saw
that there were Visual 6 projects which is quite outdated. For the
benefit of everyone, I made a preliminary CMake build file which can
right now build ChucK on Visual Studio 2010 for example. CMake is a
bit like make but can generate projects for a number of platforms.
So, to summarize, I imported the SVN repository (revision 93) into
GitHub at this address : https://github.com/speps/chuck
My changes are already there, some minor fixes so that it builds on
Windows (without HID, DirectInput support was outdated, without OTF
server too. I did not want to be asked about Windows firewall for
ChucK). These options should be CMake options if anyone is up for it.
Anyway, I hope to hear from the developers community about a possible
switch over to GitHub which would be great for ChucK (I had to go the
mailing lists to realize that the latest version from the home page
dates from around 2009).
Cheers,
Remi Gillig.
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
---------- Forwarded message ----------
From: Stephen Sinclair 
To: ChucK Developer Mailing List 
Cc:
Date: Thu, 2 Feb 2012 22:32:21 -0500
Subject: Re: [chuck-dev] ChucK GitHub
I had tried doing that quite a long time ago ;)
http://repo.or.cz/w/chuck-blob.git
But lost interest in keeping it up to date.. I hope you have more
luck!  Personally I think the project would benefit greatly by moving
completely to git.
Steve
On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan 
wrote:
...
I am in support of this idea, but I think it may be a better idea to
keep
the "master" branch representative of the official ChucK "trunk", and
keep
any other commits in other branches until they are merged into ChucK
"officially".
Just my two cents.
----------
Colin Sullivan
On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig 
wrote:
...
Hello all,
It's not that I don't like SVN but there are cool alternatives for
open source projects now. So I put ChucK on GitHub, I dream that you
would adopt this for future commits. The biggest advantage is the
"fork + pull" mechanic where someone can fork a project, do some
fixes, modifications, additions etc. and you can pull his changes into
the original repository. I know changing SCM is a big change in a
project but I had to go the mailing list archives to find the SVN URL
and I would love to see more contributions to ChucK.
Also a big change in many projects, is the change for the build
system. For Windows, the platform I'm originally interested in, I saw
that there were Visual 6 projects which is quite outdated. For the
benefit of everyone, I made a preliminary CMake build file which can
right now build ChucK on Visual Studio 2010 for example. CMake is a
bit like make but can generate projects for a number of platforms.
So, to summarize, I imported the SVN repository (revision 93) into
GitHub at this address : https://github.com/speps/chuck
My changes are already there, some minor fixes so that it builds on
Windows (without HID, DirectInput support was outdated, without OTF
server too. I did not want to be asked about Windows firewall for
ChucK). These options should be CMake options if anyone is up for it.
Anyway, I hope to hear from the developers community about a possible
switch over to GitHub which would be great for ChucK (I had to go the
mailing lists to realize that the latest version from the home page
dates from around 2009).
Cheers,
Remi Gillig.
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
---------- Forwarded message ----------
From: Ricardo Fabbri 
To: ChucK Developer Mailing List 
Cc:
Date: Fri, 3 Feb 2012 01:42:13 -0200
Subject: Re: [chuck-dev] ChucK GitHub
+1 to Git.
Ricardo Fabbri
--
Linux registered user #175401
www.lems.brown.edu/~rfabbri
pt.wikipedia.org/wiki/IPRJ
labmacambira.sf.net
On Fri, Feb 3, 2012 at 1:32 AM, Stephen Sinclair 
wrote:
...
I had tried doing that quite a long time ago ;)
http://repo.or.cz/w/chuck-blob.git
But lost interest in keeping it up to date.. I hope you have more
luck!  Personally I think the project would benefit greatly by moving
completely to git.
Steve
On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan 
wrote:
...
I am in support of this idea, but I think it may be a better idea to
keep
the "master" branch representative of the official ChucK "trunk", and
keep
any other commits in other branches until they are merged into ChucK
"officially".
Just my two cents.
----------
Colin Sullivan
On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig 
wrote:
...
Hello all,
It's not that I don't like SVN but there are cool alternatives for
open source projects now. So I put ChucK on GitHub, I dream that you
would adopt this for future commits. The biggest advantage is the
"fork + pull" mechanic where someone can fork a project, do some
fixes, modifications, additions etc. and you can pull his changes into
the original repository. I know changing SCM is a big change in a
project but I had to go the mailing list archives to find the SVN URL
and I would love to see more contributions to ChucK.
Also a big change in many projects, is the change for the build
system. For Windows, the platform I'm originally interested in, I saw
that there were Visual 6 projects which is quite outdated. For the
benefit of everyone, I made a preliminary CMake build file which can
right now build ChucK on Visual Studio 2010 for example. CMake is a
bit like make but can generate projects for a number of platforms.
So, to summarize, I imported the SVN repository (revision 93) into
GitHub at this address : https://github.com/speps/chuck
My changes are already there, some minor fixes so that it builds on
Windows (without HID, DirectInput support was outdated, without OTF
server too. I did not want to be asked about Windows firewall for
ChucK). These options should be CMake options if anyone is up for it.
Anyway, I hope to hear from the developers community about a possible
switch over to GitHub which would be great for ChucK (I had to go the
mailing lists to realize that the latest version from the home page
dates from around 2009).
Cheers,
Remi Gillig.
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
---------- Forwarded message ----------
From: mike clemow 
To: ChucK Developer Mailing List 
Cc:
Date: Fri, 3 Feb 2012 09:29:17 -0500
Subject: Re: [chuck-dev] ChucK GitHub
I'll throw my hat in the ring for for git.
I'm wondering how many users have personal changes to the main ChucK
branch...  I've dabbled in this realm before, but I'm curious what other
changes people have made.
//mike
http://michaelclemow.com
http://semiotech.org
On Thu, Feb 2, 2012 at 10:42 PM, Ricardo Fabbri 
wrote:
...
+1 to Git.
Ricardo Fabbri
--
Linux registered user #175401
www.lems.brown.edu/~rfabbri
pt.wikipedia.org/wiki/IPRJ
labmacambira.sf.net
On Fri, Feb 3, 2012 at 1:32 AM, Stephen Sinclair 
wrote:
...
...
I had tried doing that quite a long time ago ;)
http://repo.or.cz/w/chuck-blob.git
But lost interest in keeping it up to date.. I hope you have more
luck!  Personally I think the project would benefit greatly by moving
completely to git.
Steve
On Thu, Feb 2, 2012 at 9:24 PM, Colin Sullivan 
wrote:
...
I am in support of this idea, but I think it may be a better idea to
keep
the "master" branch representative of the official ChucK "trunk",
and keep
any other commits in other branches until they are merged into ChucK
"officially".
Just my two cents.
----------
Colin Sullivan
On Thu, Feb 2, 2012 at 3:50 PM, Remi Gillig 
wrote:
...
Hello all,
It's not that I don't like SVN but there are cool alternatives for
open source projects now. So I put ChucK on GitHub, I dream that you
would adopt this for future commits. The biggest advantage is the
"fork + pull" mechanic where someone can fork a project, do some
fixes, modifications, additions etc. and you can pull his changes
into
...
the original repository. I know changing SCM is a big change in a
project but I had to go the mailing list archives to find the SVN
URL
and I would love to see more contributions to ChucK.
Also a big change in many projects, is the change for the build
system. For Windows, the platform I'm originally interested in, I
saw
that there were Visual 6 projects which is quite outdated. For the
benefit of everyone, I made a preliminary CMake build file which can
right now build ChucK on Visual Studio 2010 for example. CMake is a
bit like make but can generate projects for a number of platforms.
So, to summarize, I imported the SVN repository (revision 93) into
GitHub at this address : https://github.com/speps/chuck
My changes are already there, some minor fixes so that it builds on
Windows (without HID, DirectInput support was outdated, without OTF
server too. I did not want to be asked about Windows firewall for
ChucK). These options should be CMake options if anyone is up for
it.
Anyway, I hope to hear from the developers community about a
...
...
...
...
...
switch over to GitHub which would be great for ChucK (I had to go
On 3 February 2012 15:29,  
wrote:
possible
the
...
...
...
...
...
mailing lists to realize that the latest version from the home page
dates from around 2009).
Cheers,
Remi Gillig.
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev

chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev
_______________________________________________
chuck-dev mailing list
chuck-dev@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev