- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo Days 2016 @ end of next week

by stepharo

Oui tintin est en deuil. Stef Le 24/3/16 10:46, Sven Van Caekenberghe a Ã©crit : > Much can be said about what happened this week > > https://en.wikipedia.org/wiki/2016_Brussels_bombings > > but basically most people are just very, very sad > > > An international community working together on open source software as > a common good that can benefit anyone anywhere is one of those things > that can make a difference, that can show how living together should be. > > > The Pharo Days 2016 take place at the end of next week, as planned. We > already have 25 confirmed registrations. Please consider joining us. > Registrations close at the beginning of next week (Tuesday March 29th, > midnight). We urge you to please register as soon as possible. > > http://pharodays2016.pharo.org > > > We hope to see you all soon ! > > > The Pharo Board >

March 24, 2016

Re: [Pharo-users] [Pharo-dev] Pharo Days 2016 @ end of next week

by Sven Van Caekenberghe

> On 24 Mar 2016, at 11:08, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 24-03-16 10:46, Sven Van Caekenberghe wrote: >> Much can be said about what happened this week >> >> https://en.wikipedia.org/wiki/2016_Brussels_bombings >> >> but basically most people are just very, very sad > Indeed > >> The Pharo Days 2016 take place at the end of next week, as planned. We already >> have 25 confirmed registrations. Please consider joining us. Registrations close >> at the beginning of next week (Tuesday March 29th, midnight). We urge you to >> please register as soon as possible. >> > > Payment doesn't work from the Netherlands. It tries to force me to create a > paypal account. I believe that is indeed the only option (although, I thought at least, that you do not really have to create an account, that you can do just a payment through them, but that option is probably well hidden, or maybe gone). If you really want to pay another way, just opt for the invoice/pay afterwards option, and I'll send you an invoice and you can then pay by bank transfer. Sven

March 24, 2016

Pharo Days 2016 @ end of next week

by Sven Van Caekenberghe

Much can be said about what happened this week https://en.wikipedia.org/wiki/2016_Brussels_bombings but basically most people are just very, very sad An international community working together on open source software as a common good that can benefit anyone anywhere is one of those things that can make a difference, that can show how living together should be. The Pharo Days 2016 take place at the end of next week, as planned. We already have 25 confirmed registrations. Please consider joining us. Registrations close at the beginning of next week (Tuesday March 29th, midnight). We urge you to please register as soon as possible. http://pharodays2016.pharo.org We hope to see you all soon ! The Pharo Board

March 24, 2016

Re: [Pharo-users] Customizing SmalltalkEditor context menu issue

by jtuchel＠objektfabrik.de

I am glad I am not the only one with a deep dislike for Pragmas ;-) Am 24.03.16 um 09:54 schrieb Dimitris Chloupis: > you are not the only one, I have been coding 2 years now with Pharo , > pragmas still look as the most non smalltalky things as the first time > I discovered them. > > On Wed, Mar 23, 2016 at 10:58 PM Ala'a Mohammad <amalawi(a)gmail.com > <mailto:amalawi@gmail.com>> wrote: > > Thanks for the great explanation! > > I had reached an almost the target menu by modify all of > SmalltalkEditor, TClassDescription and AbstractNautilusUI classes > methods. > > To be honest I'm newbie and this pragma thing seems foreign between > the other pleasant experiences with smalltaking, and kind of hindrance > for the exploratory nature of normal smalltalk code browsing. > > Regards, > > Ala'a > > On Wed, Mar 23, 2016 at 2:05 AM, Nicolai Hess > <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: > > > > > > 2016-03-22 22:27 GMT+01:00 Ala'a Mohammad <amalawi(a)gmail.com > <mailto:amalawi@gmail.com>>: > >> > >> Hi, > >> > >> I'm trying to modify the context menu of the code editor through > >> modification to SmalltalkEditor class >> smalltalkEditorMenuOn: > > > > > > Hi Ala'a > > > >> > >> > >> testing the modification with > >> (PragmaMenuBuilder pragmaKeyword: 'smalltalkEditorMenu' model: nil) > >> menu popUpInWorld > > > > > > The context menu for Nautilus code pane works a bit different. > > Can you test if your modifications are working in Workspace (or the > > workspace are in a basic > > inspector). > > > >> > >> > >> succeeds, and shows the final shape of the menu that I want (photo > >> attached), but the actual one used by the system is messed up! > (photo > >> attached) > >> > >> I tried also to execute TextEditor class >> initialize, but > that did not > >> help. > >> > >> Another thing I did was trying to find senders and references > to the > >> SmalltalkEditor class >> smalltalkEditorMenuOn, and find none! > (So who > >> is calling that with a 'aBuilder'?), and the only > implementation of it > >> is the one I'm trying to update (more confusion - pardon the > puzzled > >> newbie). > > > > > > The smalltalkEditorMenuOn: method, containing the > smalltalkEditorMenu-Pragma > > is not > > called explicit. Instead, there is a Method SmalltalkEditor class >> > > smalltalkEditorMenuKeyword > > that returns the pragma name ('smalltalkEditorMenu') used to > collect all > > methods using this pragma > > for defining the menus. > > > > For Nautilus, there is another step involved. First it calls > > SmalltalkEditor yellowButtonMenu > > this will ask for the pragma (SmalltalkEditor class >> > > smalltalkEditorMenuKeyword) and builds a menu > > from every method using this pragma (here only the method > SmalltalkEditor > > class >> smalltalkEditorMenuOn: ). > > NOW it modifies this menu and adds (from all methods using the > pragma > > <nautilusGlobalSourceCodeMenu> and reorganize some more entries > (this is > > ugly, yes). > > > >> > >> > >> Attached are the photos for the original menu, target menu and the > >> messed up menu. > >> > >> I'm using Pharo 4.0 from the official download for Linux from > Pharo.org. > >> > >> my system is the following: > >> Linuxmint 17.1 Rebecca > >> 3.13.0-37-generic #64-Ubuntu SMP > >> > >> What I'm doing wrong? and/or what I'm missing? > >> > >> Thanks in advance for the help. > >> > >> Regards, > >> > >> Ala'a > > > > > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

March 24, 2016

Re: [Pharo-users] Customizing SmalltalkEditor context menu issue

by Dimitris Chloupis

you are not the only one, I have been coding 2 years now with Pharo , pragmas still look as the most non smalltalky things as the first time I discovered them. On Wed, Mar 23, 2016 at 10:58 PM Ala'a Mohammad <amalawi(a)gmail.com> wrote: > Thanks for the great explanation! > > I had reached an almost the target menu by modify all of > SmalltalkEditor, TClassDescription and AbstractNautilusUI classes > methods. > > To be honest I'm newbie and this pragma thing seems foreign between > the other pleasant experiences with smalltaking, and kind of hindrance > for the exploratory nature of normal smalltalk code browsing. > > Regards, > > Ala'a > > On Wed, Mar 23, 2016 at 2:05 AM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > > > > > > 2016-03-22 22:27 GMT+01:00 Ala'a Mohammad <amalawi(a)gmail.com>: > >> > >> Hi, > >> > >> I'm trying to modify the context menu of the code editor through > >> modification to SmalltalkEditor class >> smalltalkEditorMenuOn: > > > > > > Hi Ala'a > > > >> > >> > >> testing the modification with > >> (PragmaMenuBuilder pragmaKeyword: 'smalltalkEditorMenu' model: nil) > >> menu popUpInWorld > > > > > > The context menu for Nautilus code pane works a bit different. > > Can you test if your modifications are working in Workspace (or the > > workspace are in a basic > > inspector). > > > >> > >> > >> succeeds, and shows the final shape of the menu that I want (photo > >> attached), but the actual one used by the system is messed up! (photo > >> attached) > >> > >> I tried also to execute TextEditor class >> initialize, but that did not > >> help. > >> > >> Another thing I did was trying to find senders and references to the > >> SmalltalkEditor class >> smalltalkEditorMenuOn, and find none! (So who > >> is calling that with a 'aBuilder'?), and the only implementation of it > >> is the one I'm trying to update (more confusion - pardon the puzzled > >> newbie). > > > > > > The smalltalkEditorMenuOn: method, containing the > smalltalkEditorMenu-Pragma > > is not > > called explicit. Instead, there is a Method SmalltalkEditor class >> > > smalltalkEditorMenuKeyword > > that returns the pragma name ('smalltalkEditorMenu') used to collect all > > methods using this pragma > > for defining the menus. > > > > For Nautilus, there is another step involved. First it calls > > SmalltalkEditor yellowButtonMenu > > this will ask for the pragma (SmalltalkEditor class >> > > smalltalkEditorMenuKeyword) and builds a menu > > from every method using this pragma (here only the method SmalltalkEditor > > class >> smalltalkEditorMenuOn: ). > > NOW it modifies this menu and adds (from all methods using the pragma > > <nautilusGlobalSourceCodeMenu> and reorganize some more entries (this is > > ugly, yes). > > > >> > >> > >> Attached are the photos for the original menu, target menu and the > >> messed up menu. > >> > >> I'm using Pharo 4.0 from the official download for Linux from Pharo.org. > >> > >> my system is the following: > >> Linuxmint 17.1 Rebecca > >> 3.13.0-37-generic #64-Ubuntu SMP > >> > >> What I'm doing wrong? and/or what I'm missing? > >> > >> Thanks in advance for the help. > >> > >> Regards, > >> > >> Ala'a > > > > > >

March 24, 2016

Re: [Pharo-users] Beta testers for the Pharo mooc

by Jeff Gray

I tried the link. I got a form to send a mail but it errored with 'Missing domain' Are you getting responses? -- View this message in context: http://forum.world.st/Beta-testers-for-the-Pharo-mooc-tp4886075p4886225.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 24, 2016

Re: [Pharo-users] ZnUrl>>#= - Why Require Same Classes?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I am curious though why you subclasses ZnUrl. If you did not add structure > but only behaviour you could have added some extension methods. I implemented a ProtectedUrl, which carries around the additional information it needs (in this case an authenticated client) to be accessed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/ZnUrl-Why-Require-Same-Classes-tp4886102p4886221.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 24, 2016

Re: [Pharo-users] ZnUrl>>#= - Why Require Same Classes?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I don't think the mutability is a problem I thought it was a no-no for an object's hash to ever change, which it would if the path changed, no? ----- Cheers, Sean -- View this message in context: http://forum.world.st/ZnUrl-Why-Require-Same-Classes-tp4886102p4886220.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 24, 2016

Re: [Pharo-users] patterns for representing enumerations/constants

by Johan Fabry

Exactly the solution that I thought of :-) > On Mar 23, 2016, at 16:51, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > 2016-03-23 16:31 GMT-03:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>> I would do something like: >>> >>> Color named: #red. >>> Color named: #blue. >> >> >> That idea crossed my mind (it would be good for serialization from some >> external data), but how would you as user/programmer know what to put in >> there? >> The idea of enums is that you have a predetermined set of predetermined >> values, so this >> >>> Pros are that there is no endless lists of methods at class side >> >> >> is actually a con, because the user doesn't know them. >> >> Everyone knows red and blue, but nobody remembers to the letter >> domain-specific props (in fact half of the class-side colors you wouldn't >> guess you could use named). >> >> BormParticipantRole class selectors "#(#Approves #Undefined #Performs >> #Initiates #IsResponsible #Acquires #Cooperates #IsInformed #Consults)" >> BormParticipantType class selectors "#(#Organization #System #Person)" >> >> But maybe Color was wrong example because the set can be very large >> (although the set of options is also limited if you consider some >> standards). > > > You can have something at the class side that return the colors name, > using this example, by returning the keys of such dictionary. > > Something like > > YourClass class>>#colors > > ^Colors ifNil: [Colors := Dictionary new at: #red put: ...; at: > #blue put: ..; yourself] > > Then you can have > > YourClass class>>#colorsConstants > ^self colors keys asSortedCollection > > Regards > > Esteban A. Maringolo > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

March 23, 2016

Re: [Pharo-users] patterns for representing enumerations/constants

by Damien Pollet

On 23 March 2016 at 18:40, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Why / how ? >> > > As explained in the first example. > > Try adding #organization or #package methods to the class-side. > I'd rather have selector namespaces to remove homonymy conflictsâ¦

March 23, 2016