Live Tiles, they're.. real!

Windows launches Groove Music to update the tile content, and tiles support any multimedia Doors does, so shapes, sprites, text, and more work.

The only problem is the amount of RAM, it has to launch the app to update the tile content, and it's fine for now because they're small, but larger apps can't support this awesome feature.

Check out the demo below, and remember to give feedback as always!

https://goo.gl/bgvwEf

Maybe have a small subprogram with all the variable names necessary for the tile?

Build 10584.71: http://1drv.ms/1ncaDzy

Reset, transfer everything to the archive, run Doors, and then Settings.

This build includes notable improvements, but Start is broken. Can someone find what I'm/Doors is doing wrong?

ALPHA=START OPTIONS
WINDOW=BACK
ZOOM=START
TRACE=CORTANA
2ND=HAMBURGER MENU

DO NOT CLICK Y=

http://pastebin.com/UVjRw6Z1

Simply put, there's a random 6 outputted on the screen that I can't remove.

This is build 10584.96, including Task View, a new Start experience with Live Tiles, and stability improvements overall. Task View uses some elements of new, greatly optimized OneCore background engine. Examples of OneCore taking place aren't visible at first, but two examples are the new launching mechanism for apps (look closely at the splash screen and how Task View launches) and universal app scaling (Continuum bar, apps can be freely moved now).

As always, feel free to ask questions or submit feedback! A build should be coming soon using a new installation method (think gears).







-n

Looking at some of your code, I've found a few random optimizations you could bring. I haven't looked at every file, but you mentioned that some of these routines come up in other files as well, so hopefully, these will not only help for where I found them but also where you think these optimizations might come in handy. Some are quite meaningless while others are larger. I've listed them all using the same method to make it simple to understand. The first line of each optimization is the file followed by the line at which the code was found. The 2nd line is the original code, the 3rd line is the words "could be", the 4th line is my version, and sometimes, there are little explanations in parenthesis underneath Hopefully these can make your project slightly smaller and faster

Code:

Battery Saver:


Glance:

Does anyone make universal apps for Windows 10/Mobile?

If so, in which languages?

Your wp10 thing seems cool! Could you port it ti monochrome calcs?

I don't think so.
1) Is is monochrome, so images would not work
2) The screen is much smaller, so you need to modify ALL the graphing stuff
3) The commands of DCS7 are not the same as DCS8
4) The SE does not have all the commands the CSE has.
When solarsoftware will do this, it will take a lot of time, because it's almost the same as making a new Windows 10 for the monochrome calcs.

I go on and off in C#. Occasionally I uninstall VS because it's either that or an Insider build install.

So, when DCE comes out, would this work on the CE directly, or would it take a long time to rewrite it for CE calcs? I have one, and I just want to know because this project looks awesome. If I seem like a newbie for asking, it's because I am.

This is not compatible, since the program is not in half-resolution mode. If it were, it could be compatible.

Is the win10 port faster?!

I tried downloading this onto jusTIfied, but kept getting an "INVALID DIMENSION" error. I think it was because the list "TIME" was not there or something. Did I do something wrong? I tried running settings, but had no luck. Also as a suggestion, I think it'd make sense for your builds to be grouped together, so the user can ungroup it on the calculator, instead of moving each file one at a time onto jusTIfied.

Wait...so would this work if I used calc84's LCD tool? It's bundled with DJ O's Sord of Atari.

Long time, no see!

This build includes some major performance, stability, and all-around improvements, with the addition of an on-device Visual Basic AOT compiler (more on that later), and pill switches.

OneCore has also been drastically improved in this build, along with the addition of toggle switches (thanks to PT_).

Dynamic memory allocation has also been finalized, and is the method in which resources are manipulated in the background without disturbing on-screen content (real-time multi-tasking). Simply put, the current app gets suspended with a hook, gets replaces with on-the-fly applets, and is restored after. Here is a diagram of how pill switches are currently displayed:



This contributes to a slight delay, which will be fixed in the future. Here are the on-screen results of what the toggle switches look like (all properties can be customized, whether it be if the switch is active, background and foreground colors, and if it is enabled):




Who knows, maybe a build is on the horizon? (:



?

Third-party apps and programs are still supported.

This thing here, under "Stuff nobody reads."

But this is pretty cool! Is it a program that uses xLIBC?

Yeah, this will run.

This isn't a program, it's a shell (OS-ish).

Alright, I'll run LCDtool and try your latest build.

And by Shell-ish, do you mean a program shell that runs within the OS(Doors, Celsium,Ion,etc), something that runs somewhat outside the OS(like TI-Boy), an actual Operating System, or something entirely different?