All this is of course because being supercollider native from OSX most
users are on OSX and therefore the usage and development of SwingOSC is
not as intense as we all would dream. Having one single GUI solution for
all platforms would boost and easy enormously the development of more
complex GUIs in supercollider.
I understand your point.
But because of my interests, I see the main problems not in GUI (I'm happy with SwingOSC) but in the Document class, which is extremely powerful on OSX, but, in fact, it is fundamentally an OSX class.
So you can't rely on Document to have cross-platform behavior. Which is a pity, because you can use it to specify different UI modes (e.g. key bindings).
More, Document is strongly related to help file system. Help files are generated by Cocoa HTML writer. Sources are awful and incredibly dirty.
E.g.:
<meta name="Generator" content="Cocoa HTML Writer">
<meta name="CocoaVersion" content="824.44">
<style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 18.0px Helvetica}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; color: #0000ff}
p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
p.p5 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco}
p.p6 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco; color: #982c23}
p.p7 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Helvetica}
p.p8 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Monaco; min-height: 16.0px}
p.p9 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco; min-height: 12.0px}
p.p10 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco; color: #982c23; min-height: 12.0px}
p.p11 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco; color: #0024a4}
p.p12 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Monaco; color: #606060}
span.s1 {color: #000000}
span.s2 {color: #0000ff}
span.s3 {color: #0024a4}
span.s4 {color: #bf0000}
span.s5 {color: #0024e4}
span.s6 {color: #436b2e}
span.s7 {color: #606060}
span.Apple-tab-span {white-space:pre}
</style>
</head>
<body>
<p class="p1"><b>Array</b></p>
<p class="p2"><br></p>
<p class="p3"><span class="s1"><b>Superclass: </b><a href="ArrayedCollection.html"><b>ArrayedCollection</b></a></span></p>
<p class="p2"><br></p>
<p class="p4">Arrays are ArrayedCollections whose slots may contain any object. Arrays have a fixed maximum size beyond which they cannot grow. For expandable arrays, use the <a href="List.html"><span class="s2">List</span></a> class.</p>
<p class="p2"><br></p>
The help file generation system I developed originates from the OSX html generation mechanism. Really tricky, while it would be much easier to have a minimal content structure and a (minimal) css.
Marije knows perfectly what I am seeing, as I still found no time to improve linux compatibility.
This is a big issue, IMHO.
So, maybe for a general solution would be nice to consider both issued (GUI and IDE/help files)
Best
-a-
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--------------------------------------------------
"
Think of it as seasoning
. noise [salt] is boring
. F(blah) [food without salt] can be boring
. F(noise, blah) can be really tasty
"
(Ken Perlin on noise)
_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users