hi, one of the side effects of pdpedia is that with the overview of all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :( but anyway, I created a new category called gui which will include all the graphical UI objects. http://wiki.puredata.info/en/Category:gui hans, can I do something to get the images running? marius.
Hallo, marius schebella hat gesagt: // marius schebella wrote:
one of the side effects of pdpedia is that with the overview of all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :(
Is this a problem of the objects or isn't it one of your "-path/-helppath" setup?
Frank Barknecht _ ______footils.org_ __goto10.org__
not only a settings problem. many objects are broken. at least on os x. and for some it is not possible to rightclick, like entry or popup. the rest is a settings problem, true. marius.
Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
one of the side effects of pdpedia is that with the overview of all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :(
Is this a problem of the objects or isn't it one of your "-path/-helppath" setup?
Ciao
You can browse for help patches in the help browser.
But yes, things are a mess. :D
.hc
On Oct 3, 2007, at 8:28 AM, marius schebella wrote:
not only a settings problem. many objects are broken. at least on
os x. and for some it is not possible to rightclick, like entry or popup. the rest is a settings problem, true. marius.Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
one of the side effects of pdpedia is that with the overview of
all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :(Is this a problem of the objects or isn't it one of your "-path/-helppath" setup?
Ciao
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
News is what people want to keep hidden and everything else is
publicity. - Bill Moyers
IOhannes m zmoelnig wrote:
marius schebella wrote:
not only a settings problem. many objects are broken. at least on os x.
broken in which way?
show up in the pd-extended release but cannot be created.
and for some it is not possible to rightclick, like entry or popup.
is this "broken behaviour" or just "missing feature"?
missing feature. marius.
about pdpedia features: Could there be a good way to cross-index (in pdpedia) with bug reports, and show how they were fixed? Most user problems get posted to pd-list, and any unresolved issues get placed in the reports. A "comment" section is likely to be plagued with ambiguous user problems and non-unified treatment, I think.
Chuck
On 10/3/07, marius schebella marius.schebella@gmail.com wrote:
IOhannes m zmoelnig wrote:
marius schebella wrote:
not only a settings problem. many objects are broken. at least on os x.
broken in which way?
show up in the pd-extended release but cannot be created.
and for some it is not possible to rightclick, like entry or popup.
is this "broken behaviour" or just "missing feature"?
missing feature. marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi, I think of pdpedia more like an encyclopedia. but I think a discussion forum for bugs and comments beside the mailing list is a good idea. the cross linking can by done by linking to mails in the pd-list archives and vice versa. still, I think bugs should be mentioned in the pdpedia pages. marius.
Charles Henry wrote:
about pdpedia features: Could there be a good way to cross-index (in pdpedia) with bug reports, and show how they were fixed? Most user problems get posted to pd-list, and any unresolved issues get placed in the reports. A "comment" section is likely to be plagued with ambiguous user problems and non-unified treatment, I think.
Chuck
On 10/3/07, marius schebella marius.schebella@gmail.com wrote:
IOhannes m zmoelnig wrote:
marius schebella wrote:
not only a settings problem. many objects are broken. at least on os x.
broken in which way?
show up in the pd-extended release but cannot be created.
and for some it is not possible to rightclick, like entry or popup.
is this "broken behaviour" or just "missing feature"?
missing feature. marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, marius schebella hat gesagt: // marius schebella wrote:
I think of pdpedia more like an encyclopedia. but I think a discussion forum for bugs and comments beside the mailing list is a good idea. the cross linking can by done by linking to mails in the pd-list archives and vice versa. still, I think bugs should be mentioned in the pdpedia pages.
I think, care should be taken to not duplicate the bug tracker. People or at least I won't be reading pdpedia all the time just like people don't read Wikipedia only when needed. So if pdpedia authors find a bug, they should report it to the bug tracker and then make a link to that, so everyone on pdpedia knows this bug is reported.
Frank Barknecht _ ______footils.org__
yes, maybe I was not not precise, but that's what I had in mind. I just wanted to say, that if we know about a bug then we could put a note about the bug on the wikipage of that objectclass (for information purpose, but not for discussion purpose). marius.
Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
I think of pdpedia more like an encyclopedia. but I think a discussion forum for bugs and comments beside the mailing list is a good idea. the cross linking can by done by linking to mails in the pd-list archives and vice versa. still, I think bugs should be mentioned in the pdpedia pages.
I think, care should be taken to not duplicate the bug tracker. People or at least I won't be reading pdpedia all the time just like people don't read Wikipedia only when needed. So if pdpedia authors find a bug, they should report it to the bug tracker and then make a link to that, so everyone on pdpedia knows this bug is reported.
Ciao
yes, maybe I was not not precise, but that's what I had in mind. I just wanted to say, that if we know about a bug then we could put a note about the bug on the wikipage of that objectclass (for information purpose, but not for discussion purpose). marius.
if someone leaves a note somewhere, it might go unnoticed for a while (or
for ever), right? How about giving the user 2 choices: to give the link to
file a bug report and explain how to do it, or if the user is a novice/in
a hurry (that happens a lot), inform the administrator of that language
about the bug (who will file the bug report). One 3rd option could be
informing the author, but according to my experience the authors have more
to do, so it is more efficient to make an official bug report.
On Oct 4, 2007, at 2:02 AM, Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
I think of pdpedia more like an encyclopedia. but I think a
discussion forum for bugs and comments beside the mailing list is a good
idea. the cross linking can by done by linking to mails in the pd-list archives and vice versa. still, I think bugs should be mentioned in the
pdpedia pages.I think, care should be taken to not duplicate the bug tracker. People or at least I won't be reading pdpedia all the time just like people don't read Wikipedia only when needed. So if pdpedia authors find a bug, they should report it to the bug tracker and then make a link to that, so everyone on pdpedia knows this bug is reported.
The pdpedia bugs section and the bug tracker serve quite different
purposes. The bug tracker is for information leading to fixing a
bug. The pdpedia bug section is for documenting the existance of
know bugs and known workarounds.
A pdpedia page should be a complete resource all about that given
object, or whatever. If the wikipedians avoided duplicating things
that exist, wikipedia would be tiny and not very useful. The real
advantage comes in have one resource that gives you an overview of
all you need to know.
.hc
Ciao
Frank Barknecht _
______footils.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war
on terrorism. - retired U.S. Army general, William Odom
Hans-Christoph Steiner wrote:
The pdpedia bugs section and the bug tracker serve quite different
purposes. The bug tracker is for information leading to fixing a
bug. The pdpedia bug section is for documenting the existance of
know bugs and known workarounds.
i see: the bug tracker is contra bugs, while the pdpedia bug section is pro bugs :-)
fmasd.r IOhannes
On Oct 5, 2007, at 12:27 PM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
The pdpedia bugs section and the bug tracker serve quite different purposes. The bug tracker is for information leading to fixing a bug. The pdpedia bug section is for documenting the existance of know bugs and known workarounds.
i see: the bug tracker is contra bugs, while the pdpedia bug
section is pro bugs :-)fmasd.r IOhannes
Hmm, I see it as fixing bugs vs. dealing with bugs.
.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:
A pdpedia page should be a complete resource all about that given
object, or whatever. If the wikipedians avoided duplicating things
that exist, wikipedia would be tiny and not very useful. The real
advantage comes in have one resource that gives you an overview of
all you need to know.
Which Wikipedia.org is not.
Wikipedia is inherently incomplete and full of errors and will always be that way, which is not a problem unless people aren't aware of these limitations and take for truth what's written on Wikipedia. Pdpedia may be similar: It describes a real world outside of itself (help-files, bugs, etc.) which may be out of sync at every point in time.
Frank Barknecht _ ______footils.org__
On Oct 6, 2007, at 3:07 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
A pdpedia page should be a complete resource all about that given object, or whatever. If the wikipedians avoided duplicating things that exist, wikipedia would be tiny and not very useful. The real advantage comes in have one resource that gives you an overview of all you need to know.
Which Wikipedia.org is not.
Wikipedia is inherently incomplete and full of errors and will always be that way, which is not a problem unless people aren't aware of these limitations and take for truth what's written on Wikipedia. Pdpedia may be similar: It describes a real world outside of itself (help-files, bugs, etc.) which may be out of sync at every point in time.
I should say "gives you overview of what's out there. I don't claim
(and mistakenly wrote) that any source will have "all" the info.
While we are on the topic, if you look at the research, wikipedia has
shown to be basically as accurate as traditional encyclopedias.
Traditional encyclopedias are also full of errors. That's
inevitable. There will never be an publication without errors,
everyone should expect that from any source they read.
All that said, wikipedia is a great resource for quick information.
I think we can make Pdpedia the same.
.hc
kill your television
isn't it possible to make a "comment" section, where such problems can be
indicated?
one of the side effects of pdpedia is that with the overview of all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :( but anyway, I created a new category called gui which will include all the graphical UI objects. http://wiki.puredata.info/en/Category:gui hans, can I do something to get the images running? marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Yes, definitely! This is one of the main reasons why I am interested
in the pdpedia.
.hc
On Oct 3, 2007, at 8:08 AM, João Miguel Pais wrote:
isn't it possible to make a "comment" section, where such problems
can be indicated?one of the side effects of pdpedia is that with the overview of
all the objects there are also a lot of objects that are ~buggy that are not working. especially flatspace makes problems. help-patches are not showing up, many objects cannot be created. :( but anyway, I created a new category called gui which will include
all the graphical UI objects. http://wiki.puredata.info/en/Category:gui hans, can I do something to get the images running? marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Friedenstr. 58 10249 Berlin Deutschland Tel +49 30 42020091 Mob +49 162 6843570 jmmmpais@googlemail.com skype: jmmmpjmmmp http://www.puredata.org/Members/jmmmp IBM Thinkpad R51, XP, Pd-Ext-0.39-2-t5, Pd Van 0.40-t2
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