| Re: [ptp-dev] Problems trying to create resource manager using XML framework |
So here they are.
The XML now specifies at the top level of the LaunchTab 0:unbounded "dynamic" controllers, and 0:1 "import" controller. These are heavier-weight than the simple widget nesting I suggested, as each of these represents an entire dynamic launch tab instance and not just a TabFolder. But it shouldn't really cause problems. PE could probably add 10 or 12 without causing problems. But, as they say, the proof of the pudding is in the tasting.
As I said, in your case, you probably want to set all controllers to sharedEnvironment="true", which means that what is saved to the LaunchTabConfiguration is the union of all the tab controller's settings, whether currently visible or not. False indicates that you want only the visible subset (like a "select" view into the whole).
Al
----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> Dave,
>
> If you still prefer to put all the tabs at the top level the way they are in the current PE Launch Tab, I may be able to make the changes to allow this.
>
> You would probably want to give them all shareEnvironment="true" in this case. Let me see how much work it would entail making these changes (I don't think it is as bad as I originally thought).
>
> Al
> ----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> > My last message before signing off for the evening.
> >
> > As far as I can tell, there is something wrong with the way the RM wizard is doing things. If I go to preferences, choose services, and then select the launch service and edit there, I can switch between various remote services and connection names. In the ResourceManager configuration wizard, however, you seem unable to change them.
> >
> > Al
> >
> >
> > ----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> > > Modified browse button widgets:
> > > 1. button now has default layout, text gets style and layout defined in XML
> > > 2. text can be editable
> > > 3. text can contain URI or path (two types of browse buttons).
> > >
> > > Added addition error logging to XML Validation to show line and column, e.g.:
> > >
> > > !ENTRY org.eclipse.ptp.rm.jaxb.core 4 4 2011-05-05 00:39:46.553
> > > !MESSAGE Public ID: null
> > > System ID: null
> > > Line number: 59
> > > Column number: 16
> > > Message: cvc-complex-type.2.4.a: Invalid content was found starting with element 'layout'. One of '{"http://org.eclipse.ptp/rm":tab-folder, "http://org.eclipse.ptp/rm":composite, "http://org.eclipse.ptp/rm":widget, "http://org.eclipse.ptp/rm":viewer}' is expected.
> > >
> > > You'll see this in the error log preceding the actual thrown SAXParseException.
> > >
> > > I'm still working on the configuration issue. These fixes have been checked in.
> > >
> > > Al
> > >
> > >
> > >
> > > ----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> > > > Dave,
> > > >
> > > > The bug does not lie in the RM implementation or the browse button per se; it seems to have to do with the configuration wizard. If you choose edit after the initial connection setup, the new connection does not seem to get set.
> > > >
> > > > I started with a fresh configuration, and was able to do remote browse with the browse button, but then I stopped the RM and edited its connection to local. I then rebooted and returned to the browse button, but still got the remote connection. (remoteBrowse is something of a misnomer, here. The "browseLocal" is filesystem; the browseRemote is URI-based, so if your remote connection is identical to local, you should be browsing the local system; I think I'll rename the latter to browseUri) Anyway, I have to see what exactly is happening there; we've had a few issues with configuration setup (which has become something of a complication because of the control/monitor separation).
> > > >
> > > > However, I did notice a couple of usability issues with the browse button:
> > > >
> > > > a) I had set the layout of the button to match that of the text, which is no correct; the button will now ise the default layout data for a button (and will occupy only one column), so the layout specification on this widget is specifically for the text box.
> > > >
> > > > b) Because I set the text box to read-only, you can't really scroll using the cursor inside it, so the path may not be entirely readable. What I will do is open this up to being editable as an option. You can always set the style of the text box to H_SCROLL, but that requires it to be a little taller vertically, which may not work in a layout. At any rate, I should probably provide the editable option here anyway.
> > > >
> > > > c) The path for the remote browse is a URI, so you'll get 'remotetools//EMBER/u/ac/arossi', for example. Should this be just a path instead? Perhaps I should provide an option here as to which to return.
> > > >
> > > > I will make these changes and try to chase down the configuration issue.
> > > >
> > > > Here we go ...
> > > >
> > > > Al
> > > >
> > > >
> > > >
> > > > ----- Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
> > > > >
> > > > > > Dave, I'm not quite sure what you are describing here. Did you provide an executable path widget in the ResourcesTab? That is, you configured one using the browse button widget in the XML? If so, for remote path browsing you need to use the remote-path browse button (there are two different browse widgets). Is that what you mean, or is it something else?
> > > > >
> > > > > OK, seems to be a bug here with the remote browse ... I'll look at it.
> > > > _______________________________________________
> > > > 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
> >
>
Attachment:
tab2.png
Description: PNG image
Attachment:
tab1.png
Description: PNG image
Attachment:
tab3.png
Description: PNG image
