Chaz Ginger wrote: > Edward Diener No Spam wrote: >> [EMAIL PROTECTED] wrote: >>> Edward> The definition of a component model I use below is a class >>> which >>> Edward> allows properties, methods, and events in a structured way >>> which >>> Edward> can be recognized, usually through some form of introspection >>> Edward> outside of that class. This structured way allows visual >>> tools >>> Edward> to host components, and allows programmers to build >>> applications >>> Edward> and libraries visually in a RAD environment. >>> >>> ... >>> Edward> I believe that Python should have a common components >>> model for >>> Edward> all RAD development environments, as that would allow the >>> Python >>> Edward> programmer to create a set of classes representing components >>> Edward> which would work in any environment. >>> >>> Having never used java or .NET I'm not sure what you're looking for. >>> Does >>> Python's current introspection not work? Is it someone too unstructured >>> (whatever "structured" means)? Can you give a simple example? >> In the typical RAD development environment, a particular component model >> allows one to drop components, which are classes corresponding to a >> particular inner representation which tells the development environment >> what are the "properties" and "events" of that component, and >> subsequently set "properties" for that component and add handlers for >> its "events" visually. snip... >> > > Why not propose something. That is the easiest way to get things moving.
How does one do that ? Propose something here on this NG or is there some other official way ? -- http://mail.python.org/mailman/listinfo/python-list
