[META-SIG] Re: Python a new opportunity.

[Samual M. Rushing]

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "je" == JOE ELLSWORTH <JOE_ELLSWORTH@HP-Cupertino-om5.om.hp.com> writes:
     
    je>      I believe Python and a TK look alike could fill this
    je> niche better than currently available development tools and
    je> would benefit from doing so by attracting a new group of
    je> previously inaccessible pragmatic application developers.  Of
    je> course marketing the availability of the tool would be as
    je> important as making it available in the first place.  Some non
    je> trivial applications using the tool would also help.
     
    je>      The core MFC libraries are available for CE and as such a
    je> porting effort should not be terribly difficult except for
    je> memory foot print and access to a few proprietary features of
    je> the new device.
     
I don't know about MFC on the CE platform, but elsewhere MFC is nearly
a megabyte.  [imagine what you could do with a megabyte of python byte
code!]

    je>      Features Needed to compete in this space: Compatibility
    je> with Windows CE.
     
    je>         A base memory foot print less than 500K, ideally less
    je> than 300K.  multiple copies of interpreter should be able to
    je> share base memory.
     
One thing you might want to explore is the fledgling 'class library'
that's included with the 'calldll' module: Although it's very
incomplete (I don't get to work on it much), it suffices for building
windows applications.  It uses calldll to speak directly to the
windows API: (i.e., it calls functions in user32.dll, gdi32.dll,
kernel32.dll, etc...) Even with the message loop written entirely in
Python, the performance is good: I've written applications that do
scrolled scaled graphics...  Most of this is in about, hmmm... 50-60k
of pyc files.

I think a Tk-like library (in other words, a well-designed,
object-oriented library where widgets can be composed) could be built
on this.  In fact, that was my goal when I started working on it.

[see http://www.nightmare.com/software.html for a description of the
 calldll]

- -Sam

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBM8xOpGys8OGgJmJxAQHi7QQApRXBuBabCb74h5yMFCmvCcNVTuX6E8TV
2usRLwsOSH19X3ONKjfNMhK69n/kQ1DnlrHTTFTHQleZICx11+pBgyS6hl+34DI7
XKzU+zelMcE4ySQB+1q93oJzvAAHwbSu6FzXkqPYAIXEjV6NzQztqcg8na9zDxN1
tnIPBqSoSf0=
=IXVm
-----END PGP SIGNATURE-----

_______________
META-SIG  - SIG on Python.Org SIGs and Mailing Lists

send messages to: meta-sig@python.org
administrivia to: meta-sig-request@python.org
_______________