Hi!
I am almost done with porting DSM views into Roassal. There is several
times (for
example: NumberColoredDSM>>contentOfSimplyCell:for:with:out:) used method
MOFilledStyle>>borderStyle: which is not supported by Roassal.
Just for sure: Is it obligatory for this views? Should I implement this
feature in Roassal?
Thanks,
Jura
Hi,
I started to look into the Delphi parser. I was successfully parsing a
couple of large files. I will let you know how it goes.
In the meantime, I would also migrate it to STHub in the Moose team. Is
this Ok with you?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium
New issue 917 by usman.bh...(a)gmail.com: ConfigurationOfMerlin on
Smalltalkhub needs to be updated
http://code.google.com/p/moose-technology/issues/detail?id=917
ConfigurationOfMerlin on Smalltalkhub needs to be updated because the
baseline still loads from squeaksource, it should normally load from the
packages from SmallTalkHub.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.7
New issue 895 by andreho...(a)gmail.com: Lack of entities in verveineJ model
http://code.google.com/p/moose-technology/issues/detail?id=895
I'm parsing the single .java attached file (I have also copied in the end
of this message), and I have some points:
- A stub class FileUtils is not created. As consequence the receiver os the
static invocation "FileUtils.close(ti)" (see last line) is "nil".
- A stub class ArchiveScanner (superclass) is not created.
What do you think about that?
In addition (I believe it is OK):
- A stub class Map is created as FAMIXParameterizableClass (it should just
be used to Generics, no?).
- A 'V' FAMIXParameterType is created
- A Comparable is created as FAMIXParameterizedType
Maybe these three points are coming from the class Map in Java, then it is
OK.
Basically this is the code attached:
=========
public class TarScanner extends ArchiveScanner {
...
protected void fillMapsFromArchive(Resource src, String encoding,
Map fileEntries, Map
matchFileEntries,
Map dirEntries, Map matchDirEntries)
{
TarEntry entry = null;
TarInputStream ti = null;
try {
try {
ti = new TarInputStream(src.getInputStream());
} catch (IOException ex) {
throw new BuildException("problem opening " + srcFile, ex);
}
while ((entry = ti.getNextEntry()) != null) {
Resource r = new TarResource(src, entry);
String name = entry.getName();
if (entry.isDirectory()) {
name = trimSeparator(name);
dirEntries.put(name, r);
if (match(name)) {
matchDirEntries.put(name, r);
}
} else {
fileEntries.put(name, r);
if (match(name)) {
matchFileEntries.put(name, r);
}
}
}
} catch (IOException ex) {
throw new BuildException("problem reading " + srcFile, ex);
} finally {
FileUtils.close(ti);
}
}
...
=========
Hi Doru,
I posted this at the wrong list … probably arrived you, but still. Repost on the proper list.
> Hi Doru,
>
> Feel free to improve on the tool. Some things I agree are not very neatly coded.
>
> Cheers,
> Diego
>
>> Hi Diego,
>>
>> I did not forget about your announcement. I am still going through it. There are things that I would like changed, but nevertheless we now have a first robust solution for in-image configuration development.
>>
>> I will come back with suggestions (and code modifications :)).
>>
>> Cheers,
>> Doru
>>
>
Ok, so I will be able to use "attributes" for a good rendering with
the laggered tree layout.
Well, I did not know that, that's why I've
created a new class which is now called ROCompactTreeNode (or something
like that), but maybe it's not useful to keep it, just a little refactor
of the algorithms, and it will works with regular ROElement.
Igor told
us, that the problem was due to the fact that we keep visualizations
open, while quitting our image, and that when launching it athens try to
draw on a surface (external to pharo) that does not exist any more.
Updating to 2.1 solve the problem, we have an error instead of an
exit.
Regards
Mathieu
Hello, I'm trying to put on the same graph a cloud of points and a straight
line calculated by the method of least squares. Not working very well when
I use a code like what goes down:
|x y data scat line k xx yy renderer|
> x := #(0 1 2 3 4).
> y := #(0 1 2 3 4).
> data := OrderedCollection new.
> k := 0.
> x size timesRepeat: [
> k := k + 1. xx := x at: k. yy := y at: k.
> data add: xx @ yy
> ].
> scat := ESScatterPlot new.
> scat
> x: [:each| each value x];
> y: [:each| each value y];
> baseAxisLine;
> valueAxis;
> models: data.
> line := ESLineDiagram new.
> line
> x: [:each| each value x];
> y: [:each| each value y];
> models: data.
>
> renderer := ESDiagramRenderer new.
> renderer compositeDiagram
> add: scat;
> add: line.
>
> renderer open
The chart can be seen in http://tinypic.com/r/34zeicg/5.
Already grateful for any assistance.
--
Sds.,
Francisco Ary Martins
http://chicoary.wordpress.com
----
"Estes são os meus princÃpios. Se você não gosta deles, eu tenho outros."
Grouch Marx