Written by vgregorio the 4 Dec 12 at 23:02.

Since the lenses are connected to the dash, it would be interesting to access this settings screen along with the access to the lens.

This screen should have the option of adding lenses (a brief description of what the lens does, along with image), enable / disable a lens already installed, configure the behavior of the lens.

The option of adding lenses could be connected to a repository of lenses fed by the community. There are a series of lenses designed by users who would benefit from official exposure on a system screen like this. Just add the PPA and perform the installation of the lens!

Since the lenses are connected to the dash, it would be interesting to access this settings screen along with the access to the lens. This screen should have the option of adding lenses (a brief description of what the lens does, along with image), enable / disable a lens already installed, configure the behavior of the lens. The option of adding lenses could be connected to a repository of lenses fed by the community. There are a series of lenses designed by users who would benefit from official exposure on a system screen like this. Just add the PPA and perform the installation of the lens!

Written by GizmoChicken the 1 Jan 13 at 08:38.

Depending on what is meant by "configure" as used in the original rationale post, one could argue that a lens must be "configured" (or reconfigured) each time that it is used. For example, on each use, one may "configure" the "Search Applications" lens such that "See ## more results" is selected and/or the "filter" panel is exposed.

So as to reduce the need for reconfiguring a lens to a preferred configuration upon each use, I suggest that, at the very least, dash should remember the configuration of the lens as last used and then present that last used configuration upon next use (so that a user wouldn't have to reconfigure the lens each time it is used).

Depending on what is meant by "configure" as used in the original rationale post, one could argue that a lens must be "configured" (or reconfigured) each time that it is used. For example, on each use, one may "configure" the "Search Applications" lens such that "See ## more results" is selected and/or the "filter" panel is exposed. So as to reduce the need for reconfiguring a lens to a preferred configuration upon each use, I suggest that, at the very least, dash should remember the configuration of the lens as last used and then present that last used configuration upon next use (so that a user wouldn't have to reconfigure the lens each time it is used).