This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

AW: [PATCH] setup - help and local dir command line options was"Re: Setup Command Line Options"

> -----Ursprüngliche Nachricht-----
> Von: Robert Collins []

> On Sat, 2003-10-25 at 10:43, Ralf Habacker wrote:
> > Below there are two patches:
> >
> > 1. A patch implementing a help option, it prints it output to
> the setup.log
> > (
> Approved.


> > 2. Additional a patch to allow setting the local dir from the
> commandline.
> > (
> This is in the wrong place: LocalDirSetting::load is the right method to
> query the option from.
While thinking about this a while more, I recognized that there is some more
basic work necessary how to design the command line interface.
Are there any other requests or hints about the design ?

For me there is currently one major question. Is it possible to print
message on stdout/stderr from a gui application ?
If not than the first step seems to me really to split the gui from the
core, so that a console application could be build. Has anyone done some
analysis, where the cut could be done ?

A personal note: I will take some time for this because this is a need for
further kde releases, so I probably will be able to help with the design,
implementing some functions and making an initial design document about the
command line design works, but there is much more work to do. At all I see
the following tasks:

1. analyse how to seperate the gui from the engine (the core) and the helper
	- identifing the classes
	- move identified classes the related subdirs rsp libraries, for example
		core			- the dir holding all engine stuff
		setup (or gui) 	- the dir with the gui installer
		cygsetup or (???) - the dir with the command line installer

2. make a design about (a) the engine api and (b) the command line design
3. build up the engine
4. change the gui stuff to use the new engine
5. build a command line front end using the new engine

As stated above I can help in 2b and 5 and problaby in 2a, because of the
evolution of the command line interface and caused engine api

Any comments and/or other contributors ?


Attachment: cygsetup-kdevelop-0.0.1.tar.bz2
Description: Binary data

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]