actually, I think this is better:
FreqScope -> SCFreqScopeWindow (since FreqScope always has a window)
that will be less confusing
jostM
jostM wrote:
Ok, then back to my original list using the SC prfix:
Font redirect-> SCFont
Pen redirect-> SCPen
FreqScope redirect-> CocoaFreqScope (SCFreqScope already exists)
Stethoscope redirect-> SCStethoscope
Speech redirect-> SCSpeech
However, I need a better name for the CocoaFreqScope then. FreqScope is
itself a wrapper, but I think that JFreqScope works differently.
SCFreqScopeView sound good? It is a bit confusing, because its base
redirects unintuitively:
FreqScope -> SCFreqScopeView -> JFreqScope
FreqScopeView -> SCFreqScope -> JSCFreqScope
This is for historical reasons then.
jostM
Scott Wilson wrote:
Jan, just pointed out to me that it would CocoaSlider might seem to
imply this:
S.
On 11 Dec 2008, at 11:16, Dan Stowell wrote:
2008/12/11 Julian Rohrhuber <rohrhuber@xxxxxxxxxxxxxx>:
Even though it is inconsistent, maybe it would be better to rename
them Cocoa* rather than SC*, because that's more indicative of what
they're really about.
this is true, but won't it add another layer if you have to rename
SCWindow
to CocoaWindow and yet support old code?
no, I wouldn't propose that. Only for the "new" redirects/renames jost
mentioned in that email.
Dan
Of course the redirector classes could be named SCSomething and then
the
originals CocoaSomething.
Dan
2008/12/11 jostM <sc3@xxxxxxxx>:
OK, I'd like to do this then:
These all will involve changing class names (I will have to adjust
the
docs)
Font redirect-> SCFont
Pen redirect-> SCPen
FreqScope redirect-> CocoaFreqScope (SCFreqScope already exists)
Stethoscope redirect-> SCStethoscope
Speech redirect-> SCSpeech
any objections or comments?
jostM
Dan Stowell wrote:
2008/12/8 jostM <sc3@xxxxxxxx>:
Regarding the scopes: SwingOSC obviously uses a different approach
for
scoping which doesn't require the internal server. There was some
talk
of trying to do something similar in Cocoa, which would be great, but
I don't know what the issues are. If that were done, they could
become
redirect classes themselves (possibly could now anyway), which for
consistency's sake should be our goal I think.
The same goes for Pen and Font, IMO. Since this is the path we're
taking, these should probably just become redirect classes, and the
existing ones just become CocoaPen and CocoaFont.
Other opinions?
S.
yes, this what I was thinking also.
jostM
Me too
Dan
_______________________________________________
sc-dev mailing list
info (subscription, etc.):
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
--
http://www.mcld.co.uk
_______________________________________________
sc-dev mailing list
info (subscription, etc.):
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
--
.
_______________________________________________
sc-dev mailing list
info (subscription, etc.):
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
--
http://www.mcld.co.uk
_______________________________________________
sc-dev mailing list
info (subscription, etc.):
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
|