I don't think you're hearing exactly what I'm saying. I would not expect the users to "install and run a web server". If you're using Xastir, you have the option now of starting a "server"; I'm talking about the same thing, only having it speak a standard protocol, http.
-- William McKeehan KI4HDU http://mckeehan.homeip.net On Tue, October 9, 2007 3:16 pm, Brad Douglas wrote: > On Tue, 2007-10-09 at 15:02 -0400, William McKeehan wrote: >> On Tue, October 9, 2007 2:46 pm, Brad Douglas wrote: >> > Are you suggesting that everyone have a working http server on their >> > local machine? That is quite an excessive (and generally insecure) >> > method of accomplishing the given goal, locally. >> >> Well, I'm thinking about a limited http server as part of Xastir, not >> necessarily on port 80 (the default http port). It would be similar to the >> current Xastir server port. I think we could find code for a simple http >> engine to incorporate into the Xastir code that is neither excessive nor >> insecure. > > If that happens, I will stop using Xastir. It is unreasonable to > require users to install and run a web server for a single application. > Web GUIs are highly limited in functionality. > >> > IMO, wxPython is the way to go for GUI development. >> >> My suggested approach would let people develop a GUI in multiple >> environments >> and provide a standard "API" to facilitate this development. > > This is not practical, IMO. > > > -- > 73, de Brad KB8UYR/6 <rez touchofmadness com> > > > _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
