Once again showing what could be done on the Playbook.
And once again I'm wondering since they are owned by RIM, why don't they just do it?
Printable View
Once again showing what could be done on the Playbook.
And once again I'm wondering since they are owned by RIM, why don't they just do it?
Beta release.
Oh yeah. Forgot.
Everything Blackberry is beta until the competition leaves them in the dust.
Hardware, software, dev tools. Yeah. Forgot.
This kind of stuff is like concept cars at auto shows; you can see what's possible BUT it doesn't mean that it's going to make it to the "production line". Sure, it's really disappointing to see cool stuff at an auto show that never makes it to your local showroom floor, but that's life. With that being said, RIM had better get their s**t together... and FAST!
On the other hand, there are a lot of concept stuff that should never be productized --- like the Pontiac Aztek, the ugliest car on the planet.
Today's TAT email demo is another example of stuff that will never make into production units.
Isn't Cascade the name of the UI engine?
Posted from my CrackBerry at wapforums.crackberry.com
Yes, Cascades is TAT's UI framework.
TAT Cascades + QtCore = BBX native UI.
Except this is the software industry and not the auto industry. Production cost of building a concept would be expensive compared to a normal current year car as a production line item.
In IT it is usually the reverse. Building something requires a cost of labour hours. And it is usally more expensive for someone to build from scratch after a demo then to build and expand on a demo.
No dude no, TAT Cascades + Developers = Cool Native BBX apps
so why are people acting like its an App they arent releasing?
The keynote specifically talked about Cascades and QtCore.
Well first because to show up cascades you need to have apps developed with that, so just like last time TAT developed some apps to show up the advantages of the cascades UI framework integration with the SDK 2.0, and just like last time we probably arent going to see any of those apps in appworld with the exception of Scrapbook wich by the way was also done with cascades, people think that TAT was adquired by RIM to make apps thats why they are dissapointed.
samab makes it seem like the demo TAT was showing was the GUI of the new BBX OS and while it could be that RIM might implement some of that into the OS, they didnt show us any of that.
I never said that --- I have repeated and consistently said that TAT demo's are concept stuff that will NEVER be productized.
In other threads, I have said that the Playbook OS 2.0 developer beta that was released today --- has a new UI that is still based on Flash/Air. I said that things which are closer to metal will eat less battery.
RIM has a native C UI framework and a team of native C UI designers. RIM already known to have an obsession with battery life --- so it isn't that much of a stretch to migrate to a native C UI just to get better battery life.
I take back what i said then, and yeah i could definitely see that happening although i think that RIM is more concentrated in getting devs to write some apps for BBX than recoding the OS GUI wich is actually very good IMO, also adding flashy transitions and 3D effects to the main UI might actually decrease battery life and increase RAM consumption.
I never said anything about flashy 3D effects either.
BBX is going to be on both phones and tablets with vastly different resolutions. It makes sense that they are going to go with a native UI to make this transition. Especially the delays right now is on the server side for native email, not on the client side.
Yeah you didnt say that but flashy 3D effects and transitions is what cascades is all about.
This is something that is actually very close to implementation - it's already in the NDK in a beta form. Cascades is actually baked into the NDK for programmers to use to create their UI, it's not something that is a stand alone product like the scrapbook.
Also, TAT cannot just go and 'release' something without approval - if each individual group did that then everything would become a huge mess in a hurry. Even open source projects that depend on the free labour of their team have a hierarchy, and it's purpose is to control what gets implemented in the project. There are often fierce arguments over what gets implemented and how, but without that hierarchy the project would cease to function, and possibly exist quickly.
No, that's what those concept videos are all about.
The productized UI is Android's original UI (which was designed by TAT) and Playbook's subtle and understated 3D transition in the Photo app.
Cascades is not in the NDK yet.
So is there any news on Cascades. As I understand useful apps cannot be developed until the UI has been made available.
It was probably well-named "Cascades" and like the bears that live here, time to hibernate and hope that it will be released before next fall when the new phones have been delayed till. In other words, no word whatsoever on when/if/ever!
If you follow Alec Saunders on Twitter, he said private beta (to specific dev's) soon, and beta release sometime in January.
Interesting timing. Would be nice to think that means they'll announce something publicly soon. Maybe at some big trade show...