March 2014 - Pharo-users - lists.pharo.org

Am not sure if that is a good idea

by Friedrich Dominicus

anyway. Has anyone considered adding filtering to the Debugger (in my case the Glamorous Debugger) in a way that not all instance variables values are shown in the value pane? Well a kind of watch as in other debuggers. You just can "ask" to watch e.g field firstName but not lastName or something like that. Even if I try to keep the information down some classes still do have a lot of elements (think of articles, which usually have at least some kind of id, a description, a price tag, but also some other information (be it internal or extenal for the programm)

March 11, 2014

Re: [Pharo-users] CodeCity

by Sven Van Caekenberghe

Wow ! On 11 Mar 2014, at 14:29, Richard Wettel <wettel(a)gmail.com> wrote: > Dear all > > After the short preview at the last Moose Dojo, I am happy to let you know that the first version of the brand new CodeCity is out. > > CodeCity is a 3D visualization engineased on a city metaphor, which enables us to depict software systems as cities. If you want to know more about this approach, have a look here: > http://www.inf.usi.ch/phd/wettel/codecity.html > > I have now implemented the basic functionality of CodeCity in Pharo and integrated it with Moose. Here is a code city of ArgoUML in the new CodeCity: > > <CodeCity-Argo.png> > > To install CodeCity, you need to run this code in a Moose image (setting Moose as a prerequisite is on my TODO list): > > Gofer new > smalltalkhubUser: 'RichardWettel' project: 'CodeCity'; > configuration; > load. > (Smalltalk at: #ConfigurationOfCodeCity) loadDevelopment > > > You can also get the latest successful build from: > http://ci.inria.fr/moose/job/codecity/lastSuccessfulBuild/artifact/codecity… > > The new CodeCity does not provide a configuration UI, but it relies on scripting. A script to obtain a city visualization of a Moose model is shown here: > > <CodeCity-ArgoScript.png> > > > A good way to get familiar with the scripting API of CodeCity are the examples. You can open CCBuilder in the new workspace (Playground) and you can browse the examples (the "e.g." tab). > > <PharoScreenshot.5.png> > > While CodeCity was initially aimed at software systems only, there is nothing that stops us to use it at visualizing any kind of data! One example was the visualization of the data taken from a database (population, city, countries, continents) presented at the Moose Dojo. I'm sure Doru will be pleased to show you more of that. > > In conclusion, I hope you'll enjoy playing/working with CodeCity as much as I have been enjoying re-implementing it in the last few months. Playing with CodeCity integrated in the Moose workflows is pure fun. But don' take my word for it, just give it a try! > > Cheers > Ricky

March 11, 2014

Re: [Pharo-users] CodeCity

by Tudor Girba

Beautiful! (I have been spoiled by being exposed to this for quite some time now :)) Thanks, Ricky. This is a valuable addition. Cheers, Doru On Tue, Mar 11, 2014 at 2:29 PM, Richard Wettel <wettel(a)gmail.com> wrote: > Dear all > > After the short preview at the last Moose Dojo, I am happy to let you know > that the first version of the brand new CodeCity is out. > > CodeCity is a 3D visualization engineased on a city metaphor, which > enables us to depict software systems as cities. If you want to know more > about this approach, have a look here: > http://www.inf.usi.ch/phd/wettel/codecity.html > > I have now implemented the basic functionality of CodeCity in Pharo and > integrated it with Moose. Here is a code city of ArgoUML in the new > CodeCity: > > [image: Inline image 1] > > To install CodeCity, you need to run this code in a Moose image (setting > Moose as a prerequisite is on my TODO list): > > Gofer new smalltalkhubUser: 'RichardWettel' project: 'CodeCity'; > configuration; load. (Smalltalk at: #ConfigurationOfCodeCity) > loadDevelopment > > You can also get the latest successful build from: > > http://ci.inria.fr/moose/job/codecity/lastSuccessfulBuild/artifact/codecity… > > The new CodeCity does not provide a configuration UI, but it relies on > scripting. A script to obtain a city visualization of a Moose model is > shown here: > > [image: Inline image 4] > > > A good way to get familiar with the scripting API of CodeCity are the > examples. You can open CCBuilder in the new workspace (Playground) and you > can browse the examples (the "e.g." tab). > > [image: Inline image 2] > > While CodeCity was initially aimed at software systems only, there is > nothing that stops us to use it at visualizing any kind of data! One > example was the visualization of the data taken from a database > (population, city, countries, continents) presented at the Moose Dojo. I'm > sure Doru will be pleased to show you more of that. > > In conclusion, I hope you'll enjoy playing/working with CodeCity as much > as I have been enjoying re-implementing it in the last few months. Playing > with CodeCity integrated in the Moose workflows is pure fun. But don' take > my word for it, just give it a try! > > Cheers > Ricky > -- www.tudorgirba.com "Every thing has its own flow"

March 11, 2014

CodeCity

by Richard Wettel

Dear all After the short preview at the last Moose Dojo, I am happy to let you know that the first version of the brand new CodeCity is out. CodeCity is a 3D visualization engineased on a city metaphor, which enables us to depict software systems as cities. If you want to know more about this approach, have a look here: http://www.inf.usi.ch/phd/wettel/codecity.html I have now implemented the basic functionality of CodeCity in Pharo and integrated it with Moose. Here is a code city of ArgoUML in the new CodeCity: [image: Inline image 1] To install CodeCity, you need to run this code in a Moose image (setting Moose as a prerequisite is on my TODO list): Gofer new smalltalkhubUser: 'RichardWettel' project: 'CodeCity'; configuration; load. (Smalltalk at: #ConfigurationOfCodeCity) loadDevelopment You can also get the latest successful build from: http://ci.inria.fr/moose/job/codecity/lastSuccessfulBuild/artifact/codecity… The new CodeCity does not provide a configuration UI, but it relies on scripting. A script to obtain a city visualization of a Moose model is shown here: [image: Inline image 4] A good way to get familiar with the scripting API of CodeCity are the examples. You can open CCBuilder in the new workspace (Playground) and you can browse the examples (the "e.g." tab). [image: Inline image 2] While CodeCity was initially aimed at software systems only, there is nothing that stops us to use it at visualizing any kind of data! One example was the visualization of the data taken from a database (population, city, countries, continents) presented at the Moose Dojo. I'm sure Doru will be pleased to show you more of that. In conclusion, I hope you'll enjoy playing/working with CodeCity as much as I have been enjoying re-implementing it in the last few months. Playing with CodeCity integrated in the Moose workflows is pure fun. But don' take my word for it, just give it a try! Cheers Ricky

March 11, 2014

Re: [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by Laurent Laffont

Thanks a lot Phil. I will try to have a look. Laurent Le samedi 8 mars 2014, 11:57:30 phil(a)highoctane.be a Ã©crit : > TWM works in 3.0 after some work on icons and updating menus. > > Gofer new > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > configuration; > load. > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') > load > > You can also use > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > #development) load > > but this will for sure change over time. > > There is the World management icon which is still there and it looks like > it can create worlds but switching between them just breaks havoc. > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be > multiworld friendly. > > Nothing done on tests nor themeing (which appears to be not that working > well in 3.0 either due to theming changes); > > At least the thing is back :-) [I missed it...] > > Phil

March 11, 2014

Re: [Pharo-users] [ANN] BabyMock 2

by Benjamin

It looks even cooler than before :) Ben On 11 Mar 2014, at 12:30, Attila Magyar <m.magyar3(a)gmail.com> wrote: > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > mock object library that supports test-driven development. > > This version has a new syntax which is incompatible with the old version. > Therefore it has a new repository > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > (BabyMock 1 is still available at its old location, but in the future I'd to > focus on the development of BabyMock2, so don't expect too many changes > regarding the old version). > > Changes in 2.0 > > - A new, extensible DSL (no more should/can) > - Improved error messages, history of messages, detailed information about > argument mismatches > - An improved, Spec based GUI > - Clicking on a mock opens an inspector on the expectations > - Clicking on a message opens an inspector on the message > - Object methods can be mocked by defaults > - Blocks can be executed after receiving a message by the mock. The block > has access to the arguments of the incoming message. > - Any argument matcher > - Cleanups and simplifications in the code > > I hope you don't mind the changes regarding the syntax. Personally I think > it has lot more pros than cons. > > More information > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > p.s. > It needs Pharo3.0. > > Attila > > > > -- > View this message in context: http://forum.world.st/ANN-BabyMock-2-tp4748530.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

March 11, 2014

Re: [Pharo-users] [ANN] BabyMock 2

by Guillaume Larcheveque

Cool!!! I use BabyMock a lot and I'm curious to see the new DSL. Thanks a lot for your work. 2014-03-11 12:30 GMT+01:00 Attila Magyar <m.magyar3(a)gmail.com>: > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > mock object library that supports test-driven development. > > This version has a new syntax which is incompatible with the old version. > Therefore it has a new repository > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > (BabyMock 1 is still available at its old location, but in the future I'd > to > focus on the development of BabyMock2, so don't expect too many changes > regarding the old version). > > Changes in 2.0 > > - A new, extensible DSL (no more should/can) > - Improved error messages, history of messages, detailed information about > argument mismatches > - An improved, Spec based GUI > - Clicking on a mock opens an inspector on the expectations > - Clicking on a message opens an inspector on the message > - Object methods can be mocked by defaults > - Blocks can be executed after receiving a message by the mock. The block > has access to the arguments of the incoming message. > - Any argument matcher > - Cleanups and simplifications in the code > > I hope you don't mind the changes regarding the syntax. Personally I think > it has lot more pros than cons. > > More information > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > p.s. > It needs Pharo3.0. > > Attila > > > > -- > View this message in context: > http://forum.world.st/ANN-BabyMock-2-tp4748530.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- *Guillaume Larcheveque*

March 11, 2014

[ANN] BabyMock 2

by Attila Magyar

I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual mock object library that supports test-driven development. This version has a new syntax which is incompatible with the old version. Therefore it has a new repository http://smalltalkhub.com/#!/~zeroflag/BabyMock2 (BabyMock 1 is still available at its old location, but in the future I'd to focus on the development of BabyMock2, so don't expect too many changes regarding the old version). Changes in 2.0 - A new, extensible DSL (no more should/can) - Improved error messages, history of messages, detailed information about argument mismatches - An improved, Spec based GUI - Clicking on a mock opens an inspector on the expectations - Clicking on a message opens an inspector on the message - Object methods can be mocked by defaults - Blocks can be executed after receiving a message by the mock. The block has access to the arguments of the incoming message. - Any argument matcher - Cleanups and simplifications in the code I hope you don't mind the changes regarding the syntax. Personally I think it has lot more pros than cons. More information http://smalltalkhub.com/#!/~zeroflag/BabyMock2 p.s. It needs Pharo3.0. Attila -- View this message in context: http://forum.world.st/ANN-BabyMock-2-tp4748530.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 11, 2014

String>>match issue

by vmusulainen

Hi! >From comment to #match: method match: text "Answer whether text matches the pattern in this string. Matching ignores upper/lower case differences. Check it now: 1. 'V' match: 'v' -> true "Ok, It's fine" 2. 'Ð¨' match: 'Ñ' -> false "Use non-English (Cyrillic) letters Ups-s" -regards Vladimir Musulainen -- View this message in context: http://forum.world.st/String-match-issue-tp4748497.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 11, 2014

Re: [Pharo-users] OS question

by Friedrich Dominicus

Pierce Ng <pierce(a)samadhiweb.com> writes: > I hope NativeBoost will work on FreeBSD eventually. All the world's not > just Linux, OSX and Windows. Well, yes that what I would think, but well at least not for Pharo I guess ;-) Regards Friedrich

March 10, 2014