That's very likely. Since then the "chrome" module has been
refactored into "content" and "chrome".
Adam
> On Mar 11, 8:21 pm, Mike West <mk...@chromium.org> wrote:
>> The sidebar API was removed inhttp://crrev.com/116901
>>
>> http://commondatastorage.googleapis.com/chromium-browser-continuous/i...
>> looks like the most recent Linux build with the API. That should be a
>> good start for your experimentations. I wouldn't recommend running it
>> as your main browser though, for a variety of reasons
>>
>> -mike
>>
>> On Mar 10, 6:40 pm, trappedIntoCode <trapped.into.c...@gmail.com>
>> wrote:
>>
>>
>>
>>
>>
>>
>>
>> > Hello. I want to checkout the chromium source revision with dropped
>> > experimental sidebar api.
>>
>> > Can I get the last revision no from somewhere, before the code was
>> > removed?
>
> --
> You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.
> For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
>
If you're not planning to contribute your patch back to trunk, there's
no need to worry about such things, of course.
Adam
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.
It's hard to find folks who've become successful members of the
community by starting out implementing a big new feature. Folks tend
to be more successful when they start by fixing bugs, becoming
familiar with the codebase and the community, and then start to
understand/influence the direction of the project.
For sidebars, in particular, my understanding is that we removed them
from the product because we neither liked the way the code was written
nor the user experience of sidebars themselves. From the starting
point, it unlikely that the project would accept a new sidebar
implementation without both significant changes in the implementation
and the user experience.
Adam
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.