The End so short...

[Prototik]

Hey guys.
It's very sad, but as you can seen HoloEverywhere is reached for the end. End of development, end of using. This project was started with one small target - bring holo look & feel to old devices. For these years of development I can say that we reached this target. And... No more active users with Android 2.x is exists, total rate for old phones too small.
So... This project in EOL stage now, thanks everyone for supporting me, thanks for 2k stars, special thanks to @ChristopheVersieux, @BraisGabin! You're the best!

Prototik.

[4nd3250n]

Aaarrgh. It would be nice for a few loose ends to be sorted out.
But any way:
THANK YOU ALL FOR A GREAT JOB ! ! !

[itvdonsk]

Эх, спасибо за работу 👍
Хотя насчет старых телефонов спорно все-таки. Например у меня в одном приложении более 10% пользователей с 2.х. Придется все-таки их отбросить :(

[ChristopheVersieux]

Thank a lot to all of you.
This was a great adventure, my first in the open source, and it was great
to see people talking and using this project.

Sergey, thank a lot for taking the project and making it alive when I was
going to drop it!

Cheers!

On Tue, May 13, 2014 at 7:14 PM, Sergey Shatunov
[email protected]:

Hey guys.
It's very sad, but as you can seen HoloEverywhere is reached for the end.
End of development, end of using. This project was started with one small
target - bring holo look & feel to old devices. For these years of
development I can say that we reached this target. And... No more active
users with Android 2.x is exists, total rate for old phones too small.
So... This project in EOL stage now, thanks everyone for supporting me,
thanks for 2k stars, special thanks to @ChristopheVersieuxhttps://github.com/ChristopheVersieux,
@BraisGabin https://github.com/BraisGabin! You're the best!

Prototik.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/831
.

[Lakedaemon]

Thanks for this great piece of work. It really helped me and a lot of other people out there.

[BraisGabin]

Assist in this library has been a pleasure. @Prototik, thanks for trust me. I learned a lot of stuff reading your code. Great work!

[HenriqueRocha]

Thanks to everyone involved in this project. Thanks to @ChristopheVersieux for starting it, to @Prototik for maintaining it and for everyone that submitted pull requests with bug fixes.
Using HoloEverywhere in the AndroidPIT app resulted, IMHO, in a much better experience for the user, even with all the headaches that it sometimes gave me.
Android 2.2 is dead, 2.3 is also going to the grave soon and hopefully developers won't need to use this library anymore. I'm glad I was able to convince the product team of "my" app to use this library and I'm hoping that I'll contribute to your development projects someday, just like you contributed to mine. Thanks again @ChristopheVersieux and @Prototik for all the effort. Maybe I'll meet you someday in person and buy you a drink. Merci beaucoup and Большое спасибо.

[trietbui85]

I'm a freelancer for 3 years. From the second project, I started using HoloEverywhere because it makes app more beautiful and conform to Android design guideline. Perhaps my clients often have low quality (= not beautiful) projects, so when get started working with me and receive beautiful apps, they're very happy.
Because Android 2.x is about to dead, HoloEverywhere is also about to end. But, @ChristopheVersieux and @Prototik, thank you so much for your effort.

[lixikun]

thank you for your good job!!

[kkocel]

Hey, thanks for for Your heavy work!
I have only one question - Do Yo plan to release the very last final version from master? It would be nice because it fixes some serious bugs (eg. Sony Xperia layout bug)

[Prototik]

@kkocel okay, will released into couple hours.

[Prototik]

@kkocel ... or not. Plugin seems to be incompatible with latest gradle/android plugin version.

[ChristopheVersieux]

Wonder what a MaterialEverywhere could do... :-p

[Prototik]

@ChristopheVersieux yep, one my friend already suggest me this idea :D

[BraisGabin]

I suppose that I was not the only one thinking about it.

[ChristopheVersieux]

I have already rewritten one of my app with the Material theme, and ported
it back to older version (mainly default ActionBar color, and some
typography)
I am convinced a pretty neat theme can be created.

But keep in mind, that like Holo, our theme should not be used "as is" (I
am totally bored with 100% Holo and pure card layout) and other developers
should bring their own branding.

I also don't think that trying to emulate elevation and motion is a great
idea, as the performance ill be poor.

As a conclusion, I strongly believe something can be done easily to bring a
basic but still "better than holo" working Material theme.

MaterialEverywhere?
MaterialCompat?

On Sat, Jun 28, 2014 at 5:49 PM, Brais Gabín [email protected]
wrote:

I suppose that I was not the only one thinking about it.

—
Reply to this email directly or view it on GitHub
#831 (comment)
.

[HenriqueRocha]

Material is supposed to work in Android 4.0+ but without all those neat
shadow effects? I think I saw that in a Google I/O presentation.
IHMO, no effort should be made to support Android 2.x anymore.

On Sat, Jun 28, 2014 at 6:17 PM, Christophe Versieux <
[email protected]> wrote:

I have already rewritten one of my app with the Material theme, and ported
it back to older version (mainly default ActionBar color, and some
typography)
I am convinced a pretty neat theme can be created.

But keep in mind, that like Holo, our theme should not be used "as is" (I
am totally bored with 100% Holo and pure card layout) and other developers
should bring their own branding.

I also don't think that trying to emulate elevation and motion is a great
idea, as the performance ill be poor.

As a conclusion, I strongly believe something can be done easily to bring
a
basic but still "better than holo" working Material theme.

MaterialEverywhere?
MaterialCompat?

On Sat, Jun 28, 2014 at 5:49 PM, Brais Gabín [email protected]
wrote:

I suppose that I was not the only one thinking about it.

—
Reply to this email directly or view it on GitHub
<
https://github.com/Prototik/HoloEverywhere/issues/831#issuecomment-47430868>

.

—
Reply to this email directly or view it on GitHub
#831 (comment)
.

Henrique Rocha
Lead Android Developer @ AndroidPIT.de

[ChristopheVersieux]

I don't think it will be backported.
From here : https://developer.android.com/preview/material/theme.html
Note: The material theme is only available in the Android L Developer
Preview. For more information, see Compatibility
https://developer.android.com/preview/material/compatibility.html.

And the link :
The material theme is only available in the Android L Developer Preview. To
configure your app to use the material theme on devices running the Android
L Developer Preview and an older theme on devices running earlier versions
of Android:

Define a theme that inherits from an older theme (like Holo)
in res/values/styles.xml.Define a theme with the same name that inherits
from the material theme in res/values-v21/styles.xml.Set this theme as your
app's theme in the manifest file.

Note: If you do not provide an alternative theme in this manner, your app
will not run on earlier versions of Android

By the way, I totaly agree : let's forget 2.x and focus on API 14
#holoyolo
On Jun 28, 2014 7:24 PM, "Henrique Rocha" [email protected] wrote:

Material is supposed to work in Android 4.0+ but without all those neat
shadow effects? I think I saw that in a Google I/O presentation.
IHMO, no effort should be made to support Android 2.x anymore.

On Sat, Jun 28, 2014 at 6:17 PM, Christophe Versieux <
[email protected]> wrote:

I have already rewritten one of my app with the Material theme, and
ported
it back to older version (mainly default ActionBar color, and some
typography)
I am convinced a pretty neat theme can be created.

But keep in mind, that like Holo, our theme should not be used "as is"
(I
am totally bored with 100% Holo and pure card layout) and other
developers
should bring their own branding.

I also don't think that trying to emulate elevation and motion is a
great
idea, as the performance ill be poor.

As a conclusion, I strongly believe something can be done easily to
bring
a
basic but still "better than holo" working Material theme.

MaterialEverywhere?
MaterialCompat?

On Sat, Jun 28, 2014 at 5:49 PM, Brais Gabín [email protected]
wrote:

I suppose that I was not the only one thinking about it.

—
Reply to this email directly or view it on GitHub
<

https://github.com/Prototik/HoloEverywhere/issues/831#issuecomment-47430868>

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/Prototik/HoloEverywhere/issues/831#issuecomment-47431628>

.

Henrique Rocha
Lead Android Developer @ AndroidPIT.de

—
Reply to this email directly or view it on GitHub
#831 (comment)
.

[Prototik]

MaterialEverywhere sounds cool - let's keep brand! :)
I have plans to provide some compability support for custom inflaters for layouts/drawables and also backport shadow effects, but I'll begin work only after final L release. And I need to go to university for now, so not too much time available for work for me. But it's great idea and I really need to realize it.

And yeah... Fuck 2.x!

[ChristopheVersieux]

Good luck at the university.

I will maybe start something before official L if I got free time.
The only thing I would like to avoid is to override Activity or Fragment
and keep an XML only approach to avoid messing with system.
Let's see what we can do..
On Jun 28, 2014 7:40 PM, "Sergey Shatunov" [email protected] wrote:

MaterialEverywhere sounds cool - let's keep brand! :)
I have plans to provide some compability support for custom inflaters for
layouts/drawables and also backport shadow effects, but I'll begin work
only after final L release. And I need to go to university for now, so not
too much time available for work for me. But it's great idea and I really
need to realize it.

And yeah... Fuck 2.x!

—
Reply to this email directly or view it on GitHub
#831 (comment)
.

[Lakedaemon]

Is there a way to make the Holoeverywhere plugin work with gradle plugin
0.10, 0.11, 0.12 ?

I would still like to be able to use holoeverywhere a little while with
intellij idea with target 19
Because Material phones aren't going to be available and to represent a
significant % for a while yet
And in the mean time, we are stuck with 4.0/4.1/4.2....

I can still compile it with intellij idea 13.1 and gradle 0.9 in the
worst case

On 06/28/2014 08:02 PM, Christophe Versieux wrote:

Good luck at the university.

I will maybe start something before official L if I got free time.
The only thing I would like to avoid is to override Activity or Fragment
and keep an XML only approach to avoid messing with system.
Let's see what we can do..
On Jun 28, 2014 7:40 PM, "Sergey Shatunov" [email protected]
wrote:

MaterialEverywhere sounds cool - let's keep brand! :)
I have plans to provide some compability support for custom
inflaters for
layouts/drawables and also backport shadow effects, but I'll begin work
only after final L release. And I need to go to university for now,
so not
too much time available for work for me. But it's great idea and I
really
need to realize it.

And yeah... Fuck 2.x!

—
Reply to this email directly or view it on GitHub

#831 (comment)
.

—
Reply to this email directly or view it on GitHub
#831 (comment).

[BraisGabin]

Support API 14 is senseless. https://developer.android.com/about/dashboards/index.html

I think that API 15 is the best choice.

[HenriqueRocha]

I think even 15 is not worth it because it has less user base than 2.3
(12.3% vs 14.9% respectively) and by the time Android L is released
officially the % will probably be lower than 10%.

On Sun, Jun 29, 2014 at 1:21 PM, Brais Gabín [email protected]
wrote:

Support API 14 is senseless.
https://developer.android.com/about/dashboards/index.html

I think that API 15 is the best choice.

—
Reply to this email directly or view it on GitHub
#831 (comment)
.

Henrique Rocha
Lead Android Developer @ AndroidPIT.de

[BraisGabin]

True. But this is a backport library. 27% seems too much.

[ChristopheVersieux]

I guess it's a matter of days before we can learn if Google will improve their compatibility library or if a new community based project is needed. Just in case, here are some links that might be relevant, just in case... (Will update if necessary)

https://plus.google.com/b/108315424589085456181/+RubenGerits/posts/fcbS9pLR6oP

https://gist.github.com/homj/f456dede83cb34a9e997

[Prototik]

@ChristopheVersieux good links, thanks :)

Anyway I have some plans about MaterialEverywhere, it will not a fat library as HE. I have some interest concept for now, it's awesome for me :)

[ChristopheVersieux]

Just wanted to share this awesome lib:
https://github.com/traex/RippleEffect

[BraisGabin]

Google will release a "Material support library": https://plus.google.com/103829716466878605055/posts/gmAV3n2wmXs

[kkocel]

What the didn't is support for VectorDrawable and AnimatedVectorDrawable

[Prototik]

@kkocel we will support new drawables. Plus optional drawable inflater module.

[kkocel]

@Prototik Any work in progress? Is there any project opened for it? Maybe we could contribute ;)

[Prototik]

@kkocel that's secret ;) Soon I'll publish sources and setup repositories. Then community (and I) can develop modules for library.

[ChristopheVersieux]

Just in case you didn't know yet: https://github.com/antoniolg/MaterialEverywhere