StoppedInTracks
Member
Jeff dude nothing personal but you are like 2011 version of 2001 Lazy 8s. Total lunatic.
Hmmmm..... So providing a link to a company that is supporting HTML/Web in game that uses webcore and mentions the PS3 among other platforms known to be using webkit/HTML5 is Lunacy?Jeff dude nothing personal but you are like 2011 version of 2001 Lazy 8s. Total lunatic.
We are working on an additional assembly for the next version of AwesomiumSharp (renamed to Awesomium.NET), namely: Awesomium.Mono.Gtk. This will contain utilities and a Gtk WebControl widget to be used with Mono projects using Gtk.
http://venturebeat.com/2011/12/08/google-nabs-square-enix-and-other-game-developers-to-do-native-chrome-games/ said:Google announced today that its three-year effort to create a muscular browser technology that can run heavy duty apps such as console-like games is now ready for prime time.
Google has provided the platform to allow games to run in the Chrome browser and make use of the computers 3D graphics hardware. That makes it possible to run games with high-end console-like graphics in a web browser.
A group of game developers, including Square Enix, Unity Technologies, and Bungie, appeared at Google Thursday night to promote the use of the in-browser Native Client technology, which could result in a rich, Chrome-based gaming platform.
Native Client (abbreviated as NaCl for short, or the atomic name for table salt) was first launched for Chrome in August. An open-source project, Native Client allows native code bases to be run inside Chrome, Google's proprietary browser. Since the original Chrome port, Google has ported a full-screen API, mouse lock, and even OpenGL ES 2.0 3D graphics to the browser.
Among the many possibilities this brings to Chrome is easier to render 2D and 3D graphics, meaning Chrome could become a rich gaming platform that works on computers of every kind. While Chrome will be able to store the code for the game inside the browser, users will still have to fork over money for the necessary hardware to run it.
Since the technology is open source, Google and the developer community have already ported the Unity and Moai game engines, programming language environments Mono and Lua, audio middleware such as fmod and Wwise, as well as the Bullet physics engine, Google said.
Square Enix’s Mini Ninjas, a popular 2009 action-adventure game, is coming to the Chrome Web Store, the publisher announced yesterday. It will be the first game to utilize the Native Client SDK beta that Google released at Google I/O in May of this year as an open-source technology for running native compiled code in the browser. Chief executive officer of Square Enix Holdings, Yoichi Wada, says Native Client “enables the same consumer experience in the browser as in a native application”.
The game will require Chrome 17 Beta which will be available in the coming weeks (support for native code execution first appeared in Chrome 14). Mini Ninjas will be entering an open beta in December. The blurb promises console-quality gaming in the browser
Any tie-in to this Dec 16 th release and the Vita Dec 17 release in Japan?http://blogs.igalia.com/carlosgc/2011/12/16/preliminary-webkit2-gtk-api-documentation/ said:Preliminary WebKit2 GTK+ API documentation
December 16th, 2011Carlos Garcia CamposLeave a commentGo to comments
We have just released WebKitGTK+ 1.7.3, the first release that includes WebKit2 API docs already generated in the tarball. The documentation is also available online now. Take into account that WebKit2 is still under development and the API might change, more specifically WebKitWebLoaderClient is going to be removed soon.
What's new in WebKitGTK+ 1.7.1?
This is the first release providing a minimal working WebKit2 GTK+
API. This API is still under design and development, so use it
carefully and take into account that it might change.
Warning Wild speculation.
Warning Wild speculation
When has always been wild speculation. Obviously you haven't been following the thread very closely or you would have seen that alot of early speculation in this thread has proved true. It's not just about the browser! Google is even using many of the same cross platform libraries that Sony is using. Is that by design (collaboration between Sony and Google) or because they are the best choices? In either case it implies that many of my "Walls of text" are correct. I believe androvsky has early on supported this and would agree; see post 1055 above.Wild speculation!!
The whole thread about the browser has just been that.
Are you truly insane?
When has always been wild speculation. Obviously you haven't been following the thread very closely or you would seen that alot of early speculation in this thread has proved true. It's not just about the browser! Google is even using many of the same cross platform libraries that Sony is using. Is that by design (collaboration between Sony and Google) or because they are the best choices? In either case it implies that many of my "Walls of text" are correct.
When has always been wild speculation. Obviously you haven't been following the thread very closely or you would seen that alot of early speculation in this thread has proved true. It's not just about the browser! Google is even using many of the same cross platform libraries that Sony is using. Is that by design (collaboration between Sony and Google) or because they are the best choices? In either case it implies that many of my "Walls of text" are correct.
I didn't name the thread and in my opinion it's about more than the browser as should be obvious by now. Gesh...... The same open source libraries needed to support webkit in the PS3 provide tools to support applications in the PS3. Those same libraries are being used by both PS Suite and Google NaCl games.I read the title of the thread ": PS3 Web Browser Discussion - big upgrade rumoured for long time, but no concrete news .. maybe I can´t read..
http://news.cnet.com/8301-30685_3-57332622-264/google-well-prove-native-clients-worth-on-the-web/ said:The biggest barrier to NaCl's success so far is the lack of support from other browser makers. Without that, NaCl runs the risk of introducing a technology to the Web that fragments it as a programming platform. After years of concerted effort, browser makers and Web developers are only now building HTML, CSS, and JavaScript into a heavy-duty foundation to rival proprietary alternatives such as Adobe Systems' Flash and Microsoft's Silverlight.
Those plug-ins require browsers to have an interface such as NPAPI (Netscape Plug-in Application Programming Interface). Native Client needs an interface, too, but NPAPI isn't up to the challenge, so Google created a new one instead called Pepper. (NaCl is the chemical abbreviation for sodium chloride, more commonly known as table salt. Get it? Salt and pepper.)
The Native Client open-source technology is designed to run native compiled code securely inside browsers. Native Client puts web applications on the same playing field as local applications, providing the raw speed needed to compete with traditional software like 3D games, video editing, and other applications. Native Client also gives languages like C and C++ (and eventually others as well) the same level of portability and safety that JavaScript provides on the web today.
Here are some of the key features that Native Client offers:
Graphics, audio, and much more: Run native code modules that render 2D and 3D graphics, play audio, respond to mouse and keyboard events, run on multiple threads, and access memory directly—all without requiring the user to install a plugin.
Portability: Write your apps once and you'll be able to run them on any major platform (Windows, Linux, Mac, and soon, Chrome OS).
Security: Installing a desktop app or a browser plugin can present serious security risks and deter potential users. Native Client uses a double sandbox designed to protect resources on the user's system. This framework offers the safety of traditional web apps in addition to the performance benefits of native compiled code, without requiring users to install a plugin.
Easy migration path to the web: Many developers and companies have years of work invested in existing desktop applications. Native Client makes the transition from desktop app to web app significantly easier because Native Client supports C and C++ (and will continue to add more languages).
Performance: Native Client allows your app to run at a speed comparable to a desktop app. This capability enables demanding applications such as console-quality games to run inside the browser.
But if you actually attempt to wade into the "content" of Jeff's loony posts, you'll see that it's not just about GTK#WebKitBrowser.web3point0. He also thinks the Gnome desktop (the most common UI for desktop Linux) is going to be ported to PS3.
It's all utterly ridiculous.
jeff_rigby said:I've done the research and have read and understood the email from Geoff Levand (person in charge of the GTKwebkit port to the PS3, or rather the person signing off and posting the required LGPL Disclosures on-line). It's coming but he cautions to not have high expectations, he wrote that after reading my posts on the Sony Blog where I stated we might get a Sony flavor multi-media version of the Gnome Shell.
I didn't name the thread and in my opinion it's about more than the browser as should be obvious by now. Gesh...... The same open source libraries needed to support webkit in the PS3 provide tools to support applications in the PS3. Those same libraries are being used by both PS Suite and Google NaCl games.
Wake UP!!!! LOLs are a poor substitute for honest comments on DISCOVERIES like in 1055!!! PS Suite comes on-line within weeks of Chrome NaCl games....why?
Cairo build for NaCl proof!
PS Suite? Mono.Net based VM + IDE + GUI editor + tools. What about Google's Native Client plugin?
Multiple people have your opinion that it's late to be doing this.... Everything done for the PS3, since they are primarily using cross platform libraries will be use-able on a PS4.I'd love for the PS3 to get some insane software upgrade like all of this from the browser to apps, but I just don't see it happening now, so late in the game. Maybe this stuff is pointing towards PS4 and theyre devving around with it on PS3 until that hardwares locked down, but I just dont think you can honestly see all this coming to PS3 anymore.
Especially when the Vita has a more advanced system, just released, and the PS3 has seen none of that incorporated into itself.
I don't understand your question. Look at http://www.neogaf.com/forum/showpost.php?p=33320752&postcount=1055 and go to http://code.google.com/p/naclports/...scripts/cairo-1.8.8/nacl-cairo-1.8.8.sh?r=141 Look at the blue box on the right side and look at Review URL and below it at the Go to Forms Window for scripts to compile Open Source applications and tools to be used in NaCl.
Also note-able is that PS Suite and Chrome are webkit2 versions of Webkit.
In fact the model is so similar the fact that Chrome NaCl is only supporting desktop and PS Suite is only supporting hand-helds is suspicious....a timed agreement between Sony and Google?
PS Suite is more about a games and high quality interactive GUI apps targeted VM which can run on all Sony's platforms. Think of it as a super PSP Minis program of some sort .
PS suite uses a Mono VM and NaCl can use a Mono VM.
PS Suite obtains it's resources from the Dalvik VM through the Android Browser which is sitting on top of the Webkit which is sitting on top of the webkit core.
The above is my understanding of PS Suite and Chrome NaCl from the reading I have done in the last 30 days. It appears my understanding is subtly different from yours or we have a communication problem (probably on my side). In any case thanks, it forced me to have a possibly <grin> clearer understanding of both Chrome NaCl and PS Suite.
PS Suite obtains it's resources from the Dalvik VM through the Android Browser which is sitting on top of the Webkit which is sitting on top of the webkit core.
PS suite must use a Mono VM and NaCl can use a Mono VM.
Not webkit but the browser which is separate from the webkit and webcore I think it's very interesting to see that they use the MONO sandboxAlso, why should it go through Webkit to get access to Dalvik when it has a much shorter path (JNI)?
PS Suite may come to the PS3...it's up in the air with several Sony comments confirming then backing off.StoppedInTracks said:I appreciate Panajev's input but none of that will be done on/ for the PS3. PS4 is another story
Why would PS Suite come to PS3? Granted I haven't followed it much, but I was pretty certain it was a development framework for Android infrastructure and the PS Vita. Given that the goal of PS Suite is to allow certain PS titles to run on the Android platform (which consists of only PS1 titles at the moment) it makes no sense for Suite to come to PS3, since it already emulates PS1 titles flawlessly.
Also, pretty sure it's coming to Vita solely as an Emulation tool for PS1 titles, and not for anything else. Seems like a whole lot of speculation with a very small amount of tangible information.
Yes that's true and PS Suite on the PS3 for only applications was mentioned.Why would PS Suite come to PS3? Granted I haven't followed it much, but I was pretty certain it was a development framework for Android infrastructure and the PS Vita. Given that the goal of PS Suite is to allow certain PS titles to run on the Android platform (which consists of only PS1 titles at the moment) it makes no sense for Suite to come to PS3, since it already emulates PS1 titles flawlessly.
Also, pretty sure it's coming to Vita solely as an Emulation tool for PS1 titles, and not for anything else. Seems like a whole lot of speculation with a very small amount of tangible information.
I do remember reading PS Suite is running in the Android browser sandbox.
Vita is not running on an Android OS. Sony quote; "Any applications written for the Vita with the Android hardware limitations in mind (no game controls) can be PS Suite applications" and also ported to the PS3 version of PS Suite.
Not webkit but the browser which is separate from the webkit and webcore I think it's very interesting to see that they use the MONO sandbox
Yes but Native code which supports webkit and webkit routines including the javascript engine (also native language) can be accessed through the Android browser APIs in a cross platform standard. This is just a guess and has no cites other than it's obvious. I'll still search for the browser sandbox reference for PS Suite.There is still no urging need to go through webkit and webcore to access Dalvik's resources and talk to the Java side of things from native code because you already have the default and officially sanctioned way of doing so which is JNI.
The goal of PS Suite is much above and beyond the scope you have in mind .
PS Suite presentation at GDC:
http://www.youtube.com/watch?v=clk3uu6o5KY
http://www.youtube.com/watch?v=hUQk-tuPFmY
http://www.youtube.com/watch?v=9L_oXvIhOWM (I think this is the video in which they show the IDE and most importantly a good attempt at an Interface Builder clone)
Do you like this kind of tangible information ?
P.S.: PS Suite could have been even more awesome it it were built on Sony's own SNAP platform (now abandoned Objective-C + GNUStep powered framework) , but C# is good too .
Panajev2001a said:The goal of PS Suite is much above and beyond the scope you have in mind .
PS Suite presentation at GDC:
http://www.youtube.com/watch?v=clk3uu6o5KY
http://www.youtube.com/watch?v=hUQk-tuPFmY
http://www.youtube.com/watch?v=9L_oXvIhOWM (I think this is the video in which they show the IDE and most importantly a good attempt at an Interface Builder clone)
Do you like this kind of tangible information ?
P.S.: PS Suite could have been even more awesome it it were built on Sony's own SNAP platform (now abandoned Objective-C + GNUStep powered framework) , but C# is good too .
It's interesting that Panajev2001a has mentioned the Sony SNAP program and provided links to the PS Suite GDC lectures just as I have done in this thread. I too consider this important to understanding where Sony is going. Are posters going to call Panajev2001a crazy too? <sigh>Looks awesome. Thank You.
There is another one I'm still looking for that mentions the Android sandbox....put the two together. I'll still try to find that reference.jeff_rigby said:Edit: From Sony-Erikson video, Android's webkit had to be modified to work with PS Suite as it breaks from Webkit standards. This is another job Sony has to do for PS Suite. I believe I read where Google is rewriting Android's webkit to be more compliant.
It's interesting that Panajev2001a has mentioned the Sony SNAP program and provided links to the PS Suite GDC lectures just as I have done in this thread. I too consider this important to understanding where Sony is going. Are posters going to call Panajev2001a crazy too? <sigh>
Yes but Native code which supports webkit and webkit routines including the javascript engine (also native language) can be accessed through the Android browser APIs in a cross platform standard.
Edit: From Sony-Erikson video, Android's webkit had to be modified to work with PS Suite as it breaks from Webkit standards. This is another job Sony has to do for PS Suite. I believe I read where Google is rewriting Android's webkit to be more compliant.
Untrue. His info is 100% inaccurate.I've been enjoying this thread since its beginning and I don't think you are crazy. As someone posted before its not that your info is inaccurate, but that you catch things too early and with the possibility of being cancelled, adjourned or not being used at all in the end.
PS Suite does not allow you to directly access native code or the Android stack, everything is through Mono. We are confusing how Mono interacts with Android and gets access to system features with how we as developers will get access. Its understandable as I started with a statement that Chrome NaCl and PS suite are similar.So? We are at the "it is possible to do it this way, so they must have done it this way".
The problem is that while it indeed is technically possible to do it jumping through hoops, they have a better path on Android if they use what it is meant to be used in cases like this one. JNI (and the NDK).
Maybe one days we will only use JavaScript or a higher level version of it plus CSS for application code and layout, but while Sony wants to provide a cross platform solution... Sony wants it to be PlayStation Suite.
Whether you use other layers to give PS Suite the resources and I/O paths it needs, it makes little difference (in theory). Still, the NDK+JNI path looks like the most straightforward approach of the two we are looking at here... at least it does look that way to me.
html5test.com http://html5test.com/ の実行結果
スコア:66 + 0 Bonus(PC版Chrome16:344 + 13 Bonus)
Parsing rules 1/11
triggers standards mode Yes
HTML5 tokenizer No
HTML5 tree building No
SVG in text/html No
MathML in text/html No
Canvas 20
canvas element Yes
2D context Yes
Text Yes
Video 0/31
video element No
Subtitle support No
Poster image support No
MPEG-4 support No
H.264 support No
Ogg Theora support No
WebM support No
Audio 0/31
audio element No
PCM audio support No
MP3 support No
AAC support No
Ogg Vorbis support No
WebM support No
Elements 6/28
Embedding custom non-visible data No
New or modified elements
Section elements No
Grouping content elements No
Text-level semantic elements Partial ○
Interactive elements Partial ○
Global attributes or methods
hidden attribute No
Dynamic markup insertion Yes
Forms 11/98
Field types
input type=search Yes
input type=tel Yes
input type=url Partial ○
input type=email Partial ○
input type=datetime No
input type=date No
input type=month No
input type=week No
input type=time No
input type=datetime-local No
input type=number Partial ○
input type=range Partial ○
input type=color No
input type=checkbox Yes
input type=image Partial ○
textarea Partial ○
select Partial ○
fieldset Partial ○
datalist No
keygen Partial ○
output No
progress No
meter No
Fields
Field validation No
Association of controls and forms No
Other attributes Partial ○
CSS selectors No
Events Partial ○
Forms
Form validation No
User interaction 17/36
Drag and drop
Attributes No
Events No
HTML editing
Editing elements Yes
Editing documents Yes
APIs Yes
History and navigation 0/5
Session history No
Microdata 0/5
Microdata No
Web applications 0/20
Application Cache No
Custom scheme handlers No
Custom content handlers No
Custom search providers No
Security 0/10
Sandboxed iframe No
Seamless iframe No
Related specifications
Geolocation 0/15
Geolocation No
WebGL
3D context No
Native binary data No
Communication 5/25
Cross-document messaging Yes
Server-Sent Events No
WebSocket No
Files 0/20
FileReader API No
FileSystem API No
Storage 0/20
Session Storage No
Local Storage No
IndexedDB No
Web SQL Database No
Workers 0/15
Web Workers No
Shared Workers No
Local multimedia 0/20
Access the webcam No
Notifications 0/10
Web Notifications No
Other 6
Text selection Yes
Scroll into view Yes
PS Vita browser test: http://www.roshi.tv/2011/12/psvitano.html
Not great , it barely supports html5.
Thats a lost opportunity for Sony. I don't think it would be very difficult to support at least a video or audio tag. And of course, no webgl support.
Which would indicate the Vita is using the same OS (kernel) as the PS3; FreeBSD with routines from NetBSD. Just as the choice to use a BSD licence version of Pearl regular expressions which is a required part of a Script engine (needed to process text expressions, find etc.) like that used for Python in OLPC which I believe is the Game OS mentioned by Sony that influenced the Vita OS. LGPL would require Sony publish a Diff file so that others could upgrade to newer versions themselves. BSD only requires an acknowledgement. Using the Netfront Access NX browser front end helps keep Sony from being required to publishing the webkit API and Browser Diff. This would apply to the PS3 also....we may get a Netfront NX browser front end for the PS3.Access NetFront
asiasoft AsiaFont
FONTFWORKS(日本語フォント/欧文フォントの一部)
MPEGLA(MPEG-4)
iWnn
楽ひら(手書き文字認識エンジン)Handwriting recognition
QUALCOMM
RSA
Skyhook Wireless
Sony Music Publishing
Fraunhofer IIS and Thomson(MP3)
blist
CyrusSASL
FLANN
FreeBSD
FreeType
giflib
libEtPan! Open Source mail library supports Gmail
libjpeg
libtiff
MD5
NetBSD
OpenCV (Open Source Computer Vision) is a library of programming functions for real time computer vision.
squish
strlcpy
Open source list for the Vita might be misleading. There is no Mono or GTK+ UI toolkit, both should be part of PS Suite. Cairo is listed for only the browser port but is needed for Mono/PS Suite and GTK toolkit. Cairo is not listed for the Vita OS but Pixman is listed outside of Cairo, Cairo and Pixman are normally together to reduce the size of the combined libary; Cairo = (Cairo SVG + Pixman + GlitZ). In this case the Vita OS may not use Cairo, instead uses Pixman which would mean the Vita OS UI does not use the GTK toolkit (PS SUite has it's own UI Toolkit which might be a heavily modified GTK+ which Sony may not have to disclose).Open source software used in PS Vita
1. blist Web based database
2. bzip2 Open source data compressor
3. Cyrus SASL Simple Authentication and Security Layer
4. FreeBSD Unix OS
5. FreeType2 Fonts
6. giflib GIF picture library utilities
7. libEtPan! Mail library
8. libjpeg Jpeg picture utilities
9. libpng PNG picture utilities
10. libtiff Tiff picture utilities
11. MD5 Checksum
12. NetBSD Unix OS
13. squish Open Source DXT compression
14. strlcpy String copy with protection for buffer overflow (increases security)
15. zlib Compression library
Internet Browser
1. cairo SVG drawing library and more used by webkit for rendering text and graphics
2. dtoa Math rounding libary
3. expat Expat is a stream-oriented XML 1.0 parser library, written in C
4. FreeType2
5. hash.c routines to manipulate a hash table = data structure that uses a hash function to map identifying values, known as keys
6. ICU Unicode and Globalization support for software applications
7. libjpeg
8. libpixman library of Pixel manipulation routines now part of Cairo?????
9. libxml2
10. list.c
11. PCRE Perl Compatible Regular Expressions (or something like it is part of script engines; PHP, Mono, Python and more)
12. trio Trio - portable and extendable printf and string functions
13. Webkit
Welcome Park
1. Boost C++ libraries
2. FLANN "Fast Approximate Nearest Neighbors with Automatic Algorithm in C++ Configuration
3. OpenCV (Open Source Computer Vision) is a library of programming functions for real time computer vision.
Specifications | NetFront Browser NX
[Markup]
HTML 5, HTML 4.01, XHTML 1.1, XHTML Basic 1.1, XML 1.1, RSS feed (RSS 0.9/0.91/0.92/1.0/2.0, Atom 1.0)
[Style Sheets]
CSS1, CSS2.1, CSS3
[Advanced Scripting]
ECMAScript 262 3rd Edition
DOM Level 1, Level 2, Level 3
Ajax (XMLHttpRequest)
[Protocols]
HTTP 1.0/1.1
IPv4/IPv6
[Security]
SSL3
TLS1.0
[Memory Requirements]
ROM: 12MB (Browser engine only)
RAM: Less than 25MB (Depending on web content)
[Main Features]
Tabbed Multi-Window support
Smart Frame (Frame Flattening)
Continuously adjustable Zooming/Animated Zoom
Page/Image Saving
Word Wrap, Line boundary character check
International Domain Name
[Supported Operating Systems]
Linux® (Android™, Qt/Embedded, Qtopia, GTK+, and others)
UNIX
Microsoft® Windows® CE family, Microsoft® Windows Mobile® (Pocket PC, Smartphone)
Others
[Supported CPU]
ARM®
XScale
StrongARM®
Others
[Plug-In and Extension Modules]
Adobe Flash Player 10 (In planning)
Vita Browser Documentation
Multiple Browser windows can be open, Up to 8 tabs at a time in a browser window.
Multi-window, multi-tab would suggest webkit2...not absolutely necessary but more stable and one tab crashing won't affect the whole browser. We will have to wait for reviews on this, if they mention a tab crash does not lock the browser then it's most likely a webkit2.
GTKwebkit 1.73 just released and GTK API for webkit 2 was a major feature (partially implemented). Sony may have been waiting for webkit 2 to port the already disclosed GTKwebkit to the PS3.
But
and the webkit2 to GTK API interface is not finished yet.
Geolocation, SVG and WebGL not implemented yet.... Admittedly, Sony is going to not support some features to lock us into them but SVG icons and text is not a threat and appear to be needed by the new PS store and menu navigation. By Feb 2012 more of the Webkit2 API will be done and Vitas sold in the US should have a more robust webkit browser. Expect many updates for Vita.
Your find is more support for webkit2 if I'm correct.
The user agent string is chosen to give a web site an idea of the features supported, it does not necessarily indicate the webkit build. If I am correct and more is coming (with webkit2 GTK API updates to the GTKwebkit builds)....the user agent string will be changed when the Vita browser supports more features.Now I'm pretty sure Sony is not going to use cutting edge software for security reasons.
Microsoft stated that WebGL contained security holes.
[User-Agent] => Mozilla/5.0 (PlayStation Vita 1.00) AppleWebKit/531.22.8 (KHTML, like Gecko) Silk/3.2
It uses 531. The same used safari 4 or chrome 2 in september 2009...
Geolocation is a HTML5 feature that reports the Latitude and Longitude with the users permission from a GPS embedded in the handheld. It is not supported on the PS3 (location can be roughly discovered from IP address tables) so why is the library listed in the PS3 GTKwebkit disclosure?$(CAIRO_LIBS) \ Cairo SVG library
+ $(COVERAGE_LDFLAGS) \
+ $(ENCHANT_LIBS) \...............Front end API for a spell checker and more
+ $(FREETYPE_LIBS) \...............Font Library
+ $(GAIL_LIBS) \......................GNOME Accessibility Implementation Library
+ $(GEOCLUE_LIBS) \...............No need for this on the PS3, NGP will use!
+ $(GLIB_LIBS) \......................low level C cross platform lib (needed for just about everything webkit & cairo & Gstreamer)
+ $(GSTREAMER_LIBS) \...........Gstreamer AV library *
+ $(GTK_LIBS) \.......................GTK toolkit library
+ $(HILDON_LIBS) \..................See below*
+ $(JPEG_LIBS) \......................Jpeg compression picture library (Video too?)
+ $(LIBSOUP_LIBS) \................HTTP library
+ $(LIBXML_LIBS) \
+ $(LIBXSLT_LIBS) \
+ $(PANGO_LIBS) \...................International Fonts Cairo-pango = SVG international fonts
+ $(PNG_LIBS) \.......................PNG picture library
+ $(SQLITE3_LIBS) \.................Data Base Library
+ $(UNICODE_LIBS) \
+ $(XT_LIBS) \.........................
+ $(WINMM_LIBS) \..................
+ $(SHLWAPI_LIBS) \ wrapper functions convert the Unicode input string parameters to ANSI and call ANSI versions of functions
+ $(OLE32_LIBS)
... and how do you think Mono accesses Android resources and device resources which are NDK bound at this point? Dalvik (native code compiled with the NDK has Dalvik as Gatekeeper anyways).PS Suite does not allow you to directly access native code or the Android stack, everything is through Mono.
We are confusing how Mono interacts with Android and gets access to system features with how we as developers will get access.
It is entirely possible that they did this, the Android "jail" would not help for PS Suite applications on other OS's.Mono is the PS Suite sandbox, that's now clear to me.
PS Vita browser test: http://www.roshi.tv/2011/12/psvitano.html
Not great , it barely supports html5.
Thats a lost opportunity for Sony. I don't think it would be very difficult to support at least a video or audio tag. And of course, no webgl support.