There is much that can and should be done. Here's some ideas ranked
into of difficulty:
helpfiles, manuals, examples, etc then write code to index it all,
and create a GUI to navigate that content
At this point, I think it is mostly a waste of time to do constant
little workarounds like moving around objects. We should be putting
our scarce resources towards real improvements, not temporary fixes,
IMHO.
.hc
On May 17, 2008, at 12:54 PM, Rich E wrote:
Working here too. Thanks, again it looks great!
I wanted to mention that one of the most intimidating things for me
when I was first learning about all the externals in pd is that
nothing was working by default and I didn't know how to get it
working. Pd-extended has come a long way since then, and now I
know how to look for missing paths, where to find sources and
compile, etc., but I am sure there are many others that give up on
pd-extended when things seem 'broken'.I guess what I am suggesting is that something, anything, be one so
that the help files can find the externals and the externals can
find the help files, by default. If there are issues about
organization that are later to be sought out, maybe externals like
[pvoc~] should be moved into flatspace until a better solution is
committed?rich
On Thu, May 15, 2008 at 6:58 AM, Hans-Christoph Steiner
hans@eds.org wrote:On May 15, 2008, at 5:37 AM, Rich E wrote:
The May 9th build doesn't have the same problem. I've also tried
the newest nightly build on both Gutsy and Hardy, they have the
same "stacksmashing" error.Today's build gets rid of the stacksmashing error (for me at
least). Please test! :Dhttp://autobuild.puredata.info/auto-build/2008-05-15/
So now that I've ben searching around in the new Pd-extended, here
are some things I noticed:
- The new hotkeys (clear console, open help browser) don't work.
Fixed.
- dragging the pd console window (making it longer) makes the
panel longer too, even if it is already big enough (which it is by
defaultYeah, that could be a lot nicer...
.hc
- bsaylor's [pvoc~] and [partconv~] externals cannot be found
because the path isn't added by libdir (the rest of the externals
in the folder appear to be in extra/flatspace, so they can be
found. adding /usr/local/lib/pd/extra/bsaylor to the paths list
fixes this.That is as far as I've looked.. time to start messing around
more. It looks great, by the way!Also, I would like to learn how to commit the changes that I know
how to do so Hans doesn't have to bother, but I am having problems
with svn right now. I posted another message about this.regards, rich
On Wed, May 14, 2008 at 12:52 AM, IOhannes m zmoelnig
zmoelnig@iem.at wrote: Hans-Christoph Steiner wrote:You can now file bug reports from the Help menu in Pd-extended. Please file a bug report for this.
i cannot: "/usr/bin/gnome-open 'http://sourceforge.net/tracker/?func=add&group_id=55736&atid=478070' Error showing url: There was an error launching the default action command associated with this location."
i guess i should file a bug-report :-)
fgmasdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
All information should be free. - the hacker ethic
"Free software means you control what your computer does. Non-free
software means someone else controls that, and to some extent
controls you." - Richard M. Stallman