I would love to have everything well documented, but alas,
documentation takes a long time. So I think the best way to spend
time is to first get the code working well, then document it.
Otherwise, you have to change the code AND the documentation to fix it.
There is lots of discussion in the list archives on these topics.
Personally, I have written a lot of documentation while I was
figuring out some code. I think that works well, and I encourage
others to try to do that.
.hc
On Apr 15, 2008, at 3:26 PM, marius schebella wrote:
Hans-Christoph Steiner wrote:
Lots of people contribute, but I am the person who manages the
releases. Any help is welcome. The path/import/declare stuff is
currently a half-complete effort of Miller's and mine.is there a page where this idea is documented? how is it supposed
to work in the future? I still don't know. will I have to include
declare in every patch that I write???Basically up until recently, I was pursing Pd-extended as a proof
of concept for building libraries as standalone binaries in
directories instead of all compiled into one binary. I think that
clearly works, so now it is time to clean things up into a
coherent package.It doesn't work for abbreviations.
I document what I can here: http://puredata.info/docs/developer/
thanks.
I don't really know what else needs to be documented. One way to
find out is when people start to contribute, then they find
shortcomings that we can fill in.well, it would be nice if there was some documentation of which
libraries and objects are included, how to handle all the path
problems, which paths and libs are loaded by default how to load
the other libs/externals. filessystem layout, platform
compatibility, which libraries do *not* work on which os. what
additional features you added to pd-extended (advanced helpmenu,
advanced tcltk interface (colorscheme...), differences in
shortcuts, closing, ..... all that.marius.
.hc On Apr 15, 2008, at 2:15 PM, marius schebella wrote:
Hi, is it true, that only hans is working on the pd-extended
releases? are there other maintainers? I got the impression in the past that pd-extended is very useful
(and I personally use it a lot), but development for it is also very
cryptical and almost hidden like a secret. and often things are implemented
that seem to be good ideas, but do not really work (like the whole path/import stuff). maybe hans, if you could provide more information and documentation about pd-extended and how the whole integration of libraries
works then more people would be able to help you and development would be more consistent. what is the direction that you want to go? for me pd-extended is the attempt to create a pd distribution that includes as many as possible external libraries in addition to pd vanilla. I love most of the things in pd-ext, although there is
still a lot of work that needs to be done... marius.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
------- I have the audacity to believe that peoples everywhere can
have three meals a day for their bodies, education and culture for
their minds, and dignity, equality and freedom for their
spirits. - Martin Luther King, Jr.
All information should be free. - the hacker ethic