https://mediawiki.gnustep.org/api.php?action=feedcontributions&feedformat=atom&user=Martin 2026-04-11T16:25:48Z User contributions MediaWiki 1.35.7 https://mediawiki.gnustep.org/index.php?title=User:Martin&diff=6905 2016-11-26T23:15:29Z

<p>Martin: </p> <hr /> <div></div>

Martin https://mediawiki.gnustep.org/index.php?title=Building_GNUstep_with_Clang&diff=6904 2016-11-26T23:15:07Z

<p>Martin: Update link</p> <hr /> <div>1) Build using the instructions here: http://clang.llvm.org/get_started.html<br /> <br /> 2) Once that's done, download the latest version of Hans Boehm's garbage collector here: http://www.hboehm.info/gc/<br /> <br /> 3) Untar, Build and install boehm-gc.... it should be gc-7.1.tar.gz<br /> build it with clang like so:<br /> ./configure CC=clang LD=gcc &amp;&amp; make CC=clang LD=gcc<br /> make install<br /> <br /> 4) Build gnustep-make like so and install it:<br /> <br /> ./configure CC=clang LD=gcc &amp;&amp; make CC=clang LD=gcc<br /> make install<br /> <br /> 5) Build libobj2 and install it:<br /> make CC=clang CXX=clang++ LD=gcc<br /> make install<br /> <br /> 5) Build base, gui and back and install them:<br /> ./configure CC=clang CXX=clang++ LD=gcc &amp;&amp; make CC=clang CXX=clang++ LD=gcc messages=yes<br /> su<br /> . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh &amp;&amp; make GNUSTEP_INSTALLATION_DOMAIN=SYSTEM install<br /> <br /> That should be all there is too it. Not much, but a few little details which might serve to make it enough of a pain to discourage some people.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Unit_Testing&diff=5715 2009-11-09T19:37:28Z

<p>Martin: </p> <hr /> <div>'''Unit Testing''' is the practice of writing code that tests the code in your application and quickly determines if the code is working properly. The concept of unit testing is implemented in libraries for most modern languages, including Objective-C.<br /> <br /> ==Common Frameworks==<br /> There are several unit testing frameworks for Objective-C projects.<br /> * OCUnit, built in to Apple Xcode and open sourced. Version 27 (pretty old) has been tested with GNUstep<br /> * UnitKit, common for Mac OS X until OCUnit was built into Xcode. Now ported to Etoile.<br /> * ObjCUnit, a Mac OS X framework that has been ported to GNUstep.<br /> * TestKit, an inactive framework<br /> <br /> ==See also==<br /> * Mock objects</div>

Martin https://mediawiki.gnustep.org/index.php?title=Library_combos&diff=5704 2009-10-22T19:10:46Z

<p>Martin: </p> <hr /> <div>'''Library combos''' are compile-time decisions about which libraries and runtimes to use. Since the only other major libraries are from Apple, this applies only to [[Darwin]] and [[Mac OS X]].<br /> <br /> There are three libraries that can be linked to. The [[Objective-C runtime]], the [[Foundation]] implementation, and the [[AppKit]] implementation.<br /> <br /> Specifying which libraries to use is done with &lt;code&gt;./configure --with-library-combo=&lt;/code&gt;objcruntime-foundation-applicationkit. Each of the three could have either the value &lt;tt&gt;gnu&lt;/tt&gt; or &lt;tt&gt;apple&lt;/tt&gt;, but not all of these are implemented.<br /> <br /> The following options are supported:<br /> {|<br /> |-<br /> ! Runtime !! Foundation !! AppKit <br /> |-<br /> | GNU || GNU || GNU<br /> |-<br /> | Apple || GNU || GNU<br /> |-<br /> | Apple || Apple || GNU<br /> |-<br /> | Apple || Apple || Apple<br /> |}<br /> <br /> Of these, the first and last options are recommended (all GNU or all Apple). The default when building on Darwin and OS X is &lt;tt&gt;apple-apple-apple&lt;/tt&gt;. Even when GNUstep apps use the all Apple option, GNUstep extensions are available to the app.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5703 2009-10-22T19:09:04Z

<p>Martin: /* History */</p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' provides C functions and data structures required to execute an Objective C program. It is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> <br /> ==History==<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project re-wrote it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it. The biggest change Apple has made is supporting [[Objective-C 2.0]].<br /> <br /> The [[Etoile]] project maintained its own extension to the GNU runtime for a few years. This updated runtime added support for many of the features that Apple added. However, David Chisnall added all the features from the Etoile runtime into a framework that runs on top of the GNU runtime. This framework, &lt;tt&gt;ObjectiveC2.framework&lt;/tt&gt; obsoletes the Etoile runtime and makes it easier for regular GNUstep applications to use.&lt;ref&gt;[http://etoileos.com/news/archive/2009/09/10/1744/ The Étoilé Runtime is dead, long live the GNUstep runtime!]&lt;/ref&gt;<br /> <br /> ==Choosing a runtime==<br /> * The GNU runtime supports everything needed by traditional Objective-C applications. Apple calls this Objective-C 1.0. Nothing special needs to be done for a GNUstep application to use this runtime.<br /> * The Apple runtime from 10.0 to 10.4 is another runtime that supports Obj-C 1. Because this runtime is different from the GNUstep runtime, applications from Mac OS X will have to be re-compiled to run on GNUstep (they are not binary-compatible).<br /> * In Mac OS X 10.5 Apple introduced many new features to the runtime under the name Objective-C 2.0. None of these features were added to the GNUstep runtime.<br /> * The Etoile runtime added most of the features that Apple announced in Objective-C 2.0, but it was not possible for ordinary GNUstep applications to use. The Etoile runtime has been superseded by the ObjectiveC2 framework.<br /> * The ObjectiveC2 framework relies on the GNU runtime for most features, yet adds new features on top. It is possible for ordinary GNUstep applications to link to this framework and get the benefits of Objective-C 2.0.<br /> <br /> Of course, the Apple runtime is only available on Apple operating systems ([[Darwin]] and [[Mac OS X]]).</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5702 2009-10-22T19:06:21Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' provides C functions and data structures required to execute an Objective C program. It is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> <br /> ==History==<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project re-wrote it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it. The biggest change Apple has made is supporting [[Objective-C 2.0]].<br /> <br /> The [[Etoile]] project maintained its own extension to the GNU runtime for a few years. This updated runtime added support for many of the features that Apple added. However, David Chisnall added all the features from the Etoile runtime into a framework that runs on top of the GNU runtime. This framework, &lt;tt&gt;ObjectiveC2.framework&lt;/tt&gt; obsoletes the Etoile runtime and makes it easier for regular GNUstep applications to use.<br /> <br /> ==Choosing a runtime==<br /> * The GNU runtime supports everything needed by traditional Objective-C applications. Apple calls this Objective-C 1.0. Nothing special needs to be done for a GNUstep application to use this runtime.<br /> * The Apple runtime from 10.0 to 10.4 is another runtime that supports Obj-C 1. Because this runtime is different from the GNUstep runtime, applications from Mac OS X will have to be re-compiled to run on GNUstep (they are not binary-compatible).<br /> * In Mac OS X 10.5 Apple introduced many new features to the runtime under the name Objective-C 2.0. None of these features were added to the GNUstep runtime.<br /> * The Etoile runtime added most of the features that Apple announced in Objective-C 2.0, but it was not possible for ordinary GNUstep applications to use. The Etoile runtime has been superseded by the ObjectiveC2 framework.<br /> * The ObjectiveC2 framework relies on the GNU runtime for most features, yet adds new features on top. It is possible for ordinary GNUstep applications to link to this framework and get the benefits of Objective-C 2.0.<br /> <br /> Of course, the Apple runtime is only available on Apple operating systems ([[Darwin]] and [[Mac OS X]]).</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5701 2009-10-22T18:52:38Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' provides C functions and data structures required to execute an Objective C program. It is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> <br /> =History=<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project started to re-write it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it. The biggest change Apple has made is supporting [[Objective-C 2.0]].<br /> <br /> The [[Etoile]] project maintained its own extension to the GNU runtime for a few years. This updated runtime added support for many of the features that Apple added. However, David Chisnall added all the features from the Etoile runtime into a framework that runs on top of the GNU runtime. This framework, &lt;tt&gt;ObjectiveC2.framework&lt;/tt&gt; obsoletes the Etoile runtime and makes it easier for regular GNUstep applications to use.<br /> <br /> = Choosing a runtime =<br /> The GNU runtime supports everything needed by traditional Objective-C applications. Apple calls this Objective-C 1.0.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5700 2009-10-22T18:45:27Z

<p>Martin: /* GNU Objective C Compiler and Runtime */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** (Preferred Option): Get the source code via SVN:<br /> *** svn co http://svn.gna.org/svn/gnustep/autotest gnustep-testfarm<br /> ** (Alternate Option): ...Or download the source code and test files<br /> *** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> *** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> *** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> *** wget http://ftp.gnustep.org/pub/daily-snapshots/tests.current.tar.bz2<br /> *** tar xjf startup.current.tar.bz2 ; tar xjf core.current.tar.bz2; tar xjf tests.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to http://www.gnustep.org/developers/testfarm.html <br /> The test script will automatically update using SVN if possible.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The [[Objective-C runtime]] Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops etc.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X-Window. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X-Window? ===<br /> <br /> Display Ghostscript runs on top of X-Window.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5699 2009-10-22T18:42:24Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' provides C functions and data structures required to execute an Objective C program. It is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> =History=<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project started to re-write it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5698 2009-10-22T18:41:22Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' provides C functions and data structures required to execute an Objective C program.. It is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> =History=<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project started to re-write it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Library_combos&diff=5697 2009-10-22T18:36:37Z

<p>Martin: </p> <hr /> <div>'''Library combos''' are compile-time decisions about which libraries and runtimes to use. Since the only other major libraries are from Apple, this applies only to [[Darwin]] and [[Mac OS X]].<br /> <br /> There are three libraries that can be linked to. The [[Objective-C runtime]], the [[Foundation]] implementation, and the [[AppKit]] implementation.<br /> <br /> Specifying which libraries to use is done with &lt;code&gt;./configure --with-library-combo=&lt;/code&gt;objcruntime-foundation-applicationkit. Each of the three could have either the value &lt;tt&gt;gnu&lt;/tt&gt; or &lt;tt&gt;apple&lt;/tt&gt;, but not all of these are implemented.<br /> <br /> The following options are supported:<br /> {|<br /> |-<br /> ! Runtime !! Foundation !! AppKit <br /> |-<br /> | GNU || GNU || GNU<br /> |-<br /> | Apple || GNU || GNU<br /> |-<br /> | Apple || Apple || GNU<br /> |-<br /> | Apple || Apple || Apple<br /> |}<br /> <br /> Of these, the first and last options are recommended (all GNU or all Apple). The default when building on Darwin and OS X is &lt;tt&gt;apple-apple-apple&lt;/tt&gt;.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Platform_compatibility&diff=5696 2009-10-22T18:27:04Z

<p>Martin: /* Darwin */</p> <hr /> <div>{{stub}}<br /> <br /> Following are procedures for installing GNUstep on different Operating Systems.<br /> * You may also want to take a look at the [[dependencies]].<br /> <br /> <br /> = BSD-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:BSD|be found here]].<br /> <br /> <br /> = HP/UX =<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW/References_Manual#GNUstep_and_CPAM. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> <br /> = Linux-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Linux|be found here]].<br /> <br /> <br /> = Solaris =<br /> Take a look at the required and recommended [[dependencies]]. Most of these can be found at [http://www.blastwave.org/ BlastWave] (which I personally recommend) or [http://www.sunfreeware.com/ Sun Freeware].<br /> The notable exception are [http://www.haible.de/bruno/packages-ffcall.html ffcall]/[http://sources.redhat.com/libffi/ libffi], [http://www.apple.com/macosx/features/bonjour/ Bonjour] and [http://www.portaudio.com/ portaudio] (as of 2008-05-23).<br /> <br /> If you plan on compiling those from source, make sure to enable the creation of SHARED libraries. ''Bonjour'' and ''ffcall'' compile right out of the box. For ''portaudio'' to compile, you will need to grab a daily-snapshot and you need to install [http://www.blastwave.org/packages.php/osndsys Open Sound System headers].<br /> <br /> Then, if you follow the installation instructions for GNUstep, you should not run into any problems.<br /> <br /> === Intel ===<br /> <br /> ''Intentionally left blank''.<br /> <br /> === Sparc ===<br /> <br /> * http://www.linuks.mine.nu/gnustep/solaris is one of package sources to create Solaris packages for GNUstep.<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW#GNUstep_and_TWW_HPMS. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> === GNUstep Solaris 10 U2 vmware appliance ===<br /> <br /> * [http://developers.sun.com/solaris/downloads/solaris_apps/index.jsp Download sol u2 image], you need to have a Sun site account.<br /> * You can run this image in VMware server or VMware player 1.0.3.<br /> * Install Sun Studio 11 with latest patches.<br /> * Objective Compiler<br /> ** compile your own<br /> ** get it from [http://www.blastwave.org/ BlastWave] using pkg-get.<br /> * download all the GNUstep tar balls and follow build instruction.<br /> <br /> <br /> = OpenSolaris =<br /> <br /> This will be an add-on packages to OpenSolaris distributions using TWW tools to create SPARC/Intel packages in SVR4 formats. &quot;pkg-inst gnustep-user-1.0 gnustep-developer-1.0 gnustep-apps-1.0&quot; will install GNUstep user,developer and GNUstep native applications. pkg-rm will perform the reverse of installation.<br /> <br /> It will have a nice name like GNUstep O.S. (OpenSolaris).<br /> <br /> <br /> = Darwin =<br /> Two issues differentiate Darwin from its FreeBSD cousin.<br /> # Darwin uses the Apple [[Objective-C runtime]], not the GNU version<br /> # Darwin uses the Apple version of GCC, not the GNU version<br /> <br /> See [[Platform:BSD#Darwin]].<br /> <br /> = Windows =<br /> <br /> There are many Unix Environment solutions for windows. Currently GNUstep is using [http://www.mingw.org/ MingW] as its UNIX environment foundation for Windows.<br /> <br /> === MingW ===<br /> <br /> See [[Installation on Windows]] for details on MingW setup. Also look at precompiled binary installer, available from [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/ GNUstep's ftp site].<br /> <br /> <br /> = Others =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Other|be found here]].<br /> <br /> <br /> [[Category:Development]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=Objective-C_runtime&diff=5695 2009-10-22T18:25:30Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> The '''Objective-C runtime''' is low-level code that makes your applications work. Every Objective-C program links to the runtime, and the runtime manages objects, looks up methods, and implements the features of Objective-C.<br /> =History=<br /> The first Objective-C runtime was created by [[NeXT]] in the 1980s for their implementation of Obj-C and NeXTSTEP. The GNU project started to re-write it in 1992. This runtime was significantly modified in 1993 by Kresten Krab Thorup. Since then, there have been two runtimes evolving in parallel.<br /> <br /> When Jobs returned to Apple, he brought with him NeXTSTEP's code. The Obj-C runtime used in Apple's [[Mac OS X]] is inherited from NeXT. Apple has made many changes to it.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Library_combos&diff=5694 2009-10-22T18:20:25Z

<p>Martin: </p> <hr /> <div>'''Library combos''' are compile-time decisions about which libraries and runtimes to use. Since the only other major libraries are from Apple, this applies only to [[Darwin]] and [[Mac OS X]].<br /> <br /> There are three libraries that can be linked to. The [[Objective-C runtime]], the [[Foundation]] implementation, and the [[AppKit]] implementation.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Platform_compatibility&diff=5693 2009-10-22T18:00:38Z

<p>Martin: </p> <hr /> <div>{{stub}}<br /> <br /> Following are procedures for installing GNUstep on different Operating Systems.<br /> * You may also want to take a look at the [[dependencies]].<br /> <br /> <br /> = BSD-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:BSD|be found here]].<br /> <br /> <br /> = HP/UX =<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW/References_Manual#GNUstep_and_CPAM. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> <br /> = Linux-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Linux|be found here]].<br /> <br /> <br /> = Solaris =<br /> Take a look at the required and recommended [[dependencies]]. Most of these can be found at [http://www.blastwave.org/ BlastWave] (which I personally recommend) or [http://www.sunfreeware.com/ Sun Freeware].<br /> The notable exception are [http://www.haible.de/bruno/packages-ffcall.html ffcall]/[http://sources.redhat.com/libffi/ libffi], [http://www.apple.com/macosx/features/bonjour/ Bonjour] and [http://www.portaudio.com/ portaudio] (as of 2008-05-23).<br /> <br /> If you plan on compiling those from source, make sure to enable the creation of SHARED libraries. ''Bonjour'' and ''ffcall'' compile right out of the box. For ''portaudio'' to compile, you will need to grab a daily-snapshot and you need to install [http://www.blastwave.org/packages.php/osndsys Open Sound System headers].<br /> <br /> Then, if you follow the installation instructions for GNUstep, you should not run into any problems.<br /> <br /> === Intel ===<br /> <br /> ''Intentionally left blank''.<br /> <br /> === Sparc ===<br /> <br /> * http://www.linuks.mine.nu/gnustep/solaris is one of package sources to create Solaris packages for GNUstep.<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW#GNUstep_and_TWW_HPMS. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> === GNUstep Solaris 10 U2 vmware appliance ===<br /> <br /> * [http://developers.sun.com/solaris/downloads/solaris_apps/index.jsp Download sol u2 image], you need to have a Sun site account.<br /> * You can run this image in VMware server or VMware player 1.0.3.<br /> * Install Sun Studio 11 with latest patches.<br /> * Objective Compiler<br /> ** compile your own<br /> ** get it from [http://www.blastwave.org/ BlastWave] using pkg-get.<br /> * download all the GNUstep tar balls and follow build instruction.<br /> <br /> <br /> = OpenSolaris =<br /> <br /> This will be an add-on packages to OpenSolaris distributions using TWW tools to create SPARC/Intel packages in SVR4 formats. &quot;pkg-inst gnustep-user-1.0 gnustep-developer-1.0 gnustep-apps-1.0&quot; will install GNUstep user,developer and GNUstep native applications. pkg-rm will perform the reverse of installation.<br /> <br /> It will have a nice name like GNUstep O.S. (OpenSolaris).<br /> <br /> <br /> = Darwin =<br /> Two issues differentiate Darwin from its FreeBSD cousin.<br /> # Darwin uses the Apple [[Objective-C runtime]], not the GNU version<br /> # Darwin uses the Apple version of GCC, not the GNU version<br /> <br /> It is recommended to compile GNUstep with the GNU version of GCC, not Apple's version. (See the file &lt;tt&gt;README.Darwin&lt;/tt&gt; for more info. Furthermore, since Darwin includes Apple's runtime, you must decide which to use at compile time. For more information, see [[Library combos]].<br /> <br /> = Windows =<br /> <br /> There are many Unix Environment solutions for windows. Currently GNUstep is using [http://www.mingw.org/ MingW] as its UNIX environment foundation for Windows.<br /> <br /> === MingW ===<br /> <br /> See [[Installation on Windows]] for details on MingW setup. Also look at precompiled binary installer, available from [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/ GNUstep's ftp site].<br /> <br /> <br /> = Others =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Other|be found here]].<br /> <br /> <br /> [[Category:Development]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=Talk:Emacs.app&diff=5691 2009-10-21T18:29:14Z

<p>Martin: </p> <hr /> <div>==Version==<br /> Since the latest version is a branch of the original (since July 2008), I think the download link to the 9.0r1 should be removed. --[[User:Martin|Martin]] 20:29, 21 October 2009 (CEST)</div>

Martin https://mediawiki.gnustep.org/index.php?title=Cross_Compiling&diff=5258 2008-06-09T02:52:57Z

<p>Martin: cleanup</p> <hr /> <div>Cross Compiling and GNUstep depends on what you want to achieve.<br /> <br /> The following is based on [http://groups.google.com/group/gnu.gnustep.discuss/browse_frm/thread/06920400aed740d2 this discussion] on the mailing list.<br /> <br /> == I have a GNUstep source running on Linux/GNUstep and want the same application to run on OSX ==<br /> <br /> You have several options - more or less complex.<br /> <br /> === Copy source files to OSX and use gnustep-make ===<br /> <br /> The simplest, and best option is obviously to install [[Media:FOSDEM2007Make-2.0.pdf|gnustep-make]] on your Mac.<br /> <br /> curl ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.0.5.tar.gz<br /> ./configure<br /> make<br /> sudo make install<br /> <br /> and then compile your project by typing 'make'. You get a native Apple OSX application compiled against the Apple OSX ObjC frameworks ... using <br /> the same GNUmakefiles you were using on GNU/Linux/*BSD/Windows. :-)<br /> --N. Pero<br /> <br /> <br /> Additionally to the already suggested use of Xcode, you can build GNUstep on OS X with the apple-apple-apple combo.<br /> While this might need a tweak or two to work, this gives you a thin layer of GNUstep (its additions) onto what Cocoa already provides. <br /> --Markus Hitter<br /> <br /> === Copy source files to OSX and build using Xcode ===<br /> <br /> Add a wrapping Xcode project (in addition to the GNUstep makefile) and configure it to compile directly on OSX for OSX using the OSX Cocoa frameworks.<br /> You can share the sources e.g. through SVN.<br /> There is no problem having GNUmakefiles and some .xcodeproj in the same source code directory. <br /> <br /> Examples:<br /> 1. SWK Browser from the GNUstep SWK project, DataBuilder from <br /> 2. GSCoreData (look into the sources at www.gna.org) <br /> <br /> Development is done by either working on Linux and using GORM/Project Center and compiling for Linux, or on OSX opening the project in Xcode.<br /> The only thing to keep in mind is that you must also update the Xcode project or the GNUmakefile if you add source files or resources. <br /> The GNUstep .app bundle is different and runs on Linux only.<br /> The OSX .app bundle runs only on OSX, i.e. there is no single bundle that covers all architectures (unless you do some additional tricks). <br /> <br /> === Install GNUstep on OSX using MacPorts ===<br /> <br /> Then, you can set up an identical build environment on both machines. <br /> The drawback is that you don't have a &quot;native&quot; OSX application which you can easily launch by a double-click on the .app icon. <br /> <br /> Benoit Astruc writes: I think I have done this : <br /> - I installed GNUstep Make and BaseAdditions on Mac OS X 10.3 (it was 2 years ago so not the Make 2.0 version, I don't know if it works with <br /> the new version), <br /> - I used a GNUmakefile like this one : <br /> # This usually happens when you source GNUstep.sh, then run ./configure, <br /> # then log out, then log in again and try to compile <br /> ifeq ($(GNUSTEP_MAKEFILES),) <br /> $(error You need to run the GNUstep configuration script before compiling!) <br /> endif <br /> include $(GNUSTEP_MAKEFILES)/common.make <br /> APP_NAME = WRP <br /> WRP_MAIN_MODEL_FILE = MainMenu <br /> WRP_APPLICATION_ICON = WRP.icns <br /> WRP_PRINCIPAL_CLASS = NSApplication <br /> WRP_RESOURCE_FILES = gui/* Images/* Resources/* <br /> WRP_OBJC_FILES = main.m \ <br /> ... <br /> snip a bunch of sources files <br /> ... <br /> DEGeneralPrefsController.m \ <br /> GSStringCat.m <br /> include GNUmakefile.preamble <br /> include $(GNUSTEP_MAKEFILES)/application.make <br /> <br /> There was a trick however, the first time I had to write manually some file, WRPInfo.plist if I remember well, and then it was used. <br /> I don't do anything on this app since 2 years ago so I don't remember well, but I am pretty sure I had nothing more to do.<br /> And the result was a perfectly Mac OS X app build with GNUstep make. <br /> <br /> <br /> === Real cross-compiling (building on Linux for MacOS X) ===<br /> <br /> This means that you have a gcc version on your Linux machine that emits executables that run on OSX. Unfortunately, OSX uses MACH-O binaries and building a cross-compiling gcc is very tricky. <br /> So I would not consider this as a reasonable option.<br /> <br /> == I have an Xcode project and want to run on Linux ==<br /> <br /> a) your target machine has a compiler <br /> Here, you have to check that you are not using too specific <br /> frameworks. Then, add a GNUmakefile. Copy the files to your Linux <br /> system and run the GNUstep makefile. <br /> <br /> b) your target machine is an embedded system <br /> In this case, you need a cross-compiler on the build host. This can be <br /> a full Linux machine or a OSX machine (but it is more difficult to get <br /> a working cross-compiler running on OSX).</div>

Martin https://mediawiki.gnustep.org/index.php?title=User:Martin/myskin.css&diff=5109 2008-03-11T17:26:44Z

<p>Martin: </p> <hr /> <div>/* &lt;pre&gt;&lt;nowiki&gt;*/<br /> @import url(&quot;http://www.bleb.org/software/maemo/wikipedia/myskin.css&quot;);<br /> /* &lt;/nowiki&gt;&lt;/pre&gt; */</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSMutableString&diff=5108 2008-03-10T21:56:48Z

<p>Martin: </p> <hr /> <div>[http://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSString.html#class$NSMutableString NSMutableString] inherits from [[NSString]], but includes methods for changing the string.<br /> <br /> == Editing Strings ==<br /> <br /> === Adding To Strings ===<br /> <br /> Strings can be added on to by appending the new substring to the end, or by inserting it any where in the middle.<br /> <br /> ==== Appending Strings ====<br /> <br /> The simplest way to edit a string is by appending to the end of the string, as shown here:<br /> <br /> NSMutableString *str = @&quot;short string&quot;;<br /> [str appendString: @&quot; made longer&quot;];<br /> // str is now = @&quot;short string made longer&quot;<br /> <br /> C style formating flags can also be used as follows:<br /> <br /> NSMutableString *str = @&quot;short string&quot;;<br /> [str appendFormat: @&quot; made longer %@.&quot;, @&quot;with formating&quot;];<br /> // str is now = @&quot;short string made longer with formating.&quot;<br /> <br /> ==== Inserting Substrings ====<br /> <br /> The more advanced method of adding to strings in by insertion, as demonstrated here:<br /> <br /> NSMutableString *str = @&quot;a string&quot;;<br /> [str insertString: @&quot;new &quot; atIndex: 2];<br /> // str is now = @&quot;a new string&quot;<br /> <br /> === Replacing Substrings ===<br /> <br /> A certain substring can be replaced with a new one as follows:<br /> <br /> NSMutableString *str = @&quot;a old string&quot;;<br /> [str replaceString: @&quot;old&quot; withString: @&quot;new];<br /> // str is now = @&quot;a new string&quot;<br /> <br /> This can also be done with ranges:<br /> <br /> NSMutableString *str = @&quot;a old string&quot;;<br /> NSRange range = {2, 3};<br /> // start at index 2 and include the next 3 characters<br /> [str replaceCharactersInRange: range withString: @&quot;new];<br /> // str is now = @&quot;a new string&quot;<br /> <br /> <br /> [[Category:Foundation]]<br /> [[Category:Snippets]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=DesktopServicesKit&diff=4883 2007-10-28T03:47:42Z

<p>Martin: add link</p> <hr /> <div>== Proposal for a Desktop Services Framework ==<br /> <br /> With [[Camaelon]] theming, GNUstep applications may be able to offer an &quot;almost native&quot; experience in alien environments like Windows and MacOS.<br /> <br /> To avoid significant and repetitive modifications to applications which may require some support from the native desktop environment or provide services to other applications (classic low-threshhold activities such as handling MIME and file types, all the way through to native file dialogs and gateways into local accessibility services), it may be sensible to begin work on a DesktopServicesKit.<br /> <br /> The following is a limited list of common desktop services offered (to one extent or another) by environments like KDE, GNOME, Windows, MacOS, Etoile and ...:<br /> * desktop notifications and information<br /> * file and directory dialogs<br /> * printing services and dialogs<br /> * registration of MIME and file-type handling capabilities<br /> * native application helper launch and termination <br /> * gateway from GNUstep accessibility framework (does it exist yet?) to local platform<br /> * privilege escalations<br /> <br /> This would logically be complemented by a rather lighter System Services Framework to deal with native operating system issues such as networking, disk, volume, filesystem and file metadata, capabilities and permissions management, authentication services, etc.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Writing_portable_code&diff=4882 2007-10-28T03:36:34Z

<p>Martin: /* Xcode conversion */ add link</p> <hr /> <div>GNUstep opens up some fairly interesting opportunities to target a number of platforms with the same source code, for example porting Mac OS X Cocoa applications to Linux, the BSDs, other Unices and (ultimately) Windows without significant re-engineering effort or degraded end-user functionality. <br /> <br /> Some portability gotchas are listed below (please update when you run into a new one!):<br /> <br /> == Porting Applications ==<br /> <br /> === Porting from NeXTSTEP (NX*) to GNUstep ===<br /> <br /> For this you should have access to an old OPENSTEP installation, or find a friend who has one, otherwise you're simply better off just rewriting the application from scratch. There are some scripts which can be used to convert an application from NeXTSTEP to OPENSTEP located in &lt;tt&gt;/NextDeveloper/OpenStepConversion/ConversionScripts&lt;/tt&gt;. They use a scripting language called &quot;tops&quot;. I haven't been able, as yet, to locate a version of tops for Linux or any other operating system other than Mac OS X or OPENSTEP/Mach or NeXTSTEP. There are a few conversion applications which basically just use the tops scripts to do the conversion. They are actually two versions of the same program, but the second one doesn't run on NeXT, so here's both. These are:<br /> <br /> * [ftp://next-ftp.peak.org/openstep/mach/apps/devtools/Conversion.0.5.NI.tar.gz]<br /> * [ftp://next-ftp.peak.org/openstep/mach/apps/devtools/ConversionII.1.0.I.tar.gz]<br /> <br /> You should be able to point it at the project directory you wish to convert and start the conversion. The GUI is very straightforward. You can also run the tops scripts on a Mac simply by saying:<br /> <br /> tops -verbose -scriptfile {scriptfilename} {filestoconvert}<br /> <br /> All of the files are converted in place. You must run all of the tops scripts in the ConversionScripts directory against the application code. It is considerably simply to use the existing applications. Unfortunately these scripts do not exist on Mac OS X, otherwise porting the Conversion application might be useful.<br /> <br /> When you start the scripts, if you're running them on black hardware you should go get a cup of coffee and watch a movie with your wife or go code something else for a while. The conversion will take a good long while on an older machine. I haven't timed it on the Mac, though. Once this is done, there is still a long way to go. Read on.<br /> <br /> OPENSTEP4.2/Mach had a class called NSCStringText. This class was primarily for apps which were converted from NeXTSTEP to use as a stop-gap measure in OpenStep. This is one of the main reasons why it isn't in GNUstep. You will need to make sure that any classes modified by the scripts to use NSCStringText will use NSText and it's related classes as appropriate. OPENSTEP4.2/Mac also had some other extensions on the OpenStep standard such as NXStreams. You will also need to convert any and all instances of NXStream to use NSData instead in order to make your app work with GNUstep.<br /> <br /> If your app is fairly small, you shouldn't be in for a great shock, but if your app is heavily reliant on the old Text object from NeXTSTEP, you have a lot of work ahead. Other gaps which the scripts might leave are problems with NSUserDefaults which it can't fix on it's own.<br /> <br /> === Porting from Cocoa or OPENSTEP (NS*) to GNUstep ===<br /> <br /> Porting from Cocoa or OPENSTEP to GNUstep has different aspects. First there is the compatibility of the basic Foundation Kit and Application Kit. We support a lot of classes, but not all of them and the same is true for specific methods, specifically newly introduced classes and methods in Cocoa may still be missing as GNUstep started out aiming at OpenStep compatibility.<br /> <br /> Second you have all the additional frameworks and libraries programmers on Mac OS X take for granted, for some of them free replacements exists, for most they are still missing. Mac OS X developers should try and avoid CoreFoundation as this will complicate your dependency situation on non-Mac hosts, even if that part of CoreFoundation has actually been ported. GNUstep Base and the FoundationKit offer many parts of the CoreFoundation functionality in a natural [[Objective-C]] manner. To be a bit more specific:<br /> <br /> * don't use Core* (CoreFoundation, CoreSound, CoreAnimation, ...)<br /> * don't use KeyChain<br /> * don't use Carbon<br /> * don't use Quartz<br /> * don't use QuickTime<br /> * don't use WebKit (GCC 4.1 and up support ObjC++, but currently, there exists no WebKit port for GNUstep)<br /> * don't use altivec features or the vecLib.framework (a collection of functions for vector manipulation, an Apple specific extension)<br /> * don't use anything else we do not provide<br /> <br /> If you committed none of these portability evils, the rest is relatively straightforward:<br /> <br /> # [[Writing Makefiles|Write a new GNUstep make file]] for the project (very easy, still there is currently no automatic way to do so).<br /> # Make sure the Nib files are readable by GNUstep.<br /> ## When saving a NIB file in project builder, ensure that &quot;10.2 or later&quot; format is selected. Also, ensure that &quot;Use text archive format&quot; is NOT checked, as this created problems.<br /> ## Another option is to load them into Gorm and convert them into .gorm files. If they're from OPENSTEP or Mac OS X 10.1 or earlier, see [[#Porting_.nib_files_from_OPENSTEP_or_Mac_OS_X_10.1_and_earlier|below]].<br /> # Provide an Info.plist.<br /> <br /> === Porting from GNUstep to Cocoa ===<br /> <br /> This should be an easy transition since GNUstep implements most of Cocoa, except for the very Apple specific classes such as the scripting extensions. Since Gorm does not yet save .nib files, you will need to create the interfaces using IB. Also there is a gorm reading/parsing framework for Cocoa in the works as well, so please stay tuned.<br /> <br /> Will need to:<br /> <br /> * Make a Project Builder project for your app or<br /> * an Xcode project for your app<br /> <br /> Do the following:<br /> <br /> * Open Xcode.<br /> * Choose Application (if your project is an application)<br /> * Enter the name and location you wish the Project to reside at<br /> * Copy your files from your GNUstep application into the new project<br /> * Using the &quot;Add Existing Files&quot; option to add these file to your project.<br /> <br /> You should preserve your original directory structure if you want to distribute one package for both GNUstep and Cocoa.<br /> <br /> == Stumbling Blocks ==<br /> <br /> === Apple's Cocoa.h ===<br /> <br /> It is there to enable pre-compiled headers and speed up compile time thusly. Anyway, it contains just two lines:<br /> <br /> #import &lt;Foundation/Foundation.h&gt;<br /> #import &lt;AppKit/AppKit.h&gt;<br /> <br /> On older GNUstep systems, you may have to work around this by providing your own or replace your include of &lt;Cocoa/Cocoa.h&gt; with just the above, which will also work on OS-X.<br /> <br /> === Distinguishing Between Cocoa and GNUstep ===<br /> <br /> #ifdef GNUSTEP<br /> ''/* GNUstep code goes here ... */''<br /> #else<br /> ''/* OS-X Cocoa native code goes here ... */''<br /> #endif<br /> <br /> === Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier ===<br /> <br /> On Mac OS X, this is a simple matter of loading the .nibs into InterfaceBuilder.app and saving them in the new format. Another possibility is using nib2gmodel, the only one when porting from OPENSTEP, and mind you, you need to do the converting ''there''. First, get [http://freshmeat.net/projects/nib2gmodel/ nib2gmodel], follow the included instructions to build and install it. Once that's done you're ready to begin:<br /> <br /> Run the nib2gmodel program on your nib:<br /> <br /> nib2gmodel mygui.nib mygui.gmodel<br /> <br /> This should create the .gmodel as a plist. I recommend that you convert the gmodel to a &quot;normal&quot; plist instead of an XML plist. You can do that by doing this on OS X:<br /> <br /> pl &lt; mygui.gmodel -output mygui.ser<br /> pl &gt; mygui.gmodel -input mygui.ser<br /> rm mygui.ser<br /> <br /> Now you can either use the gmodel as it is, or you can convert it to a .gorm file.<br /> <br /> ==== Gmodel to .gorm conversion ====<br /> <br /> NOTE: Conversion from gmodel to .gorm is experimental and will probably remain so for a while. It currently works in the majority of cases, but there are still improvements which need to be made.<br /> <br /> Conversion to a .gorm file is relatively straightforward:<br /> <br /> * Start Gorm.app.<br /> * Choose Gorm-&gt;Document-&gt;Open and find the gmodel you wish to load.<br /> * Gorm will prompt you to either define the superclass for classes it doesn't know about or to parse the headers. <br /> <br /> After you've defined all of the unknown classes, Gorm should complete the conversion. Once this is done you should save the result to make sure you don't loose your work.<br /> <br /> === Xcode conversion ===<br /> <br /> * how to convert Xcode project to GNUstep project (creating a GNUstep [http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/index.html Makefile] or [[ProjectCenter]])<br /> <br /> * [[pbxbuild]]<br /> <br /> * PBTOMAKE. [http://www.macdevcenter.com/pub/a/mac/2004/04/20/xcodetounix.html xcodetounix] (download at [http://members.bellatlantic.net/%7Evze35xda/software.html]) is a tool for converting Xcode and Project Builder files to generic Unix Makefiles. It would probably be a good start for converting to a GNUstep makefile.<br /> <br /> == Notes ==<br /> <br /> === Do not rely on tools available in development environment ===<br /> <br /> All the world is not Linux or FreeBSD or Windows. System constants may be different on different platforms. Paths to command-line tools, the parameters they accept and locations of temporary directories may be different to what you are used to on your platform.<br /> <br /> * [[Foundation|GNUstep Base]] and the [[Foundation|FoundationKit]] offer some of this functionality &quot;for free&quot;.<br /> * Try not to hard code paths and so on into your code, use macros (not recommended), or even better an abstraction mechanism.<br /> * Avoid hard-coding system constants, or platform-specific ones where POSIX or commonly-accepted ones exist (and we're not talking about glibc here :-)<br /> * Try to avoid advanced features of the linker, such as weak symbols, which may not be present on non-ELF systems. While this will work perfectly on most systems, it is not portable to all systems, most notably Windows.<br /> <br /> === When platform-specific code cannot be avoided ===<br /> <br /> There are cases where you may need to write platform-specific code, especially in the case of desktop applications and services which make use of facilities not standardised by POSIX or by the FoundationKit and AppKit specifications, at least use [[Identifying the target platform|standard platform macros]].<br /> <br /> These platform-specific, or even desktop-specific requirements could be re-used by other projects - and even enhance desktop-integration efforts for GNUstep applications - by abstracting out common code into currently hypothetical [[PlatformKit]] and [[DesktopServicesKit]] frameworks.<br /> <br /> [[Category:Project procedures]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=Pbxbuild&diff=4858 2007-10-17T05:05:56Z

<p>Martin: add category</p> <hr /> <div>'''Pbxbuild''' (not to be confused with [http://www.hmug.org/man/1/pbxbuild.php the OS X tool of the same name]) is used to take Xcode project files and build the code. It does this by creating GNUmakefiles, and using [[Make]] to build those.<br /> <br /> It reads &lt;tt&gt;.xcodeproj&lt;/tt&gt; or &lt;tt&gt;.xcode&lt;/tt&gt; files and parses them to determine the structure. Then it re-creates that structure with a makefile. It does not inspect the source code, so it cannot guarantee that an OS X project will compile on GNUstep.<br /> <br /> Hans Baier created pbxbuild in 2006, and it's distributed with the GNUstep tools.<br /> <br /> [[Category:Development]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=Pbxbuild&diff=4857 2007-10-17T04:55:21Z

<p>Martin: Created article</p> <hr /> <div>'''Pbxbuild''' (not to be confused with [http://www.hmug.org/man/1/pbxbuild.php the OS X tool of the same name]) is used to take Xcode project files and build the code. It does this by creating GNUmakefiles, and using [[Make]] to build those.<br /> <br /> It reads &lt;tt&gt;.xcodeproj&lt;/tt&gt; or &lt;tt&gt;.xcode&lt;/tt&gt; files and parses them to determine the structure. Then it re-creates that structure with a makefile. It does not inspect the source code, so it cannot guarantee that an OS X project will compile on GNUstep.<br /> <br /> Hans Baier created pbxbuild in 2006, and it's distributed with the GNUstep tools.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Application_wish_list&diff=4737 2007-05-20T15:10:07Z

<p>Martin: /* Networking */</p> <hr /> <div>What applications do you want for GNUstep? Please check the [[:Category:Applications|list of applications]] before adding.<br /> <br /> == Database ==<br /> <br /> === Database management ===<br /> <br /> A desktop software (like [http://www.flex.ro/pgaccess/ PgAccess] for example) to manage database. This program could use the GDL2 (Gnustep Database Library). It could be a good exercice and demonstration of this very good library.<br /> <br /> == Development ==<br /> <br /> === Project Management app ===<br /> <br /> Something like [http://mrproject.codefactory.se/screenshots.php MrProject]. It has to be simple, not overbloated as MS Project.<br /> <br /> === nib2gmodel/nib2gorm without OPENSTEP/MacOSX ===<br /> GORM can open NIB files created with MacOSX 10.2 and later. OPENSTEP/MacOSX is still needed for older NIB files.<br /> <br /> === CVS app ===<br /> <br /> Port CVL.<br /> <br /> === F-Script ===<br /> [http://www.fscript.org/ F-Script] is useful for examining applications' properties and various Objective-C objects. It's FOSS, but I don't think there's a GNUstep port yet.<br /> <br /> == Graphics ==<br /> <br /> === Blender ===<br /> <br /> Blender has recently (since October 2002) gone GPL. Consisting of porting the Blender GUI/WM abstract library GHOST, using NSOpenGLContext, or a CoreGraphics implementation one day. Objective-C++ might be needed for implementing GHOST, but probably can be worked around easily enough. There is an OSX port, probably using CoreGraphics.<br /> <br /> [http://www.blender.org/ Blender Foundation Homepage]<br /> <br /> Most of Blender is written in C++ doesn't seem to use CoreGraphics but Apple's GL.<br /> <br /> === OmniGraffle clone ===<br /> <br /> (I don't really know what this is, but people have said they want one. Someone please add a description! :)<br /> <br /> This is for diagram, UML ....<br /> I 'm thinking to write it. But not *right now*.<br /> It will have probably a Gorm-feel<br /> <br /> [http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] was a clone of Lighthouse Design's Diagram.app, which was a re-working of the NeXT Developer Example Sketch.app, adding rubber-banding / angular connection lines.<br /> <br /> === OmniOutliner clone ===<br /> <br /> This is a really cool app which can be used for anything. Mostly i think it is used to organise your minds while being creative (some kind of knowledge manager).<br /> <br /> The inspiration for this was Jayson Adams' Millennium Software's NoteBook.app, which lives again as the (commercial) program [http://www.aquaminds.com/ NoteTaker].<br /> <br /> === Painting app (photoshop) ===<br /> <br /> Bitmap drawing app.<br /> <br /> Think Photoshop, not [http://www.gimp.org/ The Gimp].<br /> <br /> In fact, forget that. Something new.<br /> <br /> Something usable - can do Photoshop, but easy to learn. The Gimp can nearly do photoshop, but who can use it?<br /> <br /> It would be great if it consisted of two parts - a very small very useful image viewer/manager (eg gqview) and the actual editor plugin (the big part). So installing image-core would give a very small useful app, then adding image-edit would make it into photoshop.<br /> <br /> When opening an image file eg by clicking on it or running image-core thefile.jpg then only the core apps should start, so it starts real quick. If i right-click and choose edit or something .. THEN the other stuff is pulled in.<br /> <br /> Or whatever. Just an idea. But makes development path cool. Could also have a vector plugin, or whatever.<br /> <br /> Maybe we should wait, when (if?) Gimp gets '[http://gegl.org/ gegl]'ed.<br /> then having a decent photoshop like app would be as simple as writing a gui for the gegl foundation.<br /> + gives us a nice featureset + plugins!<br /> <br /> Maliwan project is aiming to achieve the same goal of GEGL. Right now GEGL isn't even half complete but we can still reimplement it base on GEGL's design. lastlife is waiting for you in irc if you want to discuss the idea. Maliwan is planned to be the heart of the BluTulip which is the actual application.<br /> <br /> * porting http://seashore.sourceforge.net/ from their website: Seashore is an open source image editor for Cocoa. It features gradients, textures and anti-aliasing for both text and brush strokes. It supports multiple layers and alpha channel editing. It is based around the GIMP's technology and uses the same native file format.<br /> <br /> a screenshot is here: [http://seashore.sourceforge.net/screenshot.php] which looks very clean and easy to use.<br /> <br /> === Pixen (Pixel Art Tool) ===<br /> <br /> [http://www.opensword.org/ Pixen] is a decent, open source pixel art tool and there aren't alot of free or professional programs like it. There is also a compliment tool by the same guys for mapping called Reptile.<br /> <br /> A port can be found [http://home.gna.org/gsimageapps/ here].<br /> <br /> == MultiMedia ==<br /> <br /> === iTunes/Rhythmbox clone ===<br /> <br /> It would be nice to see a music or video player with real music/media management like [http://www.gnome.org/projects/rhythmbox/ Rhythmbox] or [http://www.apple.com/itunes/ iTunes]. iTunes has started to support management of movies and videoclips, so maybe media management is the way to go?<br /> <br /> === DivX/XViD/DVD/VCD Player ===<br /> <br /> I see that there was at least an attempt to port mplayer at one point but it seems to be dead. Maybe [http://www.videolan.org/ VLC] which does have an OSX version, could be ported.<br /> <br /> : ''Looks cool, but requires CoreFoundation'' -- cbv<br /> <br /> I'd like to see [http://www.dtek.chalmers.se/groups/dvd/ Ogle] (a DVD player) ported. [[User:Martin|Martin]]<br /> <br /> : ''As far as I can see, Ogle (the actual player) doesn't really need porting, only Ogle-gui (the user interface add-on), which is GTK2 based'' -- cbv<br /> <br /> == Networking ==<br /> <br /> === ICQ ===<br /> <br /> And other instant messengers.<br /> <br /> * Check http://freshmeat.net/projects/fireapp/<br /> * See [[Grouch]].<br /> <br /> === Web browser ===<br /> <br /> Seems to be a popular request :).<br /> <br /> * Work is on the way to bring [[SimpleWebKit]], a small WebKit compatible library up to working condition. [[SimpleWebKit]] is part of the GNUstep project and can be found in the SVN. This library will allow the creation of a simple web browser, such as [[Vespucci.app]].<br /> <br /> * The WebKit project has also offered their support to anyone who wishes to port WebKit to GNUstep, [http://lists.gnu.org/archive/html/discuss-gnustep/2007-03/msg00290.html see this e-mail]. This framework would allow the creation of a fully functional web browser.<br /> <br /> === Web services app ===<br /> A [http://www.karelia.com/developer/watson/ Watson] / Sherlock clone would be useful to me.<br /> <br /> === Video conferencing software ===<br /> <br /> There's [http://www.gnomemeeting.org/ Ekiga] (excellent piece of software) which it no longer dependent on the GNOME libraries to work but looses some functionality.<br /> * Would be nice to have a GNUstep native application that could use the same protocols (SIP and H.323).<br /> <br /> == PIM ==<br /> <br /> === Task management app ===<br /> <br /> Chronographer (lobbying by ludovic) + libical<br /> or<br /> ~TaskManager (lobbying by Fabien) + libical<br /> <br /> Check SKYRIX libs (Opengroupware)<br /> <br /> == Security ==<br /> ===Keychain===<br /> I want a better Keychain. I need an architecture and app to securely store not just usernames and passwords, but also other useful data. Think associated email / verification method, SSH passwords and keys, email public and private keys, and user-defined name-value pairs (for unforeseen uses, this facilitates micro-formats, like a standard for voicemail PIN etc). And a pony!<br /> <br /> Apple indicates that their KeyChain is derived from the open-source Common Data Security Architecture, so such a project would not have to start from scratch. I'm unsure how useful the third-party open-source [http://sourceforge.net/projects/keychain Keychain Framework] would be.<br /> <br /> ''The above mentioned keychain on SourceForge depends on Apple's own 'Security' framework. I'm not sure how much of it is publicly available (and if so, portable)'' -- cbv<br /> <br /> == Text Processing / Office ==<br /> <br /> === Abiword (Word Processor) ===<br /> <br /> A port of the Cocoa version of [http://www.abisource.com/ AbiWord] would be great, considering a word processor is a pretty vital application, and that Abiword is a pretty good one.<br /> <br /> === Spreadsheet ===<br /> <br /> A spreadsheet application would be great for GNUstep. A clone of Lotus Improv or Lighthouse Design's Parasheet would be a nice thing for GNUstep to have.<br /> <br /> : You could look at porting [http://www.materialarts.com/FlexiSheet/ FlexiSheet]; it's the only Cocoa FOSS spreadsheet I know of. Coincidentally, it has a couple of ideas borrowed from Lotus Improv.<br /> <br /> === CSS/html editor ===<br /> <br /> A cool html/css editor - emphasis on the css structural side.<br /> <br /> Object oriented properties application to CSS element definitions, and insert those properties into HTML in web pages. Don't worry about WYSIWIG - that's what web browsers are for, displaying web pages. Just make a object-oriented CSS/HTML editor.<br /> <br /> Maybe port [http://www.w3.org/People/Berners-Lee/WorldWideWeb.html Nexus] for that?<br /> <br /> ''This might actually be feasible, however, Nexus is based on [http://www.w3.org/Library/ libwww] and its source is, well, very NeXTSTEP'ish...'' -- cbv<br /> <br /> === A simple DTP application ===<br /> <br /> A simple frame-based application for desktop publishing. Something like [http://www.calamus.net/ Calamus] ([http://www.calamus.net/man/index_us.htm here] is the documentation of tools and modules). Nothing fancy, just application that can lay out frames, control text flow, use paragraph styles and master pages.<br /> <br /> I'd rather see TeXView.app come back myself.... I think it's far more feasible (doing a decent page layout app is _hard_ just as Donald E. Knuth). Perhaps better still would be to take advantage of LyX's ``GUI-independence'' and provide a GNUstep front-end for it, http://www.lyx.org .<br /> <br /> No, nothing like LyX or TeX. I have in mind a ''visual'' page layout editing tool with features as described above (similar to PageMaker). LyX and TeX are a bit different approaches and should be alternatives to Frame based DTP application.<br /> <br /> - Stefan<br /> <br /> I think a heavy-weight drawing package w/ page layout features would be a better solution here (this is the workflow I'm using on my NeXT Cube now), then it could be tied into an XML-based workflow in a fashion like to Apple's new Keynote, perhaps in a fashion like to Pages-by-Pages. To describe my workflow a bit---I now use Altsys Virtuoso on my NeXT Cube w/ Omega (Unicode-aware TeX variant) for most of my page layout. IME, if a document gets too large to manage w/ Altsys Virtuoso, it might as well go into TeX... Not that I'd mind seeing a replacement for PasteUp.app, I just think that a drawing program is more immediately important / useful.<br /> <br /> For simple DTP utility, I'd dearly love to see a re-creation of [http://members.aol.com/willadams/gnustep/apps/type/touchtype.html TouchType.app]<br /> <br /> - William<br /> <br /> Maybe you should take a look at [http://www.texmacs.org/ TeXmacs]. Looks promising and is in great need of a GNUstep frontend.<br /> <br /> - david.<br /> <br /> Interesting. I'd seen TeXMacs mentioned on comp.text.tex quite often, but hadn't realized it had gotten as far as it had. Interesting counterpoint to LyX.<br /> - William<br /> <br /> One really interesting thing would be to have a fame class which would useful enough so it could be used to put together a simple DTP Application but which would be flexible enough that it could be available to any application - the text control is a standard control for windows managers like MS Windows or Gnome. If there were an equivalent &quot;flowing graphic control&quot;, you'd have a powerful building block indeed (note that in MS windows, the text control is actually poor enough that no credible application can built around besides notepad).<br /> Also, for a programming text editor, scintilla is great. One thing to consider is that for DTP/HTML editor, what you would want would be a *superset* of the scintilla interface. It would be great to add all the different features in such a way that you didn't have interfaces duplicating each other's functionalities.<br /> <br /> -- JosephSolbrig<br /> <br /> === Digital Librarian-like ===<br /> <br /> I would really, really like a Digital Librarian for GNUstep. Basically, imagine an application that manage your documents the same way iTunes manage your music or iPhoto your photos... (to take well-known OSX apps as example ;-)<br /> <br /> It would provide 1) automatic management of the documents by projects/ideas/whatever metadata 2) index your documents to let you search quickly in it 3) handles bibliography<br /> As a postgrad student I have a LOT of articles in PDF/PS/DVI/html on my hard drive, and such an application would be really nice to help managing that.<br /> <br /> * How about something like [http://debian.uni-essen.de/misc/GNUstep/Apps/GNUlibrarian/ GNULibrarian]? I was just browsing the other day and found it! [[User:Stefanbidi|Stefanbidi]]<br /> <br /> == Misc ==<br /> <br /> === Old NeXTSTEP/OPENSTEP apps ===<br /> See [http://www.levenez.com/NeXTSTEP/meApps.html this side (in French)] for a list.<br /> <br /> === Frontend for different platform to [http://www.granddictionnaire.com/ Grand Dictionnaire (in French)] ===<br /> <br /> === Keyboard switcher application ===<br /> <br /> === Google.app ===<br /> <br /> * Complete with ApplicationServices<br /> * WebBrowser integration<br /> * Using proper NS* classes for HTML retrieval<br /> * Ability to select which Google server (www.google.ca, www.google.co.jp)<br /> * Google News, Google Groups, Google Images too.<br /> <br /> Hns: his looks more like a general WebBrowser than a special Google.app<br /> <br /> === DMG.app? ===<br /> <br /> * Installer/extractor/viewer for DMG images.<br /> * Create DMG packages<br /> * Useful for OSX source packages<br /> <br /> ''Note:'' The DMG format is Apple proprietary and undocumented. Basically, DMG support is only available under OSX and its unlikely to change.<br /> <br /> === CronniX - A cron front end ===<br /> <br /> http://www.abstracture.de/projects-en/cronnix<br /> <br /> That won't be easily portable, as different OSs use a different cron setup. Eg. BSD has (and uses) both, /etc/crontab __and__ /var/cron/tabs/&lt;username&gt; ...<br /> <br /> === PfaEdit - A font editor ===<br /> <br /> PfaEdit has its name changed to [http://fontforge.sourceforge.net/ FontForge].<br /> <br /> Actually, Cenon (see above) is able to do some limited font editing. Not to knock pfaedit, I use it a lot and think it's a way cool program. Wonder if the two could be merged somehow.<br /> <br /> === GuileServices / StepTalk Services ===<br /> <br /> On NeXTSTEP there was an application (service?) called [http://www.doubleu.com/TickleServices.html TickleServices] that allowed you to write your own services in the Tcl language. Something along these lines, but using guile/steptalk would be a nice addition to gnustep.<br /> <br /> === Printer.app ===<br /> <br /> An application/framework for managing printers, printer properties and print queues. (CUPS frontend?) (NOTE: To an extent, GNUstep already has CUPS support, and has number of builtin classes and panels for managing printers and printer settings. They may just need to be extended a little for different uses and environments.)<br /> <br /> === Growl! (Global notification system) ===<br /> <br /> [http://growl.info/ Growl!] uses distributed notification center to display a graphic message on screen. Every application can send messages to it, for example, when new emails arrive, buddies sign in the instant messager, a task end, etc. It is very easy to implement.<br /> <br /> ''Parts require CoreFoundation and/or WebKit'' -- cbv<br /> <br /> Perhaps the CoreFoundation bits could be handled by [http://developer.apple.com/opensource/cflite.html CF-Lite].<br /> <br /> ''Since about version 299 CoreFoundation doesn't compile properly anymore on systems other than Darwin.'' -- [[User:Cbv|cbv]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=KVO_Bindings_Project&diff=4732 2007-05-13T03:44:53Z

<p>Martin: </p> <hr /> <div>== People ==<br /> <br /> Student: Christopher Farber<br /> <br /> Mentor: Nicola Pero<br /> <br /> == Overview ==<br /> KVO and bindings lead to faster, easier application development, and cleaner code. It also brings GNUstep closer to compiling most [[Cocoa]] code without modification. Key Value Observing is necessary to implement bindings, and would increase the flexibility of GNUstep's KeyValueCoding implementation. Bindings support would eliminate the need for most outlets and controller code that deals with updating the GUI controls, while reinforcing the separation between Controller and View in the Model-View-Controller design pattern.<br /> <br /> == Deliverables ==<br /> Creating the classes: <br /> * NSController<br /> * NSArrayController<br /> * NSObjectController<br /> * NSValueTransformer<br /> Adding bindings support for existing classes; for example NSTextField, NSPopUpButton, and NSProgressIndicator<br /> == Milestones ==<br /> <br /> {To be agreed}<br /> <br /> == Progress ==<br /> <br /> None (project not officially started)</div>

Martin https://mediawiki.gnustep.org/index.php?title=Summer_Of_Code_2007&diff=4731 2007-05-13T03:39:40Z

<p>Martin: link</p> <hr /> <div>The [http://code.google.com/soc/ Summer Of Code] is a Google program that offers student developers stipends to create new freely available programs or to help currently established projects. This year, GNUstep had two projects accepted:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Project<br /> ! Student<br /> ! Mentor<br /> |-<br /> | [[Text_System_Project|Improving GNUstep AppKit components and the Text System]]<br /> | Christopher Elsmore<br /> | David Chisnall<br /> |-<br /> | [[KVO Bindings Project|Key Value Observing and Bindings implementation]]<br /> | Christopher Farber<br /> | Nicola Pero<br /> |}<br /> <br /> The original [[Summer_Of_Code_Ideas|proposed ideas]] are maintained for historical interest, and for students thinking of applying next year. <br /> <br /> === Mentors ===<br /> <br /> The following agreed to provide additional mentoring, and answer questions for students in addition to their assigned mentors:<br /> <br /> * Adam Fedor (Also main administrator)<br /> * Nicolas Roard<br /> * Richard Frith-Macdonald</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4727 2007-04-30T00:28:21Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundle&lt;/tt&gt; additions / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> |- <br /> | &lt;tt&gt;NSButton&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonic&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Mnemonics are not supported in Mac OS X.<br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonicLocation&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;attributedAlternateTitle&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;setAlternateMnemonicLocation&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;setAlternateTitleWithMnemonic&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | TODO: We should underline this character<br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;setAttributedAlternateTitle&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4726 2007-04-30T00:26:14Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundle&lt;/tt&gt; additions / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> |- <br /> | &lt;tt&gt;NSButton&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonic&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Mnemonics are not supported in Mac OS X.<br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonicLocation&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;attributedAlternateTitle&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;setAlternateMnemonicLocation&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;setAlternateTitleWithMnemonic&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | TODO: We should underline this character<br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4725 2007-04-30T00:19:28Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundle&lt;/tt&gt; additions / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> |- <br /> | &lt;tt&gt;NSButton&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonic&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Mnemonics are not supported in Mac OS X.<br /> |- <br /> | &lt;tt&gt;NSButtonCell&lt;/tt&gt; / &lt;tt&gt;alternateMnemonicLocation&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4721 2007-04-23T03:51:41Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundle&lt;/tt&gt; additions / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> |- <br /> | &lt;tt&gt;NSButton&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4720 2007-04-23T03:48:37Z

<p>Martin: typos</p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundle&lt;/tt&gt; additions / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4719 2007-04-23T03:44:03Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutosaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBundleAdditions&lt;/tt&gt; / &lt;tt&gt;contextHelpForKey&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBundle_AppKitAdditions/Reference/Reference.html Apple's docs] list the changes<br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4687 2007-04-11T23:58:04Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutosaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;image&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/image??<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowserCell&lt;/tt&gt; / &lt;tt&gt;setImage&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | or use NSCell/setImage??<br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4686 2007-04-11T23:47:55Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutosaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser sizeToFitWidthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser notification&lt;/tt&gt; / &lt;tt&gt;NSBrowserColumnConfigurationDidChangeNotification&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=ApplicationKitCompatibility&diff=4685 2007-04-11T23:42:56Z

<p>Martin: </p> <hr /> <div>{|border=&quot;1&quot;<br /> ! Class / method<br /> ! MacOS X version<br /> ! Status<br /> ! Comments<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIColor&lt;/tt&gt; Additions <br /> | 10.4 <br /> | Not Implemented <br /> |<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;CIImage&lt;/tt&gt; Additions<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSActionCell&lt;/tt&gt;<br /> | 10.0<br /> | Looks Good<br /> | <br /> |-<br /> | &lt;tt&gt;NSAffineTransform&lt;/tt&gt; Additions<br /> | 10.0<br /> | Looks Good<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAlert&lt;/tt&gt; / &lt;tt&gt;alertWithError&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAnimation&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSAppleScript&lt;/tt&gt; Addition<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;activateIgnoringOtherApps&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | The app is always activated unconditionally<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Currently just centers window on the screen<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginModalSessionForWindow relativeToWindow&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;runModalSession&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Apple's docs state that, before processing the events, it makes the session window key and orders the window front. This method does not attempt to do this because: 1) we don't want to interfere with use of other apps during modal session for this app; 2) occasionally other windows are active and should be usable during modal sessions (e.g., a popup dialog from a modal window); 3) most of the time &lt;tt&gt;beginModalSessionForWindow&lt;/tt&gt; will have been called in advance. If the latter is not the case, you may need to order the window front yourself in advance.<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;beginSheet modalForWindow modalDelegate didEndSelector contextInfo&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Under GNUstep, the sheet aspect is not implemented (just centers window on the screen), but &lt;tt&gt;modalDelegate&lt;/tt&gt; &lt;tt&gt;didEndSelector&lt;/tt&gt; is called if both non-nil.<br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |-<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;endSheet returnCode&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;preventWindowOrdering&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;hide&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | On OS X this activates the next app that is running, however on GNUstep this is up to the window manager<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedDocuments&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;orderedWindows&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | OS X scripting method to return windows in front-to-back on-screen order for scriptable windows. The GNUstep implementation returns all the windows excluding &lt;tt&gt;NSPanel&lt;/tt&gt;s. some backends may return an array in an unspecified order.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;cancelUserAttentionRequest&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;requestUserAttention&lt;/tt&gt;<br /> | 10.1<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSApplication&lt;/tt&gt; / &lt;tt&gt;replyToOpenToPrint&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSArrayController&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSATSTypesetter&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;appendBezierPathWithPackedGlyphs&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;getLineDash count phase&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: How big is the pattern array?<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;stroke&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |-<br /> | &lt;tt&gt;NSBezierPath&lt;/tt&gt; / &lt;tt&gt;fill&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: I don't see how this should work with color changes<br /> |- style=&quot;background-color:yellow;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorizeByMappingGray toColor blackMapping whiteMapping&lt;/tt&gt;<br /> | 10.0<br /> | Behaves Differently<br /> | Does nothing<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initWithBitmapDataPlanes pixelsWide pixelsHigh bitsPerSample samplesPerPixel hasAlpha isPlanar colorSpaceName bitmapFormat bytesPerRow bitsPerPixel&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;initForIncrementalLoad&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;bitmapFormat&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |-<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;representationOfImageRepsInArray usingType properties&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: returns only the first image in the array, and only works for &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; or subclasses thereof.<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;incrementalLoadFromData complete&lt;/tt&gt;<br /> | 10.2<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;colorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setColorAtX Y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;getPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBitmapImageRep&lt;/tt&gt; / &lt;tt&gt;setPixel atX y&lt;/tt&gt;<br /> | 10.4<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;boxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setBoxType&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBox&lt;/tt&gt; / &lt;tt&gt;setTitle&lt;/tt&gt;<br /> | 10.0<br /> | Not Implemented<br /> | <br /> |- <br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;displayColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | FIXME: why the following? Are we displaying now, or marking for &lt;em&gt;later display&lt;/em&gt;?? Given the name, I think we are displaying &lt;em&gt;now&lt;/em&gt;.<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;titleheight&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | Nextish look requires 21 here ( hardcode )<br /> |-<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;frameOfInsideOfColumn&lt;/tt&gt;<br /> | 10.0<br /> | ?<br /> | xxx what does this one do?<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnContentWidthForColumnWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnWidthForColumnContentWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnResizingType&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setPrefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;prefersAllColumnUserResizing&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setWidth ofColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;widthOfColumn&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;setColumnsAutoSave&lt;em&gt;Name&lt;/em&gt;&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | I cannot find &lt;tt&gt;setColumnsAutoSave&lt;/tt&gt; at [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSBrowser_Class/Reference/Reference.html Apple's docs], but I can find &lt;tt&gt;setColumnsAutoSaveName&lt;/tt&gt;. [[User:Martin|Martin]] 06:59, 17 March 2007 (CET)<br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;columnAutoSaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser&lt;/tt&gt; / &lt;tt&gt;removeSavedColumnsWithAutosaveName&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |- style=&quot;background-color:orange;&quot;<br /> | &lt;tt&gt;NSBrowser delegate&lt;/tt&gt; / &lt;tt&gt;browser shouldSizeColumn forUserResize toWidth&lt;/tt&gt;<br /> | 10.3<br /> | Not Implemented<br /> | <br /> |}<br /> <br /> <br /> <br /> TODO wiki [http://www.sonappart.net/gnustep/AppKit_Compat.html that]</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSData&diff=4673 2007-04-09T05:20:40Z

<p>Martin: rewording</p> <hr /> <div>'''NSData''' is a class in Foundation for working with binary data that does not fit any specific type. Methods are provided that work with generic data, such as reading and writing files, working with data in memory, and obtaining data over the network.<br /> <br /> The data that an NSData object holds can come from a file, from a memory location, or from the network. Methods are provided that can move the data between all three of these. NSData is immutable, so a similar mutable type '''NSMutableData''' is provided (also in &lt;tt&gt;NSData.h&lt;/tt&gt;). GNUstep defines extensions to NSData for use with shared memory. Also GNUstep adds methods to calculate a checksum and obtain various representations of the data (e.g. hexadecimal).<br /> <br /> NSData inherits from [[NSObject]]. It is declared in &lt;tt&gt;Foundation/NSData.h&lt;/tt&gt; and conforms to [[NSCoding]], [[NSCopying]], and NSMutableCopying.<br /> <br /> [[Category:Foundation]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSData&diff=4672 2007-04-09T05:19:19Z

<p>Martin: overview</p> <hr /> <div>'''NSData''' is a class in Foundation for working with binary data that does not fit any specific type. Methods are provided that work with generic data, such as reading and writing files, working with data in memory, and obtaining data over the network.<br /> <br /> The data that an NSData object holds can come from a file, from a memory location, or from the network. Methods are provided that can move the data between all three of these. NSData is immutable, so a similar mutable type '''NSMutableData''' is provided (also in &lt;tt&gt;NSData.h&lt;/tt&gt;). GNUstep also defines extensions to NSData for use with shared memory. Also GNUstep adds methods to calculate a checksum and obtain various representations of the data (e.g. hexadecimal).<br /> <br /> NSData inherits from [[NSObject]]. It is declared in &lt;tt&gt;Foundation/NSData.h&lt;/tt&gt; and conforms to [[NSCoding]], [[NSCopying]], and NSMutableCopying.<br /> <br /> [[Category:Foundation]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSBundle&diff=4671 2007-04-09T05:12:07Z

<p>Martin: typo</p> <hr /> <div>'''NSBundle''' is a class in Foundation for the manipulation of bundles. Bundles are specialized directories that collect related resources for an application or framework (or even an ordinary file) and present them to a user as a single, opaque file. Common resources are images, NIB or GORM interface files, localizations, and executable binaries.<br /> <br /> NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate [[localization]]s, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: &lt;tt&gt;bundleForLibrary&lt;/tt&gt; and &lt;tt&gt;pathForLibraryResource&lt;/tt&gt;. However, these two extensions are experimental and might change.<br /> <br /> NSBundle inherits from [[NSObject]] and is declared in &lt;tt&gt;Foundation/NSBundle.h&lt;/tt&gt;.<br /> <br /> [[Category:Foundation]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSBundle&diff=4670 2007-04-09T05:00:54Z

<p>Martin: </p> <hr /> <div>'''NSBundle''' is a class in Foundation for the manipulation of bundles. Bundles are specialized directories that collect related resources for an application or framework (or even an ordinary file) and present them to a user as a single, opaque file. Common resources are images, NIB or GORM interface files, localizations, and executable binaries.<br /> <br /> NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate [[localization]]s, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: &lt;tt&gt;bundleForLibrary&lt;/tt&gt; and &lt;tt&gt;pathForLibraryResource&lt;/tt&gt;. However, these two extensions are experimental and might change.<br /> <br /> NSBundle inherits from [[NSObject]] and is defined in &lt;tt&gt;Foundation/NSBundle.h&lt;/tt&gt;.<br /> <br /> [[Category:Foundation]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=NSBundle&diff=4669 2007-04-09T04:56:31Z

<p>Martin: Introduction in layman's terms and note GS extensions</p> <hr /> <div>'''NSBundle''' is a class in Foundation for the manipulation of bundles. Bundles are specialized directories that collect related resources for an application or framework (or even an ordinary file) and present them to a user as a single, opaque file. Common resources are images, NIB or GORM interface files, localizations, and executable binaries.<br /> <br /> NSBundle is mostly used to find the executable code for a given bundle (and vice versa), to choose appropriate [[localization]]s, and to locate other resources in a bundle's directory. Currently GNUstep defines two methods in addition to those from OpenStep: &lt;tt&gt;bundleForLibrary&lt;/tt&gt; and &lt;tt&gt;pathForLibraryResource&lt;/tt&gt;. However, these two extensions are experimental and might change.<br /> <br /> [[Category:Foundation]]</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4663 2007-04-04T20:06:47Z

<p>Martin: </p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> [http://interfacewm.sourceforge.net/ Interface WM] defines the following, but they might not be necessary:<br /> Atom gnustep_wm_attr;<br /> Atom gnustep_titlebar_state;<br /> Atom gnustep_wm_miniaturizable_window;<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. [http://standards.freedesktop.org/wm-spec/wm-spec-latest.html Extended Window Manager Hints] defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.<br /> <br /> =Menus=<br /> Again, because there are no real hints about which one is the main menu and submenu besides window level, it is hard to find the correct one. So menus are treated as regular windows in most cases.<br /> <br /> Besides the focus issue, there is also a boundary issue. Say the user puts the mouse on the right edge of the screen and clicks the right button (bringing up a menu): the main menu will be off of the right boundary. GNUstep tries to move it back, and some window managers also try to move it back. When a window is moved, the mouse tracking may be offset. After the main menu is open, a user clicks on a submenu, which will also be off of the right boundary. Then should the window manager move both the main menu and submenu to the left? Does GNUstep do that? It is not clear which one should do what.<br /> <br /> And now, some people like to have a horizontal menu (like Mac OS X) instead of a vertical menu (like NEXTSTEP). They behave differently for submenus. For a horizontal menu, the submenu will close on an action fire. For a vertical menu, the submenu will stay open after an action fire. So I guess only GNUstep can handle it.<br /> <br /> =Window Resizing and Moving=<br /> GNUstep defines:<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> I didn't see it in Window Maker, therefore, I don't know whether it is really supported. But it may be key for some windows turning black when resizing.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Talk:NSString&diff=4662 2007-04-04T19:54:51Z

<p>Martin: </p> <hr /> <div>I have changed the &quot;Constant Strings&quot; section to the &quot;Constructing Strings&quot; section, and add more ways to create a string object.<br /> <br /> --[[User:Kendall|Kendall]] 02:50, 4 April 2007 (CEST)<br /> :: Nice job. [[User:Martin|Martin]] 21:54, 4 April 2007 (CEST)</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4661 2007-04-04T19:43:57Z

<p>Martin: /* Window Level */</p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. [http://standards.freedesktop.org/wm-spec/wm-spec-latest.html Extended Window Manager Hints] defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.<br /> <br /> =Menus=<br /> Again, because there are no real hints about which one is the main menu and submenu besides window level, it is hard to find the correct one. So menus are treated as regular windows in most cases.<br /> <br /> Besides the focus issue, there is also a boundary issue. Say the user puts the mouse on the right edge of the screen and clicks the right button (bringing up a menu): the main menu will be off of the right boundary. GNUstep tries to move it back, and some window managers also try to move it back. When a window is moved, the mouse tracking may be offset. After the main menu is open, a user clicks on a submenu, which will also be off of the right boundary. Then should the window manager move both the main menu and submenu to the left? Does GNUstep do that? It is not clear which one should do what.<br /> <br /> And now, some people like to have a horizontal menu (like Mac OS X) instead of a vertical menu (like NEXTSTEP). They behave differently for submenus. For a horizontal menu, the submenu will close on an action fire. For a vertical menu, the submenu will stay open after an action fire. So I guess only GNUstep can handle it.<br /> <br /> =Window Resizing and Moving=<br /> GNUstep defines:<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> I didn't see it in Window Maker, therefore, I don't know whether it is really supported. But it may be key for some windows turning black when resizing.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4616 2007-03-30T04:26:06Z

<p>Martin: </p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.<br /> <br /> =Menus=<br /> Again, because there are no real hints about which one is the main menu and submenu besides window level, it is hard to find the correct one. So menus are treated as regular windows in most cases.<br /> <br /> Besides the focus issue, there is also a boundary issue. Say the user puts the mouse on the right edge of the screen and clicks the right button (bringing up a menu): the main menu will be off of the right boundary. GNUstep tries to move it back, and some window managers also try to move it back. When a window is moved, the mouse tracking may be offset. After the main menu is open, a user clicks on a submenu, which will also be off of the right boundary. Then should the window manager move both the main menu and submenu to the left? Does GNUstep do that? It is not clear which one should do what.<br /> <br /> And now, some people like to have a horizontal menu (like Mac OS X) instead of a vertical menu (like NEXTSTEP). They behave differently for submenus. For a horizontal menu, the submenu will close on an action fire. For a vertical menu, the submenu will stay open after an action fire. So I guess only GNUstep can handle it.<br /> <br /> =Window Resizing and Moving=<br /> GNUstep defines:<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> I didn't see it in Window Maker, therefore, I don't know whether it is really supported. But it may be key for some windows turning black when resizing.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4615 2007-03-30T04:23:43Z

<p>Martin: /* Menu */</p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.<br /> <br /> =Menus=<br /> Again, because there are no real hints about which one is the main menu and submenu besides window level, it is hard to find the correct one. So menus are treated as regular windows in most cases.<br /> <br /> Besides the focus issue, there is also a boundary issue. Say the user puts the mouse on the right edge of the screen and clicks the right button (bringing up a menu): the main menu will be off of the right boundary. GNUstep tries to move it back, and some window managers also try to move it back. When a window is moved, the mouse tracking may be offset. After the main menu is open, a user clicks on a submenu, which will also be off of the right boundary. Then should the window manager move both the main menu and submenu to the left? Does GNUstep do that? It is not clear which one should do what.<br /> <br /> And now, some people like to have a horizontal menu (like Mac OS X) instead of a vertical menu (like NEXTSTEP). They behave differently for submenus. For a horizontal menu, the submenu will close on an action fire. For a vertical menu, the submenu will stay open after an action fire. So I guess only GNUstep can handle it.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4614 2007-03-30T04:16:28Z

<p>Martin: </p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.<br /> <br /> =Menu=<br /> Again, because there are no real hints about which one is the main menu and submenu besides window level, it is hard to find the correct one. So menus are treated as regular windows in most cases.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4613 2007-03-30T04:08:18Z

<p>Martin: </p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.<br /> <br /> =Focus=<br /> X has focused and unfocused window, GNUstep has key window and main window, plus menu and app icon. I don't know how the chain of focus should go when the window and menu are up and down. But again, if there is a hint for the main window, key window, main menu, etc, it will be easy for the window manager to know where the focus should go. A documentation of how the focus should shift from which to which may help.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4612 2007-03-30T04:03:15Z

<p>Martin: /* App Icon */</p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).<br /> <br /> EWMH defines &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt; for app icon image. GNUstep supports it, but I am not sure if it is updated when the app icon image is changed. And if people use app icon as a &lt;tt&gt;NSWindow&lt;/tt&gt; and draw directly on it, there is no way the window manager will know. The solution is that if there is a notification that the icon is redrawn, the window manager or GNUstep can copy (or take a screenshot of) the image from that &lt;tt&gt;NSWindow&lt;/tt&gt; and put it into &lt;tt&gt;_NET_WM_ICON&lt;/tt&gt;. It requires something like &lt;tt&gt;XCopyArea()&lt;/tt&gt;.</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4611 2007-03-30T03:58:11Z

<p>Martin: </p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;<br /> <br /> =App Icon=<br /> GNUstep used to have &lt;tt&gt;NSDockWindowLevel&lt;/tt&gt;, but it is deprecated. So to know which window is the app icon, you have to first find a GNUstep window, check its &lt;tt&gt;group_leader&lt;/tt&gt;, (See &lt;tt&gt;XWMHints&lt;/tt&gt; in X protocols), then check its &lt;tt&gt;icon_window&lt;/tt&gt; which points to app icon. Again, it will be easier if there is hint (see above).</div>

Martin https://mediawiki.gnustep.org/index.php?title=Window_manager&diff=4610 2007-03-30T03:40:18Z

<p>Martin: /* Window Type */</p> <hr /> <div>In Windows and Mac OS X the window manager is tied into the OS. That's not the case for Linux or BSD. [[Window Maker]] is the recommended window manager for GNUstep, but a standard feature-set is needed. GNUstep-based applications have additional needs beyond traditional window managers, like handling the dock icon or the menus. Collecting the requirements here will lead to a specification, so any window manager can clearly state whether or not it is GNUstep-compliant.<br /> <br /> =Backend WM Attributes=<br /> Headers/x11/XGServerWindow.h defines<br /> unsigned long flags<br /> unsigned long window_style<br /> unsigned long window_level<br /> unsigned long reserved<br /> Pixmap miniaturize_pixmap; // pixmap for miniaturize button<br /> Pixmap close_pixmap; // pixmap for close button.<br /> Pixmap miniaturize_mask; // miniaturize pixmap mask<br /> Pixmap close_mask; // close pixmap mask<br /> unsigned long extra_flags;<br /> <br /> #define GSWindowStyleAttr (1&lt;&lt;0)<br /> #define GSWindowLevelAttr (1&lt;&lt;1)<br /> #define GSMiniaturizePixmapAttr (1&lt;&lt;3)<br /> #define GSClosePixmapAttr (1&lt;&lt;4)<br /> #define GSMiniaturizeMaskAttr (1&lt;&lt;5)<br /> #define GSCloseMaskAttr (1&lt;&lt;6)<br /> #define GSExtraFlagsAttr (1&lt;&lt;7)<br /> #define GSDocumentEditedFlag (1&lt;&lt;0)<br /> #define GSWindowWillResizeNotificationsFlag (1&lt;&lt;1)<br /> #define GSWindowWillMoveNotificationsFlag (1&lt;&lt;2)<br /> #define GSNoApplicationIconFlag (1&lt;&lt;5)<br /> #define WMFHideOtherApplications 10<br /> #define WMFHideApplication 12<br /> <br /> =Window Level=<br /> GNUstep needs arbitrary window levels. EWMH defines these two:<br /> _NET_WM_STATE_ABOVE, ATOM<br /> _NET_WM_STATE_BELOW, ATOM<br /> <br /> The rest depends on the function of a window. To obtain good interoperability between different Desktop Environments, the following layered stacking order is recommended, from the bottom to the top:<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DESKTOP&lt;/tt&gt;<br /> # windows having state &lt;tt&gt;_NET_WM_STATE_BELOW&lt;/tt&gt;<br /> # windows not belonging in any other layer<br /> # windows of type &lt;tt&gt;_NET_WM_TYPE_DOCK&lt;/tt&gt; (unless they have state &lt;tt&gt;_NET_WM_TYPE_BELOW&lt;/tt&gt;) and windows having state &lt;tt&gt;_NET_WM_STATE_ABOVE&lt;/tt&gt;<br /> # focused windows having state &lt;tt&gt;_NET_WM_STATE_FULLSCREEN&lt;/tt&gt;<br /> <br /> Windows that are transient for another window should be kept above this window.<br /> <br /> The window manager may choose to put some windows in different stacking positions, for example to allow the user to bring currently active window to the top and return it back when the window loses focus.<br /> <br /> =Window Style=<br /> Window style is more or less unchanged, except GNUstep want to display edited document: &lt;tt&gt;GSDocumentEditedFlag&lt;/tt&gt;<br /> <br /> =Window Type=<br /> EWMH defines:<br /> _NET_WM_WINDOW_TYPE_DESKTOP, ATOM<br /> _NET_WM_WINDOW_TYPE_DOCK, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM<br /> _NET_WM_WINDOW_TYPE_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_UTILITY, ATOM<br /> _NET_WM_WINDOW_TYPE_SPLASH, ATOM<br /> _NET_WM_WINDOW_TYPE_DIALOG, ATOM<br /> _NET_WM_WINDOW_TYPE_DROPDOWN_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_POPUP_MENU, ATOM<br /> _NET_WM_WINDOW_TYPE_TOOLTIP, ATOM<br /> _NET_WM_WINDOW_TYPE_NOTIFICATION, ATOM<br /> _NET_WM_WINDOW_TYPE_COMBO, ATOM<br /> _NET_WM_WINDOW_TYPE_DND, ATOM<br /> _NET_WM_WINDOW_TYPE_NORMAL, ATOM<br /> <br /> Comments from Yen-Ju Chen: &quot;GNUstep has no such definition and use window level for this purpose. Personally, I wish GNUstep had a better way to tell which window is for which functions, like app icon, floating panel, menu, key window, main window. The window level is not that reliable when people want to do some tricks. It may not match EWMH one-to-one, but it will be useful for various reasons.&quot;</div>

Martin