Just to throw in another suggestion (that I hope hasn't come up or been
implied so far):
The way I see it, the themes you visited/installed are part of your history,
so why not spruce up the history page and include visited themes there
directly, with "Theme" as a semantic annotation. In this way the user could
specify the search by himself ("themes I looked at last week" in some
suitable syntax), and/or filter out only links of a specific sort ("show
only themes"). This can of course be extended to other annotations, like
"News", etc. (Now how we can best come up with such an annotation is a
problem to be solved, e.g., annotate directly by domain visited, e.g., "
wsj.com" -> "News").
We can show a list of annotation keys as clickable links next to the search
box so that the user can select what type of history item is shown with a
single click.
In this way, "chrome://themes" needs just to be rewritten to
"chrome://history/#a=theme" or some such.
Further, links in the history can be rendered by showing a preview if the
item is a link to a theme (or - if that takes too much space - just with a
small marker "Theme" and rendered fully to the side on mouse-over).
- Roland
On Wed, Aug 12, 2009 at 1:41 PM, PhistucK <phist...@gmail.com> wrote:
> I have not read through the entire message, so forgive me if I am saying
> something unrelated and that was already answered here -It seems like
> there might be security issues with loading web resources in the internal
> pages, since internal pages seem to have a lot of power and privileges and
> the web is posed here as "unsafe and must be sandboxed through the whole
> way" (which is correct, of course). Combining the two may lead to
> unfortunate consequences.
> For the same reason, the "Tips & Recommendations" was pulled out.
> There is a command line switch called --enable-web-resources and, probably,
> just like the remote fonts feature (which is preventing Chrome from fully
> passing the ACID3 test, as far as I recall), that is behind a command line
> switch due to yet to be resolved security concerns.
>
> ☆PhistucK
>
>
>
> On Wed, Aug 12, 2009 at 07:08, Meok <meok...@gmail.com> wrote:
>
>>
>> I'm all in favor of Chromium using web interfaces instead of local
>> code. As I've said before in a thread on Chromium-Discuss, if Google
>> is creating a browser to maximize the potential of the web, and
>> encourage web developers to make more complex applications, then the
>> said Google browser should be leading the charge by embracing the web
>> as a platform. If you're going to invest so much in V8 to make AJAX
>> faster, why not use AJAX and an online interface to do many things for
>> the browser itself?
>>
>> I'm in favor of seeing Bookmarks and Themes presented in "Web-app"
>> format, running powerful Javascript on par with Gmail or Google Docs,
>> with effects as stunning as some of the ChromeExperiements. In other
>> words, show off what the browser can do, as well as promote the use of
>> the web as a platform.
>>
>> However, the reason I'm a little skeptical is that I'm afraid Google
>> may come under fire. How will the Theme Gallery know my most used
>> themes without authentication. If you make the theme gallery pull the
>> info from the browser history, you may be accused of violating privacy
>> rights, and if you force users to sign-in to the gallery to access the
>> feature, you make the process more tedious and if you use a Google
>> account, you risk looking monopolistic. Maybe I'm just being too
>> paranoid, and maybe you already have an ingenious programming
>> solution, but that was my motivation for suggesting the internal
>> page.
>>
>> On Aug 11, 9:23 pm, Peter Kasting <pkast...@google.com> wrote:
>> > On Tue, Aug 11, 2009 at 4:03 PM, Meok <meok...@gmail.com> wrote:
>> > > Just to add my two cents worth. Even though there is a full resource,
>> > > I still see a need for users to be able to keep their favorites easily
>> > > accessible. It;s the same philosophy of having a New Tab Page even
>> > > though you can pull back your most visited sites from the bookmarks.
>> >
>> > As we've already (sort of) said on this thread, it seems like having
>> your
>> > MRU themes is useful, but it's appropriate to do as an element of the
>> theme
>> > gallery itself, not as a separate local page.
>> >
>> > PK
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
