[protege-discussion] Getting plugin code to run at Protege start-up time

[Daniel Holbert]

Yes, you're correct -- I'm using a static method to load the data.

I'll look into using a project plugin -- thanks for the suggestion! In 
the meantime, if anyone else has any other ideas, let me know.

Thanks,
~Daniel



Richard Dunlap wrote:
> If the delay occurs only the first time you display the widget, is it a
> correct inference that you're loading static data through a method that
> either is static or could be refactored into a static method?  If so,
> then you could try writing a project plugin to call the static method
> during project load.
> 
> <chuckle> If my inference is wrong, then I'll go sit in a corner and see
> what the Protege team comes up with. :-)
> 
> -- Richard Dunlap
> 
> Daniel Holbert wrote:
>  > Hi all,
>  >
>  > I'm developing a slot widget plugin that requires reading in some data
>  > files, which takes 10-15 seconds.   Right now, I've put the code for
>  > this in my widget's "initialize()" method, but I don't like this very
>  > much because it means the GUI hangs for 10-15 seconds the first time
>  > one of my widgets is displayed.
>  >
>  > Is it possible for me to run this code when Protege starts up, instead
>  > of in "initialize()"?  And if so, what's the best way to do this?
>  > (ideally staying within the plugin framework -- I'd rather not have to
>  > edit the Protege sources)
>  >
>  > Thanks!
>  > ~Daniel
>  > _______________________________________________
>  > protege-discussion mailing list
>  > protege-discussion at lists.stanford.edu
>  > https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>  >
>  > Instructions for unsubscribing: 
> http://protege.stanford.edu/doc/faq.html#01a.03
>  >
>  >
> 
> 
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
> 
> Instructions for unsubscribing: 
> http://protege.stanford.edu/doc/faq.html#01a.03
>