Moose-dev June 2013

moose-dev@list.inf.unibe.ch

36 participants
163 discussions

Issue 910 in moose-technology: [VerveineJ] Some methods have 'private' modifier in source code but not in model

by moose-technology＠googlecode.com

Status: New Owner: anquetil...(a)gmail.com CC: damien.c...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 910 by damien.c...(a)gmail.com: [VerveineJ] Some methods have 'private' modifier in source code but not in model http://code.google.com/p/moose-technology/issues/detail?id=910 1- Take ant-1.8.2.mse 2- Search methods with each isProtected not and: [each isPublic not and: [each isPrivate not and: [each isStub not]]] 3- Some methods are private here

12 years

CI slaves not doing well

by Yuriy Tymchuk

Hi everyone. As far as I know cloud stack should be online. But when I check the status of the slave it says "starting". Does anybody know what can be done to help it get started at last :) Cheers. Uko -- View this message in context: http://moose-dev.97923.n3.nabble.com/CI-slaves-not-doing-well-tp4027831.html Sent from the moose-dev mailing list archive at Nabble.com.

12 years

Re: PetitJava

by Yuriy Tymchuk

Hi, so there are a few parts. 1) Visitors I suggest that abstract visitor should guide you how to visit this node. For example just do 'visitNodes: aPrimaryWithSelectorsNode codeList' so when someone will overwrite it he will know that he should pay attention to codeList data. Also comment will be lovely to have and this is a tough part as almost no classes in PJ have comments. 2). AST nodes The reason why we create an AST is that PetitParser's native parse result are arrays, and we want more structured data. For instance this.getCommand().getContext().getUser().getActiveProfile() is a method call. It has a selector "getActiveProfile" it has no parameters and it's invoked on this.getCommand().getContext().getUser(). I may be wrong about this, but on the other hand current AST is constructed like this. So maybe if you need some other kind of AST you should create it and make one more subclass of parser that will construct that. Also I'll sent a copy to moose-dev because maybe people there will have better vision. Cheers Uko On 29 трав. 2013, at 19:33, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > Hi, > > I'm not sure what exactly you want out of the visitor pattern. It seems like the current accept.. methods (that aren't either 'TO DO' or #subclassResponsibility, that is) just ask you to #visitNode: or #visitNodes: for the various instance variables in the AST classes. Am I missing something here? I must say that I haven't used the visitor pattern with parsed results before, and am not sure what you want and/or need out of this. > > As for PrimaryWithSelectorsNode, after looking back at it, I can see that I have obscured what the 'primary' was from when it was parsed out. however, in looking at what could constitute a primary (versus the selectors part), I find myself confused with what answering a primary would be. I could by most anything - for a single item (boolean, literal, variable) to something very complex (such as a string of identifiers hanging off of an identifier with or without message sends on the end). Instead I attempted to simplify it into an array of the parts so that I could iterate over them as needed. sometimes I would like to find the first in the list, sometimes the last, and sometimes I'd like to search the whole list for a specific call (if present) in the middle. > > so, take the code: > this.getCommand().getContext().getUser().getActiveProfile() > The current PJPrimaryWithSelectorsNode will have these in the codeList array: > this > getCommand() > getContext() > getUser() > getActiveProfile() > I did change the behaviour of the parsed #primaryWithselectors - previously it would have bundled this and getCommand() together into one unit identified as 'primary' and all of the other methods as an array of 'selectors'. > > similarly, this code: > new SearchUrl(Search.class).set(parm1, p1).set(parm2, params.get2(p2)).set(parm3, p3).getHref() > will return the codeList array: > new SearchUrl(Search.class) > set(parm1, p1) > set(parm2, params.get2(p2)) > set(parm3, p3).getHref() > Previously, it would identify the first item of the array as the primary, and the rest as the selectors. Which does make a lot of sense to me. > > finally, this code: > this.context.getUser().getActiveProfile().getProfileProperties() > will return in the code array: > this > context > getUser() > getActiveProfile() > getProfileProperties() > Previously, primary would have consisted of the array > this > context > getUser() > while selectors would have been the array of > getActiveProfile() > getProfileProperties() > > I should note that I'm not a Java coder myself and am not clear on how Java coders identify the parts of their code. I have tried to mostly follow what was previously there in the parser as it was clearer than what I'd likely come up with. However, I can't really see myself why the 'primary' was primary in the previous examples - is it clear and I should revert back, and have the visitor visit the restored primary and selectors? or should I have the visitor visit each part of the stacked structure that the Java coder has presented us? Which way would you prefer it - I'll modify it to fit your desires. > > Thanks, > Chris > > On Tue, May 28, 2013 at 10:55 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > HI, > > I've checked the changes. `acceptPrimaryWithSelectorsNode:` has only a flag so I didn't get how should I accept it and started to check out what the idea is. I still don't get it. It has some code list that is usually an array. Why do we need that node? What code entity does it represent? It looks like instead of building an AST from parsed arrays we are wrapping them in other classes. > > Yuriy > > On 28 трав. 2013, at 21:30, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > >> Hi. >> >> I've added the missing method (as well as related missing #acceptVisitor: methods on most of the other nodes that I've added) in the latest change. >> >> If you have any other questions or requests, please let me know. >> >> Thanks, >> Chris Cunningham >> >> >> On Tue, May 28, 2013 at 7:45 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Thank you >> >> Надіслано з iPhone >> >> 28 трав. 2013 о 17:18 Chris <cunningham.cb(a)gmail.com> написав(ла): >> >> > Thanks for letting me know. I'll fix that today. >> > >> > Sent from my iPhone >> > >> > On May 28, 2013, at 1:59 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> > >> >> Hi, >> >> >> >> your changes to PetitJava break my builds on fast. The problem is that `acceptVisitor:` of PJPrimaryWithSelectorsNode is not implementing `acceptVisitor: aVisitor` method, and so PJASTNodeVisitor is not implementing some visiting method that can give a hint on what should I do in my visitor subclass. >> >> >> >> Thank you for your contributions. >> >> Uko >> > >

12 years

OpenGL: NBMacGlAPI missing?

by Alexandre Bergel

Hi! I have installed NBOpenGL from http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL I have loaded Version 2.0 using the configuration The method NBMacGlAPI>>glApiCall: fnSpec index: fnIndex attributes: attributes context: contextToRetry refers to the class NBCallFailureHandler, which is not existing Apparently NBSTIvarLoader is also missing... I guess ConfigurationOfNBOpenGL is not loading everything... It would be nice to fix this. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years

Re: [Pharo-dev] SourceCity works

by Igor Stasenko

On 8 June 2013 10:29, Stephan Eggermont <stephan(a)stack.nl> wrote: > Thank you Igor, > > This allowed me to successfully load, debug & run SourceCity on an 10.6.8 Mac. > i just updated the config, to fix an issue when using in 3.0 image, which miss ShortPointArray. (but it is used only by my demo) > Steps taken: >> just tried in latest 2.0 image. >> >> Pharo2.0 >> Latest update: #20606 >> >> Gofer new >> smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; >> package: 'ConfigurationOfNBOpenGL'; >> load. >> >> (ConfigurationOfNBOpenGL project version: '2.0') load >> >> GLTTRenderingDemo new openInWorld > > Load the individual SourceCity packages from smalltalkhub: > > SourceCity-Core > SourceCity-Importer > SourceCity-Layout > SourceCity-Tools > > remove > display bindRenderBuffers > from > SourceCityGLVizualisationBuilder>fillRenderingList:pickingMode: > SourceCityGLVizualisationRenderer>render > > see it work: > SourceCity exampleRpackage > > Next step: fix code & configuration > > Stephan > > > > On 7 jun 2013, at 23:34, Igor Stasenko wrote: > >> On 7 June 2013 21:07, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi! >>> >>> I have installed NBOpenGL from http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL >>> I have loaded Version 2.0 using the configuration >>> >>> The method NBMacGlAPI>>glApiCall: fnSpec index: fnIndex attributes: attributes context: contextToRetry refers to the class NBCallFailureHandler, which is not existing >>> >>> Apparently NBSTIvarLoader is also missing... >>> I guess ConfigurationOfNBOpenGL is not loading everything... >>> It would be nice to fix this. >> >> just tried in latest 2.0 image. >> >> Pharo2.0 >> Latest update: #20606 >> >> Gofer new >> smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; >> package: 'ConfigurationOfNBOpenGL'; >> load. >> >> (ConfigurationOfNBOpenGL project version: '2.0') load >> >> GLTTRenderingDemo new openInWorld >> >> everything loads and works. >> (it takes 5 minutes to load though... ) >> >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- Best regards, Igor Stasenko.

12 years

holidays :)

by Tudor Girba

Hi, I am on holidays for the next two weeks, and as a consequence, I will be less responsive. I am looking forward to a ton of new things to catch up with when I come back :). Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

12 years

Issue 946 in moose-technology: MorphTreeMorph truncates labels

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 946 by tu...(a)tudorgirba.com: MorphTreeMorph truncates labels http://code.google.com/p/moose-technology/issues/detail?id=946 Here is how to reproduce: 1. Download a Moose 4.8 image 2. Install the moose fonts and theme: MooseImageSetupCommandLineHandler new installFonts; installGLMWhitespaceTheme. 3. Open a GTInspector Smalltalk explore You will see that some letters appear on the next row (like sessio + n). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

12 years

Re: SourceCity works

by Stephan Eggermont

On 8 jun 2013, at 10:30, pharo-dev-request(a)lists.pharo.org wrote: > display bindRenderBuffers And they need to go in fillRenderingList: anOpenGLList drawDependencies: aBuilding too. I was not successful in committing to smalltalkhub (500) Stephan

12 years

Sunbursts are coming in Roassal

by Alexandre Bergel

Hi! Milton, an excellent engineer from Object Profile, just produced the following: Sunburst is a visualization particular efficient at visualizing hierarchical domain. It naturally uses Athens. We will show more at esug :-) Milton & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years

Question about CollectionExtensions

by Sebastian Tleye

Hello, I have installed the package CollectionExtension to my Pharo3.0 image (i have the latest image) but there is a test that it stopped working. There is a bug in Collection>>includesAllOf: if i do "#(#1 #2) includesAllOf: #(#1 #1)" it returns false. Do i have to install something else? I know that in the latest image of moose this bug was fix. Thanks!

12 years

← Newer
1
...
10
11
12
13
14
15
16
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2013