On Tue, Jun 07, 2005 12:55:07 PM -0400, Daniel Carrera
([EMAIL PROTECTED]) wrote:
For once in my life, I will defend Microsoft.
I'm sorry Marco, but no. Using different APIs between Word and Front
Page does not at all help Microsoft achieve lock-in. And to some
extent makes it harder. But
M. Fioretti wrote:
I was thinking to different version of the same applications. Or (on a
limited set of functionalities) to two applications of the same type
(two office suites in this case).
Microsoft makes only one office suite.
Are you sure that different versions of MS Office use
Ian wrote:
At the risk of getting flamed I think that Marco has a good idea, I
would like to bounce some ideas about how it could be implemented.
Oh, until now I don't see that anybody denied that. It just seems that
Marco doesn't know how things work and why it is so complicated to
implement
Ian Laurenson wrote:
At the risk of getting flamed I think that Marco has a good idea,
Hi Ian,
Yes, the idea of standarisatin is a really good one. Internet is the
proof: it wouldn't have been possible without common standard protocols.
I can imagine a world where all applications share a
Enrique wrote:
Is it possible to define a common API to manage OpenDocument
programmatically?(not including GUI aspects), yes, of course. And with
some more rounds of standarization and agreement between software makers
it will be a reality. Not in the short term, but an idea that deserves
Mathias Bauer wrote:
Enrique wrote:
Is it possible to define a common API to manage OpenDocument
programmatically?(not including GUI aspects), yes, of course. And with
some more rounds of standarization and agreement between software makers
it will be a reality. Not in the short term,
Quoting Bernd Eilers [EMAIL PROTECTED]:
Hi there!
[...]
please let me know what you think of my reply to Daniel, where I
talk of a set of python functions etc
What I think is that you think about things that in reality are very
hughe and complex as being small and simple things. When
Marco Fioretti wrote:
Laurent Godard wrote.
IMHO, macros (developepd in StarBasic, python, beanshell,
whateverlanguage) do not deal with openDocument at all
It only deals with the layer the software (OOo) that render an
OpenDocument gives the script through its API. It is implementation
Enrique wrote:
If you go to macros you are talking about an _application_
standardising on that has been much more difficult ever.
No, I'm talking of a _language_. You can write Python, Perl
or many others and, with some obvious exceptions, those
scripts will run on different platforms.
Hi there!
[...]
please let me know what you think of my reply to Daniel, where I
talk of a set of python functions etc
What I think is that you think about things that in reality are very
hughe and complex as being small and simple things. When you say A set
of python functions that
Marco Fioretti wrote:
Even within single companies like Microsoft or Adobe, different
products use different APIs, just because they were created by
different people.
Bingo! You are comparing closed source apps with open source ones.
Different proprietary products *must* invent different
Marco Fioretti wrote:
Think Javascript applets controlling what you enter in a web form,
runnable by all *decent* browsers, versus all the possible FireFox
extensions that even make coffee for you.
OpenDocument already include xforms which covers much (most?) of what
people use Javascript
Daniel Carrera wrote:
For once in my life, I will defend Microsoft.
Yes, you new employer. :-)
I'm sorry Marco, but no. Using different APIs between Word and Front
Page does not at all help Microsoft achieve lock-in. And to some extent
makes it harder. But the simple fact is that they are
Ian Laurenson wrote:
2. For changing the document, an approach might be, for each call to the
common scripting routine:
* The file gets saved (temporary file?)
* The file location gets passed to the script
* The script manipulates the file contents, using common library
routines (I am aware of
14 matches
Mail list logo
