Bundling chrome extension by default with chromium build

[Prathap]

i am try to bundle chrome extension with chromium build…. could anyone
help me out where should i place my extension so it will be bundled on
the build time… currently i have added my extension in
external_extension.json & also i have updated the same common.gypi …
but nothing seems to work...

your help is much appreciated... thanks in advance

[Sam Kerner]

On Tue, Nov 8, 2011 at 8:54 AM, Prathap <jayap...@gmail.com> wrote:
> i am try to bundle chrome extension with chromium build…. could anyone
> help me out where should i place my extension so it will be bundled on
> the build time… currently i have added my extension in
> external_extension.json & also i have updated the  same common.gypi …
> but nothing seems to work...

While you could bundle an extension by making it a part of chrome at
build time, there is no simple way to do this and code changes might
break your method in the future. If you control an installer that the
user will run, consider having the installer create a registry key
that will cause chrome to install the extension on startup. Docs on
this are available here:

http://code.google.com/chrome/extensions/trunk/external_extensions.html

Stepping back, if you tell us your overall goal we might be able to
recomend a better course of action.

Sam

>
> your help is much appreciated... thanks in advance
>

> --
> You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.
> For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
>
>

[Prathap]

hi SAM,
thanks for the response
i am building a customized browser from chromium code base for mac/
windows environment. One of the things i thought for restricting user
browsing websites is with extension and so there isn't much effort for
changing the chromium code. Basically i want to do the following
things

[1] By default chromium browser should have a set of extension
installed in it
[2] User shouldn't have option to disable or remove the extension from
the browser.

is these things possible using a installer for both mac/windows. your
help is much appreciated

thanks
Prathap

On Nov 10, 2:22 am, Sam Kerner <sker...@google.com> wrote:

> On Tue, Nov 8, 2011 at 8:54 AM, Prathap <jayaprat...@gmail.com> wrote:
> > i am try to bundle chrome extension with chromium build…. could anyone
> > help me out where should i place my extension so it will be bundled on
> > the build time… currently i have added my extension in
> > external_extension.json & also i have updated the  same common.gypi …
> > but nothing seems to work...
>
> While you could bundle an extension by making it a part of chrome at
> build time, there is no simple way to do this and code changes might
> break your method in the future.  If you control an installer that the
> user will run, consider having the installer create a registry key
> that will cause chrome to install the extension on startup.  Docs on
> this are available here:
>
> http://code.google.com/chrome/extensions/trunk/external_extensions.html
>
> Stepping back, if you tell us your overall goal we might be able to
> recomend a better course of action.
>
> Sam
>
>
>
>
>
>
>
>
>
> > your help is much appreciated... thanks in advance
>
> > --
> > You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

> > To post to this group, send email to chromium-extensi...@chromium.org.
> > To unsubscribe from this group, send email to chromium-extensions+unsubscr...@chromium.org.

[Mihai Parparita]

Chrome itself is experimenting with something like this (using the external extension mechanism that was mentioned earlier). See http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/default_apps.cc?revision=HEAD&view=markup for starting points.

Mihai

To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.

[Sam Kerner]

On Thu, Nov 10, 2011 at 3:14 AM, Prathap <jayap...@gmail.com> wrote:
> hi SAM,
> thanks for the response
> i am building a customized browser from chromium code base for mac/
> windows environment. One of the things i thought for restricting user
> browsing websites is with extension and so there isn't much effort for
> changing the chromium code. Basically i want to do the following
> things
>
> [1] By default chromium browser should have a set of extension
> installed in it
> [2] User shouldn't have option to disable or remove the extension from
> the browser.
>
> is these things possible using a installer for both mac/windows. your
> help is much appreciated

Take a look at the documentation for administrators on pre-installing
extensions:

http://www.chromium.org/administrators/pre-installed-extensions

Of the three options on that page, the only one that prevents users
from uninstalling an extension is "Pre-installing via Group Policy".
If you can use this, you will not have to modify chrome. The specific
policy you will want to set is:

http://www.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist

If you can not set a policy, the only way to keep users from
uninstalling an extension is to alter chrome. The method
Extension::UserMayDisable() in chrome/common/extensions/extension.h
tests that an extension from a specific source can be disabled by a
user. You could create a new install source and add its type to this
method. Making this work is not trivial, and maintaining it will be a
significant effort, so use policy if possible.

Sam

> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.

[Prathap]

Thanks Mihai & Sam...I will check it out and let you guys know if i
face any difficulty in implementing... thanks alot


Prathap

On Nov 12, 9:53 am, Sam Kerner <sker...@google.com> wrote:

> On Thu, Nov 10, 2011 at 3:14 AM, Prathap <jayaprat...@gmail.com> wrote:
> > hi SAM,
> > thanks for the response
> > i am building a customized browser from chromium code base for mac/
> > windows environment. One of the things i thought for restricting user
> > browsing websites is with extension and so there isn't much effort for
> > changing the chromium code. Basically i want to do the following
> > things
>
> > [1] By default chromium browser should have a set of extension
> > installed in it
> > [2] User shouldn't have option to disable or remove the extension from
> > the browser.
>
> > is these things possible using a installer for both mac/windows. your
> > help is much appreciated
>
> Take a look at the documentation for administrators on pre-installing
> extensions:
>
> http://www.chromium.org/administrators/pre-installed-extensions
>
> Of the three options on that page, the only one that prevents users
> from uninstalling an extension is "Pre-installing via Group Policy".
> If you can use this, you will not have to modify chrome.  The specific
> policy you will want to set is:
>

> http://www.chromium.org/administrators/policy-list-3#ExtensionInstall...

[Prathap]

hello Sam
I checked out on "Pre-installing via Group Policy"... but where do i
have to change for mac and windows... for mac is it on
org.chromium.chromium.manifest under the app/contents.. and for
windows is it in registry? currently i tried in mac by changing the
org.chromium.chromium.manifest file but it doesnt reflect here is the
piece of code

<dict>
<key>pfm_description</key>
<string></string>
<key>pfm_name</key>
<string>ExtensionInstallForcelist</string>
<key>pfm_targets</key>
<array>

<string>cfhdojbkjhnklbpkdaibdccddilifddb;https://clients2.google.com/
service/update2/crx</string>
</array>
<key>pfm_title</key>
<string></string>
<key>pfm_type</key>
<string>array</string>
</dict>

your help is much appreciated. thanks

Prathap

[Sam Kerner]

On Wed, Nov 16, 2011 at 11:44 AM, Prathap <jayap...@gmail.com> wrote:
> hello Sam
> I checked out on "Pre-installing via Group Policy"... but where do i
> have to change for mac and windows... for mac is it on
> org.chromium.chromium.manifest under the app/contents.. and for
> windows is it in registry? currently i tried in mac by changing the
> org.chromium.chromium.manifest file but it doesnt reflect here is the
> piece of code
>
> <dict>
>                        <key>pfm_description</key>
>                        <string></string>
>                        <key>pfm_name</key>
>                        <string>ExtensionInstallForcelist</string>
>                        <key>pfm_targets</key>
>                        <array>
>
> <string>cfhdojbkjhnklbpkdaibdccddilifddb;https://clients2.google.com/
> service/update2/crx</string>
>                        </array>
>                        <key>pfm_title</key>
>                        <string></string>
>                        <key>pfm_type</key>
>                        <string>array</string>
>                </dict>
>
> your help is much appreciated. thanks

I have no knowledge of the policy system, so I can't give you specific
instructions on how to use it. I would start by looking at the
following page:

http://www.chromium.org/administrators/policy-templates

If you get stuck after reading the documentation, the chrome support
forum would be a good place to ask questions:

http://www.google.com/support/forum/p/Chrome/

Sam

> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.

[Vương Nguyễn]

Did you bundle extension with chromium build? I have the same problem with you and can't fill the solution for it

Vào 20:54:18 UTC+7 Thứ ba, ngày 08 tháng mười một năm 2011, Prathap đã viết:

[nicholas...@lucidworks.com]

I am also having this problem. Did anyone ever figure out how to build an extension into chromium during build process?