Hello,
Below are links to the first alpha release of the GUI port of Pd-l2ork.

The GUI has been ported from tcl/tk to nw.js. The biggest visual improvements are ability to zoom in and out of a canvas, smoother animation of canvas objects (like the PacData game), user-friendly editing inside msg/obj boxes, and a more flexible API for visualizing data structures.

I've nicknamed it "Purr Data", because cats.

This is mainly a bug-collecting release. It should be decent enough to do some basic patching for awhile before hitting a bug. Some caveats up front: OSX is missing Gem and PDP, and both OSX and Windows are missing some pd-l2ork-related externals.

Bug tracker is here:
https://puredata.osuosl.org/jwilkes/purr-data/issues

Alpha builds are listed below (I'm abusing gitlab to distribute these, so some may have a zip within a zip):
OSX x_64 - https://puredata.osuosl.org/purr-data-binaries/osx-64-alpha0/repository/archive.zip?ref=master

Ubuntu 15.10 x_64 - https://puredata.osuosl.org/purr-data-binaries/ubuntu-15.10-64-alpha0/repository/archive.zip?ref=master

Ubuntu 14.04 x_64 - https://puredata.osuosl.org/purr-data-binaries/ubuntu-14.04-64-alpha0/repository/archive.zip?ref=master

Ubuntu 14.04 i386 - https://puredata.osuosl.org/purr-data-binaries/ubuntu-14.04-32-alpha0/repository/archive.zip?ref=master

Debian Jessie x_64 - https://puredata.osuosl.org/purr-data-binaries/debian-jessie64-alpha0/repository/archive.zip?ref=master

Debian Jessie i386 - https://puredata.osuosl.org/purr-data-binaries/debian-jessie32-alpha0/repository/archive.zip?ref=master

Windows 32-bit - https://puredata.osuosl.org/purr-data-binaries/win32-alpha0/repository/archive.zip?ref=master

Whoop! Will this install safely along side the previous L2Ork release? (Ubuntu 14.04 64).

@LiamG: Unfortunately, no. But for the next alpha I'll look into changing the paths and executable name to make that possible.

Hi,

tried to install it, but my Jessie couldn't resolve dependencies, any clue?

nau@lapdell:~/Bureau$ sudo dpkg -i pd-l2ork-x86_64-jessie-a0.deb 
(Reading database ... 166599 files and directories currently installed.)
Preparing to unpack pd-l2ork-x86_64-jessie-a0.deb ...
Unpacking pd-l2ork (20160406) over (20160406) ...
dpkg: dependency problems prevent configuration of pd-l2ork:
 pd-l2ork depends on tcl; however:
  Package tcl is not installed.
 pd-l2ork depends on tk; however:
  Package tk is not installed.
 pd-l2ork depends on libglew-dev; however:
  Package libglew-dev is not installed.
 pd-l2ork depends on libmagick++-dev; however:
  Package libmagick++-dev is not installed.
 pd-l2ork depends on libftgl2; however:
  Package libftgl2 is not installed.
 pd-l2ork depends on libgmerlin0; however:
  Package libgmerlin0 is not installed.
 pd-l2ork depends on libgmerlin-avdec1; however:
  Package libgmerlin-avdec1 is not installed.
 pd-l2ork depends on libavifile-0.7c2; however:
  Package libavifile-0.7c2 is not installed.
 pd-l2ork depends on libmpeg3-1 | libmpeg3-2; however:
  Package libmpeg3-1 is not installed.
  Package libmpeg3-2 is not installed.
 pd-l2ork depends on libquicktime2; however:
  Package libquicktime2 is not installed.
 pd-l2ork depends on libfftw3-3; however:
  Package libfftw3-3 is not installed.
 pd-l2ork dep
dpkg: error processing package pd-l2ork (--install):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for systemd (215-17+deb8u4) ...
Errors were encountered while processing:
 pd-l2ork

Thanks!
Nau

@nau: if you have gdebi installed, you can try this:
sudo gdebi pd-l2ork-x86_64-jessie-a0.deb

gdebi will resolve the dependencies for you.

(I see there are some dev packages in the dependency chain, which is weird. So I made an entry in the bug tracker about that.)

Great job ! It works fine on OsX 10.11.4. Did you change all the tcl/tk methods (sys_gui & sys_vgui) or is it some kind of wrapper that translates the messages from PD to JS ?

@Pierre-Guillot: I changed all the tcl/tk methods:

https://puredata.osuosl.org/jwilkes/purr-data#gui-messaging-specification

So I've got a handfulof js-specific wrappers in s_inter.c. But everywhere else I'm using parameterized messages that follow the pd_vmess pattern.

@jancsika said:

@nau: if you have gdebi installed, you can try this:
sudo gdebi pd-l2ork-x86_64-jessie-a0.deb

gdebi will resolve the dependencies for you.

(I see there are some dev packages in the dependency chain, which is weird. So I made an entry in the bug tracker about that.)

Thanx Jancsika, but here is the problem : gdebi claims that package "libjack-jackd2-0" has to be removed, but my system apparently needs this package very much (as if I try to remove it Synaptic tells me that a long list of applications relies on it, like gnome itself, gstreamer etc).

Nau

Thanks, I'll look into this.

Great and refreshing idea! Is it possible to use nw.js GUI as drop-in replacement for pd-gui? Do I need the whole l2ork distribution? I work on Arch Linux and use vanilla Pd.

@sidec said:

Great and refreshing idea! Is it possible to use nw.js GUI as drop-in replacement for pd-gui? Do I need the whole l2ork distribution? I work on Arch Linux and use vanilla Pd.

Unfortunately it's not as simple as that. The tcl/tk code in Vanilla isn't limited to pd-gui.tcl, nor even to the tcl directory. It is also spread throughout the C code.

Someone on Pd list mentioned Manjaro as a user-friendly alternative to Arch. So I'll try to fire up a VM and release an alpha for that. (Maybe without all the externals...)

cool, I will give it a try as soon as you make this release available. So I stay tuned.

@software-materialism Ok, try the following:

1. Download https://puredata.osuosl.org/purr-data-binaries/manjaro-64-alpha0/repository/archive.zip?ref=master
2. Unzip the zip
3. untar the tar (sorry for the double compression here)
4. navigate to pd/src
5. If you're on amd_64, you can just do
   sudo make install then type pd-l2ork to run once it's installed

If not, do this in pd/src:
aclocal
autoconf
./configure
make
make install

(It's a debug versions of nw.js so the install is rather large.)

f <-- I typed a funch of f's here because this forum overlays a footer over the bottom of the textarea, making it impossible to see what I'm typing here. Is there some way to turn that off?

Thanks, it works both binary you provide and recompiled with jack support.
It looks awesome!
What version of Pd is that? I'm asking because it seems that [array] object is absent and [netreceive] has old syntax.
I have no experience with aur packages, but I hope to find some spare time to get into it and make PKGBUILD in the future.

It's based off Pd-l2ork. I've backported most of the commits, but Pd-l2ork itself is still missing some functionality from the most recent versions of Vanilla. That includes [array] and some other recent changes.

If you wouldn't mind making some bug reports about what you find missing, I'd appreciate it:
https://puredata.osuosl.org/jwilkes/purr-data/issues

I'm not sure I'll be able to add [array] before an initial stable release, but I'll try.

I made an issue. Does it make big difference in terms of development to base purr-data on upstream vanilla?

@software-materialism: Thanks for the bug report. I don't know if I'll be able to add those objects for the first release, but I do want to get them into Pd-l2ork very soon.

If I based off Vanilla I'd lose all the benefits of Pd-l2ork. It's difficult to exaggerate the impact of that. Presets, infinite undo, all kinds of bug fixes going back over a decade, etc.

Hello, I just installed the Ubuntu 15.10 version and it works great. Is it possible to change the zoomlevel via messages? I'd like to have two windows and control the zoomlevel of the second window with a slider.
Would something like this work?

[zoomlevel 1(
[s pd-mypatch.pd]

@sensn said:

Hello, I just installed the Ubuntu 15.10 version and it works great. Is it possible to change the zoomlevel via messages? I'd like to have two windows and control the zoomlevel of the second window with a slider.
Would something like this work?

[zoomlevel 1(
[s pd-mypatch.pd]

Could you describe a bit more about your use case?

For example: what is the benefit of changing the zoom level from within the patch vs. using the menu/shortcut key?

I'd like to make a pianoroll which can be zommed in and out from another window.
That was the first case which came to my mind. Acually I think being able to call these functions from whithin a patch window (like [hcs/sys_gui]) could be usefull for a lot of GUI applications.
You could have a "tool-window" where the user can zoom several other open windows without having to pay attention on which one is focused.

Same would be nice for scrolling

@sensn said:

I'd like to make a pianoroll which can be zommed in and out from another window.
That was the first case which came to my mind. Acually I think being able to call these functions from whithin a patch window (like [hcs/sys_gui]) could be usefull for a lot of GUI applications.
You could have a "tool-window" where the user can zoom several other open windows without having to pay attention on which one is focused.

Same would be nice for scrolling

Ah, I see. I think patch-level zoom is the wrong tool for that job. It'd be more flexible to have a "widget" level zoom, plus the ability to define a viewport for that widget (i.e., a rectangular region that demarcates the visible boundaries of the object). Unfortunately gop canvas doesn't do a very good job of either-- objects can extend past the bounds of the gop border, which consequently makes zooming very clunky and error-prone.

If you want an example of "widget" level zooming, click Help->Help Browser, Then in the search box, type "notes". Scroll down to the last link and click it to open a demo with a little data structure staff.

I don't have a good solution for a clipping path, though.