- Pharo-dev - lists.pharo.org

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

by phil＠highoctane.be

Check 14h50 https://devfest.be/schedule/day1 [image: Inline image 1] Question: does anyone here has made some integration with Angular (1.x) in Seaside? I mean tag brushes for ng-app and possible other interesting associated features (like passing parms from a component to the ng-app parms, having angular service calling in Pharo Seaside callbacks etc)? Would be nice to have a few extra Google-centric things to show. Phil On Sat, Oct 8, 2016 at 6:59 PM, stepharo <stepharo(a)free.fr> wrote: > super cool :) > > You should contact cyril because he once explained to me that the pharo > version was better > > than the google one (but now they released a new version). > > > Le 7/10/16 Ã 14:03, phil(a)highoctane.be a Ã©crit : > >> >> Title is Material Design Lite in Pharo. >> >> Phil >> >> > >

Oct. 9, 2016

Re: [Pharo-dev] [ANN] Tealight

by Attila Magyar

Nice extension. Thanks. -- View this message in context: http://forum.world.st/ANN-Tealight-tp4918431p4918455.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 8, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by Damien Pollet

It's a breaking change and I don't know if there's a way to do it with proper deprecationâ¦ my hope is that there are not many users of it, but I haven't checked yet. Any opinions among users of FileSystem? On 8 October 2016 at 19:12, stepharo <stepharo(a)free.fr> wrote: > So damien what is the solution? > > > > Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : > > 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 > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 8, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by stepharo

So damien what is the solution? Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : > 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. 8, 2016

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

by stepharo

super cool :) You should contact cyril because he once explained to me that the pharo version was better than the google one (but now they released a new version). Le 7/10/16 Ã 14:03, phil(a)highoctane.be a Ã©crit : > > Title is Material Design Lite in Pharo. > > Phil >

Oct. 8, 2016

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

by Guillaume Larcheveque

Really Nice! We developed some of the Widgets with Cyril (NestedList, Paginated list...) so told us if you want some explanations about their implementation. 2016-10-07 17:34 GMT+02:00 olivier auverlot <olivier.auverlot(a)gmail.com>: > 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 >> > -- *Guillaume Larcheveque*

Oct. 8, 2016

Re: [Pharo-dev] [ANN] Tealight

by philippe.back＠highoctane.be

Looks nice. Is there a way to turn the dynamic routes done in the "experiments" mode into a set of methods + pragmas? Phil Le 8 oct. 2016 10:16, "Torsten Bergmann" <astares(a)gmx.de> a Ã©crit : > 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

Re: [Pharo-dev] [ANN] Tealight

by Tudor Girba

Nice work. Thanks! Doru > On Oct 8, 2016, at 10:15 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > 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. > -- www.tudorgirba.com www.feenk.com "Every successful trip needs a suitable vehicle."

Oct. 8, 2016

[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