Skip to content
This repository has been archived by the owner on Jun 5, 2018. It is now read-only.

Migration on 1.4

Prototik edited this page Nov 15, 2012 · 2 revisions

Release 1.4 contains a lot of changes from 1.3.* It's page contains some recommendations for migration to the new version.

Change of package

The main difference - HoloEverywhere moved to a new package.
Previously, it was com.WazaBe.HoloEverywhere.
Now it's just org.holoeverywhere.

That is, if you previously used com.WazaBe.HoloEverywhere.app.AlertDialog, it is now necessary to fix imports to org.holoeverywhere.app.AlertDialog.

Remove .sherlock package

Yes, org.holoeverywhere.sherlock you can't find.

And as the same SActivity, SFragment and other amenities from ABS?

No, of course we are support ActionBarSherlock. Just now, you should use simple org.holoeverywhere.app.Activity and other classes without S- prefix in .app package.

I can't find FragmentActivity

Even org.holoeverywhere.app.Activity has the support of the fragments. You don't need use FragmentActivity for this.

ThemeManager always enabled

Earlier ThemeManager had even enable in static code block in Application class, that it somehow worked.
Now it's enabled by default.
To that, he became a little more friendly.
For example, you do not need to specify a hard theme in the manifest or elsewhere. If you forget to specify it, ThemeManager will do it for you!

Theme Holo.Theme.Sherlock removed

Also, theme names less .Sherlock postfix, use Holo.Theme, Holo.Theme.Light etc.

Addons

This project is in the testing phase and is not connected to the main project by default.
It is a port of the various third-party libraries for compatibility with HoloEverywhere.
Just clone the project to root of HoloEverywhere, import and connect the needed addons. git clone https://github.com/Prototik/HoloEverywhere-Addons.git addons