Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 743 by [hidden email]: This is strange that we have to  
systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743

a typical sript to import a model is


        MooseSqueakClassPackageImporterTask new
                importerClass: SmalltalkImporter;
                model: model;
                addFromPackageNamed: #'Moose-TestResources-LAN';
                run;
                yourself

But it is rare that we should change the importerClass (it was useful when  
we had to import FAMIX2 and FAMIX3 side by side).
I suggest that we introduce a default and that we initialize the  
importerClass to SmalltalkImporter.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

moose-technology

Comment #1 on issue 743 by [hidden email]: This is strange that we  
have to systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743

The default was there and we put it at the right place. So yes most of the  
importerClass: can be removed from the expression as the one above.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

moose-technology
Updates:
        Labels: -Type-Defect Type-Enhancement Component-SmalltalkImporter

Comment #2 on issue 743 by [hidden email]: This is strange that we  
have to systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743

Does it mean that we can close the issue?

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

moose-technology
Updates:
        Status: Fixed

Comment #3 on issue 743 by [hidden email]: This is strange that we  
have to systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743

yes now fixed for me does not mean closed.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

moose-technology
Updates:
        Labels: Milestone-4.6

Comment #4 on issue 743 by [hidden email]: This is strange that we  
have to systematically specify the class of the importer
http://code.google.com/p/moose-technology/issues/detail?id=743

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev