[Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-05-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On May 20, 2013, at 7:00 AM, seas...@rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community > an opportunity to easily know what's happening and to coordinate efforts. > Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Opal major progress. -> 20 Issue tracker entries left -> 20 Regression tests failing (most are tests specific to old compiler) > > ### What's next, until 2013-05-31 (*): > Finishing touches… --- -> Fix all failing regression tests Opal -> Fix bug Semantic Analysis for AST Interpreter -> merge Guille's changes to use Opal Semantic Analysis in AST Interprer -> Change Gisela's AST Suggestions/Navigation to use Opal Semantic Analysis -> Remove RB-AST-Semantics Package -> Check all remaining references to Compiler (and other classes) -> Move old Compiler to OldCompiler Package and make it unloadable Plugability --- -> Clients should be able to replace all components (Parser, ASTTranslater, SemCheck, BytecodeBuilder, IRBuilder). This is quite easy: we change the CompilationContext to provide the default classes. Just set your own. -> Add Plugin architecture for SemanticCheck Plugins and AST Transformation Plugins. If you just want to do something in addition, no need to override visitors: there should be a way to just subclass a pre-defined abstract visitor and a way to define order and Setting support…. Reflectivity -- -> Iterate with Camille on the reimplementation of Reflectivity. -> Add ReflectiveMethod to Pharo3. -> First Link-Inliner as Plugin for Opal. When all this is Done: === -> add entry to Suggestions Menu "Halt Once Here" which will just annotate this AST node with a meta-link which deinstalls itself and calls Halt. The Reflectivity model is quite powerful, and we can then build things on top that would be even unthinkable without… AST Everywhere + Slots + Reflectivity… this will be great :-) Marcus
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Marcus Denker-4 wrote > "Halt Once Here" which will just annotate w00t!! - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-WhatsUp-from-2013-05-20-until-2013-05-31-tp4688515p4688546.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On 20 May 2013 07:00, wrote: > ### Here's what I've been up to since the last WhatsUp: > - Started looking at the ARM architecture specs and sketching ARM support into AsmJit with Camillo > ### What's next, until 2013-05-31 (*): > - more of the same :) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On May 20, 2013, at 7:00 AM, seas...@rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community > an opportunity to easily know what's happening and to coordinate efforts. > Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - read all the logging frameworks - designed a minimal core one based on objects (no strings) - clean pharo by example repositories - starting a pass on Deep into Pharo - creating lecture support for Pharo - working on new chapters for the next book - cleaning UI - studying theme - running smallLint - AST for class/package definition discussions - changes design - prepare lecture in programming school > ### What's next, until 2013-05-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - work on UI for the logger - continue to work on theme changes - continue to work on logger: creating a UI - running smallLint and fixing code > (*) we'll be expecting results by then ;) >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
### Here's what I've been up to since the last WhatsUp: - Started doing serious stuff in Amber. - Interview of Nicolas Petton on Amber Smalltalk - Demoed Amber at Google IO Extended Brussels ### What's next, until 2013-05-31 (*): - Make Pharo and Amber talk with each other (explorations...) - Start a set of videos on Amber On Mon, May 20, 2013 at 12:43 PM, Damien Pollet wrote: > On 20 May 2013 07:00, wrote: > >> ### Here's what I've been up to since the last WhatsUp: >> > > - Started looking at the ARM architecture specs and sketching ARM support > into AsmJit with Camillo > > >> ### What's next, until 2013-05-31 (*): >> > > - more of the same :) > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On 20 May 2013, at 07:00, seas...@rmod.lille.inria.fr wrote: > ### Here's what I've been up to since the last WhatsUp: - implemented Zn server side gzip compression & chunking - tried to improve Zn IO efficiency - various small Zn/Zdc improvements and new tests - debugged cmsbox's decision to block all Zn request - added REPL Zn handler - picked up an old, not yet pubished, project bringing it up to date > ### What's next, until 2013-05-31 (*): - prepare another Zn/Zdc version for inclusion in 3.0 (and 2.0) - prepare slides for Pharo Web conference (ahead of time ;-) Sven
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
### Here's what I've been up to since the last WhatsUp: SmalltalkHub - continue working on the configuration (it looks like Zinc has a bug with its handling of PUT requests) - fix a bug - add a button so that users can delete a mcz from SmalltalkHub Pharo packaging - send many patches upstream - delete the same patches from Ubuntu packaging scripts - update VM with latest upstream release Lectures - prepare Pharo lecture with Stéphane Books - work on some Jenkins jobs to build books ### What's next, until 2013-05-31 (*): -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On 21 May 2013, at 09:30, Damien Cassou wrote: > - continue working on the configuration (it looks like Zinc has a bug with > its handling of PUT requests) Hi Damien, please elaborate, maybe I can help. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Not sure if this is related, but my FileSystem-Git build for 2.0 broke this morning with a Zn stack trace (bad gateway): https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/PHARO=20,VERSION=development,VM=vm/53/ Max On 21.05.2013, at 09:38, Sven Van Caekenberghe wrote: > > On 21 May 2013, at 09:30, Damien Cassou wrote: > >> - continue working on the configuration (it looks like Zinc has a bug with >> its handling of PUT requests) > > Hi Damien, please elaborate, maybe I can help. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Max, On 21 May 2013, at 09:43, Max Leske wrote: > Not sure if this is related, but my FileSystem-Git build for 2.0 broke this > morning with a Zn stack trace (bad gateway): > https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/PHARO=20,VERSION=development,VM=vm/53/ Assuming you are loading Zn's #bleedingEdge, could you send me the URL you try to access and that fails ? I mean a standalone version of what is happening here ZnClient>>get GitDumbHTTPProtocol class>>initialRequestTo: GitDumbHTTPProtocol class>>connectTo: GitAbstractProtocol class>>url: GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>newProtocol GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>testTags GitSmartHTTPProtocolTest(TestCase)>>performTest If that is possible without giving out credentials. Sven > Max > > On 21.05.2013, at 09:38, Sven Van Caekenberghe wrote: > >> >> On 21 May 2013, at 09:30, Damien Cassou wrote: >> >>> - continue working on the configuration (it looks like Zinc has a bug with >>> its handling of PUT requests) >> >> Hi Damien, please elaborate, maybe I can help. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> > >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
On 21.05.2013, at 10:01, Sven Van Caekenberghe wrote: > Max, > > On 21 May 2013, at 09:43, Max Leske wrote: > >> Not sure if this is related, but my FileSystem-Git build for 2.0 broke this >> morning with a Zn stack trace (bad gateway): >> https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/PHARO=20,VERSION=development,VM=vm/53/ > > Assuming you are loading Zn's #bleedingEdge, could you send me the URL you > try to access and that fails ? Hm, doesn't seem to be bleeding edge (although is 2.0 dev). The test is fine on my local machine, so perhaps there's something wrong at inria? Here's the incantation: ZnClient new url: aUrl asZnUrl / 'info' / 'refs'; queryAt: 'service' put: 'git-upload-pack'; "username: 'admin' password: 'admin';" enforceHttpSuccess: true; streaming: true; get; yourself with url: 'https://git.gitorious.org/gitorious/mainline.git' Thanks Sven. > > I mean a standalone version of what is happening here > > ZnClient>>get > GitDumbHTTPProtocol class>>initialRequestTo: > GitDumbHTTPProtocol class>>connectTo: > GitAbstractProtocol class>>url: > GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>newProtocol > GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>testTags > GitSmartHTTPProtocolTest(TestCase)>>performTest > > If that is possible without giving out credentials. > > Sven > >> Max >> >> On 21.05.2013, at 09:38, Sven Van Caekenberghe wrote: >> >>> >>> On 21 May 2013, at 09:30, Damien Cassou wrote: >>> - continue working on the configuration (it looks like Zinc has a bug with its handling of PUT requests) >>> >>> Hi Damien, please elaborate, maybe I can help. >>> >>> Sven >>> >>> >>> -- >>> Sven Van Caekenberghe >>> Proudly supporting Pharo >>> http://pharo.org >>> http://association.pharo.org >>> http://consortium.pharo.org >>> >>> >>> >>> >>> >> >> > >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Sven, the build is back to stable. Thanks anyway! Max On 21.05.2013, at 10:27, Max Leske wrote: > > On 21.05.2013, at 10:01, Sven Van Caekenberghe wrote: > >> Max, >> >> On 21 May 2013, at 09:43, Max Leske wrote: >> >>> Not sure if this is related, but my FileSystem-Git build for 2.0 broke this >>> morning with a Zn stack trace (bad gateway): >>> https://ci.inria.fr/pharo-contribution/job/FileSystem-Git/PHARO=20,VERSION=development,VM=vm/53/ >> >> Assuming you are loading Zn's #bleedingEdge, could you send me the URL you >> try to access and that fails ? > > Hm, doesn't seem to be bleeding edge (although is 2.0 dev). The test is fine > on my local machine, so perhaps there's something wrong at inria? > > Here's the incantation: > ZnClient new > url: aUrl asZnUrl / 'info' / 'refs'; > queryAt: 'service' put: 'git-upload-pack'; > "username: 'admin' password: 'admin';" > enforceHttpSuccess: true; > streaming: true; > get; > yourself > > with url: 'https://git.gitorious.org/gitorious/mainline.git' > > Thanks Sven. > >> >> I mean a standalone version of what is happening here >> >> ZnClient>>get >> GitDumbHTTPProtocol class>>initialRequestTo: >> GitDumbHTTPProtocol class>>connectTo: >> GitAbstractProtocol class>>url: >> GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>newProtocol >> GitSmartHTTPProtocolTest(GitAbstractProtocolTest)>>testTags >> GitSmartHTTPProtocolTest(TestCase)>>performTest >> >> If that is possible without giving out credentials. >> >> Sven >> >>> Max >>> >>> On 21.05.2013, at 09:38, Sven Van Caekenberghe wrote: >>> On 21 May 2013, at 09:30, Damien Cassou wrote: > - continue working on the configuration (it looks like Zinc has a bug > with its handling of PUT requests) Hi Damien, please elaborate, maybe I can help. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org >>> >>> >> >> >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
### Here's what I've been up to since the last WhatsUp: LightHouse -Learning Glamour -Started new project with Stephan Eggermont and Diego Lont as part of GSoC. Project is a Distributed Issue Tracker built in Pharo for Pharo! (https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/riverdusty/1) ### What's next, until 2013-05-31 (*): LightHouse -More Learning Glamour -More working on LightHouse UI Dusty
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
What is LightHouse? :) Doru On Tue, May 21, 2013 at 2:14 PM, Gareth Cox wrote: > ### Here's what I've been up to since the last WhatsUp: > > LightHouse > -Learning Glamour > -Started new project with Stephan Eggermont and Diego Lont as part of GSoC. > Project is a Distributed Issue Tracker built in Pharo for Pharo! > ( > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/riverdusty/1 > ) > > > ### What's next, until 2013-05-31 (*): > > LightHouse > -More Learning Glamour > -More working on LightHouse UI > > Dusty > -- www.tudorgirba.com "Every thing has its own flow"
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
It is a new project to help with workflow for developers in Pharo. The idea is a Distributed Issue Tracker, so you can keep track of your own issues, for your own projects, in your own image. The link is to the proposal for the GSoC 2013! So go vote! -Dusty >What is LightHouse? :) >Doru >On Tue, May 21, 2013 at 2:14 PM, Gareth Cox wrote: > ### Here's what I've been up to since the last WhatsUp: > > LightHouse > -Learning Glamour > -Started new project with Stephan Eggermont and Diego Lont as part of GSoC. > Project is a Distributed Issue Tracker built in Pharo for Pharo! > ( > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/riverdusty/1 > ) > > > ### What's next, until 2013-05-31 (*): > > LightHouse > -More Learning Glamour > -More working on LightHouse UI > > Dusty >
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Hi, I've worked a bit with Dusty & Diego on LightHouse, the Distributed Issue Tracker. Here is a short video of the current state of the project: http://www.youtube.com/watch?v=g_Q1DeeEiAQ Source can be found on Smalltalkhub, DiegoLont/LightHouse Stephan
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Le 20 mai 2013 à 07:00, seas...@rmod.lille.inria.fr a écrit :
> Hi! We're sending this automatic email twice a month, to give the community
> an opportunity to easily know what's happening and to coordinate efforts.
> Just answer informally, and feel free to spawn discussions thereafter!
>
> ### Here's what I've been up to since the last WhatsUp:
Work on Metacello with Dale :
- to include Pharo2 and Pharo3 as platforms to test on travis (Metacello is
tested with travis CI)
- to get MetacelloPreview working on Pharo2 and Pharo3 : we still need some
work but not so far!
**
Results for #('BaselineOfMetacello') Test Suite
737 run, 722 passes, 0 skipped, 0 expected failures, 0 failures, 7 errors, 8
unexpected passes
**
> ### What's next, until 2013-05-31 (*):
Include MetacelloPreview as default Metacello version in Pharo3
Get back on Versionner to use MetacelloPreview
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
cool :)
On May 22, 2013, at 9:34 AM, Christophe Demarey
wrote:
>
> Le 20 mai 2013 à 07:00, seas...@rmod.lille.inria.fr a écrit :
>
>> Hi! We're sending this automatic email twice a month, to give the community
>> an opportunity to easily know what's happening and to coordinate efforts.
>> Just answer informally, and feel free to spawn discussions thereafter!
>>
>> ### Here's what I've been up to since the last WhatsUp:
>
> Work on Metacello with Dale :
> - to include Pharo2 and Pharo3 as platforms to test on travis (Metacello is
> tested with travis CI)
> - to get MetacelloPreview working on Pharo2 and Pharo3 : we still need some
> work but not so far!
>
> **
> Results for #('BaselineOfMetacello') Test Suite
> 737 run, 722 passes, 0 skipped, 0 expected failures, 0 failures, 7 errors, 8
> unexpected passes
> **
>
>
>> ### What's next, until 2013-05-31 (*):
>
> Include MetacelloPreview as default Metacello version in Pharo3
> Get back on Versionner to use MetacelloPreview
>
Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
> Hi! We're sending this automatic email twice a month, to give the community > an opportunity to easily know what's happening and to coordinate efforts. > Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: I have been working on the Distributed Issue Tracker. We now have real distribution. I can serve my issues in one issue tracker and then set the url on another image and push and pull issues from / to this image. It has an automatic merge (last one wins), and updates the ui (so that is nice) on both sides. > ### What's next, until 2013-05-31 (*): Main next step is: get the project to be accepted! So please vote in favor of this project. You can find a detailed description at: http://gsoc2013.esug.org/projects/distributed-issue-tracker You can download it and play with it yourself at the smalltalkhub: http://smalltalkhub.com/#!/~DiegoLont/LightHouse Because a lot of work still needs to be done. The interesting part is of course getting the distributed aspect work properly, including file uploads, user management and ownership, NAT traversal, merging handling conflicts and integrating in different workflows So if you are a mentor, please vote for this project. Diego
