Hmm, not able to access squeaksource. Are there dependencies that should move
to smalltalkhub or ss3 (like OSProcess)? July 15th Squeaksource will become static.
Stephan
This looks like really a fantastic job. I cannot wait to see the code :)
Doru
On Jul 4, 2013, at 3:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
> Hi!
>
> We are currently working on a Sunburst based on top of Roassal. Milton is doing a fantastic job!
> Here some early screenshots:
>
> <image copy 2.png><image copy.png><image.png>
>
>
> Milton & Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
--
www.tudorgirba.com
"If you can't say why something is relevant,
it probably isn't."
:)
I'm happy
With Athens a new space is opening :)
Now do you handle interaction?
Stef
On Jul 4, 2013, at 3:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
> Hi!
>
> We are currently working on a Sunburst based on top of Roassal. Milton is doing a fantastic job!
> Here some early screenshots:
>
> <image copy 2.png><image copy.png><image.png>
>
>
> Milton & Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
One good news never come alone :-)
We are working on a 3d version of Roassal. Here is a preliminary screenshot:
More to come soon!
Cheers,
Ronie, Milton, Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi
I have Roassal as speed with 30,000 elements as with 1,000 elements.
But still I have to udpate the view when resizing the window and
translating the view.
Does anyone know how to send the view an event when I resize the view ?
Regards
Mathieu
Hi,
The isPackage method is implemented only in FAMIXNamedEntity (and obviously in FAMIXPackage).
The isClass method is implemented only in FAMIXSourcedEntity (and obviously in FAMIXClass).
The isAttribute method is implemented only in FAMIXStructuralEntity (and obviously in FAMIXAttribute).
The isMethod method is not implemented…
Why not harmonizing this and defining all these methods in FAMIXEntity?
In fact, I am working with Nicolas Anquetil on the diff of models. I would like to create an Orion action for each change. Thus, if a class is added between version n and version n+1, I would like to instantiate an AddClass operator. And so on for each change. So I need to know the type of the FAMIXEntity on which the change occurred. Using these methods would be tidier than using isKindOf: method.
Please let me know if such implementations make sense for you or not.
Anne
Hi all,
I try to make sense of Petit Java and the discussions around it, because it makes sense to have a similar architecture for Petit Delphi. The Delphi syntax contains 141 rules, versus 137 rules in java. So we compare pretty closely. But when I try to read the petit java code, I notice some odd things, so maybe someone can tell me why things are as they are.
I thought AST meant we have an Abstract Syntax Tree. A syntax tree, that only contains the information needed. The way we do it on the Delphi side, is that only when we have a purpose for a certain AST Node we create it. On the detail level, we do not have many AST nodes yet, since we only generate FAMIX to the method level. And the number of AST nodes is growing fast. Why does the AST needs to stick to the java grammar as closely as possible?
When I look at the AST Node and at the places where they are created, they more look like grammar nodes than syntax nodes. I have a node called MethodDeclarationNode. But it is created in the rule "methodNotConstructorDeclaration" and when I look at the rule "methodDeclaration" I would expect to have 2 subclasses: a ConstructorDeclarationNode and a MethodNotConstructorDeclarationNode … but instead I have a subclass InterfaceMethodDeclarationNode. I thought FAMIX was meant for this and that is why we convert our AST into FAMIX as well …
In PetitJava there is a visitor for the AST. I do not see how this visitor helps. The AST is changing faster than the implementors of the visitor, not only because we are evolving Petit Java, but also because Java itself also evolves and will make changes to the language in the future. I see only a few possible implementors of this visitor.
And maybe some of the Petit Java developers want to take a look at the Petit Delphi code. Because I am sure we did things good and also some stupid things, so please help us find the stupid things and copy the good things! I know I try to copy the good ideas from petit java.
Regards,
Diego
