Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

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, 2 months

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, 2 months

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, 2 months

[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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev