idea: gecko-based wave client.

1 view
Skip to first unread message

qMax

unread,
Aug 17, 2009, 2:47:54 AM8/17/09
to Google Wave API
Hi.

I'm just thinking about creating wave-client as a XUL-application
inside firefox (or maybe thunderbird?).
Once wave-client can run in pure js inside web-page, why not to move
it one level up?

One of the advantages it gives is an ability to widely extend such
client with new functionality,
with all power of XUL.

Any ideas?

vadbars

unread,
Aug 17, 2009, 4:37:09 AM8/17/09
to Google Wave API
This is the correct idea! I also thought about something like that.
This is true in terms of practical convenience, and ideologically
correct. Imho, we should think about the wave-server as a root wave (a
meta-wave), which unites all its wave (like wavelets). Similarly, any
browser or standalone wave-program is the front-end for this meta-
waves.

In addition to XUL, there are scripts type GreaseMonkey, http://userscripts.org/.
We should not be limited gecko-browsers. For example, Google Chrome
(dev) now also supports java-scripts plugins. :)

Jason Salas

unread,
Aug 17, 2009, 4:53:41 AM8/17/09
to google-...@googlegroups.com
That's a very clever idea! I guess as long as the XUL client can
support (or effectively emulate) the server features, it'd be popular.
I've done some XUL work, and it's cool...albeit cumbersome.

FireFTP and of course Firebug are great examples of rich extensions in FF.

On a converse idea, I'd like to investigate building a Wave robot that
captures HTTP traffic. :)

qMax

unread,
Aug 17, 2009, 5:59:25 AM8/17/09
to Google Wave API
I'm not gecko expert,
but it might make a sence to create such wave client as a standalone
XUL-application,
rather then as firefox add-on.
I dunno what advantages could give firefox browser environment.
(the question is asked in mozilla.dev.extensions group)


Current web-client in firefox(3.0.x and 3.5.x) lags like hell.
( http://twitter.com/qmaxa/status/3329284211 )

I could not find out where is it's bottleneck.
Intuitively, i can suppose "too much javascript" in non-threading
environment.

Taking this in account,
writing pure-xul-based client may give some performance improvement,
simply by moving interface stuff into gecko,
and removing unnecessary web-browser-specific stuff.

And especially if to write XPCOM component for wave protocol.
But the latter is out of my competence.

Sarath Kummamuru

unread,
Aug 17, 2009, 4:56:36 AM8/17/09
to google-...@googlegroups.com
Hi Max and Vadim,
    I agree that it is a good direction to go in. 

thanks,
Sarath.
--
Thanks,
Sarath.

Quad One Technologies | Mobile: +91 98490 05620 | Off: +91 40 2335 0221 | www.quadone.com
Reply all
Reply to author
Forward
0 new messages