[ge-talk] UI ideas

[Jonathan Thompson]

That's only your perception: it is *USED* by many other Windows 
applications, though a large number of them are centered around the MS 
Office ecosystem.  Curiously enough, if you try modern versions of 
Office, they don't support OLE nearly as well as the older versions did, 
because it wasn't nearly as popular as Microsoft had hoped.  Also, being 
able to run applications with a browser as the root container for 
functionality has reduced the need/desire to do such things with most 
other applications.

Now, part of the reason why OLE wasn't as popular everywhere is that it 
is truly a PITA to program for, regardless of MFC/OWL or other 
frameworks that "simplify" things a bit, though MFC adds its own 
complexification into anything it supports doing, and that's why 
programming BeOS replicants is easier, but not as full-featured as OLE 
under Windows, because the system doesn't provide all that much for 
Replicants, but it also doesn't require a lot of wiring complexity, either.

Niklas Nisbeth wrote:
> Yes, yes, yes, yes... This we must have. Be API is perfect for this 
> kind of thing, I reckon. The problem is you need to standardise the 
> data in some ways. I think.
>
> I think the problem is that OLE is only *used* by MS Office, maybe cos 
> the documentation is wank or maybe it's just a pain to use.
>
>   
>> Where did I get the idea that OLE was only for Microsoft Office? 
>> Maybe
>> because Office "owns" the file formats.
>> With the translator idea you could have several apps that can deal 
>> with the
>> same object and you would pick any one you want when you want to edit 
>> an
>> object in your document, instead of say "Excel" for xls.
>>
>> On 1/5/07, Gavin James <gavin.james at runbox.com> wrote:
>>     
>>> On 5 Jan 2007, at 18:45 PM, Ari Haviv wrote:
>>>
>>> I really like that Linkback idea. Should be part of the OS so that 
>>> more
>>> than a dozen or so apps will use it.
>>> Microsoft will never do such a thing because they want everyone to 
>>> buy
>>> their entire friggin suite.
>>>
>>>
>>> I'm pretty sure they already did... and called it Object Linking 
>>> and
>>> Embedding (OLE). ;-)
>>>
>>> - Gavin
>>>
>>>       
>
> _______________________________________________
> glasselevator-talk mailing list
> glasselevator-talk at bug-br.org.br
> http://www.bug-br.org.br/mailman/listinfo/glasselevator-talk
>
>