[jboss-as7-dev] birth of "console ui" in eclipse

[Max Andersen]

Embedding webui is crapy. 

Which is why we link
To the console and show in browser externally or embedded. 

We deliberately try not to depend
Nor duplicate the console. 

The "tree" browser is simply just there since its trivial to do and been asked for. 

Afaik there is no tree browser in console and even if there is then its a webapp with no way to integrate with besides viewing. 

Btw. Latest as7.1 has weird scrolling behavior when embedded in eclipse. Just noticed that :(

/max (sent from my phone)


On 10/02/2012, at 20.09, Heiko Braun <hbraun at redhat.com> wrote:

> 
> 
> IMO it's pretty lame to work on three different, redundant efforts:
> 
> - the web UI
> - the CLI UI
> - the eclipse UI
> 
> I can somehow understand the CLI UI, but i think the best approach for eclipse would be to embed the web UI. Maybe with a different layout. Something that fits better into the overall frame. But technically it should be possible to reuse the web UI.
> 
> I keep hearing the term "like JMX console" over and over again. If  you think that power users require something more generic then the full blown web UI, why not build it within the console itself? And then use it embedded within eclipse? 
> 
> /Ike
> 
> On Feb 10, 2012, at 7:54 PM, Max Rydahl Andersen wrote:
> 
>> 
>> For now we just added the "raw" view but would like to either make this more "beginner user-friendly" or move it over to something like the full blown JMX console we got
>> for "older" AS's where you can do edit operations etc. 
>> 
>> but for now we just do this "baby" raw console as a read only operation and see where it takes us.
>> 
>> /max
>> 
>> On Feb 10, 2012, at 19:08, Rob Cernich wrote:
>> 
>>>> Looks a lot like the CLI GUI. We should collaborate.
>>> 
>>> It was certainly inspired by the CLI GUI, though I haven't had a chance to look at the code yet.  The UI piece is probably going to be specific to each (SWT on the Eclipse side, I assume Swing on the CLI side).  The model code could be shared, but there's not much there on the Eclipse side:
>>> * a resource node - represents an addressable resource (e.g. /subsystem=switchyard)
>>> * an attributes node - container for attributes defined by a resource
>>> * an attribute node - an attribute value associated with a resource
>>> * a category node - represents a "child-type" defined by a resource (e.g. subsystem).
>>> 
>>> The model is built using read-resource-description, read-children-names and read-resource, depending on the node type.
>>> 
>>> For me, I was just looking to make sure I had access to the management interface from within Eclipse so I could add some SwitchYard specific capabilities to the Servers View.  The "baby console" was just a POC demonstrating the possibilities.
>>> 
>>> Best,
>>> Rob
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>> 
>> 
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>