Re: [Sc-devel] RC5

[felix <felix@xxxxxxxxxxxxxxxxxxx>]

the instructions are to place the quarks folder into app support.

so if you followed the directions, then its not possible for the quarks folder to be anywhere else.

other than still on the disk image.

so there's nowhere to copy it from.

On Feb 11, 2008 3:48 PM, ronald kuivila <rkuivila@xxxxxxxxxxxx> wrote:

Hi Felix,

So, if the quarks folder does not exist in app support, it could test for the preloaded folder and ask if you want it copied into app support...

Would that take care of it?

RJK

On Feb 11, 2008, at 9:38 AM, felix wrote:

there are a few more complications to it then that.

for the moment its best to have them place it in app support, named quarks, right where the svn quarks would be.

thus is you already have svn quarks, you will know there is a conflict.

if you change to svn quarks later, you will know you have to resolve the conflict.

the alternative is to have several quarks folders around ... hilarity ensues.

On Feb 10, 2008 2:18 PM, ronald kuivila <rkuivila@xxxxxxxxxxxx> wrote:

Hi all,

  With the release including Quarks, how are users supposed to configure them?  Do they need to drag them into

the userApplicationSupport dir?  If so, it might be better to allow them to be runnable out of the box.  This would be easy to do,

it is simply a matter of having the directory be an instance variable rather than a call to Platform.userSupportDir.  

Here is a patch that illustrates what I mean: 

+LocalQuarks {

*new { | path, parent |

^super.newCopyArgs((path ?? { QuarksDir.dir ++ "/quarks"}), parent)

}

}

QuarksDir {

classvar <>dir;

*initClass { 

Class.initClassTree( Platform );

Class.initClassTree( String );

if (File.exists("preloadedQuarks") ) {

dir = "".absolutePath ++ "/preloadedQuarks";

} { 

dir = Platform.userAppSupportDir;

}

}

}

RJK