[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sc-devel] SC3.2 RC 3 and SC 3.2



Single generic user accounts are not particularly good practice for
computer labs, but I take your point - the suggested change would
break things for you so we definitely shouldn't do it.

Thanks
Dan

2008/2/2, ronald kuivila <rkuivila@xxxxxxxxxxxx>:
> Hi Dan,
>
> This may be a 3.3 issue, but, frankly, I do not like any of these
> approaches.
>
> It seems to me that there should support for booting one copy of SC3
> from different directories of startup files.
>
> This would make the book-keeping associated with multiple project
> much easier both for personal and shared machines
>
> As a particular example, machines at Wesleyan are configured so that
> everyone uses a single generic user account (it authenticates
> over the network but drops you into a "labuser" account).  So it is
> currently impossible to fiddle with startup without affecting
> everyone else's work.  The current solution is to simply make another
> copy of SC3 and redirect startup to the SC3 directory.
> Of course this generates an enormous mess almost instantly...
>
>
>
> RJK
>
>
>
>
> On Feb 2, 2008, at 5:52 AM, Dan Stowell wrote:
>
> > OK, I think I agree with you here Scott, and the change should be
> > painless. I will commit the following today unless anyone talks me out
> > of it:
> >
> > Index: SuperCollider3/build/SCClassLibrary/Platform/osx/OSXPlatform.sc
> > ===================================================================
> > --- SuperCollider3/build/SCClassLibrary/Platform/osx/OSXPlatform.sc
> > (revision 7195)
> > +++ SuperCollider3/build/SCClassLibrary/Platform/osx/OSXPlatform.sc
> > (working copy)
> > @@ -1,7 +1,7 @@
> >  OSXPlatform : UnixPlatform
> >  {
> >         name { ^\osx }
> > -       startupFiles { ^#["~/scwork/startup.rtf"] }
> > +       startupFiles { ^#["~/Library/Application
> > Support/SuperCollider/startup.rtf"] }
> >         startup {
> >                 Document.implementationClass.startup;
> >                 // make server window
> >
> >
> >
> >
> >
> >
> > 2008/2/2, Scott Wilson <i@xxxxxxxxxxxxxx>:
> >>  I'm not proposing to put a 'work' directory in the App Support
> >> dir, just
> >> the startup file.
> >>
> >> Putting a work directory there (or anywhere) presupposes how
> >> people want to
> >> organise their work, which is basically what I object to with ~/
> >> scwork/. I
> >> (and I suspect many other people) have nothing in my scwork directory
> >> besides a startup file. As I mentioned before, I don't like things
> >> which
> >> create directories for me in ~/ and I feel the same about ~/
> >> Documents/. 2
> >> cents.
> >>
> >> App support seems to me the right place for a configuration file,
> >> at least
> >> on OSX anyway.
> >>
> >> recordings/ I'm less fussed about, although putting it in ~/Music/
> >> sort of
> >> implies you're recording pieces, which is not the only way the record
> >> functionality is used. There's also something to be said for
> >> putting things
> >> in fewer places rather than more.
> >>
> >> S.
> >>
> >>
> >> On 1 Feb 2008, at 23:35, felix wrote:
> >>
> >>
> >> I'd actually vote for the chosen work directory, which should be
> >> whatever
> >> Document.dir is set to.
> >>
> >> and the default for that...
> >>
> >> well we risk annoying people by moving it.  it they already have an
> >> ~/scwork.
> >> we could check for its existence. and if it doesn't exist then:
> >>
> >>
> >> I like
> >> ~/Documents/SuperCollider
> >>
> >> which is also standard for applications to do.
> >> Acrobat User Data
> >> eFax Messenger
> >>  Microsoft User Data
> >> etc.
> >>
> >> it wouldn't affect me (for example) because no matter what the
> >> default, I
> >> would set it in my own startup to where I already have it.
> >>
> >> the problem I see with the application support directory is that
> >> it doesn't
> >> seem like its for normal everyday work.  it really is out of the
> >> way.  its
> >> for plug ins, extensions and the like.  or app cacheing.  but not
> >> for people
> >> to work out of.
> >>
> >> so its good for the synth defs I think.
> >>
> >> for recordings I still like
> >> ~/Music/SuperCollider/recordings
> >>  or we could put it also in the chosen work directory wish would
> >> leave less
> >> of a mess.
> >>
> >> you have to consider that some people will play around with this
> >> and then
> >> forget about it.  they shouldn't have 3 large folders to get rid of.
> >>
> >>
> >>
> >> -cx
> >>
> >>
> >>
> >>
> >> On Feb 2, 2008 12:33 AM, Scott Wilson <i@xxxxxxxxxxxxxx> wrote:
> >>> What about the notion of moving the startup file and recordings
> >>> folders to platform specific app support directories?
> >>>
> >>> This wouldn't be problematic to do I think.
> >>>
> >>> S.
> >>> _______________________________________________
> >>> Sc-devel mailing list
> >>> Sc-devel@xxxxxxxxxxxxxxx
> >>> http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
> >>>
> >>
> >>
> >>
> >> _______________________________________________
> >> Sc-devel mailing list
> >> Sc-devel@xxxxxxxxxxxxxxx
> >> http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
> >>
> >> _______________________________________________
> >> Sc-devel mailing list
> >> Sc-devel@xxxxxxxxxxxxxxx
> >> http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
> >>
> >>
> >
> >
> > --
> > http://www.mcld.co.uk
> > _______________________________________________
> > Sc-devel mailing list
> > Sc-devel@xxxxxxxxxxxxxxx
> > http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
> >
>
> _______________________________________________
> Sc-devel mailing list
> Sc-devel@xxxxxxxxxxxxxxx
> http://lists.create.ucsb.edu/mailman/listinfo/sc-devel
>


-- 
http://www.mcld.co.uk