John.Birch at xtra.co.nz
Tue Dec 12 03:26:09 UTC 2000
Just got back from a long ride - that always helps.
I'm not going to buy into you're "there can be only one" statement (shades of
"Highlander" anyone :-) Let me give you a real example - kdevelop
It's C++/C right - well wrong actually there's lots of wonderful perl in it.
Hmmm, Why isn't this parsed? There are various ways to do this, but one would
be to have two separate class browsers at the same time. Quite conceivable
and there could be benefits from this approach. But it can't be done because
the framework will not allow it. (note: I'm not suggesting we actually do
So can you see that by restricting the framework, we restrict the app we can
build. This is okay _provided_ that we understand we are doing this.
Of course, there are some advantages doing it your way, but ...
On Tue, 12 Dec 2000 08:58, Bernd Gehrmann wrote:
> On Tue, 12 Dec 2000, John Birch wrote:
> > Because the component pointers are held in the component base class, then
> > every component "knows" about the other components.
> No it doesn't. Each component just knows the 'KDevApi' which is
> a set of interfaces (which is at the same time a set of DCOP
> interfaces) that are needed to process the bread & butter tasks
> an IDE must perform. There are a number of parts that bring
> the user to a certain location in a certain file. This is
> something that must be centralized in exactly _one_ part,
> not less than one, not more than one. It's the same for other
> interfaces: For compiled languages, you need one component
> that starts the compiler and displays its output.
> to unsubscribe from this list send an email to
> kdevelop-devel-request at kdevelop.org with the following body: unsubscribe
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel