FAQ for DevTools

  1. Which systems are the DevTools currently compatible with?
  2. Will the DevTools be ported to VisualWorks 7i?
  3. Will the DevTools be ported to the next version of ControlWorks?
  4. Will the DevTools be ported to VisualWorks 3.x with Envy or 5i with Envy?
  5. Will the DevTools be ported to any other Smalltalk environments?
  6. Can I port the DevTools to another Smalltalk environment on my own?
  7. Are any existing methods modified by the DevTools?
  8. What does it mean if I get an error like: "Cannot complete the load because [Class name and date here] in [Application name here] does not exist in the library. ..."?

Q: Which systems are the DevTools currently compatible with?

Q: Will the DevTools be ported to VisualWorks 7i?

I would like to do this if I have time. However, thanks to the programmers at Cincom, their helpers, and the various goodies they include, some of the things I’ve included in the DevTools are already in VisualWorks 7i.

Q: Will the DevTools be ported to the next version of ControlWORKS?

If I continue to be an employee at Objective Solutions, and they continue to do ControlWORKS consulting, then yes, I will port the code to the next version of Adventa Control Technologies’ ControlWORKS framework.

If your company uses ControlWORKS, makes hardware for the Semiconductor industry, or needs help with other software development projects, then please consider using Objective Solutions’ services.

Q: Will the DevTools be ported to VisualWorks 3.x with Envy or 5i with Envy?

Currently, I don’t have access to copies of VisualWorks 3.x or 5i with Envy.

If you or your company use it, I'd be happy to try to port the DevTools, providing that there is a way for me to legally use one of your development images. If so, then please contact me.

Q: Will the DevTools be ported to any other Smalltalk environments?

Possibly, but I'm currently only familiar with the inner workings of VisualWorks, so porting to other environments has a lower priority.

Q: Can I port the DevTools to another Smalltalk environment on my own?

For your personal use, yes. Beyond that, please see information on how I want to exercise my copyrights.

You should also check out some of the provided porting tips.

Q: Are any existing methods modified by the DevTools?

Yes. For details, please see the following parts of the documentation and read the information about the destructive change notations:

Q: What does it mean if I get an error like: "Cannot complete the load because [Class name and date here] in [Application name here] does not exist in the library. ..."?

Editions and Versions pane pop-up menu. There are no new additions to this menu but a new feature has been added to the load menu item.First, check to make sure that the correct version of the DevTools has been downloaded.

If you have the correct version, it is possible that some of the names of the existing Applications do not have the expected name.

The DevTools modify code from several different companies and in an effort to protect their copyrights, I used the export changes... menu item from the Editions and Version pane pop-up menu in the Configuration Maps browser.

Applications that are brought into an Envy library after they were exported using the export changes... menu item, require that an Application with the same name as their "parent" Application exist in the new library.

If you still have problems loading the Configuration Maps, or you are trying to use the DevTools in an unsupported configuration, you might need to follow some of the porting tips.


[ < Modified Methods ] [ Copyright Preferences and Contact Info > ]

[ Main ] [ Table of Contents ] [ Contact info ] [ Index ]

[ Home ]

This work is licensed under a Creative Commons License.

Creative Commons License