[Pharo-project] Xtreams's FileDirectory dependence
Xtreams depends on FileDirectory in at least three places, all in the Xtreams-Terminals package. (Three messages on FileUrl, #appending, #reading, #writing; two tests in XTFileReadingWritingTest >> #setUp and #tearDown) Pharo 2.0 has no FileDirectory. So it seems like the easiest (not necessarily simple, nor right) thing to is to break that out into Xtreams-Terminals-Squeak and Xtreams-Terminals-Pharo packages, and similarly for the tests. After that, we'd need to adjust the ConfigurationOfXtreams. I think I forgot to fulfil a promise to submit an updated version of this that loaded FFI correctly (sorry!). Thoughts? Do any Pharo folk load Xtreams? frank
FileSystemLegacy is your friend: http://smalltalkhub.com/#!/~PharoExtras/FileSystemLegacy On 2013-04-17, at 16:57, Frank Shearar <frank.shearar@gmail.com> wrote:
Xtreams depends on FileDirectory in at least three places, all in the Xtreams-Terminals package. (Three messages on FileUrl, #appending, #reading, #writing; two tests in XTFileReadingWritingTest >> #setUp and #tearDown)
Pharo 2.0 has no FileDirectory. So it seems like the easiest (not necessarily simple, nor right) thing to is to break that out into Xtreams-Terminals-Squeak and Xtreams-Terminals-Pharo packages, and similarly for the tests.
After that, we'd need to adjust the ConfigurationOfXtreams. I think I forgot to fulfil a promise to submit an updated version of this that loaded FFI correctly (sorry!).
Thoughts? Do any Pharo folk load Xtreams?
frank
On 17 Apr 2013, at 17:09, Camillo Bruni <camillobruni@gmail.com> wrote:
FileSystemLegacy is your friend:
Yes, that is one possibility. But we want a clean loading Xtreams using FileSystem directly, do we not ?
On 2013-04-17, at 16:57, Frank Shearar <frank.shearar@gmail.com> wrote:
Xtreams depends on FileDirectory in at least three places, all in the Xtreams-Terminals package. (Three messages on FileUrl, #appending, #reading, #writing; two tests in XTFileReadingWritingTest >> #setUp and #tearDown)
Pharo 2.0 has no FileDirectory. So it seems like the easiest (not necessarily simple, nor right) thing to is to break that out into Xtreams-Terminals-Squeak and Xtreams-Terminals-Pharo packages, and similarly for the tests.
After that, we'd need to adjust the ConfigurationOfXtreams. I think I forgot to fulfil a promise to submit an updated version of this that loaded FFI correctly (sorry!).
Thoughts? Do any Pharo folk load Xtreams?
frank
On 2013-04-17, at 17:12, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 17 Apr 2013, at 17:09, Camillo Bruni <camillobruni@gmail.com> wrote:
FileSystemLegacy is your friend:
Yes, that is one possibility.
But we want a clean loading Xtreams using FileSystem directly, do we not ?
yes definitely ;). but for loading it the first time, this is easier.
+1 for using a brand new and much cleaner FileSystem But you must let some time to lazy developpers, so FIleSystemLegacy should be used in some ConfigurationOf in the interim. 2013/4/17 Camillo Bruni <camillobruni@gmail.com>
On 2013-04-17, at 17:12, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 17 Apr 2013, at 17:09, Camillo Bruni <camillobruni@gmail.com> wrote:
FileSystemLegacy is your friend:
Yes, that is one possibility.
But we want a clean loading Xtreams using FileSystem directly, do we not
?
yes definitely ;). but for loading it the first time, this is easier.
We are really interested by Xtreams for replacing Pharo Streams. Now we should evaluate again Xtreams. So any action that make them easier to load is welcome. On Apr 17, 2013, at 4:57 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
Xtreams depends on FileDirectory in at least three places, all in the Xtreams-Terminals package. (Three messages on FileUrl, #appending, #reading, #writing; two tests in XTFileReadingWritingTest >> #setUp and #tearDown)
Pharo 2.0 has no FileDirectory. So it seems like the easiest (not necessarily simple, nor right) thing to is to break that out into Xtreams-Terminals-Squeak and Xtreams-Terminals-Pharo packages, and similarly for the tests.
After that, we'd need to adjust the ConfigurationOfXtreams. I think I forgot to fulfil a promise to submit an updated version of this that loaded FFI correctly (sorry!).
Thoughts? Do any Pharo folk load Xtreams?
frank
Stéphane Ducasse wrote
We are really interested by Xtreams for replacing Pharo Streams. Now we should evaluate again Xtreams.
IIRC at ESUG the version on squeaksource is not up to date with the VW version, which is why we were working on handling namespace/prefix mapping in filetree/cypress... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-s-FileDirectory-dependence-tp4682133p4682221.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 18 April 2013 01:42, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stéphane Ducasse wrote
We are really interested by Xtreams for replacing Pharo Streams. Now we should evaluate again Xtreams.
IIRC at ESUG the version on squeaksource is not up to date with the VW version, which is why we were working on handling namespace/prefix mapping in filetree/cypress...
How up to date is https://github.com/mkobetic/Xtreams/ ? That's surely not the "canonical" repository, which would be in the Cincom Smalltalk Public Repository. I think? Anyway, assuming it's up to date, one promising approach to using Martin Kobetic's repository directly is: * have a way of importing chunk format stuff from a GitHub repository (see Squeak's inbox for my doesn't-support-filetree-yet-but-can-do-chunk-format InstallerGitHub (and I plan to submit a Gofer patch to do the same)) * load into an Environment (Squeak 4.5 can do this, modulo its alpha state). It might even be possible to import into an Environment with the prefix-adding import and then fileout/monticelloise the resulting things as a prefix-using, non-Environments-requiring blob ready for everyone to use. frank
On 18/04/13 11:42, Frank Shearar wrote:
On 18 April 2013 01:42, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stéphane Ducasse wrote
We are really interested by Xtreams for replacing Pharo Streams. Now we should evaluate again Xtreams.
IIRC at ESUG the version on squeaksource is not up to date with the VW version, which is why we were working on handling namespace/prefix mapping in filetree/cypress...
How up to date is https://github.com/mkobetic/Xtreams/ ?
Better ask Martin :-) I know he's now playing now with Xtreams & Cypress to see how it can be used to maintain cross-dialect projects. So you may need an up-to-date implementation of Cypress reader/writer. Jan
On 18 April 2013 10:42, Frank Shearar <frank.shearar@gmail.com> wrote:
On 18 April 2013 01:42, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stéphane Ducasse wrote
We are really interested by Xtreams for replacing Pharo Streams. Now we should evaluate again Xtreams.
IIRC at ESUG the version on squeaksource is not up to date with the VW version, which is why we were working on handling namespace/prefix mapping in filetree/cypress...
How up to date is https://github.com/mkobetic/Xtreams/ ?
Given that there's 'From Smalltalk/X, Version:6.2.1 on 30-01-2012 at 10:57:56 PM' in files (like https://github.com/mkobetic/Xtreams/blob/master/stx_goodies_xtreams_core.st), it might be possible that this is the Smalltalk/X port's repository. frank
participants (7)
-
Camillo Bruni -
Frank Shearar -
Jan Vrany -
Nicolas Cellier -
Sean P. DeNigris -
Stéphane Ducasse -
Sven Van Caekenberghe