reusable software components

[simonb at webone.com.au]

Well, yes im working on this stuff now;
trying out ideas anyway.

i was wondering about this aswell,
searching from the point of
view of design patterns, rather than
beans. still i found little.
the design patterns SIG is dead and burried,
not even the archives are available right now.

My suspician is that all this framework
stuff is so easy to do in python that
no one bothers to "encapsulate" it for others.
A lot of the design patterns are one-liners in python!

Still, i am interested.
it has a lot of relevance, i think, eg.
anygui, types-sig, CP4E, beans, design patterns.

Anyway, u r talking about the bean trick in particular.
i was never convinced that Bean Info was
all that necessary to accomplish the task at hand.
what im thinking of is full introspection
coupled to direct user manipulation.
this is not so bad in java where
u can find out what to plug into what,
but the type system in python is
... absent? or just dynamic, i guess.
Although, we do have doc strings,
and we can parse our own code...
Beans are a kind of type system, if u like.
and this is one thing i think
a SuperPythonMachine should incorporate... :)

Simon Burton


Kevin Altis wrote:

>Are there any current efforts to build cross-platform Python components or
>standardize a Python component model?
>
>I've been thinking about creating a component framework for PythonCard,
>which will use wxPython for its GUI widgets. The component framework is
>mostly going to be a set of conventions to follow, so that a visual
>environment can hook together components and make compound components. Since
>Python itself already provides introspection, what seems to be missing are
>the hints to use at design time for specifying the properties and events for
>the component. While Python doesn't use strong typing, components need type
>info, especially when the component is wrapping a native control written in
>C/C++.
>
>There is no particular reason the conventions need to be limited to
>wxPython, they could be applied to tkinter components or even non-visual
>components.
>
>Software components are described by the excellent Java Beans intro, which
>you should take ten minutes to read if you don't know what software
>components are:
>
>http://developer.java.sun.com/developer/onlineTraining/Beans/Beans1/index.ht
>ml
>
>Anyway, I searched the comp.lang.python archive and a few other sources and
>except for some older messages talking about COM and CORBA and Java Beans, I
>didn't find any current efforts to make a standard set of conventions for
>Python components. The PyXPCOM stuff looks like it is stalled out.
>
>I would appreciate any feedback, suggestions, or links on software
>components for Python.
>
>Thanks,
>
>ka
>ps. My first post seems to have been eaten by my ISP, but apologies in
>advance for a double-post if it shows up (I posted the first one over six
>hours ago).
>
>