This example produce a bug dnu.
view := RTView new.
el := (RTBox new size: 20) elementOn: #symbol.
el @ RTPopup.
view add: el.
view open
--
Cheers,
Leo Perard
University of Lille 1
Hi,
Here is our submission for the ESUG Innovation Awards:
Title: GT Inspector
Submitter: Andrei Chis, Tudor Girba, Alex Syrel
Smalltalk Dialect: Pharo
Affiliation: University of Bern, tudorgirba.com
Country: Switzerland
Website: http://gt.moosetechnology.org
Trailer: http://vimeo.com/103463364
Keywords: Pharo, IDE, Moose, Visualization
Licence: MIT
Cheers,
The Glamorous Team
On Thu, Aug 14, 2014 at 1:24 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr
> wrote:
> Hi smalltalkers
>
> for the awards it seems that the registration server has still a problem.
> I suggest that you prepare your video and that you send a title and a
> little description of your project
> as a reply to this mail. We will manage it differently but we will do this
> great competition.
>
> Stef
> _______________________________________________
> Esug-list mailing list
> Esug-list(a)lists.esug.org
> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
>
--
www.tudorgirba.com
"Every thing has its own flow"
Good evening,
I have just pushed a new version of the FamixGenerator tool to my website.
So if you want to give it a try:
http://www.sharpmetrics.net/index.php/famix-generator
I have added a couple of features, like
* export of method invocations for FAMIX 3.0 models
* export of local variable and parameter access.
* several bug fixes
* and last but not least: export of generated C#-like code, which can be "attached" inside MOOSE
(more is written in the readme file inside the zip file.)
The tools does still export Famix 2 and 3.0 models, but currently I am struggling with the Famix 2.1 models for CodeCity. I think this relates to "analysis" and export of generic classes and generic type instances. This feature is not yet complete, so this might be the reason. I will investigate that issue in the next weeks.
If you want to view a city inside MOOSE, you can try the following script (if you have the new CodeCity for MOOSE installed):
| models builder |
models := MooseModel root allModels.
builder := CCBuilder new.
models notEmpty
ifTrue: [
| packages classes classNormalizer packageNormalizer |
builder packingLayout.
packages := models first allModelNamespaces.
classes := packages flatCollect: #classes.
packageNormalizer := CCColorNormalizer new
low: (Color gray: 0.6);
high: (Color gray: 0.95);
transformation: #numberOfClasses;
population: packages.
builder shapeBuilder platform color: packageNormalizer.
builder nodes: packages.
classNormalizer := CCColorNormalizer new
low: (Color gray: 0.25);
high: Color blue;
transformation: #weightedMethodCount;
population: classes.
builder shapeBuilder box
color: classNormalizer;
height: #numberOfMethods;
width: #numberOfAttributes;
depth: #numberOfAttributes.
builder nodes: classes.
builder nest: packages node: #yourself in: #parentScope.
builder nest: classes node: #yourself in: #namespaceScope ].
builder open
As you can see this script uses Famixnamespaces ('allModelNamespaces' and 'namespaceScope'). This is because the FamixGenerator currently does not export FamixPackages. This is also on my agenda...
Good night and take care,
Thomas
Hi!
I am thinking about extending FAMIXClass with the following:
withAllSuperclasses
^ self superclassHierarchyGroup
isPharoTest
^ self superclassHierarchyGroup anySatisfy: [ :c | c name = 'TestCase’ ]
Does this makes sense?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Thanks to both :-)
Daniel: Contributions from you will be certainly very welcome :-) But watch out, to be able to remote control the EV3 you also need a WiFi key, specifically the Netgear N150 (WNA1100 chipset). Only that one works, and they are getting harder to find these days :-(
On Aug 14, 2014, at 11:03 PM, Lemuus <lemuus(a)gmail.com> wrote:
> Awesome!!! now I really need to get a Lego Mindstorms EV3 :)
>
>
> On Thu, Aug 14, 2014 at 2:50 PM, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote:
> Great Johan! Congrats for both of you :)
>
>
> 2014-08-14 22:37 GMT+02:00 Johan Fabry <jfabry(a)dcc.uchile.cl>:
>
>
> Aargh, copy-paste error. The Lego robot example is on Instagram of course :-)
>
> http://instagram.com/p/pEhm0Oj837/
>
>
> On Aug 14, 2014, at 4:28 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
>
> > Hi all,
> >
> > it’s with great joy that I can announce the project that my PhD student Miguel and I have been working on recently: Live Robot Programming, or LRP for short.
> >
> > LRP is a live programming language designed for the creation of the behavior layer of robots. It is fundamentally a nested state machine language built with robotics applications in mind, but it is not bound to a specific robot middleware, API or OS. Have a look at one minute of LRP programming to get an idea of what it is like: http://youtu.be/4Ma8ZapBUqA
> >
> > Live programming is fun, and live robot programming even more so, as it brings all the advantages of live programming to programming a robot. You get direct manipulation of a running robot, and that’s just cool beyond words. As an example of LRP on a robot, this guy was programmed in LRP: http://youtu.be/4Ma8ZapBUqA Note that you can use LRP ‘just’ for live programming nested state machines as well.
> >
> > More information on LRP is available on its website: http://pleiad.cl/LRP where you can also find download instructions.
> >
> > LRP is implemented in Pharo, and uses Roassal2 for the visualization of its state machines. We currently can steer the Lego Mindstorms EV3 and ROS robots, thanks to a small layer on top of the cool Pharo support that Jannik, Luc, Santiago and Noury are implementing at Douai. I am going to look into support for the Parrot AR.Drone 2.0esug in a few weeks.
> >
> > Miguel will be at ESUG next week (I cannot make it), and has a talk at the IWST workshop about LRP, in the morning session. I am sure that he will also be happy to give demos of LRP if you ask him to (but sadly without a robot).
> >
> > All feedback is welcome, and … have fun!
> >
> > ---> Save our in-boxes! http://emailcharter.org <---
> >
> > Johan Fabry - http://pleiad.cl/~jfabry
> > PLEIAD lab - Computer Science Department (DCC) - University of Chile
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry - http://pleiad.cl/~jfabry
> PLEIAD lab - Computer Science Department (DCC) - University of Chile
>
>
>
>
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
Hi all,
it’s with great joy that I can announce the project that my PhD student Miguel and I have been working on recently: Live Robot Programming, or LRP for short.
LRP is a live programming language designed for the creation of the behavior layer of robots. It is fundamentally a nested state machine language built with robotics applications in mind, but it is not bound to a specific robot middleware, API or OS. Have a look at one minute of LRP programming to get an idea of what it is like: http://youtu.be/4Ma8ZapBUqA
Live programming is fun, and live robot programming even more so, as it brings all the advantages of live programming to programming a robot. You get direct manipulation of a running robot, and that’s just cool beyond words. As an example of LRP on a robot, this guy was programmed in LRP: http://youtu.be/4Ma8ZapBUqA Note that you can use LRP ‘just’ for live programming nested state machines as well.
More information on LRP is available on its website: http://pleiad.cl/LRP where you can also find download instructions.
LRP is implemented in Pharo, and uses Roassal2 for the visualization of its state machines. We currently can steer the Lego Mindstorms EV3 and ROS robots, thanks to a small layer on top of the cool Pharo support that Jannik, Luc, Santiago and Noury are implementing at Douai. I am going to look into support for the Parrot AR.Drone 2.0esug in a few weeks.
Miguel will be at ESUG next week (I cannot make it), and has a talk at the IWST workshop about LRP, in the morning session. I am sure that he will also be happy to give demos of LRP if you ask him to (but sadly without a robot).
All feedback is welcome, and … have fun!
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
