April 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] questionable questionable code critic

by ClÃ©ment Bera

Code critics relies on simple rules, such as the use of the selector #isKindOf: . It does not detect the second case because the rule is simple, though both are questionable. Best, 2015-04-24 18:24 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Why does CodeCritic (QualityAssistant) considers this questionable > > ~~~~~~~~~~~~~~~~ > canBeTargetFor: aController > ^ aController isKindOf: DMNodeController > ~~~~~~~~~~~~~~~~ > > and yet this seems fine to him > > ~~~~~~~~~~~~~~~~ > canBeTargetFor: aController > ^ aController class = DMNodeController > ~~~~~~~~~~~~~~~~ > > shouldn't it be the same? > > Peter >

April 24, 2015

Package for building class diagrams

by Laura Risani

Hi all, Is there any package to build class diagrams? I've seen one somewhere but can't remember where. Any other tool / diagram type you find useful as visual support for the description of a system? Best, Laura

April 24, 2015

questionable questionable code critic

by Peter UhnÃ¡k

Why does CodeCritic (QualityAssistant) considers this questionable ~~~~~~~~~~~~~~~~ canBeTargetFor: aController ^ aController isKindOf: DMNodeController ~~~~~~~~~~~~~~~~ and yet this seems fine to him ~~~~~~~~~~~~~~~~ canBeTargetFor: aController ^ aController class = DMNodeController ~~~~~~~~~~~~~~~~ shouldn't it be the same? Peter

April 24, 2015

Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

by Rafael Luque

Hi Uko I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:" This is the stack trace for your information: =========================================== NBFFICallout>>loaderForArgNamed: NBFFICallout>>loaderForArgNamed:indirectIndex: NBFFICallout>>argName:indirectIndex:type:ptrArity: NBFnSpecParser>>parseArgument NBFnSpecParser>>parseArguments NBFnSpecParser>>parseAnonFunction: NBFFICallout>>anonSpec: [ :t3 | t3 useEmitCall; callType: conv; sender: context; parseOptions: options; anonSpec: t1; generate: t2 ] in NBFFICalloutAPI>>function:emit: [ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: BlockClosure>>on:do: NBRecursionDetect class>>in:during: NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode: NBFFICalloutAPI>>function:emit: NativeBoostMac32(NativeBoost)>>loadModule: CairoLibraryLoader class>>loadCairoLibrary CairoLibraryLoader class>>getLibraryHandle AthensCairoSurface class>>nbLibraryNameOrHandle AthensCairoSurface class(Object)>>nbCall: AthensCairoSurface class>>primImage:width:height: AthensCairoSurface class>>extent:format: AthensCairoSurface class>>extent: TRCanvas>>initialize TRCanvas class(Behavior)>>new RTView>>initialize RTView class(Behavior)>>new R3View>>initialize R3View class(Behavior)>>new Roassal3DModel>>initialize Roassal3DModel class(Behavior)>>new Roassal3DModel class(ComposableModel class)>>owner: CityBrowser(ComposableModel)>>instantiate: CityBrowser>>initializeWidgets CityBrowser(ComposableModel)>>initialize CityBrowser class(Behavior)>>new CityBrowser class(ComposableModel class)>>owner: VidiBrowser(ComposableModel)>>instantiate: VidiBrowser>>initializeWidgets VidiBrowser(ComposableModel)>>initialize VidiBrowser>>initialize VidiBrowser class(Behavior)>>new ReModel>>vidi VidiSession>>openVidi [ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction [ self value. Processor terminateActive ] in BlockClosure>>newProcess =========================================== Thank you. 2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi Rafael, > > now ViDI should work. I haven't been working on it for a while, but feel > free to report more issues, as I'll get back to it soon. > > Uko > > > > On 24 Apr 2015, at 09:57, Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > > Thank you! I'm looking forward to hearing from you about the new version. > > 2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> Ok, I found the problem. Some Spec api changed. I stable version will >> work at least on Mac quite soon. :) >> >> Uko >> >> >> >> On 23 Apr 2015, at 17:46, Rafael Luque <rafael.luque.leiva(a)gmail.com> >> wrote: >> >> I'd like to use it in a Linux box, but as you told me Linux is not yet >> supported, I'm using a Mac OS X Yosemite (version 10.10.2). >> >> Thanks >> >> 2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >>> Hi Rafael, >>> >>> I will take a look. Which operating system are you using? >>> >>> Uko >>> >>> On 23 Apr 2015, at 17:30, Rafael Luque <rafael.luque.leiva(a)gmail.com> >>> wrote: >>> >>> Hi, >>> >>> I installed ViDI on Pharo 4 following the project instructions detailed >>> in its GitHub page: >>> >>> Gofer new >>> smalltalkhubUser: 'YuriyTymchuk' >>> project: 'Configuration'; >>> configurationOf: 'Vidi'; >>> load. >>> #ConfigurationOfVidi asClass loadStable >>> >>> When I launch a review session over any package I always get the >>> following error: >>> >>> "Could not find accesor for variable named "aModuleName" in >>> NativeBoost>>#loadModule:" >>> >>> I'm very interested in this kind of quality assurance tools, so any help >>> will be very welcomed. >>> >>> Thank you. >>> >>> >>> >> >> > >

April 24, 2015

Who is maintaining Marina?

by Yuriy Tymchuk

HI, so far Iâve found 2+ issues: 1) 3 tests are failing because "MRRoot class>>#defaultâ returns nil. 2) "MRRoot>>#initializeâ references ânameâ variable which is not defined (the question if it should be defined, or itâs a refactoring leftover) Also can I configure CI to build Marina on Pharo 4.0?

April 24, 2015

Re: [Pharo-users] [Moose-dev] What's new on Pillar ?

by Alexandre Bergel

This is excellent !! I am really pleased to see effort to improve Pillar. Keep going! Alexandre > Le 24 avr. 2015 Ã 07:26, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©crit : > > Hi everyone ! > > I'm currently working on Pillar ! > It's been a little while now so I wanted to share what's new. > > --> First of all, with Stephane we created a new project, Cocoon, > based on the configuration system of Pillar. And now Pillar uses > Cocoon for his configurations. > http://smalltalkhub.com/#!/~PharoExtras/Cocoon > > --> Pillar unit tests weren't working on Windows before > > --> With Damien we also added two new abstractions: > --> The transformers: They take the Pillar tree and modify it. For > exemple we have a transformer which evaluates the scripts with a > "eval=true" parameter. > --> The annotations: They let the writer specify many different > things in their document using just 1 syntax (see below for an > example) > > --> We now have our first annotation tag: the inclusion tag ! > If you add this: > ${inputFile:test.pillar}$ or ${inputFile:folder/test.pillar}$ > into your Pillar file, that will include the content of test.pillar. > I recommend for now to use it at the root of the pillar file and not > inside a paragraph. That still needs some improvement. > > > --> We now have a transformer which adds an anchor after each title. > The anchor will have the text of the title. > This still needs some improvement, it's really simple for now. For > exemple we need to consider the case where we have 2 titles with the > same text (like 'introduction'). > > --> Now you can add 'lineNumber=true' as parameter for a Script. This > will add a numerotation at your script, usefull if we want to explain > a long code. > > --> I did some refactorisation on the parameters used by pillar to > clean the code. > > --> I did some refactorisation of the template system, the old one was > really ugly and changed the baseDirectory. Now template are managed by > a stream and not a file. > > --> I improved a little the configuration > --> Now if you want to change the baseDirectory you can pass a > FileReference, a relative path or an absolute path. > --> Now we look for the inputFiles from the baseDirectory and not > the working directory like before. You can also pass a FileReference, > a relative path or an absolute path. > > --> I added some tests to Pillar. > > --> I added some doc to EnterprisePharo > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > --> To help the users I improved the error reports. Before we had > really few errors specific to Pillar. > For this one you can help me ! If you found a weird error or something > really not easy to deal with, send me your problem ! > > > -- > Cheers > Cyril Ferlicot > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

April 24, 2015

Re: [Pharo-users] Test to fix first

by stepharo

I will have a look :) Thanks for this nice addons Le 24/4/15 17:02, Laura Risani a Ã©crit : > Hi all, > Made a little extension of method TestSuite>>run in order to print to > the Transcript a suggested test to fix first among the failing ones. > Logic is based on comment in "Modeling Examples to Test and Understand > Software" ( http://stephane.ducasse.free.fr/Supervised.html ). > Run test TestResultMsgsTest for example usage. > > To get the package > Gofer new smalltalkhubUser: 'squidik' project: 'TestToFixFirst'; > package: 'TestToFixFirst'; load. > > Comments? > > Best, > Laura

April 24, 2015

Test to fix first

by Laura Risani

Hi all, Made a little extension of method TestSuite>>run in order to print to the Transcript a suggested test to fix first among the failing ones. Logic is based on comment in "Modeling Examples to Test and Understand Software" ( http://stephane.ducasse.free.fr/Supervised.html ). Run test TestResultMsgsTest for example usage. To get the package Gofer new smalltalkhubUser: 'squidik' project: 'TestToFixFirst'; package: ' TestToFixFirst'; load. Comments? Best, Laura

April 24, 2015

Re: [Pharo-users] [Pharo-dev] QualityAssistant v0.4

by stepharo

The problem with Pharo-Dev in olden days wasn't that no one used the image, but that there was no good process for pushing required updates to "external" packages, so it was more convenient to just develop in the Core image, and leave the other packages for their maintainers to update at the end of a cycle. I don't think the best answer is to pull more and more packages into the Pharo "Core" repository and effectively do double versioning, as seems to be the trend lately... It is not really the case, because the external projects are autonomous. Why not require write access to repositories of external projects that are included in a Pharo-Dev image? Then you can have the Pharo team responsible for a (currently) #Pharo5 symbolic version in the Configuration. It could be the trick. But people will have to merge our changes. Then, when merging slices, push updates to external repos as appropriate (updating #Pharo5 version in Conf), and build new Dev image from a list of such approved Configurations. Lets the external developer do improvements against a static version, and merge with latest non-release when appropriate without leaving the comfort of a single repository. So we have when we integrate from a project a given version and when we push to the project a symbolic version but it can lead to some mess, no? Cheers, Henry

April 24, 2015

Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

by Yuriy Tymchuk

Hi Rafael, now ViDI should work. I havenât been working on it for a while, but feel free to report more issues, as Iâll get back to it soon. Uko > On 24 Apr 2015, at 09:57, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > > Thank you! I'm looking forward to hearing from you about the new version. > > 2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :) > > Uko > > > >> On 23 Apr 2015, at 17:46, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >> >> I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2). >> >> Thanks >> >> 2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi Rafael, >> >> I will take a look. Which operating system are you using? >> >> Uko >> >>> On 23 Apr 2015, at 17:30, Rafael Luque <rafael.luque.leiva(a)gmail.com <mailto:rafael.luque.leiva@gmail.com>> wrote: >>> >>> Hi, >>> >>> I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page: >>> >>> Gofer new >>> smalltalkhubUser: 'YuriyTymchuk' >>> project: 'Configuration'; >>> configurationOf: 'Vidi'; >>> load. >>> #ConfigurationOfVidi asClass loadStable >>> >>> When I launch a review session over any package I always get the following error: >>> >>> "Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:" >>> >>> I'm very interested in this kind of quality assurance tools, so any help will be very welcomed. >>> >>> Thank you. >> >> > >

April 24, 2015