Difference between revisions of "Roadmap"
Jump to navigation
Jump to search
m |
|||
| Line 5: | Line 5: | ||
== TODO == | == TODO == | ||
| − | * ease installation process | + | * ease installation process (see [[GNUstep Installation Process]]) |
** what are potential platforms? | ** what are potential platforms? | ||
** what are their possibilities of installation? | ** what are their possibilities of installation? | ||
| Line 14: | Line 14: | ||
** how to cope with more than one GNUstep environments installed? | ** how to cope with more than one GNUstep environments installed? | ||
| − | * make GUI work on MS windows | + | * make GUI work on MS windows (see [[GNUstep Portability]]) |
** what is broken? | ** what is broken? | ||
** what needs to be done? | ** what needs to be done? | ||
Revision as of 15:17, 15 February 2005
GNUstep has no roadmap...!
Anyway, here is small list of what has to be done. Refine the list, prioritize and build the roadmap. Perhaps some checklist would help...
TODO
- ease installation process (see GNUstep Installation Process)
- what are potential platforms?
- what are their possibilities of installation?
- how can installation be combined for several platforms (one installation package for more linux distros, for example)
- how to distribute binary packages?
- what should be in the binary package?
- how should be the binary package installed? where? what should be configurable during installation?
- how to cope with more than one GNUstep environments installed?
- make GUI work on MS windows (see GNUstep Portability)
- what is broken?
- what needs to be done?
- who is working on it?
- what is the objective of GNUstep GUI/AppKit 1.0?
- what is missing?
- what does not work?
- what is the objective of GNUstep core 1.0?
- what is missing?
- what does not work?