On Tue, Nov 10, 2009 at 3:21 PM, Nebojša Ćirić <c...@google.com> wrote:
>> > One minor thing you left out was getURL providing a way to generate a
>> > localized URL (ideally without stats). If we don't provide devs a way
>> > to
>> > construct URLs manually, then they won't have a good migration path for
>> > when
>> > we do implement localized resource fetching.
>>
>> One thing is that odd is that if we don't do fallback for getURL(), it
>> will be inconsistent. The manifest and getMessage() API will localize
>> using fallback, but getURL() won't.
>
> We could let them build resource URL in the message catalog and get it using
> getMessage.
> JavaScript:
> ...
> getURL(chrome.i18n.getMessage("some_resource"));
> ...
> _locales/en/messages.json:
> ...
> "some_resource" : "_locales/en/some_resource.jpg"
> ...
> This approach would solve fallback problem too, since we would check all
> sublocales, without stating files. Developer would have to make sure the
> file actually exists.
Yeah, I would rather something like this.
Erik, I don't understand why you say this has no forward migration
path. Wouldn't it just keep working if we introduced more clever APIs
that automate more of this?
At that point, the developer could choose to use the new APIs or keep
doing it the old way.
- a
--
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to chromium-extensi...@googlegroups.com.
To unsubscribe from this group, send email to
chromium-extensions+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=.
