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

Re: [Pharo-dev] TextAttribute, TextAction and TextDoIt or TextURL: not working

by Sean P. DeNigris

philippeback wrote > doing: > > ((Text withAll: 'foo') , (Text string: 'some link' attribute: (TextURL new > url:'http://philippeback.eu')) , (Text withAll: 'bar')) asMorph > openInWorld. > > gives me a nice purple 'some link' bit but clicking on it fails with > > MessageNotUnderstood: TextURL>>actOnClick:for:in:editor: Issue 12075: Fix TextActions and Add SourceWebBrowser for TextUrl Fix in inbox: TextDoIt, TextPrintIt, PluggableTextAttribute, and TextURL now work. This fix also adds a SourceWebBrowser, which simply opens the page source in a Workspace, and registers it under "tools webBrowser". The idea is that e.g. ExternalWebBrowser or another external project could override this very basic functionality. I'm also attaching the .cs to Nabble TextActions.cs <http://forum.world.st/file/n4719448/TextActions.cs> in case you want it in pre-3.0 (tested in 2.0). To test: ws := Workspace openContents: 'Transcript open'. wsWindow := World submorphs detect: [ :e | e model == ws ]. wsTextMorph := wsWindow findDeeplyA: TextMorph. text := wsTextMorph text. attr := TextDoIt evalString: text. text addAttribute: attr. ws := Workspace openContents: '1 + 1'. wsWindow := World submorphs detect: [ :e | e model == ws ]. wsTextMorph := wsWindow findDeeplyA: TextMorph. text := wsTextMorph text. attr := PluggableTextAttribute evalBlock: [ :e | e contents: '' ]. text addAttribute: attr. ws := Workspace openContents: '1 + 1'. wsWindow := World submorphs detect: [ :e | e model == ws ]. wsTextMorph := wsWindow findDeeplyA: TextMorph. text := wsTextMorph text. attr := TextPrintIt evalString: text. text addAttribute: attr. ws := Workspace openContents: '1 + 1'. wsWindow := World submorphs detect: [ :e | e model == ws ]. wsTextMorph := wsWindow findDeeplyA: TextMorph. text := wsTextMorph text. attr := TextURL new url: 'http://www.google.com';. text addAttribute: attr. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TextAttribute-TextAction-and-TextDoIt-or-TextURL-not-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2013

builds

by Max Leske

Iâve temporarily disabled the Fuel builds. Martin and I discovered VM crashes related to (maybe) garbage collection during our test runs. So right now a lot of builds are crashing. Weâll keep investigating so as to reenable the builds. Max

Nov. 5, 2013

No decompile string at all, bad idea?

by Mariano Martinez Peck

Hi. From what I understand you removed the old Compiler but yet Opal does not support compiling. Also, #sourceCode was changed etc... That means that there is no way to see the decompiled string of a method? Which means I cannot deploy and image without sources and then browse/debug/inspect/write pharoDebug.log etc because we don't have even the decompile string??? Serializing compiled methods is not fun either since we cannot decompile it after... So I wonder, was this a good idea? -- Mariano http://marianopeck.wordpress.com

Nov. 5, 2013

Re: [Pharo-dev] Feature request poll

by Sean P. DeNigris

Goubier Thierry wrote > for me, Pharo will stay Pharo Smalltalk That's valid, and just what I was speaking to. For us Smalltalkers, the tiny sliver of people who understand the subtleties, Pharo (in its current form, who knows in a year!) is quite reasonably described as Smalltalk - an evolution of Smalltalk-80. What the "inspired" part is about is the 99.99999999999% of the world who we're marketing to who think "Smalltalk = Smalltalk-80 = dead over-30-year-old language", which does not acknowledge Pharo's evolution and vision. It seems to me to be mostly a question of marketing and practicality. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Feature-request-poll-tp4718993p4719426.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2013

Bug? AdditionalMethodState suddenly stores Associations

by Max Leske

I discovered that AdditionalMethodState now (sometimes) stores Associations, not only Pragmas and Messages. That seems to work fine so fare but leads to an exception if #analogousCodeTo: is sent to a state which stores an Association. Can someone please confirm that this is a bug? Cheers, Max

Nov. 5, 2013

Re: [Pharo-dev] Feature request poll

by GOUBIER Thierry

I find this debate interesting... but a bit strange For me, Smalltalk-80 is what is inside the 80's book, and no implementation of Smalltalk was really Smalltalk-80 but something else (some principles plus a huge amount of code)... Pharo is no more different from Smalltalk-80 than all the others were, and, compared to Self, Pharo looks like a very tame variant :) So for me, Pharo will stay Pharo Smalltalk: a member of a large family which I had the pleasure to work in and use for a very long time, and in many different shapes but still respecting the same core principles. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Sean P. DeNigris [sean(a)clipperadams.com] Date d'envoi : mardi 5 novembre 2013 17:53 Ã : pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] Feature request poll Tudor Girba-2 wrote > Pharo is Pharo. And we should promote it like that. It is inherently confusing because originally "Smalltalk" meant "a language/environment that's continually reinvented every 4 years based on the knowledge gained by the last iteration". Then, Smalltalk-80 was frozen and released, and "Smalltalk" was repurposed in the wider world as a shorthand for Smalltalk-80. So, one would be correct in saying that Pharo is Smalltalk in the original meaning, as the next iteration after 80 (although it missed the 4 year target by a bit ha ha). But, since the nearly universal understanding of "Smalltalk" is Smalltalk-80, the "more true" and practical choice is to say that Pharo is Smalltalk-inspired (i.e. inspired by Smalltalk-80, but clearly not Smalltalk-80). HTH. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Feature-request-poll-tp4718993p4719415.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2013

Re: [Pharo-dev] Feature request poll

by Sean P. DeNigris

Tudor Girba-2 wrote > Pharo is Pharo. And we should promote it like that. It is inherently confusing because originally "Smalltalk" meant "a language/environment that's continually reinvented every 4 years based on the knowledge gained by the last iteration". Then, Smalltalk-80 was frozen and released, and "Smalltalk" was repurposed in the wider world as a shorthand for Smalltalk-80. So, one would be correct in saying that Pharo is Smalltalk in the original meaning, as the next iteration after 80 (although it missed the 4 year target by a bit ha ha). But, since the nearly universal understanding of "Smalltalk" is Smalltalk-80, the "more true" and practical choice is to say that Pharo is Smalltalk-inspired (i.e. inspired by Smalltalk-80, but clearly not Smalltalk-80). HTH. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Feature-request-poll-tp4718993p4719415.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2013

Re: [Pharo-dev] Pb team in Smalltalk hub?

by Alexandre Bergel

Ok, thanks guy! Alexandre On Nov 5, 2013, at 11:21 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > REVEAL team is experiencing this too. > > On 05 Nov 2013, at 15:13, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi! >> >> Apparently I cannot add any new team member in the team of ObjectProfile. >> Am I the only one to experience this? When I click on add, the member is not added. I've tried refreshing... >> >> Cheers, >> Alexandre >> <Screen Shot 2013-11-05 at 11.11.21 AM.png> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 5, 2013

Re: [Pharo-dev] Pb team in Smalltalk hub?

by Yuriy Tymchuk

REVEAL team is experiencing this too. On 05 Nov 2013, at 15:13, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Apparently I cannot add any new team member in the team of ObjectProfile. > Am I the only one to experience this? When I click on add, the member is not added. I've tried refreshing... > > Cheers, > Alexandre > <Screen Shot 2013-11-05 at 11.11.21 AM.png> > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Nov. 5, 2013

Re: [Pharo-dev] Pb team in Smalltalk hub?

by Camillo Bruni

nope, that's a know bug which will be take care of. as for now, you can only add new contributors to repositories. On 2013-11-05, at 15:13, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Apparently I cannot add any new team member in the team of ObjectProfile. > Am I the only one to experience this? When I click on add, the member is not added. I've tried refreshing... > > Cheers, > Alexandre > <Screen Shot 2013-11-05 at 11.11.21 AM.png> > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Nov. 5, 2013