OSX gui classes
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
OSX gui classes
by nescivi
::
Rate this Message:
Hiho,
The OSX Gui classes are still in the main Class Library, even though they are only usable on OSX. They should be moved to an osx folder. This affects quite a lot of classes, and I am wondering what the preferred way to do it would be. I would propose to create a directory osx under build/SCClassLibrary/Common/GUI/ and move all the files that are concerned in there, in a similar tree as they are now. I am testing right now, if this will give any problems. The mix of OSX only stuff and GUI based stuff is quite confusing right now to sort out all the files... I'm also not sure whether I have all the rights to change directory structure in the svn tree... sincerely, Marije _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
|
|
Re: OSX gui classes
by nescivi
::
Rate this Message:
Hi again,
On Monday 21 April 2008 15:38:01 nescivi wrote: > Hiho, > > The OSX Gui classes are still in the main Class Library, even though they > are only usable on OSX. They should be moved to an osx folder. > > This affects quite a lot of classes, and I am wondering what the preferred > way to do it would be. > > I would propose to create a directory osx under > build/SCClassLibrary/Common/GUI/ > and move all the files that are concerned in there, in a similar tree as > they are now. > > I am testing right now, if this will give any problems. The mix of OSX only > stuff and GUI based stuff is quite confusing right now to sort out all the > files... > > I'm also not sure whether I have all the rights to change directory > structure in the svn tree... It will affect quite a few documents, which will be moved, and some have to have internal bits moved out to separate files; below is a quick overview. It will also affect quarks and other extensions (like SwingOSC), in that they have to have their stuff properly put in osx folders as well, but I think this should be recommended style anyway. I will test my setup like this for the next few days, while I await your reactions. Sincerely, Marije Affected files: M build/SCClassLibrary/crucial/UncoupledUsefulThings/viewExtensions.sc M build/SCClassLibrary/crucial/Gui/gui.sc ! build/SCClassLibrary/Common/OSX must be renamed to: ? build/SCClassLibrary/Common/osx ! build/SCClassLibrary/Common/GUI/SCFreqScope.sc ! build/SCClassLibrary/Common/GUI/PlusGUI/Core/ColorPlusGUI.sc ! build/SCClassLibrary/Common/GUI/PlusGUI/Math/IntegerPlusGUI.sc ! build/SCClassLibrary/Common/GUI/SCInterfaceBuilder ! build/SCClassLibrary/Common/GUI/Stethoscope.sc ! build/SCClassLibrary/Common/GUI/ScopeView.sc (move from SCView.sc of Gradient stuff) ? build/SCClassLibrary/Common/GUI/Base/Gradient.sc ! build/SCClassLibrary/Common/GUI/Base/SCQuartzComposerView.sc ! build/SCClassLibrary/Common/GUI/Base/SCView.sc ! build/SCClassLibrary/Common/GUI/Base/Pen.sc ! build/SCClassLibrary/Common/GUI/Base/GUIScreen.sc ! build/SCClassLibrary/Common/GUI/Base/SCCocoaView.sc ! build/SCClassLibrary/Common/GUI/Base/SCViews2.sc ! build/SCClassLibrary/Common/GUI/Base/Font.sc ! build/SCClassLibrary/Common/GUI/Base/SCSoundFileView.sc ! build/SCClassLibrary/Common/GUI/SCEnvelopeEdit.sc ! build/SCClassLibrary/backwards_compatibility/views.sc _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
|
|
Re: OSX gui classes
by LFSaw
::
Rate this Message:
Hey,
looks good to me; AFAIK as a sf-developer you should be able to "svn mv". kind regards Till On 21.04.2008, at 22:15, nescivi wrote: > Hi again, > > On Monday 21 April 2008 15:38:01 nescivi wrote: >> Hiho, >> >> The OSX Gui classes are still in the main Class Library, even >> though they >> are only usable on OSX. They should be moved to an osx folder. >> >> This affects quite a lot of classes, and I am wondering what the >> preferred >> way to do it would be. >> >> I would propose to create a directory osx under >> build/SCClassLibrary/Common/GUI/ >> and move all the files that are concerned in there, in a similar >> tree as >> they are now. >> >> I am testing right now, if this will give any problems. The mix of >> OSX only >> stuff and GUI based stuff is quite confusing right now to sort out >> all the >> files... >> >> I'm also not sure whether I have all the rights to change directory >> structure in the svn tree... > > > It will affect quite a few documents, which will be moved, and some > have to > have internal bits moved out to separate files; below is a quick > overview. > > It will also affect quarks and other extensions (like SwingOSC), in > that they > have to have their stuff properly put in osx folders as well, but I > think > this should be recommended style anyway. > > I will test my setup like this for the next few days, while I await > your > reactions. > > Sincerely, > Marije > > > Affected files: > > M build/SCClassLibrary/crucial/UncoupledUsefulThings/ > viewExtensions.sc > M build/SCClassLibrary/crucial/Gui/gui.sc > > ! build/SCClassLibrary/Common/OSX > must be renamed to: > ? build/SCClassLibrary/Common/osx > > > ! build/SCClassLibrary/Common/GUI/SCFreqScope.sc > ! build/SCClassLibrary/Common/GUI/PlusGUI/Core/ColorPlusGUI.sc > ! build/SCClassLibrary/Common/GUI/PlusGUI/Math/IntegerPlusGUI.sc > ! build/SCClassLibrary/Common/GUI/SCInterfaceBuilder > ! build/SCClassLibrary/Common/GUI/Stethoscope.sc > ! build/SCClassLibrary/Common/GUI/ScopeView.sc > > (move from SCView.sc of Gradient stuff) > ? build/SCClassLibrary/Common/GUI/Base/Gradient.sc > > ! build/SCClassLibrary/Common/GUI/Base/SCQuartzComposerView.sc > ! build/SCClassLibrary/Common/GUI/Base/SCView.sc > ! build/SCClassLibrary/Common/GUI/Base/Pen.sc > ! build/SCClassLibrary/Common/GUI/Base/GUIScreen.sc > ! build/SCClassLibrary/Common/GUI/Base/SCCocoaView.sc > ! build/SCClassLibrary/Common/GUI/Base/SCViews2.sc > ! build/SCClassLibrary/Common/GUI/Base/Font.sc > ! build/SCClassLibrary/Common/GUI/Base/SCSoundFileView.sc > ! build/SCClassLibrary/Common/GUI/SCEnvelopeEdit.sc > > ! build/SCClassLibrary/backwards_compatibility/views.sc > > _______________________________________________ > Sc-devel mailing list > Sc-devel@... > http://lists.create.ucsb.edu/mailman/listinfo/sc-devel _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
|
|
Re: OSX gui classes
by felix-38
::
Rate this Message:
yes, the directory structure looks good.
the easiest way I know is that you should redo your moving work and do it all using svn mv M build/SCClassLibrary/crucial/UncoupledUsefulThings/viewExtensions.sc
this can be split into two files. some are extensions to SCView classes, and some are extensions to platform neutral classes. M build/SCClassLibrary/crucial/Gui/gui.sc this doesn't look like it has any OS X specific things > ! build/SCClassLibrary/backwards_compatibility/views.sc this I should move into an SC2 compat quark probably nobody uses this anyway On Tue, Apr 22, 2008 at 9:38 AM, LFSaw <lfsaw@...> wrote:
Hey, _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
|
|
Re: OSX gui classes
by James Harkins-2
::
Rate this Message:
Before doing this, I think it would be essential to survey initClass methods for those that try to get information out of the GUI scheme. Linux users without SwingOSC might not be able to complete the language startup sequence...? Unless I'm missing something. hjh On Apr 22, 2008, at 4:52 AM, felix wrote: yes, the directory structure looks good. : H. James Harkins : http://www.dewdrop-world.net .::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..: "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
|
|
Re: OSX gui classes
by nescivi
::
Rate this Message:
Hiho,
On Tuesday 22 April 2008 07:58:44 James Harkins wrote: > Before doing this, I think it would be essential to survey initClass > methods for those that try to get information out of the GUI scheme. > Linux users without SwingOSC might not be able to complete the > language startup sequence...? Unless I'm missing something. as being discussed in another thread, GUI scheme is only set in the startup file on Linux, so initClass methods cannot depend on them anyway, and currently there are no problems there, with everything moved out. > On Apr 22, 2008, at 4:52 AM, felix wrote: > > yes, the directory structure looks good. > > > > the easiest way I know is that you should redo your moving work and > > do it all using svn mv I know. I just wanted to test first without that. > > M build/SCClassLibrary/crucial/UncoupledUsefulThings/ > > viewExtensions.sc > > this can be split into two files. some are extensions to SCView > > classes, and some are extensions to platform neutral classes. That's why I had to modify it. > > M build/SCClassLibrary/crucial/Gui/gui.sc > > this doesn't look like it has any OS X specific things It has extensions for SCView and some others in it. > > > ! build/SCClassLibrary/backwards_compatibility/views.sc > > > > this I should move into an SC2 compat quark > > probably nobody uses this anyway Then the whole backwards_compatibility folder should go into that quark? But still, it would have to be moved there into a special osx folder, so we might as well do that now. So, I'll get this done in the next days. sincerely, Marije _______________________________________________ Sc-devel mailing list Sc-devel@... http://lists.create.ucsb.edu/mailman/listinfo/sc-devel |
| Free Forum Powered by Nabble | Forum Help |