- Pharo-dev - lists.pharo.org

Re: [Pharo-project] files.pharo.org: Moving to new server

by Marcus Denker

On Apr 18, 2013, at 3:01 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > We will change the DNS to a new server. > > This should be transparent, but of course we never knowâ¦ > > Stages: > > 1) Change DNS to point to new server of (TODAY) > files.pharo.org > get.pharo.org > updates.pharo.org > Success! DNS has propagated (at least to here) and it works. I should be more reliable and faster. Marcus

April 18, 2013

Re: [Pharo-project] [squeak-dev] Xtreams's FileDirectory dependence

by Frank Shearar

On 18 April 2013 15:14, <mkobetic(a)gmail.com> wrote: > As Jan mentioned, in https://github.com/mkobetic/Xtreams I'm primarily just experimenting with Cypress. However the master branch there is misleading, it contains a very early port of Xtreams to ST/X (there's a much more up to date version in Jan's ST/X project @ https://swing.fit.cvut.cz/jenkins/job/xtreams_reports/) > > However if you look at some of the other branches in the github project you can find a fairly up to date, Cypress formatted dump from VW as well as the results of Sean's ESUG effort to add namespace-prefix mapping to Filetree (branch pharo_experiment). My ultimate goal is to test Dale's idea to maintain a cross-dialect project as parallel branches in git. However we still need to iron out various dialect differences in terms of what they emit as Cypress formatted output. BTW, does anyone know if git/github can handle absence of a master branch? I'd be inclined to just delete the master from the repository if that works well. Github's fine with this. You have to choose a new default branch, and then you can freely git push origin :master. You can also recreate a new master, and reset default to it if desired. > I've been planning to ping Sean about his Filetree fixes for a while, but I need to find the time to be able to actually act on it :-). The prefix-namespace mapping is crucial to make the parallel branch approach at all feasible. There's also the Environment effort on Squeak side which may obviate the prefix mapping need, but it seems to be still in fairly early stages. Environments definitely needs more beating on it. We have flushed out a number of bugs, but in particular we need folks to just use it, and try out importing, nesting, and the like > So far it was mostly Nicolas' manual effort that brought VW updates over the Squeak/Pharo side. I think it was a while since the last time he's done that, so the VW port is probably ahead somewhat. But Xtreams development isn't that active anymore. Most of our Xtreams related efforts are about using them for various things, so any changes are mostly fixes or small improvements driven by that use. So in some sense a manual update could be a feasible approach at this point. But I would really like to turn the project into a more collaborative effort, where updates can flow reasonably in any direction. Agreed. In particular I'd like to push my #interleave: implementation upstream! I don't know how far out of sync things are, but certainly I don't feel any pain when using Xtreams. > While I'm on the topic, I'm considering some API changes and am not sure how to go about discussing it. I don't want to cross post discussions to a number of mailing lists, so I think I'm inclined to just cross-post an invitation to anyone interested to subscribe to the Issues on the project site (https://code.google.com/p/xtreams/) and have those discussions there. Any thoughts on that? That's probably the best approach: people interested in Xtreams ought to talk about Xtreams on the Xtreams list! frank > "Frank Shearar"<frank.shearar(a)gmail.com> wrote: >> 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 >> >

April 18, 2013

Re: [Pharo-project] [squeak-dev] Xtreams's FileDirectory dependence

by mkobetic＠gmail.com

As Jan mentioned, in https://github.com/mkobetic/Xtreams I'm primarily just experimenting with Cypress. However the master branch there is misleading, it contains a very early port of Xtreams to ST/X (there's a much more up to date version in Jan's ST/X project @ https://swing.fit.cvut.cz/jenkins/job/xtreams_reports/) However if you look at some of the other branches in the github project you can find a fairly up to date, Cypress formatted dump from VW as well as the results of Sean's ESUG effort to add namespace-prefix mapping to Filetree (branch pharo_experiment). My ultimate goal is to test Dale's idea to maintain a cross-dialect project as parallel branches in git. However we still need to iron out various dialect differences in terms of what they emit as Cypress formatted output. BTW, does anyone know if git/github can handle absence of a master branch? I'd be inclined to just delete the master from the repository if that works well. I've been planning to ping Sean about his Filetree fixes for a while, but I need to find the time to be able to actually act on it :-). The prefix-namespace mapping is crucial to make the parallel branch approach at all feasible. There's also the Environment effort on Squeak side which may obviate the prefix mapping need, but it seems to be still in fairly early stages. So far it was mostly Nicolas' manual effort that brought VW updates over the Squeak/Pharo side. I think it was a while since the last time he's done that, so the VW port is probably ahead somewhat. But Xtreams development isn't that active anymore. Most of our Xtreams related efforts are about using them for various things, so any changes are mostly fixes or small improvements driven by that use. So in some sense a manual update could be a feasible approach at this point. But I would really like to turn the project into a more collaborative effort, where updates can flow reasonably in any direction. While I'm on the topic, I'm considering some API changes and am not sure how to go about discussing it. I don't want to cross post discussions to a number of mailing lists, so I think I'm inclined to just cross-post an invitation to anyone interested to subscribe to the Issues on the project site (https://code.google.com/p/xtreams/) and have those discussions there. Any thoughts on that? "Frank Shearar"<frank.shearar(a)gmail.com> wrote: > 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 >

April 18, 2013

Re: [Pharo-project] About sqnappy and LZ4

by Masashi UMEZAWA

Hi, > Anyways, my sarcasm was not to discourage you, just wanted to point > out that making plugin > and selling it as "having less dependencies" or "less work for users" > , not really true :) I know what you mean. We live in a DLL hell. But what I really meant was that it has minimum dependency to 'other Squeak/Pharo class libraries'. >From the image perspective, Sqnappy core just consists of two classes. It is easy to install to older or stripped images (yep, for non CogVM, we need to recompile the plugin source. ;) Probably I should have said 'no need to install any other prerequisites' or something. Sorry for the confusion. Best regards, -- [:masashi | ^umezawa]

April 18, 2013

Re: [Pharo-project] How to get the AST Node for a Context

by Ben Coman

stephane ducasse wrote: > On Apr 17, 2013, at 10:29 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > >> I really really like this :) >> >> very simple yet powerful! >> > > Yes this will massively simplify the debugger :) > So we will be able to get a debugger really working without needing an magician to fix > its bugs. > > Stef > > > > Along the lines of a good engineering principle I like... If you can't solve a problem, change the problem to one you can solve. cheers -ben

April 18, 2013

[Pharo-project] files.pharo.org: Moving to new server

by Marcus Denker

Hi, We will change the DNS to a new server. This should be transparent, but of course we never knowâ¦ Stages: 1) Change DNS to point to new server of (TODAY) files.pharo.org get.pharo.org updates.pharo.org 2) Change DNS Server from NameCheap to new provider (TOMORROW) (this will speed up DNS queries ;-) 3) enable CDN for the static files. (NEXT WEEK) Marcus and Camillo

April 18, 2013

Re: [Pharo-project] About sqnappy and LZ4

by Igor Stasenko

On 18 April 2013 13:33, Masashi UMEZAWA <masashi.umezawa(a)gmail.com> wrote: > Hi, > >> > Some Sqnappy characteristics: >> > - it has a minimum dependency (it does not use FFI, NativeBoost) so >> > that it can be run on older images >> >> - having a separate plugin/VM , which users always have trouble dealing wih >> :) > > You may recompile SnappyPlugin as an internal plugin. It is nice. ;) > Actually Snappy itself is optimized for 64-bit platform. So you may > need a recompilation if you try it in 64 bit VM. > yeah yeah.. recompile VM.. think how many users will stop right at this point and go no further :) Anyways, my sarcasm was not to discourage you, just wanted to point out that making plugin and selling it as "having less dependencies" or "less work for users" , not really true :) > Best regards, > -- > [:masashi | ^umezawa] > -- Best regards, Igor Stasenko.

April 18, 2013

Re: [Pharo-project] pharo-project.org: small updates website

by Marcus Denker

On Apr 18, 2013, at 2:46 PM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi Marcus: > > On 09 Apr 2013, at 20:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hi, >> >> -> The download button now goes to http://www.pharo-project.org/pharo-download, not the zip (because there are now 3) >> -> updated http://www.pharo-project.org/pharo-download for the platform specific zip files > > Looks like you missed a link: > > The Pharo2.0 (mac) link should point here: https://gforge.inria.fr/frs/download.php/32303/Pharo2.0-mac.zip > Thanks! I fixed it. Marcus

April 18, 2013

Re: [Pharo-project] pharo-project.org: small updates website

by Stefan Marr

Hi Marcus: On 09 Apr 2013, at 20:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > -> The download button now goes to http://www.pharo-project.org/pharo-download, not the zip (because there are now 3) > -> updated http://www.pharo-project.org/pharo-download for the platform specific zip files Looks like you missed a link: The Pharo2.0 (mac) link should point here: https://gforge.inria.fr/frs/download.php/32303/Pharo2.0-mac.zip Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 18, 2013

Re: [Pharo-project] Metacello configuration conventions

by Christophe Demarey

Yes. It would be very helpful to highlight a bit compatibility between versions. I keep that in mind for versionner. Le 17 avr. 2013 Ã 11:10, Camillo Bruni a Ã©crit : > > On 2013-04-17, at 02:50, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Camillo Bruni-3 wrote >>> I liked ruby-gems approach more than the one in Metacello. You usually >>> specify >>> a major version (as under linux) for your dependency. >> >> It seems they're using semantic versioning, which is *awesome*, but can we >> depend on the convention being followed? I've been pushing to get the tools >> (e.g. Versionner) to use semantic version numbers by default (i.e. new >> bugfix version, new enhancement version, new incompatible version) > > Yeah I think we can run all of that on top of versioner/conventions. > You can always introduce symbolic versions for releases as well so the old > habit of directly referring to a fixed version number will still continue to > work. >

April 18, 2013