Hi, I'm sorry for replying so late to this - this message didn't make it to my primary account due to the problems with my IMAP server and so I've just seen it while going through the archive. On Thu, 18 Apr 2002, tom campbell wrote:
> First I hope this is appropriate for me to post messages here. Yes, it's perfectly ok. > I'm trying to compile the M source on a RedHat 7.1 Linux from the tip of > CVS a few minutes ago. I'm getting multiple compile errors of the sort: > > .src/gui/wxlparser.cpp:47: no method `wxFontMapper::Get' > > There was a post about this a day or so ago on this list, but I didn't > see a solution. I've compiled and installed wxGTK-2.3.3-M.tar.gz as > downloaded from mahogany. So a couple of questions... > > 1. Has anybody else solved this? Yes :-) > 2. Have I got the right version of wxGTK? No, you need the latest wxGTK from the cvs as well. 2.3.3-M is sufficient for 0.64 Mahogany release but not for the cvs version. Mahogany tends to follow wxWindows very closely. > 3. How "stable" does the tip of CVS tend to be? I use Mahogany from the cvs all the time as my mail client (although not this time - see above) so it more or less always works. Of course, sometimes it does get broken but then you can just do "cvs up -Dyesterday", complain loudly (after checking that nobody else had already done it) and wait until it gets fixed... There are also periods of "deep changes" but I announce them on this list first. In general, I appreciate a lot people using the cvs version because I hardly have any time for testing any configurations different from my own and so it can be very helpful as others find the bugs which I'd never encounter myself. > I'm compiling from source to get access to the --configure option that got > posted a couple of days ago. I've got a dual booted (Win2k/Linux) laptop > that I really, really want to use the same email client and message files. I realized that there were still some problems with this usage pattern: in particular, you can't/don't want to share some options between the systems, i.e. the paths for the external programs, for example. I didn't yet have time to think more about this nor find the right way to deal with this problem though. BTW, sharing the message files is trivial - i.e. it was always possible. But it's true that maintaining 2 configurations in parallel is painful. I hope to have it solved for 0.65 but, as I said above, I don't know how exactly. I think the best would be to have some smart synchronization algorithm which would know that some options are local and shouldn't be affected by the synchronization - this would be (very) useful for synchronizing with the remote config (stored on an IMAP server) and could be used here as well. I.e. I think that you wouldn't use --config option at all but simply set "Sync config on startup and shutdown" option and specify a local file to sync with. But any other/better ideas are welcome! > I'm a professional developer (see www.DinkumSoftware.com if you care) No need, Dinkum is rather well-known! > I'm not opposed to lending a hand in development, but I'll need to get my > feet a little damp before jumping in. You can find some basic info in doc/tech directory. But, being realistic, I think that to find your way in the code you really have to ask here. Globally, the program is not very easy to understand although an experienced programmer shouldn't have much trouble with it neither. But locally - and except for a few dark corners where we still have 6 year old code - it is hopefully quite clear. IOW, there are a few rather self-contained subsystems and it shouldn't matter if you don't know the global design for as long as you work just on one of them. I can think of several sub projects which fall in this category. The most important (not the most difficult to do, mind you, but simply the most useful to have) would be adding spell checker support to the composer. If you are interested in this, please let me know and I can explain what exactly needs to be done. Regards, VZ _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
