A quick note: Any control that you can set "run at server" will be able to translate the "~". And for the CSS links, I just use a "Response.Write"
Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michal Altair Valasek Sent: Thursday, September 09, 2004 4:20 PM To: [EMAIL PROTECTED] Subject: [xmail] Xmail-WAI features FAQ Hi, I have received numerous e-mails regarding implementation of various features in Xmail-WAI. The questions are generally repeated, so here is FAQ. LANGUAGE TRANSLATIONS OF INTERFACE Experience with previous (non-.NET) version was that there were people able and willing to do the translation once, bud NOBODY was willing to maintain the translations as WAI evolved. Thus new features were in English only. Also, to make interface multilanguage, all text need to be generated dynamically, which is not easy to implement. Therefore, I do not plan to implement multilanguage interface to WAI. This may change after ASP.NET 2.0 (Whidbey) would be available, because it should naturally support localization in easy way. FOLDERS, READ/UNREAD, SENT MAIL ETC. Xmail is going to support IMAP in near future, and therefore would need to support these features natively. After that would happen, I will write interface. I'm not going to make solution right now, when it can lead to collision with future Xmail implementation. RUNNING UNDER VIRTUAL DIRECTORY, NOT SEPARATE SERVER The main catch here is in HTML links. ASP.NET supports app-relative links (~) in some cases (ie. web controls), but not everywhere, like in images or CSS links. I plan to write some universal output rewriting module to implement this everywhere, but currently have no timeframe. HOW ABOUT PDA/WAP access I plan to make some interface for PDAs and WAP phones too. It would probably not include all features of Xmail-WAI, but would allow all important things. I'm not yet decided if it would be better to make it as separate app or include this functionality in WAI. You may tell mne what you would prefer and why! MAY I USE MIME PARSER OR ABSTRACTION LAYER IN MY APP? You can. Xmail-WAI and all parts (including MIME parser and Xmail Abstraction Layer) are covered by GNU General Public license. You can use any component or code in your application. Only catch here is that if you plan to distribute your app (and not use it only for yourself), you need to share alike - use the GPL too. MAY I CHANGE THE LAYOUT? WHAT ABOUT DIFFERENT SKINS WAI is skinnable right now! Most of layout is CSS-based and everything is template-based. I do not plan to implement some specific skinning technique, because standard HTML/CSS is sufficient. The GPL applies also to layout. You may change the layout as you wish, to match your corporate identity or whatever. You are even not required to leave there link to my site or my logo. However, you cannot remove my copyright notice (about page), you may only add your own statement regarding modified/created parts. GENERAL XMAIL-WAI DEVELOPMENT POLICY Generally, I would personally develop only features being useable for me. And expect that others would do the same. If anybody would develop additional functionality in way compatible with current WAI's code and architecture, I would be happy to merge it to a next version (few people already did - see acknowledgements in documentation). That's how I understand (and implement) the open source idea. -- Michal Altair Valasek [EMAIL PROTECTED] Altair Communications - web hosting, web design, application development ___________________________________________________________________________ http://www.altaircom.net | PGP: 0xC4F3579D | Phone (support): +420602137341 Panic. Chaos. Fear. My work here is done. - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]