Topic: Microsoft and VCSY
These will be various old posts made in various locations. You can probably find the original locations by searching unique phrases.
MICROSOFT JUPITER and APOLLO?
arthur "Go behind the scenes and learn all about the new app model that allows you to create powerful new apps. All while retaining the ability to use your existing apps. "
That would be Jupiter which would be using XAML to encapsulate and abstract HTML5/Javascript and the .Net capabilities together. I suspect Jupiter is going to be 744.
If that's the case it means for all Ballmer's BS and bluster the Microsoft engineers won the faction wars and Ballmer is going to go out on the cusp of Microsoft's rising ability to interoperate between smartphone and PC/laptop/tablet. He will look like a hero instead of a sloppy drunk.
I draw that inference from this:
https://channel9.msdn.com/Forums/Coffeehouse/Jupiter/e7960a6237024c1598639efc00d8e394
Jun 08, 2011 at 6:09 AM
@Ian2:
As far as I can see, Jupiter is not Silverlight nor WPF, its another kind of framework that kinda similiar or compatible to Silverlight/WPF code.
so Sinofsky is right, that 'Silverlight', as we know it, is still a Browser/Desktop thing.
what he didn't say is, the 'Jupiter' framework will enable you to leverage your Silverlight/.NET skills to write Immersive (or desktop) applications in XAML/C#/VB/C++, its very very similiar, but not exatcly the same thing.
(-- Now THAT looks very much like arbitrary use of different language components to me. )
the situation is similiar to the relationship of Silverlight and WPF and Silverlight for Phone, you need to create different project in VS, then you can write very similiar UI/code...
(-- UI/code meaning the User Interface and processing code can be written)
...even sharing most of your portable code in a common library
(-- Bingo. Read 744. A "common library" containing different-objects/different-technologies is an arbitrary object library.)
, but the underlying technology are still very different.
(-- Cryptic statement. what "underlying technology"? "ARE" meaning multiple not "IS" meaning singular. Microsoft in their claim construction argued "arbitrary" to be defined as AN arbitrary object. Vertical argued "arbitrary" to mean ANY arbitrary object. If Microsoft handles more than one technology they are using Vertical's claim construction. So I take this to mean the common library holds arbitrary objects each built using different techologies. THAT is 744.)
that said, I think you can easily port a 'real WPF' app to the immersive ui, just host your WPF content inside an immersive HWND,
(-- see hWnd definition below. So you can port a 'real WPF' app to the UI by containing your WPF content in a container object.)
maybe you can play some trick with 'real' silverlight too, with COM interop or P/Invoke.
(-- Holy $hit. There it is. COM meaning Component Object Model http://en.wikipedia.org/wiki/Component_Object_Model which is Microsoft's overarching OS connectivity and interoperation capability. P/Invokr meaning Platform Invocation Services (PInvoke) allows managed code to call unmanaged functions that are implemented in a DLL. http://msdn.microsoft.com/en-us/library/aa288468%28v=vs.71%29.aspx - in other words the "hook" into the operating system code. So what that one phrase means is to be able to use the Silverlight structure to embedded operating system objects and their various coded capabilities for platform interoperation. COM is the old world. P/Invoke is the new world. They are able in these objects to knit both worlds together and I would think "arbitrarily". That's 744.)
Hmm.. maybe Microsoft can have these little tricks offically builtin but that wont make much sense, because in the end of day, you still need to call some new apis to provide a real native experience, so what you get is just a hybrid monster, why not just use Jupiter ?
(-- Blink Blink. OK I'm sold.)
and, the Silverlight is portable, and the immsersive experience is very unique and not portable, you cant use them in the browser or on a Mac, it doesnt make sense to add those into a portable technology. the only exception may be the phone. but Apollo is the son of Jupiter IIRC.
(-- and the Jupiter construction system has a child which is Apollo which I would suspect would look like what VCSY built as a small footprint distributed interoperation system for the Apollo smartcard. It would be in keeping with Wade to force the use of a codename to signal to outside world that VCSY is at work.)
(-- You folks who think I "technobabble" have an easy solution: take this post to somebody you know familiar with Microsoft platforms and have them come up with a rebuttal. None of this "bogus" crap. I want a point by point dissection detailing why and where I am "wrong" or stfu. I get the feeling [although I'm not getting my hopes up that Microsoft will play fair] that there is a real reason for the BUILD secrecy and we already know the secret.)
======================================================
--HWND:
http://msdn.microsoft.com/en-us/library/aa979055%28v=vs.71%29.aspx
hWnd Property
Visual Studio .NET 2003
Returns a handle to Forms and user-defined Toolbar objects.
Object.hWnd
The Microsoft Windows operating environment identifies each form in an application by assigning it a handle, or hWnd. The hWnd property is used with Windows API calls. Many Windows operating environment functions require the hWnd of the active window as an argument.
Because the value of this property can change while a program is running, you cannot rely on its value (e.g., when stored in a variable).
hWnd is available in user-defined Forms and Toolbar objects and is read-only at both run and design-time. --
--FORM Object
http://msdn.microsoft.com/en-us/library/aa975432%28v=vs.71%29.aspx
The definition describes what many would refer to as an object container where events may be trigger and sensed with designed responses to the events.--
--Forms
http://msdn.microsoft.com/en-us/library/aa975571%28v=vs.71%29.aspx
You can use forms to give your users a familiar interface for viewing and entering data into a database, but forms provide far more than just an interface. Forms provide a rich set of objects that can respond to user (or system) events, so you can make it possible for your users to accomplish their information management tasks as easily and as intuitively as possible.
I can continue if you like. If you have any questions please ask and I'll dig through the structure as best I can and show the encapsulation process into objects. But so far I think we're seeing an encapsulation process using objects to contain arbitrary coded objects of different technology basis. That's 744 and Apollo being a child of Jupiter is 629.
