Thanks Uwe. I'm going to proceed with my "current user" functionality.
This will be included in a class that extends the JUMP AbstractPlugIn
class, so the functionality will be available to other plug-in
developers if they so choose.

I'll be trying to modify the Super Select tool so that the
configurations can be stored separately for different users using this
scenario. Look for it in an upcoming release of the plug-in.

The Sunburned Surveyor

On 11/2/07, Uwe Dalluege <[EMAIL PROTECTED]> wrote:
> Hi Landon,
>
> if you are teaching OpenJUMP you have one installation
> and lots of students using OpenJUMP over a network.
> It would be very nice to have a plugIn
> to configure the personal settings.
>
> Regards
>
> Uwe
>
> Sunburned Surveyor schrieb:
> > I'd like to know if anyone is using OpenJUMP in a situation where more
> > than one person would using an OpenJUMP installation on a single
> > computer. This might happen if OpenJUMP were being accessed over a
> > network, or if more than one person accessed a computer with OpenJUMP
> > installed to perform GIS tasks.
> >
> > I'd like to know how common this scenario is because I am trying to
> > determine how useful it would be to design plug-ins for OpenJUMP that
> > maintain "current user information". This functionality would allow
> > you to store personalized tool configurations for each user and would
> > also be used to identify the user/organizatoin for logging and
> > metadata tools. (I don't intend to use the "current user information"
> > functionality to control or restrict access to data or functions in
> > OpenJUMP. That is a whole other can of worms and not my goal in this
> > case.)
> >
> > Thanks,
> >
> > The Sunburned Surveyor
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Jump-pilot-devel mailing list
> > Jump-pilot-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to