« Return to Thread: OSX gui classes

Re: OSX gui classes

by felix-38 :: Rate this Message:

Reply to Author | View in Thread

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,

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

 « Return to Thread: OSX gui classes