- Pharo-dev - lists.pharo.org

[ANN] Tealight

by Torsten Bergmann

Hi, I wrote a small extension "Tealight" for the Teapot framework that makes it even easier to experiment with web based interfaces/web calls into Pharo running on the server side. It additionally allows you to easily define and generate a simple or versioned web interface for your own apps. With this extension REST annotated methods like greeting: aRequest <REST_API: 'GET' pattern: 'hello'> ^'HelloWorld from Pharo' are transformed into dynamic Teapot routes and can be accessed easily via web. You can use two pragmas: #REST_API:pattern: for standard APIs #REST_API:versions:pattern for versioned APIs Full docu explaining how to use it is added on https://github.com/astares/Tealight It also shows the new custom "Teaspoon" inspector extension tool implemented by Attila Magyar - which is really cool to experiment and call the web methods without a web browser or Zinc scripts. So far there is no config for Tealight for the catalog yet, will add this soon. So for the time being you need to load the latest version via Metacello new repository: 'github://astares/Tealight/repository'; baseline: 'Tealight'; load to follow the docu description. Have fun! Bye T.

Oct. 8, 2016

Path >> fullName should not be the same as printString

by Damien Pollet

Path >> printString returns a self-evaluating representation, which is fine. Its symmetric is thus Compiler >> evaluate: aString. (Path from: aString) parses the unix/url representation of a path and results in a Path instance. As far as I understand, #fullName should be the symmetric of that, so that we always have (modulo syntactic normalization, maybe) : (Path from: aString) fullName = aString Note that there's an edge case with the empty string that is wrong (at least it should be confusing to unix guys): Path from: ''. "Path root" Usually the absolute path for the root of the filesystem is explicitly noted '/', and an empty path is equivalent to '.' -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 7, 2016

Re: [Pharo-dev] Talk at Google Devdays BE accepted

by olivier auverlot

Cool ð Le 7 oct. 2016 14:04, "phil(a)highoctane.be" <phil(a)highoctane.be> a Ã©crit : > Title is Material Design Lite in Pharo. > > Phil >

Oct. 7, 2016

Talk at Google Devdays BE accepted

by phil＠highoctane.be

Title is Material Design Lite in Pharo. Phil

Oct. 7, 2016

[pharo-project/pharo-core] 8eedb0: 60257

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 8eedb05543da1bc89197b48ec4b55736006cc62e https://github.com/pharo-project/pharo-core/commit/8eedb05543da1bc89197b48e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-07 (Fri, 07 Oct 2016) Changed paths: M Refactoring-Critics.package/RBTransformationRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBTransformationRule.class/instance/running/checkMethod_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60256.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60257.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60256.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60257.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60257 19107 Rule "Eleminate unnecessary nots" suggest to introduce some bugs https://pharo.fogbugz.com/f/cases/19107 http://files.pharo.org/image/60/60257.zip

Oct. 7, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60257 Home: https://github.com/pharo-project/pharo-core

Oct. 7, 2016

Re: [Pharo-dev] [Issue tracker] Down to 603 open issues

by Marcus Denker

> On 6 Oct 2016, at 15:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > We still have *a lot* of half-done issues open on the issue tracker: > > https://pharo.fogbugz.com/f/filters/57/All-newest-first > > We are slightly down to 603 open issues. (We closed 47 entries the last 7 days). > > It would be nice if people could check old issue tracker entries! To me many > look stale, but it is very hard to assess if this includes following a multi-page > discussionâ¦ > Down to 599. It would be really good if everyone would look at the issues they have been involved in. There are so many that look stale. Marcus

Oct. 7, 2016

Re: [Pharo-dev] Extending Pharo Debugger

by stepharo

It looks fun :) Are you looking for more ideas for your thesis? Le 6/10/16 Ã 10:05, Matteo Marra a Ã©crit : > Hello Stephan, > > In the work for my thesis, I'm building a debugger for big data > applications, that when a bug happens doesn't stop the computation but > proceeds evaluating the next data. This opens a series of debuggers in > separate threads, that are shown one by one. I added a button that > allows me to restart and automatically proceed all the waiting > debuggers from a certain point of the stack (assuming that the stack > has the same "shape"), so basically after I fix a bug in the first > debugger I can say to the others: ok, the bug is solved, restart > yorself and proceed. > > The thing seems more or less to work, except some details that I still > have to implement. > > Matteo > > 2016-10-06 7:40 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi matteo > > What do you want to add? > > Stef > > > Le 4/10/16 Ã 16:10, Matteo Marra a Ã©crit : > > Hello, > > I'm working on the Pharo debugger, and I wanted to add a > button with new functionality just besides the buttons > "Proceed" "restart" ... > > Is there an easy way to do it? Which is the class that I have > to Modify/Extend in order to do that? > > I tried to look around the methods and I found where > DebugSession is created, but I didn't see any clear reference > to the UI or to how is constructed in it. > > Thank you in advance, > Matteo > > > >

Oct. 6, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] New "DarkMetalTheme" for Pharo

by Dimitris Chloupis

sure it is an opportunity to see how metadaless gitfiletree works, are there any instruction or documentation about it ? On Thu, Oct 6, 2016 at 4:04 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yeah. > btwâ¦ feel free to do âmetadatalessâ that repo. > > Esteban > > On 6 Oct 2016, at 14:54, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > fork and pull request ? > > On Thu, Oct 6, 2016 at 3:43 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > On 6 Oct 2016, at 14:38, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Dark theme is a diffirent theme so this one cannot replace it > > I really like this one too but I feel the contrasts could be better , I > find it hard to make out some buttons. > > > I know. > Feel free to contribute ;) > > Esteban > > > On Thu, Oct 6, 2016 at 2:59 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > On 6 Oct 2016, at 12:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > >> On 06 Oct 2016, at 10:39, Norbert Hartl <norbert(a)hartl.name> wrote: > >> > >> You should call it Insomnia! > > > > +1 > > > > For which Pharo versions will this work, is it supported ? 4 ? 5 ? 6 ? > > it should work on 5 and 6 out of the boxâ¦ and I guess pharo 4 too, never > tried. > > > Is the plan to replace the previous Dark Theme or are both going to be > maintained in parallel ? > > not at all (unless community decides so, but if thatâs the case I think it > needs some workâ¦ as Phil said, there are some colors that are not working > so well) > I made it for another project (and to prove that applying a palette was > easyâ¦ which turned to be not true because of the spotter themers). > > I do not think all themes needs to be in image. In my âdesign-in-the-mindâ > we should have just two: one white and one dark, and we should made the > others easily accessible/installable. > > This theme, so far, is just intended for my use and all who want to use > and enhance it, so Iâm maintaining it but I accept contributions :) > > Esteban > > > > > >> Norbert > >> > >>> Am 06.10.2016 um 10:36 schrieb Esteban Lorenzano <estebanlm(a)gmail.com > >: > >>> > >>> Hi, > >>> > >>> I took some time to extract the ==MUDDarkTheme== I made for my > *MUDClient>https://github.com/estebanlm/MUDClient*, > >>> repackage it, rebrand it and make it available for everybody. > >>> > >>> So behold, the new DarkMetalTheme ! > >>> > >>> https://github.com/estebanlm/themes > >>> > >>> <DarkMetalPharo.png> > >> > > > > > > > >

Oct. 6, 2016

[Issue tracker] Down to 603 open issues

by Marcus Denker

Hello, We still have *a lot* of half-done issues open on the issue tracker: https://pharo.fogbugz.com/f/filters/57/All-newest-first We are slightly down to 603 open issues. (We closed 47 entries the last 7 days). It would be nice if people could check old issue tracker entries! To me many look stale, but it is very hard to assess if this includes following a multi-page discussionâ¦ Marcus

Oct. 6, 2016