At 03:20 AM 3/22/2002 -0800, Michael Cummings wrote: .... >My thought was a simple one, so to speak, never mind >the coding involved. A generic UI module, invoked like >$new_something = UI::new(html), or $new_something = >UI::new(gtk), etc (syntax not the point here, I know >that that's bad even for pseudo code), but the idea is >a generic UI that takes a common set of functions and >produces at least similar results for a wide variety >of interface types. That way you could develop an app, >use this generic UI, and with one incoming parameter >(html, tk, gtk, curses, what have you) you would have >an interface that met your needs without an recoding. >Yeah, the backend modules would be huge, rough, and >very sticky, but the results might warrant that. And >in my "enterprise" experiences, that would be a >wonderful thing, the ability to display a project in a >large variety of gui types. ....
Hi, * Do you actually need this or are you just curious? * Are you interested in exploring how this might be done within the P5EEx::Blue framework? * Do you have skills with any of the non-HTML Perl UI environments of which you speak? (Gtk, Curses, WxPerl, etc.) I have thought about how this would be done with Widgets. Solving the problem is not unlike solving the problem of presenting different variants of HTML based on the capabilities of the browser (DHTML, JavaScript, Java, etc.). I agree in general that the UI's may need to be tremendously different for different user agents. However, at some logical level in the application design, they will be the same. If you have the interest to pursue these thoughts within the P5EEx::Blue framework, let me know. Stephen
