Sugar Labs - User contributions [en]

Features/Multi selection screenshots

2013-04-16T08:42:04Z

Ajay Garg: Replaced content with "<noinclude> Multi selection screenshots </noinclude> http://wiki.sugarlabs.org/go/Features/Multi_selection"

<noinclude>
[[Category:Feature|Multi selection screenshots]]
</noinclude>

http://wiki.sugarlabs.org/go/Features/Multi_selection

Features/Multi selection screenshots

2013-04-16T08:41:40Z

Ajay Garg:

<noinclude>
[[Category:Feature|Multi selection screenshots]]
</noinclude>

http://wiki.sugarlabs.org/go/Features/Multi_selection

== Summary ==

Implements the ability to select multiple journal entries in the journal entry view and perform group operations (like copy, delete) on them.

== Owner ==
* Name: [[User:Walter| Walter Bender]], [[User:Gonzalo| Gonzalo Odiard]], [[User:erikos| Simon Schampijer]], [[tch| Martin Abente]], [[User:Ajay| Ajay Garg]], [[User:M_anish| Anish Mangal]]
* Email: walter@sugarlabs.org, gonzalo@laptop.org, erikos@sugarlabs.org, tch@activitycentral.com, ajay@activitycentral.com, anish@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Development status: This feature is tested to be working quite well in sugar-0.94 based dextrose-3 images. The patchset just needs to be ported over to the latest sugar code.

== Benefit to Sugar ==
This feature allows the users to perform operations on multiple journal entries at once, making it very efficient if the user has to perform repetitive tasks like copying/deleting journal entries for many entries. The users can also filter journal entries by using the already existing search facilities and perform operations on those.

Two ways of selecting multiple journal entries have been provided. The user can either click the checkbox next to individual journal entries or use the select/deselect all buttons provided on the toolbar (which only shows up if the feature is being used). This UI takes some ideas from the standard gmail interface in how it allows users to select multiple entries and perform operations on them.

Another interesting and useful side-effect of this feature is that a user can insert a pen-drive with many activity bundles, select 'all' and copy them to journal. The resulting operation will install all bundles on the XO laptop!

== Scope ==
This feature has already been implemented in sugar-0.94 based dextrose-3 builds. The feature just needs porting to the latest sugar version.
===Patches===
* Patch in sugar-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/1d3574120ac7d7bbc4017aa0d0b2aab19553cd4a 1] [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/dfb8c33f9591f7610e1b780bf7a95412c7cf8382 2]
* Patch in sugar-toolkit-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar-toolkit/sugar-toolkit-dextrose/commit/e5c63fd56cf9a3982e9629229870aa4319af3b76 1]
* Patch in sugar-artwork-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/348bef5511cc8b6774199a7d46b2740036e26431 1] [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/136d7abaf9b451aa18023b5c95bc79f3b622814c 2]

== History ==

The implementation is almost identical to the one done by Martin; details available at :
http://www.sugarlabs.org/~tch/journal2.mpeg

The only differences are ::

* More copy-to options :: Clipboard, Documents (in addition to mounted drives).
* When entries are copied to another location, both - the sources and the destinations - are de-selected automatically, without the user explicitly have to de-select them all manually.
* There has been a progress bar added for batch-operations.

== Basic utility of this feature ==

* This feature, merely does a loop-over for multiple entries. That is, the workflow and the end-result in the following two scenarios should be exactly the same ::
** Entries, E1, E2, E3 .... En, are operated upon one after the another, individually.
** Entries, E1, E2, E3 .... En, are selected together, and operated upon one after the another, as a single macro batch-operaton.

* Some particular use-cases ::
** Batch-operations <del>speeds up</del> makes XO-bundle installations more convenient, when multiple bundles are copied together from a USB drive to the journal. Thanks a ton to Sridhar Dhanapalan for the attention generated towards this (otherwise obscure) use-case.

== UI Design ==

=== Typical copy-to workflow ===

=[Step 01] Initial "Journal" view=
**[[File:b1.png]]

=[Step 02] Initial "Documents" view=
**[[File:b2.png]]

=[Step 03] Select an entry in the journal. The Edit-Toolbar, signifying batch-operations, appears.=
**[[File:b3.png]]

=[Step 04] Select more entries in the Journal.=
**[[File:b4.png]]

=[Step 05] Click "Copy" toolbar button, and select to copy to "Documents" from the pop-up=
**[[File:b5.png]]

=[Step 06] The confirmation alert appears. Click 'OK'=
**[[File:b6.png]]

=[Step 07] If there ia any error for a entry, the message is displayed as an alert. Click 'OK' to continue.=
**[[File:b7.png]]

=[Step 08] Progress status for entry=
**[[File:b8.png]]

=[Step 09] Progress status for next entry. Note that the progress-status changed without any user convention=
**[[File:b9.png]]

=[Step 10] Final "Journal" view. Note that all the "source" entries are de-selected.=
**[[File:b10.png]]

=[Step 11] Final "Documents" view. Note that all "destination" entries are de-selected.=
**[[File:b11.png]]

== Dependencies ==

None

== Contingency Plan ==

Don't use this feature

== Documentation ==

This feature was discussed in EDUJam 2011 and [http://wiki.sugarlabs.org/go/Features/Multi_selection this] feature page was a result of that.

Features/Transfer to many options

2013-03-26T17:26:51Z

Ajay Garg:

__TOC__
<br style="clear: both" />
== Basic Usage ==

* This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms ::

**Peer-to-Peer mode
*** Sharing in this mode is possible, only when the server and client XO(s) are on the same networks. Thus, peer-to-peer sharing would work on
**** XOs connected to the same Access Point.
**** Adhoc-Network connections.

**Via-School-Server mode
*** In this mode, an XO uploads an entry to the central School Server; from where the client XO(s) may download the entry.
*** This mode of sharing works as long as the School-Server is HTTP-pingable between the server and client XOs. Thus, this mode of sharing would work when
**** XOs are connected to the same Access Point (as long as school-server is pingable throughout).
**** XOs are connected to the different Access Points (as long as school-server is pingable throughout).
**** XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout).

== Credits ==
* '''Plan Ceibal'''
** For supporting this feature development.

* '''Sascha Silbe''' ''silbe@activitycentral.com''
** Initial Proposal for the solution based on WebDAV.

* '''Anish Mangal''' ''anish@activitycentral.com''
** Showed why simply accessing the webdav shares via "Browse" activity won't work.
** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But a Sugar-entry is more than just the (data) file; it is a combination of
*** Metadata-file
*** Data-file
*** Preview-file (optional)
** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).

* '''Ruben Rodriguez''' ''ruben@activitycentral.com''
** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.

* '''Nitika Mangal''' ''nitika@activitycentral.com''
** Testing

* '''David Rodriguez''' ''daroal@activitycentral.com''
** Testing

== Example Workflow for Peer-To-Peer Mode ==

== NOTES ==
** An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.
** Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".
** In the following screenshots' example, "PEER 2" mounts the shares of "PEER 1"; and uses that to copy entries onto its own XO. Thus, the entry is copied from XO-of-PEER-1 to XO-of-PEER-2.

== SCREENSHOTS ==

== [PEER 1] "Journal" - View. ==
:[[File:p11.png|640px]]

== [PEER 1] Detail view of the journal-entry. Note the preview presence. ==
:[[File:p12.png|640px]]

== [PEER 1] Initial "Local Shares" View ==
:[[File:p13.png|640px]]

== [PEER 1] Copy the journal entry to "Local Shares", to make it available for sharing to other peers. ==
:[[File:p14.png|640px]]

== [PEER 1] "Local Shares" view, after copying the entry. ==
:[[File:p15.png|640px]]

== [PEER 1] The detail view in "Local Shares". NOTE that the preview MUST be present, and it must be same as that of "Journal". ==
:[[File:p16.png|640px]]

== [PEER 2] Initial "Journal" - View. ==
:[[File:p20.png|640px]]

== [PEER 2] Neighborhood View. ==
:[[File:p21.png|640px]]

== [PEER 2] Click on "Access Share" of the peer, whose shares need to be accessed. ==
:[[File:p22.png|640px]]

== [PEER 2] The peer's shares are mounted. ==
:[[File:p23.png|640px]]

== [PEER 2] Copy the entry to the journal. ==
:[[File:p24.png|640px]]

== [PEER 2] Final "Journal" View. ==
:[[File:p25.png|640px]]

== [PEER 2] Detail-view of the entry. Note that the preview is the same as was on the remote peer. ==
:[[File:p26.png|640px]]

== Example Workflow for Via-School-Server Mode ==

== NOTES ==
** An entry present in "School Server Shares", is available to all the XOs. There isn't any mounting or anything required as such.
** Note that the entries present in "School Server Shares", have nothing to do with the entries present in "Local Shares".
** In the following screenshots' example, an XO uploads an entry to the school-server, and then downloads the same. HOWEVER, NOTE THAT ANY XO WOULD BE ABLE TO DOWNLOAD THE ENTRY PRESENT ON THE SCHOOL-SERVER, AND NOT ONLY NECESSARILY THE UPLOADER.

== SCREENSHOTS ==

== [UPLOAD] Initially, no entries are present on the school-server. ==
:[[File:sss1.png|640px]]

== [UPLOAD] Choose an entry to upload to the school-server. ==
:[[File:sss2.png|640px]]

== [UPLOAD] Enter the pasphrase when prompted. ==
:[[File:sss3.png|640px]]

== [UPLOAD] After uploading, ensure that the entry has in fact been uploaded to the school-server. ==
:[[File:sss4.png|640px]]

== [DOWNLOAD] Initial "Documents" view. ==
:[[File:sss5.png|640px]]

== [DOWNLOAD] Choose to copy the entry from school-server, to "Documents". ==
:[[File:sss6.png|640px]]

== [DOWNLOAD] Enter (incorrect) password. ==
:[[File:sss7.png|640px]]

== [DOWNLOAD] 'Passphrase not match' error occurs. ==
:[[File:sss8.png|640px]]

== [DOWNLOAD] Try copying again. ==
:[[File:sss9.png|640px]]

== [DOWNLOAD] Enter (correct) password. ==
:[[File:sss10.png|640px]]

== [DOWNLOAD] Confirm that the entry has been successfully downloaded. ==
:[[File:sss11.png|640px]]

== [DOWNLOAD] Ensure that in the detail view, the uploader-details are present. ==
:[[File:sss12.png|640px]]

== TEST-CASES THAT NEED TO PASS ==

* Inter-copying an entry between Journal/Documents/Mounted-Drives/Local-Shares/School-Server-Shares should behave in the same way. For eg, in the peer-to-peer mode, it was shown that the source-entry (on PEER-1) had a preview; the same was true when the entry finally arrived on PEER-2. In particular, the preview should "go along" as and when the entry goes, '''intra-XO''' or '''inter-XO'''.

* Things should work fine, irrespective of the fact that whether the sharing is done via single-mode, or batch-mode.

File:Proxy24.png

2013-02-17T11:07:52Z

Ajay Garg: uploaded a new version of "File:Proxy24.png"

File:Proxy21.png

2013-02-17T11:07:07Z

Ajay Garg: uploaded a new version of "File:Proxy21.png"

File:Proxy21.png

2013-02-17T11:06:22Z

Ajay Garg: uploaded a new version of "File:Proxy21.png"

Features/Proxy Settings

2013-02-17T11:05:52Z

Ajay Garg:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.99
* Last updated: 2013-02-17
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via "gconf" as well as "dconf" (gsettings).

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually", and restart when prompted so.
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file, and restart when prompted so.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-02-17T11:00:19Z

Ajay Garg: /* Detailed Description */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.99
* Last updated: 2013-02-17
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via "gconf" as well as "dconf" (gsettings).

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually".
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-02-17T10:59:17Z

Ajay Garg: /* Current status */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.99
* Last updated: 2013-02-17
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually".
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-02-17T10:58:53Z

Ajay Garg:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.98
* Last updated: 2013-02-17
* Percentage of completion: 100%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually".
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Proxy21.png

2013-02-17T10:55:15Z

Ajay Garg: uploaded a new version of "File:Proxy21.png"

File:Proxy24.png

2013-02-17T10:54:18Z

Ajay Garg: uploaded a new version of "File:Proxy24.png"

File:Proxy24.png

2013-02-17T10:48:00Z

Ajay Garg: uploaded a new version of "File:Proxy24.png"

File:Proxy21.png

2013-02-17T10:45:49Z

Ajay Garg: uploaded a new version of "File:Proxy21.png"

Features/Proxy Settings

2013-02-17T10:45:06Z

Ajay Garg:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually".
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy5.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy4.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Proxy23.png

2013-02-17T10:38:06Z

Ajay Garg:

File:Proxy22.png

2013-02-17T10:15:30Z

Ajay Garg:

File:Proxy24.png

2013-02-17T10:13:46Z

Ajay Garg:

File:Proxy21.png

2013-02-17T10:12:06Z

Ajay Garg:

Features/Proxy Settings

2013-02-17T10:10:22Z

Ajay Garg:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== "Manual" mode==

* Fill in the settings "manually".
:[[File:proxy21.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy22.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy23.png|640px]]

== Automatic mode - PAC==

* Fill in the URL of the proxy-file.
:[[File:proxy24.png|640px]]

* Now, open Browse. "www.facebook.com" should be blacklisted.
:[[File:proxy22.png|640px]]

* "www.google.com" shoud be allowed.
:[[File:proxy23.png|640px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Configuring Hidden Wifi Access Points

2013-02-16T07:27:49Z

Ajay Garg: /* Now, the workflow is the same, as conencting to any "normal" non-hidden wifi-network. */

<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Configuring Hidden Wifi Access Points]]
</noinclude>

== Summary ==
Currently, there is no way to connect to a hidden wifi Access-point, as it is (by definition) hidden in the Neighborhood-View.
This feature helps connect to such wifi access-points, whose SSIDs are not being broadcasted.

== Owner ==
* Name: [[User:ajay|Ajay Garg]]
* Email: <ajay@activitycentral.com>

== Current status ==
* Targeted release: DX4
* Percentage of completion: 100%

== Workflow Screenshots ==
===Configure the router/access-point, to ensure that the SSID is not being broadcasted===
[[Image:hnw_1.png|640px]]

===Ensure that there is no wifi-icon in the "Neighborhood-View", for the hidden wifi access-point===
[[Image:hnw_2.png|640px]]

===Go to "My Settings" -> "Network"; enter the SSID of the hidden wifi network, and restart when prompted===
[[Image:hnw_3.png|640px]]

===Upon restart, go to "Neighborhood-View"; the wifi-icon for the hidden network is now vissible. ===
[[Image:hnw_4.png|640px]]

===Now, the workflow is the same, as conencting to any "normal" non-hidden wifi-network.===

== Dependencies ==
None

== Documentation ==
None

== Release Notes ==
Nothing to be released (yet).

== Comments and Discussion ==
Please follow the comments on Dextrose and sugar-devel mailing list.

File:Hnw 1.png

2013-02-16T07:09:59Z

Ajay Garg: uploaded a new version of "File:Hnw 1.png"

File:Hnw 1.png

2013-02-16T07:08:59Z

Ajay Garg:

File:Hnw 4.png

2013-02-16T07:07:36Z

Ajay Garg:

File:Hnw 3.png

2013-02-16T07:06:48Z

Ajay Garg:

File:Hnw 2.png

2013-02-16T07:05:35Z

Ajay Garg:

Features/Configuring Hidden Wifi Access Points

2013-02-16T07:04:50Z

Ajay Garg:

<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Configuring Hidden Wifi Access Points]]
</noinclude>

== Summary ==
Currently, there is no way to connect to a hidden wifi Access-point, as it is (by definition) hidden in the Neighborhood-View.
This feature helps connect to such wifi access-points, whose SSIDs are not being broadcasted.

== Owner ==
* Name: [[User:ajay|Ajay Garg]]
* Email: <ajay@activitycentral.com>

== Current status ==
* Targeted release: DX4
* Percentage of completion: 100%

== Workflow Screenshots ==
===Configure the router/access-point, to ensure that the SSID is not being broadcasted===
[[Image:hnw_1.png|640px]]

===Ensure that there is no wifi-icon in the "Neighborhood-View", for the hidden wifi access-point===
[[Image:hnw_2.png|640px]]

===Go to "My Settings" -> "Network"; enter the SSID of the hidden wifi network, and restart when prompted===
[[Image:hnw_3.png|640px]]

===Upon restart, go to "Neighborhood-View"; the wifi-icon for the hidden network is now vissible. ===
[[Image:hnw_4.png|640px]]

===Now, the workflow is the same, as conencting to any "normal" non-hidden wifi-network.===
[[Image:hnw_5.png|640px]]

== Dependencies ==
None

== Documentation ==
None

== Release Notes ==
Nothing to be released (yet).

== Comments and Discussion ==
Please follow the comments on Dextrose and sugar-devel mailing list.

Features/Configuring Hidden Wifi Access Points

2013-02-16T07:03:58Z

Ajay Garg: Created page with "<noinclude>{{TOCright}} Category:Feature Page Incomplete Configuring Hidden Wifi Access Points </noinclude> == Summary == Currently, there is no way ..."

<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Configuring Hidden Wifi Access Points]]
</noinclude>

== Summary ==
Currently, there is no way to connect to a hidden wifi Access-point, as it is (by definition) hidden in the Neighborhood-View.
This feature helps connect to such wifi access-points, whose SSIDs are not being broadcasted.

== Owner ==
* Name: [[User:ajay|Ajay Garg]]
* Email: <ajay@activitycentral.com>

== Current status ==
* Targeted release: DX4
* Percentage of completion: 100%

== Workflow Screenshots
===Configure the router/access-point, to ensure that the SSID is not being broadcasted===
[[Image:hnw_1.png|640px]]

===Ensure that there is no wifi-icon in the "Neighborhood-View", for the hidden wifi access-point===
[[Image:hnw_2.png|640px]]

===Go to "My Settings" -> "Network"; enter the SSID of the hidden wifi network, and restart when prompted===
[[Image:hnw_3.png|640px]]

===Upon restart, go to "Neighborhood-View"; the wifi-icon for the hidden network is now vissible. ===
[[Image:hnw_4.png|640px]]

===Now, the workflow is the same, as conencting to any "normal" non-hidden wifi-network.===
[[Image:hnw_5.png|640px]]

== Dependencies ==
None

== Documentation ==
None

== Release Notes ==
Nothing to be released (yet).

== Comments and Discussion ==
Please follow the comments on Dextrose and sugar-devel mailing list.

Features/Proxy Settings

2013-02-05T18:52:43Z

Ajay Garg: /* Owner */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]], [[User:ajay_garg|Ajay Garg]] (ajay@activitycentral.com)

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Cp 14.png

2013-01-30T07:06:30Z

Ajay Garg: uploaded a new version of "File:Cp 14.png"

File:Cp 13.png

2013-01-30T07:04:28Z

Ajay Garg: uploaded a new version of "File:Cp 13.png"

File:Cp 12.png

2013-01-30T07:03:09Z

Ajay Garg: uploaded a new version of "File:Cp 12.png"

Features/Proxy Settings

2013-01-25T17:05:29Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode ('''Automatic-WPAD''' Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T17:04:34Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:46:36Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** '''(For those not interested in the technicalities, please proceed to the next bullet :D)''' To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:45:58Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** ('''For those not interested in the technicalities''', please proceed to the next bullet :D) To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:45:19Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** (For those not interested in the technicalities, please proceed to the next bullet :D) To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:29:48Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the settings, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:29:06Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manual''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:28:45Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user
*** to manualyy enter the proxy-settings ('''Manaul''' mode)
*** to manually enter the location of proxy-configuration file herself ('''Automatic (PAC)''' mode).

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:27:19Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:26:54Z

Ajay Garg:

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode( (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

* NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF ) (Thanks Ariel).

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Proxy5.png

2013-01-25T16:25:23Z

Ajay Garg:

File:Proxy4.png

2013-01-25T16:24:48Z

Ajay Garg:

File:Proxy3.png

2013-01-25T16:24:24Z

Ajay Garg:

Features/Proxy Settings

2013-01-25T16:23:38Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode( (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* '''Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com'''

:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

=Automatic mode - WPAD=

[[File:testproxysupport-wpad.png|400px]]

[http://wiki.sugarlabs.org/go/Features/Automatic_Proxy_Settings#WPAD_-_Web_Proxy_Autodiscovery WPAD Web Proxy AutoDiscovery]

* Open Browse activity with a white-listed page ( google.com in this example )

[[File:testproxysupport-google.png|400px]]

* Open Browse activity with a black-listed page ( facebook.com in this example )

[[File:testproxysupport-facebook.png|400px]]

:: NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF )

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:23:01Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

* Motive
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode( (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

=Automatic mode - WPAD=

[[File:testproxysupport-wpad.png|400px]]

[http://wiki.sugarlabs.org/go/Features/Automatic_Proxy_Settings#WPAD_-_Web_Proxy_Autodiscovery WPAD Web Proxy AutoDiscovery]

* Open Browse activity with a white-listed page ( google.com in this example )

[[File:testproxysupport-google.png|400px]]

* Open Browse activity with a black-listed page ( facebook.com in this example )

[[File:testproxysupport-facebook.png|400px]]

:: NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF )

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:22:16Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

==Automatic mode - WPAD==

===Motive===
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode( (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

=Automatic mode - WPAD=

[[File:testproxysupport-wpad.png|400px]]

[http://wiki.sugarlabs.org/go/Features/Automatic_Proxy_Settings#WPAD_-_Web_Proxy_Autodiscovery WPAD Web Proxy AutoDiscovery]

* Open Browse activity with a white-listed page ( google.com in this example )

[[File:testproxysupport-google.png|400px]]

* Open Browse activity with a black-listed page ( facebook.com in this example )

[[File:testproxysupport-facebook.png|400px]]

:: NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF )

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

Features/Proxy Settings

2013-01-25T16:21:18Z

Ajay Garg: /* Automatic mode - WPAD */

<noinclude>[[Category:Feature Ready for Release Manager]]
[[Category:Feature|Proxy Settings]]
</noinclude>

== Summary ==

Allow the user to configure proxy settings using the Sugar Control Panel.

== Owner ==

[[User:sascha_silbe|Sascha Silbe]]

== Current status ==

* Targeted release: 0.98
* Last updated: 2012-02-14
* Percentage of completion: 95%

== Detailed Description ==

Both individual users and deployments need to be able to set a proxy for
Sugar and activities to use. While we'd like the system to work that all
out automatically (e.g. using [https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol WPAD]), this often isn't possible. Common
reasons include legacy ("inherited") setups and network uplinks simply being
out of control of the user respectively deployment.

The existing Network Control Panel is enhanced by adding a new section for the
proxy settings. For consistency between Sugar and Gnome, the basic layout of
the Gnome 3 proxy settings has been mirrored: A combo box allows the user to
select how the proxy setting should be determined (None=direct connection,
Automatic=WPAD or PAC, Manual=enter host names and ports for each protocol).
Based on which method was selected, additional configuration options are
presented to the user.

The settings are stored via gconf, using the same keys as Gnome 2.

== Benefit to Sugar ==

See [[#Detailed Description|Detailed Description]].

== Scope ==

Modifying the existing Network Control Panel.

== UI Design ==

The Feature adds a new section to the Network Control Panel.

[[File:Proxy-section-1.png|center|600px|Upper part of the Network Control Panel]]
[[File:Proxy-section-2.png|center|600px|No proxy (direct connection)]]
[[File:Proxy-section-3.png|center|600px|Automatic proxy selection (WPAD)]]
[[File:Proxy-section-4.png|center|600px|Manual proxy settings (no authentication)]]
[[File:Proxy-section-5.png|center|600px|Manual proxy settings (with authentication)]]

For comparison, this is what the Gnome 3 proxy settings dialog looks like:

[[File:Gnome-3-proxy-settings.png|600px]]

== How To Test ==

* Proxy configuration can be done in three ways:

::: '''Explicit Proxy''' – A single proxy is specified in the browser with a literal proxy bypass list.
::: '''PAC File''' – The location of a PAC file is specified (e.g. hosted locally or on a web server) in the browser. The PAC file can provide proxy fail-over support, advanced proxy bypass support , and much more (see below).
::: '''WPAD''' – Only requiring a check box be selected in the browser, the browser may use DHCP or DNS in attempt to guess the location of the PAC file.

* Go to mysettings

[[File:testproxysupport-mysettings.png|400px]]

* Click network button

[[File:testproxysupport-network.png|400px]]

* Select mode of proxy ( automatic / manual )

[[File:testproxysupport-modeview.png|400px]]

[[File:testproxysupport-modeselector.png|400px]]

* Manual mode

[[File:testproxysupport-form.png|400px]]

===Automatic mode - WPAD===

==== Motive====
** To provide proxy-configuration, without needing the client-user to enter the location of proxy-configuration file herself.

* Benefits
** By not needing the client-user to manually specify the proxy-configuration file, every client-user is saved a headache :) Instead, all the configuration is done via a network-administrator, on the server-side.
** By delegating the responsibility of specifying every proxy-rule (even the proxy-configuration file) to the network-administrator, security is increased dramatically.

* Notes
** Setting this particular mode( (Automatic Proxy) is quite complicated; and many possibilities exist. '''However, the bottom-rule is, client should himself not need to specifiy the location of proxy-configuration file as per say'''.

* Testing (one of the possible ways :) )
** To verify that current dextrose-4 supports Auto-WPAD mode, we test using the method, as per the following 4 requirements, as listed at http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol#Requirements ::
***In order to use the DNS only method, a DNS entry is needed for a host named WPAD.
***The host at the WPAD address must be able to serve a Web page.
***In both cases, the Web server must be configured to serve the WPAD file with a MIME type of "application/x-ns-proxy-autoconfig".
***If the DNS method is used, a file named wpad.dat must be located in the WPAD Web site's root directory.

* Select "Automatic" mode in "My Settings" -> "Proxy" (without specifying anything else), and restart when prompted so.
:[[File:proxy1.png|640px]]

* The above step is all that is needed for "Automatic (WPAD)" mode to take effect; the WPAD-configuration-file will be located by the DHCP/DNS Server. However, for easy QA testing, we specify an easy way to replicate this DNS behavior ::

** Add the line "build.activitycentral.com wpad" to the file "/etc/hosts" on the XO, and reboot. '''It is repeated innumerable times, that this step is required just for easy testing; in actual deployments, the DNS-name resolution will be provided by network-administrators/School-Server-running-DHCPD'''
** Also, thanks a ton to '''Santiago Rodriguez (scollazo@activitycentral.com)''' for setting up the proxy-configuration-files at build.activitycentral.com.

* Open "Browse", and type in "www.google.com". You should be prompted for credentials (as is required by the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy2.png|640px]]

* Entering wrong credentials in the previous step, re-prompts :). This time, enter correct credentials.
:[[File:proxy3.png|640px]]

* The page opens successfully.
:[[File:proxy4.png|640px]]

* Next, type "www.facebook.com"; the "Access Denied" page is shown instantaneously, as per the rule in the WPAD-configuration-file at build.activitycentral.com
:[[File:proxy5.png|640px]]

=Automatic mode - WPAD=

[[File:testproxysupport-wpad.png|400px]]

[http://wiki.sugarlabs.org/go/Features/Automatic_Proxy_Settings#WPAD_-_Web_Proxy_Autodiscovery WPAD Web Proxy AutoDiscovery]

* Open Browse activity with a white-listed page ( google.com in this example )

[[File:testproxysupport-google.png|400px]]

* Open Browse activity with a black-listed page ( facebook.com in this example )

[[File:testproxysupport-facebook.png|400px]]

:: NOTE: The proxy setup will persist even if a user switches to Gnome Desktop, because the way it is setup, is the natural way gnome does too ( GCONF )

== User Experience ==

See [[#UI Design|UI Design]]

== Dependencies ==

There are no new dependencies.

== Contingency Plan ==

Users can continue to use the Gnome Control Center to configure proxy settings.

== Documentation ==

There is no documentation beyond this page.

== Release Notes ==

There have been no changes to public API. The Release Notes merely need to mention that users can now configure proxy settings from within Sugar. As detailed above, the UI is very similar to the Gnome UI.

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]

File:Proxy2.png

2013-01-25T16:20:26Z

Ajay Garg: