Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hash: SHA1

On 14/06/2011 15:31, Alexandro Colorado wrote:

How exactly would that work. So far the discussion was about moving code around, but what about 
generating code for both?

As a practical matter, the code would have to modified to work as
expected with at least one, if not both projects.

How much modification would be required, depends upon what the code
does, and how deeply into other code it interacts.

By way of example.

You could dump the entire SQLite code into LibO, or Apache_OOo, with no
modifications, if nothing called that code.  However, for end users,
that SQLite code would be useless, because there would be no way for
them to create, edit, or retrieve data from an SQLite database.

If code for the UI is included, so that end users can create, edit, or
modify SQLite databases, then the code (SQLite + UI code dump) may have
to be massaged to fit project guidelines, fix bugs, or other things.

- -- 
If Bing copied Google, there wouldn't be anything new worth requesting.

If Bing did not copy Google, there wouldn't be anything relevant worth

                              DaveJakeman 20110207 Groklaw.
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.