Android M Developer Course on Kickstarter

[BarryK]

I thought maybe some Puppy Forum readers might find this interesting:

https://www.kickstarter.com/projects/90 ... with-andro

I pledged 15 UK Pounds, but if the fund reaches 50,000 then I will get another course for free.

I had a play with installing the Oracle Java JDK and Android Studio (SDK) in Quirky 32-bit edition:

http://bkhome.org/news/?viewDetailed=00208

Android M is looking good:

https://www.androidpit.com/android-m-re ... tures-name

...the big problem though, is when it will eventually appear in phones. Maybe not until well into 2016, and there is always a problem of existing phones not getting upgraded, or taking ages to be upgraded.

[gcmartin]

Thanks @BarryK.

Many may already know of the course curriculums that has sprouted over past 4 years centered around understanding, use, integration, and development of mobile technologies in both High School and Universities across the world. This provides intellectual understanding to meet the current direction of the world. And certainly the business, engineering, and IT sections of these schools are moving to equip students for the movement in data and product futures.

There also was/is a free education over the Internet that was made available by several professors of noted Universities in 2014 spring-summer, for anyone with an interest.

I see the value of this for the world (and our) future need and use.

On the "M" comment you made
With the development "kits" available, you, the app builder, tells the kit which platform to build for. Thus, if its kitkat it will build a kitkat compatible app. If its Lollipop, it will build a Lollipop compatible app. etc. But, I'm sure you are already aware of this setting needed when using the kits for building.

[8Geee]

I would respectully ask Barry that when learning Android for the purposes of Puppy, that Android not 'phone-home' to google or its 3rd-party friends at any time. IMHO puppy must be independent of giga-corporates like google apple, microsoft, etc as a base. If a user wants things like chrome, or ie, or other programs, let it be by user choice. I'm sure some developers here would like to generally flavor the Andro-pup in generic, universal styles/platforms.

[gcmartin]

Hope, everyone/any looks at the Kickstart that is referenced in opening post of this thread BEFORE commenting so that it is clear on what this thread is trying to share.

Nothing is mentioned to change PUPPY's direction. What is being presented appears to merely announce the offering.

Further, in order to be able to satisfy the educational offering, Puppy needs a packaging so that the education requirement can be carried out. (Kinda like "you need pen and paper to do your homework")

There is a "Surging stream" about things that is counter to what is needed to support this education.

I, personally, don't see this thread as changing PUPPY Linux's structure in any way. Nor, do I see it leading to any change. Thus, EVERYTHING we have remains and continues to remain. Puppy services stays, security stays, performance stays, everything we know about Puppy stays!

Any subsystem to support the education requirement has NO impact or change on Puppy Linux or its advantages. In fact, it advances the kinds of things that PUPPY is known for.

For anyone wanting to discuss something other than education, or this kickstarter, see this thread where a packaging of the supporting subsystem is discussed..

Hope this is helpful.

[technosaurus]

If you find yourself stuck between a rock (app store requirements) and a hard place (open source licenses) you can run a native dialog to allow the user to select a location to get libraries.

For instance, you can build against QT libs but distribute only a helper lib with the same name similar to this post where I show how to have all binaries and libraries load from a remote location on first use (well, except those that are required for internet connection and downloading them)

Instead of using a repository you could use a native dialog to allow the user to either choose a directory where they already have the shared libraries to load (unlikely) or offer to download them (and optionally the sources) automatically to a default location. Since this whole thing happens in an __attribute__((constructor)) function, the shared library loading is delayed until the dialog is completed, so you shouldn't get load errors. Once this is done successfully you simply store their location for future use.

On the plus side you can develop multiple apps that use the same libraries from some default location and actually save your users some storage space and reduce memory usage if multiple apps are running.