Franz Steinhauesler wrote:
Von: Robin Dunn <robin@alldunn.com>
An: Franz Steinhaeusler <francescoa@users.sourceforge.net>
Betreff: Re: Pycrust support of plugins:
Datum: Fri, 24 Feb 2006 13:42:42 -0800Franz Steinhaeusler wrote:
Message body follows:
What do you think of the whole approach
If you don't like it, no problem.I do like it, my only concern was that it isn't "general purpose" enough yet. I guess my comments so far could be summed up by saying that the plugin framework should be usable for all of Py,
Yes, this patch was a kind of fast shoot.
It is better to think again about the architecture,
and I want to study the "Py" package more thoroughly.(in case Py someday grows to achieve Patrick's vision and becomes a whole lot more than just PyCrust.)
Eh, Patrick's vision. Sounds interesting, but that is this exactly
(In one sentence)?
It was very much like what Stanni is currently discussing about creating the ultimate programmable IDE.
Also, I think it would be helpful if the plugins don't have to know very many details of the inner workings of Py in order to plug into it.
How can one make it in such a way?
To not use anything from the core?
More level of abstraction?So, for example, perhaps instead of the plugin needing to know that the Frame has a viewMenu the Frame should provide a method AddToViewMenu and etc.
Ok, this looks better of course.
Or perhaps there should be a plugin base class
This would be cool, how to design such a base class?
Not really a question, only loud thinking.
See my other mail.
···
--- Ursprüngliche Nachricht ---
that Py provides that takes care of details like that, and then the actual plugins can derive from that base class and call various base-class methods to initialize themselves.
Does this make sense?
Yes, yes.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!