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.

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 ;)

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.

Also midiclock is a good idea :)


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.

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 !