Times New RomanHi there, > Good day to you all at Abiword. I am at a verge of > incorporatingwxWindow and FLTK into the current/future > version of Abiword that I have just downloaded and built.   > 1.) My Question is -> Is this OK and "Acceptable"? You can hack AW privatly as much as you want, and since wxWindows is licenced under GPL just as AbiWord, there is nothing to stop you from distributing the hacked code (I do not know what FLTK is, so I cannot comment on that). Also, I would certainly be interested in having a wxWindows port as a part of the official tree one day.  > b) If yes! Or Ok! Please let me know if there are rules to >follow and how to go about doing this in your already laid out > way. There are basic guidlines in AbiSourceCodeGuidelines.abw. Now, where the code should go is a good question, since wxWindows is cross-platform in itself. I think you should place the wx code into a new wx subirectories along the unix, win, QNX, mac, etc. The makefiles will eventually require some thought if we would want to achieve a wx build on other platforms than win32, but for the moment in the part of the tree which is not wx specific, e.g., abi/src/util/, just create wx directory with makefiles pointing to the win32 directory sources. > The only problem at moment is at Top level menu (e.g. &File, > &Edit...etc) but the other menu-items and controls can be > translated into any World language with ease without rely on the > OS but with supplied localised font(s). If the problem with the top level windows is caused by the wxWindows API, then you should contact the wx people and ask them to change things. with best wishes Tomas