Can you dynamically change the propath with proLint?

Just like you can do with Progress. I work on lots of projects and this ability would be great.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jurjen's picture

re: can you dynamically change the propath with Prolint?

Hi Jay,

Sorry I am afraid I don't quite understand the question.
As far as I know, Progress does not have the concept of "project" although Eclipse/OEA has.

Prolint, just like the Progress compiler, works with the current state of the Progress session, e.g. the current Propath, current working directory, current database-connections and session start-up parameters. I suppose the specification of this state could be regarded as "project", and after you switch to a different project and run Prolint then Prolint will be using whatever the Propath happens to be at that time. You can't define "projects" in Prolint just like you can't define them in Progress, but you can define multiple Progress sessions with different parameters and run Prolint in their context.
But I probably just don't understand the question. Can you elaborate a little?

Thanks,
Jurjen


I just added a button to

I just added a button to desktop.w called Propath. When the user presses this button, the code executes RUN protools/_propath.r. That's what I meant. I think this would be a nice feature. In my case because I may have multiple projects active and would like a fairly easy way to change the propath while I'm working with prolint and my projects.


propath button

I think that's a good addition to the desktop, as would be a button to connect to databases. Isn't there one of those on protools too?


Yes there is. But there are

Yes there is. But there are also a few of other features that might be nice. Maybe we should just add a button to Protools or some menu option? Personally, being able to change the propath has been a great improvement for my development needs.


protools button

That would be one way to go. The other is to remember that you can launch prolint from protools. That leaves protools running. I'd actually suggest doing it that way, add prolint to the protools button. There are instructions there on how to do that. Actually, all you have to do is click the 'add to protools' button at the bottom of the desktop. Then change the way you come into prolint to go to protools first and click the prolint button.