[L2Ork-dev] updating cyclone

[Jonathan Wilkes]

> 2017-03-21 3:44 GMT-03:00 Albert Graef <aggraef at gmail.com>:



I have to agree with Alexandre there, the built-in comment object is somewhat lacking in features. Cyclone's new comment object would certainly be nice to have. But I guess that it still needs to be ported to Purr Data? Then it all boils down to whether anyone is volunteering to do that.


> I had a response with an attachment that didnt go through...
> Well, I just wanted to highlight how cyclone's comment is nothing new, it's been there in cyclone for over a decade. It was just never included in Pd-l2ork or Purr Data. We haven't really touched it yet (at least for adding features, we have made a couple of fixes).
> I'm just trying to say nothing really changed with us... and my idea was that we were to include it in Purr Data eventually, but not just right now. 

> As far as documentation goes. I made an adaptation where it doesn't really look relevantly different. So no problem there, other than there are 2 different sets of docs... but what can you do?
> I'm just not willing to exclude comment from the cyclone pack or take it out the documentation just because it hasn't been ported to Purr Data...
> Now, if there's an idea that cyclone/comment shouldn't be ported to Purr Data, well, now that's something else... but even if that is so... we could still make the new cyclone get into Purr Data, in the same way as the old cyclone (which already had comment) is!
The problem is more general than cyclone/comment.  The problem is that if you let users specify arbitrary font families and sizes in pixels/points/etc., you can 
no longer guarantee that the patch will display without collisions on all platforms.  (I explained the details about why this is so on the 80-message font thread on 
the Pd user list-- it boils down to the fact that the font renderer on one platform cannot know what the maximum height/width will be on other platforms.)
The right way to solve this is to use the tools designed for reflowing text-- the tk text widget in tcl/tk, and HTML in Purr Data.  Figuring out how to 
display that alongside a pd canvas is a difficult problem, though.
I don't have a problem porting cyclone/comment, but it's just not a very robust solution to rich text in patches.  And I'm absolutely sure 
that users won't understand the drawback that I wrote in the parentheses above.

> I just hope this doesn't get in the way of us trying to build it and ship it ASAP in the next Purr Data release.
It won't get in the way.  But there's going to be a release soon, before I am able to port your new cyclone repo to Purr Data.
-Jonathan

> cheers_______________________________________________
L2Ork-dev mailing list
L2Ork-dev at disis.music.vt.edu
http://disis.music.vt.edu/listinfo/l2ork-dev

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20170321/e0b6bd58/attachment-0001.html>