De:NeoOffice und Aqua

From NeoWiki

(Difference between revisions)

Revision as of 16:34, 4 February 2006

HÃ¤ufige Fragen zum Design und zur Entwicklung von NeoOffice oder "Alles, was Sie Ã¼ber NeoOffice nicht wissen (und daher lesen sollten, bevor Sie auf [Mac]Slash[Dot] posten)."

1 Aqua-Anpassung und Mac-OS-X-Integration
- 1.1 Warum hat NeoOffice nicht die typische Mac-OS-X-OberflÃ¤che mit den blauen KnÃ¶pfen?
- 1.2 Was sind die neuesten DurchbrÃ¼che bei der Aqua-Anpassung?
2 Technologien und Toolkits
3 Andere Fragen

Aqua-Anpassung und Mac-OS-X-Integration

Warum hat NeoOffice nicht die typische Mac-OS-X-OberflÃ¤che mit den blauen KnÃ¶pfen?

NeoOffice ist zur Zeit noch nicht sehr an Aqua angepaÃŸt. Aber die Entwickler arbeiten daran!

Das Ziel ist, langsam Aqua-OberflÃ¤che hinzuzufÃ¼gen, so daÃŸ es mehr und mehr wie ein Mac-Programm aussieht, bis es keinen Hinweis mehr darauf gibt, daÃŸ es jemals kein Mac-OS-X-Programm war.

In den letzten Monaten ist NeoOffice StÃ¼ck fÃ¼r StÃ¼ck verbessert worden.

Was sind die neuesten DurchbrÃ¼che bei der Aqua-Anpassung?

Stand von November 2005:

Verbesserte KompatibilitÃ¤t mit sprachgesteuerter Software (10/2005)
Eingebettete EPS-Dateien kÃ¶nnen gedruckt werden. (09/2005)
Verbesserte UnterstÃ¼tzung von internationalen Tastaturbelegungen (09/2005)
DockmenÃ¼ mit Items aus dem "Quickstart"-Service (auch im NeoOffice-MenÃ¼ zu finden) (06/2005)
Kein "graues Fenster" mehr, wenn das letzte Dokumentenfenster geschlossen wird, aber das Programm bleibt trotzdem geÃ¶ffnet, genau wie ein normales Mac-Programm (05/2005)
Spotlight-Integration unter Mac OS X 10.4 "Tiger" per NeoLight (en) (05/2005)
Benutzung der Farben, die im Erscheinungsbild-Fenster festgelegt wurden (04/2005)
UnterstÃ¼tzung indischer Sprachen (04/2005)
UnterstÃ¼tzung fÃ¼r Eudora, Entourage und Mail als externe Mail-Programme (03/2005)
AppleScript fÃ¼r Drag-and-Drop-Installation der Hilfedateien fÃ¼r nicht-englische Sprachen (03/2005)
Drag & Drop zwischen NeoOffice und anderen Programmen (03/2005)
Beendet sich nicht mehr, wenn das rote SchlieÃŸen-Widget am letzten Dokumentenfenster gedrÃ¼ckt wird (03/2005)
"Ãœber NeoOffice"- und "Einstellungen"-Items im "NeoOffice"-MenÃ¼ (02/2005)
Lokalisierte BenutzeroberflÃ¤chen fÃ¼r 40 Sprachen (12/2004)
Neues Aqua-Ikon und Startbildschirm (12/2004)
Optimiert/kleinere PDFs (12/2004)
Drag & Drop fÃ¼r Texte (12/2004)
Scrollrad-UnterstÃ¼tzung (11/2004)
MenÃ¼s erscheinen jetzt in der weiÃŸen Leiste am oberen Bildschirmrand, wie in jedem anderen Mac-Programm (vorher waren sie oben im Dokumentenfenster) (11/2004)
Automatische Benachrichtigung bei neuen Patches und Versionen (11/2004)
Patches sind als Standard-Mac-OS-X-Installationspakete verfÃ¼gbar (09/2004)
UnterstÃ¼tzung fÃ¼r Macintosh-Datei-Aliase in Ã–ffnen- und SchlieÃŸen-Dialogen (09/2004)

Bleiben Sie dran, es werden weiterhin neue Funktionen hinzugefÃ¼gt!

Technologien und Toolkits

Welche Technologien werden bei der Aqua-Anpassung von NeoOffice verwendet?

Aqua ist die BenutzeroberflÃ¤che, die Apple fÃ¼r OS X entwickelt hat. Apple stellt drei Umgebungen zur Entwicklung von Programmen mit Aqua-OberflÃ¤che zur VerfÃ¼gung:

Carbon (eigentlich fÃ¼r KompatibilitÃ¤t mit OS 9, auch von Mozilla/Firefox verwendet)
Cocoa (neue Umgebung, die von NeXT fÃ¼r Mac OS X adaptiert wurde)
Java (plattformÃ¼bergreifende Sprache, beinhaltet JFC/Swing fÃ¼r eine an Aqua angepaÃŸte OberflÃ¤che)

NeoOffice/C (das ursprÃ¼ngliche Prototyp-Projekt) war ein Versuch, Cocoa und Carbon zu benutzen. Das erfolgreichere Projekt, NeoOffice (ursprÃ¼nglich bekannt als NeoOffice/J), verwendet im Moment eine Mischung aus Cocoa und Java 1.4.2.

Also...ist NeoOffice in Java geschrieben?

Nein.

NeoOffice ist eine Mac-OS-X-Version von OpenOffice.org, die kleine Mengen von Java-Code fÃ¼r das Zeichnen und Konfigurieren von Graphiken verwendet.

OpenOffice.org ist in erster Linie in plattformunabhÃ¤ngigem C++ geschrieben. NeoOffice bedient sich jedoch der fortgeschrittenen Mac-OS-X-Integration von Java, um die Mac-OS-X-OberflÃ¤che anzuzapfen. Mit anderen Worten: Die kleinen Anteile an Java in NeoOffice haben hauptsÃ¤chlich mit VorgÃ¤ngen zu tun, die beeinflussen, wie das Programm aussieht. Der Kern des Officepakets ist in C++ geschrieben. (Der Code, aus dem NeoOffice besteht, ist zu 99% OpenOffice.org-Code, der von allen OpenOffice.org-Plattformen benutzt wird, und zu 1% spezieller Mac-OS-X-Code in Java, C++, C und Objective-C.)

NeoOffice lÃ¤uft nur auf Macintosh-Computern mit Mac OS X 10.3.x oder 10.4.x - nicht unter Mac OS 9, Mac OS X 10.2 oder darunter, Windows, Linux, Darwin oder irgendeiner anderen Art von UNIX.

Wie wird Java in NeoOffice verwendet?

Wie oben erwÃ¤hnt ist Java hauptsÃ¤chlich dazu da, an das Mac-OS-X-Aussehen heranzukommen. Was NeoOffice zum Laufen bringt, ist nicht Java selbst, sondern eher die Bibliotheken, die dabei sind, wie Java 2D zum Zeichnen und AWT fÃ¼r MenÃ¼s. Sie gehÃ¶ren schon zu Apple insofern als Java 2D eigentlich Quartz und AWT Carbon ist. [1]

DarÃ¼ber hinaus ist der Java-Anteil mit der Zeit geringer geworden. Als NeoOffice mit der OpenOffice.org-1.1.2-Codegrundlage aufgerÃ¼stet wurde (NeoOffice/J 1.1 Alpha), wechselte das Rendering von Texten von Java zu den ATSUI-APIs von Mac-OS-X, da sie wesentlich besser fÃ¼r komplexes Textlayout geeignet sind als Java. [2] Einige andere Funktionen hat es in Java noch nie gegeben (z.B. das Dock-MenÃ¼, das in NeoOffice/J 1.1 mit Carbon arbeitet und in neueren Versionen mit Cocoa)

Warum arbeitet ihr nicht an einer Cocoa-Version von Aqua OpenOffice.org?

There are several reasons. OpenOffice.org is not built like a native Cocoa Mac application. Translating all of the event model, font management and display routines into Cocoa would be a great deal of work. On the other hand, Apple's Java implementation provides good access to Aqua features and is easier to meld with the underlying OpenOffice.org code. NeoOffice/C proved that a Cocoa implementation was not a viable solution in the short-to-medium-term; while it looked great after a lot of hacks, it was not stable enough for even casual use.

DafÃ¼r gibt es mehrere GrÃ¼nde. OpenOffice.org ist nicht wie ein normales Cocoa-Programm fÃ¼r den Mac aufgebaut. Alle Routinen fÃ¼r Ereignisse, Fontmanagement und Darstellung in Cocoa umzuschreiben wÃ¤re eine Riesenarbeit. DemgegenÃ¼ber ermÃ¶glicht Apples Java-Implementation guten Zugriff auf Aqua-Funktionen und ist einfacher

As it stands, NeoOffice is very stable and quite far along towards providing a fully-Aquafied user interface, and taking a different path now would be to throw a lot of good code in the trash. The downside to using Java is that is consumes (somewhat) more resources than a pure Cocoa implementation would. (You need more RAM than the minimum requirements for Mac OS Xâ€”but then Mac OS X benefits from having more RAM than its minimum requirements!â€”and RAM is cheap; adding RAM is the most cost-efficient way to speed up your Mac.) Apple's improvements in Java 1.4.2 over Java 1.3.1 have actually allowed NeoOffice 1.2 Alpha to reduce resource usage and improve performance.

Ist Cocoa nicht besser als Java?

Aqua ist Aqua.

This question is most often asked by developers and power users. End users, on the other hand, tend to judge by the results. As one tester put it:

"If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant."

And, as John Gruber puts it, after quoting an Apple engineer posting to Carbon-Dev, "send [the second paragraph] to anyone who claims that only 'Cocoa apps are 'truly native' Mac OS X apps."

Ist Java nicht langsam?

The majority of NeoOffice is written in C++. Only those bits that facilitate an Aqua look in Mac OS X were customized to use Java. The reason is that Mac OS X Java looks terrific and hooks right into the native Aqua "blue-button" controls.

And by the wayâ€”Java isn't really that slow any more.

Weshalb benutzt NeoOffice nicht Java 1.5.x?

There are a number of reasons why NeoOffice uses Java 1.4.2, both human and technical. To start at the beginning, when the application was initially being developed (as NeoOffice/J), Java 1.4.x was not available on Mac OS X. When Java 1.4.1 did finally become available on Mac OS X, it proved to be quite buggy and was missing many key features on Mac OS X 10.2.x. Java 1.5 is only available on Mac OS X 10.4.x. Moreover, Java 1.4.x and 1.5 are Cocoa-based while Java 1.3.1 is Carbon-based. So for much of its early life as NeoOffice/J, the application used Java 1.3.1 on Mac OS X 10.2.x, 10.3.x, and 10.4.x.

Switching to a newer version of Java not only involved dropping support for users of older versions of Mac OS X but also required hundreds if not thousands of hours of time reimplementing the Carbon portions of the application in Cocoa and working around new bugs in the new Java versions. Thus switching to Java 1.4.x (or 1.5) was not a viable option for most of NeoOffice/J's existence given the size of the development team and the fact that Java 1.3.1 continued to work well.

Since Java 1.3.1 will not make the transition to Intel-based Macs, the summer of 2005 (July-September) was spent in full-time work to transition NeoOffice/J to Java 1.4.2, and October and most of November were spent (again full-time) fixing new bugs that arose in wider testing. NeoOffice 1.2 Alpha is the first release to require Java 1.4.2 and Mac OS X 10.3 or higher.

A transition to Java 1.5.x will not be as difficult since it is also Cocoa-based, but at the moment there are no plans to do so, as Java 1.5.x was only just released (mid-November 2005)â€”and only for Mac OS X 10.4.xâ€”and there are still many users running Mac OS X 10.3.x. Moreover, there are more important tasks ahead, such as MacIntel support, that require scarce developer resources. (Forcing NeoOffice/J 1.1 or NeoOffice 1.2 Alpha to use Java 1.5 will result in crashes and is not supported.)

Warum kann man nicht gtk oder Qt oder anderes plattformÃ¼bergreifendes Toolkit verwenden?

See Why aren't you working on a Cocoa version of an Aqua OpenOffice.org? and Isn't Cocoa better than Java? :-) The short answer is that reworking the OpenOffice.org codebase to use another toolkit would take at least as much time and work as it has taken to get NeoOffice to the point where it is today (two years of nearly full-time work by 1.5 developers and additional work before that), with no guarantees that it would be as stable.

Moreover, in the case of gtk, the ports to Mac OS X are older versions of gtk and fairly incomplete. Even in the case of Qt, which has a modern and complete Mac OS X port of the toolkit, the existing OpenOffice.org work would not benefit an Aqua version of OpenOffice.org at all. The Qt/KDE OpenOffice.org (Native Widget Framework effort) is not a "native Qt" implementation of vcl (OpenOffice.org's cross-platform windowing toolkit and abstraction layer). All of the underlying font handling, drawing, etc., is still done using X11; it's only the widget drawing that is using Qt's equivalent of the appearance manager.[3]

Was ist mit Intel-Macs?

See this FAQ for a detailed explanation of MacIntel issues and the latest developments.

Andere Fragen

Hat NeoOffice NeoOffice/C ersetzt?

Was ist mit NeoOffice/J passiert?

In recognition of the fact that the "classic" CoreGraphics/Cocoa port (NeoOffice/C) was a dead-end and no longer under development, as well as the fact that the "/J" was very confusing to many users and pundits, the application known as NeoOffice/J was renamed simply NeoOffice beginning with the 1.2 Alpha release.

Is there a Development Roadmap?

The direction of the NeoOffice project is typically discussed in the NeoOffice Development forum on trinity. The current (post-June 6, 2005) plans of NeoOffice's two primary developers are outlined in this topic.

Wo kann ich mehr Ã¼ber NeoOffice erfahren?

FÃ¼r Tips zur Benutzung von NeoOffice gehen Sie zu Tips und Tricks-Seite dieses Wiki.

Ich habe noch eine andere Frage zum Design oder zur Entwicklung von NeoOffice. Wo wird sie mir beantwortet?

Sehen Sie sich die offiziellen NeoOffice-FAQs an.
Durchsuchen Sie dieses Wiki
Durchsuchen Sie die Trinity-Foren
Falls Sie dann immer noch keine Antwort gefunden haben, stellen Sie Ihre Frage in der entsprechenden Rubrik des Trinity-Forums.

Dieser Artikel in anderen Sprachen: English

Retrieved from "https://neowiki.neooffice.org/index.php/De:NeoOffice_und_Aqua"

Categories: NeoOffice | NeoOffice/C | NeoWikiDE

 As it stands, NeoOffice is very stable and quite far along towards providing a fully-Aquafied user interface, and taking a different path now would be to throw a lot of good code in the trash. The downside to using Java is that is consumes (somewhat) more resources than a pure Cocoa implementation would. (You need more RAM than the minimum requirements for Mac OS Xâ€”but then Mac OS X benefits from having more RAM than its minimum requirements!â€”and RAM is cheap; adding RAM is the most cost-efficient way to speed up your Mac.)  Apple's improvements in Java 1.4.2 over Java 1.3.1 have actually allowed NeoOffice 1.2 Alpha to reduce resource usage and improve performance.
-=== Isn't Cocoa better than Java? ===
+=== Ist Cocoa nicht besser als Java? ===
-''Aqua is aqua''.
+''Aqua ist Aqua''.
 This question is most often asked by developers and power users. End users, on the other hand, tend to judge by the results. As one tester put it:
 And, as [http://daringfireball.net/linked/2005/may#tue-31-apis John Gruber] puts it, after quoting an [http://lists.apple.com/archives/Carbon-dev/2005/May/msg01121.html Apple engineer posting to Carbon-Dev], "send [the second paragraph] to anyone who claims that only 'Cocoa apps are 'truly native' Mac OS X apps."
-=== Isn't Java slow? ===
+=== Ist Java nicht langsam? ===
 The majority of NeoOffice is written in C++. Only those bits that facilitate an Aqua look in Mac OS X were customized to use Java. The reason is that Mac OS X Java looks terrific and hooks right into the native Aqua "blue-button" controls.
 And by the wayâ€”Java isn't really that slow any more.
-=== Why doesn't NeoOffice use Java 1.5.x? ===
+=== Weshalb benutzt NeoOffice nicht Java 1.5.x? ===
 There are a number of reasons why NeoOffice uses Java 1.4.2, both human and technical.  To start at the beginning, when the application was initially being developed (as NeoOffice/J), Java 1.4.x was not available on Mac OS X.  When Java 1.4.1 did finally become available on Mac OS X, it proved to be quite buggy and was missing many key features on Mac OS X 10.2.x.  Java 1.5 is only available on Mac OS X 10.4.x.  Moreover, Java 1.4.x and 1.5 are Cocoa-based while Java 1.3.1 is Carbon-based.  So for much of its early life as NeoOffice/J, the application used Java 1.3.1 on Mac OS X 10.2.x, 10.3.x, and 10.4.x.
 A transition to Java 1.5.x will not be as difficult since it is also Cocoa-based, but at the moment there are no plans to do so, as Java 1.5.x was only just released (mid-November 2005)â€”and only for Mac OS X 10.4.xâ€”and there are still many users running Mac OS X 10.3.x.  Moreover, there are more important tasks ahead, such as MacIntel support, that require scarce developer resources.  (Forcing NeoOffice/J 1.1 or NeoOffice 1.2 Alpha to use Java 1.5 '''will''' result in crashes and '''is not supported'''.)
-===Why not use gtk or Qt or some other cross-platform toolkit?===
+===Warum kann man nicht gtk oder Qt oder anderes plattformÃ¼bergreifendes Toolkit verwenden?===
 See [[NeoOffice_and_Aqua#Why_aren.27t_you_working_on_a_Cocoa_version_of_an_Aqua_OpenOffice.org.3F|Why aren't you working on a Cocoa version of an Aqua OpenOffice.org?]] and [[NeoOffice_and_Aqua#Isn.27t_Cocoa_better_than_Java.3F|Isn't Cocoa better than Java?]] :-)  The short answer is that reworking the OpenOffice.org codebase to use another toolkit would take at least as much time and work as it has taken to get NeoOffice to the point where it is today (two years of nearly full-time work by 1.5 developers and additional work before that), with no guarantees that it would be as stable.
 Moreover, in the case of gtk, the ports to Mac OS X are older versions of gtk and fairly incomplete.  Even in the case of Qt, which has a modern and complete Mac OS X port of the toolkit, the existing OpenOffice.org work would not benefit an Aqua version of OpenOffice.org at all. The Qt/KDE OpenOffice.org (Native Widget Framework effort) is not a "native Qt" implementation of vcl (OpenOffice.org's cross-platform windowing toolkit and abstraction layer).  All of the underlying font handling, drawing, etc., is still done using X11; it's only the widget drawing that is using Qt's equivalent of the appearance manager.[http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=2673#2673]
-===What about Intel-based Macs?===
+===Was ist mit Intel-Macs?===
 See [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=2230 this FAQ] for a detailed explanation of MacIntel issues and the latest developments.
-==Other Questions==
+==Andere Fragen==
-=== Has NeoOffice replaced NeoOffice/C? ===
+=== Hat NeoOffice NeoOffice/C ersetzt? ===
-[[NeoOffice/C Status|Yes]].
+[[NeoOffice/C Status|JA]].
-===What happened to NeoOffice/J?===
+===Was ist mit NeoOffice/J passiert?===
 In recognition of the fact that the "classic" CoreGraphics/Cocoa port ([[NeoOffice/C]]) was a dead-end and no longer under development, as well as the fact that the "/J" was very confusing to many users and pundits, the application known as NeoOffice/J was renamed simply NeoOffice beginning with the 1.2 Alpha release.
 The direction of the NeoOffice project is typically discussed in the [http://trinity.neooffice.org/modules.php?name=Forums&file=viewforum&f=9 NeoOffice Development forum on trinity].  The current ([http://www.apple.com/pr/library/2005/jun/06intel.html post-June 6, 2005]) plans of NeoOffice's two primary developers are outlined in [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1481 this topic].
-=== Where can I learn more about NeoOffice? ===
+=== Wo kann ich mehr Ã¼ber NeoOffice erfahren? ===
-For tips on using NeoOffice, see the [[NeoOffice_Tips_and_Hints|Tips and Hints]] section of this Wiki.
+FÃ¼r Tips zur Benutzung von NeoOffice gehen Sie zu [[NeoOffice_Tips_and_Hints|Tips und Tricks]]-Seite dieses Wiki.
-=== I have another question about the design or development of NeoOffice; where can I get an answer? ===
+=== Ich habe noch eine andere Frage zum Design oder zur Entwicklung von NeoOffice. Wo wird sie mir beantwortet? ===
-* Check out the [http://www.planamesa.com/neojava/faq.php official NeoOffice FAQ]
+* Sehen Sie sich die [http://www.planamesa.com/neojava/faq.php offiziellen NeoOffice-FAQs an.]
-* Search this wiki
+* Durchsuchen Sie dieses Wiki
-* Search the [http://trinity.neooffice.org/modules.php?name=Forums trinity Forums]
+* Durchsuchen Sie die [http://trinity.neooffice.org/modules.php?name=Forums Trinity-Foren]
-* If you still haven't found an answer, post your question in the appropriate section of the [http://trinity.neooffice.org/modules.php?name=Forums trinity Forums]
+* Falls Sie dann immer noch keine Antwort gefunden haben, stellen Sie Ihre Frage in der entsprechenden Rubrik des [http://trinity.neooffice.org/modules.php?name=Forums Trinity-Forums.]
 {{botlangbarDE|[[fr:NeoOffice/J et Aqua|FranÃ§ais]] [[NeoOffice and Aqua|English]]}}
 [[Category:NeoOffice]][[Category:NeoOffice/C]][[Category:NeoWikiDE]]