Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use JNIPort to connect to VerveineJ #482

Closed
seandenigris opened this issue Aug 3, 2015 · 5 comments
Closed

Use JNIPort to connect to VerveineJ #482

seandenigris opened this issue Aug 3, 2015 · 5 comments

Comments

@seandenigris
Copy link
Contributor

seandenigris commented Aug 3, 2015

Originally reported on Google Code with ID 482

It would be interesting to see if it is possible to access Verveine via JNIport instead
of  generating a MSE from verveine and then load it in moose

Reported by cy.delaunay on 2010-11-09 09:19:12

@seandenigris
Copy link
Contributor Author

seandenigris commented Aug 3, 2015

I tried to implement something: The idea was to access directly the famixRepository
generated by verveine, instead of exporting it to mse and then re-import it in pharo.
Is that the good idea ?
But doing that seems to be very slow (But I suspect my image/machine to be very slow
a this moment. Should be better with a cog vm. For example, Access any parameter of
a FamixEntity (a Java object), took more than one second. So I guess it was faster
to export the mse and then re-import it).
Another idea would be to 're-implement' verveine in smalltalk and access the AST using
JNIPort.

You can have a look at it by just loading:

Gofer new
     url: www.squeaksource.com;
     package: 'JNIPortExample';
    load

It should work in a 1.1 image, but if not , maybe try a second time :) (I don't know
why but sometimes it loads well, sometimes not).

Then there will be an example in the class side of ImportFromVerveineExample (you have
to set your own path to the verveines librairies). Open a transcript, and the example
should display all the entities of the famixRepository.

Reported by cy.delaunay on 2010-11-09 09:33:34

@seandenigris
Copy link
Contributor Author

seandenigris commented Aug 3, 2015

you should now use that:

Gofer new
     url: 'www.squeaksource.com/DelaunayTmpStuffs';
     package: 'JNIPort-Initialization';
    load.

Gofer new
     url: 'www.squeaksource.com/DelaunayTmpStuffs';
     package: 'JNIPortExample';
    load.

The initialization part still has to be fixed, sometimes it works, sometimes not. 

Reported by cy.delaunay on 2010-12-07 14:29:22

@seandenigris
Copy link
Contributor Author

seandenigris commented Aug 3, 2015

Is there any progress on this issue?

Reported by tudor.girba on 2011-07-24 14:58:07

  • Labels added: Type-Enhancement
  • Labels removed: Type-Defect

@seandenigris
Copy link
Contributor Author

seandenigris commented Aug 3, 2015

No, at least not from me :)

Reported by cy.delaunay on 2011-07-26 08:14:42

@seandenigris
Copy link
Contributor Author

seandenigris commented Aug 3, 2015

Is anyone interested in picking this one up? It would definitely provide high value
for Moose.

Reported by tudor@tudorgirba.com on 2013-06-30 20:31:55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants