]>
Commit | Line | Data |
---|---|---|
a660d684 KB |
1 | |
2 | Prototype dialog editor and property sheet classes | |
3 | -------------------------------------------------- | |
4 | ||
5 | Julian Smart, October 4th 1995 | |
6 | ------------------------------ | |
7 | ||
8 | Here's what I've done so far on a lightweight dialog editor. The 16-bit | |
9 | Windows binaries in the bin directory are dialoged.exe (the dialog | |
10 | editor) and test.exe (a small property sheet demo). | |
11 | ||
12 | Main points: | |
13 | ||
14 | - You can create a new dialog box and add items to it. | |
15 | - You can move items around, and right-click | |
16 | to edit a few properties (very incomplete). | |
17 | - Can't write out .wxr files yet. Loading code is in | |
18 | wxWindows, but writing code is absent: should be put | |
19 | into wxWindows. | |
20 | - No attempt at resources other than dialogs yet. | |
21 | Should have menu editor too. | |
22 | - Should *somehow* have a protocol to allow | |
23 | existing resources e.g. in wxCLIPS/wxPython | |
24 | to be edited in situ. | |
25 | This should be made simpler by the existance of | |
26 | the plug-in event handler mechanism, which means you | |
27 | can temporarily handle all the events yourself. | |
28 | - See dialoged.cc: the main program is tiny because | |
29 | it's meant to be embeddable. | |
30 | - The wxPropertySheet (set of) classes are very | |
31 | general and should be put into wxWin and documented. | |
32 | ||
33 | Comments, chivvying and help all appreciated. Maybe if | |
34 | I documented what I had, it would be easier for others | |
35 | to do some work on it. | |
36 | ||
37 | Regards, | |
38 | ||
39 | Julian |