Please note: We do not recommend that anyone other than developers and
testers download this Alpha 2 milestone release. It is intended for
testing purposes only.
Changes in this milestone that require feedback include:
* Links default to opening in new tabs, not new windows
* Close buttons now appear on every tab, and the close behaviour is
slightly different
* Inline spell checking in text boxes
* Automatic restoration of your browsing session if there is a crash
* Search suggestions now appear in the search box auto-complete for
Google and Yahoo!
* New search plugin manager for removing and re-ordering search
engines
* Improved support for previewing and subscribing to web feeds
* New Microsummaries feature
* New Add-Ons manager improves the user interface for managing
extensions and themes
* Updates to the extension system to provide enhanced security and to
allow for easier localization of extensions
* New search service that supports Sherlock and OpenSearch engines
* Support for SVG text using svg:textPath
The Bon Echo start page has also been changed to make it easier for
testers to provide feedback to the mozilla.feedback newsgroup.
Builds are available for testing here:
Windows (5.3 MB)
http://download.mozilla.org/?product=bonecho-alpha2&os=win&lang=en-US
Mac OS X (17 MB)
http://download.mozilla.org/?product=bonecho-alpha2&os=osx&lang=en-US
Linux (9 MB)
http://download.mozilla.org/?product=bonecho-alpha2&os=linux&lang=en-US
Testers should also be sure to read the Release Notes which have been
posted at:
http://www.mozilla.org/projects/bonecho/releases/2.0a2.html
Note: Please do not link directly to the download site. Instead we
strongly encourage you to link to this Bon Echo milestone announcement
so that everyone will know what this milestone is, what they should
expect, and who should be downloading to participate in testing at this
stage of development.
Enjoy!
---
Christopher Beard
Mozilla Corporation
cbe...@mozilla.com
650.903.0800 x201
650.903.0875
http://cbeard.typepad.com
No matter what browser I use to visit that URI, it says I've downloaded
or compiled Bon Echo Alpha 2.
Jeff
The JS in question is:
if (version == "BonEcho/2.0a1")
window.location='http://www.mozilla.org/projects/bonecho/index-2.0a1.html';
else
window.location='http://www.mozilla.org/projects/bonecho/index-2.0a2.html';
-Boris
According to bug 285848, it looks like the easier localization work
won't make 2.0. Has that changed?
No. Pretty sure this was an oversight.
-- Mike
I thought we had the localization stuff except for "managed locales"
(automatic fetching of late-breaking localizations for installed
extensions in the user's selected locales, etc.)....?
Mike
Robert
I wouldn't say "allow for easier localization of extensions". The thing
we have right now that wasn't possible before is that a localization of
an extension doesn't break if the extension gets updated and the
localization does not. *Iff* both the extension author and locale pack
author do the right thing with versions and dependencies.
That leads me to a question, I know that the extension compat for the
target application gets updated via amo, does that apply to
dependencies, too?
Which leads me to another question, for target app, do we support
distinct version ranges? I'd just try to add the target app more than
once, as multiple target apps imply an "or" for the different version
checks. For requires, I expect an "and" and thus I wouldn't know how to
depend on an extension 1.0-1.0.* and 2.0-2.0.*, but not on 1.5.
Mike, is
http://developer.mozilla.org/en/docs/Extension_Etiquette#Dependencies
still the statement we want in the extension ecosystem? Just came across
that while searching for deps docs.
Axel
> That leads me to a question, I know that the extension compat for the
> target application gets updated via amo, does that apply to
> dependencies, too?
A dependency *is* an add-on and uses the same update mechanism whether
it is with an add-on defined update rdf in the install.rdf or if one
isn't specified in the install.rdf it will use AMO... so, yes.
> Which leads me to another question, for target app, do we support
> distinct version ranges? I'd just try to add the target app more than
> once, as multiple target apps imply an "or" for the different version
> checks. For requires, I expect an "and" and thus I wouldn't know how
> to depend on an extension 1.0-1.0.* and 2.0-2.0.*, but not on 1.5.
No, version ranges are not supported yet for update. I wrote the
blocklist code to support ranges from the start but the update code will
need to be re-written which is more difficult due to it already being
used throughout the code.
> Mike, is
> http://developer.mozilla.org/en/docs/Extension_Etiquette#Dependencies
> still the statement we want in the extension ecosystem? Just came
> across that while searching for deps docs.
That sounds quite appropriate and I hope shaver agrees. I think it
should go without saying that this applies to people creating locale
packs for someone else's extension as well.
-Robert
I don't think we should discourage people from having dependencies on
other extensions. I would rather have someone depend on Greasemonkey
than ship a duplicate copy of it, especially now that we have real
dependency management and updating. And I hope that we have a bunch
of "library extensions" (webdav is one candidate, calendar another, a
beefed-up RDF possibly a third) to encourage use of shared, optional
code among different extensions with similiar needs.
So I would rather have that paragraph say something about being
careful to only express dependencies on things that are really
_required_, and work to dynamically detect optional stuff that you
might know how to work with. And encourage people to build deps
primarily on either their own factored sub-extensions or ones which
are hosted on AMO, for reliability of update and such.
Mike
I still think what you wrote is appropriate. I also think it is
appropriate for anyone creating a locale for someone else's extension to
contact the author and let them know before distributing the locale.
Robert
The first sentence is fine, but the second one is wrong: you shouldn't
always try to avoid dependencies on other extensions; in many cases
it'll be exactly the right thing to do. My "only express as
dependencies things that are _required_" point was aimed at people who
might add something to their extension that integrates optionally with
another extension, and that they should not add that as a <requires>
in the install.rdf.
> I still think what you wrote is appropriate. I also think it is
> appropriate for anyone creating a locale for someone else's extension to
> contact the author and let them know before distributing the locale.
There are a bunch of ways to go there, but I suspect that an extension
localizer will almost always want to be in contact with the extension
author for their own sake, and the cases that aren't caught in that
"almost always" can be handled one at a time. Hard cases make bad
law, and all that.
Mike
For that specific issue
http://wiki.mozilla.org/Extension_Manager:Extension_Dependencies#Item_Updates_.28future.29
Robert
Schrep