- Moose-dev - INF Mailman

by Hani Abdeen

Hi, Using VerveineJ, the stub classes realted to unit tests (TestCase, TestSuit and Test classes) are not imported also their namesapce junit.framework These classes are imported using inFamix. junit.framework.TestCase class is particularly important in order to automatically detect unit test classes: TestCase subclassHierarchy. If this class is not available in the moose model then the only way to automatically detect unit test classes is by detecting the classes that their names are postfixed by 'Tests': mooseModel allClasses select: [:c| '*Tests' match: c name] such a way can provide us with wrong results! Cheers, Hani P.S.: use-case JFreechart project: http://sourceforge.net/projects/jfreechart/files/latest/download which includes about 380 test classes (classes inherit from TestCase) --

13 years, 6 months

3
6
0 0

Issue 765 in moose-technology: Meta Browser search list should offer the full name of classes

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.6 New issue 765 by tudor.gi...(a)gmail.com: Meta Browser search list should offer the full name of classes http://code.google.com/p/moose-technology/issues/detail?id=765 Currently, we use the name when searching for classes in the MetaBrowser, and when we get classes named the same but in different packages it gets confusing. We should use the fullName

13 years, 6 months

1
1
0 0

Issue 764 in moose-technology: The Glamorous Inspector should allow editing the values of variables

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 764 by tudor.gi...(a)gmail.com: The Glamorous Inspector should allow editing the values of variables http://code.google.com/p/moose-technology/issues/detail?id=764 In the regular inspector, you can just accept a new value in the preview pane and the instance variable gets updated. Glamorous Inspector should offer a similar support. Most likely, we will start with a dialog for entering a new value. That is until we get the ability to edit in place in the table.

13 years, 6 months

1
0
0 0

gt inspector

by Tudor Girba

Hi, Just out of curiosity: Does any of you use the GTInspector? For those that wonder what that is, here is a demo:http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk This is available in any recent Moose image mapped as Explorer (CMD+I). You can load it in a Pharo 1.3 image by:Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load.(Smalltalk at: #ConfigurationOfGlamoroust) loadDefault.(Smalltalk at: #GTInspector) registerToolsOn: Smalltalk tools. Cheers,Doru -- www.tudorgirba.com "Every thing has its own flow"

13 years, 6 months

2
1
0 0

gtinspector

by Tudor Girba

Hi, Just out of curiosity: Does any of you use the GTInspector? For those that wonder what that is, here is a demo: http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk This is available in any recent Moose image mapped as Explorer (CMD+I). You can load it in a Pharo 1.3 image by: Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load.(Smalltalk at: #ConfigurationOfGlamoroust) loadDefault.(Smalltalk at: #GTInspector) registerToolsOn: Smalltalk tools. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

13 years, 6 months

2
1
0 0

Re: Jenkins build is still unstable: moose-latest-dev #756

by Alexandre Bergel

Hi! I worked on the failing test. It is now green. In the process, I added comments and unit test for part there were not tested. Here are my changes: Moose-Tests-MonticelloImporter-AlexandreBergel.4 : renamed testBasic into something more meaningful (testImporting) Moose-MonticelloImporter-AlexandreBergel.26 : Replace reference to SmalltalkMethodVisitor by MonticelloMethodVisitor Moose-SmalltalkImporter-AlexandreBergel.124 : Rename SmalltalkMethodVisitor into AbstractSmalltalkMethodVisitor. Added two subclasses to it, SmalltalkMethodVisitor and MonticelloMethodVisitor. I did this since the lookup of name is different. Famix-Implementation-AlexandreBergel.98 : Added a new unit test, FAMIXNameResolverTest Cheers, Alexandre > On 19 Dec 2011, at 22:41, Alexandre Bergel wrote: > >> Tomorrow I work on it. >> >> Alexandre >> >> >> >> Le 19 déc. 2011 à 18:34, admin(a)moosetechnology.org a écrit : >> >>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/756/> >>> >>> > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 6 months

2
1
0 0

Re: Glamour-Merilin-Mondrian

by Júlio Martins

Correting the code >> >> | filterWizard view | >> browser := GLMTabulator withStatusbar. >> filterWizard := BMBugMapsFilterWizard new. "a child of WizardControl" >> browser >> row: [ :row | row column: #map span: 2.5; column: #metrics] span: 1.5; >> row: [ :row | row column: #code span: 2.5; column: #chart]. >> >> browser transmit >> to: #map; >> andShow: [ :b | self distributionMapIn: b]. >> >> filterWizard := BMBugMapsFilterWizard new. >> > filterWizard > glamourWizard >> initialExtent: 400@200; >> yourself. >> >> browser >> spawn: [:a| >> filterWizard >> atEndDo:[:wizardInformation| . >> self distributionMapIn: a with: (wizardInformation at: #textEntry). >> a update.]. >> ] entitled: 'Filter'. >> >> where self is an instance of GLMBrowserTemplate. >> >> >> On 19 December 2011 10:51, Tudor Girba <[hidden email]<http://user/SendEmail.jtp?type=node&node=4214005&i=0> >> > wrote: >> >>> Hi, >>> >>> If the first parameter is a browser, something is probably wrong (you >>> might be using the wrong api). Please send also the browser code. >>> >>> Cheers, >>> Doru >>> >>> 2011/12/19 Júlio Martins <[hidden email]<http://user/SendEmail.jtp?type=node&node=4214005&i=1> >>> >: >>> > Ok! >>> > >>> > distributionMapIn: a with: aNumber >>> > >>> > "in this point the method is executed" >>> > >>> > ^a mondrian >>> > painting: [ :view :model | self halt. >>> > view shape rectangle withoutBorder. >>> > view nodes: (model allModelNamespaces asSet sortedAs: [ :x :y | x >>> > numberOfClasses > y numberOfClasses ]) forEach: [ :each | >>> > view shape label. >>> > view node: each name. >>> > view node: each forIt: [ >>> > view interaction menu: #mooseMenu. >>> > view shape rectangle size: 12; >>> > if: [ :c | c numberOfMethods = 0 ] fillColor: Color green; >>> > if: [ :c | c numberOf Methods >= 1 and: [ c numberOfBugs < 3 ] ] >>> fillColor: >>> > Color orange; >>> > if: [ :c | c numberOfMethods >= 3 ] fillColor: Color red. >>> > view nodes: ((each classes select: [ :class | class numberOf >>> Methods >= >>> > aNumber]) sortedAs: #numberOfMethods). >>> > >>> > view gridLayout gapSize: 2 ]. >>> > view verticalLineLayout ]. >>> > view gridLayout ]. >>> > >>> > the first method parameter is a GLMTabulator, The block started by the >>> > method "halt" is not executed, I no wonder why! >>> >> -- View this message in context: http://forum.world.st/Re-Moose-dev-Glamour-Merilin-Mondrian-tp4214058p42140… Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

2
1
0 0

Glamour Presentations

by Júlio Martins

Might one of you give me a code example that show a way of how show different views of a same type of mondrian presentation, just changing a value? This value must be gotten from a window and the mondrian presentation must be in another window. For example a window with presentation have a menu that call the another window, or something so. . It is possible? Julio. * * -- View this message in context: http://forum.world.st/Glamour-Presentations-tp4215080p4215080.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

1
0
0 0

java (jboss) dynamic instrumentation?

by Tudor Girba

Hi, Can anyone recommend an dynamic instrumentation tool for Java? I am interested in a solution that would work also on the server side (in particular, inside a JBoss server). I found some links, but I do not know how good they are: http://java-source.net/open-source/profilers Cheers, Doru -- www.tudorgirba.com "Reasonable is what we are accustomed with."

13 years, 6 months

3
2
0 0

Re: Moose-dev Digest, Vol 64, Issue 56

by Sergio Castro

On 19/12/11 13:09, moose-dev-request(a)iam.unibe.ch wrote: > > ---------------------------------------------------------------------- > > > Message: 2 > Date: Mon, 19 Dec 2011 05:07:39 +0100 > From: Tudor Girba<tudor(a)tudorgirba.com> > Subject: [Moose-dev] java (jboss) dynamic instrumentation? > To: Moose-dev Moose Dev<moose-dev(a)iam.unibe.ch> > Message-ID:<56F679FD-8623-4A68-BD18-B7C3B3C3D340(a)tudorgirba.com> > Content-Type: text/plain; charset=us-ascii > > Hi, > > Can anyone recommend an dynamic instrumentation tool for Java? > > I am interested in a solution that would work also on the server side (in particular, inside a JBoss server). > > I found some links, but I do not know how good they are: > http://java-source.net/open-source/profilers > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > > As far as I know, Javassist is what you need. I have used it for byte code instrumentation and is relatively easy to learn and use, if I remember correctly JBoss provides support for it. Take a look to: http://www.jboss.org/javassist Sergio

13 years, 6 months

4
4
0 0

designing a log parser

by Tudor Girba

Hi, I am currently working on analyzing some log files using PetitParser, and I have some metaphysical questions about the design I use :). The log file contains all sorts of events, including method start, method end and others. Furthermore, the log can collect events coming from multiple clients. See below: 2011-12-12 00:00:00,000 TRACE MethodTraceLogInterceptor: Client 1: START method package.Class#method 2011-12-12 00:00:00,010 TRACE MethodTraceLogInterceptor: Client 1: START method package2.Class2#methodWithoutEnd 2011-12-12 00:00:00,020 DEBUG Something else 2011-12-12 00:00:00,030 TRACE MethodTraceLogInterceptor: Client 2: START method package2.Class2#method 2011-12-12 00:00:00,040 DEBUG Something else 2011-12-12 00:00:02,000 TRACE MethodTraceLogInterceptor: Client 1: END after 2000 ms method package.Class#method 2011-12-12 00:00:02,030 TRACE MethodTraceLogInterceptor: Client 2: END after 2000 ms method I would like to retrieve for each client a tree based on the nesting of method calls. The grammar is quite straightforward. But, the question is how to get the tree from the parser. My current solution is to hold a stack in the parser and push/pop to it when a method starts/ends (actually, I have a stack for each client). Something like this: methodStart super methodStart. ==> [:token | ... (self topForClient: (token at: 2)) addChild: newMethodLogEntry. self push: newMethodLogEntry forClient: (token at: 2) ] methodEnd super methodEnd. ==> [:token | ... self popForClient: (token at: 2) ] This works Ok, and in the end I get my tree in the stack instance variable of the parser. But what makes me uneasy is that the result of the parser is somewhat unclean, because both for methodStart and for methodEnd I will get the same object. However, the good thing about this is that I do not have to create an intermediary representation for the log and directly produce the tree (which can save memory when we talk about large log files). What do you think? Do you have a more elegant solution? Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

13 years, 6 months

2
1
0 0

Glamour-Merilin-Mondrian

by Júlio Martins

> > This is it > > | filterWizard view | > browser := GLMTabulator withStatusbar. > filterWizard := BMBugMapsFilterWizard new. > browser > row: [ :row | row column: #map span: 2.5; column: #metrics] span: 1.5; > row: [ :row | row column: #code span: 2.5; column: #chart]. > > browser transmit > to: #map; > andShow: [ :b | self distributionMapIn: b]. > > filterWizard := BMBugMapsFilterWizard new > glamourWizard > initialExtent: 400@200; > yourself. > > browser > spawn: [:a| > filterWizard > atEndDo:[:wizardInformation| . > self distributionMapIn: a with: (wizardInformation at: #textEntry). > a update.]. > ] entitled: 'Filter'. > > where self is an instance of GLMBrowserTemplate. > > > On 19 December 2011 10:51, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> If the first parameter is a browser, something is probably wrong (you >> might be using the wrong api). Please send also the browser code. >> >> Cheers, >> Doru >> >> 2011/12/19 Júlio Martins <jleandro.martins(a)gmail.com>: >> > Ok! >> > >> > distributionMapIn: a with: aNumber >> > >> > "in this point the method is executed" >> > >> > ^a mondrian >> > painting: [ :view :model | self halt. >> > view shape rectangle withoutBorder. >> > view nodes: (model allModelNamespaces asSet sortedAs: [ :x :y | x >> > numberOfClasses > y numberOfClasses ]) forEach: [ :each | >> > view shape label. >> > view node: each name. >> > view node: each forIt: [ >> > view interaction menu: #mooseMenu. >> > view shape rectangle size: 12; >> > if: [ :c | c numberOfMethods = 0 ] fillColor: Color green; >> > if: [ :c | c numberOf Methods >= 1 and: [ c numberOfBugs < 3 ] ] >> fillColor: >> > Color orange; >> > if: [ :c | c numberOfMethods >= 3 ] fillColor: Color red. >> > view nodes: ((each classes select: [ :class | class numberOf Methods >= >> > aNumber]) sortedAs: #numberOfMethods). >> > >> > view gridLayout gapSize: 2 ]. >> > view verticalLineLayout ]. >> > view gridLayout ]. >> > >> > the first method parameter is a GLMTabulator, The block started by the >> > method "halt" is not executed, I no wonder why! >> > >> > On 19 December 2011 10:15, Tudor Girba <[hidden email]> wrote: >> >> >> >> Hi, >> >> >> >> I am sorry, but I cannot understand what the issue is. Could you >> >> provide some runnable code? >> >> >> >> Cheers, >> >> Doru >> >> >> >> >> >> 2011/12/19 Júlio Martins <[hidden email]>: >> >> >> >> > Hi people! >> >> > >> >> > I was with problems figure out the question "how to update the >> >> > distribution >> >> > map from a secundary wizard? So searching for the solution i found a >> >> > another >> >> > problem: when a mondrian receive a message to GLMTabulator and send a >> >> > message to method "painting:[:a :b| ... ]" , the execution flow >> doesn't >> >> > enter on block, where is all commands to build my new distribution >> map >> >> > view. >> >> > The code is like this sample: >> >> > >> >> > >> >> > GLMTabulator new mondrian >> >> > painting:[:a :b| >> >> > .... >> >> > "here the flow doesn't enter, why?" >> >> > ] >> >> > >> >> > Before this block, the flow is normal and works, but have no >> commands to >> >> > execute >> >> > i need help of you. >> >> > >> >> > ________________________________ >> >> > View this message in context: Glamour-Merilin-Mondrian >> >> > Sent from the Moose mailing list archive at Nabble.com. >> >> > >> >> > _______________________________________________ >> >> > Moose-dev mailing list >> >> > [hidden email] >> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > >> >> >> >> >> >> >> >> -- >> >> www.tudorgirba.com >> >> >> >> "Every thing has its own flow" >> >> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> [hidden email] >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> > >> > >> > ________________________________ >> > View this message in context: Re: [Moose-dev] Re: >> Glamour-Merilin-Mondrian >> > >> > Sent from the Moose mailing list archive at Nabble.com. >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > -- View this message in context: http://forum.world.st/Glamour-Merilin-Mondrian-tp4214005p4214005.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

1
0
0 0

Re: Glamour-Merilin-Mondrian

by Júlio Martins

Ok! *distributionMapIn:* a *with:* aNumber "in this point the method is executed" ^a mondrian painting: [ :view :model |* self halt*. view shape rectangle withoutBorder. view nodes: (model allModelNamespaces asSet sortedAs: [ :x :y | x numberOfClasses > y numberOfClasses ]) forEach: [ :each | view shape label. view node: each name. view node: each forIt: [ view interaction menu: #mooseMenu. view shape rectangle size: 12; if: [ :c | c numberOfMethods = 0 ] fillColor: Color green; if: [ :c | c numberOf Methods >= 1 and: [ c numberOfBugs < 3 ] ] fillColor: Color orange; if: [ :c | c numberOfMethods >= 3 ] fillColor: Color red. view nodes: ((each classes select: [ :class | class numberOf Methods >= aNumber]) sortedAs: #numberOfMethods). view gridLayout gapSize: 2 ]. view verticalLineLayout ]. view gridLayout ]. the first method parameter is a GLMTabulator, The block started by the method "halt" is not executed, I no wonder why! On 19 December 2011 10:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am sorry, but I cannot understand what the issue is. Could you > provide some runnable code? > > Cheers, > Doru > > > 2011/12/19 Júlio Martins <jleandro.martins(a)gmail.com>: > > Hi people! > > > > I was with problems figure out the question "how to update the > distribution > > map from a secundary wizard? So searching for the solution i found a > another > > problem: when a mondrian receive a message to GLMTabulator and send a > > message to method "painting:[:a :b| ... ]" , the execution flow doesn't > > enter on block, where is all commands to build my new distribution map > view. > > The code is like this sample: > > > > > > GLMTabulator new mondrian > > painting:[:a :b| > > .... > > "here the flow doesn't enter, why?" > > ] > > > > Before this block, the flow is normal and works, but have no commands to > > execute > > i need help of you. > > > > ________________________________ > > View this message in context: Glamour-Merilin-Mondrian > > Sent from the Moose mailing list archive at Nabble.com. > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- View this message in context: http://forum.world.st/Re-Moose-dev-Re-Glamour-Merilin-Mondrian-tp4213899p42… Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

3
2
0 0

xpath queries

by Tudor Girba

Hi, Is there some solution for supporting XPath queries in Pharo? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

13 years, 6 months

3
4
0 0

Glamour-Merilin-Mondrian

by Júlio Martins

Hi people! I was with problems figure out the question "how to update the distribution map from a secundary wizard? So searching for the solution i found a another problem: when a mondrian receive a message to GLMTabulator and send a message to method "painting:[:a :b| ... ]" , the execution flow doesn't enter on block, where is all commands to build my new distribution map view. The code is like this sample: GLMTabulator new mondrian painting:[:a :b| .... "here the flow doesn't enter, why?" ] Before this block, the flow is normal and works, but have no commands to execute i need help of you. -- View this message in context: http://forum.world.st/Glamour-Merilin-Mondrian-tp4213842p4213842.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

2
1
0 0

Fwd: [vwnc] Introducing SimpleXPath

by Steffen Märcker

Hi, during my work on the XML-Mapping framework SimpleXO, I realized that the XML querying code could be useful standalone, too. I factored out a library named SimpleXPath and made it available in Cincom public repository under the MIT license. It is similar to the XPath location path subset (without predicates) but offers some distinct features: - paths are built as pure Smalltalk expressions - extended wildcard support - simple API Example: (RootStep // 'source' /@ 'id') "XPath: //source/@id" contextNode: anXmlNode; nodesDo: [:node | Transcript show: node stringValue; cr]. The above code prints the 'id' value of all 'source' elements in the XML document from which anXmlNode is taken. I am interested in your opinions. I'd be glad If you give it a try and discuss your thoughts here. Below I've attached the package comment explaining the API, just in case. ;) Regards and happy coding! Steffen Simple XPath is an XML query library based on a subset of the XPath 1.0 language. It provides a handy API to construct paths and a parser for abbreviated XPath location paths without predicates. See also: http://www.w3.org/TR/xpath/. I. NodeSets ----------------- The result of constructing a path or parsing an XPath location path is a NodeSet. If applied to an XML node, a NodeSet provides access to the nodes selected by this set. 1. Call #contextNode: to define the node a NodeSet is applied to. 2. Call #nodes to get a set of all matched nodes, #nodesDo: with a one argument block to iterate over all matched nodes and #selectNodes: with a one argument block to select some of the matched nodes. If you are working with tags that have prefixed names, ensure that you resolve the associated namespace before using a NodeSet. Call >>#resolveNamespaces: with a dictionary that maps all prefixes to their namespace. II. Path construction API: ------------------------------------ To construct a path programmatically, use the Axis classes and the methods from the protocol "path construction". 1. Single path steps: ChildAxis ? 'name'. "select all child nodes tagged with 'name'" ChildAxis ? ('prefix' + 'name'). "select all child nodes tagged with 'prefix:name'" AttributeAxis ? 'id'. "select all attribute nodes tagged with 'id'" SelfAxis ? AnyNodeTest. "select the context node itself" DescendantOrSelfAxis ? CommentTest. "select all descendant comment nodes" 2. Concatenate steps with #/ : (ChildAxis ? 'name') / (ChildAxis ? ('second' + 'name')). (ChildAxis ? AnyNodeTest) / (AttributeAxis ? 'id'). "Often, the axis can be omitted:" 'name' / ('second' + 'name'). "same as" (ChildAxis ? 'name') / (ChildAxis ? ('second' + 'name')). AnyNodeTest / (AttributeAxis ? 'id'). "same as" (ChildAxis ? AnyNodeTest) / (AttributeAxis ? 'id'). "Similar to XPath, #/@, #// and #//@ abbreviate attribute and descendant-or-self steps:" AnyNodeTest /@ 'id'. "same as" (ChildAxis ? AnyNodeTest) / (AttributeAxis ? 'id'). 'name' // CommentTest. "same as" (ChildAxis ? 'name') / (DescendantOrSelfAxis ? AnyNodeTest) / (ChildAxis ? CommentTest). 'name' //@ 'id'. "same as" (ChildAxis ? 'name') / (DescendantOrSelfAxis ? AnyNodeTest) / (AttributeAxis ? 'id'). 3. Query from the document root with a RootStep: RootStep // AnyNodeTest. "all nodes" RootStep //@ 'id'. "id of each node" 4. Create the union of two NodeSets with #| : (RootStep // 'element') | (RootStep // CommentTest). "#\@ abbreviates the union with an attribute step:" CommentTest \@ 'id'. "same as" (ChildAxis ? CommentTest) | (AttributeAxis ? 'id'). 5. The wildcards # and * match single and multiple characters in local tag names: ChildAxis ? 'name_##'. "selects e.g. <name_01 />" AttributeAxis ? '*_id'. "selects e.g. ... svg_id='0x5' ..." "NOTE: XPath allows * only for the whole tag name, e.g. //prefix:* " III. Parser API: -------------------- To parse an abbreviated XPath location path, use SimpleXPathParser. However, predicate expressions are not supported. Call #parseString: with the XPath string to parse that string and obtain a NodeSet and #validateString: to check whether the string is free of syntax errors. If parsing fails, a SyntaxError is raised that gives the error position and a brief description. _______________________________________________ vwnc mailing list vwnc(a)cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

13 years, 6 months

2
1
0 0

Thanks for the Overview Pyramid

by pascal.vollmer＠nexgo.de

To whoever implemented the Overview Pyramid in moose: thank you indeed! I like the book "Object-Oriented Metrics in Practice" and I am happy to recommend it by giving a demo on real code. Kind regards, Pascal Pascal Vollmer Email: pascal.vollmer(a)ieee.org

13 years, 6 months

2
1
0 0

almost green tests

by Tudor Girba

Hi, There were several test problems due to the introduction of the new method in LANNode, but I solved them. We now have only one red test: MooseMonticelloImporterTest>>testBasic It seems to be a setup problem, but I cannot figure out why it breaks all of a sudden. Could someone take a look? Cheers, Doru -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

13 years, 6 months

2
1
0 0

3 fame tests disabled

by Tudor Girba

Hi, I disabled the 3 tests from Fame that caused failures on the server, but were running Ok locally. They can be found in the FMMetaRepositoryFilterTest class: - disabledBecauseItFailsOnTheServerInHeadlessModetestExportLIBBookWithPartialMetamodel - disabledBecauseItFailsOnTheServerInHeadlessModetestExportLIBLibraryWithPartialMetamodel - disabledBecauseItFailsOnTheServerInHeadlessModetestExportLIBPersonWithPartialMetamodel Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

13 years, 6 months

2
1
0 0

Re: Issue 216 in moose-technology: No unnecessary port validation

by moose-technology＠googlecode.com

Updates: Status: Fixed Labels: Milestone-4.6 Comment #2 on issue 216 by tudor.gi...(a)gmail.com: No unnecessary port validation http://code.google.com/p/moose-technology/issues/detail?id=216 This is done now using suspendAllWhile: in the renderer

13 years, 6 months

1
0
0 0

Re: Glamour-Merilin-Mondrian

by Júlio Martins

Hi Tudor! On 15 December 2011 19:06, Tudor Girba-2 [via Smalltalk] < ml-node+s1294792n4201975h14(a)n4.nabble.com> wrote: > Hi, > > In general, if you are looking for a code solution, it goes much faster if > you provide some code for us to work on. > > You asked how to run the example with updateable browsers. Every example > from the GLMBasicExamples has a comment with a sample of running it. In > this case, it would be: > |collection| > collection := GLMAnnouncingCollection new. > collection add: 1; add: 2; add: 3. > GLMBasicExamples new updateableIndividualPresentations openOn: collection. > > Ok! I will remember this. Thanks! > But, coming back to the problem, let me summarize what I understood the > problem is, and then you tell us if it is so: > - you have a browser > - in that browser you have an action that opens a Merlin wizard > - you want that given the value returned by the wizard to update the whole > browser, or just a part of it > > If this is correct, you can probably do something like: > browser act: [:b | filterWizard atEndDo: [...]. b update ] entitled: '...' > > You are correct! This value retrieved from the wizard i need to update the browser Indeed what I have to update is a distribution map. I have tried to use this browser act: [:b | filterWizard atEndDo: [...]. b update ] entitled: '...' method but my Merlin wizard doesn't appear. I only can do this when I use browser spawn: [:a| filterWizard atEndDo:[:wizardInformation| a transmit to: #map; andShow:[:b| self distributionMapIn: b with: (wizardInformation at: #textEntry) ] ] ] entitled: 'Filter'. I thought this would be sufficient to update the distribution map, but I was wrong. I can't understand good how use your hint.. > > > On 15 Dec 2011, at 14:37, Júlio Martins wrote: > > > Very nice! > > > > This is what I was needing. This method atEndDo serves to me good. > However i can't update the view yet. The current modrian view persist and I > can't show a new view based on the value gotten from the wizard. > > Following the code that I am using. The method distributionMapIn: with: > just build the view. I thought this was sufficient to update the view, but > it doesn't work.The old view persist. > > > > filterWizard := WizardControl new > > atEndDo:[:wizardInformation| > > browser transmit > > to: #map; > > andShow: [ :a | self distributionMapIn: a with: (wizardInformation at: > #textEntry) ]. ] > > > > How can I show the new view? > > > > On 14 December 2011 16:48, Cyrille Delaunay [via Smalltalk] <[hidden > email]> wrote: > > I think that what you are looking for is the place where to retrieve the > values returned by your wizard and update your visualization according it. > > What you could do is: when you create your merlin wizard, send the > message 'atEndDo:', where your specify a block with the action to perform > at the end of the wizard: > > > > WizardControl new > > ...; > > ...; > > atEndDo: [:wizardInformations | updateVisualizationWith: > (wizardInformations at: #key)]. > > > > > > > > 2011/12/14 Alexandre Bergel <[hidden email]> > > > > > > > > > A mondrian browser call a window that contain radio buttons, text > field. A value that I need will be on text field, so when I performed an > action in a button finish, I can update the view in back window. ( ok?) > > > How a good manner to do it? > > > > Hi! > > I still do not understand the example. How a Mondrian browser can call a > window? > > Maybe a screenshot will help us help you > > > > Alexandre > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > -- > > Cyrille Delaunay > > http://cyrilledelaunay.seasidehosting.st/ > > > > > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Glamour-Merilin-Mondrian-tp4195096p4196469.html > > To start a new topic under Moose, email [hidden email] > > To unsubscribe from Moose, click here. > > NAML > > > > > > View this message in context: Glamour-Merilin-Mondrian > > Sent from the Moose mailing list archive at Nabble.com. > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] <http://user/SendEmail.jtp?type=node&node=4201975&i=0> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "To utilize feedback, you first have to acquire it." > > > _______________________________________________ > Moose-dev mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=4201975&i=1> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Glamour-Merilin-Mondrian-tp4199967p4201975.html > To start a new topic under Moose, email > ml-node+s1294792n1310756h25(a)n4.nabble.com > To unsubscribe from Moose, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Re-Glamour-Merilin-Mondrian-tp4202902p4202902.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

3
2
0 0

VerveineJ does not parse some annotations in Java

by Usman Bhatti

I am parsing a small java project with VerveineJ. The purpose is to see the capability of VJ to parse EJB and specifically session beans. There is a small student project of which a few classes implement SessionBeans. http://code.google.com/p/sius/ When I parse the project with VerveineJ from the menu in Moose, I see other annotations but I do not find the session and WLHTTPTransport annotations in my moose model. These annotation are present in the following file: http://code.google.com/p/sius/source/browse/trunk/jws_basic/audi/SimpleBean… . Also, I do not see the type SessionBean that is an interface, in the list of types in my moose model. I did not open an issue because I wasn't sure if the problem originates from the class path not well-defined or verveineJ not correctly parsing. Can you please help? thanx, Usman

13 years, 6 months

2
1
0 0

Glamour-Merilin-Mondrian

by Júlio Martins

Very nice! This is what I was needing. This method atEndDo serves to me good. However i can't update the view yet. The current modrian view persist and I can't show a new view based on the value gotten from the wizard. Following the code that I am using. The method distributionMapIn: with: just build the view. I thought this was sufficient to update the view, but it doesn't work.The old view persist. filterWizard := WizardControl new atEndDo:[:wizardInformation| browser transmit to: #map; andShow: [ :a | self distributionMapIn: a with: (wizardInformation at: #textEntry) ]. ] How can I show the new view? On 14 December 2011 16:48, Cyrille Delaunay [via Smalltalk] < ml-node+s1294792n4196469h28(a)n4.nabble.com> wrote: > I think that what you are looking for is the place where to retrieve the > values returned by your wizard and update your visualization according it. > What you could do is: when you create your merlin wizard, send the message > 'atEndDo:', where your specify a block with the action to perform at the > end of the wizard: > > WizardControl new > ...; > ...; > atEndDo: [:wizardInformations | updateVisualizationWith: > (wizardInformations at: #key)]. > > > > 2011/12/14 Alexandre Bergel <[hidden email]<http://user/SendEmail.jtp?type=node&node=4196469&i=0> > > > > >> >> > A mondrian browser call a window that contain radio buttons, text >> field. A value that I need will be on text field, so when I performed an >> action in a button finish, I can update the view in back window. ( ok?) >> > How a good manner to do it? >> >> Hi! >> I still do not understand the example. How a Mondrian browser can call a >> window? >> Maybe a screenshot will help us help you > > >> Alexandre >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] <http://user/SendEmail.jtp?type=node&node=4196469&i=1> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > > > -- > Cyrille Delaunay > http://cyrilledelaunay.seasidehosting.st/ > > > _______________________________________________ > Moose-dev mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=4196469&i=2> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Glamour-Merilin-Mondrian-tp4195096p4196469.html > To start a new topic under Moose, email > ml-node+s1294792n1310756h25(a)n4.nabble.com > To unsubscribe from Moose, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Glamour-Merilin-Mondrian-tp4199967p4199967.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

2
1
0 0

Glamour-Merilin-Mondrian

by Júlio Martins

I can't sent a screenshot, sorry. Maybe I should choose better the words. It is not a mondrian that call a window, but a main window (an instance of GLMTabulator ) that contain a modrian view and that call a secondary window (an instance of WizardSinglePanel) by a menu. So what I need is, from this secondary window, be able to update the view, in the main window, using the value that I typed on secondary window.. It's better now? On 14 December 2011 15:53, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > A mondrian browser call a window that contain radio buttons, text field. > A value that I need will be on text field, so when I performed an action in > a button finish, I can update the view in back window. ( ok?) > > How a good manner to do it? > > Hi! > I still do not understand the example. How a Mondrian browser can call a > window? > Maybe a screenshot will help us help you > > Alexandre > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- View this message in context: http://forum.world.st/Glamour-Merilin-Mondrian-tp4196361p4196361.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

2
1
0 0

publishing my importer fixes

by Stéphane Ducasse

Hi guys I published my smalltalkimporter fixes. Now would be good to check if everything is working. BTW I put the pools fixed code I did in pharo 1.4 as extensions of SmalltalkImporter. We will have to removed them when migrating to 1.4 so let me know Stef

13 years, 6 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev