Related
I've seen that .Net CF 3.7 doesnt have the directx ( Direct 3d) libraries and i was wondering if microsoft decided to delete them and not continue using directx with .net cf or if it's only because the 3.7 version is a beta and lacks many things.
Apart of that, i don't know what new things has 3.7 version, is there any changelog? because if there aren't important changes, i consider it may be better to continue using .net cf 3.5.
No follow up?
I'm curious if anybody has any more information on this matter. I'm currently using a slightly older version of NRGZ's EnergyROM with a Touch Pro and am unable to use Diamond Hologram because of a TypeLoadException stating that Microsoft.WindowsMobile.DirectX can not be found.
There's a chance that the rip of the unreleased .NET CF 3.7 was incomplete (though the GAC is pretty straightforward) or the pre-release state of it could also be used to rationalize missing assemblies, but if I were to take a random crack at it, I would guess that they're working on XNA for Windows CE/Mobile since it's based on CF and runs on Windows, XBox 360 and Zune it would be a logical step for Microsoft (just as they stopped supporting Managed DirectX on desktop editions), though it does seem a bit unfair to developers of existing applications since the desktop edition was not shipped with the framework, but rather with the DirectX SDK whereas this was deployed in the framework.
Is there a chance that someone could test using the 3.5 version on a 3.7 runtime? If the CLRs are compatible (and they seem to be) then it should still be able to load the assembly, and if binding works at all similar to the desktop framework we could probably just copy it into the directory of the application path, rather than GACing it.
After some searching around this is better discussed in the original CF 3.7 thread since it has been brought up. I'll repost my thoughts there and see if someone can help with experimenting.
http://forum.xda-developers.com/showthread.php?p=4060348
Not sure if this should be posted in the aforementioned thread, but it has long been rumoured that MS would phase out Direct3D by Windows Mobile 7, in favour of OpenGL and OpenGLES. Hope this helps at all.
GL
Well, I'm not so sure MS will ever officially support GL since it's a "competing" product to DirectX. In fact, to me it seems very unlikely. While they have been supporting community solutions and open source work more lately, generally Microsoft makes an effort to have developers use Microsoft technologies which in turn makes applications dependent on Microsoft and therefore users dependent on Microsoft. They have (arguably) the most powerful, useful and time-saving development tools which keeps many developers (like myself) developing applications that are inherently designed for their operating systems.
XNA, on the other hand is a Microsoft technology that is gaining a lot of traction and is directly related to the .NET Compact Framework, which is what leads me to believe they'll choose that route. With the right love and care a single XNA game can be played on PC, XBOX 360 and Zune and it seems likely that supporting the platform that .NET CF was first implemented on is only a matter of time. It's been rather surprising to many in the XNA community that MS hasn't already supported it, since their original press releases strongly indicated support for it. One thing's for sure: while there is an XNA Game Studio built on top of Visual Studio, there will probably not be any MS initiative to build a GL game studio.
http://www.microsoft.com/presspass/press/2004/mar04/03-24xnalaunchpr.mspx
To be fair though, that doesn't necessarily mean they won't implement the Windows Mobile version of XNA using OpenGL ES, though it seems likely that the architecture is designed more toward DirectX. Still hardware manufacturers could play a huge role in this decision.
I’ve thoroughly tested the brand new Opera Mobile 10 beta on all the supported mobile phone platforms (Windows Mobile Professional / Standard and Symbian S60). In general, apart from some problems, I liked what I saw – particularly on Symbian and the touchscreen version of Windows Mobile.
The browser is available for download HERE for both operating systems. For Windows Mobile, a unified download (for both subtypes) is provided.
1. Windows Mobile
Also see the XDA-Devs discussion, which starts on THIS page.
1.1 Touchscreen devices
I’ve installed it on the HP iPAQ 210 and found it great. Sure, it lacks some features (for example, the excellent dynamic zooming & text reflowing features of some (not all!) of the 9.50/9.70 builds and the (hacked) Flash Lite support), but, on the whole, I was more than happy with it. It doesn’t load much faster than the older version (9 seconds as opposed to 10) and, as has already been pointed out, lacks some of the goodies; however, it’s a pleasure to use.
Unfortunately, it (still) doesn’t support Opera Link, one of the best features of Opera Mini and the desktop Opera browser. (One of the reasons I’ve completely switched to using Opera on the desktop.)
Also see THIS demo for more info.
1.2 Non-touchscreen (Microsoft Smartphone) devices
1. Unfortunately, the two hotkeys are in no way supported on any of the tested Smartphones (on the s710, including the ones on the hardware keyboard). Therefore, a cursor emulator is needed to access even the menu at the bottom and almost everything. In-page scrolling and, on the Quick access page (default one and the one that comes up when you open a new tab), switching between the address input field, the Google field and the main surface area works OK. (Hotkeys are supported just great on Symbian S60.)
2. There are no button scrolling shortcuts, as opposed to the SP version of 8.65 (the last Opera Mobile version to have a dedicated MS Smartphone version – see my MS Smartphone Web Browser Bible HERE).
3. While you can’t use the hotkeys in fullscreen mode, with SPHelper, you can still access the two buttons in the lower right and left corners. (Hotkey-based scrolling – 2/4/6/8 – works just great on Symbian S60.)
176*220 (old) MS Smartphones running the official WM5 (tested on the HTC s310 (Oxygen)): excellent (tested running from memory card) program / page load time; responsive. Landscape mode isn’t supported – as opposed to the s710.
HTC s710 Vox (320*240 newer Smartphone running the official WM6): running great. However, multi-function keys on the hardware keyboard don’t work (always the numeric values are inserted) – to enter them, you need to use either the on-screen keyboard (which, BTW, is rendered properly even on a 176*220 Smartphone in Portrait mode) or the numeric keypad.
All in all, until the hotkey bug is fixed (operating the browser with SPHelper is really painful), you will want to stick with either the old 8.65 version or Opera Mini. (This, again, only stands for the non-touchscreen-enabled MS Smartphone platform, NOT the touchscreen-based one!)
2. Symbian S60
It’s nice to see Opera to return to Symbian, which they have seemed to have completely neglected in the last few years.
I’ve tested OM10 on the Nokia N95 on firmware version 30 and found it excellent. It has very quick program / page loading; OK multitabs (albeit, after opening two – large, about 600k+ - Wiki pages, when minimizing Opera mobile, it was immediately terminated from memory, showing Opera indeed took up quite a bit of RAM memory. This was expected – if you need multitab supporting up to 30 pages open at the same time, your only choice is Opera Mini.)
Basically, it’s as easy to use as Opera Mini 4.2 and has a lot of additional goodies – for example, text copy/paste is supported and works, unlike in 4.2. (Note that the text copy/paste in the current beta of Opera Mini 5.0 works just fine on Symbian.)
The only problem I found was the lack of support for Flash Lite 3 – to access Flash Lite content, you’ll still need to use the built-in Nokia Web browser instead. (Nevertheless, you will want to use it was a last resort to play back, say, YouTube videos. Dedicated YouTube players are far better at playing back videos – no stuttering, unlike when using Flash Lite.)
Thanks a lot Amigo!, as always great reviews
I´ll post a link to this on Opera Thread
Cheers,
Menneisyys said:
I’ve thoroughly tested the brand new Opera Mobile 10 beta on all the supported mobile phone platforms (Windows Mobile Professional / Standard and Symbian S60). In general, apart from some problems, I liked what I saw – particularly on Symbian and the touchscreen version of Windows Mobile.
The browser is available for download HERE for both operating systems. For Windows Mobile, a unified download (for both subtypes) is provided.
1. Windows Mobile
Also see the XDA-Devs discussion, which starts on THIS page.
1.1 Touchscreen devices
I’ve installed it on the HP iPAQ 210 and found it great. Sure, it lacks some features (for example, the excellent dynamic zooming & text reflowing features of some (not all!) of the 9.50/9.70 builds and the (hacked) Flash Lite support), but, on the whole, I was more than happy with it. It doesn’t load much faster than the older version (9 seconds as opposed to 10) and, as has already been pointed out, lacks some of the goodies; however, it’s a pleasure to use.
Unfortunately, it (still) doesn’t support Opera Link, one of the best features of Opera Mini and the desktop Opera browser. (One of the reasons I’ve completely switched to using Opera on the desktop.)
Also see THIS demo for more info.
1.2 Non-touchscreen (Microsoft Smartphone) devices
1. Unfortunately, the two hotkeys are in no way supported on any of the tested Smartphones (on the s710, including the ones on the hardware keyboard). Therefore, a cursor emulator is needed to access even the menu at the bottom and almost everything. In-page scrolling and, on the Quick access page (default one and the one that comes up when you open a new tab), switching between the address input field, the Google field and the main surface area works OK. (Hotkeys are supported just great on Symbian S60.)
2. There are no button scrolling shortcuts, as opposed to the SP version of 8.65 (the last Opera Mobile version to have a dedicated MS Smartphone version – see my MS Smartphone Web Browser Bible HERE).
3. While you can’t use the hotkeys in fullscreen mode, with SPHelper, you can still access the two buttons in the lower right and left corners. (Hotkey-based scrolling – 2/4/6/8 – works just great on Symbian S60.)
176*220 (old) MS Smartphones running the official WM5 (tested on the HTC s310 (Oxygen)): excellent (tested running from memory card) program / page load time; responsive. Landscape mode isn’t supported – as opposed to the s710.
HTC s710 Vox (320*240 newer Smartphone running the official WM6): running great. However, multi-function keys on the hardware keyboard don’t work (always the numeric values are inserted) – to enter them, you need to use either the on-screen keyboard (which, BTW, is rendered properly even on a 176*220 Smartphone in Portrait mode) or the numeric keypad.
All in all, until the hotkey bug is fixed (operating the browser with SPHelper is really painful), you will want to stick with either the old 8.65 version or Opera Mini. (This, again, only stands for the non-touchscreen-enabled MS Smartphone platform, NOT the touchscreen-based one!)
2. Symbian S60
It’s nice to see Opera to return to Symbian, which they have seemed to have completely neglected in the last few years.
I’ve tested OM10 on the Nokia N95 on firmware version 30 and found it excellent. It has very quick program / page loading; OK multitabs (albeit, after opening two – large, about 600k+ - Wiki pages, when minimizing Opera mobile, it was immediately terminated from memory, showing Opera indeed took up quite a bit of RAM memory. This was expected – if you need multitab supporting up to 30 pages open at the same time, your only choice is Opera Mini.)
Basically, it’s as easy to use as Opera Mini 4.2 and has a lot of additional goodies – for example, text copy/paste is supported and works, unlike in 4.2. (Note that the text copy/paste in the current beta of Opera Mini 5.0 works just fine on Symbian.)
The only problem I found was the lack of support for Flash Lite 3 – to access Flash Lite content, you’ll still need to use the built-in Nokia Web browser instead. (Nevertheless, you will want to use it was a last resort to play back, say, YouTube videos. Dedicated YouTube players are far better at playing back videos – no stuttering, unlike when using Flash Lite.)
Click to expand...
Click to collapse
OP , i have installed you app, good app but a little clunky in my phone.it shuffled for a long time to enter CNN. i like the icon most. LOL
I like it
Slightly out of date review. And now Opera Mobile 11 does not support Windows Mobile.
Opera mini 11 is for me the best Browser on Android platform.
I was wondering, tht when buying a new smartphone if I go with windows based OS on mobile, will I be able to run any software tht can run on windows based desktop computer? If not, such functionality is expected to come with forthcoming Windows 8 mobile?
PS: I wana run my live stock market terminal on mobile phone.
Since ver 7, the os is no longer called windows mobile; its now called windows phone. but to answer your question, no you can't run desktop applications on windows phone (or windows mobile for that matter) and this is unlikely to change.
That said I'm sure you can find another application to achieve whatever it is that you're after on the marketplace...
:-( my all needs are getting completed with an smartphone, but i guess eventually i will have to buy a laptop as well... just to run my stockmarket software.... Damn and they are telling smartphones (Like SGS2 etc.) are quickly replacing laptops...
PS: Wht is the latest ver. of windows phone called and, what is the windows phone marketplace url (Kind of new to smartphones)
Well for a lot of people smartphones or tablets can replace computers, most people aren't stockbrokers!
The latest version of Windows Phone is 7.5 Mango, which is currently at RTM stage - i.e. released to OEMs pending approval for new devices and upgrades to existing devices.
The Windows Phone Marketplace can only be accessed via the phone or via the Zune desktop software. The Zune software comes highly recommended from me, it's a very, very good media management software and I can't live without the wireless sync function anymore!
You can browse the marketplace through Zune without owning a Windows Phone device.
Perhaps you could let the community know what it is exactly that you need to do and someone might be able to suggest something?
EDIT: As you're new to smartphones, from a usability perspective Windows Phone 7 would be an excellent choice for you - it is simply brilliant to use, the interface is understated and elegant and the lack of pointless graphics makes it both simple and quick. Microsoft have clearly put massive effort into making Windows Phone highly usable and have surpassed pretty much all expectations, especially with the 7.5 update, which brings in a huge amount of functionality. A lot of people try and put Windows Phone down having never used it, because it's one of those things that needs you to spend 10 minutes with it to understand - but once you've spent 9 minutes with it, everything else just seems ridiculously complicated.
olivespin said:
:-( my all needs are getting completed with an smartphone, but i guess eventually i will have to buy a laptop as well... just to run my stockmarket software.... Damn and they are telling smartphones (Like SGS2 etc.) are quickly replacing laptops...
PS: Wht is the latest ver. of windows phone called and, what is the windows phone marketplace url (Kind of new to smartphones)
Click to expand...
Click to collapse
Silverlight in Windows
Hi
Silverlight apps are currently available in Windows and I think that the concept being put out there at the moment is that Windows 8 will run the same apps as Windows Mobile 8.
Nobody knows if this will become a reality or not.
Cheers
andrew-in-woking
olivespin said:
I was wondering, tht when buying a new smartphone if I go with windows based OS on mobile, will I be able to run any software tht can run on windows based desktop computer? If not, such functionality is expected to come with forthcoming Windows 8 mobile?
PS: I wana run my live stock market terminal on mobile phone.
Click to expand...
Click to collapse
The best thing for you to do would be to find a mobile version of the software you are trying to run. Then get the device that runs that particular software.
The closest you'll come to running your "exact" software on a mobile device is to get a Windows based tablet or laptop. But to run your stock software on a smartphone, you will need the "mobile" version of that software, if it exists.
Also, check to see if your stock-terminal application is web-based. If it is, you may be able to access what you need with ANY smartphone through the smartphone's web browser. That means your "stock terminal" would work on Windows Phone, iPhone, Android, etc.
Hello guy,
I have a question,
Do you think i.e10 on rt will support WebGl in a future?????. I don't even know if the system will be compatible with windows rt. I think, it is important for the future, i guess.
I tried the new google maps but it really sloooooooww. Maybe it's quicker on nexus 7 android, its the same cpu/gpu!! Don't know if it's running well on nexus.
What do you think???
Thank you .
At the moment RT doesn't support OpenGl or OpenGl ES. WebGL relies on OpenGL ES.
However. The windows 8.1 previews seem to have a few debug stubs for WebGL in internet explorer 11 so there is hope.
SixSixSevenSeven said:
At the moment RT doesn't support OpenGl or OpenGl ES. WebGL relies on OpenGL ES.
However. The windows 8.1 previews seem to have a few debug stubs for WebGL in internet explorer 11 so there is hope.
Click to expand...
Click to collapse
Humm ok thanks for the answers. Do you think, it's an important things to have webgl??
WebGL exposes OpenGL.
Microsoft's alternative to OpenGL is called DirectX.
DirectX was exposed via Internet Explorer since forever (via the infamous DXfilters and ActiveX controls).
The reason why is because back then it did things that HTML was incapable of doing.
IE in their latest release *dropped* support because html is now *going* to be capable (html5, css3).
Also, this approach opened the browser to all kinds of attacks and we are all glad it is dropped.
Other browsers in their latest releases *embrase* this webgl approach.
The reason why is because html again is incapable of doing 3d and other fancy stuff (I oversimplify things I know, dont flame me).
This approach (webgl) still opens the browser to all kinds of attacks. (ms has expressed conserns and they are right)
So, Is WebGL important?
IE did what webgl does and dropped support. So no. BUT:
Unfortunatelly, the big brother (google) wants us to use the browser for everything, even gaming.
Also, IE is untested by most developers. IE is doomed to make their rendering work perfectly because people need a small excuse to start flaming again.
Because of the above facts, I believe IE is doomed to make webGL available somehow.
Some time in the future, html will be capable again and these workarounds will be probably dropped. Until then, webgl enabled browsers will be unsecure.
(Personal opinion)
PS: Other funny fact: IE had addins like forever. Now the most used excuse for anti-IE is that it does not have addins. Despite that, MS discourages addins because of security concerns (Metro IE does not have them). I personally believe they are right for thisone too.
ActiveX saw little use because it was vulnerable (more so than webgl which although is a security concern, isn't the largest one ever) and proprietary. It only worked in IE which at the time was god awful.
Modern html accomplishes its fancy 3d effects via webgl.... Or the much slower html5 canvas which has pretty poor performance (and is likely the reason that maps is slow on rt, I believe it fallbacks on standard html5 whereas on the nexus it can be hardware accelerated via webgl).
Ok guys. Thanks you for the explanations, i really appreciate. it's really war between all this standard.
Afaik IE11 will support WebGL.
Hi,
Is there any app to remote control a W10M device ??
On Android devices and W8/10 desktops I use TeamViewer and I like it much, however, the W10M version allows me to control another device from the phone but not to control the phone from another device...
What I want is to be able to control a Lumia 650 from a Windows PC. Any utility for that ?? Any way to RDP into W10M ??
Thanks in advance,
Manuel
[ I'm new to W10Mobile (Today!), I've done a search but not found anything about it... ]
nope sorry,isnt possible. no app has enough permissions (or is able to get enough) to do that. dunno if it was possible in the past with the project my screen app (via usb) to make inputs, but that feature isnt implemented in win 10 mobile (was only available in 8(.1)) either way (only screen sharing via miracast is possible with 10 mobile, or continuum)
Thanks for your answer. I suspected it but had some hope...
This is a real drawback, no way to give remote support to users !!
iOS and Android both work really well with TeamViewer..
W10M supposedly has Universal app, but the remote control is just one way... and I need just the other !!
Thanks, Regards,
for such things there a no api, should be possible for a dev to make a "look"on the device possible, but only within that one app. and thats useless, everything else would need deep system access/integration. and that is just not possible (and somehow against ms' safety concept of windows 10 mobile)
call me old fashioned, but i find it useless either way. anyone who needs "remote support" for his phone shouldnt be allowed to have a smartphone or using the internet at all (yes im voting for a "internet driving license", but sadly that system doesnt work on the street at all too...)
hehe... please don't give such ideas... Internet driving license... plus taxes, of course !!
Actually I have lots of that kind of users to support... That's why I need a remote tool !
Once resigned to not having it... MS concept of "safety" seems too different on Desktop than on mobile. WDesktop has RDP tightly integrated (That was my last hope on mobile, to have sth simmilar, but no luck... ) and lots of apps to remote control... Including the W10M version of TeamViewer, that allows you to control a Windows Desktop, and even a Windows Server !!)
It's only me, or... seems weird?
There is a app named "Teamviewer Quicksupport preview" which can be used for remotely control w10 mobile.but it's only available for Redstone user..
Redstone mean insider fast ring?
You can also remote control your device using device portal in developer settings of your Windows 10M. To use it from your phone, go to "127.0.0.1" in your browser. From other device through common Wi-Fi or hotspot connection, your phone's ip address as the link in browser of android device.
(this has some cool stuffs to use).
augustinionut said:
Redstone mean insider fast ring?
Click to expand...
Click to collapse
No different Release Preview , fast or slow
augustinionut said:
Redstone mean insider fast ring?
Click to expand...
Click to collapse
Not ony fast ring ..slow and release preview also..