[forge-dev] WindowBlu for Forge

Mike Brock cbrock at redhat.com
Wed Nov 16 19:30:26 EST 2011


I spoke to Lincoln about this, and I'm working on coming up with a way to make this "safer" for IDE integration -- ie. plugins like this can refuse to load if they're in an unsuitable environment. 

On Nov 16, 2011, at 4:24 PM, Max Rydahl Andersen wrote:

> It's cool - but I was really hoping such things as direct/raw text control/buffer output would not be exposed or at least not be the norm that plugins uses/depends on it.
> 
> It still annoys me to see forge plugins that does shell.print(Color.RED, "blah blah") instead of shell.error("blah blah")
> 
> /max
> 
> On Nov 16, 2011, at 17:04, Mike Brock wrote:
> 
>> Internally, there is a new concept known as a BufferManager. Essentially the idea is that a plugin can create it's own sub-buffer to the main shell buffer. 
>> 
>> When WindowBlu loads, it registers its own buffer with the Shell, taking control of the display buffer so it can intercept and translate all the ANSI -- as well as pre-buffer repainting of the titlebar to minimize flickering, etc.  
>> 
>> Mike. 
>> 
>> On Nov 16, 2011, at 9:03 AM, Koen Aers wrote:
>> 
>>> Yeah, the windowblu command shuts down Forge Tools. I'll take a closer look at what can be done to support it.
>>> 
>>> Cheers,
>>> Koen
>>> 
>>> On Wed, Nov 16, 2011 at 1:49 AM, Lincoln Baxter, III <lincolnbaxter at gmail.com> wrote:
>>> I think you forgot the video :) this is awesome!
>>> 
>>> http://www.youtube.com/watch?v=gQp_N-gGDzk
>>> 
>>> On Wed, Nov 16, 2011 at 1:09 AM, Mike Brock <cbrock at redhat.com> wrote:
>>> So, I've been back working on Forge Core -- scripting and internal API improvements. One thing that upset me was that Forge lacked a sub-buffering facility for console output, so you could intercept console output and do fun stuff like add a status bar. Well, Forge has this limitation no longer -- at least not in my branch (https://github.com/mikebrock/core)
>>> 
>>> Haven't pushed the changes upstream, mainly because I don't know if they break JBoss Tools or not -- pretty sure they don't break anything else. 
>>> 
>>> Anyways, here's my first demo plugin that takes advantage of these new features in the shell API: https://github.com/mikebrock/core
>>> 
>>> Mike.
>>> 
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Lincoln Baxter, III
>>> http://ocpsoft.com
>>> http://scrumshark.com
>>> "Keep it Simple"
>>> 
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>> 
>>> 
>>> _______________________________________________
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> 
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
> /max
> http://about.me/maxandersen
> 
> 
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev




More information about the forge-dev mailing list