That sounds horrible doesn't it? I have ability I mean... this project will humble me I believe. I am not a GUI guru. I will probably stick to non-GUI things for now ... i.e. XPlatform stuff.
> Our cross-platform code base allows hackers just like you to do
> pretty amazing things in the xp/ parts of the tree and have the
> changes affect all platforms simultaneously. For instance, fixing
> a layout bug or adding a file filter (import or export).
I am perusing the code. I am somewhat "getting" your organization scheme. It is still hard to find specific files that do specific things. More comments!
> Take a walk through the tree... a good exercise, as Bob recommended,
> would be to pick a bug that looks easy and tackle it. Tree navigation
> is probably the first obstacle; we've got a very layered project tree
> which lets us keep our classes in order for cross application frame-
> work code, WP (word processor) application code, and platforms at
Do you recommend the /wp/ap/xp section? That looked interesting. Or /text/ptbl/xp? I just started looking at that.
> each level (xp == cross platform, unix, beos, win32, mac). Swinging
> through the tree takes some time but soon you should be able to get
> around to the layer you need.
LXR is wonderful!
> Something we also value very much, and might be a more narrowly
> targeted introduction, would be a new file importer and/or exporter.
I know you guys are hurting for help here, but I think I will dive into bug-hunting until I am more confident. I will let you know.
COMPILING ISSUES:
I have had difficulty compiling abiword. I just re-did a checkout of expat and abi from scratch and am in the process of recompiling, but I have had some difficulty.
Is expat supposed to spew warnings? It compiles, but that many warnings makes me nervous.
Abi also spews warnings when compiling. I mean loads and loads of warnings. I presume this is somewhat normal or am I screwing something up. I am using RedHat 6.0 and just going into abi/src and typing make. (This is after compiling expat.)
Hell I was thinking about taking a look at some of the warnings and fixing a few "ANSI C++ forbids..." errors.
OK. I did a compile and it wrecks here... Anyone have a clue?
.............................................................................
make[3]: Entering directory `/home/tw/abisource/abi/src/wp/ap/unix'
Building with [LicensedTrademarks:Off Debug:Off].
ap_UnixApp.cpp:
ap_UnixApp.cpp: In method `UT_Bool AP_UnixApp::initialize()':
ap_UnixApp.cpp:99: warning: unused variable `UT_Bool bVerified'
ap_UnixApp.cpp: In method `UT_Bool AP_UnixApp::parseCommandLine()':
ap_UnixApp.cpp:510: no matching function for call to `AP_BuiltinStringSet::dumpBuiltinSet (char[13])'
make[3]: *** [/home/tw/abisource/abi/src/../src/Linux_2.2.5-15_i386_OBJ/obj/ap_UnixApp.o] Error 1
make[3]: Leaving directory `/home/tw/abisource/abi/src/wp/ap/unix'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/home/tw/abisource/abi/src/wp/ap'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/home/tw/abisource/abi/src/wp'
make: *** [build] Error 2
.............................................................................
Lemme know what you think. Don't flame me if it is something obvious please. I am still learning.
-Todd Warner