Johannes Schindelin wrote: > On Mon, 26 Nov 2007, Shawn O. Pearce wrote: > >> Actually I might revisit this XUL concept using an HTTP server and AJAX. >> I could actually link the damn HTTP server against libgit.a (Junio will >> hate me). If the server dies XUL can notice it and simply restart it. > > But if you can restart the HTTP server via XUL, you can start other git > programs directly. > > What you'd have to do is (urgh) write a wrapper via start_command() > which would recognize that the second process die()d. > > All in all, I think if you want to switch from Tcl/Tk to another language > for git-gui, for the sake of attracting more developers, it might be wiser > to go Java than XUL. Wont we get with the same problems as egit/jgit? ---- This is proposed set of questions for git-gui mini survey... 1. What language and what toolkit should git-gui be written in? (single choice) a. Tcl/Tk (current implementation) b. C++/Qt c. C/GTK+ d. Python (native) e. Python/PyQt f. Python/PyGTK g. Ruby h. Java/Swing i. Java/SWT j. XUL+JavaScript+CSS/XULRunner k. other l. no opinion 2. If you have chosen "other" in question above, what language and toolkit should it be? C/XForms? C#/Mono? C/wxWidgets? XAML+Silverlight? GTK2-Perl? C/OpenGL? ;-) 3. Do you contribute to git-gui? Yes/No 4. If git-gui would use other language/toolkit, would you contribute? Yes/No 5. What languages and what toolkits you are proficient with (to send patches)? (multiple choice) a. Tcl/Tk (current implementation) b. C++/Qt c. C/GTK+ d. Python (native) e. Python/PyQt f. Python/PyGTK g. Ruby h. Java/Swing i. Java/SWT j. XUL+JavaScript+CSS/XULRunner k. other l. N/A 6. What other? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
