I'm with Hans -- e.g., 'list' where there's a whole slew of functionalities masquerading as a single class (and sharing a help file), but in which you only need one object for each type of use, e.g., "list nth".
cheers M On Fri, Nov 18, 2011 at 01:23:12PM -0500, Mathieu Bouchard wrote: > Le 2011-11-17 à 21:17:00, Hans-Christoph Steiner a écrit : > > >The last sentence is the key there. They should not all do these > >things in their own disparate ways. If the objects stick to > >common, well-established idioms, then all these objects will be > >easy use. Just imagine the help patch of an [info] object with so > >many messages vs the help patch for each object and its specific > >task. > > Yes, it's much more convenient to open 20 tiny help patches to have > an overview, then have to open 1 big help patch that contains all of > the info in one place... ;) > > try again. > > ______________________________________________________________________ > | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list