--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wow! You should ask for your money back...
I suppose kivy or open source is not suited for everyone. If you find you want the immediate personal support, perhaps you should use something where you could pay for professional support, like qt. But clearly kivy works for many people, so it's just a matter of finding the right toolkit that works for you.I'm sorry you feel this way, and I understand that it can be quite frustrating when things are not working, but you have to consider that we are a small group of developers who volunteer for this project who have to support many platforms. What this means is that like any open source software, when things go wrong you need to be prepared to spend some time either fixing things yourself or with us to figure out what is going wrong. I would love it if we had an AI that can track down issues and possibly fix it, but unfortunately currently we need to do this manually, which means that we can only help users when we have free time and if they are willing to engage with us until we can figure out what is wrong.Generally, the missing window provider happens when you're missing a dependency, when there's a dependency clash e.g. if you use kivy in an unsupported python distribution and there's some binary clash, or if there's a graphics issue and you don't have a supported g driver. That's is why you see many posts in google because that error tends to be a catch all when something goes wrong. Also, kivy does have minimum requirements for graphics drivers. But it is hard to debug without a trace and more info.
On Tue, Jul 18, 2017 at 10:48 PM, Mark Melvin <mark....@gmail.com> wrote:
Wow! You should ask for your money back...Maybe if you post an error message and example, someone can try to help you (although I doubt anyone has much motivation to spend their time on it after that post).
On Tue, Jul 18, 2017 at 10:34 PM, Gregory Strydom <gregory.s...@gmail.com> wrote:
I am so sick and tired of Kivy's crap. Why does this have to be so difficult? The setup i had was working. Now i try run the file and i get the crappy message, Unable to get a window, abort. WHAT THE HELL?!!! I've changed nothing!!! Altered nothing!!! IT was working!!! Now its not!! Nothing has updated or been changed!! WTF!!!???!!!???And this is not the first time!!! I'm sick and tired of this crap!!! Kivy has got to be the the worst library/framework i've ever worked with!! Period. Never have I battled so much to get something so simple working!! WTF!!!???!!!After how many years and they still cant get this sorted? But they are quick to implement new features, but cant fix the old ones? What a joke. I've worked with kivy for awhile, and am always getting this problem, but try to persevere. Now im thinking, what for? When there is so much BETTER available. Just look at Google. Countless posts with the same problem. Unbelievable.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+unsubscribe@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
To post to this group, send email to kivy-...@googlegroups.com.
Visit this group at https://groups.google.com/group/kivy-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/7ade1212-a922-4499-972d-b2f1658bf6b7%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
To post to this group, send email to kivy-...@googlegroups.com.
Visit this group at https://groups.google.com/group/kivy-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/b9246dc3-a139-4290-ab19-f334f46c68f7%40googlegroups.com.
If you are going to invest a lot of time as a developer to learn a new framework you should be sure you are not waisting it away. Maybe spend it learning other frameworks. Installation of kivy is a major problem. Spending so much time installing and troubleshooting instead of learning to develop apps, will make you only an expert in installing Kivy.
I am fine with a installation that will say this is only tested on these operating systems with following version, anything else is maybe possible.
What happens in the future? Does this gets worse? I have one machine where I somehow setup Kivy development environment. Should I continue learning Kivy? Should I not waste any more time because this looks risky and unstable.
Community is always important for these kind of projects. Just give us one way of installation and one linux distribution where we know it will work every time and there will be more people building the community. Who knows how many developers came and left because installation made them rethink the stability and reliability.
Make a page where community can contribute by making detailed instructions on how to install on specific OS. Anything that bring back conference that this is worth your while.
Firstly I believe Kivy and particularly p4a are wonderful
achievements, porting Python to non-POSIX systems is remarkable. That
said there are issues withe the Android/ios tools , particularly for new
users; and if new users don't get it there wont be a user base.
One could say this is a p4a/buildozer issue not a Kivy issue, but it
seems that most people here are using Kivy because of the path the
phones.(There are other desktop alternatives)
1) I get that p4a is a work in progress, but the lack of usable version control means the user experience is like building a sand castle at the beach - every so often a wave comes in and you have to rebuild something. This experience alone is enough to generate the s-word in the title if you try to rebuild a project after 6 months.
2) Documentation is obsolete. One of the most viewed posts in the
user group lists the current (12/2018) Ubuntu dependencies for p4a. (It
took me a week, and many Ubuntu installs, to reverse engineer). Current dependencies not documented ?! really ?
3) Testing is woefully inadequate. I tried to build all the 'requirements' earlier this year - initially about 1/3 built - after some work with the developers that increased to about 2/3. Clearly there is inadequate regression testing, they should all build. (Of course the build dependencies were not documented.)
4) Buildozer tries to address the issues with abstraction, great if it always works, but it doesn't. The user is left with error messages from buried tools which are not understood - abstraction fails.
5) The core issue is that p4a/buildozer is a tool builder experience, not a tool user experience.
Suggestion:
The architecture of p4a/buildozer is a cause of the 'moving target', and 'multiple environment' problems. So do less.
Do this: python-for-android should be renamed python-for-android-dev;
a new python-for-android would include nothing that requires
build-tools (just Gradle to link the user files?), so just Python, Java,
and Linux object files. The new version would support fixed (latest?)
SDK and NDK versions ONLY. The user experience becomes running a tool,
rather than building a tool. So no longer a "-dev" experience.
Wake up! The howl here is real, look at the number of views on this thread. Fix the issues or never leave the early adopter phase, the destiny of this project will become the land of the living dead.
I get that people are working hard, and that there are limited resources; but perhaps some of that effort is misplaced?
Thank you for your attention.
Let's retire this thread... the title is offensive. Kivy is the
product of a volunteer team, delivering a great product.
Clearly there are a number of issues around Android.
There are a set of constructive comments below, how do we get to
an action plan?
Suggestion:
Start an new thread, Kivy-Android get well plan. (I would do
this but I don't develop for Android.)
Kick off a discussion on the discord server building support
for the idea of building a get well plan.
Establish a set of actions, and engage broader community
participation in the get well plan.
Execute
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
To post to this group, send email to kivy-...@googlegroups.com.
Visit this group at https://groups.google.com/group/kivy-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/06e4a30f-5bc1-4b55-b5f5-f16a564061df%40googlegroups.com.
Let's retire this thread... the title is offensive.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-...@googlegroups.com.
What would be best for Kivy is that the developer post what is required to build an android APK (step-by-step) and versions of the required stuff. Because currently, following the available guide does not help.