X11workbench Toolkit  1.0
gizzard.c
1 // //
3 // _ _ //
4 // __ _ (_) ____ ____ __ _ _ __ __| | ___ //
5 // / _` || ||_ /|_ // _` || '__|/ _` | / __| //
6 // | (_| || | / / / /| (_| || | | (_| | _| (__ //
7 // \__, ||_|/___|/___|\__,_||_| \__,_|(_)\___| //
8 // |___/ //
9 // //
10 // project creation and other 'gizzards' //
11 // //
12 // NOTE: 'gizzard' is a combination of 'wizard' and 'gizmo' //
13 // (this is done to prevent alleging tradmark/copyright infringement) //
14 // //
16 
17 /*****************************************************************************
18 
19  X11workbench - X11 programmer's 'work bench' application and toolkit
20  Copyright (c) 2010-2019 by Bob Frazier (aka 'Big Bad Bombastic Bob')
21  all rights reserved
22 
23  DISCLAIMER: The X11workbench application and toolkit software are supplied
24  'as-is', with no warranties, either implied or explicit.
25 
26  BSD-like license:
27 
28  There is no restriction as to what you can do with this software, so long
29  as you include the above copyright notice and DISCLAIMER for any distributed
30  work that is linked with, equivalent to, or derived from any portion of this
31  software, along with this paragraph that explains the terms of the license if
32  the source is also being made available. "Linked with" includes the use of a
33  portion of any of the source and/or header files, or their compiled binary
34  output, as a part of your application or library. A "derived work"
35  describes a work that uses a significant portion of the source files or the
36  algorithms that are included with this software.
37 
38  EXCLUSIONS
39 
40  Specifically excluded from this requirement are files that were generated by
41  the software, or anything that is included with the software that is part of
42  another package (such as files that were created or added during the
43  'configure' process).
44 
45  DISTRIBUTION
46 
47  The license also covers the use of part or all of any of the X11 workbench
48  toolkit source or header files in your distributed application, in source or
49  binary form. If you do not ship the source, the above copyright statement
50  and DISCLAIMER is still required to be placed in a reasonably prominent
51  place, such as documentation, splash screens, and/or 'about the application'
52  dialog boxes.
53 
54  Use and distribution are in accordance with GPL, LGPL, and/or the above
55  BSD-like license. See COPYING and README.md files for more information.
56 
57  Additionally, this software, in source or binary form, and in whole or in
58  part, may be used by explicit permission from the author, without the need
59  of a license.
60 
61  Additional information at http://sourceforge.net/projects/X11workbench
62  and http://bombasticbob.github.io/X11workbench/
63 
64 ******************************************************************************/
65 
66 #include "X11workbench.h"
67 #include "gizzard.h"
68 
69 //
70 // TENTATIVE PLANS ON APPLICATION 'Gizzards' (aka 'wizards' in case of trademarks)
71 //
72 // 1. tab-MDI and dialog-based applications for X11 Workbench Toolkit
73 //
74 // 2. similar to above, using a "foundation class" wrapper (C++)
75 //
76 // 3. MDI and dialog-based applications for wxWidgets (C++)
77 //
78 // 4. similar for GTK and/or GTK+ (C++)
79 //
80 // 5. shared lib / DLL projects.
81 // NOTE: 'dlopen' calls _init(), 'dlclose()' calls _fini() in the shared lib.
82 // MS DLLs call DllMain() with DLL_PROCESS_ATTACH or DLL_PROCESS_DETACH
83 // These need to be abstracted by whatever framework I use.
84 // NOTE 2: MS also calls DllMain() when starting/ending a process or thread
85 // for an already-loaded DLL. See MS docs for the context and
86 // implications of these calls.
87 //
88 // 6. alternate platform application wizards (such as Arduino)
89 //
90 // 7. possible Android application wizards (would require installing Android SDK)
91 //
92 //
93 // The priority, of course, is to use the X11 Workbench Toolkit. Once it is able
94 // to run under windows, there will be no real need for anything else. The next
95 // priority are the two toolkits that are already cross-platform, namely wxWidgets
96 // and GTK. Qt is also a possibility, though it has its own (pay for) IDE already.
97 //
98 // Alternate platforms like Arduino might be helpful in that there is no existing
99 // 'application gizzard', and I intend to make X11workbench's IDE easier/better to
100 // use than the Arduino IDE. However, without a proper debugging interface to a
101 // microcontroller system, it has limited added value (other than the 'gizzard').
102 //
103 //
104 
105 
106