Hi,
FAMIXJavaPrintVisitor is not present in the image which makes some tests
fail.
It was added in Famix-Java-synectique.87 but then removed
in Famix-Java-vincentBlondeau.88.
I added it back in Famix-Java-AndreiChis.89, but even if Monticello shows
that the latest package is
loaded, FAMIXJavaPrintVisitor is still missing.
Any idea what is going ok?
Cheers,
Andrei
Hi!
This method is deprecated. But it apparently has some senders in the last moose image. This makes Spotter raises en exception.
The class side of Dictionary uses this selector.
Can someone fix this? This is important
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
Moose/FAMIX uses RoelTyper for type inference, how this does not seem to be maintained (last version 2013), and for my purposes is lacking.
So do we have something more advanced, even at the expense of speed?
Other alternative would be to either extend RoelTyper or write something custom that would be ran alongside RoelTyper.
Examples of such extensions would be extracting the type from meta-annotations and the actual argument names. (e.g. if an argument is named aString, I can safely assume that it will be String).
Thanks,
Peter
Hi!
I am now attending (very) academic conferences: http://vissoft.info and http://www.icsme.uni-bremen.de . It is fantastic to see and hear a lot about Pharo.
Thanks to all the researchers around here...
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am preparing my students to use moose. Here are a couple of legends I have added.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello Alexandre,
I have added moose-dev to this reply.
I do not at this time have any particular object models that I require
exploring. I have simply watched the videos on the browser, inspector,
etc.. Most anything Doru did. :)
I am wanting to put a GUI together for a database I am building for my
wife. At this point it is simple and will be all contained in the image.
This is a pretty conventional thing at this moment.
I have done nothing GUI oriented in Pharo and I need to learn those
skills. GT seems to be an awesome tool enabling very creative things.
At a later date I will have some more adventurous things to try. But my
wife's database is where I want to begin learning.
Thanks.
Jimmie
On 09/24/2015 01:11 PM, Alexandre Bergel wrote:
> Hi Jimmie,
>
> Question about GT should be sent to the moose mailing list.
> What do you have in mind with GT? Do you have an object model to explore?
>
> Cheers,
> Alexandre
>
>> On Sep 24, 2015, at 1:57 PM, Jimmie Houchin <jlhouchin(a)gmail.com> wrote:
>>
>> Hello,
>>
>> I have watched most all of the videos about GT.
>> I am interested in learning how to use the Glamorous Toolkit.
>> I am failing to find a beginning place for learning how to use and program GT.
>>
>> I am probably overlooking it some where.
>> I have downloaded the gtoolkit.image to begin learning.
>>
>> I am currently browsing code to learn what I can from there.
>>
>> Any advise on documentation or best way to proceed in learning GT greatly appreciated.
>>
>> Thanks.
>>
>> Jimmie
>>
Hi NG,
as I understood the FAMIX is the Metamodell behind MOOSE.
Is there any Documentation / Blog / HowTo where the API Model of FAMIX is
described?
There are some Sucess-Stories with Delphi, Cobol, Java and other Integration
of Models, maybe I missed something during my websearch ;-)
Best regards,
Damir
-----
--
Damir Majer
... be agile: www.majcon.de
--
View this message in context: http://forum.world.st/FAMIX-Documentation-tp4851789.html
Sent from the Moose mailing list archive at Nabble.com.
hi!
Why is there not a method atMethodScope?
Also, why is there not a atClassScope? Apparently this method is deprecated and one should use atTypeScope instead. However, a class define a type, but a type does not necessarily defines a class. It may define an interface. I have the impression that atTypeScope and atClassScope are both relevant. We could even introduce atInterfaceScope.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi everyone,
I guess because of a rapid evolution some parts of Roassal are weird. For example RTAbstractLine>>#updateFor:trachelShape: implements the shape drawing, so theoretically RTLine has to only override #trachelShapeClass to return TRLine. Instead RTLine overrides #trachelShapeFor: and does it incorrectly, because width cannot be used as a block but only as a number.
We have to handle this somehow, because 1) RTLine works incorrectly. 2) RTLine ignores the implementation strategy coded into RTAbstractLine.
Uko
