2016-01-06 19:21 GMT+01:00 Dan Wilcox danomatika@gmail.com:
Sounds good.
I have all built in pd & iem guis implemented, feature rich. Too bad your versions currently can’t be back ported to DroidParty. In this case, I feel it would make sense to work with Chris, et al. to separate the DroidParty core from it’s specific Android UI implementation and then both projects could use the pd UI work y’all have put in. At least that’s my 2 cents and *small* fear of fragmentation. It’s not like there are tons of Pd developers. On the other hand, different projects have different focuses of course.
I agree fragmentation is sometimes an issue, but I'm sure we can minimize it so it's a goo idea to start discuss it all together.
My focus so far is to maintain compatibility with Pure Data itself and include DroidParty & RjDj compatibility. To that end I’ve spent perhaps too much time the last few weeks implementing and checking against the DroidParty tests. Maybe I’m being too thorough ;)
I loved rjdj and wrote a bunch of patches for it but sadly it doesn't exist anymore so we didn't really take rjdj compatibility into account. We are pretty much compatible with droidparty (you can use a patch from droidparty in ppp you just won't benefit from the clock), we kept the support for svg theming too.
We were not really sure of what kind of gui we will need in the future, hence our decision to ensure the gui from pd-vanilla was available with ppp and also open up the possibilities for overrides with code.
I think touch is needed for a touchscreen ... so we kept it (but how to prototype a multi-touch app in pd-vanilla ?) , and taplist is a good way to select an element in list with a very small on screen size so it's pretty usefull so we kept it too.
I think/hope that the community will tell us what they need in terms of gui :)
One of my further plans, after getting the app out, is to separate the PdParty core (libpd, OSC, MIDI, pd UI implementations) from the specific app UI so it can be used as a basis for building other apps as well.
That's mainly what we did, that makes it hard to port back new stuff :) I think it's good idea to work in that direction.
Also midiclock is a good idea :)
Cheers !
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com
On Jan 6, 2016, at 11:08 AM, Berenger Recoules < berenger.recoules@gmail.com> wrote:
Hi Dan,
To sum up we've made a break from the fork, ppp is very different in the sense that it's used to publish binaries, and we didn't keep the base functionnality of a list of patches that you can load at will : one project = one patch = one app. It's not made to replace droidparty at all, it's more about synching standalone apps built with pd with one another, and hopefully any other kind of midi gear.
You can check out this page : http://b2renger.github.io/PdDroidPublisher/2015/11/04/List_abstractions.html It explains which abstractions we kept from droidparty and what we added (mainly the clock one - that is interfaced with a java implementation of a raw midi clock) - still some stuff to document there ... but it will give you an overview.
For the gui part, we added support for the missing gui objects of pd (arrays, radios ...), made a system to use tabs, and a system to override behavior and looks with java code - those overrides are meant to be written by contributors/developp and can be used with a simple declaration when publishing (in java again).
To port all of this stuff back to droidparty would be a lot of work.
Concerning you issue thread :
- ribbon : how is it really different from slider ? it only has a
different look right ?
- the knob would be a square slider in pd with a graphical and behavior
override when used in android (we have an implementation but it's not used anywhere).
- In android the taplist can also open an android-style popup for you to
choose from instead of cycling through a list at each tap, in pd the taplist is the same as it was (plus the fix about symetric messages, and we added a label - for gui theming purposes).
- we dropped the features to add images to android menus, we will use the
android menu later on.
- we kept the touch as is.
Cheers !