April 8, 2014
A screenshot of Windows modern UI applications running within a window, rather than full screen.
Here is a screenshot of Windows modern UI applications running within a window, rather than full screen.
As you might have heard, at the BUILD conference last week, Microsoft unveiled that one of the elements of future versions (or updates) of Windows will be the ability to run Modern applications mixed in with desktop ones, that is, running in a windows rather than full screen (as it happens in Windows 8 and Windows 8.1).
Modern UI applications are applications that follow the UI style initially called Metro and are powered by the WinRT engine. Here you can see how your desktop might look like in the future.
posted by
marcocantu @ 10:06AM | 18 Comments
[0 Pending]
18 Comments
Windows Modern UI Screenshot
I am thrilled. The next innovation will be some sort
of "transparency" and/or round border edges and maybe
some gradient styles..... I am so excited
Comment by Dennis on April 8, 13:09
Windows Modern UI Screenshot
Prediction: "modern UI" apps are going to get more and
more "desktop" app features because that's what people
really know and find useful on laptops and desktops.
Another thing they will have to bring back is the Start
button. Microsoft should just eat humble pie on this
one. If it works, why break it? Improve the start
button, don't kill it.
Comment by Wilfred Oluoch
[http://www.ideaz.co.ke]
on April 8, 15:51
Windows Modern UI Screenshot
I'm always reminded of MSN, circa 1998, when I see
the "modern" UI
Comment by Michael S. on April 8, 16:26
Windows Modern UI Screenshot
Whatever. It is not like someone cares about those.
They should have named it Arcane instead of Modern -
this way they might have had some hardcore Windows 2.0
fans return.
Comment by Gad D Lord
[http://www.mtgstudio.com]
on April 8, 19:30
Windows Modern UI Screenshot
I wonder how video and image editing tools like Adobe
After Effects and Photoshop would look with those big
controls!
Microsoft has no clue of what they are doing....
Comment by Eric
[http://www.digifort.com.br]
on April 8, 22:28
Windows Modern UI Screenshot
I want to know how you see.Net Native.
I'm afraid it become the Delphi Killer
http://blogs.msdn.com/b/dotnet/archive/2014/04/02/anno
uncing-net-native-preview.aspx
The .NET Native Preview released today only targets
Store apps but we're working on improving native
compilation for all .NET apps. We've already answered
this question, and a lot of others, by the way, at
the Microsoft .NET Native FAQ:
msdn.microsoft.com/.../dn642499.aspx.
With the .NET Native Developer Preview, apps will get
deployed on end-user devices as fully self-contained
natively compiled code, and will not have a
dependency on the .NET Framework on the target
device/machine. So, no .NET framework required on
the target machine with .NET Native.
Comment by Stone on April 9, 03:16
Windows Modern UI Screenshot
Evokes a trip down the memory lane here as well...
Ah, Fashion is ever going round, I guess those Delphi 1
apps won't look out of place anymore!
Comment by Eric
[http://delphitools.info/]
on April 9, 07:47
Windows Modern UI Screenshot
Stone,
While .NET native seems a nice feature for that platform, I'm not sure
how it affects Delphi. It makes startup faster, JITed (just in time
compiled) code was already quite fast. And they still have the runtime
penalty of reflection-based features and garbage collection.
As for deploying with the full libraries and no runtime dependency, nice,
so their application will get as big as ours (we already deploy with our
libraries and application size is the drawback of that approach).
So if .NET is doing some of the things RAD Studio already does, to me it
sounds we have a rather nice technology and they are catching up ;-)
I know, it is not really comparable, but to all of those saying we need to
copy Microsoft or be doomed, it is interesting to see the opposite
happening (directly or coincidentally, it doesn't really matter).
Comment by Marco Cantu
[http://www.marcocantu.com]
on April 9, 08:53
Windows Modern UI Screenshot
The problem is you're still copying MS (and sometimes
others), just to arrive late with a worse, half-baked
solution, while MS has already moved on, still
delivering a better solution than yours.
For example "And they still have the runtime
penalty of reflection-based features and garbage
collection."
And what are you doing? Relying more and more on RTTI
(reflection, anybody?), adding ARC (a form of garbage
collection, with its serialization penalty),
marshalling API calls, and thinking to remove high-
end native language features (different string types
management, mutable strings, pointers, direct API
calls, etc.).
When Delphi will set its own agenda and work hard on
it, instead of chasing every time the most colorful
and fashionable butterlfy, it will be a great day for
Delphi developers.
Comment by Luigi D. Sandon on April 9, 14:55
Windows Modern UI Screenshot
Luigi, Delphi is setting its own agenda and delivering a multi-device
solution very different from the Windows-centric solution it was in the
past. Not chasing any fashion.
-Marco
Comment by Marco Cantu
[http://www.marcocantu.com]
on April 9, 15:10
Windows Modern UI Screenshot
Unluckily, the actual fashion is exactly "mobile
apps".
IMHO AppMethod would be a good idea if it decouples
Delphi (native development for power users
desktop/server applications) from the "apps
development" tool for "multi-devices". Two products
for different needs (although with something in
common).
Not understanding most apps need some server on the
other side to work, and that desktop applications are
not going away (otherwise MS would have not so many
issues trying to force a non-desktop UI to users) is
dangerous, and the Windows 8 debacle shows it very
well.But Windows 2012 is a very strong server
operating system, and offers powerful features - it's
going on untouched by the Windows 8 UI issues, and
now it is an excellent platform to build complex
software on.
Delivering a "multi-device" solution can exactly
bring you to deliver something with the same
issues .NET is now trying avoid, after all .NET too
was an attempt to offer a less Windows(API)-centric
solution. Maybe you're repeating the same mistake.
MS has very large shoulder and can sustain big
mistakes, Embarcadero mey be not so resilient...
Comment by Luigi D. Sandon on April 9, 16:27
Windows Modern UI Screenshot
Luigi, I have to agree with you that mobile is not the only focus for
development in the future. In fact, it is not our only focus of
development. We are keeping our Windows focus (enhancing the VCL),
going to have new server solutions, and focusing more of having mobile
working alongside Windows applications, rather than pushing developers
to move Windows applications to mobile (which rarely makes sense).
I fully agree also that most apps need a server of some sort, and are
providing a multi-facet solution (compared to Microsoft's Azure
everywhere solution). Appmethod comes as a multi-device plus server
solution.
I guess we might disagree on some of the technical decisions, but the
direction you are suggesting is our direction.
Comment by Marco Cantu
[http://www.marcocantu.com]
on April 9, 20:38
Windows Modern UI Screenshot
Luigi's words were excessive. But I have the same
feeling.
EMB seems to be very difficult to listen to the views
of others.Also refused to acknowledge that not good
enough.
Therefore, more and more people become anxious, and
begin to rage.
"so their application will get as big as ours "
In my opinion, the words is obvious to shirk
responsibility.
I can rephrase VCL code, lead VCL App significantly
smaller. It is not very difficult.Even though I am
not a good programmer.
Comment by Stone on April 10, 01:11
Windows Modern UI Screenshot
For me the question is, would Microsoft support Win32
in future. It seems a crazy question, but it seems
that Microsoft does not care to much what we are
thinking. Customers and developers may have rather
chosen Windows Phones (net/silverlight), but Microsoft
go for WinRT. There are very few App developed for
WinRT because XAML is jut like HTML5: I would never
build a user interface with this kind of technologies.
It is just code obfuscation. App using XAML are for
"Microsoft's developers only". The second problem I
have with Delphi is the weak server side support (and
no support for linux at all). For me Linux is the most
important operating system because it can be downsized
(Windows is burning for a desktop computer several
hundred watts, may be 80 watts for a notebook and
20-40 watts for a Netbook).
That is why I am now using not only Delphi but
Java/c/c++/Python for my work. I try to do as much as
possible with Java, because Java is rather like Delphi
:-), but because we are Hardware manufacturer I must
code also in c/c++. Java does not make my life easier
in this regards. In addition Java enforces certainly
good programming practice, but it come with a cost.
Java does not let you the choice, that is why I prefer
definitely Delphi.
Comment by Alexandre Jacquot on April 10, 17:12
Windows Modern UI Screenshot
1.Replace TList with TList<xxx> in classes.pas. It's
strange! I can't get the necessity. It has no obvious
benefits except to lead the programe bloated.
2.Classes.pas uses Rtti.pas is also avoidable.
3.typinfo.pas and Rtti.pas reference each other.
Typinfo is a more basic unit than Rtti.pas.
Therefore, should do only a Rtti.pas uses
typinfo.pas. If so, class.pas will not rely on
Rtti.pas. Our app can not link Rtti.pas.
These changes are begin from the XE3. My point is
XE3 started doing a lot of bat things. And, until now.
Comment by Stone on April 11, 02:05
Windows Modern UI Screenshot
What is the point of having all this high-powered
graphics hardware with all the eye candy generating
capability if all we are building is 16/256 color
windows, dialogs and forms? Retro is right, I hate the
boring, flat asthetics presented as 'modern'. If I
wanted Windows 3.1 I would have kept a Windows 3.1
machine running all these years. This is all to make
everything look like that dumb mobile Windows look and
feel. Yuch!
Comment by MikeP on April 11, 04:33
Windows Modern UI Screenshot
Delphi XE2
System.Classes.pas 439 lines
System.Classes.dcu 437k
Delphi XE3
System.Classes.pas 531 lines
System.Classes.dcu 1343k
Comment by Stone on April 11, 04:45
Windows Modern UI Screenshot
Sorry, i make some mistake.
XE2
System.Classes.pas 16087 lines
System.Classes.dcu(release) 437k
System.Classes.dcu(debug) 501k
XE5
System.Classes.pas 19515 lines
System.Classes.dcu(release) 1,406k
System.Classes.dcu(debug) 1,570k
Comment by Stone on April 11, 11:28
Post Your Comment
Click
here for posting
your feedback to this blog.
There are currently 0 pending (unapproved) messages.
