coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

There really is no way that CoApp will make its way onto embedded devices (unless you mean "Windows Embedded", and not Windows Mobile or Windows Phone--Windows Embedded is built from Windows 7).

The packages are Windows Installer (.MSI) based and use WinSxS for side by side installation of libraries. I'm pretty sure there aren't any mobile devices that support those features.

g

Garrett Serack | Open Source Software Developer | Microsoft Corporation 
I don't make the software you use; I make the software you use better on Windows.

-----Original Message-----
From: Andrew Fenn [mailto:andrewfenn@xxxxxxxxx] 
Sent: Thursday, August 05, 2010 8:20 PM
To: Garrett Serack
Cc: Rivera, Rafael; Elizabeth M Smith; coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Engine - Teds initial take

I have no idea when it comes to unicode in C/C++ however would supporting ANSI help getting CoApp to run on embedded devices?

On Fri, Aug 6, 2010 at 3:05 AM, Garrett Serack <garretts@xxxxxxxxxxxxx> wrote:
>
> (still on vacation... just poking my nose in).
>
> I had no particular opinion [ _T("") vs L"" ] but I do like the idea that perhaps we should explicitly NOT support ANSI. I can't see a really good reason to support ANSI either, and frankly I like the idea that we should do what it takes to make it hard to do so.
>
> G
> -----Original Message-----
> From: 
> coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx 
> [mailto:coapp-developers-bounces+garretts=microsoft.com@lists.launchpa
> d.net] On Behalf Of Rivera, Rafael
> Sent: Wednesday, August 04, 2010 6:06 PM
> To: Elizabeth M Smith
> Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Coapp-developers] Engine - Teds initial take
>
> That's a pretty poor reason to not type a few extra characters... but I can't offer a concrete reason why we should support ANSI.
>
> /rafael
>
> On 8/4/2010 11:25 AM, Elizabeth M Smith wrote:
>> On 8/4/2010 11:13 AM, Rivera, Rafael wrote:
>>> Looks nice, love the chip name.
>>>
>>> Just one note -- I see wide-character strings in use. I suggest 
>>> replacing them, and their print functions, with T equivalents, 
>>> leaving the choice of ANSI or UNICODE to the magical defines in the 
>>> headers and ultimately the human compiling this stuff.
>>>
>>> So, from initial glance, I'd replace L"" with _T("") and fwprintf 
>>> with _ftprintf.
>>>
>>
>> No way in hell do I want to support anyone doing that - then you'd 
>> have idiots compiling and giving out version that don't support 
>> UNICODE strings and users complaining about it
>>
>> ICK
>>
>> UNICODE or nothing.
>>
>> Thanks,
>> Elizabeth M Smith
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~coapp-developers
> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~coapp-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~coapp-developers
> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~coapp-developers
> More help   : https://help.launchpad.net/ListHelp
>