-
I'm sure this is already on everybody's radar (or would be soon anyways), but an interesting move from Google nonetheless. http://www.google.com/googlebooks/chrome/index.html Windows-only for now, and reportedly built on WebKit (the rendering engine used by Safari). Hopefully that means little-to-no additional debug time for our sites. Chris
-
Yeah, Iillustrated by Scott McCloud even! I saw it here yesterday: http://blogoscoped.com/google-chrome/ Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html -Andy On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: > I'm sure this is already on everybody's radar (or would be soon > anyways), but an interesting move from Google nonetheless. > > http://www.google.com/googlebooks/chrome/index.html > > Windows-only for now, and reportedly built on WebKit (the rendering > engine used by Safari). Hopefully that means little-to-no additional > debug time for our sites. > > Chris > > > -- > Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 > To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... > . Please contact topp-design-discussion-manager@... > for questions. >
-
Yeah, the illustrations are spectacular. It's incredible how well they communicate the concepts behind the product. Makes me want google chrome right now! On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: > Yeah, Iillustrated by Scott McCloud even! > I saw it here yesterday: http://blogoscoped.com/google-chrome/ > Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html > -Andy > > > On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: > >> I'm sure this is already on everybody's radar (or would be soon >> anyways), but an interesting move from Google nonetheless. >> >> http://www.google.com/googlebooks/chrome/index.html >> >> Windows-only for now, and reportedly built on WebKit (the rendering >> engine used by Safari). Hopefully that means little-to-no >> additional debug time for our sites. >> >> Chris >> >> >> -- >> Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >> To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... >> . Please contact topp-design-discussion- >> manager@... for questions. >> > -- Nick Grossman The Open Planning Project -- http://topp.openplans.org nickyg@... (917) 825-6590
-
I'd totally second that, seems like a brilliant way to introduce something new in an informative way, especially where they're trying to solve for some pretty complex issues. Unfortunately, it looks like they've pulled downloads for the beta from their site. I think it's supposed to be http://gears.google.com/chrome/ (though it's currently only for windows anyway). Aside from how cool it is that they're doing all this browser innovation with a modular open source model, I think it's really important how much this keeps the core idea of a web browser alive (and for use as "chrome" on standalone web apps) in the face of stuff like Adobe AIR. Considering all the re-engineering that has gone into the foundation of Chrome it looks like it'd have a better chance than the current state of something like Mozilla Prism. Nick Grossman wrote: > Yeah, the illustrations are spectacular. It's incredible how well > they communicate the concepts behind the product. Makes me want > google chrome right now! > > On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: >> Yeah, Iillustrated by Scott McCloud even! >> I saw it here yesterday: http://blogoscoped.com/google-chrome/ >> Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html >> -Andy >> >> >> On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: >> >>> I'm sure this is already on everybody's radar (or would be soon >>> anyways), but an interesting move from Google nonetheless. >>> >>> http://www.google.com/googlebooks/chrome/index.html >>> >>> Windows-only for now, and reportedly built on WebKit (the rendering >>> engine used by Safari). Hopefully that means little-to-no additional >>> debug time for our sites. >>> >>> Chris >>> >>> >>> -- >>> Archive: >>> http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >>> To unsubscribe send an email with subject "unsubscribe" to >>> topp-design-discussion@... >>> <mailto:topp-design-discussion@...>. Please contact >>> topp-design-discussion-manager@... >>> <mailto:topp-design-discussion-manager@...> for >>> questions. >>> >> > > -- > Nick Grossman > The Open Planning Project -- http://topp.openplans.org > nickyg@... <mailto:nickyg@...> > (917) 825-6590 > > >
-
Notably, we got our first support request about Xinha supporting Google Chrome today. On Sep 2, 2008, at 12:32 PM, Philip Ashlock wrote: > I'd totally second that, seems like a brilliant way to introduce > something new in an informative way, especially where they're trying > to solve for some pretty complex issues. > > Unfortunately, it looks like they've pulled downloads for the beta > from their site. I think it's supposed to be http://gears.google.com/chrome/ > (though it's currently only for windows anyway). > > Aside from how cool it is that they're doing all this browser > innovation with a modular open source model, I think it's really > important how much this keeps the core idea of a web browser alive > (and for use as "chrome" on standalone web apps) in the face of > stuff like Adobe AIR. Considering all the re-engineering that has > gone into the foundation of Chrome it looks like it'd have a better > chance than the current state of something like Mozilla Prism. > > > Nick Grossman wrote: >> >> Yeah, the illustrations are spectacular. It's incredible how well >> they communicate the concepts behind the product. Makes me want >> google chrome right now! >> >> On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: >>> Yeah, Iillustrated by Scott McCloud even! >>> I saw it here yesterday: http://blogoscoped.com/google-chrome/ >>> Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html >>> -Andy >>> >>> >>> On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: >>> >>>> I'm sure this is already on everybody's radar (or would be soon >>>> anyways), but an interesting move from Google nonetheless. >>>> >>>> http://www.google.com/googlebooks/chrome/index.html >>>> >>>> Windows-only for now, and reportedly built on WebKit (the >>>> rendering engine used by Safari). Hopefully that means little-to- >>>> no additional debug time for our sites. >>>> >>>> Chris >>>> >>>> >>>> -- >>>> Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >>>> To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... >>>> . Please contact topp-design-discussion-manager@... >>>> for questions. >>>> >>> >> >> -- >> Nick Grossman >> The Open Planning Project -- http://topp.openplans.org >> nickyg@... >> (917) 825-6590 >> >> >> -- Nick Grossman The Open Planning Project -- http://topp.openplans.org nickyg@... (917) 825-6590
-
Chrome is already getting dumped on… http://osnews.com/story/20244/Google_Chrome_Considered_Harmful/page1/ On Sep 2, 2008, at 6:16 PM, Nick Grossman wrote: > Notably, we got our first support request about Xinha supporting > Google Chrome today. > > On Sep 2, 2008, at 12:32 PM, Philip Ashlock wrote: >> I'd totally second that, seems like a brilliant way to introduce >> something new in an informative way, especially where they're >> trying to solve for some pretty complex issues. >> >> Unfortunately, it looks like they've pulled downloads for the beta >> from their site. I think it's supposed to be http://gears.google.com/chrome/ >> (though it's currently only for windows anyway). >> >> Aside from how cool it is that they're doing all this browser >> innovation with a modular open source model, I think it's really >> important how much this keeps the core idea of a web browser alive >> (and for use as "chrome" on standalone web apps) in the face of >> stuff like Adobe AIR. Considering all the re-engineering that has >> gone into the foundation of Chrome it looks like it'd have a better >> chance than the current state of something like Mozilla Prism. >> >> >> Nick Grossman wrote: >>> >>> Yeah, the illustrations are spectacular. It's incredible how well >>> they communicate the concepts behind the product. Makes me want >>> google chrome right now! >>> >>> On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: >>>> Yeah, Iillustrated by Scott McCloud even! >>>> I saw it here yesterday: http://blogoscoped.com/google-chrome/ >>>> Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html >>>> -Andy >>>> >>>> >>>> On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: >>>> >>>>> I'm sure this is already on everybody's radar (or would be soon >>>>> anyways), but an interesting move from Google nonetheless. >>>>> >>>>> http://www.google.com/googlebooks/chrome/index.html >>>>> >>>>> Windows-only for now, and reportedly built on WebKit (the >>>>> rendering engine used by Safari). Hopefully that means little-to- >>>>> no additional debug time for our sites. >>>>> >>>>> Chris >>>>> >>>>> >>>>> -- >>>>> Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >>>>> To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... >>>>> . Please contact topp-design-discussion-manager@... >>>>> for questions. >>>>> >>>> >>> >>> -- >>> Nick Grossman >>> The Open Planning Project -- http://topp.openplans.org >>> nickyg@... >>> (917) 825-6590 >>> >>> >>> > > -- > Nick Grossman > The Open Planning Project -- http://topp.openplans.org > nickyg@... > (917) 825-6590 > > >
-
Good writeup - my initial concern about testing another browser was offset by the discovery that Chrome was using WebKit. I didn't catch the panel about layout test regressions. If Google changed the renderer enough to start with only 23% of WebKit layout tests passing, that may mean we need to test against Chrome after all. I don't envy the jQuery / dojo / Prototype / Ext teams having to do the level of in-depth testing they'll need to make sure Chrome is supported. Any word from the Xinha team on support timeframe yet? Chris On Sep 4, 2008, at 8:58 AM, Andrew Cochran wrote: > Chrome is already getting dumped on… > http://osnews.com/story/20244/Google_Chrome_Considered_Harmful/page1/ > > > On Sep 2, 2008, at 6:16 PM, Nick Grossman wrote: > >> Notably, we got our first support request about Xinha supporting >> Google Chrome today. >> >> On Sep 2, 2008, at 12:32 PM, Philip Ashlock wrote: >>> I'd totally second that, seems like a brilliant way to introduce >>> something new in an informative way, especially where they're >>> trying to solve for some pretty complex issues. >>> >>> Unfortunately, it looks like they've pulled downloads for the beta >>> from their site. I think it's supposed to be http://gears.google.com/chrome/ >>> (though it's currently only for windows anyway). >>> >>> Aside from how cool it is that they're doing all this browser >>> innovation with a modular open source model, I think it's really >>> important how much this keeps the core idea of a web browser alive >>> (and for use as "chrome" on standalone web apps) in the face of >>> stuff like Adobe AIR. Considering all the re-engineering that has >>> gone into the foundation of Chrome it looks like it'd have a >>> better chance than the current state of something like Mozilla >>> Prism. >>> >>> >>> Nick Grossman wrote: >>>> >>>> Yeah, the illustrations are spectacular. It's incredible how >>>> well they communicate the concepts behind the product. Makes me >>>> want google chrome right now! >>>> >>>> On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: >>>>> Yeah, Iillustrated by Scott McCloud even! >>>>> I saw it here yesterday: http://blogoscoped.com/google-chrome/ >>>>> Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html >>>>> -Andy >>>>> >>>>> >>>>> On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: >>>>> >>>>>> I'm sure this is already on everybody's radar (or would be soon >>>>>> anyways), but an interesting move from Google nonetheless. >>>>>> >>>>>> http://www.google.com/googlebooks/chrome/index.html >>>>>> >>>>>> Windows-only for now, and reportedly built on WebKit (the >>>>>> rendering engine used by Safari). Hopefully that means little- >>>>>> to-no additional debug time for our sites. >>>>>> >>>>>> Chris >>>>>> >>>>>> >>>>>> -- >>>>>> Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >>>>>> To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... >>>>>> . Please contact topp-design-discussion-manager@... >>>>>> for questions. >>>>>> >>>>> >>>> >>>> -- >>>> Nick Grossman >>>> The Open Planning Project -- http://topp.openplans.org >>>> nickyg@... >>>> (917) 825-6590 >>>> >>>> >>>> >> >> -- >> Nick Grossman >> The Open Planning Project -- http://topp.openplans.org >> nickyg@... >> (917) 825-6590 >> >> >> >
-
I talked to the Xinha folks about it the other day -- the latest version, which we're apparently already using on Streetsblog, works OOB on Safari and Chrome. The older, hacked-together version on Openplans and LSN doesn't work on either. Doug will be upgrading everything in the coming weeks, so we should be all set. Nick On Sep 4, 2008, at 10:18 AM, Christopher Patterson wrote: > Good writeup - my initial concern about testing another browser was > offset by the discovery that Chrome was using WebKit. I didn't catch > the panel about layout test regressions. If Google changed the > renderer enough to start with only 23% of WebKit layout tests > passing, that may mean we need to test against Chrome after all. > > I don't envy the jQuery / dojo / Prototype / Ext teams having to do > the level of in-depth testing they'll need to make sure Chrome is > supported. Any word from the Xinha team on support timeframe yet? > > Chris > > > On Sep 4, 2008, at 8:58 AM, Andrew Cochran wrote: > >> Chrome is already getting dumped on… >> http://osnews.com/story/20244/Google_Chrome_Considered_Harmful/page1/ >> >> >> On Sep 2, 2008, at 6:16 PM, Nick Grossman wrote: >> >>> Notably, we got our first support request about Xinha supporting >>> Google Chrome today. >>> >>> On Sep 2, 2008, at 12:32 PM, Philip Ashlock wrote: >>>> I'd totally second that, seems like a brilliant way to introduce >>>> something new in an informative way, especially where they're >>>> trying to solve for some pretty complex issues. >>>> >>>> Unfortunately, it looks like they've pulled downloads for the >>>> beta from their site. I think it's supposed to be http://gears.google.com/chrome/ >>>> (though it's currently only for windows anyway). >>>> >>>> Aside from how cool it is that they're doing all this browser >>>> innovation with a modular open source model, I think it's really >>>> important how much this keeps the core idea of a web browser >>>> alive (and for use as "chrome" on standalone web apps) in the >>>> face of stuff like Adobe AIR. Considering all the re-engineering >>>> that has gone into the foundation of Chrome it looks like it'd >>>> have a better chance than the current state of something like >>>> Mozilla Prism. >>>> >>>> >>>> Nick Grossman wrote: >>>>> >>>>> Yeah, the illustrations are spectacular. It's incredible how >>>>> well they communicate the concepts behind the product. Makes me >>>>> want google chrome right now! >>>>> >>>>> On Sep 2, 2008, at 9:45 AM, Andrew Cochran wrote: >>>>>> Yeah, Iillustrated by Scott McCloud even! >>>>>> I saw it here yesterday: http://blogoscoped.com/google-chrome/ >>>>>> Screenshots: http://blogoscoped.com/archive/2008-09-02-n72.html >>>>>> -Andy >>>>>> >>>>>> >>>>>> On Sep 2, 2008, at 9:36 AM, Christopher Patterson wrote: >>>>>> >>>>>>> I'm sure this is already on everybody's radar (or would be >>>>>>> soon anyways), but an interesting move from Google nonetheless. >>>>>>> >>>>>>> http://www.google.com/googlebooks/chrome/index.html >>>>>>> >>>>>>> Windows-only for now, and reportedly built on WebKit (the >>>>>>> rendering engine used by Safari). Hopefully that means little- >>>>>>> to-no additional debug time for our sites. >>>>>>> >>>>>>> Chris >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220362591076 >>>>>>> To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... >>>>>>> . Please contact topp-design-discussion-manager@... >>>>>>> for questions. >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Nick Grossman >>>>> The Open Planning Project -- http://topp.openplans.org >>>>> nickyg@... >>>>> (917) 825-6590 >>>>> >>>>> >>>>> >>> >>> -- >>> Nick Grossman >>> The Open Planning Project -- http://topp.openplans.org >>> nickyg@... >>> (917) 825-6590 >>> >>> >>> >> > > > > -- > Archive: http://www.openplans.org/projects/topp-design/lists/topp-design-discussion/archive/2008/09/1220537924154 > To unsubscribe send an email with subject "unsubscribe" to topp-design-discussion@... > . Please contact topp-design-discussion-manager@... > for questions. > -- Nick Grossman The Open Planning Project -- http://topp.openplans.org nickyg@... (917) 825-6590
-
-
-
-
-
-
-
TOPP Design discussion
text.html (text/html) 1.4 kB