preparing for Moose 4.4
by Tudor Girba
Hi,
The list of issues for 4.4 got smaller, but we won't make it with a release today:
http://code.google.com/p/moose-technology/issues/list?q=milestone=4.4
I will work on them in the following week, but it would be great to have some help.
Especially, it would be cool to have VerveineJ ready for prime time. The good news is that it does not crash and it is super fast. However, there are still some small issues that make it less usable in practice (like setting correct source anchors, exporting all annotations and setting the file format in utf-8).
I would also need some help on the SmalltalkImporter issues. Cyrille and Jannik, would you have some time to look into these issues?
I will try to finalize Metanool and look into fixing FAMIX queries.
The new deadline is in 1 week or so :).
Cheers,
Doru
--
www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
11 years, 10 months
Issue 595 in moose-technology: [Glamour] Transmission>>from: is said to take a port
by moose-technology@googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 595 by damien.c...(a)gmail.com: [Glamour] Transmission>>from: is
said to take a port
http://code.google.com/p/moose-technology/issues/detail?id=595
The method GLMTransmission>>from: takes a parameter 'aPort'. However, this
method is most of the time used with a pane symbol instead of a port. This
is confusing as the Moose book says
"
For specifying a transmission origin that points to a #selection port
of a pane, you simply use from:.
"
In this case it is clear that the port is #selection and it is the default.
The reader is then waiting for an implementation similar to:
GLMTransmission>>from: aPaneSymbol
^ self from: aPaneSymbol port: #selection
11 years, 10 months