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

Improve missing imports resolution #676

Open
onor13 opened this issue Aug 11, 2017 · 1 comment
Open

Improve missing imports resolution #676

onor13 opened this issue Aug 11, 2017 · 1 comment
Labels
Type: Enhancement A request for a change that is an enhancement

Comments

@onor13
Copy link

onor13 commented Aug 11, 2017

  1. Possibility to resolve missing imports from XML Catalog and not only an ontology file.
  2. Possibility to change the active catalog.
  3. Fix: the classes hierarchy was not reloaded when adding “Direct Imports” in “Imported Ontologies” window
@buergerj
Copy link

buergerj commented May 3, 2018

I second that issue and like to add: failed imports should be at least generate some kind of notice or warning at the GUI level.
This is currently not the case, but according to console output, Protégé is aware of failed imports ("Failed to load imported ontology at ...").
This pull request #734 would at least help by adding a warning symbol which calls attention when warnings in the Protégé log appear.

@matthewhorridge matthewhorridge added the Type: Enhancement A request for a change that is an enhancement label Jan 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement A request for a change that is an enhancement
Projects
None yet
Development

No branches or pull requests

3 participants