Re: [ptp-dev] Problems trying to create resource manager using XML frame

[Dave Wootton <dwootton@xxxxxxxxxx>]

Al
I've been experimenting a bit more with
this and have been able to modify the XML config file so that the launch
tab so that it displays only the two PE settings I need to get started,
and also defined attributes that seem to save them in a run configuration.
I have a few questions

1) Is it possible to have an open ended
set of tabs in the resources pane? What I did in the existing PE resource
manager, and envisioned doing in this implementation, was to organize PE
options into logical group with each group getting its own tab. In this
implementation, it looks like I have a basic tab, an extended tab and then
a custom controller tab. In this model, it looks like I'm limited to a
single tabbed pane with a long (around 70) list of PE options or I have
to create a second tabbed pane with tabs inside the pane for the basic
and/or advanced mode tabs. I'm afraid it will be difficult to find a PE
option in a long list and I think the user will be confused to see tabs
within tabbed panes.
2) For PE, I can set options using either
command line flags to the POE command or environment variables. My existing
implementation uses environment variables. Is there a way that I can continue
to use environment variables where the plugin generates the proper export
commands to set the environment variables before invoking poe or do I have
to have a script which sets them then invokes the poe command?
Dave



From:      
 "Albert L. Rossi"
<arossi@xxxxxxxxxxxxx>
To:      
 Parallel Tools Platform
general developers <ptp-dev@xxxxxxxxxxx>
Date:      
 04/30/2011 09:11 PM
Subject:    
   Re: [ptp-dev]
Problems        trying      
 to        create    
   resource        manager
       using        XML
       framework
Sent by:    
   ptp-dev-bounces@xxxxxxxxxxx

---

Also done.

Al
----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> Great. I suggest removing it from the extension point if it's no longer
needed.
> 
> Greg
> 
> On Apr 30, 2011, at 7:28 PM, Albert L. Rossi wrote:
> 
> > Done.  The id is now totally arbitrary. -A;
> > 
> > ----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> >> Great, I'll take care of it.
> >> 
> >> Al
> >> ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> >>> Al,
> >>> 
> >>> I had a quick look and I don't think there is any need
to change RMProviderContributor. I think you just need to modify JAXBRMConfigurationSelectionFactory
so that it ignores the id altogether. The id in the org.eclipse.ptp.rm.jaxb.core.JAXBResourceManagerConfigurations
extension point is not used by anything in RMProviderContributor. fRMJAXBResourceManagers
map can just be reduced to Map<String, URL>.
> >>> 
> >>> Greg
> >>> 
> >>> On Apr 30, 2011, at 3:38 PM, Albert L. Rossi wrote:
> >>> 
> >>>> Greg, Dave
> >>>> 
> >>>> This is a follow-up to the discussion about the "id"
attribute on the org.eclipse.ptp.rm.jaxb.core.JAXBResourceManagerConfigurations
extension point.  That attribute points to the _selection factory_
(org.eclipse.ptp.ui.wizards.RMConfigurationSelectionFactory).  
> >>>> 
> >>>> If you change it, you have to implement a new selection
factory as well.  But there is no need, because 
> >>>> 
> >>>> org.eclipse.ptp.rm.jaxb.ui.wizards.JAXBRMConfigurationSelectionFactory
> >>>> 
> >>>> is written to handle all contributions to this extension
point.  It's id is "org.eclipse.ptp.rm.jaxb.JAXBServiceProvider"
> >>>> 
> >>>> At this point I'm not sure what the correct thing
to do is; the id may be redundant, or it could be useful if a special corner-case
configuration needs to be created (but that sort of defeats the purpose
of this undertaking);  hence I would be inclined to remove it from
the extension point.  However, that will inevitably entail changes
to 
> >>>> 
> >>>> org.eclipse.ptp.ui.wizards.RMProviderContributor,
> >>>> 
> >>>> private static void getRMConfigurationSelectionFactories()
[ll. 58ff.].
> >>>> 
> >>>> This is basically your domain Greg.  Let me
know what to do (I know you are currently overloaded).
> >>>> 
> >>>> For the moment, Dave, continue to set that id to
"org.eclipse.ptp.rm.jaxb.JAXBServiceProvider" for all contributors
to the extension point.
> >>>> 
> >>>> Al
> >>>> _______________________________________________
> >>>> ptp-dev mailing list
> >>>> ptp-dev@xxxxxxxxxxx
> >>>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
> >>> 
> >>> _______________________________________________
> >>> ptp-dev mailing list
> >>> ptp-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
> >>> 
> >> 
> >> _______________________________________________
> >> ptp-dev mailing list
> >> ptp-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/ptp-dev
> >> 
> > 
> > _______________________________________________
> > ptp-dev mailing list
> > ptp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ptp-dev
> 
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
> 

_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev