Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #103866
| From | GOTHIER Nathan <nathan.gothier@gmail.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: project together? |
| Date | 2017-02-14 12:11 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <20170214121133.9d99097b0f984ede42c6007e@gmail.com> (permalink) |
| References | (4 earlier) <aa80c0e8-4ccb-4155-ad9e-f10bd09eae9f@googlegroups.com> <2a31d76d-420d-4328-a88e-b86c64761c69@googlegroups.com> <o7ruon$tjl$1@dont-email.me> <20170213115845.07a60e5a42f78287396f4261@gmail.com> <9967c88c-be8e-4fde-be97-6b9a93bd51c3@googlegroups.com> |
On Mon, 13 Feb 2017 05:39:29 -0800 (PST)
Malcolm McLean <malcolm.mclean5@btinternet.com> wrote:
> Baby X will always be open source, and the intention is to keep the codebase
> small enough for one person to realistically modify it as he sees fit.
> The idea is a baby toolkit, jut enough to get a few buttons, edit boxes, and
> graphics windows going.
> However it's got a fairly powerful graphics context.
A quick view on BabyX.h show this:
typedef struct
{
HINSTANCE hinstance;
BBX_CHILD *child;
BBX_TICKER *ticker;
BBX_Clipboard *clipboard;
int Nchildren;
int childCapacity;
int screen;
struct bitmap_font *gui_font;
struct bitmap_font *user_font2;
int modalpush;
int running;
} BABYX;
What's the goal of creating a black box with a typedef while showing all its
components in a header? If you don't expect users to manually access to members
I would rather strip all unnecessary details with a source file or "private
header" inclusion such as:
/*
bbxtypes.h
*/
struct bbx
{
HINSTANCE hinstance;
BBX_CHILD *child;
BBX_TICKER *ticker;
BBX_Clipboard *clipboard;
int Nchildren;
int childCapacity;
int screen;
struct bitmap_font *gui_font;
struct bitmap_font *user_font2;
int modalpush;
int running;
};
/*
BabyX.h
*/
#include "../common/bbxtypes.h"
typedef struct bbx BABYX;
Once more, there is no copyright or license notice in your files, this can
prevent users to modify, copy or distribute your source files to build their
program possibly open source.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
project together? fir <profesor.fir@gmail.com> - 2017-02-09 10:16 -0800
Re: project together? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-02-09 18:28 +0000
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 10:45 -0800
Re: project together? gazelle@shell.xmission.com (Kenny McCormack) - 2017-02-09 20:04 +0000
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-09 21:30 +0100
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:43 -0800
Re: project together? mark.bluemel@gmail.com - 2017-02-10 00:47 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 00:57 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 07:17 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 04:24 -0800
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:31 +0100
Re: project together? Ian Collins <ian-news@hotmail.com> - 2017-02-11 19:08 +1300
Re: project together? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-02-11 10:02 -0500
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:34 +0100
Re: project together? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-02-13 10:24 -0500
Re: project together? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-02-09 10:46 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 11:06 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:06 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 12:18 -0800
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-09 21:57 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 00:48 -0800
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-10 02:52 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 06:47 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-10 07:12 -0800
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-13 10:39 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-13 02:32 -0800
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-13 11:58 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-13 05:39 -0800
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-14 12:11 +0100
Re: project together? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-02-14 03:58 -0800
Re: project together? BartC <bc@freeuk.com> - 2017-02-14 12:01 +0000
Re: project together? David Brown <david.brown@hesbynett.no> - 2017-02-14 13:36 +0100
Making things open source requires copyright notices; it's the world we live in (Was: project together?) gazelle@shell.xmission.com (Kenny McCormack) - 2017-02-14 12:46 +0000
Re: project together? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-14 14:24 +0100
Re: project together? raltbos@xs4all.nl (Richard Bos) - 2017-02-15 21:07 +0000
Re: project together? "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-02-09 12:48 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-09 13:04 -0800
Re: project together? void <nathan.gothier@gmail.com> - 2017-02-10 20:00 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 01:18 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 02:20 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:31 -0800
Re: project together? void <nathan.gothier@gmail.com> - 2017-02-11 02:48 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:16 -0800
Re: project together? fir <profesor.fir@gmail.com> - 2017-02-11 03:40 -0800
csiph-web