I think there is a whole day of reading on the squeak list now about backwards forward compatibility if you change the meaning of FileSystem default defaultDirectory and have it return a URI, that would break things, or assumptions etc. Personally I'd think it should be URI defaultFileSystemDirectory and others, temp, document, vm, etc.. Er so FileSystem default defaultDirectory would really do ^URI defaultFileSystemDirectory absolutePath On 1-Jul-09, at 4:01 PM, Stephen Pair wrote:
On Wed, Jul 1, 2009 at 5:32 PM, Michael Rueger <m.rueger@acm.org> wrote: Igor Stasenko wrote:
how then i could write a 'FileDirectory default' in terms of URIs? 'file://.' asURI ?
No, you would still write FileDirectory default :-)
But then you would do something like
(FileDirectory default uri resolveRelativePath: 'myDir/images') directory
I think I would obliterate FileDirectory and write something more like "FileSystem default defaultDirectory", which would answer a URI.
- Stephen
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================