GWT interface

[william(at)elan.net]

I guess if it was said AJAX it would have been easier to understand
what is being proposed. Now, GWT is nice - I've not seen it before
and worked with different AJAX toolkit (though my experience with
ajax is rather limited). But my general comment still remains -
many sysadmins will not want ajax as primary interface, they need
something solid that works in any browser even "crippled" one.

That is not to say that trying to do AJAX interface for nagios
is bad idea, if it is available and its good, some will no doubt
use it. Also while we're at the topic of more "active" nagios
interface, what for long time I thought would be nice to have is
window open up when alert comes in in similar way that gmail opens
up chat window for their web jabber client (btw, anyone know if
that jabber client is available in their ajax toolkit component?).
This maybe doable with just regular javascript though, I just did
not like current C cgi code that is difficult to add anything to.

On Tue, 3 Apr 2007, James Harr wrote:

> I think Tobias was referring to the client side (just the GWT stuff).
> If you're not familiar, GWT is just Java compiled down to javascript
> (you don't get all of java, like JNI, AWT, or any of the IO stuff,
> which isn't really pertinent to web development anyway). It's what
> gmail is built on, iirc. All your java code ends up being a single .js
> file you load in your web page. The server side can be anything you
> want (php, python, perl, C), it just has to communicate with your
> webapp through something (I'm a fan of JSON, it's simple, and has
> libraries for pretty much every language). In production use, you
> don't have a JVM running anywhere. I'd personally sway away from using
> java on the server side too, it overly complicates things. A python or
> perl script that spits out nagios state info would be sufficient for
> the server side.
>
> Take a look at their "Kitchen Sink" example if you have a few minutes.
> The source code is almost stupidly easy to write.
> http://code.google.com/webtoolkit/
>
> On 4/3/07, william(at)elan.net <william at elan.net> wrote:
>>
>> I think we're better off having the interfce written in php or perl
>> or ruby[on rails] or python. And I speak as someone who can write in
>> Java as well, but I find that sys/net admins try to avoid using java
>> application server in their admin infrastracture, although larger
>> enteprises do like it, but then you really need a company behind it
>> to maintain.
>>
>> On Tue, 3 Apr 2007, Tobias Mucke wrote:
>>
>>> Hi,
>>>
>>> I am working right now at a Nagios webinterface. Project is called
>>> Nicaragua. Right now I am leaving the planning and technology preview
>>> phase and implementing first details in Java. Currently I am working
>>> alone at this project, but I have written a development handbook for
>>> Nicaragua which explains some details. Would be great if someone would
>>> join the team. Interested?
>>>
>>> Tobias

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV