Difference between revisions of "Roadmap to Windows"

From GNUstepWiki
Jump to navigation Jump to search
(cleanup)
(Stress portability, compatibility, theming. Query a few unclear points.)
Line 1: Line 1:
 
This page is the starter for the "Road to Windows", a goal of the GNUstep project to deliver a very [[What is Native on Windows|native]] implementation.
 
This page is the starter for the "Road to Windows", a goal of the GNUstep project to deliver a very [[What is Native on Windows|native]] implementation.
 
Windows has many differences with *nix and OpenStep generally. These need to be dealt with in a way that delivers a 'Windows experience' to the end users but doesn't compromise the OpenStep API.
 
Windows has many differences with *nix and OpenStep generally. These need to be dealt with in a way that delivers a 'Windows experience' to the end users but doesn't compromise the OpenStep API.
−
Some differences are expected.
+
Some differences are expected, but must be minimised in order to maximise software portability.
  
 
If you'd like to work on any of these tasks you should put your hand up in gnustep-discuss or e-mail [[User:Sheldon|me]] directly.
 
If you'd like to work on any of these tasks you should put your hand up in gnustep-discuss or e-mail [[User:Sheldon|me]] directly.
Line 9: Line 9:
 
* Relies on a unix shell: We use MSYS and the mingw32 toolchain to provide a very unix-like build environment.
 
* Relies on a unix shell: We use MSYS and the mingw32 toolchain to provide a very unix-like build environment.
 
* Make doesn't support paths with spaces. Fundamental design flaw. Ideally we'd like a solution to this.
 
* Make doesn't support paths with spaces. Fundamental design flaw. Ideally we'd like a solution to this.
−
* Current implementation of 'make install' assumes *nix which doesn't really apply.
+
* Current implementation of 'make install' assumes *nix which doesn't really apply. What does this mean?
  
 
== Base ==
 
== Base ==
Line 15: Line 15:
 
=== General ===
 
=== General ===
  
−
* More flexible layout mechanism (what needs doing for this) & options to control in config file.
+
* More flexible layout mechanism (what needs doing for this) & options to control in config file. What does this mean? perhaps we actually need a less flexible mechanism, but the 'right' one?
−
* Win32 "native" mechanism over-rides
+
* Win32 "native" mechanism over-rides ... but for what?
  
 
=== GSXML ===
 
=== GSXML ===
  
−
* Use single url expansion mechanism for all (no special -//GNUstep//DTD
+
* Use single url expansion mechanism for all (no special -//GNUstep//DTD)
−
* Add option for loading from URL, not just local files. (cache in ~)
+
* Organise them clearly somehow ... need tio decide how.
−
* Organise them as
 
−
/Library/DTDs/GNUstep/
 
−
/Library/DTDs/Apple Computer/
 
−
/Library/DTDs/Microsoft/
 
  
 
=== Logging ===
 
=== Logging ===
Line 31: Line 27:
 
* NSLog() should only be used for vital/error messages. These should be localizable.
 
* NSLog() should only be used for vital/error messages. These should be localizable.
 
* Localize all error output.
 
* Localize all error output.
−
* Should implement FACILITY options for logging to SYSLOG
+
* Should implement FACILITY options for logging to SYSLOG if MacOS-X does this ... should be compatible.
 
* Use more flexible DebugLog for other output.
 
* Use more flexible DebugLog for other output.
  
Line 42: Line 38:
 
** unicode improvements (I have code for this...)
 
** unicode improvements (I have code for this...)
  
−
* Build option for native timezones only
+
* Install/runtime option for native timezones only
  
−
* Add classes for other calendars:  
+
* Add classes for other calendars as soon as we have both windows and unix implementations:  
−
** + NSJulianCalendarDate
+
** + GSJulianCalendarDate
−
** + NSHebrewCalendarDate
+
** + GSHebrewCalendarDate
−
** + NSChineseCalendarDate
+
** + GSChineseCalendarDate
−
** + NSJapaneseCalendarDate
+
** + GSJapaneseCalendarDate
−
** + NSBuddhistCalendarDate
+
** + GSBuddhistCalendarDate
  
 
=== Strings ===
 
=== Strings ===
Line 66: Line 62:
  
 
* UTF32
 
* UTF32
−
** Doesn't handle non-BMP characters right now.
+
** Does this handle non-BMP characters right now? If not, what needs fixing?
  
 
* NSStringEncoding
 
* NSStringEncoding
Line 76: Line 72:
  
 
* NSMenu
 
* NSMenu
−
** Want horizontal, in-window menus
+
** Want horizontal, in-window menus theme
  
 
* NSPopupButton
 
* NSPopupButton
−
** Menu shouldn't require continuous mousedown but rather behave like other windows menus.
+
** Menu shouldn't require continuous mousedown but rather behave like other windows menus when using windows theme.
  
 
* NSHelpPanel
 
* NSHelpPanel
−
** Interface to native windows help system
+
** Interface to native windows help system and/or 'normal' help
 
** [NSApplication showHelp] looks in Resources/(lang).lproj
 
** [NSApplication showHelp] looks in Resources/(lang).lproj
 
*** Use Info.plist for name of help book
 
*** Use Info.plist for name of help book
 
*** opens "AppName Help.chm" or
 
*** opens "AppName Help.chm" or
 
*** opens "AppName Help.hlp"
 
*** opens "AppName Help.hlp"
−
** [NSApplication activateContextHelpMode]  
+
** [NSApplication activateContextHelpMode]
 +
** Need a help generation/editing tool to support both unix and windows style help.
  
 
* Logging
 
* Logging
Line 96: Line 93:
 
=== Drawing ===
 
=== Drawing ===
  
−
* Some controls are drawn. Others use pre-drawn images. These don't change in response to color preferences. That should be corrected. Notable: Radio buttons, check boxes. scrollbar arrows, menu arrows. Clean drawing code to use right colors from system color map
+
* Some controls are drawn. Others use pre-drawn images. These don't change in response to color preferences. That should be corrected. Notable: Radio buttons, check boxes. scrollbar arrows, menu arrows. Clean drawing code to use right colors from system color map ... should all go into theme system.
  
 
* Drawing should be improved generally so that it looks better and is faster
 
* Drawing should be improved generally so that it looks better and is faster
Line 107: Line 104:
  
 
* NSColor/NSColorList
 
* NSColor/NSColorList
−
** Load System color palette from current desktop settings (I have code for this...)
+
** Windows theme code may load System color palette from current desktop settings (I have code for this...)
 
** improve system color startup, don't automatically write System.clr to user folder
 
** improve system color startup, don't automatically write System.clr to user folder
 
** get gnustep-back to handle WM_SYSCOLORCHANGE messages
 
** get gnustep-back to handle WM_SYSCOLORCHANGE messages
 
** Support ICCM colour profiles and colour correction
 
** Support ICCM colour profiles and colour correction
−
** +[availableColorLists] should read directory every time. If you need speed, cache yourself
+
** +[availableColorLists] should check directory modification date every time.
  
 
=== Panels ===
 
=== Panels ===
Line 118: Line 115:
 
** If NSDefaultOpenDirectory isn't set should use "~/" on *nix and "My Documents" on Win32.
 
** If NSDefaultOpenDirectory isn't set should use "~/" on *nix and "My Documents" on Win32.
 
** Must support multiple drives etc on Win32
 
** Must support multiple drives etc on Win32
−
** Should display as Treeview, rather than Browser
+
** Should have theme able to display as Treeview, rather than Browser

Revision as of 21:42, 20 September 2006

This page is the starter for the "Road to Windows", a goal of the GNUstep project to deliver a very native implementation. Windows has many differences with *nix and OpenStep generally. These need to be dealt with in a way that delivers a 'Windows experience' to the end users but doesn't compromise the OpenStep API. Some differences are expected, but must be minimised in order to maximise software portability.

If you'd like to work on any of these tasks you should put your hand up in gnustep-discuss or e-mail me directly.

Make

  • Relies on a unix shell: We use MSYS and the mingw32 toolchain to provide a very unix-like build environment.
  • Make doesn't support paths with spaces. Fundamental design flaw. Ideally we'd like a solution to this.
  • Current implementation of 'make install' assumes *nix which doesn't really apply. What does this mean?

Base

General

  • More flexible layout mechanism (what needs doing for this) & options to control in config file. What does this mean? perhaps we actually need a less flexible mechanism, but the 'right' one?
  • Win32 "native" mechanism over-rides ... but for what?

GSXML

  • Use single url expansion mechanism for all (no special -//GNUstep//DTD)
  • Organise them clearly somehow ... need tio decide how.

Logging

  • NSLog() should only be used for vital/error messages. These should be localizable.
  • Localize all error output.
  • Should implement FACILITY options for logging to SYSLOG if MacOS-X does this ... should be compatible.
  • Use more flexible DebugLog for other output.

Dates & Times

  • NSDate
    • Olsen <-> Windows timezone name mapping
    • knownTimeZoneNames returns Olsen
    • timeZoneWithName takes Olsen
    • unicode improvements (I have code for this...)
  • Install/runtime option for native timezones only
  • Add classes for other calendars as soon as we have both windows and unix implementations:
    • + GSJulianCalendarDate
    • + GSHebrewCalendarDate
    • + GSChineseCalendarDate
    • + GSJapaneseCalendarDate
    • + GSBuddhistCalendarDate

Strings

  • NSCaseInsensitiveSearch
    • Implementation tests
    • Add full Unicode case folding
  • NSLiteralSearch
    • Corrections for composed sequences?
  • Composed sequences & Normalisation
    • Check composed sequence handling generally
    • Implement additional normalisation forms
    • proper (full) collation and comparison
  • UTF32
    • Does this handle non-BMP characters right now? If not, what needs fixing?
  • NSStringEncoding
    • additional encodings for Indian, SE Asia...

Gui

General

  • NSMenu
    • Want horizontal, in-window menus theme
  • NSPopupButton
    • Menu shouldn't require continuous mousedown but rather behave like other windows menus when using windows theme.
  • NSHelpPanel
    • Interface to native windows help system and/or 'normal' help
    • [NSApplication showHelp] looks in Resources/(lang).lproj
      • Use Info.plist for name of help book
      • opens "AppName Help.chm" or
      • opens "AppName Help.hlp"
    • [NSApplication activateContextHelpMode]
    • Need a help generation/editing tool to support both unix and windows style help.
  • Logging
    • Use NSLog() only for vital messages
    • Use NSDebugLLog() everywhere else
    • Localise everywhere

Drawing

  • Some controls are drawn. Others use pre-drawn images. These don't change in response to color preferences. That should be corrected. Notable: Radio buttons, check boxes. scrollbar arrows, menu arrows. Clean drawing code to use right colors from system color map ... should all go into theme system.
  • Drawing should be improved generally so that it looks better and is faster
  • Taskbar
    • Application icons should appear in the taskbar and on the applications windows in the same way as other windows applications. Behaviour should follow.
  • NSImage
    • support for more image types
  • NSColor/NSColorList
    • Windows theme code may load System color palette from current desktop settings (I have code for this...)
    • improve system color startup, don't automatically write System.clr to user folder
    • get gnustep-back to handle WM_SYSCOLORCHANGE messages
    • Support ICCM colour profiles and colour correction
    • +[availableColorLists] should check directory modification date every time.

Panels

  • NSOpenPanel, NSSavePanel
    • If NSDefaultOpenDirectory isn't set should use "~/" on *nix and "My Documents" on Win32.
    • Must support multiple drives etc on Win32
    • Should have theme able to display as Treeview, rather than Browser
Retrieved from "https://mediawiki.gnustep.org/index.php?title=Roadmap_to_Windows&oldid=3585"