Projects tagged ‘chromium’

Chrome Privacy Guard is a small tool that automatically deletes the unique Client ID before each run of Google Chrome. This tool scans the "Local State" file inside the Chrome directory, removes all ... [More] Client ID related info and automatically starts Chrome. [Less]

Chromium OS is an open-source project that aims to build an operating system that provides a fast, simple, and more secure computing experience for people who spend most of their time on the web.

IntroductionThe chromium embedded framework (CEF) is a project composed of multiple parts. The core of the project is a static library, called libcef. Libcef encapsulates a standard chromium browser ... [More] implementation, including window creation, resource loading, printing, context menus and other basic capabilities. The embedded client user can customize the default functionality and handle browser notifications by registering delegate interfaces. The user of CEF is completely insulated from the underlying chromium layer, similar to how the chromium layer insulates users from WebKit objects. The libcef_dll project wraps the core libcef library in an exported C API. The libcef_dll_wrapper project then wraps the C API with the same CEF C++ interfaces allowing transparent use of both the static and dynamic CEF builds. As time goes on other interfaces will be built on top of libcef that provide easy access to the CEF core capabilities from development frameworks such as ActiveX, MFC, wxWidgets and so on. Binary DistributionsBinary distributions, which include all files necessary to build a CEF-based application, are available in the Downloads section. Binary distributions are stand-alone and do not require the download of CEF or Chromium source code. Source DistributionsThe CEF project is an extension of the Chromium project hosted at http://www.chromium.org. To build CEF from source code you must first download Chromium as described at http://dev.chromium.org/developers/how-tos/get-the-code. The CEF files must then be placed in the top-level Chromium "src" directory, at the same level as the "base", "chrome", and "third-party" directories. For instance, if your Chromium installation directory is C:\svn\Chromium\src then the CEF files should reside in C:\svn\Chromium\src\cef. The CHROMIUM_BUILD_COMPATIBILITY file provides information about compatibility between CEF and Chromium revisions. To update to a specific Chromium revision, use gclient sync --revision src@#### --force and the DEPS file will make sure you get the other directories in their matching forms. Run the cef_create_projects.bat script in the CEF root directory to generate Visual Studio project files from the GYP configuration. If both VS2005 and VS2008 are installed on your system you can set the GYP_MSVS_VERSION environment variable to "2005" or "2008" before running cef_create_projects.bat to create project files for that version. To download CEF source code updates and run the cef_create_projects.bat script automatically every time Chromium sources are updated you can integrate CEF with the gclient tool. Edit the .gclient file that resides in the parent directory of Chromium "src" ("C:\svn\Chromium" in the above example) and add the following lines to the existing solutions array: solutions = [ { #Existing definitions here... }, # BEGIN NEW LINES { "name" : "src/cef", "url" : "http://chromiumembedded.googlecode.com/svn/trunk", }, #END NEW LINES ]SupportAn overview of CEF usage is available on the General Usage Wiki page. CEF support and related discussion is available on the CEF Forum. Notable ChangesNot all revisions are listed here. View the Changes list to see the complete list of revisions. October 2, 2009: Revision 50 adds GYP support for generating the CEF project files. This makes it easy to build CEF with both VS2005 and VS2008. See the "Source Distributions" section above for additional details. August 21, 2009: Revision 37 adds support for custom scheme handlers. Use the new CefRegisterScheme() function in combination with the CefSchemeHandlerFactory and CefSchemeHandler classes to create handlers for requests using custom schemes such as myscheme://mydomain. July 24, 2009: Revision 32 helps to speed up the addition of new features and bug fixes to CEF. It adds the CEF Patch Application Tool and the "patch" project which together support automatic application of patches to the Chromium and WebKit source trees as part of the build process. See the README.txt file in the new patch directory for additional information. July 8, 2009: CEF now has a dedicated build bot thanks to Nicolas Sylvain and Darin Fisher over at Google. The build bot synchronizes to each Chromium revision and then builds CEF, reporting on any compile errors that occur. Having a build bot for CEF will help the Chromium developers avoid accidentally breaking API features required by CEF, and help the CEF developers keep up with the frequently changing Chromium HEAD revision. You can view the build bot output at http://build.chromium.org/buildbot/waterfall.fyi/waterfall?branch=&builder=Chromium+Embedded June 20, 2009: Revision 30 adds the CEF Translator Tool which facilitates automatic generation of the C API header file (cef_capi.h) and CToCpp/CppToC wrapper classes. See the translator.README.txt file in the new tools directory for additional information. Introduction of this tool required minor changes to the CEF C++ and C APIs. The C++ 'arguments' attribute of CefV8Handler::Execute() and CefV8Value::ExecuteFunction() now has the 'const' qualifier. C API global function names that were previously in the cef_create_classname() format are now in the cef_classname_create() format. The C API cef_frame_t::get_frame_names() member function now has return type 'void' instead of 'size_t'. The C API cef_frame_t::execute_javascript() member function has been renamed to cef_frame_t::execute_java_script(). May 27, 2009: Revision 26 introduces two major changes to the CEF framework. Frame-dependent functions such as loading content and executing JavaScript have been moved to a new CefFrame class. Use the new CefBrowser::Get*Frame() methods to retrieve the appropriate CefFrame instance. A CefFrame instance will now also be passed to CefHandler callback methods as appropriate. The CEF JavaScript API now uses the V8 framework directly instead of creating NPObjects. JavaScript object hierarchies can be written in native C++ code and exported to the JavaScript user-space, and user-space object hierarchies can be accessed from native C++ code. Furthermore, support for the V8 extension framework has been added via the new CefRegisterExtension() function. The CefJSHandler and CefVariant classes have been removed in favor of new CefV8Handler and CefV8Value classes. To attach values to the JavaScript 'window' object you must now implement the CefHandler::HandleJSBinding() callback method instead of calling the (now removed) CefBrowser::AddJSHandler() method. Future CapabilitiesThe following advanced capabilities will be added to the framework at a later time. Support "themes" for customizing user interface elements such as buttons, scroll bars, etc. Provide access to and support manipulation of the DOM structure. Work In ProgressCEF is still very much a work in progress. If you're looking for ways to contribute please view the open issues or do a search for TODO(cef) in the source code. We also need to write unit tests for all of the supported functionality. [Less]

I'm refocusing. I've decided that I'm going to be using Rhino for future projects. I'm building up other things to support that. OneMonkey is a set of enhancements to the Mozilla Project's ... [More] SpiderMonkey JavaScript engine. The makefile pulls a recent check-in of SpiderMonkey from CVS (20070330) and builds it with E4X, optimizations, a small framework for native interfaces, some basic POSIX-like native functions, a framework for custom virtual machines, an interpreter, an JS2XDR compiler and XDR virtual machine, and adds a UCPP-based JavaScript preprocessor. The makefile, support frameworks, OneMonkey Interpreter, Compiler, and Virtual Machine are New BSD-styled licensed, UCPP is licensed under a New BSD-styled license, and SpiderMonkey is licensed under the MPL 1.1 license. OneMonkey is a set of enhancements to the Google Chromium V8 JavaScript engine. The makefile pulls the most recent revision of V8 from SVN and builds it with a framework for native interfaces, some basic POSIX-like native functions, a framework for custom virtual machines, a JS/CC based preprocessor that implements Windows Scripting Host/JavaScript.Net style preprocessing, and a JS/CC based C2V8 interface compiler. Scratch that...I need to try to catch a bigger fish, a more utilitarian fish. And I'm finding tools that will let me do that. OneMonkey is a suite of tools and a class library that will allow you to write portable JavaScript for all scales of programing (Enterprise, Embedded, Systems, Application, Web, Scripting). I'm currently aiming towards supporting the following JavaScript implementations: Google V8, Mozilla Rhino, Mozilla SpiderMonkey/TraceMonkey, Mozilla Tamarin, Mozilla ActionMonkey, WebKit SquirrelFish Extreme, Microsoft Windows Script Host, Microsoft JScript.Net, Mono JScript, Parrot/ECMAScript, Parrot/PJS, Parrot/WMLScript, Digital Mars DMDScript, Simple ECMAScript Engine. Initial focus will be on V8, Rhino, and SpiderMonkey/TraceMonkey (in that order). The class library will mimic the JDK Class Hierarchy. --- TODODefine CLI options Implement command line handling Replace the ridiculous scons/python requirement Start by implementing JS2C.py & macros.py in something else (hopefully js, maybe ucpp) Compile everything in one step (grab pertinent sources from v8, re2c, om) Implement "newlib"-style NewJSLib for portable IO Rethinking my newjslib implementation; I may decide to refactor to a posix/libc system stdio, stdlib, unistd, signal, sys/file, sys/stat, grp, sys/wait sys/wait waitpid is incomplete, need to add W* status constants wait() waitpid(pid,opt) stdio Not implementing stdio/fgetpos,fprintf,fscanf,fsetpos,gets,printf,scanf,setbuf,setvbuf,snprintf,sprintf,sscanf,vfprintf,vfscanf,vprintf,vscanf,vsnprintf,vsprintf,vsscanf fgets( file, len ) : NULL | String fread( file, len ) : undefined | String read( fd, len ) : undefined | String unistd Not implementing unistd/fork,pipe,pthread_atfork,sbrk,brk,sysconf,vfork pread( fd, nbyte, off ) : undefined | String read( fd, len ) : undefined | String readlink( path, len ) : undefined | String grp Not implementing grp/getgrnam,getgrgid,getgroups, Figure out how not implementing om.lang.Cloneable & om.io.Serializable affects things. JavaDocs suggests that both interfaces are handled internally...hmm... Define which APIs to attack first om.lang.System, depends on om.lang.SecurityManager STUBBED, om.util.Map, om.util.Properties, om.io.Console STUBBED, om.io.PrintStream, om.io.InputStream, om.nio.channels.Channel om.io.FileInputStream & om.io.FileOutputStream should use _.FileChannelImpl om.io.PrintStream extends om.io.FilterOutputStream and depends on om.io.File, om.io.OutputStream, om.lang.CharSequence, om.util.Locale om.io.File implements om.lang.Comparable and depends on om.net.URI, om.io.FilenameFilter, om.io.FileFilter Need to implement a lot of libc calls to support om.io.File ... hmm... can* ::: access createNewFile ::: creat createTempFile ::: mktemp delete ::: unlink deleteOnExit ::: stub exists ::: open & error code getAbsoluteFile ::: js getAbsolutePath ::: js getCanonicalFile ::: js getCanonicalPath ::: js getFreeSpace ::: stub getName ::: js getParent ::: js getParentFile ::: js getPath ::: js getTotalSpace ::: stub getUsableSpace ::: stub is* ::: access length ::: stat list() ::: opendir/readdir/closedir list(FilenameFilter) ::: opendir/readdir/closedir listFiles() ::: opendir/readdir/closedir listFiles(FileFilter) ::: opendir/readdir/closedir listFiles(FilenameFilter) ::: opendir/readdir/closedir static listRoots() ::: js mkdir ::: mkdir mkdirs ::: js mkdir renameTo ::: rename set* ::: chown toString ::: js toURI ::: om.net.URI om.net.URI implements om.lang.Comparable om.net.URI is half stub/half implementation; non-functional on it's own. om.io.FilenameFilter is an interface om.io.FileFilter is an interface om.util.Locale implements om.lang.Cloneable and om.io.Serializable Stubbed om.util.Locale om.lang.Cloneable, om.io.Serializable not implemented, probably should be empty class them om.io.FilterOutputStream extends om.io.OutputStream which implements om.io.Flushable, om.io.Closeable, and om.lan.Appendable om.lang.Appendable depends on om.lang.CharSequence om.io.InputStream implements om.io.Closeable om.lang.SecurityManager extends Object om.util.Properties extends om.util.Hashtable which implements om.io.Serializable, om.lang.Cloneable, om.util.Map om.util.Map is template interface depending on two types om.io.Console implements om.io.Flushable SQLite3, Xlib, Imlib2, OpenGL java.io, java.lang, java.math, java.net, java.sql & JDBC 4, java.text, java.util, java.util.prefs, java.util.regex, javax.net Reuse k7, re2c, php.js, ucpp, JS/CC for portability layer starting with V8 & SpiderMonkey/TraceMonkey (nothing to do but write wrappers for Rhino). Start hacking [Less]

Chromium Update v0.1 Check changelog of all Chromium builds updates from Toolstrip. Screenshot Usage The updates of changelog not viewed show in the Toolstrip. Open Preferences: ... [More] Click the Icon in the Toolstrip. Open Changelog: Click the build number in Toolstrip. Requirements Last version of Google Chrome Dev or Chromium dev. More information: Chromium Dev Channel Download Last version: Chromium Update v0.1 Download ChromiumUpdate-v0.1.crx Releases Version Features 0.1 -First release. [Less]

CustomNewTab is no longer supported This is due to an incompatibility with the latest versions of Chrome that cannot be fixed. For more info, see here. CustomNewTab is a Google Chrome extension that ... [More] allows you to change the way Chrome's default new tab page behaves. Features See information on the latest version. Once you've installed the extension : Go to chrome-extension://bpadoikgkkpmocgnhmkipbchigggjnje/dashboard.html in order to customize your new tab. [Less]

Y! Weather is a Google Chrome extension. It helps you quickly check weather information. Requirement Chrome/Chromium version 4.x Usage 1. Quick weather information: 2. Setting: 3. Example: Location: Paris Language: French Unit: Fahrenheit

This extension derived from LDRFullFeed (http://userscripts.org/scripts/show/22702)

this little launcher is a GUI for launching chromium with multi command line switches. it can handle DDE calls, and register itself as default browser on start up and restore the default browser ... [More] settings when it is closed. it is an attempt to make chromium portable. [Less]

A web-content embedding layer for OGRE3D.