All,
Pd-L2ork is now available both as a tarball and via git: http://l2ork.music.vt.edu/main/?page_id=56 https://github.com/pd-l2ork/
Testers/contributors are as always most appreciated.
NB: Pd-l2ork is currently Linux-only although this may change down the road.
Some of the recent changes include:
2011-10-25 *Fixed a monster segfault bug that occurred when using toggling graph-on-parent and cut in succession (usually in combination with undo/redo). 2011-10-24 *Added undo/redo for creating new objects 2011-10-22 *Implemented universal copy/paste 2011-10-21 *Fixed gop enable/disable segfault (when doing so on an empty canvas) *Added undo for the canvas properties 2011-08-24 *Fixed gop redrawing issue when passed coords message via script *Fixed pack not converting null lists into bangs
Coming up soon: *graph-on-parent enable/disable does not activate undo/redo on the parent window (or the gop-ed patch unless it is open) *Infinite undo *Ability to draw red GOP rectangle *Universal copy/paste should also resize the canvas as per original script? *Consider making hslider and vslider capable of doing int data
Cheers!
Ivica Ico Bukvic, D.M.A. Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Director, L2Ork Linux Laptop Orchestra Assistant Director, CCTAD Virginia Tech Dept. of Music - 0240 Blacksburg, VA 24061 (540) 231-6139 (540) 231-5034 (fax) ico@vt.edu http://www.music.vt.edu/faculty/bukvic/
On Wed, 2011-10-26 at 09:42 -0400, Ivica Ico Bukvic wrote:
All,
Pd-L2ork is now available both as a tarball and via git: http://l2ork.music.vt.edu/main/?page_id=56 https://github.com/pd-l2ork/
Is this based on Pd 0.43 ?
Roman
On Oct 26, 2011, at 10:01 AM, Roman Haefeli wrote:
On Wed, 2011-10-26 at 09:42 -0400, Ivica Ico Bukvic wrote:
All,
Pd-L2ork is now available both as a tarball and via git: http://l2ork.music.vt.edu/main/?page_id=56 https://github.com/pd-l2ork/
Is this based on Pd 0.43 ?
Seems to be a mix, its got the 0.43 Tcl, but the 0.42 header:
https://github.com/pd-l2ork/pd/blob/master/src/m_pd.h
.hc
Access to computers should be unlimited and total. - the hacker ethic
Is this based on Pd 0.43 ?
Seems to be a mix, its got the 0.43 Tcl, but the 0.42 header:
https://github.com/pd-l2ork/pd/blob/master/src/m_pd.h
.hc
Indeed, it is a mix. Some of our implementations (e.g. magicglass) got ported by Hans and some of upstream was backported. I feel like 0.43 Tcl code is not yet vetted enough for me to move in that direction (we're stuck in this in-between 0.42 and 0.43 version because a lot of time was spent squashing serious bugs, many of which appear to be present in the 0.43 branch). That said, pd-l2ork has close to 200 features and bugfixes that are unique to it. For more info, please see the Changelog.
http://l2ork.music.vt.edu/data/pd/Changelog
Best wishes,
Ico
On Oct 26, 2011, at 2:03 PM, Ivica Ico Bukvic wrote:
Is this based on Pd 0.43 ?
Seems to be a mix, its got the 0.43 Tcl, but the 0.42 header:
https://github.com/pd-l2ork/pd/blob/master/src/m_pd.h
.hc
Indeed, it is a mix. Some of our implementations (e.g. magicglass)
got ported by Hans and some of upstream was backported. I feel like
0.43 Tcl code is not yet vetted enough for me to move in that
direction (we're stuck in this in-between 0.42 and 0.43 version
because a lot of time was spent squashing serious bugs, many of
which appear to be present in the 0.43 branch). That said, pd-l2ork
has close to 200 features and bugfixes that are unique to it. For
more info, please see the Changelog.
I'd love to be able to include bugfixes from pd-l2ork. I looked thru
the code and I can't really find what changes belong to what Changelog
items. Can you point me towards the code related to these Changelog
items, and expand on what they do, if you can? Then I can work on
including them in Pd-extended:
*Implemented universal copy/paste
*Fixed gop redrawing issue when passed coords message via script
*finally discovered the root of all double-entry bugs (fingers
crossed) and reverted all other previous workarounds for this problem.
*fixed bug where patch cords were not getting erased (due to
fundamental fixes in the previous patch how the things are being
destructed, this has resulted in this bug being "hidden" until now).
.hc
Access to computers should be unlimited and total. - the hacker ethic
I'd love to be able to include bugfixes from pd-l2ork. I looked thru the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these Changelog items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:
*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden" until now).
Many of the older pre-git day bugs can be only traced by diff-ing our extensive snapshot repository available here:
http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition easier for other branches...
Hope this helps!
Best wishes,
Ico
On Oct 26, 2011, at 2:49 PM, Ivica Ico Bukvic wrote:
I'd love to be able to include bugfixes from pd-l2ork. I looked thru the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these Changelog items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:
*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this
problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden" until now).Many of the older pre-git day bugs can be only traced by diff-ing
our extensive snapshot repository available here:http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition
easier for other branches...Hope this helps!
Best wishes,
Ico
One thing that you could do that would make the history much easier to
browse is to start your git repo from the pure-data.git from Miller,
then untar each pd_l2ork release on top and check each release in,
then add the current contents of your git on top of that.
I can do that for you, if that would be helpful. It would only be
worthwhile if this then replaces the contents of your current git repo.
.hc
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: Ivica Ico Bukvic ico@vt.edu Cc: pd-list@iem.at Sent: Wednesday, October 26, 2011 3:19 PM Subject: Re: [PD] New versions of pd-l2ork now available on git
On Oct 26, 2011, at 2:49 PM, Ivica Ico Bukvic wrote:
I'd love to be able to include bugfixes from pd-l2ork. I looked
thru
the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these Changelog items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:
*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden"
until now).
Many of the older pre-git day bugs can be only traced by diff-ing our
extensive snapshot repository available here:
http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition easier
for other branches...
Hope this helps!
Best wishes,
Ico
One thing that you could do that would make the history much easier to browse is to start your git repo from the pure-data.git from Miller,
Since he didn't base his initial changes off of 0.43, wouldn't this be very difficult?
then untar each pd_l2ork release on top and check each release in, then add the current contents of your git on top of that.
I can do that for you, if that would be helpful. It would only be worthwhile if this then replaces the contents of your current git repo.
.hc
"It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Oct 26, 2011, at 3:44 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: Ivica Ico Bukvic ico@vt.edu Cc: pd-list@iem.at Sent: Wednesday, October 26, 2011 3:19 PM Subject: Re: [PD] New versions of pd-l2ork now available on git
On Oct 26, 2011, at 2:49 PM, Ivica Ico Bukvic wrote:
I'd love to be able to include bugfixes from pd-l2ork. I looked
thru
the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these
Changelog items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this
problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden"until now).
Many of the older pre-git day bugs can be only traced by diff-ing
ourextensive snapshot repository available here:
http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition
easierfor other branches...
Hope this helps!
Best wishes,
Ico
One thing that you could do that would make the history much easier
to browse is to start your git repo from the pure-data.git from Miller,Since he didn't base his initial changes off of 0.43, wouldn't this
be very difficult?
Miller started using git for Pd back in August 2007, so no.
.hc
then untar each pd_l2ork release on top and check each release in, then add the
current contents of your git on top of that.I can do that for you, if that would be helpful. It would only be
worthwhile if this then replaces the contents of your current git repo..hc
"It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone." --Bjarne Stroustrup (creator of C++)
-----Original Message----- From: Hans-Christoph Steiner [mailto:hans@at.or.at] Sent: Wednesday, October 26, 2011 3:19 PM To: Ivica Ico Bukvic Cc: 'Roman Haefeli'; pd-list@iem.at Subject: Re: [PD] New versions of pd-l2ork now available on git
On Oct 26, 2011, at 2:49 PM, Ivica Ico Bukvic wrote:
I'd love to be able to include bugfixes from pd-l2ork. I looked thru the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these
Changelog
items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:
*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden" until now).
Many of the older pre-git day bugs can be only traced by diff-ing our extensive snapshot repository available here:
http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition easier for other branches...
Hope this helps!
Best wishes,
Ico
One thing that you could do that would make the history much easier to browse is to start your git repo from the pure-data.git from Miller, then untar each pd_l2ork release on top and check each release in, then add the current contents of your git on top of that.
I can do that for you, if that would be helpful. It would only be worthwhile if this then replaces the contents of your current git repo.
If you think this would yield favorable results then I'd say let's go for it. My concern is that in the process of learning the pd code which has a relatively steep learning curve I ended up a good chunk of comments and reformatted some of the code to make things more legible for me (which does not mean it would also be legible for others). I also had to backtrack some of the changes and temporary hacks until I discovered the root of the problem (e.g. double-entry bug which has been entirely solved in pd-l2ork, or the gop redrawing bugs which have been also solved, and most recently enabling and immediately disabling gop that crashes any pd but pd-l2ork). One last roadblock is that the Changelog was not date stamped right from the outset so some of the earlier patches may not be easily decipherable but I can assist with those to the best of my ability.
So, please let me know if you wish to proceed and you'll have my full support.
Best wishes,
Ico
.hc
"It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White
On Oct 26, 2011, at 7:59 PM, Ivica Ico Bukvic wrote:
-----Original Message----- From: Hans-Christoph Steiner [mailto:hans@at.or.at] Sent: Wednesday, October 26, 2011 3:19 PM To: Ivica Ico Bukvic Cc: 'Roman Haefeli'; pd-list@iem.at Subject: Re: [PD] New versions of pd-l2ork now available on git
On Oct 26, 2011, at 2:49 PM, Ivica Ico Bukvic wrote:
I'd love to be able to include bugfixes from pd-l2ork. I looked thru the code and I can't really find what changes belong to what Changelog items. Can you point me towards the code related to these
Changelog
items, and expand on what they do, if you can? Then I can work on including them in Pd-extended:
*Implemented universal copy/paste *Fixed gop redrawing issue when passed coords message via script *finally discovered the root of all double-entry bugs (fingers crossed) and reverted all other previous workarounds for this problem. *fixed bug where patch cords were not getting erased (due to fundamental fixes in the previous patch how the things are being destructed, this has resulted in this bug being "hidden" until now).
Many of the older pre-git day bugs can be only traced by diff-ing our extensive snapshot repository available here:
http://l2ork.music.vt.edu/data/pd/
This is in part why we've set up a git. To make this transition easier for other branches...
Hope this helps!
Best wishes,
Ico
One thing that you could do that would make the history much easier to browse is to start your git repo from the pure-data.git from Miller, then untar each pd_l2ork release on top and check each release in, then add the current contents of your git on top of that.
I can do that for you, if that would be helpful. It would only be worthwhile if this then replaces the contents of your current git repo.
If you think this would yield favorable results then I'd say let's go for it. My concern is that in the process of learning the pd code which has a relatively steep learning curve I ended up a good chunk of comments and reformatted some of the code to make things more legible for me (which does not mean it would also be legible for others). I also had to backtrack some of the changes and temporary hacks until I discovered the root of the problem (e.g. double-entry bug which has been entirely solved in pd-l2ork, or the gop redrawing bugs which have been also solved, and most recently enabling and immediately disabling gop that crashes any pd but pd-l2ork). One last roadblock is that the Changelog was not date stamped right from the outset so some of the earlier patches may not be easily decipherable but I can assist with those to the best of my ability.
So, please let me know if you wish to proceed and you'll have my full support.
It looks like it'll take overnight to download all of the pd-l2ork-dev tarballs. So should be able to have this done tomorrow. You still up for swapping this in as your git repo?
.hc
If you are not part of the solution, you are part of the problem.
It looks like it'll take overnight to download all of the pd-l2ork-dev tarballs. So should be able to have this done tomorrow. You still up for swapping this in as your git repo?
.hc
Will I have complete control over it? In other words, I need to be made into an admin for it. If that is ok with you I am perfectly fine with making it the main repo. As an alternative, we could always mirror ours with this one...
Best wishes,
Ico
On Oct 31, 2011, at 7:44 PM, Ivica Ico Bukvic wrote:
It looks like it'll take overnight to download all of the pd-l2ork-dev tarballs. So should be able to have this done tomorrow. You still up for swapping this in as your git repo?
.hc
Will I have complete control over it? In other words, I need to be made into an admin for it. If that is ok with you I am perfectly fine with making it the main repo. As an alternative, we could always mirror ours with this one...
Yes, of course you'll have complete control. With git, each repo is its own entity that the user has complete control over. I'll do this right now, I'm posting it to my github [1] for now, I'll let you know once I'm done. Then you can delete your repo, clone this one, and push it to your repo. And it'll be all yours.
.hc
[1] https://github.com/pd-projects/pd-l2ork
There is no way to peace, peace is the way. -A.J. Muste
On Oct 31, 2011, at 7:44 PM, Ivica Ico Bukvic wrote:
It looks like it'll take overnight to download all of the pd-l2ork-dev tarballs. So should be able to have this done tomorrow. You still up for swapping this in as your git repo?
.hc
Will I have complete control over it? In other words, I need to be made into an admin for it. If that is ok with you I am perfectly fine with making it the main repo. As an alternative, we could always mirror ours with this one...
Best wishes,
Sorry, this is taking longer than I thought. YOu can still commit to your current repo, then I can move those commits on top of the one I'm building once its done.
.hc
"A cellphone to me is just an opportunity to be irritated wherever you are." - Linus Torvalds
On Oct 31, 2011, at 7:44 PM, Ivica Ico Bukvic wrote:
It looks like it'll take overnight to download all of the pd-l2ork-dev tarballs. So should be able to have this done tomorrow. You still up for swapping this in as your git repo?
.hc
Will I have complete control over it? In other words, I need to be made into an admin for it. If that is ok with you I am perfectly fine with making it the main repo. As an alternative, we could always mirror ours with this one...
Ok, here it is, the full history of pd-l2ork:
https://github.com/pd-projects/pd-l2ork
You can clone it, then edit .git/config so that the origin points to: git@github.com:pd-l2ork/pd.git
Then force push it to overwrite what is up there now: git push -f origin master
I saw your git-commit script, I highly recommend avoiding that approach, indeed avoiding "git commit -am" all together. I find it saves a lot of time in the long run by only committing files manually, then checking the commit with "git diff" before committing.
Try "git gui" instead, it makes it really easy to select which files to commit, in fact you can even easily commit sections of a file while keeping some parts of the file uncommitted. gitk is an invaluable history browser tool (apt-get install gitk git-gui).
Git is a powerful tool, but it is not easy to learn. I recommend reading up on it whenever you have a chance. It'll pay for itself in a big way later on in terms of increased productivity. Here are two free books I learned from:
http://progit.org/book/ http://book.git-scm.com/
.hc
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman
-
Hans-Christoph Steiner -
Ivica Ico Bukvic -
Jonathan Wilkes -
Roman Haefeli