M. Fioretti wrote:
Thanks for the prompt answer, I'll look at the links you provided. One
thing to mention, maybe, is that I said Macro, not Add on.
I thought you might have been thinking about .odt files, but wasn't
sure. In any event, Python probably still comes closer to what you want
Quoting M. Fioretti [EMAIL PROTECTED]:
Greetings,
What if I wanted to implement some OO.o macros with Python?
What should I study, do, code, patch, download...?
I suggest you to read Robert Vojta's blog and also subscribe to the
dev@udk.openoffice.org list where the PyUNO guru -- Joerg is
Quoting Fbio Emilio Costa [EMAIL PROTECTED]:
Hi!
Em 05/06/05 08:30 Tony Pursell escreveu:
I saw this last week on the BBC News 24 channel. Unfortunately, it
didn't show any example screenshots of the OSS they are using. They
only managed a screenshot of XP and a shot of the MS HQ in Brazil
D. Carrera wrote:
But this addon would not be embedded in an .odt paragraph (at
least, not in the current and near-future OOo releases).
Why not, if I may ask?
May I ask... is there a reason why a .odt file is needed but
an addon won't work for you? (provided that the add-on works
Hi,
or press just F4 in a writer or calc document to open the data source view.
Best regards,
Ocke
dba.openoffice.org
Daniel Carrera wrote:
Base is a new component in the development release. If you want to try
it out you will have to download the beta version. The beta is
available from
Hi,
http://news.bbc.co.uk/1/hi/business/4602325.stm
:)
khirano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Marco,
Fair question, but you partly answered it yourself. OpenDocument
is one thing, OO.o another. Who can assume that the latter *will*
be installed wherever the former is used? Especially in 2/4 years,
if OpenDocument is to become the truly universal that we keep
saying etc etc...
http://www.iht.com/articles/2005/03/29/business/sware.html
I read this in March.
So they have made it now
:)
Cheers,
khirano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Quoting Laurent Godard [EMAIL PROTECTED]:
Hi Marco,
Fair question, but you partly answered it yourself. OpenDocument
is one thing, OO.o another. Who can assume that the latter *will*
be installed wherever the former is used? Especially in 2/4 years,
if OpenDocument is to become the truly
for all the idealism in the post, I will simply comment that MicroSoft would
only benefit themselves. They aren't around to benefit anyone else. Spyglass
model or otherwise, they make more profit lieing cheating and stealing then
by excercising integrity. My two cents.
Rigel
On 6/6/05, Gary
Hi,
Ok this is a learning opportunity, I thought odt is exactly the same as
sxw just
a with a different syntaxis. If I have a macro with a window form and I
save
that document. Does that mean that the code will be in the file or would
it be
on my computer? Does that means that they are
OSS has already replaced a number of commercial elements. Firefox for
browsing, Thunderbird for email, OpenOffice for (guess what here) in my
business, Linux for a file server ( soon the desktop). I don't get your
commment. :-)
Cheers,
Alex Janssen
Chuck wrote:
Anthony Long wrote:
Hello Gary,
will the formulas be stored as the string that I type in the spreadsheet
application, or will the tree structure of the formula be analyzed and
stored in a appropriate XML structure with different attributes for
operator, operand.
Will cell references be parseable and resolveable
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
specific
OpenDocment
I would say that in a few years time Microsoft will be heavily indebted for
its bare survival, on projects like OpenOffice.org, Mono, wine and ReactOS -
because they're F/LOSS projects that do make use of the Win32API and DotNET -
Microsoft will wind up being a retailer of a few high-cost
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
Marco Fioretti wrote:
But this addon would not be embedded in an .odt paragraph (at
least, not in the current and near-future OOo releases).
Why not, if I may ask?
Uhhm... because no such functionality is implemented yet.
May I ask... is there a reason why a .odt file is needed but
an
Alexandro Colorado wrote:
Ok this is a learning opportunity, I thought odt is exactly the same as
sxw just a with a different syntaxis.
Not quite, but close ;-) OpenDocument can do a few things that sxw
can't do; it's more general and powerful. But they are very close.
If I have a macro
Daniel Carrera wrote:
Come to think of it, I don't know how OpenDocument deals with
macros.
OpenDocument itself shouldn't deal with macros, but this is
something that _should_ be standardized, or at least well known.
This is the hole I'm trying to fill.
I very much doubt that this is
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.
Following weekend thunderstorm had problems with lan
and accessing internet, since mostly resolved. But
when I try to open OpenOffice.org 1.1.4 I get an error
message,
OpenOffice.org cannot be started due to an error in
accessing the OpenOffice .org configuration data.
Please contact your system
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:
As for macros, the issue is more tricky because a macro is a program
that tells the application to do something.
Well, not exactly, if I have understood it correctly.
A macro is a small program written in some _language_.
Uhhhm... what does that have to do with
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
On Mon, 6 Jun 2005 [EMAIL PROTECTED] wrote:
[...]
You would think that a conservative institution like Harvard would wanna
skew its results in Microsoft's favor. But I thought that their
analysis was surprisingly not handicapped very much in Microsoft's
favor.
Perhaps that's the best they
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
On Tue, 2005-06-07 at 13:05 -0400, Lars D. Noodn wrote:
On Mon, 6 Jun 2005 [EMAIL PROTECTED] wrote:
[...]
You would think that a conservative institution like Harvard would wanna
skew its results in Microsoft's favor. But I thought that their
analysis was surprisingly not handicapped
Marco Fioretti wrote:
Back to my training class example: a portable macro embedded into
an .odt file is what you could use to distribute tutorials or any
other interactive educational material where there is scarce bandwidth
and/or PCs not powerful enough to run OO.o. Ditto for CDs attached
Daniel Carrera wrote:
I very much doubt that this is possible. A macro always uses the OOo
API, and this API has no connection with OpenDocument.
You can write a Python macro that doesn't use the OOo API, you can even
write OOo Basic macros that don't use the API, only the Basic Runtime
Marco Fioretti wrote:
A macro is a small program written in some _language_. It is NOT
the code _and_ its interpreter. The latter, yes, is definitely not
portable.
But a large part of the language is also not portable, the API based
part. Of course you can write macros without using this,
On Tuesday 07 June 2005 16:33, Carl Shewmaker wrote:
Following weekend thunderstorm had problems with lan
and accessing internet, since mostly resolved. But
when I try to open OpenOffice.org 1.1.4 I get an error
message,
OpenOffice.org cannot be started due to an error in
accessing the
Stephen O'Grady of Redmonk, has an excellent commentary about MS XML and
the OASIS OpenDocument XML. He quotes Erwin Tenhumberg
http://blogs.sun.com/roller/page/dancer/20050601#microsoft_opens_office_file_formats
to make his case. It's short but well worth reading. Especially since
the
Marco Fioretti wrote:
Eh eh... This is the same simplification as OpenDocument = OO.o.
It would be more exact to say that the *interpreter* of a macro
must be written for the application that calls it (OO.o or whatever)
and today the only macros found in pre-OpenDocument files (.sxw, .sxc)
daniel heiserer wrote:
I want to use html data (http:// URL) which is behind a login mask.
With ordinary webpages I could paste an URL derived from mozilla browsing into
the openoffice URL. then I could either edit the page and save it on my disk,
export it to pdf or copy and paste data
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
Mathias Bauer wrote:
You can write a Python macro that doesn't use the OOo API, you can even
write OOo Basic macros that don't use the API, only the Basic Runtime
functions. Of course these macros don't do anything with the document.
Okay, the point of a macro is to do something with some
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
Sorry for the delay in responding. This was noticed on the version 2.0 Beta
in the Calc program.
Mike
- Original Message -
From: Peter Kupfer OOo [EMAIL PROTECTED]
To: discuss@openoffice.org
Cc: [EMAIL PROTECTED]
Sent: Friday, June 03, 2005 11:35 AM
Subject: Re: [discuss] 2.0 Beta
On Wed, Apr 20, 2005 10:49:23 AM -0400, Lars D. Noodén
([EMAIL PROTECTED]) wrote:
MSO XP on MS-Windows XP SP2 or MSO 2003 (which has DRM baked in) has
the capability that every time a document is opened, created,
edited, printed, copied, saved, or mailed that action can be
tracked.
Hello discuss,
In OOo 2.0, I can not copy a style from my currently openned document to my
default template, in
template manager.
Why? Thanks!
Best regards,
MRZ2003
[EMAIL PROTECTED]
2005-06-08
-
To unsubscribe, e-mail:
40 matches
Mail list logo
