- Moose-dev - INF Mailman

by Tudor Girba

Hi Martin, hi Mariano, Loading FuelMooseExtensions 1.4 is broken because FuelContainer is no longer loaded. This is due to the fact that FuelContainer was taken out of the CoreWithExtras group from ConfigurationOfFuel 1.7. Could you take a look? Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

13 years, 4 months

2
3
0 0

Que tal?

by Alexandre Bergel

Hi! "Que tal?" in Spanish can be translated in English as "How are you? How things are going?" It would be cool that each of us briefly summarize what he is working on and what is the future plan. Visualization engine: I am intensively working on Roassal. A new visualization engine that should replace Mondrian. Roassal will provide a better user experience with visually appealing animations and interactions. I will probably make some announcement at the beginning of March. The mid-long term vision of Roassal is to have an agile and portable visualization engine. I want to make it work on VisualWorks and Amber, in addition to Pharo. Analyzing Smalltalk application: Together with Santiago, we are working on using unit test to refine model obtained from Smalltalk applications. The idea is to profile what is currently executing to reduce superfluous invocation candidates. I also applied to some grant to analyze JavaScript applications in Moose. We will see how it goes. What about you? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 4 months

7
12
0 0

cannot import mse file gnerated with inFamix

by Fabrizio Perin

Hi all, I have some problem to load a mse file into the latest stable moose. When the progress bar reaches slightly more than the middle the image crashes. The mse file has been generated with inFamix and it is ~120MB big. The same software parsed using inFusion generates a mse file of ~100MB and this second file works. using moose 4.6 on pharo #13315 and the VM of Eliot Cog 2519 Did anybody have problems with mse files generated with inFamix? Cheers, Fabrizio

13 years, 4 months

2
2
0 0

Re: [Pharo-project] cannot add repository in monticello

by Fabrizio Perin

Hi, the error described is different but surely related because I loaded the slice and yes, the problem was solved. Thanks Matias. Cheers, Fabrizio 2012/2/14 Matias Garcia Isaia <mgarciaisaia(a)gmail.com> > Fabrizio, > > can you confirm if it's the same issue that happens with > <http://code.google.com/p/pharo/issues/detail?id=5292> ? > > There's a slice there, maybe you can try if that fixes your problem. > > On Tue, Feb 14, 2012 at 3:02 PM, Fabrizio Perin > <fabrizio.perin(a)gmail.com> wrote: > > Hi, > > I just tried to add a new repository in Monticello and I got an error: > > the error is: > > > > MessageNotUndestood: FileDialogWindow>>directoriesFor: > > > > the repository I wanted to add was a directory. It seems to work in the > case > > you want to add a HTTP repository. > > > > The problem happen on the last Moose build (#830) and on a > > Pharo1.4a > > Latest update: #14331 > > > > downloaded from the pharo web site. > > > > Cheers, > > Fabrizio > >

13 years, 4 months

1
0
0 0

troubles with glamour finder in pharo 1.4

by Tudor Girba

Hi, We are almost done with getting Glamour work on 1.4. The model works, and most of the rendering is fine as well. The only major trouble is with the rendering of the finder. In particular, the problem is the scrolling through the panes. The scrolling code was basically copied from OB (shamelessly :)). Something must have changed in Pharo 1.4 that disables some of the behavior. Could anyone spare a pair of eyes to look into this :). Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

13 years, 4 months

1
0
0 0

cannot add repository in monticello

by Fabrizio Perin

Hi, I just tried to add a new repository in Monticello and I got an error: the error is: MessageNotUndestood: FileDialogWindow>>directoriesFor: the repository I wanted to add was a directory. It seems to work in the case you want to add a HTTP repository. The problem happen on the last Moose build (#830) and on a Pharo1.4a Latest update: #14331 downloaded from the pharo web site. Cheers, Fabrizio

13 years, 4 months

1
0
0 0

pharo conference :)

by Stéphane Ducasse

http://pharoconference.eventbrite.com/ Stef

13 years, 4 months

1
0
0 0

how to load rb in pharo 1.4?

by Tudor Girba

Hi, I lost track of the latests developments around RB. What is the way to load RB in Pharo 1.4? Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

13 years, 4 months

2
1
0 0

PPParser not returning file contents

by Usman Bhatti

Hello all, We are using petitParser with a Stream by the parse method on a PPParser. This parse method calls asPetitStream on our stream which is supposed to return a stream with a valid format for PPParser. The problem is that this stream do not represent our test file but a lot of white spaces. this code: (StandardFileStream fileNamed: '/some/path/to/file/atextfile.txt' ) asPetitStream proves that. Did someone else have a similar problem with petit parser? thanx, Usman & Guillaume

13 years, 4 months

3
6
0 0

plunging towards 1.4

by Tudor Girba

Hi, I moved the moose-dev build to 1.4. Of course, it is broken :). Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

13 years, 4 months

2
1
0 0

glamour on pharo 1.4

by Esteban Lorenzano

Hi, I made glamour to load on pharo 1.4... now, I have some errors on tests (17), most of them because MorphTreeMorph>>#mouseUp:onMorph: does not exists anymore. I don't know how to fix that. Should I commit my changes anyway, and hope some benevolent developer to fix that (Doru?) best, Esteban

13 years, 4 months

2
8
0 0

Re: Issue 775 in moose-technology: Glamour should not clip panes with fixed sizes

by moose-technology＠googlecode.com

Updates: Summary: Glamour should not clip panes with fixed sizes Labels: Component-Glamour Comment #1 on issue 775 by tudor.gi...(a)gmail.com: Glamour should not clip panes with fixed sizes http://code.google.com/p/moose-technology/issues/detail?id=775 Thanks. You are not doing anything wrong. This is a bug.

13 years, 4 months

1
1
0 0

pharo sprint (feb 18) / moose dojo (feb 19) - Bern

by Tudor Girba

Hi, We would like to organize a Pharo Sprint (Feb 18) and Moose Dojo (Feb 19). Pharo Sprint - the main goal is to clarify the direction of Pharo concerning the architecture and the way to get to a small system. - current participants: Stéphane Ducasse, Jorge Ressia, Lukas Renggli, Tudor Girba, you? Moose Dojo - the main goal is to setup a new project/package structure to enable a better evolution and to match the abstract architecture: http://www.themoosebook.org/book/introduction/nutshell - current participants: Stéphane Ducasse, Tudor Girba, you? The gatherings will take place in Bern, at the Software Composition Group, University of Bern: http://scg.unibe.ch/contact/maps Please let us know if you intend to participate. Remote participation would probably be possible as well. Cheers, Doru

13 years, 4 months

2
2
0 0

[ANN] moose 4.6

by Tudor Girba

We are happy to announce the Moose Suite version 4.6: http://moosetechnology.org/download What is new: • New editors for scripting browsers and visualizations • Improved Glamour browser building engine • Improved EyeSee charting engine • Improved FAMIX API • Improved FAMIX to support Java and C++ • Improved external importers to support Java and C++ A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team

13 years, 4 months

1
0
0 0

Re: [Pharo-project] load testing a database

by Tudor Girba

Hi, Sorry for the late reply, and thanks everyone for the suggestions. I did not provide much details because I am new to this domain and I wanted to see from the reactions if maybe I am not missing some relevant direction. We are trying to measure how an Oracle database can cope with an increase in usage (basically, there will be more users for the application). We are basing our analysis on typical SQL statements coming from the application. We are currently doing load testing by: - recording sql statements from some use cases that are considered to be important - generalizing them by replacing actual values with generic variables - providing meaningful values for the generic variables - replaying them against the database from several client machines - consuming the first record from the responses - reporting the timing of the statements - recording the CPU, memory and I/O load of the server However, I am interested in pitfalls, and in the way people interpret the results given that it is hard to determine what is a typical usage in terms of what statements to trigger and at what delays. Cheers, Doru On 5 Feb 2012, at 19:02, Philippe Marschall wrote: > On 03.02.2012 16:11, Tudor Girba wrote: >> Hi, >> >> Do you happen to know methods to approach the problem of testing the >> capacity of an application to work with an SQL database? > > Which capacity? > >> In particular, I am interested in simulating concurrent requests >> towards this database that would resemble the interaction coming from >> the application. > > What are you trying to measure? > > Well you know that benchmarking is hard, don't you? I see two possible ways. First recording the SQL statements and then replaying them (have fun with bind parameters). Second just running the application itself. > > Oh yeah, Oracle has a tool named RAT, no idea what the marketing department though there. Maybe you can play similar tricks with PITR in PostgreS. > > Cheers > Philippe > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

13 years, 5 months

1
0
0 0

Issue 775 in moose-technology: Pane partially clipped

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 775 by marcmoo...(a)gmail.com: Pane partially clipped http://code.google.com/p/moose-technology/issues/detail?id=775 Hello I have some small problem in Glamour. When I execute following in a Workspace | browser | browser := GLMTabulator new. browser row: #menuBar size: 25. "Bottom Part get hidden because of this" browser row: [ :r1 | r1 column: [ :c| c row: [:r | r column: #one; column: #two ] span: 2; row: #three. ]]. browser transmit to: #one; andShow: [:a | a title: 'One'. a list ]. browser transmit to: #two; andShow: [:a | a title: 'Two'. a list ]. browser transmit to: #three; andShow: [:a | a title: 'Three'. a list "title: 'List'" ]. browser openOn: (1 to: 10) the bottom part of the third pane is partially hidden. Do I something wrong? (A hacky workaround is to simplay add an additional row with size 25 -- which then is invisible) (See attached picture) Tested in Pharo 1.1 - 1.3 Marc Please fill in the labels with the following information: * Type-Defect * Component-Glamour Attachments: hidden.png 18.5 KB

13 years, 5 months

1
0
0 0

Issue 759 in moose-technology: EyeSee window should provide export options

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee New issue 759 by tu...(a)tudorgirba.com: EyeSee window should provide export options http://code.google.com/p/moose-technology/issues/detail?id=759 We should be able to easily export a chart to file.

13 years, 5 months

1
3
0 0

Issue 751 in moose-technology: Problem with isPrime

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 751 by stephane...(a)gmail.com: Problem with isPrime http://code.google.com/p/moose-technology/issues/detail?id=751 Describe the problem: what do you get? what do you expect? How to reproduce the problem: step by step if necessary Additional information: platform, context which may impact the problem Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX

13 years, 5 months

1
4
0 0

realeasing moose 4.6

by Tudor Girba

Hi, As there is not much activity around Moose, there is hardly any point to wait for releasing 4.6. I will do it tomorrow. If you have objections, please raise them until then. Cheers, Doru -- www.tudorgirba.com "Reasonable is what we are accustomed with."

13 years, 5 months

1
0
0 0

Issue 750 in moose-technology: GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 750 by usman.bh...(a)gmail.com: GLMTextModel(Object)>>doesNotUnderstand: #highlightSmalltalk: http://code.google.com/p/moose-technology/issues/detail?id=750 In Menssana, when clicking on various reports, we get this error. - Import a model in moose - Launch detailed dashboard in menssana -> top ten lint rules -> browse classes and then we get this error. I may be missing some extensions of glamour in my image?

13 years, 5 months

3
10
0 0

Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 743 by usman.bh...(a)gmail.com: This is strange that we have to systematically specify the class of the importer http://code.google.com/p/moose-technology/issues/detail?id=743 a typical sript to import a model is MooseSqueakClassPackageImporterTask new importerClass: SmalltalkImporter; model: model; addFromPackageNamed: #'Moose-TestResources-LAN'; run; yourself But it is rare that we should change the importerClass (it was useful when we had to import FAMIX2 and FAMIX3 side by side). I suggest that we introduce a default and that we initialize the importerClass to SmalltalkImporter.

13 years, 5 months

1
4
0 0

Issue 738 in moose-technology: bugs in EyeSee

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Platform-Pharo Component-EyeSee New issue 738 by alexandr...(a)gmail.com: bugs in EyeSee http://code.google.com/p/moose-technology/issues/detail?id=738 I played with the matrix in EyeSee in a Pharo image. I found some problems: - #new:withAll: and #new: seems to raise an emergency debugger, whatever the value we provide - Many references are made that do not belong to EyeSee. For example #zero that refers to MalMatrixCoercion I also found other problems (e.g., hash). I added some tests for those. I produced version 0.9.2 Cheers, Alexandre

13 years, 5 months

1
3
0 0

Issue 730 in moose-technology: inFamix should create namespaces without path information

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 730 by tu...(a)tudorgirba.com: inFamix should create namespaces without path information http://code.google.com/p/moose-technology/issues/detail?id=730 Currently, inFamix is exporting namespaces with names containing path information like src/com::example. It should be only com::example.

13 years, 5 months

1
2
0 0

Issue 712 in moose-technology: Create a method fillColor:

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 712 by andreho...(a)gmail.com: Create a method fillColor: http://code.google.com/p/moose-technology/issues/detail?id=712 Implement a method fillColor: aBlock to be able to change the fill of a bar based on its value.

13 years, 5 months

1
2
0 0

Issue 703 in moose-technology: inFusion should export C++ Enums

by moose-technology＠googlecode.com

Status: New Owner: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 703 by tudor.gi...(a)gmail.com: inFusion should export C++ Enums http://code.google.com/p/moose-technology/issues/detail?id=703 Currently, there are no Enums in C++ models.

13 years, 5 months

1
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev