When the server is starting, stopping, etc, the icon changes between three "starting" icons, or three "stopping" icons, and the text varies between "Starting" and "Starting..." so it looks like something is happening.
<br><br>Anyway, as I said a few times, the big problem now is that my API just isn't set up for the extensions to be children of multiple servers. They're meant to be stand-alone objects that interact with servers. To stick them all into one would require re-writing the UI.. . and while it's not perfect, I think it's mostly functional for now ;)
<br><br>Anyway, I'm going to bed. It's been nice having you tear my code to shreds, Max... Look forward to it more in the future of course. <br><br>... Bastard. ;) <br><br>- Rob <br><br><div><span class="gmail_quote">On 11/14/06,
<b class="gmail_sendername">Max Rydahl Andersen</b> <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Why not just have an icon next to Server 1 that just signals stopped,<br>starting, started, stopping ?<br><br>What is that "nifty little animation" you mention ?<br><br>/max<br><br>> Server 1<br>> | - State: Started
<br>> | - Modules<br>> | - Event Log<br>> | - Descriptor XPaths<br>> | - blah blah blah<br>> Server 2<br>> | - State: Stopped<br>> | - Modules<br>> | - blah blah<br>> Server 3<br>> | - State: Starting
<br>> | - et etc etc<br><br><br>> Clearly this isn't optimal to quickly see which servers are started or<br>> stopped.<br>><br>> And finally, my server view extension API was written to accept a<br>> changing
<br>> input for the second viewer. It was not written to be a child of several<br>> different elements, but rather to be stand-alone elements with a changing<br>> input.<br>><br>> Hopefully this gives you some insight into what was going through my tiny
<br>> programmer mind.<br>><br>> - Rob<br>><br>> On 11/13/06, Max Rydahl Andersen <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:<br>>><br>>> On Mon, 13 Nov 2006 19:09:40 +0100, Rob Stryker <
<a href="mailto:rob.stryker@jboss.com">rob.stryker@jboss.com</a>><br>>> wrote:<br>>><br>>> > Because I was told much earlier that two views is crap, one is ideal.<br>>> > Users<br>>> > dont want tons of views opened to do somethign that was previously
<br>>> > controlled by a launch configuration.<br>>><br>>> the two views argument i understand...so why not just have one tree ?<br>>><br>>> I don't understand your launch configuration point is for ? We still
<br>>> have that...<br>>><br>>> /max<br>>><br>>> ><br>>> > On 11/13/06, Max Rydahl Andersen <<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>> wrote:<br>>> >>
<br>>> >> >> #1<br>>> >> >> Eclipse WTP has this notion of "Adding an applicaiton" to a<br>>> server.<br>>> >> Does<br>>> >> >> this also automatically
<br>>> >> >> add source lookup to that server ?<br>>> >> ><br>>> >> ><br>>> >> > AFAIK no.. but this is something that might be possible to code in<br>>> >> > ourselves
<br>>> >> > for our adapter (Rob would know for sure)<br>>> >><br>>> >> If not, how do they handle the "disable breakpoints" on server<br>>> feature<br>>> >> if
<br>>> >> they don't somehow get info about the source ?<br>>> >> (look in the wtp server preferences)<br>>> >><br>>> >> > #2<br>>> >> >> We have this splitted jbosserver view with what looks to me a
<br>>> >> filtered<br>>> >> >> WTP<br>>> >> >> server view and specific jboss bottm part, correct ?<br>>> >> >> Why is there both a mix of jboss inc servers and jboss wtp servers
<br>>> >> >> visible<br>>> >> >> in that one ?<br>>> >> ><br>>> >> ><br>>> >> > Well IMO this should be JBoss servers only as it is the "JBoss
<br>>> Server<br>>> >> > View"<br>>> >> > ..<br>>> >><br>>> >> Why not just reuse the existing WTP view and have the jboss specific<br>>> >> things in another view ?
<br>>> >> (just curious)<br>>> >><br>>> >> --<br>>> >> --<br>>> >> Max Rydahl Andersen<br>>> >> callto://max.rydahl.andersen<br>>> >><br>
>> >> Hibernate<br>>> >> <a href="mailto:max@hibernate.org">max@hibernate.org</a><br>>> >> <a href="http://hibernate.org">http://hibernate.org</a><br>>> >><br>>> >> JBoss a division of Red Hat
<br>>> >> <a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a><br>>> >> _______________________________________________<br>>> >> jbosside-dev mailing list<br>>> >>
<a href="mailto:jbosside-dev@lists.jboss.org">jbosside-dev@lists.jboss.org</a><br>>> >> <a href="https://lists.jboss.org/mailman/listinfo/jbosside-dev">https://lists.jboss.org/mailman/listinfo/jbosside-dev</a>
<br>>> >><br>>><br>>><br>>><br>>> --<br>>> --<br>>> Max Rydahl Andersen<br>>> callto://max.rydahl.andersen<br>>><br>>> Hibernate<br>>> <a href="mailto:max@hibernate.org">
max@hibernate.org</a><br>>> <a href="http://hibernate.org">http://hibernate.org</a><br>>><br>>> JBoss a division of Red Hat<br>>> <a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a><br>
>><br><br><br><br>--<br>--<br>Max Rydahl Andersen<br>callto://max.rydahl.andersen<br><br>Hibernate<br><a href="mailto:max@hibernate.org">max@hibernate.org</a><br><a href="http://hibernate.org">http://hibernate.org</a>
<br><br>JBoss a division of Red Hat<br><a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a><br></blockquote></div><br>