Related
WP 7 features are leaking all over the net. Let me list them :
· WP7 will be announced at MWC, and there will be a demo, but this will be just the UX
· MIX will have specific developement focus sessions on WP7
· WP7 supports both Sliverlight (out of browser) and XNA
· Silverlight is version 3.0, with elements of 4.0 plus mobile specific features such as sensors etc
· XNA apps can be developed using XNA GameStudio 3.1
· SL apps developed using Expression Blend 3.x and VS2010
· MS will release a mobile version of VS / Expression which will be free, and VS2010 / Expression Pro will have a free add-on
· WP7 will have an equivalent of .NET CF embedded into SL, but no SQL.
· WP7 will have isolated storage which is accessible using LINQ
· The UX of WP7 is based upon a theme called “METRO” and is similar to Zune HD, but with a completely new “Start” screen.
· No multi-tasking (applications will pause when in the background, however they will support notifications using the MS Push Notifications environment)
· No .NET CF backwards compatibility, however a proportion of the data and business logic in .NET CF could be ported
· MS were confident to have devices ready for Sep 2010
· No MS manufactured device, however much tighter control of manufactring process, so as an example each device has a 3D processing chipset, and MS provide all of the device drivers. So no platform builder. This enables OTA updates and simplified model for ODM’s
· Marketplace will support buy and try before you buy, as well as an API
· ODM / OEM will not be able to modify the “Start” screen, so no more HTC Sense / TouchFlo etc.
· MS are actually ahead of schedule which will surprise the analysts / journalists
· Browsing experience is currently faster / better than iPhone 3G, and they are aiming towards 3GS.
· Browser is based upon desktop IE7 codebase, but with some IE8 functionality
· No in browser Flash or SL
· WP7 has full integration with XBOX Live, and ability to purchase games
· WP7 will use the Zune software for music, videos, photos sync
· WP7 only supports app installation through service based delivery i.e. marketplace, so no side-loading
· MS will provide a hosted push notifications environment
Click to expand...
Click to collapse
[Source]
While this might disappoint most but I for one am really happy to see that Microsoft is finally taking this seriously and has worked on WM7 from ground up!
Finally we will be able to get the User Experience comparable to iPhone/Android! Xbox Live and Zune integration sounds totally awesome!
Well this would be the media edition of the phone.... and all the OEM's will sport the 'professional' version of the phone...makes sense.
Still that won't make any Extreme Changes. The basic UI will remain the same. I feel there won't be any major differences User Interface wise between Windows Mobile 7 versions...they've already disallowed 3rd Party UI!
Im afraid your wrong . HTC have already said they will continue supporting Sense 3D on WinMo7, now they wouldnt have been able to do that if MS is going to lock down the UI.
I think/heard there will be 2 versions of the OS, the zune version which is what you see above (this will run on MS hardware, pretty much like the zune) and all the OEM's such as HTC, Toshiba, SE, etc etc will run the pro version of the OS which will similar to what we are used to...how different the OS will be in terms of GUI will be interesting to see, i sure hope that the zune version doesnt get all the goodies.
"WP7 only supports app installation through service based delivery i.e. marketplace, so no side-loading"
Does that mean we could not anymore install cab files from xda.dev ?
How far the new OS is going to be customizable is still to be seen. I think they will keep everything closed just like the iPhone and only allow limited modifications.
no multi tasking?... ... ...the point is???
If the above features are true ... Good bye WinMo7
I will go with Android (Or iPhone 4.0?) ...
^Could not wait and have already went over to the dark side...android is very cool best thing I've done!
this looks like some fanboys conspiracy
all windows mobile power (from the users point of view) that its so customizable and like micro computer
if wm7 gonna be kind of an iphone people will prefer the real iphone its perfect in its own limited way...
I can only say, if winmo drops multi-tasking, I'll drop winmo.
Gee. if people want a iPhone they'll get one.
Not everyone may be able to afford a 1ghz processor now, but the future's going to catch up before winmo7 comes out anyway.
tuksedra said:
no multi tasking?... ... ...the point is???
Click to expand...
Click to collapse
Think of the pleasure to be got from watching WinMophiles having to admit to iPhonatics that WinMo is now even worse at multi-tasking than the iPhone is! (rotfl)
moooxooom said:
I can only say, if winmo drops multi-tasking, I'll drop winmo.
Gee. if people want a iPhone they'll get one.
Not everyone may be able to afford a 1ghz processor now, but the future's going to catch up before winmo7 comes out anyway.
Click to expand...
Click to collapse
x2!!!
Without Multi-Tasking, HTC Sense and not be able to install whatever I want in where I want, I will never buy a new winmo pda phone again...
I'll guess I'll have to go to Android or in the worst case to iPhone
Multi-Tasking would be indeed a absolute no-go. I'm sure, that will never NOT happen.
I hope, you're also in the future allowed to install what you want where you want. I hate these Iphone restrictions. Let's hope, this will not gonna happen for WM.
I think companies are going paranoid... don't understand why many restrictions when on the desktop side u can do whatever u want... because of a majority of dumbs, that don't even know how to shutdown a computer, the rest of us have to suffer of these limitations...
No multi-tasking means I'm sticking with 6.5.3 (or whatever they call it) or going with Android.
Don't they realize that competing with Apple in Apple's arena will only get them smoked PLUS alienate their fanbase? We go to WinMo because we DON'T want iphone os. What we do want is a rebuilt, faster, better WinMo os that is just as customizable as the current os.
Seriously, if they are planning on putting out a winphone os, they are going to lose. period.
fb401 said:
No multi-tasking means I'm sticking with 6.5.3 (or whatever they call it) or going with Android.
Don't they realize that competing with Apple in Apple's arena will only get them smoked PLUS alienate their fanbase? We go to WinMo because we DON'T want iphone os. What we do want is a rebuilt, faster, better WinMo os that is just as customizable as the current os.
Seriously, if they are planning on putting out a winphone os, they are going to lose. period.
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What he said
Maybe they will remove the file manager. If they remove the file manager, the device is no more PDA.
fb401 said:
We go to WinMo because we DON'T want iphone os.
Click to expand...
Click to collapse
"We" aren't exactly a mass market, though. There were considerably more iPhones sold in the last 12 months than every single model of Windows Mobile phone put together. (WinMo is currently a distant fourth in the smartphone market behind Symbian, RIM and iPhone, with Android closing). The bulk of those who still buy WinMo phones are corporate customers. If abandoning the needs of a tiny minority of users (i.e. us) will net Microsoft a substantially improved marketshare, you can bet they'll do just that.
Having said that, I'm inclined to view this particular rumour with some suspicion; at the very least, with other rumours persistently claiming that there is more than one version of WM7 in the offing, it certainly makes no sense to assume, at this stage, that every available version will be like this.
sigh..........
I really hope some of this is not true. And I will wait until some formal announcement to make up my mind BUT if true, no multitasking, no user UI customization, no apps installed to sd card, all apps through the Marketplace?? Had I wanted to live in a walled garden I would have already bought an Iphone.
I've been using WinMo PDAs and phones for more years than I care to admit. Maybe it is time to simplify my life and get a dumb phone and swear off tech. Guess I can start carrying around all my passwords written down in a code again in my purse (shades of the 80's here except that I have a bunch more and they are all pretty complicated now- I do love my ewallet). grrrrrrr...............
Qt apps work on WinCE. If WP7 is built on top of WinCE, why would Qt apps not be allowed on Win7?
I'm just trying to make sense of it here. Is it an artificial Microsoft restriction for their platform?
Because third-party apps are managed in .NET compact framework. Qt is a C++ framework and thus unmanaged. This is a smart move by MS as it increases system stability and enhances user experience.
leonard2010 said:
Because third-party apps are managed in .NET compact framework. Qt is a C++ framework and thus unmanaged. This is a smart move by MS as it increases system stability and enhances user experience.
Click to expand...
Click to collapse
If that's the lame reason they give for it not being doable then I will just need to hack Qt onto it. Dumbest move in Nokia's history!
discourse said:
If that's the lame reason they give for it not being doable then I will just need to hack Qt onto it. Dumbest move in Nokia's history!
Click to expand...
Click to collapse
givin that one of the main reasons that windows mobile 6 and for that matter windows desktop can be unstable is poor quality 3rd party programs i think the move was a very good one, forcing programers to stick to strict controls means they have to develop good software, also givin MS got most of the flak for these crap programs i think it was a good move on their part
at the cost of lower performance and code easily being stolen. MS don't care about developers. Hacking a silverlight app onto CE and calling it a new OS was a terrible shortcut and will cost them in the long run.
It's a matter of time until Microsoft releases a Native Development Kit. In a recent interview Brad Watson from Windows Phone 7 Development team said:
Brad Watson said:
8) What about native SDK? Android got theirs later, should we expect Microsoft to provide a native SDK also, or just forget about it ?
BLW – if by native SDK, you are asking will we allow anyone to run C or C++ unmanaged code on the device, the answer is “not now.” Our primary concern is ensuring that there is a fantastic customer experience on the phone. We recently announced that we have satisfaction rates for the phone at 93%. That’s amazing. We attribute at least some of that to the fact that customers can buy apps that they don’t have to worry will trash their phones, and they don’t have to worry because of the managed platform.
Over time we will certainly relax certain restrictions on the phone, but we cannot compromise the integrity of the phone experience or the marketplace experience.
Click to expand...
Click to collapse
Microsoft has to release a NDK because the competition has a NDK. Hopefully the competition will have more and more NDK applications (Firefox, Skype) which would make them more appealing to the user.
When such a NDK will be present, Qt (at least lighthouse) will be ported to Windows Phone 7
indiekiduk said:
at the cost of lower performance and code easily being stolen. MS don't care about developers. Hacking a silverlight app onto CE and calling it a new OS was a terrible shortcut and will cost them in the long run.
Click to expand...
Click to collapse
While I agree it's far from the entirely new OS we were promised I very much doubt it will cost them in the long run. They have provided a OS experience that is second to none, this is all because of the limitations they have put in place.
I would expect the platform to open up somewhat for the next wave of [higher-end] devices giving existing users an iOS-like experience where you can certainly upgrade to utilize multitasking and all that jazz but it will cost you some of the current smoothness of the UX.
The fact that .Net assemblies are easily decompiled into fully working Visual Studio projects hasn't been a huge problem on the desktop and as obfuscating tools become better and better I see no reason why it should lead to a problem on the mobile platform either. Looking thru some of the recent marketplace apps they are all but decipherable for the average developer. Also, as more and more processing moves to the cloud it becomes less and less of a problem - most startups are neither willing not capable of mirroring your closed-source/protected backend services.
The missing NDK is not the sole reason. The OS IS different. As others have pointed out, quite some GDI stuff is just not there, or doesn't do anything. So, Qt would probably just not start. And as there will never be (as MS said) (official) OpenGL drivers on WP7 you can't switch the backend.
And there has to be already some kind of NDK, as e.g. Navigon Select is a semi-native application and it is not created by OEMs.
Hades32 said:
The missing NDK is not the sole reason. The OS IS different. As others have pointed out, quite some GDI stuff is just not there, or doesn't do anything. So, Qt would probably just not start. And as there will never be (as MS said) (official) OpenGL drivers on WP7 you can't switch the backend.
And there has to be already some kind of NDK, as e.g. Navigon Select is a semi-native application and it is not created by OEMs.
Click to expand...
Click to collapse
They say IE9 will have accelerated graphics support, which I presume is based on Direct3D. For WinPhone7 Qt needs a Direct3D backend, which should work on all WinPhone7 devices.
Qt should have the same capabilities of IE9, which AFAIK is not written in managed code.
Qt could also use Google's angleproject which should help in translating "OpenGL ES 2.0 API calls to DirectX 9 API calls".
Since this is a discussion thread, this is going in WP7 General.
~~Tito~~
It will simply not happen. It's that easy. (Not w/o homebrew that is)
By not allowing Qt on WP7, Microsoft and Nokia have just shot themselves in the foot. Instead of offering a smooth migration path for the millions of Nokia users and devs, they've basically alienated the entire community. WP7 is also losing out on thousands of high quality applications like Angry Birds for Symbian^3 and MeeGo that was developed using Nokia's Qt SDK. http://www.youtube.com/watch?v=mS1dwYmKMjs
discourse said:
If that's the lame reason they give for it not being doable then I will just need to hack Qt onto it. Dumbest move in Nokia's history!
Click to expand...
Click to collapse
Good luck hacking Qt into it.
Using .NET also increases Security.
WP7 doens't need Qt, and Microsoft should do whatever it can to stop Nokia from putting Qt in WP7.
Those reasons aren't lame, unless you're missing the portion of you brain that controls logic.
discourse said:
By not allowing Qt on WP7, Microsoft and Nokia have just shot themselves in the foot. Instead of offering a smooth migration path for the millions of Nokia users and devs, they've basically alienated the entire community. WP7 is also losing out on thousands of high quality applications like Angry Birds for Symbian^3 and MeeGo that was developed using Nokia's Qt SDK. http://www.youtube.com/watch?v=mS1dwYmKMjs
Click to expand...
Click to collapse
It's much easier to develop for WP7 than it is for Symbian/Qt. I don't think the developers will have much of an issue with it. They didn't shoot themselves in the foot, you people just AREN'T developers, and don't understand it.
You know you're talking to clueless people when Angry Birds is the epitome o fa high quality application to them.
Cause you cannot develop Angry Birds in XNA, and you seriously believe porting Angry Birds to WP7 will involve nothing other than a few code line changes and a recompilation?
Give me a break.
I wish Microsoft had partnered with SE or something. Nokia's fanbase are more bat**** crazy over these pet projects than the Android people.
Qt will continue to be the development framework for Symbian and Nokia will use Symbian for further devices; continuing to develop strategic applications in Qt for Symbian platform and encouraging application developers to do the same. With 200 million users worldwide and Nokia planning to sell around 150 million more Symbian devices, Symbian still offers unparalleled geographical scale for developers.
Extending the scope of Qt further will be our first MeeGo-related open source device, which we plan to ship later this year. Though our plans for MeeGo have been adapted in light of our planned partnership with Microsoft, that device will be compatible with applications developed within the Qt framework and so give Qt developers a further device to target.
Updates for Android devices are always rolled by the gadget manufacturer, so every time Google introduces a new update we have to wait till the manufacturer of the device decides to roll it out, this obviously takes a lot of time and puts Android at a disadvantage against Apple and Microsoft.
For a Windows device irrespective of the manufacturer if Microsoft rolls out an update all can avail of that update through windows update. Android also being an open platform like Windows should be able to do the same.
If I have a software CD of Windows 7 I can install the software in any manufacturers PC and use it. I may just need to do some additional driver installation if required.
Why can't Android develop their platform to function in a similar manner so that once a new version of Android is released I can install it it any device and o fcourse put in the specific drivers to make it work if required.
With the approach of Microsoft looking very prominent now for both Smartphones and Tablets, this may just be a warning bell for Android, I hope they have their eyes and ears open.
Would be nice to know the views of others. As an Android user do you feel this would be a good step for Google?
kaus1108 said:
I may just need to do some additional driver installation if required.
Click to expand...
Click to collapse
The above is the key sentence in your post. The problem is that without the correct hardware drivers for your specific phone the OS may not be able to boot at all and will certainly have limited functionality - just look at the issues there are with trying to run leaded ICS / JB ROMs on phones that don't have an official version of the ROM available with the correct drivers yet.
The reason that Microsoft is able to push out a new OS and have it (mostly) work on any manufacturers PC, with any hardware, is that all the hardware manufacturers are given alpha/beta copies of Windows to test their hardware on and to allow them to build the drivers well in advance of the OS being released by the guys in Redmond.
Google don't do that. They release the OS immediately they have hardware support and compatibility for their devices - and let everybody else deal with the aftermath
windows is the opposite from open platform!
android is an open platform.
the phone makers are free to use android as they wish, they can decide if to upgrade or not.
google only realeses the source code.
XDA is there for providing the latest update.
My phone was supported by Samsung till Gingerbread. But I got jelly bean from XDA devs just after a week after the source code release.
But it does have some bugs which cannot be solved without Samsung's help.
But if you wanted the fastest OEM updates, buy a Nexus.
But 50% of the people are normal users who do not care about updates and new android versions.
Sent from my GT-S5830 using Tapatalk 2
SimonTS said:
The above is the key sentence in your post. The problem is that without the correct hardware drivers for your specific phone the OS may not be able to boot at all and will certainly have limited functionality - just look at the issues there are with trying to run leaded ICS / JB ROMs on phones that don't have an official version of the ROM available with the correct drivers yet.
The reason that Microsoft is able to push out a new OS and have it (mostly) work on any manufacturers PC, with any hardware, is that all the hardware manufacturers are given alpha/beta copies of Windows to test their hardware on and to allow them to build the drivers well in advance of the OS being released by the guys in Redmond.
Google don't do that. They release the OS immediately they have hardware support and compatibility for their devices - and let everybody else deal with the aftermath
Click to expand...
Click to collapse
Thank you for the response and I do agree with what you say and the key to it is that there are certain things that Microsoft do and Google don't and how it is going to impact users in the future.
I remember when I moved from Windows Vista to Windows 7 all the Vista drivers were functioning allright after installing Windows 7 and I have also faced situations where I did not have certain drivers but the PC still functioned on generic drivers provided in the Windows software.
Don't you feel it would be much better if Google just released a Jelly Bean OS and left it to us to install it and I am sure that based on devices already in the market those drivers can always be included in the OS and each phone would pick its own based on its hardware. Only the new devices would need new ones which Google may not be able to provide. If this were true today I would be installing JB in my Galaxy S3 and not have to wait for Sammy.
djbijo said:
windows is the opposite from open platform!
android is an open platform.
the phone makers are free to use android as they wish, they can decide if to upgrade or not.
google only realeses the source code.
Click to expand...
Click to collapse
No, Windows is quite open. Apple is the closed one.
Sent from my MB508 using xda premium
I'm wondering if apps that are on windows store for WP8 if will work on WP7.8 devices or there will be an option for developers to port easily the apps to both version of OS with same source code but with little optimizations?
I try to search something on Google but i didn't find something.
XAP and apx
well . it will NOT work . more likely developers will now have to decide .. program will run on ALL available devices or only on new .
there are 2 formats linked with minimal hardware requirements
1. XAP - Qualcomm S1 800 mghz / 256 ram. it supposed to be like universal
2. APX . qualcomm S4 / 512 ram
windows Phone 7.8 - Supports only XAP
Windows Phone 8 - Supports APX and XAP
I got HTC 7 Mozart: http://www.gsmarena.com/htc_7_mozart-3530.php as i can see thee is 512MB+ RAM so ... i hate Microsoft and i will never buy again MS Product.
512 .. and ? it only allows run FULL version of 7.x without any limitation . apparently there is also subclass of applications which require 512 ram for and for example will not work on devices with 256 ( lumia 610 and 510 ) . as well as windows phone 8 / where some applications want 1 gb .
and you forgot about CPU lol :laugh:
phones divided by generations . inside generation ( os version ) phone must run and application . upper generion must run older apps in compability mode with some impovenents . idea similar to consoles like Xbox and playstation ( for example you cant run games from ps3 on ps 2 and 1 ) . why split ? becose developers who want to develop application for android really *****ing bricks . from market fragmentation and diversity . in ms way
1. developer know target hardware and its capabilities .
2. developer know supported api set
API set heavily related to hardware itself . for example DX 9.3 , and some programming sets heavlily related to OS kernel . you may know that windows phone 8 is Windows NT .Not Windows CE 7.1 BASED
mo3ulla said:
512 .. and ? it only allows run FULL version of 7.x without any limitation . apparently there is also subclass of applications which require 512 ram for and for example will not work on devices with 256 ( lumia 610 and 510 ) . as well as windows phone 8 / where some applications want 1 gb .
and you forgot about CPU lol :laugh:
phones divided by generations . inside generation ( os version ) phone must run and application . upper generion must run older apps in compability mode with some impovenents . idea similar to consoles like Xbox and playstation ( for example you cant run games from ps3 on ps 2 and 1 ) . why split ? becose developers who want to develop application for android really *****ing bricks . from market fragmentation and diversity . in ms way
1. developer know target hardware and its capabilities .
2. developer know supported api set
API set heavily related to hardware itself . for example DX 9.3 , and some programming sets heavlily related to OS kernel . you may know that windows phone 8 is Windows NT .Not Windows CE 7.1 BASED
Click to expand...
Click to collapse
I feel like they sh1t on us with this, they push the WP7 and now they remove it from market with WP8...
when Apple can upgrade iPhone 3G to iOS6, MS can't upgrade a one to another version of OS
1 . you cant upgrade Iphone 3g to ios 6. only 3gs .
2. Ios6 on 3gs - is pretty same as 5 . nothing new.
3. despite on possobility of implement siri on 4g . they did not
4. there is plenty of apps which require dedicated minimum of Iphone (4 and later ) and not working on any others 3-3gs ) .
same approach as apple implemented by MS .
in 7.8 implemented most of features to keep platform inside Windows Phone ecosistem without any problem ( well as some sort of - low end ( :laugh: . same design . close API and programming functionality .
and Nt kernel a bit huge for low end devices , its not CE with minimal system requirements
if you think that APX will become a REQUIREMENT you are wrong . from developer side . APX more like an option
Gizmo_x said:
I got HTC 7 Mozart: http://www.gsmarena.com/htc_7_mozart-3530.php as i can see thee is 512MB+ RAM so ... i hate Microsoft and i will never buy again MS Product.
Click to expand...
Click to collapse
it's not just the ram, it's also the chipset your HTC mozart still using 1st gen snapdragon, so it might not be powerful enough to run win 8 apps
as ms supposed
apx intended for
1. HD applications or programs ported from windows RT
2. application with exccessive calculations or graphical requiremens ( premium games )
for rest of applications is still intended - xap
The HTC Mozart is now 2 years old. If it gets WP 7.8 it will still have gotten better/longer support than most android devices. Windows Phone 8 is a huge overhaul of the OS (and it uses a different kernel) so WP 8 apps can not run on WP7.5/7.8 devices, however WP8 has been designed to be backwards compatible so WP8 will run most of the WP7.5/7.8 apps.
I think it is bold to assume that every single developer will instantly abandon the WP7.x platform completely, more likely they will put out one version for each system.
Still, if you'd rather move to android or iOS, no one is stoping you.
Time to say good bye for WP7.8 by MS.
i have an other question but it is related to apps and windows phone 7.8.
Are we gonna have some new SDK coming out for the 7.8 because i see there are some differences, the live tiles which are developed with micrsoft windows phone 7 /7.1 /7.1.1 SDK flip now on 7.10.8858 ROMs just like the wp8 tiles, it is faaaar better, so my question is can we expect something like an 7.8 SDK with some new abilities for the live tiles, like making big live tiles for the 7.8? i would love to have my app have the same visual abilities like the live tiles on wp8. for now they fliping the same way. i hope we get some API with which we can work to make the big one s too and some other transition effects like on th e wp8.
Gizmo_x said:
Time to say good bye for WP7.8 by MS.
Click to expand...
Click to collapse
Ok, good bye. Have fun with android or iOS, whatever you prefer.
Dinchy87 said:
i have an other question but it is related to apps and windows phone 7.8.
Are we gonna have some new SDK coming out for the 7.8 because i see there are some differences, the live tiles which are developed with micrsoft windows phone 7 /7.1 /7.1.1 SDK flip now on 7.10.8858 ROMs just like the wp8 tiles, it is faaaar better, so my question is can we expect something like an 7.8 SDK with some new abilities for the live tiles, like making big live tiles for the 7.8? i would love to have my app have the same visual abilities like the live tiles on wp8. for now they fliping the same way. i hope we get some API with which we can work to make the big one s too and some other transition effects like on th e wp8.
Click to expand...
Click to collapse
I assume that there will be an addition of wide tiles to the API so probably a small version bump in the SDK. But if we get that for sure only time or MS can tell. Maybe they'll still lock the wide tiles to OEMs, just like they currently do (officially)
I assume that there will be an addition of wide tiles to the API so probably a small version bump in the SDK. But if we get that for sure only time or MS can tell. Maybe they'll still lock the wide tiles to OEMs, just like they currently do (officially)
Click to expand...
Click to collapse
if they lock the big tile to OEMs that would be a disappointment to all developers. first the wp8 SDK needs to much resources. i have to buy additional 2GB of RAM, and i need to reinstall my windows 8 to x64. Thats to much for the majority of developers to ask for. So wp8 could also make an slow progress on apps because of that fact. and the last thing about all that is we must pay to develop and spread our apps from which the Windows Phone ecosystem lives! i would set the developer price to $0 for the once which are offering free no ad apps. if you want to add ads to your apps microsoft gets an % share of the earnings, and the third possible situation you want to make paid apps, you pay % of the share of each app selled. so every possible developer would jump on the wp7 wp8 development. but if we pay, like i, and get our apps out, then we get the SDK late, and it uses s o much resources and Microsoft earns on us then this is not ok! They are selling apps as an major feature, and without developers no apps, no live tiles - and no apps means no business. but Microsoft wants that we pay for it to develop no matter how much we are doing for the community.
Gizmo_x said:
Time to say good bye for WP7.8 by MS.
Click to expand...
Click to collapse
Actually, this will keep 7.8 and the developers making apps for it, alive.
MS intends to keep 7.8 as the lower to mid-high end of their market, with 8 being the exclusive high end. More people will have 7.8 than 8, therefore, apps are needed more on 7.8 than on 8. This means 7.8 will not die, because both devs and MS need it.
In fact, every app that does not require very precise programming(AKA C++) will be written in the 7.8 sdk.
mcosmin222 said:
Actually, this will keep 7.8 and the developers making apps for it, alive.
MS intends to keep 7.8 as the lower to mid-high end of their market, with 8 being the exclusive high end. More people will have 7.8 than 8, therefore, apps are needed more on 7.8 than on 8. This means 7.8 will not die, because both devs and MS need it.
In fact, every app that does not require very precise programming(AKA C++) will be written in the 7.8 sdk.
Click to expand...
Click to collapse
as i know wp8 will have native code execute, what about wp7.8?
mcosmin222 said:
Actually, this will keep 7.8 and the developers making apps for it, alive.
MS intends to keep 7.8 as the lower to mid-high end of their market, with 8 being the exclusive high end. More people will have 7.8 than 8, therefore, apps are needed more on 7.8 than on 8. This means 7.8 will not die, because both devs and MS need it.
In fact, every app that does not require very precise programming(AKA C++) will be written in the 7.8 sdk.
Click to expand...
Click to collapse
yeah but to develop for the WP7.8 OS you need the WP8 SDK. windows blog stated this one or two days ago. If you want to use the new features like the biggest live tile you will need wp8 SDK. and therefor plenty developers will say this is bull****, because i think 50% or more of the world wide developers need to upgrade their PCs to run the WP8 SDK. and that gonna be hard for Microsoft. The WP7 system lives from apps, if you dont have developers to develop it, what will happen with WP8???
and if you ask me i wish they make and 7.8 sdk which can run on the same devices like 7.1 SDK. but i think that's not gonna happen, Microsoft want that we buy windows 8 x64 to developer for Windows Phones (7.8 and 8)
Dinchy87 said:
yeah but to develop for the WP7.8 OS you need the WP8 SDK. windows blog stated this one or two days ago. If you want to use the new features like the biggest live tile you will need wp8 SDK. and therefor plenty developers will say this is bull****, because i think 50% or more of the world wide developers need to upgrade their PCs to run the WP8 SDK. and that gonna be hard for Microsoft. The WP7 system lives from apps, if you dont have developers to develop it, what will happen with WP8???
and if you ask me i wish they make and 7.8 sdk which can run on the same devices like 7.1 SDK. but i think that's not gonna happen, Microsoft want that we buy windows 8 x64 to developer for Windows Phones (7.8 and 8)
Click to expand...
Click to collapse
Upgrading to win 8x64 costs like 50 bucks....not that much considering you get a lot of sweet stuff.
The bigger problem will be the emulators which require very specific hardware power. But than again, you should have a phone by now.
Gizmo_x said:
as i know wp8 will have native code execute, what about wp7.8?
Click to expand...
Click to collapse
officially there is no native code fore 7.x family at all.it just never intended.due limitations of ce7kernel(there is no security for such code at all)
Native code on RT (phone. And windows rt edition).runs in sandbox enviroment .like traditional metro apps (7x).so no kernel mode at all.it suitable only for sharing programming model with desktop version
mo3ulla said:
officially there is no native code fore 7.x family at all.it just never intended.due limitations of ce7kernel(there is no security for such code at all)
Native code on RT (phone. And windows rt edition).runs in sandbox enviroment .like traditional metro apps (7x).so no kernel mode at all.it suitable only for sharing programming model with desktop version
Click to expand...
Click to collapse
then Wp7.8 will lose opportunity for Cross platform game engines like Unity3D because they are going to support only Wp8.
mcosmin222 said:
Upgrading to win 8x64 costs like 50 bucks....not that much considering you get a lot of sweet stuff.
The bigger problem will be the emulators which require very specific hardware power. But than again, you should have a phone by now.
Click to expand...
Click to collapse
I'm speaking of development for 7.8 Europe and eat Europe, Asia markets will be very good for wp7.8 development. and 7.8 will be tied to the WP8 SDK. and i have already 7.8 and i dont want to develop for wp8 for now. the problem is not in windows 8, the problem is when they told us about the specifications. i already had x86 as they said that. and i dont have 4GB RAM and no CPU with SLAT support. this will be in east Europe about 200-250$ investment! for what? for microsoft that they can live with WP8 and with our apps? They live of our apps they should give us what we need to develop, 7.1 sdk run very well on my pc and i have no problems, and if 7.8 is stil a 7 then why new resource needs and specifications? I think their lazy to make an custom sdk for 7.8 and will just reflection some stuff from wp8. and an reflection uses the wp8 SDK and of course windows 8 and 4gb ram an an CPU with SLAT. so 50% of the worldwide developers must upgrade... half of my friends must upgrade to develop further for Windows Phone 7.8 and that is bull****.
Hi guys, I just got my surface rt And I was wondering should I keep windows 8.1 or just 8? Is it worth it to jailbreak ? Thanks
There are plenty of threads already on this topic...
Anyhow, IMO Windows RT is nigh-useless without jailbreaking. 8.1 helps a little but it's still pretty bad. On the other hand, the RT hacking scene has lost a lot of steam while waiting for an 8.1 jailbreak to come out, and most of the apps that were ported or created specifically for RT are now obsolete versions, abandoned partially complete, or both. They are still useful, but there's limits.
In any case, it really comes down to your use cases. If you need Outlook, use 8.1. If you want to run DOSBox games, use the jailbreak. If you need the latest and greatest Windows Store apps, use 8.1. If you want to try running the x86 dynamic recompilation layer (one of those incomplete-and-abandoned projects, though it works for some normal Windows apps) use the jailbreak. If you want to run the latest version of IE, use 8.1. If you want to use a mostly-functional WebKit-based browser (i.e. not IE), use the jailbreak.
Or you could try contributing to getting the jailbreak working on 8.1, I guess. That would be the best of both worlds, and would probably jump-start development for RT again.
GoodDayToDie said:
There are plenty of threads already on this topic...
Anyhow, IMO Windows RT is nigh-useless without jailbreaking. 8.1 helps a little but it's still pretty bad. On the other hand, the RT hacking scene has lost a lot of steam while waiting for an 8.1 jailbreak to come out, and most of the apps that were ported or created specifically for RT are now obsolete versions, abandoned partially complete, or both. They are still useful, but there's limits.
In any case, it really comes down to your use cases. If you need Outlook, use 8.1. If you want to run DOSBox games, use the jailbreak. If you need the latest and greatest Windows Store apps, use 8.1. If you want to try running the x86 dynamic recompilation layer (one of those incomplete-and-abandoned projects, though it works for some normal Windows apps) use the jailbreak. If you want to run the latest version of IE, use 8.1. If you want to use a mostly-functional WebKit-based browser (i.e. not IE), use the jailbreak.
Or you could try contributing to getting the jailbreak working on 8.1, I guess. That would be the best of both worlds, and would probably jump-start development for RT again.
Click to expand...
Click to collapse
Okay thanks ! Can I go back to win8 by resetting my rt in settings ?
If you save the 8.0 recover image, yes. I'm not sure whether it's saved under normal upgrade circumstances; I removed mine to free up space. You can also download the 8.0 image and restore it.
It's also possible, though a little complicated, to install 8.0 and 8.1 at the same time, in a dual-boot configuration. Doing so uses a lot of the tablet's internal storage though.