is it possible/feasible to add a switch so that "old" objects don't get
replaced by the new ones? e.g. by analysing the parameters of the creation
objects? if so, and someone delivers the code for this (I don't know how
to do it myself), there might be a better chance of these objects making
it into vanilla. (or not?)
Well, backwards compatibility can have reasonable limitations and
perhaps this is one.On Jan 13, 2014, at 6:18 AM, i go bananas hard.off@gmail.com wrote:
i very much doubt miller will include stuff in vanilla that's not
backwards compatible. seeing as how these objects don't even work withmy (relatively) recent 0.42.5 version, i can't see how they'd pass.
On Mon, Jan 13, 2014 at 6:00 PM, Pierre Guillot
guillotpierre6@gmail.com wrote:Hi, I may have been sensitive, I needed 2 days break, sorry. If we focus
on the important facts, I received really constructive feedbacksand I've been able to improve the library for the next release.
Joao suggestions :- The properties window will have a fixed size.
- We can set (in the code) if we want a color picker, checkbox, menu
or textfield for each property.
- The id name becomes receive symbol and there's also an send symbol.
IOhannes suggestions :
- The c/tcl library is now named CicmWrapper (The repository name will
change with the next release)
- If it seems better to change the libray name, Chocolate can become
CicmGUI ?
About the right click during runmode, It's possible to change it but I
don't really like it. Do you think that's really important ?To include in Pd-ext, it's possible to only include Chocolate, I just
have to replace all the c.prepend and c.loadmess with prepend andinit. I received mails and some users like c.patcherargs and the
double click of the coffee objects but they can download and add the
library manually.To include in Vanilla, you're right, the best is
to ask to Miller.
If we want to "replace" the vanilla GUIs, two suggestions for the
moment :- We keep the the vanilla GUIs and we just replace the
shortcut, we won't have any problem to load previous patchs and users
will >>>use the new GUI for their new patchs (Secure and easy to do,
we can also have an option to replace or not the vanilla shortcuts).
- We overwrite the vanilla classes then every objects will replaced
but the users will lose the properties (size, font, color, etc...). Another idea is to add a menu option or to offer 2 libraries with one
that overwrite classes.Cheers
2014/1/10 Jonathan Wilkes jancsika@yahoo.com
On 01/10/2014 12:50 PM, Dan Wilcox wrote:
I don't have any plans, I was only responding in a hypothetical
manner. I'm busy on a show right now and can't do >>>>>pd dev. A
better person to ask is Miller ...I must have misunderstood-- the way you wrote that made it sound like
there is a process by which the community gets things >>>>included
into Pd Vanilla. If such a process existed wouldn't one of the
"dupes" IOhannes cites already be included in Pd Vanilla >>>>after
over a decade now?Instead, I think Pierre has taken the only sensible approach to
making a library that works with both Pd-Vanilla and Pd-extended.>>You simply code up the stuff that's been missing forever-- some
of it probably in less time than it takes to respond to questions
>>about "dupes". Then you ship the library, and it "just works"
without users having to find other libraries.
-Jonathan
On Jan 10, 2014, at 12:48 PM, Jonathan Wilkes jancsika@yahoo.com
wrote:What is your plan for getting the necessary features into Vanilla
so that such dupes are no longer >>>>>>necessary to include in a
library like this?>>>>>>>>> --------
Dan Wilcox @danomatika danomatika.com robotcowboy.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Dan Wilcox @danomatika danomatika.com robotcowboy.com