<br><div><span class="gmail_quote">On 24/10/06, <b class="gmail_sendername">Carlos Ribeiro</b> <<a href="mailto:carribeiro@gmail.com">carribeiro@gmail.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;"> <span class="q">On 10/23/06, <b class="gmail_sendername">Ivan Krstić</b> <<a href="mailto:krstic@solarsail.hcs.harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">krstic@solarsail.hcs.harvard.edu </a>> wrote:</span><div><span class="q"><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Carlos Ribeiro wrote:<br>> before implementing a GUI tool, we should talk about whether<br>> to have X installed on a server or not.<br><br>This isn't much of a discussion topic; we absolutely won't enable X by<br> default in Ubuntu Server. </blockquote></span><div><br>Agreed :-) I was trying to say that it doesn't make much sense to talk about a GTK based GUI for a server that does not have X libraries installed - unless one is willing to write his own client-server protocol to make it work (which is not a good idea IMHO). </div></div></blockquote><div><br>Depends on how you implement it. I suspect you can use well-tested libraries to do most of the hard work.<br></div><br><div>[Snip] <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> For a first shot, I think a Web interface is the way to go - no need for X, and the limitations of the Web interface are a bonus as they force the designer to keep the UI simple. Going to the GUI route implies that either X libraries have to be installed (which may be a good idea or not), or that the application implement some "protocol" of its own (even if only to copy config files from & to the server during the configuration session). </blockquote><div><br>Web interfaces restrict the abilities of the client, not force simplicity. I've seen some really ugly, non-simple web interfaces before now.<br><br>As for inventing protocols, that depends. One way of doing it is to use the http/tls python libraries to create a specialised mini-webserver that serves and receives XML (SOAP?) files. That way various back ends can be implemented. <br><br>I'm a bit busy these coming few weeks, so I can't sit down and write a full spec, only assist, but If no one has done it by the time I'm free, I'll write one.<br></div><br>Arwyn<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Also, a simple Web interface will work over a regular SSH connection using elinks or lynx (which support curses). It's not pretty, but it works. And elinks supports HTTPS also, which is a plus.<div><span class="e" id="q_10e77ba3a618183c_6"> <br><br>-- <br>Carlos Ribeiro <br>Consultoria em Projetos<br>blog: <a href="http://rascunhosrotos.blogspot.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://rascunhosrotos.blogspot.com</a><br>blog: <a href="http://pythonnotes.blogspot.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://pythonnotes.blogspot.com</a><br>mail: <a href="mailto:carribeiro@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> carribeiro@gmail.com</a><br>mail: <a href="mailto:carribeiro@yahoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">carribeiro@yahoo.com</a><br><br> </span></div><br>--<br>ubuntu-devel mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" target="_blank"> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br><br><br></blockquote></div><br>