On Thu, Mar 12, 2015 at 2:08 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
wrote:
I was thinking that the strategy to detect classes
(Section III.A from the
paper) could be implemented in Moose, on the class FAMIXJSObject ?
The strategy to detect classes is implemented in Pharo. It reads the
FAMIX-JS meta model and creates instances of FAMIXClass, FAMIXInheritance,
FAMIXMethod and FAMIXAttributes.
Try this with the "js model" you already have:
js1 := JSClassFinder new.
js1 famixJSModel: (js model).
js1 searchJSClasses.
js1 classModel.
The link are about the nesting I think using
#belongTo
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mar 11, 2015, at 6:42 PM, Nicolas Anquetil <nicolas.anquetil(a)inria.fr>
wrote:
you mean these are classes extracted from the JS code?
if so, what are the (few) links?
nicolas
On 11/03/2015 18:24, Alexandre Bergel wrote:
Hi Again :-)
So, I compiled a fraction of the BBC News JavaScript application. And I
started to visualize their JavaScript application.
Here are my two tries:
<Mail Attachment.png><Mail Attachment.png>
So, it seems to work well :-) Happy I am :-)
Cheers,
Alexandre
[ NB: I put the moose mailing list in copy since this may have a great
interest in the community ]
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.