Ken Kozman wrote:
> > I think is, that guys @netscape should design (and follow) some
> > guidelines (and API) for XPCOM and XPCOM based components
> > installation. This would be very nice, since we all will get a
> > cross platform (XP)COM toolkit. Also I think that Mozilla itself
> > should be bit more separated. I mean, for example, that things
> > like windowing should be a separated package, wich onse
> > installed could be used by other applications. For example if
> > there is nsIWidget are perfect candidate for implementation
> > like that. So whenever someone need a user interface, it could
> > use nsIWidget based things and forget all other things (I mean
> > browser stuffs). Last, but the least, in that case, the
> > applications itself will use separate standart components, that
> > only have to be put together.
>
> This is one of the things which makes MSCOM so great and powerful. Plus it
> attracts many other development houses to just make components, knowing they
> will fit into a standard. Unfortunately MSCOM is not cross platform, nor is
> it open. I was hoping XPCOM might be able to grow into this role in at least
> a limited form, but it doesn't look like it will...
This is what XPLC is looking to do, while being quite early in its
development. http://xplc.sourceforge.net/ and
http://advogato.org/article/222.html (I think). It's close to being
usable for "application internal" use (like XPCOM in Mozilla), though.
--
Pierre Phaneuf
http://www3.sympatico.ca/pphaneuf/
