A complete rewrite of Pd's GUI is starting to be usable. Miller has
accepted the core of this code into his repo for 0.43. Now we need to
get the whole thing done! There is now a branch for continuing off of
Miller's initial 0.43 commit here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build
instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running
on Windows yet, you could be the first. Shouldn't be too hard since
its all Tcl. There is lots of work left to do, and you can contribute
in many different ways. We always need testers, try using this Pd
version in your normal work, and report any and all bugs, problems,
feature ideas, etc. The simplest way is to contribute code is to
create a translation for Pd. You can also look thru the Tcl source for
things marked TODO and take a stab and doing them. If you want to
improve the GUI, make the new Pd window for example, an announce your
interest to pd-dev to make sure there are no duplications of efforts.
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink-
collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
This looks exciting!
Just curious- what does "make a good pd window" mean?
-Jonathan
--- On Wed, 8/26/09, Hans-Christoph Steiner hans@at.or.at wrote:
From: Hans-Christoph Steiner hans@at.or.at Subject: [PD] pd 0.43 branch with the new GUI code To: "Pd List" pd-list@iem.at Date: Wednesday, August 26, 2009, 6:51 AM
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need to get the whole thing done! There is now a branch for continuing off of Miller's initial 0.43 commit here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
DesireData's is quite nice, for example. Make the layout work well,
make the text and buttons communicate well, provide useful things on
the pd window, etc.
I'd be very happy with a slightly simpler version DesireData's. But
its GPL, so we can't just take it for vanilla without getting
copyright permission.
.hc
On Aug 26, 2009, at 1:20 AM, Jonathan Wilkes wrote:
This looks exciting!
Just curious- what does "make a good pd window" mean?
-Jonathan
--- On Wed, 8/26/09, Hans-Christoph Steiner hans@at.or.at wrote:
From: Hans-Christoph Steiner hans@at.or.at Subject: [PD] pd 0.43 branch with the new GUI code To: "Pd List" pd-list@iem.at Date: Wednesday, August 26, 2009, 6:51 AM
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need to get the whole thing done! There is now a branch for continuing off of Miller's initial 0.43 commit here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
All mankind is of one author, and is one volume; when one man dies,
one chapter is not torn out of the book, but translated into a better
language; and every chapter must be so translated.... -John Donne
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has
thanks for your hard work so far. Here are some observations from quickly running it for couple of minutes on Linux with blackbox window manager.
Frank
On Aug 26, 2009, at 3:35 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has
thanks for your hard work so far. Here are some observations from
quickly running it for couple of minutes on Linux with blackbox window
manager.
Thank you for your questions, since they really seem to highlight what
I think is the most important part of the new GUI code: ease of
customizability and extensibility.
- no scrollbars in help-intro.pd. Actually nothing seems to have
scrollbars.
No scrollbars implemented yet. Its tricky to get it right...
- cannot make windows smaller than 310 px wide (height 0 is
possible, though)
It won't let you go smaller than the menubar on the window. It
wouldn't be too hard to write a little scriptlet that turns off the
menubar for all CanvasWindows (a class in the GUI) or a little Pd
patch using [sys_gui] and [window_name]. I attached the pd patch
version. If you are interested, I'll hack up a tcl script version of
this. Plugin ideas like this help me refactor the code to make such
things easier to do.
- rightclick->Put: When clicking on an object, I generally want
either help or properties, not "Put". Maybe use "Put" only for background canvas
clicks? At least move I'd move it further down in the menu
That's a plugin, to remove it, "rm pd/startup/insertintopopup.tcl"
- The "categories" like "midi, network", "storage" seem arbitrary
(like all categories do). Maybe use the categories of help-intro?
That is Federico's system based on tags. Its also a plugin.
"object_db.tcl". Change it and you can have your own custom system!
I think it could be really cool if this plug parsed all the help
patches for tags, and built the menu based on that. Currently, its
close to that, but uses an included database instead of parsing the
help files directly.
- when running from "./bin" rsp. "./src" now, no helpfiles are found
("about" is empty, too). It was very nice that Pd so far was able to be run
from there without installation.
I've been instead running everything in "src/" so that no files have
to be moved when development. The 'bin' thing should only be used
with a 'make install'. There is no need to move files if you are not
doing a "make install".
.hc
If you are not part of the solution, you are part of the problem.
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
It won't let you go smaller than the menubar on the window.
I think, being able to make a window smaller should be a default action/script, as it is with the old Pd. It definitely should be possible without externals.
That is Federico's system based on tags. Its also a plugin.
"object_db.tcl". Change it and you can have your own custom system! I think it could be really cool if this plug parsed all the help patches for tags, and built the menu based on that. Currently, its close to that, but uses an included database instead of parsing the help files directly.
Which reminds me to quickly hint at the system for "parsable" help files we have introduced into the rj library for rjdj recently. There each help file has a subpatch called "pd REFERENCE", which is GOP so the contents are readable from the parent.
This subpatch only contains comments, which act like key:value pairs. Example:
Name: e_alias Summary: distort by reducing the sample rate to generate aliasing Argument 0: name for state saving (required) Argument 1: aliasing factor (optional) Inlet 0: audio signal to distort Outlet 0: alias-distorted audio signal. Description: distorts any audio signal by reducing the sample rate to generate aliasing. Non-key comments are added to "Descripton" in y-order. Tags: distortion, effect
Not all help files have been converted to this format yet, but the idea is to make html or other docs from these comments. Think of them like docstrings in Python.
Maybe this can be used for a better help browser, too. But I tell you, converting help files to this is a lot of tedious work. :) And we don't even care for any graphical layout conventions (deliberatly).
But it keeps the docs close to Pd which IMO is better than manually editing webpages.
- when running from "./bin" rsp. "./src" now, no helpfiles are found
("about" is empty, too). It was very nice that Pd so far was able to be run
from there without installation.I've been instead running everything in "src/" so that no files have to be moved when development. The 'bin' thing should only be used with a 'make install'. There is no need to move files if you are not doing a "make install".
I don't really care if files are in bin or src. (For some reason, bin is a symlink to src anyway) But neither lets me open any help files when starting Pd as "cd src; ./pd", which definitely was possible with previous Pds. Maybe I'm doing something wrong?
Frank
On Aug 26, 2009, at 3:44 PM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
It won't let you go smaller than the menubar on the window.
I think, being able to make a window smaller should be a default
action/script, as it is with the old Pd. It definitely should be possible without
externals.
Ok, so a scriptlet it is. I've never seen any other app that allows
you to shrink further than the menubar, for apps that are the menubar
type (i.e. not emacs. The GNOME apps generally don't.
That is Federico's system based on tags. Its also a plugin. "object_db.tcl". Change it and you can have your own custom
system! I think it could be really cool if this plug parsed all the help
patches for tags, and built the menu based on that. Currently, its close to that, but uses an included database instead of parsing the help files directly.Which reminds me to quickly hint at the system for "parsable" help
files we have introduced into the rj library for rjdj recently. There each
help file has a subpatch called "pd REFERENCE", which is GOP so the contents are readable from the parent.This subpatch only contains comments, which act like key:value
pairs. Example:Name: e_alias Summary: distort by reducing the sample rate to generate aliasing Argument 0: name for state saving (required) Argument 1: aliasing factor (optional) Inlet 0: audio signal to distort Outlet 0: alias-distorted audio signal. Description: distorts any audio signal by reducing the sample rate to generate aliasing. Non-key comments are added to "Descripton" in y-order. Tags: distortion, effect
Not all help files have been converted to this format yet, but the
idea is to make html or other docs from these comments. Think of them like
docstrings in Python.Maybe this can be used for a better help browser, too. But I tell you, converting help files to this is a lot of tedious work. :) And we
don't even care for any graphical layout conventions (deliberatly).But it keeps the docs close to Pd which IMO is better than manually
editing webpages.
Its a good idea and something that should definitely happen. That's
why its part of the PDDP templates (http://puredata.info/dev/pddp) but
unfortunately not widely implemented. How about following that spec,
its close, but a bit simpler and designed to be easily parsed in Pd:
case insensitive (removing a : in Pd is a little annoying)
pain in Pd)
- when running from "./bin" rsp. "./src" now, no helpfiles are found
("about" is empty, too). It was very nice that Pd so far was able to be run from there without installation.
I've been instead running everything in "src/" so that no files
have to be moved when development. The 'bin' thing should only be used
with a 'make install'. There is no need to move files if you are not
doing a "make install".I don't really care if files are in bin or src. (For some reason,
bin is a symlink to src anyway) But neither lets me open any help files when
starting Pd as "cd src; ./pd", which definitely was possible with previous Pds.
Maybe I'm doing something wrong?
Strange it works for me on Ubuntu and Mac OS X. Where is it looking?
.hc
The arc of history bends towards justice. - Dr. Martin Luther
King, Jr.
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 3:44 PM, Frank Barknecht wrote:
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
It won't let you go smaller than the menubar on the window.
I think, being able to make a window smaller should be a default
action/script, as it is with the old Pd. It definitely should be possible without
externals.Ok, so a scriptlet it is. I've never seen any other app that allows you to shrink further than the menubar,
Uhm, maybe you should look closer? :) Here I can minimize apps like Firefox and Gvim and hide parts of their menubars and icons.
Acutally I found, that I still can minimize the Pd main window, the menus fold together.
Its a good idea and something that should definitely happen. That's why its part of the PDDP templates (http://puredata.info/dev/pddp) but
unfortunately not widely implemented. How about following that spec,
its close, but a bit simpler and designed to be easily parsed in Pd:
- the subpatch is called [pd META], and is not GOP
GOP is important for us, as the docs are for users to read. We've chosen "REFERENCE" to not conflict with META, but of course that would be easy to change.
- each comment is a whole chunk of data
Same here, just that "free" comments are allowed as well as additional description paragraphs for readability reasons.
- the first word/atom is the datatype (i.e. no : at the end of it), case
insensitive (removing a : in Pd is a little annoying)
We have some 2-word keys, like "Outlet 0", so that is a tricky decision. Anyway, as our system is mainly intended to be processed by "smarter" text processing tools, the : doesn't hurt. But maybe we could add spaces around it.
- tags are space-separated not comma-separated (handling commas is a
pain in Pd)
Again, this is to include tags with more than one word, but I see that for Pd parsing, the comma is nasty. However I guess with the text processing possibilities of tcl available in scriptlets, this may not be an issue anymore.
Generally the "pd REFERENCE" idea was to have a most simple, externally parsable and user-readable reference system. META is cool and was an obvious inspiration, but the rest of PDDP was deemed much too bloated with layout conventions and color coding and cnv-paintings and similar stuff to be useable for us. Help files IMO should be written, not designed.
I don't really care if files are in bin or src. (For some reason, bin is a symlink to src anyway) But neither lets me open any help files when
starting Pd as "cd src; ./pd", which definitely was possible with previous Pds.
Maybe I'm doing something wrong?Strange it works for me on Ubuntu and Mac OS X. Where is it looking?
no idea. the help browser doesn't open. i get this message in the pd window:
PLACEHOLDER menu_helpbrowser {$help_top_directory}
Frank
On Aug 26, 2009, at 4:46 PM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 3:44 PM, Frank Barknecht wrote:
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
It won't let you go smaller than the menubar on the window.
I think, being able to make a window smaller should be a default action/script, as it is with the old Pd. It definitely should be possible without externals.
Ok, so a scriptlet it is. I've never seen any other app that
allows you to shrink further than the menubar,Uhm, maybe you should look closer? :) Here I can minimize apps like
Firefox and Gvim and hide parts of their menubars and icons.Acutally I found, that I still can minimize the Pd main window, the
menus fold together.Its a good idea and something that should definitely happen. That's
why its part of the PDDP templates (http://puredata.info/dev/pddp) but unfortunately not widely implemented. How about following that spec, its close, but a bit simpler and designed to be easily parsed in Pd:
- the subpatch is called [pd META], and is not GOP
GOP is important for us, as the docs are for users to read. We've
chosen "REFERENCE" to not conflict with META, but of course that would be
easy to change.
- each comment is a whole chunk of data
Same here, just that "free" comments are allowed as well as additional description paragraphs for readability reasons.
- the first word/atom is the datatype (i.e. no : at the end of it),
case insensitive (removing a : in Pd is a little annoying)
We have some 2-word keys, like "Outlet 0", so that is a tricky
decision. Anyway, as our system is mainly intended to be processed by
"smarter" text processing tools, the : doesn't hurt. But maybe we could add spaces
around it.
- tags are space-separated not comma-separated (handling commas is a
pain in Pd)
Again, this is to include tags with more than one word, but I see
that for Pd parsing, the comma is nasty. However I guess with the text processing possibilities of tcl available in scriptlets, this may not be an
issue anymore.Generally the "pd REFERENCE" idea was to have a most simple,
externally parsable and user-readable reference system. META is cool and was an
obvious inspiration, but the rest of PDDP was deemed much too bloated with
layout conventions and color coding and cnv-paintings and similar stuff to
be useable for us. Help files IMO should be written, not designed.I don't really care if files are in bin or src. (For some reason,
bin is a symlink to src anyway) But neither lets me open any help files when starting Pd as "cd src; ./pd", which definitely was possible with previous Pds. Maybe I'm doing something wrong?Strange it works for me on Ubuntu and Mac OS X. Where is it looking?
no idea. the help browser doesn't open. i get this message in the pd
window:PLACEHOLDER menu_helpbrowser {$help_top_directory}
Hehe, not implemented yet. The old code would just plug in and work,
but I was hoping to rewrite the help browser so I haven't included it
yet.
Is this what you mean by not finding help patches? Or do you mean
right-click->Help?
.hc
Looking at things from a more basic level, you can come up with a more
direct solution... It may sound small in theory, but it in practice,
it can change entire economies. - Amy Smith
On Aug 26, 2009, at 4:46 PM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 3:44 PM, Frank Barknecht wrote:
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
It won't let you go smaller than the menubar on the window.
I think, being able to make a window smaller should be a default action/script, as it is with the old Pd. It definitely should be possible without externals.
Ok, so a scriptlet it is. I've never seen any other app that
allows you to shrink further than the menubar,Uhm, maybe you should look closer? :) Here I can minimize apps like
Firefox and Gvim and hide parts of their menubars and icons.Acutally I found, that I still can minimize the Pd main window, the
menus fold together.Its a good idea and something that should definitely happen. That's
why its part of the PDDP templates (http://puredata.info/dev/pddp) but unfortunately not widely implemented. How about following that spec, its close, but a bit simpler and designed to be easily parsed in Pd:
- the subpatch is called [pd META], and is not GOP
GOP is important for us, as the docs are for users to read. We've
chosen "REFERENCE" to not conflict with META, but of course that would be
easy to change.
AFAIK, the GOP status shouldn't affect the parsability. In the .pd
file, it just adds a "#X coords" line before the "#X restore" so it
would be easily ignored. Therefore, both GOP and non-GOP should be
fine.
- each comment is a whole chunk of data
Same here, just that "free" comments are allowed as well as additional description paragraphs for readability reasons.
How to you mark "free" comments? Once there are keywords, then those
can easily be mistakenly entered in the free comments. To keep the
parsing simple, it makes sense to keep the free comments out out of
the [pd META] subpatch. Then have a
This doesn't have to be any hard fast rule in the implementation. In
effect, if someone writes a comment without a recognized tag, it'll be
a free comment. But I think it would be a good convention to follow:
"each comment in [pd META] counts as a piece of data". There could
also be a comment tag, it could be "#" or "comment".
So like python style: don't force people to do the right thing, but
make the right thing easy to do.
- the first word/atom is the datatype (i.e. no : at the end of it),
case insensitive (removing a : in Pd is a little annoying)
We have some 2-word keys, like "Outlet 0", so that is a tricky
decision. Anyway, as our system is mainly intended to be processed by
"smarter" text processing tools, the : doesn't hurt. But maybe we could add spaces
around it.
How about Outlet0, etc? Its really just a unique ID, so once parsed
the tag could be displayed as whatever.
These rules make it easier to parse in any language too. But I think
its important that the help patches be designed to be read by Pd
patches, since they are pd patches themselves.
- tags are space-separated not comma-separated (handling commas is a
pain in Pd)
Again, this is to include tags with more than one word, but I see
that for Pd parsing, the comma is nasty. However I guess with the text processing possibilities of tcl available in scriptlets, this may not be an
issue anymore.
It is not only a question of making the format easy to parse, but also
easy to create. Since it is text included in a Pd patch, it should
follow Pd's syntax rules. Pd is made from [selector arg arg arg], I
think these comments should have the same syntax.
Many tag interfaces use space-separated tags, its a common idiom. It
makes sense with Pd too.
Generally the "pd REFERENCE" idea was to have a most simple,
externally parsable and user-readable reference system. META is cool and was an
obvious inspiration, but the rest of PDDP was deemed much too bloated with
layout conventions and color coding and cnv-paintings and similar stuff to
be useable for us. Help files IMO should be written, not designed.
We are only talking about [pd META], I also agree the PDDP stuff ended
up somewhat bloated. I think we are agreed on the [pd META] goals: as
simple as possible, parsable, user-readable. I hope we don't end up
with a separate, incompatible format unless there is a really good
reason for it.
.hc
All mankind is of one author, and is one volume; when one man dies,
one chapter is not torn out of the book, but translated into a better
language; and every chapter must be so translated.... -John Donne
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
How about Outlet0, etc? Its really just a unique ID, so once parsed the tag could be displayed as whatever.
Actually I think, "Outlet 0" is easier to parse with Pd: [route Outlet]-[route 0 1 2 3]. Having a separator like the ":" makes reading easier. I guess, for Pd parsing padding that with spaces would help and not hinder readability that much.
So outlet comments could look like:
Outlet 0 : left stereo signal Outlet 1 : right stereo signal
I will for now continue to not use a space, and when I'm done, run a regex over them.
Many tag interfaces use space-separated tags, its a common idiom. It
makes sense with Pd too.
I *really* want multiple-word tags. :) So a separator is needed, but one without Pd-meaning could be used, like "-".
Anyway, many values use commas already, because they are written in natural language which has commas so the parser should be aware of them.
Frank
On Aug 27, 2009, at 3:47 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
How about Outlet0, etc? Its really just a unique ID, so once
parsed the tag could be displayed as whatever.Actually I think, "Outlet 0" is easier to parse with Pd: [route
Outlet]-[route 0 1 2 3]. Having a separator like the ":" makes reading easier. I
guess, for Pd parsing padding that with spaces would help and not hinder
readability that much.
[route outlet0 outlet1 outlet2 outlet3]
So outlet comments could look like:
Outlet 0 : left stereo signal Outlet 1 : right stereo signal
I will for now continue to not use a space, and when I'm done, run a
regex over them.
Rarely do people have a standalone colon in writing, so this will
create a common syntax error.
Many tag interfaces use space-separated tags, its a common idiom. It makes sense with Pd too.
I *really* want multiple-word tags. :) So a separator is needed, but
one without Pd-meaning could be used, like "-".
A "-" dash/minus/hyphen separator would be a much better option than a
colon ":" since in normal (English at least) usage, a "-" is separated
on both sides with a space.
Can you give some examples of why [pd META] needs multiple-word tags?
I mean its nice sometimes, but there are very well established tag
interfaces that use space-separated tags. Since this text is in Pd
patches, it should follow Pd syntax rules, since Pd users already know
them well, unless there is a strong reason to diverge. With only a
few exceptions, the function in an object box is the first word in a
space-separated list. In a message, the first word of a space-
separated list is the selector.
What's more needed is a quoting mechanism. Space-separated tags
usually use "two words" quotes to join them. But that's a bigger
issue in Pd...
Anyway, many values use commas already, because they are written in
natural language which has commas so the parser should be aware of them.
That is for sure something that will happen and will have to be
handled. I just ask that we avoid making commas and semi-colons a
required part of the data format.
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink-
collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Aug 27, 2009, at 3:47 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
How about Outlet0, etc? Its really just a unique ID, so once parsed the tag could be displayed as whatever.
Actually I think, "Outlet 0" is easier to parse with Pd: [route
Outlet]-[route 0 1 2 3]. Having a separator like the ":" makes reading easier. I
guess, for Pd parsing padding that with spaces would help and not hinder
readability that much.[route outlet0 outlet1 outlet2 outlet3]
Okay, you got me here. :)
Can you give some examples of why [pd META] needs multiple-word tags?
For terms with multiple words like "frequency modulation". I know, I need them, believe me.
I mean its nice sometimes, but there are very well established tag
interfaces that use space-separated tags. Since this text is in Pd
patches, it should follow Pd syntax rules, since Pd users already know
them well, unless there is a strong reason to diverge. With only a few exceptions, the function in an object box is the first word in a
space-separated list. In a message, the first word of a space-separated list is the selector.What's more needed is a quoting mechanism. Space-separated tags usually use "two words" quotes to join them. But that's a bigger issue in Pd...
Yeah, that would solve my problems as well.
But let me repeat: Unlike "META", "REFERENCE" is meant to be documentation for the user, so readability is more important than parsability, and parsability outside of Pd to us is more important than parsability inside of Pd. The latter would be a bonus, but I won't sacrifice readability for it. We're already making concessions in that area, e.g. we have single comments for all the messages types an inlet accepts. (See "Inlet 1" in the attachement.) Pd syntax rules are fine, but English syntax rules where spaces separate words, not key:value pairs, are more important here.
I also don't like "Outlet0" of a similar reason: It's not well readable, 0 and O look too similar etc. so the two words should be separated just like everything else in English.
Attached is a comparison of the possibilities we've talked about. I like the first one best, which probably will get dashes in the Tags field as a result of our discussion. The second one in the upper right and the third one are okayish, but the "META"-version on the lower right to me looks like it is written for parsers, not for humans.
Frank
On Aug 27, 2009, at 11:04 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Aug 27, 2009, at 3:47 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
How about Outlet0, etc? Its really just a unique ID, so once
parsed the tag could be displayed as whatever.Actually I think, "Outlet 0" is easier to parse with Pd: [route Outlet]-[route 0 1 2 3]. Having a separator like the ":" makes reading easier. I guess, for Pd parsing padding that with spaces would help and not hinder readability that much.
[route outlet0 outlet1 outlet2 outlet3]
Okay, you got me here. :)
Can you give some examples of why [pd META] needs multiple-word tags?
For terms with multiple words like "frequency modulation". I know, I
need them, believe me.
I know its not perfect, but frequencymodulation and FM work.
I mean its nice sometimes, but there are very well established tag interfaces that use space-separated tags. Since this text is in Pd patches, it should follow Pd syntax rules, since Pd users already
know them well, unless there is a strong reason to diverge. With only a
few exceptions, the function in an object box is the first word in a space-separated list. In a message, the first word of a space- separated list is the selector.What's more needed is a quoting mechanism. Space-separated tags
usually use "two words" quotes to join them. But that's a bigger issue in
Pd...Yeah, that would solve my problems as well.
But let me repeat: Unlike "META", "REFERENCE" is meant to be
documentation for the user, so readability is more important than parsability, and
parsability outside of Pd to us is more important than parsability inside of Pd.
The latter would be a bonus, but I won't sacrifice readability for it. We're
already making concessions in that area, e.g. we have single comments for
all the messages types an inlet accepts. (See "Inlet 1" in the attachement.)
Pd syntax rules are fine, but English syntax rules where spaces separate
words, not key:value pairs, are more important here.I also don't like "Outlet0" of a similar reason: It's not well
readable, 0 and O look too similar etc. so the two words should be separated
just like everything else in English.
Inlet0/Outlet0 could be somewhat hard to read, but I think context
really helps a lot there. I could maybe see someone speaking Spanish
or Italian expecting "inleto" or "outleto", but I can't see a reason
why anyone would expect there to be InletO or OutletO.
OutletOne, OutletTwo, InletThree is an option, tho not very computery.
Attached is a comparison of the possibilities we've talked about. I
like the first one best, which probably will get dashes in the Tags field as
a result of our discussion. The second one in the upper right and the third one
are okayish, but the "META"-version on the lower right to me looks like
it is written for parsers, not for humans.
[pd META] was written more for meta data, since it doesn't include
things like inlets, outlets, etc. But it was not so much designed to
be easily parsed as much as easily written by Pd patchers, yet
parsable. The non-meta is on the front page of the documentation
rather than in a subpatch. I like the idea of having everything
easily parsable, including the reference text.
One thing that bugs me with [pd REFERENCE] that I find very hard to
scan is the message types an inlet takes. They are all bunched up
into a single comment, making it hard to scan and even read. The same
goes with the Gem docs.
I think that if the PDDP template had some of the graphical elements
stripped out and a couple of other minor adjustments, I think it could
work quite well. I attached my version of it from the 'apple'
library. For example, I find big blocks of text hard to scan. And
most of the time when looking at a help patch, people are scanning,
not reading. I think the layout of the PDDP template, though more
work for the creator, makes for very scannable and readable information.
Something to consider in parsing is the possibility of using Y
location in the parsing. It would require two pass parsing, since the
file is not organized by Y position, but wouldn't be so hard to do in
Pd or easier in string parsing languages. This makes the front page
format of the PDDP parsable, though getting the inlet/outlet numbers
could be a bit tricky. Having the IOlet number markers have
horizontal lines would make people naturally put them above the text,
making the parsing much easier.
.hc
¡El pueblo unido jamás será vencido!
--- On Thu, 8/27/09, Hans-Christoph Steiner hans@at.or.at wrote:
From: Hans-Christoph Steiner hans@at.or.at Subject: Re: [PD] [pd META] metadata format WAS: pd 0.43 branch with the new GUI code To: "Frank Barknecht" fbar@footils.org Cc: "Pd List" pd-list@iem.at Date: Thursday, August 27, 2009, 6:28 PM
On Aug 27, 2009, at 11:04 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph
Steiner wrote:
On Aug 27, 2009, at 3:47 AM, Frank Barknecht
wrote:
Hallo, Hans-Christoph Steiner hat gesagt: //
Hans-Christoph Steiner wrote:
How about Outlet0, etc? Its really
just a unique ID, so once parsed
the tag could be displayed as whatever.
Actually I think, "Outlet 0" is easier to
parse with Pd: [route
Outlet]-[route 0 1 2 3]. Having a separator like the ":"
makes reading easier. I
guess, for Pd parsing padding that with spaces would help
and not hinder
readability that much.
[route outlet0 outlet1 outlet2 outlet3]
Okay, you got me here. :)
Can you give some examples of why [pd META] needs
multiple-word tags?
For terms with multiple words like "frequency
modulation". I know, I need them,
believe me.
I know its not perfect, but frequencymodulation and FM work.
I mean its nice sometimes, but there are very well
established tag
interfaces that use space-separated tags.
Since this text is in Pd
patches, it should follow Pd syntax rules, since
Pd users already know
them well, unless there is a strong reason to
diverge. With only a few
exceptions, the function in an object box is the
first word in a
space-separated list. In a message, the
first word of a space-separated
list is the selector.
What's more needed is a quoting mechanism.
Space-separated tags usually
use "two words" quotes to join them. But
that's a bigger issue in Pd...
Yeah, that would solve my problems as well.
But let me repeat: Unlike "META", "REFERENCE" is meant
to be documentation for
the user, so readability is more important than
parsability, and parsability
outside of Pd to us is more important than parsability
inside of Pd. The latter
would be a bonus, but I won't sacrifice readability
for it. We're already
making concessions in that area, e.g. we have single
comments for all the
messages types an inlet accepts. (See "Inlet 1" in the
attachement.) Pd syntax
rules are fine, but English syntax rules where spaces
separate words, not
key:value pairs, are more important here.
I also don't like "Outlet0" of a similar reason: It's
not well readable,
0 and O look too similar etc. so the two words should
be separated just like
everything else in English.
Inlet0/Outlet0 could be somewhat hard to read, but I think context really helps a lot there. I could maybe see someone speaking Spanish or Italian expecting "inleto" or "outleto", but I can't see a reason why anyone would expect there to be InletO or OutletO.
OutletOne, OutletTwo, InletThree is an option, tho not very computery.
Attached is a comparison of the possibilities we've
talked about. I like the
first one best, which probably will get dashes in the
Tags field as a result of
our discussion. The second one in the upper right and
the third one are
okayish, but the "META"-version on the lower right to
me looks like it is
written for parsers, not for humans.
[pd META] was written more for meta data, since it doesn't include things like inlets, outlets, etc. But it was not so much designed to be easily parsed as much as easily written by Pd patchers, yet parsable. The non-meta is on the front page of the documentation rather than in a subpatch. I like the idea of having everything easily parsable, including the reference text.
One thing that bugs me with [pd REFERENCE] that I find very hard to scan is the message types an inlet takes. They are all bunched up into a single comment, making it hard to scan and even read. The same goes with the Gem docs.
I think that if the PDDP template had some of the graphical elements stripped out and a couple of other minor adjustments, I think it could work quite well. I attached my version of it from the 'apple' library. For example, I find big blocks of text hard to scan. And most of the time when looking at a help patch, people are scanning, not reading. I think the layout of the PDDP template, though more work for the creator, makes for very scannable and readable information.
I don't know what the patch you attached has to do with the PDDP template. There aren't any big blocks of text in the PDDP template.
Something to consider in parsing is the possibility of using Y location in the parsing. It would require two pass parsing, since the file is not organized by Y position, but wouldn't be so hard to do in Pd or easier in string parsing languages. This makes the front page format of the PDDP parsable, though getting the inlet/outlet numbers could be a bit tricky. Having the IOlet number markers have horizontal lines would make people naturally put them above the text, making the parsing much easier.
.hc
Frank Barknecht wrote:
- The "categories" like "midi, network", "storage" seem arbitrary (like all categories do). Maybe use the categories of help-intro?
yes, categories are arbitrary :-)
but that menu is a bit different.
first it uses tags.
it builds the top level categories by partitioning the object_db by most popular tags (the most popular tags are found thru a datamining application[1]).
so, the first level it's a proper category.
the second level (and further levels, if any) shows you a search "view" by that tag, so you can find an object in multiple second level categories. again, which tags to show is decided thru datamining.
I choose to did that because looking into menus could be frustrating. if accidentally you start searching in the wrong branch of menu, you never find the object you are looking for. however I eliminated dups on the first level, because too many dups were proliferating in the menu.
so you should start looking in the right category, then you have many chances to find the object you want.
anyway, the structure is hardcoded, and currently is: { connectivity {osc midi network} conversion {midi audio} cyclone {hammer sickle audio math control} zexy {audio analysis matrix control} maxlib {control time math glue} audio {abstraction conversion fftease cyclone math logical analysis filters delay effects tables} vasp {declaration arithmetic basics functions generators transcendent minmax utilities filters fft displace} storage {abstraction lists matrix tables} pdmtl {control convert list edit flow imaging} imaging {{gem particles} {gem manipulators} {gem pixes} {gem geos} {gem opengl} {pdp image} {pdp processing} {pdp abstraction} {pdp 3d} pidip manipulators wrapper particles automata processing} }
ideas on how to improve it are very welcome ;)
[1]: this datamining application allows also to add/remove tags. I'd like to share it with others, so others can contribute to tagging. I'm looking for someone that can host a php+mysql webapp. it's very tiny: only 14.8 k of code, including two images, and a database consisting of one table (occupies 656k on disk with 2685 objects in it)
hi hcs, miller,
i've been testing some changes i've made locally and i've just noticed in regards to the code miller checked into trunk, that it breaks autotools which is still attempting to install pd-gui (and failing). relevant changes will probably need to be made to 'makefile.in' i guess..
dmotd
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has
accepted the core of this code into his repo for 0.43. Now we need to
get the whole thing done! There is now a branch for continuing off of
Miller's initial 0.43 commit here:http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts.
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Yeah, I think the 'install' targets in either the old src/configure.in
build system or the new autogen.sh/configure.ac build system have not
been dealt with.
I'm pretty happy with the new build system, but it depends on libtool,
which is kind of a pain. Ideally, it would not use libtool and would
be setup to work with MinGW, then I think we'd' have a winner for a
new build system. If you want to work on that, please dive right it. :)
.hc
On Aug 26, 2009, at 9:35 AM, dmotd wrote:
hi hcs, miller,
i've been testing some changes i've made locally and i've just noticed in regards to the code miller checked into trunk, that it breaks autotools which is still attempting to install pd-gui (and failing). relevant changes will probably need to be made to 'makefile.in' i guess..
dmotd
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need
to get the whole thing done! There is now a branch for continuing off
of Miller's initial 0.43 commit here:http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build
instructions, etc.:http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it
running on Windows yet, you could be the first. Shouldn't be too hard since
its all Tcl. There is lots of work left to do, and you can contribute in
many different ways. We always need testers, try using this Pd version
in your normal work, and report any and all bugs, problems, feature ideas,
etc. The simplest way is to contribute code is to create a translation
for Pd. You can also look thru the Tcl source for things marked TODO and
take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts..hc
'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into
the possession of everyone, and the receiver cannot dispossess himself
of it. - Thomas Jefferson
on linux, right?
(I never run make install, so I don't tend to catch these problems - thanks for flagging it)
cheers M
On Wed, Aug 26, 2009 at 11:35:55PM +1000, dmotd wrote:
hi hcs, miller,
i've been testing some changes i've made locally and i've just noticed in regards to the code miller checked into trunk, that it breaks autotools which is still attempting to install pd-gui (and failing). relevant changes will probably need to be made to 'makefile.in' i guess..
dmotd
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has
accepted the core of this code into his repo for 0.43. Now we need to
get the whole thing done! There is now a branch for continuing off of
Miller's initial 0.43 commit here:http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
There is a wiki page to keep track of progress with build instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts.
.hc
'You people have such restrictive dress for women,??? she said, hobbling
away in three inch heels and panty hose to finish out another pink- collar temp pool day. - ???Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need to get the whole thing done! There is now a branch for continuing off of Miller's initial 0.43 commit here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
no configure?? marius.
There is a wiki page to keep track of progress with build instructions, etc.:
http://puredata.info/dev/PdGuiRewrite
Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to
pd-dev to make sure there are no duplications of efforts..hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller
has accepted the core of this code into his repo for 0.43. Now we
need to get the whole thing done! There is now a branch for
continuing off of Miller's initial 0.43 commit here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...no configure?? marius.
read the page a little closer: http://puredata.info/dev/PdGuiRewrite
.hc
There is a wiki page to keep track of progress with build
instructions, etc.: http://puredata.info/dev/PdGuiRewrite Try it out on GNU/Linux or Mac OS X, no one's tried to get it
running on Windows yet, you could be the first. Shouldn't be too
hard since its all Tcl. There is lots of work left to do, and you
can contribute in many different ways. We always need testers, try
using this Pd version in your normal work, and report any and all
bugs, problems, feature ideas, etc. The simplest way is to
contribute code is to create a translation for Pd. You can also
look thru the Tcl source for things marked TODO and take a stab and
doing them. If you want to improve the GUI, make the new Pd window
for example, an announce your interest to pd-dev to make sure
there are no duplications of efforts. .hc ---------------------------------------------------------------------------- 'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
"[T]he greatest purveyor of violence in the world today [is] my own
government." - Martin Luther King, Jr.
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need to get the whole thing done! There is now a branch for continuing off of Miller's initial 0.43 commit here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
no configure?? marius.
read the page a little closer: http://puredata.info/dev/PdGuiRewrite
i fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui-rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43': 302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me errors, too. marius.
.hc
There is a wiki page to keep track of progress with build instructions, etc.: http://puredata.info/dev/PdGuiRewrite Try it out on GNU/Linux or Mac OS X, no one's tried to get it running on Windows yet, you could be the first. Shouldn't be too hard since its all Tcl. There is lots of work left to do, and you can contribute in many different ways. We always need testers, try using this Pd version in your normal work, and report any and all bugs, problems, feature ideas, etc. The simplest way is to contribute code is to create a translation for Pd. You can also look thru the Tcl source for things marked TODO and take a stab and doing them. If you want to improve the GUI, make the new Pd window for example, an announce your interest to pd-dev to make sure there are no duplications of efforts. .hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
"[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller
has accepted the core of this code into his repo for 0.43. Now
we need to get the whole thing done! There is now a branch for
continuing off of Miller's initial 0.43 commit here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...no configure?? marius.
read the page a little closer: http://puredata.info/dev/PdGuiRewrite
i fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui- rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43':
302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me errors,
too. marius.
Doh sorry, put the wrong link there, please try again:)
http://puredata.info/dev/PdGuiRewrite
.hc
.hc
There is a wiki page to keep track of progress with build
instructions, etc.: http://puredata.info/dev/PdGuiRewrite Try it out on GNU/Linux or Mac OS X, no one's tried to get it
running on Windows yet, you could be the first. Shouldn't be too
hard since its all Tcl. There is lots of work left to do, and
you can contribute in many different ways. We always need
testers, try using this Pd version in your normal work, and
report any and all bugs, problems, feature ideas, etc. The
simplest way is to contribute code is to create a translation for
Pd. You can also look thru the Tcl source for things marked TODO
and take a stab and doing them. If you want to improve the GUI,
make the new Pd window for example, an announce your interest to
pd-dev to make sure there are no duplications of efforts. .hc ---------------------------------------------------------------------------- 'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out
another pink-collar temp pool day. - “Hijab Scene #2", by Mohja
Kahf _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list---------------------------------------------------------------------------- "[T ]he greatest purveyor of violence in the world today [is] my own
government." - Martin Luther King, Jr.
I hate it when they say, "He gave his life for his country." Nobody
gives their life for anything. We steal the lives of these kids. -
Admiral Gene LeRocque
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable. Miller has accepted the core of this code into his repo for 0.43. Now we need to get the whole thing done! There is now a branch for continuing off of Miller's initial 0.43 commit here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...
no configure?? marius.
read the page a little closer: http://puredata.info/dev/PdGuiRewrite
i fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite
svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui-rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43': 302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me errors, too. marius.
Doh sorry, put the wrong link there, please try again:)
doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd"
-DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4"
-DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1
-DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1
-DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1
-DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1
-DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1
-DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1
-DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1
-DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1
-DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1
-DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1
-DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1
-DHAVE_STRTOL=1 -I. -I. -I/sw/include -I../portmidi/pm_common
-I../portmidi/porttime -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd"
-DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4"
-DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1
-DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1
-DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1
-DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1
-DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1
-DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1
-DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1
-DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1
-DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1
-DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1
-DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1
-DHAVE_STRTOL=1 -DPD -DUSEAPI_PORTAUDIO -I../portaudio/include
-DMACOSX -g -O2 -MT pd-s_audio_pa.o -MD -MP -MF
".deps/pd-s_audio_pa.Tpo" -c -o pd-s_audio_pa.o test -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po"; else rm
-f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi
s_audio_pa.c:72: error: syntax error before '*' token
s_audio_pa.c: In function 'pa_lowlevel_callback':
s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use in this
function)
s_audio_pa.c:80: error: (Each undeclared identifier is reported only once
s_audio_pa.c:80: error: for each function it appears in.)
s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in this
function)
s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in this
function)
s_audio_pa.c: In function 'pa_open_callback':
s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first use in
this function)
s_audio_pa.c:118: error: syntax error before 'instreamparams'
s_audio_pa.c:153: error: 'instreamparams' undeclared (first use in this
function)
s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use in this
function)
s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream' makes
pointer from integer without a cast
s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream' makes
integer from pointer without a cast
s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream' makes
integer from pointer without a cast
s_audio_pa.c:173: error: too few arguments to function 'Pa_OpenStream'
s_audio_pa.c: In function 'pa_getdevs':
s_audio_pa.c:420: error: 'struct <anonymous>' has no member named 'hostApi'
s_audio_pa.c:427: error: 'struct <anonymous>' has no member named 'hostApi'
make[2]: *** [pd-s_audio_pa.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
marius.
On Aug 26, 2009, at 7:41 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
A complete rewrite of Pd's GUI is starting to be usable.
Miller has accepted the core of this code into his repo for
0.43. Now we need to get the whole thing done! There is now a
branch for continuing off of Miller's initial 0.43 commit here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit...no configure?? marius.
read the page a little closer: http://puredata.info/dev/ PdGuiRewrite
i fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui- rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43':
302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me
errors, too. marius.Doh sorry, put the wrong link there, please try again:)
doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" - DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" - DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 - DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 - DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 - DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 - DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 - DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 - DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 - DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 - DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 - DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 - DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 - DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 - DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 - DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 - DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 - DHAVE_STRTOL=1 -I. -I. -I/sw/include -I../portmidi/pm_common -I../ portmidi/porttime -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" - DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" - DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 - DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 - DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 - DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 - DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 - DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 - DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 - DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 - DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 - DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 - DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 - DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 - DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 - DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 - DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 - DHAVE_STRTOL=1 -DPD -DUSEAPI_PORTAUDIO -I../portaudio/include - DMACOSX -g -O2 -MT pd-s_audio_pa.o -MD -MP -MF ".deps/pd- s_audio_pa.Tpo" -c -o pd-s_audio_pa.o
test -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po"; else
rm -f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi s_audio_pa.c:72: error: syntax error before '*' token s_audio_pa.c: In function 'pa_lowlevel_callback': s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use in
this function) s_audio_pa.c:80: error: (Each undeclared identifier is reported only
once s_audio_pa.c:80: error: for each function it appears in.) s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in this
function) s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in this
function) s_audio_pa.c: In function 'pa_open_callback': s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first use
in this function) s_audio_pa.c:118: error: syntax error before 'instreamparams' s_audio_pa.c:153: error: 'instreamparams' undeclared (first use in
this function) s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use in
this function) s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream'
makes pointer from integer without a cast s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: error: too few arguments to function 'Pa_OpenStream' s_audio_pa.c: In function 'pa_getdevs': s_audio_pa.c:420: error: 'struct <anonymous>' has no member named
'hostApi' s_audio_pa.c:427: error: 'struct <anonymous>' has no member named
'hostApi' make[2]: *** [pd-s_audio_pa.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2marius.
Weird... which platform are you on? I've build this thing from
scratch many times on Ubuntu, Debian, and Mac OS X/Intel.
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink-
collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 7:41 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote:
Hans-Christoph Steiner wrote: > A complete rewrite of Pd's GUI is starting to be usable. Miller > has accepted the core of this code into his repo for 0.43. Now > we need to get the whole thing done! There is now a branch for > continuing off of Miller's initial 0.43 commit here: > http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... >
no configure?? marius.
read the page a little closer: http://puredata.info/dev/PdGuiRewrite
i fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite
svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui-rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43': 302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me errors, too. marius.
Doh sorry, put the wrong link there, please try again:)
doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" -DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" -DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -I. -I. -I/sw/include -I../portmidi/pm_common -I../portmidi/porttime -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" -DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" -DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DPD -DUSEAPI_PORTAUDIO -I../portaudio/include -DMACOSX -g -O2 -MT pd-s_audio_pa.o -MD -MP -MF ".deps/pd-s_audio_pa.Tpo" -c -o pd-s_audio_pa.o
test -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po"; else rm -f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi s_audio_pa.c:72: error: syntax error before '*' token s_audio_pa.c: In function 'pa_lowlevel_callback': s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use in this function) s_audio_pa.c:80: error: (Each undeclared identifier is reported only once s_audio_pa.c:80: error: for each function it appears in.) s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in this function) s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in this function) s_audio_pa.c: In function 'pa_open_callback': s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first use in this function) s_audio_pa.c:118: error: syntax error before 'instreamparams' s_audio_pa.c:153: error: 'instreamparams' undeclared (first use in this function) s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use in this function) s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream' makes pointer from integer without a cast s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream' makes integer from pointer without a cast s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream' makes integer from pointer without a cast s_audio_pa.c:173: error: too few arguments to function 'Pa_OpenStream' s_audio_pa.c: In function 'pa_getdevs': s_audio_pa.c:420: error: 'struct <anonymous>' has no member named 'hostApi' s_audio_pa.c:427: error: 'struct <anonymous>' has no member named 'hostApi' make[2]: *** [pd-s_audio_pa.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2marius.
Weird... which platform are you on? I've build this thing from scratch many times on Ubuntu, Debian, and Mac OS X/Intel.
still leopard, no snow yet... 10.5.8. I guess I am doing something wrong..
I get nothing more than a warning (I mean no error) from ./configure config.status: WARNING: 'makefile.in' seems to ignore the --datarootdir setting and a slightly different error with the old build system
cd ../obj; cc -Wl -framework CoreAudio -framework AudioUnit -framework AudioToolbox -framework Carbon -framework CoreMIDI -arch i386 -arch ppc -o ../src/pd g_canvas.o g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o d_fft.o d_array.o d_global.o d_delay.o d_resample.o x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o x_time.o x_acoustics.o x_net.o x_qlist.o x_gui.o x_list.o d_soundfile.o s_midi_pm.o s_audio_pa.o s_audio_pablio.o s_audio_paring.o ../portaudio/src/common/pa_allocation.o ../portaudio/src/common/pa_converters.o ../portaudio/src/common/pa_cpuload.o ../portaudio/src/common/pa_dither.o ../portaudio/src/common/pa_front.o ../portaudio/src/common/pa_process.o ../portaudio/src/common/pa_skeleton.o ../portaudio/src/common/pa_stream.o ../portaudio/src/common/pa_trace.o ../portaudio/src/common/pa_debugprint.o ../portaudio/src/common/pa_ringbuffer.o ../portaudio/src/os/unix/pa_unix_util.o ../portaudio/src/os/mac_osx/pa_mac_hostapis.o ../portaudio/src/hostapi/coreaudio/pa_mac_core.o ../portaudio/src/hostapi/coreaudio/pa_mac_core_blocking.o ../portaudio/src/hostapi/coreaudio/pa_mac_core_utilities.o ../portmidi/pm_mac/pmmac.o ../portmidi/pm_mac/pmmacosxcm.o ../portmidi/pm_common/pmutil.o ../portmidi/pm_common/portmidi.o ../portmidi/porttime/ptmacosx_cf.o d_fft_mayer.o d_fftroutine.o -ldl -lm -lpthread cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DHAVE_LIBDL -DMACOSX -DHAVE_UNISTD_H -I/usr/X11R6/include -I../portaudio/include -I../portaudio/src/common -I../portaudio/src/os/mac_osx/ -I../portmidi/pm_common -I../portmidi/pm_mac -I../portmidi/porttime -DUSEAPI_PORTAUDIO -DPA19 -DPA_USE_COREAUDIO -DNEWBUFFER -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -Wno-error -O2 -o ../src/pd-watchdog s_watchdog.c ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status lipo: can't open input file: /var/folders/TH/THjm5UAnEZSSB-y6nQY-6++++TI/-Tmp-//cc5Eh2ZJ.out (No such file or directory) make: *** [../src/pd-watchdog] Error 1
anyway, according to http://www.miscdebris.net/blog/2007/11/30/compiling-universal-binaries-in-ma... the following did the trick: sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o but then, Error in startup script: couldn't read file "../bin/pd-gui.tcl": no such file or directory weird, pd-gui.tcl is in src. what's the startup script? marius.
On Aug 26, 2009, at 8:23 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 7:41 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 5:14 PM, marius schebella wrote: > Hans-Christoph Steiner wrote: >> A complete rewrite of Pd's GUI is starting to be usable.
>> Miller has accepted the core of this code into his repo for
>> 0.43. Now we need to get the whole thing done! There is now
>> a branch for continuing off of Miller's initial 0.43 commit
>> here: >> http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... > > no configure?? > marius. read the page a little closer: http://puredata.info/dev/PdGuiRewritei fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd- gui-rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/ 0.43': 302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me
errors, too. marius.Doh sorry, put the wrong link there, please try again:)
doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" - DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" - DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 - DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 - DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 - DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 - DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1
-DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 - DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 - DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 - DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 - DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 - DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 - DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 - DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1
-DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 - DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 - DHAVE_STRTOL=1 -I. -I. -I/sw/include -I../portmidi/pm_common -I../ portmidi/porttime -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd"
-DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" - DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 - DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 - DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 - DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 - DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1
-DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 - DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 - DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 - DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 - DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 - DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 - DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 - DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1
-DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 - DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 - DHAVE_STRTOL=1 -DPD -DUSEAPI_PORTAUDIO -I../portaudio/include - DMACOSX -g -O2 -MT pd-s_audio_pa.o -MD -MP -MF ".deps/pd- s_audio_pa.Tpo" -c -o pd-s_audio_pa.otest -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po";
else rm -f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi s_audio_pa.c:72: error: syntax error before '*' token s_audio_pa.c: In function 'pa_lowlevel_callback': s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use in
this function) s_audio_pa.c:80: error: (Each undeclared identifier is reported
only once s_audio_pa.c:80: error: for each function it appears in.) s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in
this function) s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in
this function) s_audio_pa.c: In function 'pa_open_callback': s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first
use in this function) s_audio_pa.c:118: error: syntax error before 'instreamparams' s_audio_pa.c:153: error: 'instreamparams' undeclared (first use in
this function) s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use
in this function) s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream'
makes pointer from integer without a cast s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: error: too few arguments to function
'Pa_OpenStream' s_audio_pa.c: In function 'pa_getdevs': s_audio_pa.c:420: error: 'struct <anonymous>' has no member named
'hostApi' s_audio_pa.c:427: error: 'struct <anonymous>' has no member named
'hostApi' make[2]: *** [pd-s_audio_pa.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2marius.
Weird... which platform are you on? I've build this thing from
scratch many times on Ubuntu, Debian, and Mac OS X/Intel.still leopard, no snow yet... 10.5.8. I guess I am doing something wrong..
I get nothing more than a warning (I mean no error) from ./configure config.status: WARNING: 'makefile.in' seems to ignore the -- datarootdir setting and a slightly different error with the old
build systemcd ../obj; cc -Wl -framework CoreAudio -framework AudioUnit
-framework AudioToolbox -framework Carbon -framework
CoreMIDI -arch i386 -arch ppc -o ../src/pd g_canvas.o g_graph.o
g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o
g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o
g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o
g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o
m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o
s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o
d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o
d_math.o d_fft.o d_array.o d_global.o d_delay.o d_resample.o
x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o
x_time.o x_acoustics.o x_net.o x_qlist.o x_gui.o x_list.o
d_soundfile.o s_midi_pm.o s_audio_pa.o s_audio_pablio.o
s_audio_paring.o ../portaudio/src/common/pa_allocation.o ../ portaudio/src/common/pa_converters.o ../portaudio/src/common/ pa_cpuload.o ../portaudio/src/common/pa_dither.o ../portaudio/src/ common/pa_front.o ../portaudio/src/common/pa_process.o ../portaudio/ src/common/pa_skeleton.o ../portaudio/src/common/pa_stream.o ../ portaudio/src/common/pa_trace.o ../portaudio/src/common/ pa_debugprint.o ../portaudio/src/common/pa_ringbuffer.o ../portaudio/ src/os/unix/pa_unix_util.o ../portaudio/src/os/mac_osx/ pa_mac_hostapis.o ../portaudio/src/hostapi/coreaudio/ pa_mac_core.o ../portaudio/src/hostapi/coreaudio/ pa_mac_core_blocking.o ../portaudio/src/hostapi/coreaudio/ pa_mac_core_utilities.o ../portmidi/pm_mac/pmmac.o ../portmidi/ pm_mac/pmmacosxcm.o ../portmidi/pm_common/pmutil.o ../portmidi/ pm_common/portmidi.o ../portmidi/porttime/ptmacosx_cf.o
d_fft_mayer.o d_fftroutine.o -ldl -lm -lpthread cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno- parentheses -Wno-switch -DHAVE_LIBDL -DMACOSX -DHAVE_UNISTD_H -I/usr/ X11R6/include -I../portaudio/include -I../portaudio/src/ common -I../portaudio/src/os/mac_osx/ -I../portmidi/ pm_common -I../portmidi/pm_mac -I../portmidi/porttime - DUSEAPI_PORTAUDIO -DPA19 -DPA_USE_COREAUDIO -DNEWBUFFER -isysroot / Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -Wno- error -O2 -o ../src/pd-watchdog s_watchdog.c ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status lipo: can't open input file: /var/folders/TH/THjm5UAnEZSSB-y6nQY-6+++ +TI/-Tmp-//cc5Eh2ZJ.out (No such file or directory) make: *** [../src/pd-watchdog] Error 1anyway, according to http://www.miscdebris.net/blog/2007/11/30/compiling-universal-binaries-in-ma... the following did the trick: sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o /Developer/ SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o but then, Error in startup script: couldn't read file "../bin/pd-gui.tcl": no
such file or directory weird, pd-gui.tcl is in src. what's the startup script? marius.
Try this:
(delete the link) sudo rm /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/
crt1.10.5.o
and then try the updated build instructions for the old build system,
from scratch:
http://puredata.info/dev/PdGuiRewrite
Thanks for testing, we are almost there!
.hc
Programs should be written for people to read, and only incidentally
for machines to execute.
hi hans, thanks, looks good. here's some feedback... don't know whether you are using a new font, or osx is just replacing the usual font, but the font looks so much better here an error I got, when running a search: bad switch "-all": must be --, -backward, -count, -elide, -exact, -forward, -nocase, or -regexp bad switch "-all": must be --, -backward, -count, -elide, -exact, -forward, -nocase, or -regexp while executing ".pdwindow.text search -all -nocase -- $findstring 0.0" (procedure "dialog_find::ok" line 11) invoked from within "dialog_find::ok .find" (command bound to event) the menubar says "wish" instead of Pd, and has no icon. the only button (dsp) in the pd window won't turn on audio, but does turn audio off, once it's running. undo seems broken, too. I see an open recent menu entry, but it does not display any items. cheers, marius.
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 8:23 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 7:41 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote:
Hans-Christoph Steiner wrote: > On Aug 26, 2009, at 5:14 PM, marius schebella wrote: >> Hans-Christoph Steiner wrote: >>> A complete rewrite of Pd's GUI is starting to be usable.
>>> Miller has accepted the core of this code into his repo for >>> 0.43. Now we need to get the whole thing done! There is now a >>> branch for continuing off of Miller's initial 0.43 commit here: >>> http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... >>> >> >> no configure?? >> marius. > read the page a little closer: http://puredata.info/dev/PdGuiRewritei fail with the first line svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... pd-gui-rewrite
svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd-gui-rewrite/0.43' svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/0.43': 302 Found (http://pure-data.svn.sourceforge.net) hmmm... grabed the tarball from the webpage, but compiling gives me errors, too. marius.
Doh sorry, put the wrong link there, please try again:)
doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" -DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" -DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -I. -I. -I/sw/include -I../portmidi/pm_common -I../portmidi/porttime -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" -DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" -DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DPD -DUSEAPI_PORTAUDIO -I../portaudio/include -DMACOSX -g -O2 -MT pd-s_audio_pa.o -MD -MP -MF ".deps/pd-s_audio_pa.Tpo" -c -o pd-s_audio_pa.o
test -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po"; else rm -f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi s_audio_pa.c:72: error: syntax error before '*' token s_audio_pa.c: In function 'pa_lowlevel_callback': s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use in this function) s_audio_pa.c:80: error: (Each undeclared identifier is reported only once s_audio_pa.c:80: error: for each function it appears in.) s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in this function) s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in this function) s_audio_pa.c: In function 'pa_open_callback': s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first use in this function) s_audio_pa.c:118: error: syntax error before 'instreamparams' s_audio_pa.c:153: error: 'instreamparams' undeclared (first use in this function) s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use in this function) s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream' makes pointer from integer without a cast s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream' makes integer from pointer without a cast s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream' makes integer from pointer without a cast s_audio_pa.c:173: error: too few arguments to function 'Pa_OpenStream' s_audio_pa.c: In function 'pa_getdevs': s_audio_pa.c:420: error: 'struct <anonymous>' has no member named 'hostApi' s_audio_pa.c:427: error: 'struct <anonymous>' has no member named 'hostApi' make[2]: *** [pd-s_audio_pa.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2marius.
Weird... which platform are you on? I've build this thing from scratch many times on Ubuntu, Debian, and Mac OS X/Intel.
still leopard, no snow yet... 10.5.8. I guess I am doing something wrong..
I get nothing more than a warning (I mean no error) from ./configure config.status: WARNING: 'makefile.in' seems to ignore the --datarootdir setting and a slightly different error with the old build system
cd ../obj; cc -Wl -framework CoreAudio -framework AudioUnit -framework AudioToolbox -framework Carbon -framework CoreMIDI -arch i386 -arch ppc -o ../src/pd g_canvas.o g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o s_path.o s_entry.o s_audio.o s_midi.o d_ugen.o d_ctl.o d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o d_fft.o d_array.o d_global.o d_delay.o d_resample.o x_arithmetic.o x_connective.o x_interface.o x_midi.o x_misc.o x_time.o x_acoustics.o x_net.o x_qlist.o x_gui.o x_list.o d_soundfile.o s_midi_pm.o s_audio_pa.o s_audio_pablio.o s_audio_paring.o ../portaudio/src/common/pa_allocation.o ../portaudio/src/common/pa_converters.o ../portaudio/src/common/pa_cpuload.o ../portaudio/src/common/pa_dither.o ../portaudio/src/common/pa_front.o ../portaudio/src/common/pa_process.o ../portaudio/src/common/pa_skeleton.o ../portaudio/src/common/pa_stream.o ../portaudio/src/common/pa_trace.o ../portaudio/src/common/pa_debugprint.o ../portaudio/src/common/pa_ringbuffer.o ../portaudio/src/os/unix/pa_unix_util.o ../portaudio/src/os/mac_osx/pa_mac_hostapis.o ../portaudio/src/hostapi/coreaudio/pa_mac_core.o ../portaudio/src/hostapi/coreaudio/pa_mac_core_blocking.o ../portaudio/src/hostapi/coreaudio/pa_mac_core_utilities.o ../portmidi/pm_mac/pmmac.o ../portmidi/pm_mac/pmmacosxcm.o ../portmidi/pm_common/pmutil.o ../portmidi/pm_common/portmidi.o ../portmidi/porttime/ptmacosx_cf.o d_fft_mayer.o d_fftroutine.o -ldl -lm -lpthread cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -DHAVE_LIBDL -DMACOSX -DHAVE_UNISTD_H -I/usr/X11R6/include -I../portaudio/include -I../portaudio/src/common -I../portaudio/src/os/mac_osx/
-I../portmidi/pm_common -I../portmidi/pm_mac -I../portmidi/porttime -DUSEAPI_PORTAUDIO -DPA19 -DPA_USE_COREAUDIO -DNEWBUFFER -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -Wno-error -O2 -o ../src/pd-watchdog s_watchdog.c ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status lipo: can't open input file: /var/folders/TH/THjm5UAnEZSSB-y6nQY-6++++TI/-Tmp-//cc5Eh2ZJ.out (No such file or directory) make: *** [../src/pd-watchdog] Error 1anyway, according to http://www.miscdebris.net/blog/2007/11/30/compiling-universal-binaries-in-ma...
the following did the trick: sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o but then, Error in startup script: couldn't read file "../bin/pd-gui.tcl": no such file or directory weird, pd-gui.tcl is in src. what's the startup script? marius.
Try this:
(delete the link) sudo rm /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o and then try the updated build instructions for the old build system, from scratch:
http://puredata.info/dev/PdGuiRewrite
Thanks for testing, we are almost there!
.hc
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
On Aug 27, 2009, at 3:25 AM, marius schebella wrote:
hi hans, thanks, looks good. here's some feedback... don't know whether you are using a new font, or osx is just
replacing the usual font, but the font looks so much better here an error I got, when running a search: bad switch "-all": must be --, -backward, -count, -elide, -exact, - forward, -nocase, or -regexp bad switch "-all": must be --, -backward, -count, -elide, -exact, - forward, -nocase, or -regexp while executing ".pdwindow.text search -all -nocase -- $findstring 0.0" (procedure "dialog_find::ok" line 11) invoked from within "dialog_find::ok .find" (command bound to event)
Bug! Thanks. I must have used something not supported by Tcl/Tk 8.4.
the menubar says "wish" instead of Pd, and has no icon.
Yeah, that happens when you run it like ./pd on Mac OS X
the only button (dsp) in the pd window won't turn on audio, but does
turn audio off, once it's running.
Bug... thanks for reporting.
undo seems broken, too.
Not implemented yet :) Should be pretty easy tho.
I see an open recent menu entry, but it does not display any items.
It doesn't save currently, we need to figure out how the GUI should
save preferences first. So right now, its Open Recent for this
session only.
.hc
cheers, marius.
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 8:23 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 7:41 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
On Aug 26, 2009, at 6:43 PM, marius schebella wrote: > Hans-Christoph Steiner wrote: >> On Aug 26, 2009, at 5:14 PM, marius schebella wrote: >>> Hans-Christoph Steiner wrote: >>>> A complete rewrite of Pd's GUI is starting to be usable.
>>>> Miller has accepted the core of this code into his repo for
>>>> 0.43. Now we need to get the whole thing done! There is
>>>> now a branch for continuing off of Miller's initial 0.43
>>>> commit here: >>>> http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... >>> >>> no configure?? >>> marius. >> read the page a little closer: http://puredata.info/dev/PdGuiRewrite > > i fail with the first line > svn co http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-gui-rewrit... > pd-gui-rewrite > svn: PROPFIND request failed on '/viewvc/pure-data/branches/pd- > gui-rewrite/0.43' > svn: PROPFIND of '/viewvc/pure-data/branches/pd-gui-rewrite/ > 0.43': 302 Found (http://pure-data.svn.sourceforge.net) > hmmm... > grabed the tarball from the webpage, but compiling gives me
> errors, too. > marius. Doh sorry, put the wrong link there, please try again:)doh, still getting errors... portaudio?
if gcc -DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" - DPACKAGE_VERSION="0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" - DPACKAGE_BUGREPORT="" -DPACKAGE="pd" -DVERSION="0.41.4" - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 - DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 - DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 - DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 - DSTDC_HEADERS=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 - DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 - DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 - DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 - DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 - DHAVE_UNISTD_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 - DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 - DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 - DRETSIGTYPE=void -DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 - DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 - DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 - DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 - DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -I. -I. -I/sw/ include -I../portmidi/pm_common -I../portmidi/porttime - DPACKAGE_NAME="pd" -DPACKAGE_TARNAME="pd" -DPACKAGE_VERSION= "0.41.4" -DPACKAGE_STRING="pd\ 0.41.4" -DPACKAGE_BUGREPORT= "" -DPACKAGE="pd" -DVERSION="0.41.4" -DSTDC_HEADERS=1 - DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 - DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 - DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 - DHAVE_DLFCN_H=1 -DHAVE_LIBDL=1 -DHAVE_LIBM=1 -DSTDC_HEADERS=1 - DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FCNTL_H=1 - DHAVE_LIMITS_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 - DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_SOCKET_H=1 - DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_UNISTD_H=1 - DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 - DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 - DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DRETSIGTYPE=void - DHAVE_DUP2=1 -DHAVE_FLOOR=1 -DHAVE_GETCWD=1 - DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_MEMMOVE=1 - DHAVE_MEMSET=1 -DHAVE_POW=1 -DHAVE_REGCOMP=1 -DHAVE_SELECT=1 - DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRERROR=1 - DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DPD - DUSEAPI_PORTAUDIO -I../portaudio/include -DMACOSX -g -O2 -MT
pd-s_audio_pa.o -MD -MP -MF ".deps/pd-s_audio_pa.Tpo" -c -o pd- s_audio_pa.otest -f 's_audio_pa.c' || echo './'
s_audio_pa.c;
then mv -f ".deps/pd-s_audio_pa.Tpo" ".deps/pd-s_audio_pa.Po";
else rm -f ".deps/pd-s_audio_pa.Tpo"; exit 1; fi s_audio_pa.c:72: error: syntax error before '*' token s_audio_pa.c: In function 'pa_lowlevel_callback': s_audio_pa.c:80: error: 'framesPerBuffer' undeclared (first use
in this function) s_audio_pa.c:80: error: (Each undeclared identifier is reported
only once s_audio_pa.c:80: error: for each function it appears in.) s_audio_pa.c:85: error: 'inputBuffer' undeclared (first use in
this function) s_audio_pa.c:98: error: 'outputBuffer' undeclared (first use in
this function) s_audio_pa.c: In function 'pa_open_callback': s_audio_pa.c:118: error: 'PaStreamParameters' undeclared (first
use in this function) s_audio_pa.c:118: error: syntax error before 'instreamparams' s_audio_pa.c:153: error: 'instreamparams' undeclared (first use
in this function) s_audio_pa.c:159: error: 'outstreamparams' undeclared (first use
in this function) s_audio_pa.c:173: warning: passing argument 5 of 'Pa_OpenStream'
makes pointer from integer without a cast s_audio_pa.c:173: warning: passing argument 7 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: warning: passing argument 8 of 'Pa_OpenStream'
makes integer from pointer without a cast s_audio_pa.c:173: error: too few arguments to function
'Pa_OpenStream' s_audio_pa.c: In function 'pa_getdevs': s_audio_pa.c:420: error: 'struct <anonymous>' has no member
named 'hostApi' s_audio_pa.c:427: error: 'struct <anonymous>' has no member
named 'hostApi' make[2]: *** [pd-s_audio_pa.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2marius.
Weird... which platform are you on? I've build this thing from
scratch many times on Ubuntu, Debian, and Mac OS X/Intel.still leopard, no snow yet... 10.5.8. I guess I am doing something wrong..
I get nothing more than a warning (I mean no error) from ./configure config.status: WARNING: 'makefile.in' seems to ignore the -- datarootdir setting and a slightly different error with the old
build systemcd ../obj; cc -Wl -framework CoreAudio -framework
AudioUnit -framework AudioToolbox -framework Carbon - framework CoreMIDI -arch i386 -arch ppc -o ../src/pd g_canvas.o
g_graph.o g_text.o g_rtext.o g_array.o g_template.o g_io.o
g_scalar.o g_traversal.o g_guiconnect.o g_readwrite.o g_editor.o
g_all_guis.o g_bang.o g_hdial.o g_hslider.o g_mycanvas.o
g_numbox.o g_toggle.o g_vdial.o g_vslider.o g_vumeter.o m_pd.o
m_class.o m_obj.o m_atom.o m_memory.o m_binbuf.o m_conf.o m_glob.o
m_sched.o s_main.o s_inter.o s_file.o s_print.o s_loader.o
s_path.o s_entry.o s_audio.o s_midi.o d_ugen.o d_ctl.o
d_arithmetic.o d_osc.o d_filter.o d_dac.o d_misc.o d_math.o
d_fft.o d_array.o d_global.o d_delay.o d_resample.o x_arithmetic.o
x_connective.o x_interface.o x_midi.o x_misc.o x_time.o
x_acoustics.o x_net.o x_qlist.o x_gui.o x_list.o d_soundfile.o
s_midi_pm.o s_audio_pa.o s_audio_pablio.o s_audio_paring.o ../ portaudio/src/common/pa_allocation.o ../portaudio/src/common/ pa_converters.o ../portaudio/src/common/pa_cpuload.o ../portaudio/ src/common/pa_dither.o ../portaudio/src/common/pa_front.o ../ portaudio/src/common/pa_process.o ../portaudio/src/common/ pa_skeleton.o ../portaudio/src/common/pa_stream.o ../portaudio/src/ common/pa_trace.o ../portaudio/src/common/pa_debugprint.o ../ portaudio/src/common/pa_ringbuffer.o ../portaudio/src/os/unix/ pa_unix_util.o ../portaudio/src/os/mac_osx/pa_mac_hostapis.o ../ portaudio/src/hostapi/coreaudio/pa_mac_core.o ../portaudio/src/ hostapi/coreaudio/pa_mac_core_blocking.o ../portaudio/src/hostapi/ coreaudio/pa_mac_core_utilities.o ../portmidi/pm_mac/pmmac.o ../ portmidi/pm_mac/pmmacosxcm.o ../portmidi/pm_common/pmutil.o ../ portmidi/pm_common/portmidi.o ../portmidi/porttime/ptmacosx_cf.o
d_fft_mayer.o d_fftroutine.o -ldl -lm -lpthread cc -g -O2 -DPD -Wall -W -Wstrict-prototypes -Wno-unused -Wno- parentheses -Wno-switch -DHAVE_LIBDL -DMACOSX -DHAVE_UNISTD_H -I/ usr/X11R6/include -I../portaudio/include -I../portaudio/ src/common -I../portaudio/src/os/mac_osx/ -I../portmidi/ pm_common -I../portmidi/pm_mac -I../portmidi/porttime - DUSEAPI_PORTAUDIO -DPA19 -DPA_USE_COREAUDIO -DNEWBUFFER -isysroot / Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc - Wno-error -O2 -o ../src/pd-watchdog s_watchdog.c ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status ld: library not found for -lcrt1.10.5.o collect2: ld returned 1 exit status lipo: can't open input file: /var/folders/TH/THjm5UAnEZSSB-y6nQY-6+ +++TI/-Tmp-//cc5Eh2ZJ.out (No such file or directory) make: *** [../src/pd-watchdog] Error 1anyway, according to http://www.miscdebris.net/blog/2007/11/30/compiling-universal-binaries-in-ma... the following did the trick: sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o / Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.10.5.o but then, Error in startup script: couldn't read file "../bin/pd-gui.tcl":
no such file or directory weird, pd-gui.tcl is in src. what's the startup script? marius.Try this: (delete the link) sudo rm /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/ crt1.10.5.o and then try the updated build instructions for the old build
system, from scratch: http://puredata.info/dev/PdGuiRewrite Thanks for testing, we are almost there! .hc ---------------------------------------------------------------------------- Programs should be written for people to read, and only incidentally for
machines to execute.
- from Structure and Interpretation of Computer Programs
The arc of history bends towards justice. - Dr. Martin Luther
King, Jr.