Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1060 by santiago...(a)gmail.com: Static modifier missing in inner
classes (VerveineJ)
http://code.google.com/p/moose-technology/issues/detail?id=1060
If I have the following Java Code
public class A {
public static innerClass{
}
}
public is the only modifier of innerClass in the MSE. That is, the static
modifier is missing.
--
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
New issue 1059 by santiago...(a)gmail.com: Problem of VerveineJ detecting
references
http://code.google.com/p/moose-technology/issues/detail?id=1059
VerveineJ fails to represent references produced by "instanceOf" and
castings.
If I have the following Java Code
public class A {
public void foo(Object o){
if(o instanceof B){ //DoSomething }
}
Moose does not find any outgoing invocation or reference from A to B.
--
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
Hi
We found with igor the problems that produced red cross in Moose.
The problem is that the system is looking Source Sans Pro and does not find it.
The logic in findBestFont: does not find it because there is no such font registered in font manager
and the default logic is to return TextStyle defaultFont which is a bitmpa one.
So question:
- may be we should have a FT font default loaded in the system?
- Doru we remember that you loaded font in the system? May be you do not register well the fonts.
Could you let us know what you did?
Stef and Igor.
Dear all,
The MOOSEDay@UPMC 2014 will be organized in Paris, June 5th.
The day will be followed by a Pharo Sprint (June 6th) at the same place.
A first draft of the MOOSEDay@UPMC is online here:
http://www.doesnotunderstand.org/MOOSEDayUPMC/
I need you help :
- if you want to propose a talk, send me title, a short summary (3-4
lines), the name and a picture of the speaker.
- if you want to sponsor the event, just ask me :-)
- if you want to attend, just send me your name and affiliation. I
will add you on the webpage.
- if you have some graphic abilities, you can send me a better cover
picture (maybe with some MOOSE pictures).
The webpage is managed on github, if you want to modify the page, just
send me a pull request on github:
https://github.com/SergeStinckwich/MOOSEDayUPMC
Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
Hi,
If you want to install GToolkit (the project that contains GTInspector,
GTPlayground and GTDebugger) in your image, you can follow one of the
options as described here:
http://www.humane-assessment.com/blog/installing-gtoolkit
If you give it a try, please let us know how it works for you.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
Is there any particular reason for GLMRoassal2Presentation working with
RTView instead of RTMondrianViewBuilder i.e. in the painting block, we get
RTView object instead of the builder.
I am asking this question because the predecessor, GLMRoassalPresentation,
used to work with ROMondrianViewBuilder. Now, when we'll move our
visualizations to work with Roassal2 in Glamour we'll have to make major
modifications to the source code because the level of details with RTView
and RTMondrianViewBuilder is not the same.
Usman
Hi everybody,
I am using PetitParser a lot and had implemented some little tools that
help me for writing or generating grammars. I put two of the most useful in
the project PetitParserExtension (
http://smalltalkhub.com/#!/~Moose/PetitParserExtensions).
the first one is useful when you generate grammars with lots of rules:
A PPExtendedCompositeParser offers you a new way to create rules. Just
define your rule as a method in the #rules protocol and it will be managed
exactly like rules in PPCompositeParser.
You will not have the limitation of 256 rules due to the instance variables
limit but you will need to refer to your rule with the method #rule: in any
other rule using it.
You can mix PPCompositeParser and PPExtendedCompositeParser way to define
rules.
the second one is cool for token identification because it creates a parser
that will parse in a time depending on token length and not the number of
different tokens.
A PPMultiStringParser is a tool able to create a really effective parser on
a huge collection of Strings. This parser will match any string in this
collection, and the longest one if two are matchable (( PPMultiStringParser
on: #('tin' 'tintin')) parse: 'tintin' will match 'tintin' and not just
'tin')
If someone else has implemented some tools around PetitParser, it will be
great to put those all together so feel free to commit your tools in this
project and to improve mines.
--
*Guillaume Larcheveque*