Smalltalk › Instantiations

Errors using WindowBuilder Translation Toolkit

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Carl Gundel-2

Errors using WindowBuilder Translation Toolkit

I ran the scripts to export my VSE application from our Team/V repository. When I try to import into VAST using the Translation Toolkit I get the following errors.

One or more classes is referenced improperly in the imported files.

Please correct this problem before proceeding.

*** The class 'WPARStuffApp' is referenced but never defined. An input file may be missing.

*** The class 'WPDatabaseApp' is referenced but never defined. An input file may be missing.

*** The class 'WPMailApp' is referenced but never defined. An input file may be missing.

*** The class 'WPUnprocessedApp' is referenced but never defined. An input file may be missing.

*** The class 'WPUtilityApp' is referenced but never defined. An input file may be missing.

The classes it refers to (actually Stuff, Database, Mail, Unprocessed, and Utility before a pre and post identifier are added) are not classes at all, but packages in our application. Not sure why it thinks they are classes.

Any ideas?

Thanks,

-Carl

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Thomas Koschate-2

Re: Errors using WindowBuilder Translation Toolkit

On Tuesday, February 5, 2013 10:04:45 AM UTC-5, libertybasic wrote:

The classes it refers to (actually Stuff, Database, Mail, Unprocessed, and Utility before a pre and post identifier are added) are not classes at all, but packages in our application. Not sure why it thinks they are classes.

In ENVY, VA Smalltalk's code repository, every application (package to you) includes a class subclassed from Application that is the name of the application.

I've never used the Translation kit, but I'd suspect that you're either importing files in the wrong order, or you need to have defined the applications before importing the classes that will reside in them.

Tom

John O'Keefe-3

Re: Errors using WindowBuilder Translation Toolkit

In reply to this post by Carl Gundel-2

Answered offline.

John

On Tuesday, February 5, 2013 10:04:45 AM UTC-5, libertybasic wrote:

I ran the scripts to export my VSE application from our Team/V repository. When I try to import into VAST using the Translation Toolkit I get the following errors.

One or more classes is referenced improperly in the imported files.

Please correct this problem before proceeding.

*** The class 'WPARStuffApp' is referenced but never defined. An input file may be missing.

*** The class 'WPDatabaseApp' is referenced but never defined. An input file may be missing.

*** The class 'WPMailApp' is referenced but never defined. An input file may be missing.

*** The class 'WPUnprocessedApp' is referenced but never defined. An input file may be missing.

*** The class 'WPUtilityApp' is referenced but never defined. An input file may be missing.

The classes it refers to (actually Stuff, Database, Mail, Unprocessed, and Utility before a pre and post identifier are added) are not classes at all, but packages in our application. Not sure why it thinks they are classes.

Any ideas?

Thanks,

-Carl