Thanks for that link, it was a real help. I can't say I'm pleased, but the
decision has been made and I will not go against the steering community.
Something I did note was that a-lot of the points we have raised match
theirs concept-for-concept if not word-for-word.
On Tue, Nov 23, 2010 at
On Mon, 22 Nov 2010 22:24:00 +1100, Sean White runicpala...@gmail.com wrote:
One of the things i LOVE about open source software is the ability for me to
ask someone else to code something or port something that i cant do myself.
So my solution to your problem of incompatible extensions is to
One of the things i LOVE about open source software is the ability for me to
ask someone else to code something or port something that i cant do myself.
So my solution to your problem of incompatible extensions is to set up a
new mailing list for OO to LO extension porting. the public can send
because the underlining code inst changing overly-much, most of the
extensions should be easy to port and in th odd case where an extension is
truely broken by LO's remakes then we can rewrite the plugin from scratch.
As a side not we will probably need a page on the document foundation site
that
Hi Florian Reisinger, *,
This mail arrived completely screwed up!
I'm sure no one made the effort to read it.
Florian Reisinger schrieb:
[.. screwed content ..]
Gruß/regards
--
Friedrich
Libreoffice-Box http://libreofficebox.org/
LibreOffice and more on CD/DVD images
(german version already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/22/2010 11:24 AM, Sean White wrote:
One of the things i LOVE about open source software is the ability for me to
ask someone else to code something or port something that i cant do myself.
Have you looked at the percentage of extensions for
jonathon wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2010 09:15 PM, James Wilde wrote:
...and? Is LibO going to upgrade the version number every time OOo does? And
only then?
Unless there is a compatibility tag for extensions, the way that there
is for firefox,
Hi,
I've tried to fix the mail from Florian Resinger:
Btw, Florian, which email client do you use? Your email was horrible to
read I've had a hard time figuring out, who said what after your mail.
Sigrid
Am Sat, 20 Nov 2010 11:25:11 +0100
schrieb Florian Reisinger reisi...@live.at:
Claus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2010 09:15 PM, James Wilde wrote:
...and? Is LibO going to upgrade the version number every time OOo does?
And only then?
Unless there is a compatibility tag for extensions, the way that there
is for firefox, LibO is stuck with the
On Nov 21, 2010, at 22:31 , jonathon wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2010 09:15 PM, James Wilde wrote:
...and? Is LibO going to upgrade the version number every time OOo does?
And only then?
Unless there is a compatibility tag for extensions, the way
On Mon, Nov 22, 2010 at 12:12 AM, James Wilde wilde.ja...@gmail.com wrote:
Well, I appreciate that it would mean two sets of numbers for extensions,
but I can imagine that, in a not too distant future, OOo and LibO are going
to grow apart, possibly sufficiently that an extension for the one
As a concerned user, if LibreOffice is meant a independent office project
derived from the OpenOffice code then why do we still use their version
numbering system. Wouldn't it be better to start from 1 to reinforce in
peoples minds that we are a separate project.
--
Sean White,
Concerned User
Sean White wrote:
As a concerned user, if LibreOffice is meant a independent office project
derived from the OpenOffice code then why do we still use their version
numbering system. Wouldn't it be better to start from 1 to reinforce in
peoples minds that we are a separate project.
I couldn't
13 matches
Mail list logo
