![]() ![]() ![]() If that’s what you object to, I understand, and we can agree to disagree. ![]() Maybe we could extend the Haiku Mail GUI, keep the Haiku mailstore code as is, and crib the HERMES Mail feature code. That’s what I meant by one-codebase-per-system: we could (conceivably) have a common pool of libraries to draw from, and a separate application on each. Ignoring Mac for a second, it’s clear we can use most of the libraries and business code in Windows, Haiku, and Linux, and we can design a native GUI for each. I mentioned a one-codebase-per-system philosophy because, as given to us, the source tree had one codebase for Windows in C++, and an entirely unrelated codebase for Mac in C and Carbon (this was frozen in the Intel transition days). On the other hand, my original idea was to create a whole new GUI for the libraries and business code as a whole. It’s a big collection of files, and I refuse to believe that nothing in there would be useful. Now, that wouldn’t be in the spirit of my original proposal, but there we are. The project’s used Visual Studio since, well, forever, but that doesn’t mean you can’t compile it in GCC instead (some assembly What I’m unsure about, and tried to express but couldn’t really find the words, was how does the collection of GUI, libraries, etc called HERMES Mail disagree with the Haiku philosophy? Consider an approach where you simply take whatever libraries you need (be it an updated SMTP stack, Kerberos authentication, etc) and use it in Haiku. If you need a library, of course you can compile just that library. Other than the GUI, HERMES Mail is really nothing more than a collection of libraries for sending and receiving POP and SMTP mail, as well as authenticating with SSL and Kerberos, Hunspell… it’s fully modularised. Well, it’s C++, so it should be entirely possible. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |