March 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] redefining default smalltalk shortcuts in (pluggable)textmorph

by Tudor Girba

Hi, I am trying to redefine shortcuts such as Cmd+s for an instance of PluggableTextMorph, but I cannot find a way. Now that we have Kemappings in the image, I see that Cmd+s is defined in: TextMorph>>buildTextEditorKeymapsOn: aBuilder <keymap> (aBuilder shortcut: #accept) category: #TextMorph default: $s ctrl win | $s ctrl unix | $s command mac do: [ :morph | morph acceptContents ]. aBuilder attachShortcutCategory: #TextMorph to: TextMorph. Nice, but this defines a behavior that is global to the TextMorph class. The Keymappings extensions from Morph do allow some degree of morph specific shortcuts, but it seems that the only thing I can do is: - create a category with my keymappings; the category must have a name - registered it the dispatcher - tell the morph to attach this category by passing the name of the category I could not get a code that sets this up because I stumbled across too much symbol-based indirection. Can anyone help? Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

March 24, 2013

Re: [Pharo-project] Loading webdoc

by Sven Van Caekenberghe

On 24 Mar 2013, at 20:15, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-03-24, at 20:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 24 Mar 2013, at 19:37, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>> >>>> Hi Camillo! >>>> >>>> I was trying to load webdoc but there are a lot of not loading dependencies >>>> (Seaside, grease, Omnibrowser...)... The configuration does not load for >>>> 1.4 nor for 2.0... I was using this snippets: >>>> >>>> for 2.0 >>>> >>>> Gofer new >>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>> configurationOf: 'WebDoc'; >>>> loadDevelopment. >>>> >>>> for 1.4 >>>> >>>> Gofer new >>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>> package: 'ConfigurationOfWebDoc'; >>>> load. >>>> >>>> ConfigurationOfWebDoc loadDevelopment. >>>> >>>> Any hint? How did you bypass them in a safe way? >>>> tx, >>>> Guille >>> >>> for 1.4 it should work out of the box. >>> >>> for 2.0 I can only make it work after there is a valid Configuration for >>> seaside :/. >>> So for now under 2.0 you have to follow this stupid manual process: >>> - get a 2.0 seaside image: >>> https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ >>> - manually install the dev version of PPMarkdownParser from: >>> http://smalltalkhub.com/#!/~dh83/petitmarkdown >>> - then load the latest package from for 2.0 from here: >>> http://smalltalkhub.com/#!/~dh83/webdoc >>> >>> Maybe I missed that there is now a 2.0 config for seaside, if that is so >>> let me know and I will create a proper configuration for webdoc, beacuse >>> this process here is plain stupid :D. >> >> It seems like the whole world is waiting for this elusive configuration, what a messâ¦ >> >> It is just a question of making some decisions and going forward. > > I guess I missed the point, but can't we just make the configuration do > whatever the jenkins job does and declare it as the development version > for 2.0? We (as the Pharo community) will most probably have to do that, but it is not the right way or the best for the future. Seaside has currently two main versions 3.0.x and 3.1 and targets many platforms, that is what Metacello is for, but it makes the config complex. Normally, the main Seaside developers should have to do this, it is their (communities') code. Sven

March 24, 2013

Re: [Pharo-project] Loading webdoc

by Camillo Bruni

On 2013-03-24, at 20:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 24 Mar 2013, at 19:37, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> >> On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >>> Hi Camillo! >>> >>> I was trying to load webdoc but there are a lot of not loading dependencies >>> (Seaside, grease, Omnibrowser...)... The configuration does not load for >>> 1.4 nor for 2.0... I was using this snippets: >>> >>> for 2.0 >>> >>> Gofer new >>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>> configurationOf: 'WebDoc'; >>> loadDevelopment. >>> >>> for 1.4 >>> >>> Gofer new >>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>> package: 'ConfigurationOfWebDoc'; >>> load. >>> >>> ConfigurationOfWebDoc loadDevelopment. >>> >>> Any hint? How did you bypass them in a safe way? >>> tx, >>> Guille >> >> for 1.4 it should work out of the box. >> >> for 2.0 I can only make it work after there is a valid Configuration for >> seaside :/. >> So for now under 2.0 you have to follow this stupid manual process: >> - get a 2.0 seaside image: >> https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ >> - manually install the dev version of PPMarkdownParser from: >> http://smalltalkhub.com/#!/~dh83/petitmarkdown >> - then load the latest package from for 2.0 from here: >> http://smalltalkhub.com/#!/~dh83/webdoc >> >> Maybe I missed that there is now a 2.0 config for seaside, if that is so >> let me know and I will create a proper configuration for webdoc, beacuse >> this process here is plain stupid :D. > > It seems like the whole world is waiting for this elusive configuration, what a messâ¦ > > It is just a question of making some decisions and going forward. I guess I missed the point, but can't we just make the configuration do whatever the jenkins job does and declare it as the development version for 2.0?

March 24, 2013

Re: [Pharo-project] Loading webdoc

by Sven Van Caekenberghe

On 24 Mar 2013, at 19:37, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> Hi Camillo! >> >> I was trying to load webdoc but there are a lot of not loading dependencies >> (Seaside, grease, Omnibrowser...)... The configuration does not load for >> 1.4 nor for 2.0... I was using this snippets: >> >> for 2.0 >> >> Gofer new >> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >> configurationOf: 'WebDoc'; >> loadDevelopment. >> >> for 1.4 >> >> Gofer new >> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >> package: 'ConfigurationOfWebDoc'; >> load. >> >> ConfigurationOfWebDoc loadDevelopment. >> >> Any hint? How did you bypass them in a safe way? >> tx, >> Guille > > for 1.4 it should work out of the box. > > for 2.0 I can only make it work after there is a valid Configuration for > seaside :/. > So for now under 2.0 you have to follow this stupid manual process: > - get a 2.0 seaside image: > https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ > - manually install the dev version of PPMarkdownParser from: > http://smalltalkhub.com/#!/~dh83/petitmarkdown > - then load the latest package from for 2.0 from here: > http://smalltalkhub.com/#!/~dh83/webdoc > > Maybe I missed that there is now a 2.0 config for seaside, if that is so > let me know and I will create a proper configuration for webdoc, beacuse > this process here is plain stupid :D. It seems like the whole world is waiting for this elusive configuration, what a messâ¦ It is just a question of making some decisions and going forward. <frustrated/>

March 24, 2013

Re: [Pharo-project] Loading webdoc

by Camillo Bruni

On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi Camillo! > > I was trying to load webdoc but there are a lot of not loading dependencies > (Seaside, grease, Omnibrowser...)... The configuration does not load for > 1.4 nor for 2.0... I was using this snippets: > > for 2.0 > > Gofer new > url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; > configurationOf: 'WebDoc'; > loadDevelopment. > > for 1.4 > > Gofer new > url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; > package: 'ConfigurationOfWebDoc'; > load. > > ConfigurationOfWebDoc loadDevelopment. > > Any hint? How did you bypass them in a safe way? > tx, > Guille for 1.4 it should work out of the box. for 2.0 I can only make it work after there is a valid Configuration for seaside :/. So for now under 2.0 you have to follow this stupid manual process: - get a 2.0 seaside image: https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ - manually install the dev version of PPMarkdownParser from: http://smalltalkhub.com/#!/~dh83/petitmarkdown - then load the latest package from for 2.0 from here: http://smalltalkhub.com/#!/~dh83/webdoc Maybe I missed that there is now a 2.0 config for seaside, if that is so let me know and I will create a proper configuration for webdoc, beacuse this process here is plain stupid :D.

March 24, 2013

[Pharo-project] Loading webdoc

by Guillermo Polito

Hi Camillo! I was trying to load webdoc but there are a lot of not loading dependencies (Seaside, grease, Omnibrowser...)... The configuration does not load for 1.4 nor for 2.0... I was using this snippets: for 2.0 Gofer new url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; configurationOf: 'WebDoc'; loadDevelopment. for 1.4 Gofer new url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; package: 'ConfigurationOfWebDoc'; load. ConfigurationOfWebDoc loadDevelopment. Any hint? How did you bypass them in a safe way? tx, Guille

March 24, 2013

Re: [Pharo-project] [3.0] 9 issues need reviews

by stephane ducasse

Thanks I will try to allocate time to have a look at them. Stef > Hi, > > Even with the integrations of saturday, there was a lot done that need > attention: > > > https://pharo.fogbugz.com/f/filters/22/3-0-Integration > > 6 are ready to be integrated, > 9 need a code review. > > > > (for getting an account at fogbugz, see http://bugs.pharo.org ) > > Marcus > >

March 24, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by stephane ducasse

You are probably right. Now we are all underestimating the amount of energy that we spend on addressing stupid/boring/idiot issues that unfortunately must be done. Yes esteban, marcus and Igor I know you know. I think that in general we do not value these little issues, we believe that somebody will address them, and of course for free (because this is open-source). Now we will see if the community succeeds to understand that because we have the consortium and the association but may be they will not succeed (but not because we did not put energy into it). Stef >>>> On Mar 24, 2013, at 10:40 AM, "Sean P. DeNigris" >>>> <sean(a)clipperadams.com> wrote: >>>> >>>>> Mark Bestley wrote >>>>>> For OSX what should probably happen is that the image is saved to >>>>>> ~/Library/Application Support >>>>> That doesn't sound right to me. How about the use case where I have a >>>>> portable image on a USB stick? I don't want to make a local copy of the >>>>> image, just run it. I get putting the VM in a shared predictable >>>>> location, >>>>> but why the image? How does one then keep multiple Pharo 2.0's on >>>>> the same >>>>> computer? >>>> We will not do it like this. >>>> >>>> What is planned is that the "Pharo installation" contains a template >>>> (read only). >>>> When you open the template, it will ask you to save the image to your >>>> home directory. >>>> >>>> Images are like documents, it should be very easy to have a lot of them. >>> >>> >>> why should we decide where people should put them. >>> I put the images where I want them to be. > > You have learnt where you want them to be. The defaults are for a user who does not know where to put them. As well as the following ... > >> Because corporate system administrators expect programs to put things in >> the "correct" locations as defined by the OS vendor. >> This helps OS platform certification and even if you don't go that far, >> it lends an air of professionalism. > > > >> It only needs to be a default. >> > > I was only suggesting this as a default. It also helps new users so that when they ask for help with OS related stuff elsewhere Pharo appears to act like a normal OS program, this would help to limit the number of responses like the original article where Pharo did not fit in with what was expected by the user of the Operating system. > > However the freedom to do what ever is wanted should be kept as well. > > >>>> I should write down what is the planâ¦ sadly I have too much else to >>>> do, so this >>>> will take a while. >>>> >>>> Marcus >>> >>> >>> >> >> >> > > >

March 24, 2013

[Pharo-project] [3.0] 9 issues need reviews

by Marcus Denker

Hi, Even with the integrations of saturday, there was a lot done that need attention: https://pharo.fogbugz.com/f/filters/22/3-0-Integration 6 are ready to be integrated, 9 need a code review. (for getting an account at fogbugz, see http://bugs.pharo.org ) Marcus

March 24, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Mark Bestley

On 24/03/2013 17:19, Ben Coman wrote: > StÃ©phane Ducasse wrote: >> On Mar 24, 2013, at 10:43 AM, Marcus Denker >> <marcus.denker(a)inria.fr> wrote: >> >>> On Mar 24, 2013, at 10:40 AM, "Sean P. DeNigris" >>> <sean(a)clipperadams.com> wrote: >>> >>>> Mark Bestley wrote >>>>> For OSX what should probably happen is that the image is saved to >>>>> ~/Library/Application Support >>>> That doesn't sound right to me. How about the use case where I have a >>>> portable image on a USB stick? I don't want to make a local copy of the >>>> image, just run it. I get putting the VM in a shared predictable >>>> location, >>>> but why the image? How does one then keep multiple Pharo 2.0's on >>>> the same >>>> computer? >>> We will not do it like this. >>> >>> What is planned is that the "Pharo installation" contains a template >>> (read only). >>> When you open the template, it will ask you to save the image to your >>> home directory. >>> >>> Images are like documents, it should be very easy to have a lot of them. >> >> >> why should we decide where people should put them. >> I put the images where I want them to be. You have learnt where you want them to be. The defaults are for a user who does not know where to put them. As well as the following ... > Because corporate system administrators expect programs to put things in > the "correct" locations as defined by the OS vendor. > This helps OS platform certification and even if you don't go that far, > it lends an air of professionalism. > It only needs to be a default. > I was only suggesting this as a default. It also helps new users so that when they ask for help with OS related stuff elsewhere Pharo appears to act like a normal OS program, this would help to limit the number of responses like the original article where Pharo did not fit in with what was expected by the user of the Operating system. However the freedom to do what ever is wanted should be kept as well. >>> I should write down what is the planâ¦ sadly I have too much else to >>> do, so this >>> will take a while. >>> >>> Marcus >> >> >> > > >

March 24, 2013