Purr Data release candidate 1! (Don't have a semver figured out yet...)
please report lots of bugs to https://git.purrdata.net/jwilkes/purr-data/issues
Binaries:
rpi Raspbian (armv7l): https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-arm...
Debian Jessie 32-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-i68...
Debian Jessie 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
Ubuntu 14.04 32-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-i38...
Ubuntu 14.04 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
Ubuntu 16.04 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
Windows with 64-bit GUI: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
OSX 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
OSX 64-bit Out of Date Style (10.8): https://git.purrdata.net/jwilkes/purr-data-binaries/raw/master/purr-data-x86...
awesome to see this close to a final release
i see some guis seem to be fine, but still no cyclone/comment, are there plans to work it out?
cheers
2016-11-24 14:16 GMT-02:00 Jonathan Wilkes via Pd-list <pd-list@lists.iem.at
:
Purr Data release candidate 1! (Don't have a semver figured out yet...)
- fix for iemgui colors not getting properly updated
- allow opening a file at OSX startup
- fix weird behavior when dragging files onto a Pd patch
- remove more debugging statements
- fix slider display error
- fix "Select All" on OSX
- fix allowed characters in atom box dialog
- forward console key events to Pd
- change [draw group] to [draw g]
- add fit width/height/optimal zoom shortcuts
- fix consistency bug with [draw]
- put "Window" menu in the customary position next to "Help" menu
- fix clipboard operations for patch snippets
- some translation fixes
- some Pd-l2ork fixes backported
- improvements for opening files in the same instance
please report lots of bugs to https://git.purrdata.net/jwilkes/purr-data/issues
Binaries:
rpi Raspbian (armv7l): https://git.purrdata.net/ jwilkes/purr-data-binaries/raw/master/purr-data-armv7l-raspbian-rc1.deb
Debian Jessie 32-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-i686-debian_jessie-rc1.deb
Debian Jessie 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64-debian_jessie-rc1.deb
Ubuntu 14.04 32-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-i386-ubuntu_14.04-rc1.deb
Ubuntu 14.04 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64-ubuntu-14.04-rc1.deb
Ubuntu 16.04 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64-ubuntu-16.04-rc1.deb
Windows with 64-bit GUI: https://git.purrdata.net/ jwilkes/purr-data-binaries/raw/master/purr-data-x86_64-windows-rc1.zip
OSX 64-bit: https://git.purrdata.net/jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64-osx-rc1.dmg
OSX 64-bit Out of Date Style (10.8): https://git.purrdata.net/ jwilkes/purr-data-binaries/raw/master/purr-data-x86_64-osx-10.8-rc1.dmg
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
awesome to see this close to a final release
i see some guis seem to be fine, but still no cyclone/comment, are there plans to work it out?
I don't have plans to port it for the initial release, but I'd definitely still like to port it.
Question: Have you made substantial improvements to comment.c in your fork?
The code I've been working from is from the old "miXed" directory. In that code, comment.c is so complicated it would probably take 10 times longer to port it than just starting from scratch with the Max docs. Also, I'm not sure whether that code is trying to match Max's interface or whether it's simply an ad hoc approach to getting arbitrary fonts to display and interact in a Pd canvas. If it's the latter then I don't want to waste time on it.
Another reason for putting it off is that I still haven't figured out a sane approach to handling arbitrary fonts in a diagram where everything is absolutely positioned. In fact I only have a minimally-workable approach to handling a single, mono- spaced font across platforms. For example, there was a change somewhere in the Gnu/Linux font-stack (relatively) recently that renders fonts (or at least DejaVu Sans Mono) noticeably wider than before. So Windows, OSX, and old Gnu/Linux would render a particular line of text sized at "12px" within less than a single pixel of each other. The new Gnu/Linux font stack (seen in Ubuntu 16.04 and some recent Arch) rendered the same text about 7 pixels wider. Worse, the newer Gnu/Linux font stack quantizes the "px" sizes such that the next smallest size is noticeably smaller. So in Ubuntu 16.04 I have to compromise by keeping the object box the same size and having some extra padding at the end-- otherwise users of that OS could end up tightly spacing their object chains in ways that cause overlaps on the other platforms. So... I'd like to get a handle on that mess first, then handling arbitrary font families-- as in cyclone/comment-- will hopefully be easier and less prone to bugs. -Jonathan
cheers
2016-11-24 14:16 GMT-02:00 Jonathan Wilkes via Pd-list pd-list@lists.iem.at:
Purr Data release candidate 1! (Don't have a semver figured out yet...)
please report lots of bugs to https://git.purrdata.net/ jwilkes/purr-data/issues
Binaries:
rpi Raspbian (armv7l): https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-armv7l- raspbian-rc1.deb
Debian Jessie 32-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-i686- debian_jessie-rc1.deb
Debian Jessie 64-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- debian_jessie-rc1.deb
Ubuntu 14.04 32-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-i386- ubuntu_14.04-rc1.deb
Ubuntu 14.04 64-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- ubuntu-14.04-rc1.deb
Ubuntu 16.04 64-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- ubuntu-16.04-rc1.deb
Windows with 64-bit GUI: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- windows-rc1.zip
OSX 64-bit: https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- osx-rc1.dmg
OSX 64-bit Out of Date Style (10.8): https://git.purrdata.net/ jwilkes/purr-data-binaries/ raw/master/purr-data-x86_64- osx-10.8-rc1.dmg ______________________________ _________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
2016-11-24 20:20 GMT-02:00 Jonathan Wilkes jancsika@yahoo.com:
Have you made substantial improvements to comment.c in your fork?
so, here's the deal, we haven't touched it, but we really needed to. I wanted to at least add a properties window and we really need to fix some issues it has in cross platforms
Also, I'm not sure whether that code is trying to match Max's interface or whether it's simply an ad hoc approach to getting arbitrary fonts to display and interact in a Pd canvas. If it's the latter then I don't want to waste time on it.
It's not a good clone, and it is only related to old Max 4.0 - we don't think it is a good idea to make it really compliant with the latest Max, it'd be kinda crazy, but no matter how good of a clone it is and which version it is related to, it is only a comment, it displays text on the patch.
Another reason for putting it off is that I still haven't figured out a sane approach to handling arbitrary fonts in a diagram where everything is absolutely positioned. In fact I only have a minimally-workable approach to handling a single, mono- spaced font across platforms. For example, there was a change somewhere in the Gnu/Linux font-stack (relatively) recently that renders fonts (or at least DejaVu Sans Mono) noticeably wider than before. So Windows, OSX, and old Gnu/Linux would render a particular line of text sized at "12px" within less than a single pixel of each other. The new Gnu/Linux font stack (seen in Ubuntu 16.04 and some recent Arch) rendered the same text about 7 pixels wider.
Worse, the newer Gnu/Linux font stack quantizes the "px" sizes such that the next smallest size is noticeably smaller. So in Ubuntu 16.04 I have to compromise by keeping the object box the same size and having some extra padding at the end-- otherwise users of that OS could end up tightly spacing their object chains in ways that cause overlaps on the other platforms.
So... I'd like to get a handle on that mess first, then handling arbitrary font families-- as in cyclone/comment-- will hopefully be easier and less prone to bugs.
well, it seems some of the issues are exactly what we're facing now...
cheers
so, here's the deal, we haven't touched it, but we really needed to. I wanted to at least add a properties window and we really need to fix some issues it has in cross platforms
well, it seems some of the issues are exactly what we're facing now...
yep, take my attached screenshot of the comment help file running on pd vanilla. I've noticed that Alex's new help files (obv) look fine on his machine, but then when it comes to my machine running Xubuntu,.. looks less than fine... weird sizes and placement of comments. Especially that red one...
Derek
Another reason for putting it off is that I still haven't figured out a sane approach to handling arbitrary fonts in a diagram where everything is absolutely positioned. In fact I only have a minimally-workable approach to handling a single, mono- spaced font across platforms. For example, there was a change somewhere in the Gnu/Linux font-stack (relatively) recently that renders fonts (or at least DejaVu Sans Mono) noticeably wider than before. So Windows, OSX, and old Gnu/Linux would render a particular line of text sized at "12px" within less than a single pixel of each other. The new Gnu/Linux font stack (seen in Ubuntu 16.04 and some recent Arch) rendered the same text about 7 pixels wider. Worse, the newer Gnu/Linux font stack quantizes the "px" sizes such that the next smallest size is noticeably smaller. So in Ubuntu 16.04 I have to compromise by keeping the object box the same size and having some extra padding at the end-- otherwise users of that OS could end up tightly spacing their object chains in ways that cause overlaps on the other platforms. So... I'd like to get a handle on that mess first, then handling arbitrary font families-- as in cyclone/comment-- will hopefully be easier and less prone to bugs.
well, it seems some of the issues are exactly what we're facing now...
I think those issues are impossible to solve for displaying arbitrary fonts in a diagram like a Pd patch, and especially for arbitrary fonts in multi-line text. The user simply won't be able to predict whether or not there will be collisions on someone else's platform (or even if those fonts aren't available, which fonts will get chosen).
I'm all for porting cyclone/comment for the sake of Max compatibility. But I'd strongly advise against using cyclone/comment in any patch that's supposed to be used cross-platform (aside from its own help patch, of course).
-Jonathan
cheers