LiquidMetal14
hide your water-based mammals
Sounds interesting. When will we see the fruits lol
Beam said:Since Sony and Google are close now. Is there any possibility, that Sony can use Crome as a browser?
SolidusDave said:but not only pointer support but the whole Minority Report tech demo thing:
3D accelerated effects are no longer the monopoly of desktop beta browsers (Firefox 4, Google Chrome 9 I am looking at you). Sony demoes Javascript WebGL on its Xperia handset. WebGL would be major turning point for mobile gaming, as it would lower the barrier of enty for building cross-platform mobile games.
, which platforms that can play games like the above has. As do all Playstation certified Android platforms. The NGP and PS3 have PSGL and custom support for WebGL would be needed."So, Chrome has WebGL on by default ... if you have hardware OpenGL 2.0 support"
3rd March, 2011 Game Developers Conference, San Francisco The Khronos Group today released the final WebGL 1.0 specification to enable hardware-accelerated 3D graphics in HTML5 Web browsers without the need for plug-ins. WebGL defines a JavaScript binding to OpenGL® ES 2.0 to allow rich 3D graphics within a browser on any platform supporting the industry-standard OpenGL or OpenGL ES graphics APIs. WebGL has the support of major silicon and browser vendors including Apple, Google, Mozilla and Opera with multiple browsers already shipping with WebGL implementations including the beta releases for Mozilla Firefox 4.0, all channels of Google Chrome 9.0, an Opera preview build, and Apple Mac OS Safari nightly builds.
WebGL leverages the pervasive availability of OpenGL ES 2.0 graphics on almost all browser-capable desktop, mobile and embedded platforms and the recent developments in Web technology including the massive increases in JavaScript performance. The ability for Web developers to directly access OpenGL-class graphics directly from JavaScript, and freely mix 3D with other HTML content, will enable a new wave of innovation in Web gaming, educational and training applications and graphically rich user interfaces to make the Web more enjoyable, productive and intuitive.
There is already a thriving middleware ecosystem around WebGL to provide a wide diversity of Web developers the ability to easily create compelling 3D content for WebGL-enabled browsers. These tools include: C3DL, CopperLicht , EnergizeGL, GammaJS, GLGE, GTW, O3D, OSG.JS, SceneJS, SpiderGL, TDL, Three.js and X3DOM. Links to these authoring tools and WebGL demos can be found at www.khronos.org/webgl/wiki/Main_Page.
"WebGL enables an entire new class of applications on the web. Being able to take advantage of first-class 3D hardware acceleration in a browser on both desktop and mobile allows web developers to create compelling and immersive experiences for their users," said Vlad Vukićević of Mozilla and chair of the WebGL Working Group.
DrXym said:A couple of random thoughts:
a) Webkit doesn't need QT and it would be mad to port QT to the PS3 just for some browser. There are impls of WebKit that go through QT, GTK, Cocoa etc. I imagine the best approach for the PS3 would be to make some thin widgets staight over OpenGL ES
b) It's not the disk foot print size that matters, but the runtime footprint. i.e. how much it consumes when running standalone or in a game. I expect Webkit has reasonable performances thanks to it's use in Android / iOS.
The GTK port of the WebKit HTML rendering engine has gained support for the HTML5 video element. The media backend, which uses GStreamer, was implemented by Pierre-Luc Beaudoin of Collabora. Developer Alp Toker integrated the backend with GTk/WebKit's Cairo graphics pipeline, making it possible for the video content to be embedded in SVG and manipulated with CSS and JavaScript.
Plans for GStreamer-based HTML5 video support in GTK/WebKit were initially revealed by Toker in September, when he published slides from his presentation at LinuxConf Europe.
As some of you may recall, support for the HTML5 video element was implemented experimentally for Firefox back in August.
The GTK/WebKit port appears to be maturing rapidly and offers some unique advantages over Firefox's Gecko rendering engine in certain contexts. GTK/WebKit is lightweight and less resource intensive than Gecko, which makes it a particularly good choice for mobile and embedded environments. GTK/WebKit will also eventually be a very good solution for GTK and GNOME applications that want lightweight embedded HTML rendering
Clutter allows implicit animations of every item on the canvas using special objects called behaviours: each behaviour can be applied to multiple actors, and multiple behaviours can be composed on the same actor. Behaviours handle animations implicitly: the developer specifies the initial and final states, the time (or number of frames) needed to complete the animation, the function of time to be used (linear, sine wave, exponential, etc.), and the behaviour will take care of the tweening. Clutter provides a generic base class for developers to implement custom behaviours, and various simple classes handling simple properties, like opacity, position on the Z axis (depth), position along a path, rotation, etc.
Sonys Networked Application Platform is a project designed to leverage the open source community to build and evolve the next generation application framework for consumer electronic devices.
The developer program gives access to a developer community and resources like SDK, tools, documentation and other developers.
The foundation upon which this project is base comes from the GNUstep community, whose origin dates back to the OpenStep standard developed by NeXT Computer Inc (now Apple Computer Inc.). While Apple has continued to update their specification in the form of Cocoa and Mac OS X, the GNUstep branch of the tree has diverged considerably.
The GNUstep core libraries strictly adhere to the OpenStep standard and OPENSTEP implementation. They consider changes and additions to their API only under the following circumstances:
SNAP has a re-architected display model and backend based on Cairo evolving toward COLLADA over time. Our look and feel also includes navigation metaphors derived from standard Sony UX constructs such as our XrossMediaBar.
People are already making Cairo/SVG driven desktops.
On the X Windowing System and why Google isn't using it for Chrome OS
14 July 2009
Now, why then does Google not use an X windowing system in Chrome OS? The technical explanation for this is they simply dont need it for what theyre doing.
Another acquisition Google made in 2005 was a company called Skia Inc. that marketed a 2D graphics library also called Skia. The Skia library, written in C, does vector graphics, text, and images. It was open-sourced in 2008. Same features as Cairo
In writing Android, Google used Skia as the graphics backend for its windowing system and GUI toolkit. They also wrote a Skia backend for WebKit, which is used in the Android web browser. This same Skia Webkit backend is also used by Chrome on all of the platforms it supports. This is what I think Sony will do with Cairo
What Google has done in Android, and will do in Chrome OS, is write a simplistic windowing system using Skia, and let that output directly to the device framebuffer, while Im no expert on Skia, I assume it also has a backend implementing its painting operations via OpenGL, which would then make it easily hardware-acceleratable on a variety of different hardware offerings.
So to sum it up:
Google already has Skia-on-kernel-without-X working in Android, and they already have Chrome/WebKit using Skia. Chrome OS is unlikely to have the sort of drag-windows-around-on-a-desktop user experience that OS X or KDE offer (I expect it will be something more iPhone/Android-like), so while they could certainly use X, the small subset of its functionality they actually require is easily written anew using Skia, and doing so means they dont have to import a significant outside codebase and get involved with its development.
COLLADA is a COLLAborative Design Activity for establishing an interchange file format for interactive 3D applications. COLLADA is managed by the not-for-profit technology consortium, the Khronos Group.
COLLADA defines an open standard XML schema for exchanging digital assets among various graphics software applications that might otherwise store their assets in incompatible file formats. COLLADA documents that describe digital assets are XML files, usually identified with a .dae (digital asset exchange) filename extension.
Originally created at Sony Computer Entertainment
magicaltrevor said:Bundled with Cross-game Voice Chat?
Job Summary: The Sony Network Entertainment Senior Software Engineer-WebKit will join a dynamic team of experienced engineers developing WebKit and related open source software for the Playstation3, Sony Android devices, and other Sony consumer electronics products.
phosphor112 said:I'll be so happy if we get a new browser. The current one is garbage. And why only watch youtube at such low resolutions on it? Hope they get that fixed.
Gravijah said:ps3youtube!
Naturally the full source of his changes are in that .diff file also. From what I can tell, the posix platform only refers to the PS3 in webkit, it doesn't show up at all in the mainline source code (unix versions are typically under their widget library, like Qt or gtk). There's a lot of functions that aren't implemented, but they're mainly ones that involve windowing that you wouldn't expect to be supported on the PS3.Source/WebKit/posix/WebCoreSupport/ChromeClientPOSIX.cpp | 664 +++++
Source/WebKit/posix/WebCoreSupport/ChromeClientPOSIX.h | 177 +
I think secondapps.com/neogaf works, but I'm not sure.Jtrizzy said:What was the trick to using the current browser on gaf? I'd like some improved web browsing, mostly for watching game videos etc.
Yeah, http://www.secondapps.com/neogaf/ to browse neogaf on the PS3, and http://ps3youtube.com/ to view youtube videos at decent resolutions.Lesiroth said:I think secondapps.com/neogaf works, but I'm not sure.
androvsky said:I'm going through ps3-webkit-support.diff because I'm bored. Edit: Incorrect assumption Looks like we're actually getting Chrome, since Geoff's added a couple of files for ChromeClientPOSIX. See below
Naturally the full source of his changes are in that .diff file also. From what I can tell, the posix platform only refers to the PS3 in webkit, it doesn't show up at all in the mainline source code (unix versions are typically under their widget library, like Qt or gtk). There's a lot of functions that aren't implemented, but they're mainly ones that involve windowing that you wouldn't expect to be supported on the PS3.
This might not mean much since I don't see the cool stuff from Chrome in these sources, like bookmark syncing, but it's a huge freaking project., and the diff only covers what needed to be changed so it works on the PS3. It might not even get Chrome branding visible to the user, but I think if he's calling it ChromeClient, we can expect good things for the future.
All the AC_SUBST in the diff file above are changing the git (Internet link-able source code libraries) to Sony internal librariesSubject: Add PS3 target to Webkit build configure
Signed-off-by: Geoff Levand <geoff.levand@am.sony.com>
---
configure.ac | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
--- a/configure.ac
+++ b/configure.ac
@@ -170,13 +170,13 @@ AC_SUBST([PNG_LIBS])
# determine the GDK/GTK+ target.................................This is the key to understanding what's coming *GTK+ webkit* http://www.webkitgtk.org/
AC_MSG_CHECKING([the target windowing system])
AC_ARG_WITH(target,
- AC_HELP_STRING([--with-target=@<x11/win32/quartz/directfb@:>@],
+ AC_HELP_STRING([--with-target=@<x11/win32/quartz/directfb/ps3@:>@],
[Select webkit target [default=x11]]),
[],[with_target="x11"])
case "$with_target" in
- x11|win32|quartz|directfb) ;;
- *) AC_MSG_ERROR([Invalid target: must be x11, quartz, win32, or directfb.]) ;;
+ x11|win32|quartz|directfb|ps3) ;;
+ *) AC_MSG_ERROR([Invalid target: must be x11, quartz, win32, directfb, or ps3.]) ;;
esac
AC_MSG_RESULT([$with_target])
@@ -196,6 +196,8 @@ if test "$with_hildon" = "yes"; then
AC_SUBST([HILDON_LIBS])
fi
+if test "$with_target" != "ps3";
+
# minimum base dependencies
LIBSOUP_REQUIRED_VERSION=2.28.2
CAIRO_REQUIRED_VERSION=1.6
@@ -281,6 +283,8 @@ AC_SUBST(GTK_LIBS)
AC_SUBST(CAIRO_CFLAGS)
AC_SUBST(CAIRO_LIBS)
AC_SUBST([LIBSOUP_CFLAGS])
@@ -772,6 +778,8 @@ if test "$enable_video" = "yes"; then
AC_SUBST([GSTREAMER_LIBS])
androvsky said:A minor update. I checked the page where Sony keeps their webkit source, and noticed there's an update; a new snapshot of the webkit port as of early February, uploaded March 31. Now, the nice thing about this is there's a file that shows only the changes being made to the project to make it run on the PS3. The update from the fall only showed updates to the javascript core.
http://downloads.snei-opensource.com/pub/webkit/
This update has a ton of changes, including additions to the webkit interface core, like virtual keyboard support, mouse support, various strings ("Save as...", "missing plugin", etc) to be localized, etc. We're definitely getting a webkit browser, and it's probably mostly ready.
fake edit: They added a test directory two days ago. One of the pages tests the "video" tag (even though the page is supposedly html 4 "transitional", whatever that means).
http://downloads.snei-opensource.com/pub/webkit-tests/
Note that the Silverlight test page is apparently to make sure it handles the lack of a plugin correctly. The flash page is amusing though (it embeds a 640 x 380 youtube clip). If they're testing it on sample pages, I'm going to make a wild guess that a wide release is still a couple months out. At least it's in a form suitable for testing...
And yes, there's some Cairo patches listed in the new directory, but they're just a couple of quick hacks to help make them build on the PS3. There's no source changes to Cairo. Is PS3 support in the main Cairo branch, or is there still work to be done there?
That said, doesn't mean that all companies follow that section correctly. For example, the latest versions of Sony TVs and some other consumer devices (Bluray players, etc) use Pango and cairo to provide i18n text. They make the sources to pango and cairo available on their website, but no way for me to build a new firmware using an updated pango. Reminds me that I wanted to contact the SFLC about this.
I've been going through the Diff file too. Naming conventions for the different styles of webkit branches like QT or GTK look like it's based on the GUI toolkit used; Androvsky mentions that above. In the PS3 webkit port they apparently take a GTK port and convert it to what they call a POSIX port similar to what Google does with Android. This would be confusing/will be confusing to just about everyone because POSIX is normally thought of as a extended set of OS standards for a bunch of things starting with File I/O and ending up with mouse events. We don't normally associate it with a webkit port.androvsky said:I'm going through ps3-webkit-support.diff because I'm bored.
Naturally the full source of his changes are in that .diff file also. From what I can tell, the posix platform only refers to the PS3 in webkit, it doesn't show up at all in the mainline source code (unix versions are typically under their widget library, like Qt or gtk). There's a lot of functions that aren't implemented, but they're mainly ones that involve windowing that you wouldn't expect to be supported on the PS3.
This might not mean much since I don't see the cool stuff from Chrome in these sources, like bookmark syncing, but it's a huge freaking project., and the diff only covers what needed to be changed so it works on the PS3. It might not even get Chrome branding visible to the user, but I think if he's calling it ChromeClient, we can expect good things for the future.
On the X Windowing System and why Google isn't using it for Chrome OS
14 July 2009
Now, why then does Google not use an X windowing system in Chrome OS? The technical explanation for this is they simply dont need it for what theyre doing.
Another acquisition Google made in 2005 was a company called Skia Inc. that marketed a 2D graphics library also called Skia. The Skia library, written in C, does vector graphics, text, and images. It was open-sourced in 2008. Same features as Cairo
In writing Android, Google used Skia as the graphics backend for its windowing system and GUI toolkit. They also wrote a Skia backend for WebKit, which is used in the Android web browser. This same Skia Webkit backend is also used by Chrome on all of the platforms it supports. This is what I think Sony will do with Cairo
What Google has done in Android, and will do in Chrome OS, is write a simplistic windowing system using Skia, and let that output directly to the device framebuffer, while Im no expert on Skia, I assume it also has a backend implementing its painting operations via OpenGL, which would then make it easily hardware-acceleratable on a variety of different hardware offerings.
So to sum it up:
Google already has Skia-on-kernel-without-X working in Android, and they already have Chrome/WebKit using Skia. Chrome OS is unlikely to have the sort of drag-windows-around-on-a-desktop user experience that OS X or KDE offer (I expect it will be something more iPhone/Android-like), so while they could certainly use X, the small subset of its functionality they actually require is easily written anew using Skia, and doing so means they dont have to import a significant outside codebase and get involved with its development.
Source/WebCore/platform/posix/SearchPopupMenuPOSIX.cpp | 61
Source/WebCore/platform/posix/SearchPopupMenuPOSIX.h | 50
+ // draw popup menu bg
+ cairo_set_source_rgba(cr, RGBA_BG);
+ cairo_rectangle(cr,
+ m_x,
+ m_y + m_h,
+ m_w,
+ m_itemH * m_visibleCount + m_outlineW * 2);
+ cairo_fill(cr);
+
+ // draw popup menu outline
+ cairo_set_source_rgba(cr, RGBA_OUTLINE);
+ cairo_rectangle(cr,
+ m_x,
+ m_y + m_h,
+ m_w,
+ m_itemH * m_visibleCount + m_outlineW * 2);
+ cairo_set_line_width(cr, m_outlineW);
+ cairo_set_line_join(cr, CAIRO_LINE_JOIN_MITER);
+ cairo_stroke(cr);
+#endif
+
+ // set clip area
+ cairo_rectangle(cr, m_x, m_y + m_h + m_outlineW, m_w, m_itemH * m_visibleCount);
+ cairo_clip(cr);
+ cairo_new_path(cr);
+
+ // draw text
+ cairo_select_font_face(cr,
+ "",
+ m_fontIsItalic ? CAIRO_FONT_SLANT_ITALIC : CAIRO_FONT_SLANT_NORMAL,
+ m_fontIsBold ? CAIRO_FONT_WEIGHT_BOLD : CAIRO_FONT_WEIGHT_NORMAL);
+ cairo_set_font_size(cr, m_fontSize);
+
+ for (int i = 0; i < m_itemCount; i++) {
+ if (i == m_selected) {
+#if USE_THEME_IMAGES
+ WebCore::RenderThemePOSIX:aintThemeImage3x3(&ctx, highlight,
+ WebCore::IntRect((int)(m_x + m_outlineW),
+ (int)(m_visibleY + m_itemH * i),
+ (int)(m_w - m_outlineW * 2),
+ (int)(m_itemH)),
+ 1, 1, 1, 1);
+#else
+ // draw hovered highlight
+ cairo_set_source_rgba(cr, RGBA_HIGHLIGHT);
+ cairo_rectangle(cr,
+ m_x + m_outlineW,
+ m_visibleY + m_itemH * i,
+ m_w - m_outlineW * 2,
+ m_itemH);
+ cairo_fill(cr);
+#endif
+
+ // draw hovered text
+ cairo_set_source_rgba(cr,RGBA_TEXT_HOVERED);
+ cairo_move_to(cr,
+ m_x + m_outlineW + m_paddingW,
+ m_visibleY + m_itemH * (i + 1) - m_paddingH - m_fontDescent);
+ cairo_show_text(cr, m_items);
+ } else {
+ // draw non-selected text
+ cairo_set_source_rgba(cr, RGBA_TEXT_NORMAL);
+ cairo_move_to(cr,
+ m_x + m_outlineW + m_paddingW,
+ m_visibleY + m_itemH * (i + 1) - m_paddingH - m_fontDescent);
+ cairo_show_text(cr, m_items);
+ }
+ }
+
+ cairo_restore(cr);
+
+if TARGET_POSIX
+WebKit := $(srcdir)/Source/WebKit/posix
+else
WebKit := $(srcdir)/Source/WebKit/gtk
+endif
WebKit2 := $(srcdir)/Source/WebKit2
# Libraries and support components
@@ -106,8 +110,11 @@ global_cppflags += \
-Wformat -Wformat-security -Wno-format-y2k -Wundef \
-Wmissing-format-attribute -Wpointer-arith -Wwrite-strings \
-Wno-unused-parameter -Wno-parentheses \
- -fno-exceptions -DENABLE_GLIB_SUPPORT=1
+ -fno-exceptions
+if !TARGET_POSIX
+global_cppflags += -DENABLE_GLIB_SUPPORT=1 This is interesting.
+endif
global_cxxflags += \
-fno-rtti
@@ -163,6 +170,7 @@ libJavaScriptCore_la_CPPFLAGS = \
$(javascriptcore_cppflags)
# Extra checks and flags
+if !TARGET_POSIX
global_cppflags += \
-DBUILDING_CAIRO__=1 \
-DBUILDING_GTK__=1 \
H_Prestige said:How would Chrome even run on just 256mb RAM? That browser is a notorious RAM hog.
H_Prestige said:How would Chrome even run on just 256mb RAM? That browser is a notorious RAM hog.
Truespeed said:Wait, what? Is there a reason why it can't use the available video ram? As for Chrome being a memory hog, well that's debatable as it opens a new process for each tab - which is good. There's nothing preventing them from not doing this in the PS3 implementation or just using virtual RAM to handle the extra tabs.
jeff_rigby said:One last time, it's not Chrome it's Android Chrome-like. Webkit isn't even the big news, it's Cairo SVG.
And for those of you who question how much memory will be needed, just like with Chrome on Android platforms, it's all Scalable Vector Graphics which requires less ram.
At least in Linux, the PS3 can use the video ram as a swap file. It's slow, but still better than going to disk. The problem is that the Cell can't access video memory directly at anything close to a reasonable speed, so you have to tell the RSX to move data in and out of system ram. The PS3 has much leaner (I hope) GUI libraries, which will help, in addition to the OS not taking a lot of ram. Might not be able to have as many tabs open as you can with the current browser, but I'll take two good tabs over eight poorly-rendered ones.Truespeed said:Wait, what? Is there a reason why it can't use the available video ram? As for Chrome being a memory hog, well that's debatable as it opens a new process for each tab - which is good. There's nothing preventing them from not doing this in the PS3 implementation or just using virtual RAM to handle the extra tabs.
Well, Steam did just get a new codec for cross-game chat, and we are supposed to have cross-platform play... heh, would be nice. I'm still half-expecting a firmware update before Portal 2 just due to how cagey Sony and Valve are about the details even now.Considering that PS3 firmware updates have been minor for a looooong time, it would be nice if they had in store a big UI upgrade, Chrome as the new web browser and finally cross game chat implemented for 4.0 to be released around E3.
Lol, wow. Someone even asked Google. Reminds me of a person I know who works at Google who was surprisingly upset at the rumor that Firefox was coming to the PS3 that was going around a couple years ago.Well guys you are famous now: http://translate.google.com/translat...rnetbrowser/
Ooops, good catch. Oh well, at least we're getting something close enough to Chrome (although I'd love bookmark syncing on the PS3). I did notice all the not enabled ChromeClient functions, but I assume they had to do with how the PS3 handles windows.Edit: Chromeclient is a term coined because Google Chrome developed the library and pushed it back into the main webkit branch. It's related to the opening of windows in webkit. It does not mean Chrome is coming to the PS3.
The ChromeClientPOSIX mentioned above is the opening and drawing of a window using the Sony POSIX theme Cairo SVG script. If you look at the .diff file many of the ChromeClient routines return not enabled.
Link doesn't work..arnoldocastillo2003 said:Well guys you are famous now: http://translate.google.com/transla...jgt-de-ps3-google-chrome-als-internetbrowser/
wild optimism:Kingsora said:Link doesn't work..
this one does: http://translate.google.com/transla...jgt-de-ps3-google-chrome-als-internetbrowser/
Btw when is the soonest you guys think this could come out? Months, a year, years?
Not to mention you won't have extensions running, and they could easily put a tab limit like most portable browsers.jeff_rigby said:One last time, it's not Chrome it's Android Chrome-like. Webkit isn't even the big news, it's Cairo SVG.
And for those of you who question how much memory will be needed, just like with Chrome on Android platforms, it's all Scalable Vector Graphics which requires less ram.
No, but given their relationship ... it'll be curious to see how things pan out for the future. Could PS4 see an actual Chrome build? Or how about GoogleTV, or an Android-like browser? For an Android-like browser, I wouldn't be shocked if NGP sees it. GoogleTV? Not be surprising if it hits their TV's, BD-players, receivers, and PS4.Truespeed said:Of course it's not going to be Chrome. Google wouldn't waste their time with a PS3 Chrome build.
Admittedly I'm a newb for haxx0ring ... but is there any reason to assume the current PS3 browser is any less susceptible to such an attack?sharath_kumar said:since the browsers are susceptible to buffer overflow attacks, wont this be a problem for ps3 security? the browser will be running in gameos. won't it? unless they can make it to run in some non-priviliged mode, i wonder how sony will handle this problem.
Raistlin said:No, but given their relationship ... it'll be curious to see how things pan out for the future. Could PS4 see an actual Chrome build? Or how about GoogleTV, or an Android-like browser? For an Android-like browser, I wouldn't be shocked if NGP sees it. GoogleTV? Not be surprising if it hits their TV's, BD-players, receivers, and PS4.
assuming the browser runs inside the hypervisor.sharath_kumar said:since the browsers are susceptible to buffer overflow attacks, wont this be a problem for ps3 security? the browser will be running in gameos. won't it? unless they can make it to run in some non-priviliged mode, i wonder how sony will handle this problem.
sharath_kumar said:since the browsers are susceptible to buffer overflow attacks, wont this be a problem for ps3 security? the browser will be running in gameos. won't it? unless they can make it to run in some non-priviliged mode, i wonder how sony will handle this problem.
theBishop said:Just friendly head's up. "POSIX" is just a generic term for unix-like platforms. Maybe somebody has super insider info that I missed and a Sony coder is being cute, but it's highly unlikely a Playstation Theme would be named that.
http://en.wikipedia.org/wiki/Posix
I haven't read this thread very carefully, but jeff_rigby seems to be stabbing wildly in the dark.
I've been going through the Diff file too. Naming conventions for the different styles of webkit branches like QT or GTK look like it's based on the GUI toolkit used; Androvsky mentions that above. In the PS3 webkit port they apparently take a GTK port and convert it to what they call a POSIX port similar to what Google does with Android.
This would be confusing/will be confusing to just about everyone because POSIX is normally thought of as a extended set of OS standards for a bunch of things starting with File I/O and ending up with mouse events. We don't normally associate it with a webkit port.
Hildon is an application framework originally developed for mobile devices (PDAs, mobile phones, etc.) running the Linux operating system. It was developed by Nokia for the Maemo operating system and is now a part of GNOME. It focuses on providing a finger-friendly interface.[1] It is primarily a set of GTK+ extensions that provide mobile-deviceoriented functionality, but also provides a desktop environment that includes a task navigator for opening and switching between programs, a control panel for user settings, and status bar, task bar and home applets.
Edit: You could be on to something. It looks like Sony is planning to port webkit to multiple platforms. This to probably support webkit applications. Chrome for instance is included in Sony Vaio laptops sold by Sony for I would guess coming webGL games.patsu said:You should check if Cairo SVG and POSIX are part of PS Suite specs. If so, it may mean that every PS Suite device has a WebKit browser. And perhaps the POSIX theme is just a temp name for PS Suite theme.
It's best if we don't go there...jeff_rigby said:Kinda reminds me of the "3.5" Flash stream and HTML"5" references in number for Firmware 3.5 in the PS3 and 6.35 for the PSP<grin>.
Isn't Android based on a 2.6 linux kernel? And how do you know NGP and the PS3 run on linux? I remember seeing some evidence that the PS3 OS uses a commerical embedded unix variant.Most I have been able to find is NGP and PS3 are going to share libraries. I'm confident that the NGP is going to use Cairo. Sony is apparently going SVG on ALL networked platforms that can support SVG.
I know you already know this; NGP is not based on Android, it's a CE/Embedded Linux (2.6) kernel just like the PS3.
Okay, why do you think Gstreamer is in the PS3? Video codecs on the PS3 are mostly useless without SPU support, and I think it's safe to say that there wasn't any SPU support in Gstreamer until after linux was removed. The only way it could've been is as a wrapper for Sony's codecs, at which point I have to wonder why bother with Gstreamer?Cairo & Gstreamer are now in the PS3 (Gstreamer since 2005) and from the NGP demos are already in the NGP.
androvsky said:It's best if we don't go there...
Isn't Android based on a 2.6 linux kernel? And how do you know NGP and the PS3 run on linux Linux 2.6 kernel? I remember seeing some evidence that the PS3 OS uses a commerical embedded unix LINUX variant.
Okay, why do you think Gstreamer is in the PS3? Video codecs on the PS3 are mostly useless without SPU support, and I think it's safe to say that there wasn't any SPU support in Gstreamer until after linux was removed. The only way it could've been is as a wrapper for Sony's codecs, at which point I have to wonder why bother with Gstreamer?
androvsky said:wild optimism:
If they tested it in private and only just now put the testing pages out for people with debug units to check out, it could happen in a few weeks. Even though the code was recently posted, it was dated from early February. Since they're making their GPL-compliance post now, one could assume that a debug firmware is going out soon for wide testing.
realism:
Summer is much more likely though. It looks like Geoff Levand is the only person working on it, so if any issues crop up, it could get delayed a lot. And those testing pages are pretty basic... I have no clue how far along the port actually is. I'd like to say it's done and ready to be distributed, otherwise they wouldn't have posted the snapshot, but I have no way of knowing. They still haven't uploaded the video clip for the video tag test page. :/
I can't imagine it not being done this year, the fall update at the latest I'd say.
Playstation Plus subscribers only!ReBurn said:Will I have to log into PSN to use it?
jeff_rigby said:1) Gstreamer, Cairo and Linux 2.6 are mentioned in the Sony Snap developer site
2) The libraries I listed pulled from the .Diff file are Linux (glib for instance) and the list includes Gstreamer and Cairo.
3) Wiki states that Power PC support for Gstreamer was available in 2005 with it's primary use for game consoles. Too soon for the Wii and MS wouldn't use it in the Xbox360 as Gstreamer is a AV standard for Linux platforms.
Parade officially rained on.Mush said:Playstation Plus subscribers only!