June 2015 - Pharo-users - lists.pharo.org

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

by 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 23, 2015

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

by Mariano Montone

Just curious. How do you implement authorization/authentication? Is there OAuth(2) support? Or you just use api token? Mariano On 23/06/15 16:12, Sebastian Heidbrink 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 23, 2015

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

by Andrew Glynn

In the event you need a bit more than the below would buy you (although it sounds like it would be fine) Seaside has a REST add-on -> http://book.seaside.st/book/advanced/restful Andrew From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> on behalf of Sebastian Heidbrink <sheidev(a)yahoo.de> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Tuesday, June 23, 2015 at 3:12 PM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] RESTful API with Pharo with Gemstones 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 23, 2015

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

by Sebastian Heidbrink

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 23, 2015

RESTful API with Pharo with Gemstones

by 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 23, 2015

Re: [Pharo-users] Any YAML parser?

by Julien Delplanque

Oh thanks! I'll search through this web site next time before asking :)... On 22/06/15 01:50, Peter UhnÃ¡k wrote: > I suggest using http://forum.world.st/ for searching through mailing lists; > using Google is often hit-or-miss (which even with all its neural networks > and tracking me everywhere is still after years suggesting Pharaoh...) > > Anyway, there seems to be something > http://forum.world.st/PetitYAML-td4803677.html > > If you are not familiar with PetitParser, there's a chapter about it in > PBE2 ( > http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.… > ) > > Peter > > On Sat, Jun 20, 2015 at 4:10 PM, Julien Delplanque <julien(a)tamere.eu> wrote: > >> Hi everybody, >> >> I googled a bit for a YAML parser in Pharo but I didn't found anything. >> >> Does anybody wrote a YAML parser for Pharo? >> >> Regards, >> Julien >> >>

June 23, 2015

Re: [Pharo-users] Roasal: Putting a white background instead of a transparent one in word clouds

by Alexandre Bergel

Done! Sorry for taking so long before actingâ¦ Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 17, 2015, at 5:56 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > There is any other way I can help with debugging this? Should I open a bug report to get this solved on Roassal? > This is best directed at Alex, but I would think that the solution should be pretty straight forward (maybe just copying part of the solution between the exporters). > > Alex: could you please rename DCTRCanvasExporter to TRCanvasExporter? Or whatever you fancy, but without the DC prefix. This was mentioned before by Jan but probably got lost somewhere. > > Peter

June 23, 2015

Re: [Pharo-users] Roasal: Putting a white background instead of a transparent one in word clouds

by Alexandre Bergel

Hi Jan! Sorry to replied so lately. I have renamed DCTRCanvasExporter into RTCanvasExporter. As you said, it works essentially on Trachel for now. However, I suspect this will change. You often want to particularize the export (e.g., do you want to have the menu or not?) Thanks! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 17, 2015, at 6:30 PM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> wrote: > > Second, it's not much of a problem, but in the class name, > DCTRCanvasExporter, the "DC" letters we use to indicate it is part of our > project, DynaCASE, but since it became part of whole roassal, I think the > "DC" is not appropriate anymore there.

June 23, 2015

Re: [Pharo-users] Moose

by abdelghani ALIDRA

Ok. Thanks a lot. Abdelghani DeÂ : Tudor Girba <tudor(a)tudorgirba.com> ÃÂ : abdelghani ALIDRA <alidrandco(a)yahoo.fr> CcÂ : Any question about pharo is welcome <pharo-users(a)lists.pharo.org> EnvoyÃ© le : Mardi 23 juin 2015 13h51 ObjetÂ : Re: [Pharo-users] Moose You do not have to return anything if you do not have any information. FAMIXAssociation already does that job for you. Doru On Tue, Jun 23, 2015 at 11:42 AM, abdelghani ALIDRA <alidrandco(a)yahoo.fr> wrote: Thank you Tudor, Yes, it makes sence.Then I suppose that I just return nil if I dont want to display the previous and next information. Regards DeÂ : Tudor Girba <tudor(a)tudorgirba.com> ÃÂ : abdelghani ALIDRA <alidrandco(a)yahoo.fr>; Any question about pharo is welcome <pharo-users(a)lists.pharo.org> EnvoyÃ© le : Lundi 22 juin 2015 21h25 ObjetÂ : Re: [Pharo-users] Moose Hi, from/to are derived properties and they should describe the association. For example: FAMIXAccess>> from ^ self accessorÂ FAMIXAccess>> to ^ self variableÂ next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code: self doSomething.self doSomethingElse. you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived). Does this make sense? Btw, these questions are better suited for the Moose mailing list:http://www.moosetechnology.org/#twitter Cheers,Doru On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco(a)yahoo.fr> wrote: Hi everybody, when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to?if I make MyFamixClass>>from^previousthe same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass)Who can one avoid that? Regards Abdelghani -- www.tudorgirba.com "Every thing has its own flow" -- www.tudorgirba.com "Every thing has its own flow"

June 23, 2015

Re: [Pharo-users] Moose

by Tudor Girba

You do not have to return anything if you do not have any information. FAMIXAssociation already does that job for you. Doru On Tue, Jun 23, 2015 at 11:42 AM, abdelghani ALIDRA <alidrandco(a)yahoo.fr> wrote: > Thank you Tudor, > > Yes, it makes sence. > Then I suppose that I just return nil if I dont want to display the > previous and next information. > > Regards > > ------------------------------ > *De :* Tudor Girba <tudor(a)tudorgirba.com> > *Ã :* abdelghani ALIDRA <alidrandco(a)yahoo.fr>; Any question about pharo > is welcome <pharo-users(a)lists.pharo.org> > *EnvoyÃ© le :* Lundi 22 juin 2015 21h25 > *Objet :* Re: [Pharo-users] Moose > > Hi, > > from/to are derived properties and they should describe the association. > For example: > > FAMIXAccess>> from > ^ self accessor > FAMIXAccess>> to > ^ self variable > > next/previous denote the position of the association in the code with > respect to the other associations. For example, imagine this Pharo code: > > self doSomething. > self doSomethingElse. > > you will get two FAMIXInvocations, and these can be linked through the > previous property (next is derived). > > Does this make sense? > > Btw, these questions are better suited for the Moose mailing list: > http://www.moosetechnology.org/#twitter > > Cheers, > Doru > > > > > > On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco(a)yahoo.fr> > wrote: > > Hi everybody, > > when working with the FAMIX meta model, one must implement the previous, > next, from and to methods for each class extending FAMIXAssosiation. > What is the diffence between previous/from and next/to? > if I make > MyFamixClass>>from > ^previous > the same information is displayed twice in the Moose panel (because both > methods are annotated with the MSEProperty in the superclass) > Who can one avoid that? > > Regards > > Abdelghani > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

June 23, 2015