It's true XPCOM's are quite big, but not really that specific to Mozilla. It's just a collection of the modules something similar to DLL's which also in most cases provides API's for desktop like functionality. Basically is the way of extending the JavaScript capabilities, to give it a power to access files, to listen ports and etc.. Besides the nice thing about it that xpcom's can be written almost in any language and then it will be wrapped to JS as module.
Basically what we can benefit from that will be that all browsers will be powered as firefox is. Of course that means any kind of web based apps instead of desktop ones. Great example can be all kind of vendors of hardware like (mobile phones, media players etc..) All of them are creating the desktop apps, usually platform specific, just for the one goal - to manage content on the device. I'm pretty sure all of them would happily jump to gears if it will provide the ability of doing that. I can't tell for sure as I don't have clue how it works on C++ side, but I suppose it doesn't have to be a very complicated task creation of module for gears, from the part of the xulrunner which imports xpcoms. Besides it's fully open source. On Nov 10, 3:22 am, Khookie <[EMAIL PROTECTED]> wrote: > I don't know but looking at XPCOM from the outside, it always struck > me as being big and specific to Mozilla, whereas Gears is more about > providing base APIs for desktop-like functionality while being cross- > browser & maintaining browser security. > > Both have very different goals I would say. > > Chris > > On Nov 10, 3:25 am, rFobic <[EMAIL PROTECTED]> wrote: > > > Hey is this going to be ignored completely?? > > Maybe at least someone would say that it's stupid idea or maybe > > something else :(
