- Pharo-users - lists.pharo.org

Re: [Pharo-users] Status of Twitter (api/analysis/visualization) in Pharo?

by Offray Vladimir Luna CÃ¡rdenas

Hi Martin, Thanks, we had already detected the problem with Jpeg images and even reported here to the list, but until now the solution eluded us. Your solution is already on the repo. Cheers, Offray On 21/06/15 10:53, MartinW wrote: > Offray wrote >> Ok. Let me know what happens. > Hi Offray, > I got the scraping, importing and visualization working. Not sure, what went > wrong the first time. > > I found one little bug, when the avatar was a jpeg. It can be solved by > changing the following lines in TwitterProfile>>scrapAvatarFrom: > > from: > > ((avatarUrl asLowercase endsWith: '.jpeg') or: (avatarUrl asLowercase > endsWith: '.jpg')) > ifTrue: [ > avatarImage := ZnEasy get: avatarUrl. > "(PNGReadWriter on: avatarImage ) nextPutImage: (JPEGReadWriter on: > avatarImage )" ]. > > to: > > ((avatarUrl asLowercase endsWith: '.jpeg') or: (avatarUrl asLowercase > endsWith: '.jpg')) > ifTrue: [avatarImage := ZnEasy getJpeg: avatarUrl.]. > > > Very nice result. Thank you a lot for sharing it! > Best regards, > Martin. > > > > -- > View this message in context: http://forum.world.st/Status-of-Twitter-api-analysis-visualization-in-Pharo… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 25, 2015

Re: [Pharo-users] RESTful API with Pharo with Gemstones

by Sebastian Heidbrink

Actually with the new version 2.0 I would also change my workflow. Version 1.2 had not online spec editor tooling support and this is why I let Gemstone describe my REST API and render the Swagger json specification. In Swagger 2.0 I would rather take the online spec editor define a swagger spec and take the resulting json file to generate ZincRESTCall subclasses. This way a client developer or user is able to define his or her needs. Whish I had more time right now. Sebastian Am 24.06.2015 um 01:14 schrieb itlists(a)schrievkrom.de: > We go a very similiar way as Sebastian - but with our company need NOT > to build a Smalltalk-only system, but also offer support for several > other developers/languages. > > We use > > * Zinc REST > > * Gemstone 3.2.6 > > We generate code to have: > > * Swagger-UI and Swagger-Core support (currently 1.2) > > Earlier the swagger stuff was also handled by Gemstone, but now we > create Gemstone-Code to write the Swagger-specs into the server filesystem. > > Practically the swagger-core support has been working with C# (we had to > correct/change the template for source code generation). > > We see now the need to go to Swagger 2.0, to stay near the development > master stream. > > The whole system is working very stable - the only problem I have is a > 10 MB limit on the Gemstone socket system - here the Zinc HTTP System > subsystem must be changed to get rid of this problem. > > > Marten > > Am 23.06.2015 um 20:40 schrieb sergio_101: >> I have been a project coming up that I really onlyneed a restful API on. >> >> The front end will be first built on a mobile device(iOS )then back on >> possibly android, with a very stripped down web application. >> >> i would like to use pharo/gemstones as the database. >> >> is there a project out there that allows for such restful API >> development in pharo land? This would be so fun! >> >> thanks >

June 25, 2015

Giving skype lectures to cameron students

by stepharo

Hi we are giving some skype lectures to cameron students with damien. A fun experience, because the network is so bad that I cannot demo Pharo interactively. But I'm learning from it. Stef

June 25, 2015

Re: [Pharo-users] the importance of your story

by Alexandre Bergel

Yes, it would be great to discuss about that. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 25, 2015, at 11:28 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2015-06-25 15:56 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>>: > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from the StackOverflow and Github scene. I feel it is like a researcher without a webpage. Without a webpage, he does not exist. > > Well, we could put Roassal on github ;) > > > But I have faith things will soon change... > > I hope so. It would make Roassal configurations and versions a tad easier :) > > If I was to use Roassal in a professionnal product, I'd be really tempted to do a freeze of Roassal on github along with a few of its dependencies :P > > Thierry > > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. >> >> There are several things I would like to emphasize. >> >> I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. >> >> One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. >> >> But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. >> >> While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. >> >> Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. >> >> Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" > >

June 25, 2015

Pharo image processing library

by Peter UhnÃ¡k

Hi, is there any image (as in picture) processing library in the likes of Python's PIL(http://effbot.org/imagingbook/image.htm), or even (highly unlikely) something like OpenCV (http://opencv.org/)? Thanks, Peter

June 25, 2015

Re: [Pharo-users] RESTful API with Pharo with Gemstones

by Sebastian Heidbrink

Hi Sven, I put some code on GitHub. There is no working example yet, but all one needs. I have to get back into Amber and their current way to integrate external libs. As soon as I have that working again I will add a Version 1.2 petstore example. https://github.com/HeSe/amber-swaggerJs Most important part is the SwaggerApi class and the methods build and initializeSwaggerInterfaceFor: They import the hosted swagger spec and build the JS-Api Interface object one can use in Amber,.... there is really not much to it. Sebastian Am 23.06.2015 um 14:39 schrieb Sven Van Caekenberghe: >> On 23 Jun 2015, at 22:55, Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: >> >> Hi Sergio, >> >> Zinc-REST is part of the Zinc repository and a fork for Gemstone can be found here: https://github.com/GsDevKit/zinc/tree/gs_master/repository/Zinc-REST.package >> Most part is to implement the code that generates the Swagger specification for your ZnRESTCall subclasses. But it is no vodoo. >> It becomes more complexe if you would actually like to use the swagger specification on the server site to do request data validation and error handling,.... I currently use Swagger only for documentation purposes. >> >> Amber limitations? Not really. >> It took me some time to figure out how to configure my servers to cope with CORS for the Swagger-UI and my current jsonwebtocken security mechanism is not supported by the SwaggerUI and I had to allow insecure access for the Swagger UI to the Gemstone server. >> >> The Amber Swagger-JS integration works quite nicely. >> I did not publish the code on Github because the integration is so tiny. I can send it to you if you like. >> Or no,... let me prepare a demo based on the Swagger petshop demo and I will put it online. >> Might take a day or two until I find some time. > Yes please write something about this, this is interesting for many people. > >> Sebastian >> >> >> >> >> Am 23.06.2015 um 13:05 schrieb sergio_101: >>> hey, sebastian.. this looks great! this looks like what i am after.. >>> >>> did you run into any problems or limitations using Amber as a front end? I have not tried Amber yet, so this might be the right time to give it a shot.. where did you find zinc-rest? a quick search turns up references to it.. should i be able to just install it via my image? >>> >>> andrew - i thought about using the seaside rest add on, but seaside seems to be alot of overhead just to run a rest server.. >>> >>> mariano - i am thinking about using api token.. >>> >>> >>> >>> On Tue, Jun 23, 2015 at 3:13 PM Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: >>> Am 23.06.2015 um 11:40 schrieb sergio_101: >>>> I have been a project coming up that I really onlyneed a restful API on. >>>> >>>> The front end will be first built on a mobile device(iOS )then back on possibly android, with a very stripped down web application. >>>> >>>> i would like to use pharo/gemstones as the database. >>>> >>>> is there a project out there that allows for such restful API development in pharo land? This would be so fun! >>>> >>>> thanks >>> I am not so sure what you mean exactly but this is my stack. >>> >>> I use pure Zinc-REST on the Gemstone side and the REST API is described in Swagger-Spec from within Gmestone. >>> Clients are VBA, Amber and Pharo and they utilize the Swagger API spec to access the server. >>> >>> Works pretty well and is much more preformant than the intial Pharo MongoDB backend I initially used. >>> >>> Have a look into http://smalltalkhub.com/#!/~HeSe/Swagger-Spec >>> There you can find most of the needed Swagger implementation some minor details like type constants are missing. >>> >>> Once your Gemstoneserver knows how to host his Swagger-Spec you can host it via https://github.com/swagger-api/swagger-ui >>> This saves a lot of explaning time to client developers. >>> >>> >>> Sebastian > >

June 25, 2015

Re: [Pharo-users] the importance of your story

by Serge Stinckwich

On Thu, Jun 25, 2015 at 3:56 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from the > StackOverflow and Github scene. I feel it is like a researcher without a > webpage. Without a webpage, he does not exist. I also have this "coup de blues" from time to time for similar reason and because I have to fight sometimes to defend this choice. Thank you Doru for giving us inspiration for the future. I will come to ESUG this year. This is usually a good place to have a boost for several months after. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 25, 2015

DNS level changes for smalltalkhub.com Friday

by Marcus Denker

Hello, Friday morning we will do some DNS level changes for smalltalkhub.com. This should normally have no impact on the server, as the new DNS server will point to the same IP as the old. Marcus

June 25, 2015

Re: [Pharo-users] the importance of your story

by Thierry Goubier

2015-06-25 15:56 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Thanks Doru for your inspiring words. > > Recently I had a âcoup de bluesâ because Pharo is completely absent from > the StackOverflow and Github scene. I feel it is like a researcher without > a webpage. Without a webpage, he does not exist. > Well, we could put Roassal on github ;) > > But I have faith things will soon change... > I hope so. It would make Roassal configurations and versions a tad easier :) If I was to use Roassal in a professionnal product, I'd be really tempted to do a freeze of Roassal on github along with a few of its dependencies :P Thierry > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". > While the talk is less technical, I did exemplified the message by demoing > Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think > our system as being niche and perhaps not mature enough. We need to change > that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the > implementation. The Spotter implementation is 3500 lines of code -- and > that it is so large because it currently comes with its own widgets. > Furthermore, the extensions average 8 lines per custom processor (including > the method header and the pragma). This is orders of magnitude smaller than > what is typically out there, and it is precisely the reason why we can > compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for > ourselves. For example, with GT we do not want to compete. We want to > outcompete. So can you. > > While details are important, high goals require us to get away from those > details. Only polishing details will tend to limit you to incremental > improvements. We need to jump from time to time. But, these jumps are hard. > On the one hand, it is hard to find the right jump and convince people to > jump with you. On the other hand, they are hard to predict. For example, > Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make > us dream. And the beauty is that Pharo breaths such a story. We should not > limit ourselves to that story only. For example, with GT we want to > reinvent the developer experience by making the developer be able to mold > visual tools to her context because that is the only effective way to build > sustainable systems. This little point of view will turn the IDE upside > down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you > build. And remember that Pharo already offers a beautiful story to start > from. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

June 25, 2015

Re: [Pharo-users] the importance of your story

by Alexandre Bergel

Thanks Doru for your inspiring words. Recently I had a âcoup de bluesâ because Pharo is completely absent from the StackOverflow and Github scene. I feel it is like a researcher without a webpage. Without a webpage, he does not exist. But I have faith things will soon change... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 25, 2015, at 8:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. > > There are several things I would like to emphasize. > > I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. > > One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. > > But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. > > While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. > > Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. > > Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

June 25, 2015