With both MOOSE 4.6 release and 4.7 dev the number of available fonts seems to be limited to DejaVu Sans, and Accuny in 4.6. How do I load system truetype fonts? Is this related to one of the 1.4 bugs?
Stephan
Hello,
A research using Moose at UFMG, Brazil.
More information in the web site below.
---------- Forwarded message ----------
From: Marco Tulio Valente <mtov(a)dcc.ufmg.br>
Date: Tue, Nov 20, 2012 at 1:03 PM
Subject: COMETS - Code Metrics Time Series Dataset
To: Nicolas Anquetil <nicolas.anquetil(a)inria.fr>, Andre Hora <
andrehoraa(a)gmail.com>, Stéphane Ducasse <stephane.ducasse(a)inria.fr>, Cesar
Couto <cesarfmc(a)gmail.com>
Hi Nicolas, Andre, and Stephane,
Just to inform that we have made public the dataset with the code
metrics time series that Cesar is using in his research.
java.llp.dcc.ufmg.br/comets
All time series have been extracted using Moose (in fact, we are
making public not only the csv files with the metrics, but also the
mse files).
Cheers,
Marco Tulio.
--
Andre Hora
Hi,
today I deliver a moose one-click image downloaded from the moose ci and
the vm was crashing on start. the OS was Windows 7 64-bit.
Any idea / know problem?
Cheers,
Fabrizio
Guillermo wrote:
>It is a really great idea since stackoverflow is searchable on google,
>therefore people can find answers easily.
For that the mailing list works just as well.
>Besides one feature of stackoverflow is that answers get voted on by users,
>therefore the most popular answers bubble up naturally.
That is no longer the case. The first year that worked pretty well, but
if you take a look at more current questions you'll see that Stackoverflow
is basically dying. The gamification is no longer working. Quality of the
questions is getting pretty bad: very detailed questions with less and less
relevance. The refusal to deal with questions relevant for software and
team development is also not helping.
Another point is that often popular answers are simply wrong. There is a very
large cargo culture visible. Just take a look at the OODB questions.
It is a pity that nobody tried to visualize the number of answers, votes
and comments the questions get over time, and the size of the different
communities.
It's not that I don't like the format, or the gamification. In our Seaside/
smalltalk workshop we use an example that looks a lot like it.
Stephan
Status: New
Owner: ----
CC: chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 864 by tu...(a)tudorgirba.com: Updating a browser should preserve
the visual selection in morphic
http://code.google.com/p/moose-technology/issues/detail?id=864
The following snippet should work.
browser := GLMFinder new.
browser show: [ :a | a list ].
browser openOn: ($a to: $d).
browser panes first presentations selection: $b.
browser update.
And at the end $b should continue to be selected.
Hi!
Some asked for this on some point.
A new event is generated every 100 nodes that are layouted:
-=-=-=-=-=-=-=-=-=-=-=-=
| view rawView statusBar |
rawView := ROView new.
view := ROMondrianViewBuilder view: rawView.
"-------------"
"-------------"
statusBar := ROElement new + ROLabel + ROBox white.
view stack add: statusBar.
statusBar translateTo: 0 @ 480.
view interaction on: ROMouseEnter do: [ :event |
statusBar model: event element model.
].
view shape rectangle size: 10.
view nodes: (1 to: 1500).
view horizontalLineLayout
on: ROLayoutStep do: [ :evt |
statusBar model: evt currentIteration printString, ' / ', evt maxInterations printString.
World doOneCycleNow.
view raw signalUpdate.
].
"-------------"
"-------------"
"Below is the initiation of the menu and opening the visualization"
ROEaselMorphic new populateMenuOn: view.
view open
-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
CC: anquetil...(a)gmail.com, eitch...(a)gmail.com
Labels: Type-Defect Priority-Medium Maintainability Milestone-4.7
New issue 866 by tu...(a)tudorgirba.com: MalKontractorTest should be moved
into Moose-Tests-Algos-Kontractor
http://code.google.com/p/moose-technology/issues/detail?id=866
Right now it resides in the same package as the implementation.
Status: New
Owner: ----
CC: esteba...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 799 by tudor.gi...(a)gmail.com: Editing code in Glamour must be
faster
http://code.google.com/p/moose-technology/issues/detail?id=799
Launch the following browser, and then try to type more code. It is dead
slow. Using the same fragment in the workspace is fast. This means that we
are probably using the PluggableTextMorph in a wrong way. The problem
appeared since Pharo 1.4.
GLMWrapper new
show: [:a | a text ];
openOn: 'GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.'
Hi,
is there in roassal any event that triggers right after the layout is
applied?
What I'm trying to do is to center on an element after the layout is
applied (so after the element have a position in the visualization).
Thanks,
Fabrizio
Status: New
Owner: ----
CC: chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 863 by tu...(a)tudorgirba.com: Browsers that subclass
GLMCompositePresentations should be embed-able
http://code.google.com/p/moose-technology/issues/detail?id=863
This snippet should work:
GLMCompositePresentation new wrapper
with: [:w | w show: [ :a | a custom: MooseFinder new]];
openOn: (1 to: 100)
Status: New
Owner: ----
Labels: Type-Engineering Priority-Medium Maintainability Milestone-4.7
New issue 865 by tu...(a)tudorgirba.com: Reloader should get the list of
packages to be loaded from the ConfigurationOfMoose
http://code.google.com/p/moose-technology/issues/detail?id=865
Right now, the list of packages is hardcoded. We should get it directly by
traversing the Configuration.
Hi,
I was loading some old code and some of browsers I wrote do not open
correctly anymore. Apparently I cannot do something like this anymore:
browser transmit
to: #finder;
from: #functions port: #selection;
andShow: [ :a | a custom: (MooseFinder startOn: a) ].
This because MooseFinder do not understand anymore startOn:.
Any suggestions on how can I make this glamour example working again?
mooseFinderOnSelectedElement
"self new mooseFinderOnSelectedElement openOn: (1 to: 100)"
<glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'>
| browser |
browser := GLMTabulator new.
browser
column: #functions;
column: #finder.
browser transmit
to: #functions;
andShow: [ :a |
a list
title: 'Functions';
display: [ :each | each ] ].
browser transmit
to: #finder;
from: #functions port: #selection;
andShow: [ :a | a custom: (MooseFinder startOn: a) ].
^browser
Thanks,
Fabrizio
Hi Vanessa,
>I fix the little bug with the numberOfLinearOfCode, however, I do not
>understand the issue with the String crlf as I can see the popupText ok.
>Where this happens?
Great, it now works for me. I've probably loaded something in the wrong order.
Thanks for the fast response,
Stephan
Hi,
In a 7.8.1 image, the Roassal SystemComplexity example shows a few MNUs.
The popupText expects String crlf instead of String cr, and numberOfLinesOfCode
is not recognized, even though it is added to ClassDescription in *roassal-core
Cheers,
Stephan
Hi,
Right now, we have several pieces of code that involve hi-graphs:
- DSM
- Softwarenaut
- Carrack
On the other hand, we have the graph support from Moose-Algos.
It would be cool to look into the variation and consolidate them. Perhaps
this can also be a topic for the Moose Dojo.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Call for Participation in the Smalltalk Devroom at FOSDEM 2013.
http://www.fosdem.org
" A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside,
Moose Smalltalk projects & Newspeak as derived language.
Smalltalk environments offer a very high development productivity,
unmatched by their successors. Come do some pair programming
with us and experience yourself the advantages of a real OO
environment"
The meetup will take place Sunday, February 3, 2013,
from 9AM until 5PM, building AW. This room has 72 seats,
a VGA video projector and wireless internet.
More information will be available later.
Proposals on content and format are welcome.
People interested in running a session should announce that
on the smalltalk-devroom mailing list, with the following
information:
- Their name
- The project they are associated with
- A short bio, to be put on the website along with their speaker name
- (optionally) a picture of themselves
- The title of their session (which will go on the website and in the booklet)
- A abstract describing the session in further detail.
- The desired length of the session.
- The desired time slot in which they want to hold the session.
Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha).
The desired time slot is meant to help you prevent conflicts with other dev
rooms in which you might have a talk or your travel arrangements.
There are alternative, non smalltalk-specific tracks available:
lightning talk and the main track
The deadline for submissions is December 31, 23:00 GMT+1.
Discussion takes place on the
smalltalk-devroom(a)lists.fosdem.org
mailing list. Please subscribe if you are interested:
https://lists.fosdem.org/listinfo/smalltalk-devroom
The local VUB/ULB Smalltalkers have been asked to organize
a sprint/BSUG meeting/Camp Smalltalk on Saturday February 2.
Devroom related URLs:
http://www.pharo-project.orghttp://www.squeak.org/http://etoileos.com/http://www.seaside.st/http://smalltalk.gnu.org/http://www.moosetechnology.orghttp://amber-lang.nethttp://newspeaklanguage.org/http://www.esug.org
Hi,
During November 15,16 we will organize a Moose Dojo at the University of Bern (starting at 09:00):
http://www.moosetechnology.org/events/2012-11-16-dojo
The goal of the sprint is to get as close as possible to a 4.7 release:
http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone%3D4…
Some of the more important todos:
- Issue 799: Editing code in Glamour must be faster
- Issue 851: Create a stable version for Moose and all its subparts
- Issue 853: ConfigurationOfMoose should be split to reflect core vs suite
- Review and refactor old FAMIX Cook navigation
Cheers,
Doru
--
www.tudorgirba.com
"What we can governs what we wish."
Is there a way nice way to do a lookup in PP ?
for example, I want to ensure that I have a 'a' then a 'b'.
But I don't wan't to consume 'b'
'a' asParser , 'b' asParser lookup
currently I implemented it with a double not :-)
'a' asParser , 'b' asParser not not
not very nice
nicolas
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 860 by tu...(a)tudorgirba.com: Updatng a list disables the visible
selection
http://code.google.com/p/moose-technology/issues/detail?id=860
For example, try:
GLMFinder new
show: [:a | a list display: [:x | 1 to: x]];
openOn: 10;
with: [:b | b panes first presentations selection: 4. b update ].
Doing it without the explicit update works just fine, though