suggestions sought for a framework for a quick, dirty, reallysimple GUI prototype

[Oleg Goldshmidt]

On Thu, Jul 19, 2012 at 12:40 PM, Dov Grobgeld <dov.grobgeld at gmail.com>wrote:

> The advantage of using Qt or Gtk compared with some of the other gui
> toolkits mentioned (fltk, Tcl/Tk, SDL, or Matlab GUI) are that they are
> complete (lots of widgets, internationalization and localization support
> etc) if the prototype turns into something bigger than was initially
> envisioned. To often have I seen tools that were written like "oh, its's
> only for me" and then a company is trying to figure out how to deploy and
> support the tool. I therefore thing it is worth taking the time to learn
> complexity of one of these GUI's, and then use it.
>

I understand all of this and this is exactly why I stressed in the original
post that I was sure it would be thrown away. The reason is that our
product includes a very sophisticated GUI that is Windows/.NET and I do not
see  either the company or our customers to switch to, say, Linux/Qt in the
foreseeable future. So whatever we do in a demo/mockup/prototype will have
to be re-implemented in the current GUI framework. What we do not currently
have is skilled GUI development resources to participate in the prototyping
effort, so integrating the prototype with the existing GUI is out of the
question.

Therefore feature-completeness is not a consideration in this particular
case, though I fully support the philosophy in general.

Thanks to all those who have already made suggestions, and keep them
coming. I cannot keep up in real time (i.e., each time something gets
mentioned, look it up, evaluate, respond), so my lack of specific reactions
does not mean I am not paying close attention.

-- 
Oleg Goldshmidt | pub at goldshmidt.org <oleg at goldshmidt.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20120719/5f00bb2a/attachment.html>