J
Jeff Higgins
????
I suspect Martin Gregorie means this:
<http://www.microsoftvirtualacademy....windows-8-and-windows-phone-8-app-development>.
????
From the presentation:I suspect Martin Gregorie means this:
<http://www.microsoftvirtualacademy....windows-8-and-windows-phone-8-app-development>.
From what I've written so far you might be able to see where the disorientation / confusion originates from ... My mind says I should do some C proramming where there is the best chance to do some work with it at some company one day. But my heard tells me to do some more fancy stuff like Go or D.
From the presentation:
Platform-specific Features
Similar features with different APIs and implementations
Do not try to reuse code for these features
Some examples:
Application lifecycle (PLM)
Background processing
Tiles and toast notifications
Image/video capture
System services
App bar
Networking differences
windows-phone-8-app-development>.
I hadn't seen that, but had read about the incompatible Win8 APIs in an
article in The Register.
Sure - I'm not saying they should be the same, only that I don't see any
reason why a program shouldn't use the same API to display menus and
accept input from them regardless of how the OS chooses to display the
menus. After all, a program that is useful on a desktop, tablet or phone
will need to display the same menus and accept the same inputs from them
regardless of which device its running on. Similar arguments apply to all
the other elements of a graphical interface.
I did not watch it.
But "Do not try to reuse code for these features" sounds like
"the API is the same but you should do things differently".
Me neither.
I downloaded the slides for the first part of the presentation.
Then I would have been required to register before any more access.
Actually, the point was that these APIs are different and here
is what you can do to maximize code reuse.
One of the slides promises:
<quote>
We are on the path to
Windows and Windows Phone
convergence
</quote>
"these APIs are different" is not a very technical description. It
is even close to me misleading.
MS invented a new API to be shared between Windows 8 and
Windows Phone 8.
Exactly what was requested in this thread.
Windows Phone did not get the full version in 8.0.
People that has counted say that WP 8 WinRT has
2800/11000 of what Win8 WinRT has (measured in
public members of the classes).
MS has also stated that they will increase that in 8.1
(already released for Win, soon to be released for WP)
and further increase it in 9.
I guess short of registering for the course and watching 4-6 hours
of video you could download the first section of slides, as I've done.
MS has "invented" a lot of stuff.
Huh? Now's my turn for the ????Yes.
But wouldn't it make more sense to criticize them for not doing
something if they did not do it?
I agree about the complexity. I'll wager most people do, even C++Way back when C++ was the new kid on the block I remember reading that
the first C++ compilker was actually a standard C compiler with the Cfront
preprocessor substituted for the usual cpre preprocessor.
====
Personally I still can't be arsed to spend the time needed to learn C++.
I looked at it some time ago and found it offensive for both its
complexity and the obscene amount of code generated. In any case, far too
much of the so-called "C++" I've looked at has been nothing more than
ANSI C with comments delimited by "//": and not class or object in sight.
I probably wouldn't resort to C as quickly as you do, but my generalIf a programming task is essentially file manipulation I'll use awk. If
the job is moderately complex and can be written in ANSI C I'll use that.
If an OO approach is called for I'll use Java and, if some fiddling is
required that Java can't do, I'll use a combination of C and Java with
sockets for inter-language data transfer.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.