Hi, sorry for the trouble, I know that sta...@tntnet should be documented.
I have not mentioned it in the discussion, since I don't think, it is the right way to go for TinyMCE or other javascript libraries you have. It is indeed the right way to use, if you allow users to add or change files. I feel, that it is a feature in tntnet, that you can compile static content into your application. javascript libraries or css or small images, which are part of your user interface are a substatial part of your application. I prefer to add all to the single applicaton binary, so I have no problems dealing with additional files and finding them in the file system. For testing it is ok to put the files into the file system, but at least when I create the final application I package all in one file. I wonder why you get corrupt content without ios::binary. It shouldn't. It really has no effect on CentOS or other linux or unix systems. Have you compared the output? A hex dump may help. I use curl to get the output of a application and xxd to hexdump it. Then I can compare binary content easily with gvimdiff. If you have a testcase, I would really like to see it. It is really important to know, what is going wrong here. It really must not happen. Tommi Am Sonntag, 29. November 2009 18:45:09 schrieb Shadowcat: ... ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
