- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Dr. Geo 15.04

by Hilaire

Le 01/04/2015 00:19, phil(a)highoctane.be a Ã©crit : > > I guess > > Make ox and ox axes independent to the grid > > is > > Make ox and oy axes independent to the grid > Thanks, updated. > Dr Geo is about 20 years old now. > > Yes, it has been a long road to reach part of the Dr. Geo vision: from basic usage of interactive geometry to an empowered user with programming capabilities it was a long way. Only with Pharo, this vision became incredibly vivid with results beyond my initial expectations: not only Dr.Geo user can write script in a *comfortable environment*, more she can also study its code, and even modify it while DrGeo is in activity! >From now, there are many improvements to conduct[1], documentation to update and to improve[2]. I want communities to grow around DrGeo: community of users sharing their findings and experiments[3] and community of developers to make DrGeo bigger, better. Anyone willing to help to pursue this road is welcome to join! Hilaire [1] https://bugs.drgeo.eu [2] http://www.drgeo.eu/community/documentation [3] http://www.drgeo.eu/community/publication -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

April 1, 2015

[ANN] Pharo Consortium New Academic Partner: UMMISCO

by Marcus Denker

The Pharo Consortium is very happy to announce that UMMISCO has joined the Consortium as an Academic Partner. UMMISCO is an international research unit under the supervision of IRD (Research for Development) and UPMC (UniversitÃ© Pierre Marie Curie) located in France, Senegal, Morocco, Cameroun and Vietnam. UMMISCO group carries out research in Computer Science and Mathematics with the goal of modelling and simulation of complex systems with applications regarding southern countries concerns like : epidemiology modelling, disaster management, urban mobility and environmental monitoring. About - UMMISCO: http://www.ummisco.ird.fr - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

April 1, 2015

Re: [Pharo-users] Proxies: Subclassing nil

by Mariano Martinez Peck

On Wed, Apr 1, 2015 at 4:29 AM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > and the latest repo is: http://smalltalkhub.com/#!/~CAR/Ghost > but it has not diverged too much from the old one yet. > > Luc...something that would be super super cool is to take the proxies I implemented for Marea and adapt them as custom Ghost proxies. Because the idea of Ghost was mostly the design, not the code itself. The code was very very little. So in Marea proxies you can see how I: 1) Created a few different proxies for different purposes. For example, I created special proxies for classes and metaclasses. And each of them implements custom messages to avoid unnecessary interception (for example, MARMetaclassProxy implements #isMeta answering true. Both, proxy for Class and Metaclass implement: isKindOf: aClass ^ (aClass == Class) ifTrue: [ true ] ifFalse: [ super isKindOf: aClass ] "would be intercepted" and so on.... So basically....you are able to implement custom proxies and implement custom messages so that you avoid intercepting them. 2) In Marea, I have multiple proxies that store the information differently. So for example, Marea proxies needed a graph id and a "position" (an integer). If both were small enough, I was doing a bitShift and storing them in a super compact proxy class that would have only one small integer. So....what I want to say is that while ghost code is OK, the most interesting usage and development of those proxies is in Marea, in the category 'Marea-Proxies'. > #Luc > > 2015-04-01 8:29 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Mariano spent a couple of years on it so... >> >> >> >> Le 31/3/15 21:37, Denis Kudriashov a Ã©crit : >> >> Hi >> if you want to build proxy look at Ghost library from Mariano Martinez >> I not know right repository. Maybe this: >> http://smalltalkhub.com/#!/~CAR/Ghost/ or >> http://ss3.gemstone.com/ss/Ghost >> >> 2015-03-31 19:51 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> >>> From "Design Patterns" pg. 215: >>> >>> You can make[8] generic proxies in Smalltalk by defining classes >>> whose >>> superclass is nil and defining the doesNotUnderstand: method to handle >>> messages. >>> >>> [8] Almost all classes ultimately have Object as their superclass. >>> Hence >>> this is the same as saying "defining a class that doesn't have Object as >>> its >>> superclass." >>> >>> but in Pharo: >>> nil subclass: #MyProxy >>> instanceVariableNames: '' >>> classVariableNames: '' >>> category: '' >>> -> MessageNotUnderstood: receiver of >>> "subclass:instanceVariableNames:classVariableNames:category:" is nil >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Proxies-Subclassing-nil-tp4816443.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >> >> > -- Mariano http://marianopeck.wordpress.com

April 1, 2015

Re: [Pharo-users] [ANN] Dr. Geo 15.04

by Hilaire

Le 31/03/2015 23:13, Nicolai Hess a Ã©crit : > > This looks great! > Think about rating it on its Google+ page: http://google.com/+DrgeoEu Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

April 1, 2015

Re: [Pharo-users] [Pharo-dev] [ANN] New service: The Pharo catalog

by Esteban Lorenzano

> On 01 Apr 2015, at 13:04, Norbert Hartl <norbert(a)hartl.name> wrote: > > Cool! At the moment I'm searching where to put a description for the projects :) > I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken? because I have no idea where the project is. I just take the configurations in the meta repos. Esteban > > Norbert > >> Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >> Hi, >> >> Last week I made a super small project to consolidate all projects published in all metarepos. >> Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. >> Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) >> >> You can see the catalog here: >> >> http://catalog.pharo.org <http://catalog.pharo.org/> >> >> and a JSON variant here: >> >> http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> >> >> enjoy, >> Esteban >> >> >

April 1, 2015

Re: [Pharo-users] [ANN] New service: The Pharo catalog

by kilon alios

" is because thatâs the description of the version (or baseline), not the project description (thatâs the place of #catalogDescription, and thatâs why it is on class side: is more durable). cheers, Esteban" ah ok makes sense now. Will do thanks.

April 1, 2015

Re: [Pharo-users] [Pharo-dev] [ANN] New service: The Pharo catalog

by Norbert Hartl

Cool! At the moment I'm searching where to put a description for the projects :) I was asking myself why the link of a project opens a small project description taken from the metacello config instead just opening the project on smalltalkhub. Or from where are the projects in this list are taken? Norbert > Am 01.04.2015 um 12:13 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > Last week I made a super small project to consolidate all projects published in all metarepos. > Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. > Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) > > You can see the catalog here: > > http://catalog.pharo.org <http://catalog.pharo.org/> > > and a JSON variant here: > > http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> > > enjoy, > Esteban > >

April 1, 2015

Re: [Pharo-users] [ANN] New service: The Pharo catalog

by Esteban Lorenzano

> On 01 Apr 2015, at 12:53, kilon alios <kilon.alios(a)gmail.com> wrote: > > > > "yes, check âa note to developersâ link :)" > > yeap thats an obvious one, should have clicked that in the first place. > > Question: I see you ask for dedicate methods. In this case catalogDescription . Is it really necessary , metacello spec already offers sped description: which my project already takes advantage of for example > ----------------------------------------------------------------------------- > <version: '0.1' imports: #('0.2-baseline' )> > > spec for: #'common' do: [ > spec blessing: #'stable'. > spec description: 'version 0.1 > This is 0.1 the first stable release of Ephestos. This release contains the following > > -a socket client bridge for sending and receiving messages from Blender which acts as a socket server > > - a sendMessage: message to send python command as string to Blender to be executed > > - a python parser that allows the pharo syntax to be used to parse to a python command for simple things like calling instance and class method and assigning class and instance variables > > - a getValue: message for reading python values from variables > > - support for triggering the pharo dedugger on python error > > - support for sending multiple lines of python code in a single message'. > spec author: 'kilonAlios'. > spec timestamp: '9/20/2014 20:15'. > spec package: 'Ephestos' with: 'Ephestos-kilonAlios.16'. ]. > ---------------------------------------------------------------------------------------------------- > > I dont mind defining a separate method, I am just curious. is because thatâs the description of the version (or baseline), not the project description (thatâs the place of #catalogDescription, and thatâs why it is on class side: is more durable). cheers, Esteban > > " they will think I suck at design" > > good Design , is like good code, needs time. Loads of time. Time you dont have and is understandable. Still its a very useful to have a project catalogue and thank you. > > >

April 1, 2015

Re: [Pharo-users] [ANN] New service: The Pharo catalog

by kilon alios

"yes, check âa note to developersâ link :)" > yeap thats an obvious one, should have clicked that in the first place. Question: I see you ask for dedicate methods. In this case catalogDescription . Is it really necessary , metacello spec already offers sped description: which my project already takes advantage of for example ----------------------------------------------------------------------------- <version: '0.1' imports: #('0.2-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 0.1 This is 0.1 the first stable release of Ephestos. This release contains the following -a socket client bridge for sending and receiving messages from Blender which acts as a socket server - a sendMessage: message to send python command as string to Blender to be executed - a python parser that allows the pharo syntax to be used to parse to a python command for simple things like calling instance and class method and assigning class and instance variables - a getValue: message for reading python values from variables - support for triggering the pharo dedugger on python error - support for sending multiple lines of python code in a single message'. spec author: 'kilonAlios'. spec timestamp: '9/20/2014 20:15'. spec package: 'Ephestos' with: 'Ephestos-kilonAlios.16'. ]. ---------------------------------------------------------------------------------------------------- I dont mind defining a separate method, I am just curious. " they will think I suck at design" good Design , is like good code, needs time. Loads of time. Time you dont have and is understandable. Still its a very useful to have a project catalogue and thank you.

April 1, 2015

Re: [Pharo-users] [ANN] New service: The Pharo catalog

by Sven Van Caekenberghe

Cool! > On 01 Apr 2015, at 12:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Last week I made a super small project to consolidate all projects published in all metarepos. > Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. > Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) > > You can see the catalog here: > > http://catalog.pharo.org > > and a JSON variant here: > > http://catalog.pharo.org/catalog/json > > enjoy, > Esteban > >

April 1, 2015