UI toolkits for Python

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Mike Meyer

    #46
    Re: UI toolkits for Python

    aleaxit@yahoo.c om (Alex Martelli) writes:[color=blue]
    > Mike Meyer <mwm@mired.or g> wrote:[color=green]
    >> aleaxit@yahoo.c om (Alex Martelli) writes:[color=darkred]
    >> > Mike Meyer <mwm@mired.or g> wrote:
    >> >> What surprises me is that marketing types will accept turning away -
    >> >> what's the current internet user base? 200 million? - 10 million
    >> >> potential customers without a complaint. Or maybe they just don't get
    >> >> told that that's what's going on.
    >> > In firms where marketing has lots of power, they may indeed well decide
    >> > to pursue those "10 millions" by demanding an expenditure of effort
    >> > that's totally out of proportion[/color]
    >> What makes you think that the expenditure of effort is "totally out of
    >> proportion"? In my experience, that isn't the case - at least if you
    >> go into it planning on doing things that way. Retrofitting a site that
    >> was built without any thought but "make it work in my favoriter
    >> browser in my favorite configuration" can be a radically different
    >> thing.[/color]
    > We ARE talking about moving from supporting 95% to supporting
    > (*supposedly*!) 100%, after all -- very much into the long, *LONG* tail
    > of obscure buggy versions of this browser or that, which SOME users
    > within those last centiles may have forgotten to patch/upgrade, etc.[/color]

    I'm talking about supporting standards instead of clients, which is
    how you get interoperabilit y. You clearly can't support all the buggy
    browsers that exist, especially not when even commercial browsers are
    releasing betas to the public. Reality is that you *have* to support
    the most popular browser(s) - except for the betas, anyway. Other
    browsers that have bugs - well, you can patch around them if it's
    trivial enough, and identify where the browser is out of spec
    otherwise in hopes the author will fix it. Unless you're out of spec,
    in which case you fix your code.
    [color=blue][color=green][color=darkred]
    >> > Maybe that's part of the explanation for the
    >> > outstanding success of some enterprises founded by engineers, led by
    >> > engineers, and staffed overwhelmingly with engineers, competing with
    >> > other firms where marketing wield power...?[/color]
    >> You mean like google? Until recently, they're an outstanding example
    >> of doing things right, and providing functionality that degrades
    >> gracefully as the clients capabilities go down.[/color]
    > I'm not sure what you mean by "until recently" in this context. AFAIK,
    > we've NEVER wasted our efforts by pouring them into the quixotic task of
    > supporting *100%* of possible browsers that may hit us, with the near
    > infinite number of combinations of browsers, versions and disabled
    > feature that this would require.[/color]

    Google's sites have been very good about working with many browsers
    and configurations, especially when compared with the run of the mill
    on the web. If that's unintentional - well, that's simply a shame.
    [color=blue]
    > One may quibble whether the target percentage should be, say, 93%,
    > 95%, or 97%, and what level of degradation can still be considered
    > "graceful" around various axes, but the 100% goal which you so
    > clearly imply above would, in my personal opinion, be simply foolish
    > now, just as it would have been 3 years ago.[/color]

    I never meant to imply that you should try and support 100% of all
    browsers, merely that they should try and support every browser that
    follows the specifications (and IE). I can see how what I said might
    be construed to mean the latter, and I'm sorry about that.

    <mike
    --
    Mike Meyer <mwm@mired.or g> http://www.mired.org/home/mwm/
    Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

    Comment

    • Kenneth McDonald

      #47
      Re: UI toolkits for Python

      I'd have to agree with this. Unfortunately, the only way to use Swing
      (in a
      reasonable manner) from Python is to use Jython, and Jython has other
      shortcomings that make me not want to use it.

      Sigh.

      Ken
      On 19-Oct-05, at 9:59 AM, Ed Jensen wrote:
      [color=blue]
      > Claudio Grondi <claudio.grondi @freenet.de> wrote:
      >[color=green]
      >> I haven't seen any really platform-independent software yet and I
      >> don't
      >> expect to see any in the future.
      >> It is simply not possible to have one, even if much progress was
      >> done lately
      >> in many areas in order to try to approach it as close as possible.
      >>[/color]
      >
      > Java + Swing is probably as good as it gets when the goal is to write
      > platform independent software.
      > --
      > http://mail.python.org/mailman/listinfo/python-list
      >[/color]

      Comment

      • Ed Jensen

        #48
        Re: UI toolkits for Python

        Kenneth McDonald <kenneth.m.mcdo nald@sbcglobal. net> wrote:[color=blue]
        > I'd have to agree with this. Unfortunately, the only way to use Swing
        > (in a
        > reasonable manner) from Python is to use Jython, and Jython has other
        > shortcomings that make me not want to use it.[/color]

        What shortcomings?

        Comment

        Working...