April 2013 - Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] Versionner in 2.0 again

by Christophe Demarey

Le 18 avr. 2013 Ã 05:16, Sean P. DeNigris a Ã©crit : > Christophe Demarey wrote >> I was wondering if it is possible to downgrade an already installed >> package in a configuration. > > For now, why don't we just declare a dependency to the correct version of > the toolbox? I'm uploading a config to Nabble which does this and seems to > work... ConfigurationOfVersionner-SeanDeNigris.101.mcz > <http://forum.world.st/file/n4682230/ConfigurationOfVersionner-SeanDeNigris.…> I tried with a baseline but it doesn't work (metacello keep the most up to date toolbox). I didn't think to declare the toolbox as package. Your version works fine. Thanks. I pushed it to the Versionner repo. :) So, now Versionner is loadable as any other lib. @Marcus: Yes, if possible, it should be nice to update the toolbox version in the image. Best regards, Christophe.

April 18, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Sean P. DeNigris

stephane ducasse wrote > add a bug entry and tag it so that we simply do not forget. >From https://pharo.fogbugz.com/f/cases/10228/Fix-tab-key-for-autocompletion : Fix in inbox: SLICE-Issue-10228-Fix-tab-key-for-autocompletion-SeanDeNigris.1 Accept-on-tab if there are no common prefixes (Package Johan's cs from [1]) [1] http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-td… And https://pharo.fogbugz.com/f/cases/10311/Backport-2-0-10228-Fix-tab-key-for-… : Fix in inbox: SLICE-Issue-10311-Backport-2-0-10228-Fix-tab-key-for-autocompletion-SeanDeNigris.1 I'm leaving https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… as a separate issue because I have a few more ideas ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 18, 2013

Re: [Pharo-project] About sqnappy and LZ4

by Masashi UMEZAWA

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. Best regards, -- [:masashi | ^umezawa]

April 18, 2013