I wanted to host a online kitchen(s) for the community. After some diligent research, I cannot find any scripts or server side software, etc. for this purpose.
I have written code for android in the past, and am familiar with git and java, as well as the Android SDK, so I am not new to this. In addition I have no concerns about hosting, or other needs, as I have way more facilities than I need to do so.... (In my personal Lab/Datacenter, among other very cool and overpowered toys, I have a 42U rack full of gear, a pair of HP BladeCenters with 16 Blades each, and plenty of bandwidth all to myself.) The environment is mostly ESX 4 and scalable which makes projects like this both fun and easy.
My hope was that someone here can point me in the direction of how or where to obtain the base scripts/software/files necessary to put together an online kitchen. I am happy to contribute my time assisting in testing and developing should it be necessary.
If I am successful in doing so, and I find it does not tax my resources after some testing, I would have no issues hosting for free for other Devs as well, if they are interested.
Hopefully someone can point me in the right direction.
(Forgive me in advance if this is information that is already available, I did search both XDA and Google first, before I posted this question.)
Bump!
Anyone have any answers?
10charisticcharacters
It really shouldn't be too hard to take the bash scripts used in some of the existing kitchens and create a web based front end to call them using php on a linux server. I have done similar things in the past. which distro is your server running? I would be willing to help you put something together if your willing to host it for everybody.
This is a pretty interesting idea. We would have to do some planning and figure out exactly what features should be in an online kitchen vs a standalone. Do we want to store a set of base roms to modify, or do users of the kitchen always upload the rom they are modifying, do we simply force a download of the modified rom, save it on the site, seed a torrent, etc?
I'll try to cook up a very simple example, and then we could always build on it.
http://forum.xda-developers.com/showthread.php?t=722405
Seems the OP has done this already. Maybe he will be so kind as to assist.
DieHappy, PM me pls.
Related
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
I cannot agree more. Learning the in's and out's of the Android framework will benefit newcomers SIGNIFICANTLY.
Building ROMs is easy, fixing bugs and adding new functionality is the fun stuff, and having a solid understanding of the Android framework helps with this. The best way to learn is to pick up the Android SDK and whip up some apps, there are great tutorials out there.
Awesome information! It is good to see I have been reading the right literature... There are also a few that I missed... Thanks again for the links!
cyanogen said:
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse
I completely agree. But it's cyan saying it, who wouldn't
I am ok with "chef" terms because they were born on XDA, which makes them kinda cool, but I agree that the file-pusher mentality/stereotype is quite derogatory.
I hope this section goes places.
P.S. Hearing a diehard android dev like you (cyanogen) say that you are biased against sense really made me think about how good plain old android really is... so clean and functional. Good stuff bro.
very nice thanks for the info was looking into this...now to fill the brain.
Weird how this is exactly what i was looking for. Time to read. Thank you cyanogen.
I'm with Cyanogen on the bias against pre-built, proprietary code blobs. Even the non-free, basic parts to get AOSP to build for dream give me the hivie-jivies, mostly because the reason we're in such a pit now with further versions of Android is because we have no source to maintain working basic functionality (yeah, video in a device capable of recording/playback is basic).
I'll try to work a couple basic tutorials based on my rom-building exploits covering things from getting android built from source, to actual troubleshooting possible problems, to having a hand at modifying the source so you can make the built your own. I really want to see somebody come up with a real custom rom on the android part of the OS and leave the linux part rest for a while.
Oh man! PDK! Never seen it! Thanks a lot
Great job
As always, my hat is off to you Cyanogen. This is exactly what i was looking for. Once again thanks for your hard work and dedication to the project.
This is awesome. I am going to be learning this stuff over summer. But there seems to be a gap of information between learning the android stuff, and learning the linux stuff.
Hi do you know some guides online to build Overclocked Kernels ???
PDK website
Odd that the PDK website does not function. Anyone know who owns it?
mistere372002 said:
Odd that the PDK website does not function. Anyone know who owns it?
Click to expand...
Click to collapse
Works fine for me. What issues are you having?
I guess I'll be the first in the thread to ask the extreme newbie questions.
Are the links in the OP in a particular reading order, or is there a recommended order?
Since the entirety of my programming experience is some simple VB type stuff, will I be able to learn from the ground up via those links, or will it be more like trying to figure out the words in a Chinese book with no knowledge of the language?
At one point I had managed to cobble together a web front end on my Droid for wowhead.com (all it did was bring up a screen with a search box, which would then pop open the browser with the results of whatever you searched for), but to say I had a firm grasp of what I was doing in my tinkering would be a gross overstatement.
cyanogen said:
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Click to expand...
Click to collapse
So, firstly thanks for the websites. Personally, I already knew about most of those. But that is beside the point right now.
Why would someone want to learn how to program anything when they are just building a rom? I just don't understand what is wrong with someone only tweaking and slimming a rom down. What point would it be for a website like this to make everybody just go out and learn on their own EVERYTHING, and then what would this site be for? Posting only in the development forums? This is a support website. Plain and simple. Who cares if someone asks a question? If they searched and couldn't find something, let it go.
In your same thought process, very FEW WM chefs could call themselves chefs. And before you ask yes, I could call myself a chef because I have written quite a few apps to assist in building a rom or actual tool for WM. Maybe not the best chef, but one nonetheless.
I just think this is basically discouragement of any new developers/chefs from posting something in fear of being chastised. I am absolutely still learning android. If it wasn't for the people of SDX, particularily joeykrim, I wouldn't be so close to a final product of my Android kitchen.
This being said, maybe I am just full of crap and the only one that will go against your POV. Mainly because I am not afraid to state my opinion. And this POV is wide across the forum and this is why I don't contribute much here anymore
cyanogen said:
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse
Thank you.
cyanogen said:
I really dislike the "chef" moniker when it comes to Android, since we are more of an open-source community. I think it implies a "file pusher" mentality. But then again, I am biased against proprietary versions of Android like Sense, so feel free to disregard all of this.
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse
Thanks for your support/advice,
I'm trying to understand all the stuff in order to create a new ROM for Tattoo from 0, and I will take your info in order to. Crate this ROM and make a step by step manual to help people to understand how to modify their Tattoo's. I will like to see this cooperative knoledge share for this phone. As more peoople understands all this stuff, and all this work done by the comunity, more people will join and share to have better phones every day.
Tanks
java version
hi all,
Working 100%. Thanks for this great work. Now runing this 2.6.34 kernel on tattoo. Just now ajusting the kernel configuration.
Cheers
great advice
Cyanogen
Thanks for your support & advice
Time to start reading....
trying to understand all that is needed ==
TO BE A DEVELOPER..
IF ANY BODY HAS MORE INFO OR VIDEOS ..
PLEASE POST
----------------------------------
Currently own a Sprint EVO 4g > and plan on making great things for it..
Cyanogen you are so damned right. Building a Rom should implicitly mean that you know git, Android, dev and... read api and docs
I'm thinking about dsixda Rom kitchen.
I use its scripts to unpack kernel and zip everything, but largely customized the scripts and added some. In fact I love shell scripts.
I just wish you could also post a link to a toolchain tutorial for those willing to compile binaries from sources on x86 for an ARM architecture. And also to add shared libraries.
Have a nice day.
Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Whosdaman said:
Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Click to expand...
Click to collapse
Here are some links to get you started. There's a lot of stuff to learn, so my best advice is to be patience and lurk, read, and learn. I know nothing about your particular device, but much of this will apply.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
http://forum.xda-developers.com/showthread.php?t=633246
http://blog.coralic.nl/2010/01/28/build-eclair-aka-android-2-1-for-hero-from-source/
http://forum.xda-developers.com/showthread.php?t=622916
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
http://www.kandroid.org/android_pdk/index.html
http://android-dls.com/wiki/index.php?title=Main_Page
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=641223
http://adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://forum.xda-developers.com/showthread.php?t=623976
http://lukasz.szmit.eu/2009/12/making-your-own-rooted-android-rom.html
http://groups.google.com/group/android-kernel
http://groups.google.com/group/android-building
http://groups.google.com/group/android-porting
http://groups.google.com/group/android-developers
http://groups.google.com/group/android-ndk
http://groups.google.com/group/android-platform
Look for the sticky thread by Cyanogen in this forum called "some advice". Are you looking to build roms from source, or just modify existing roms?
Do you know any Java or C?
Building roms may seem fun, but it takes research and patience. Lurking github commits, textbooks, and the forums is a great start. The community is very eager to help, and that's one of my favorite parts about android. But deving shouldn't be as simple as copy paste. Where's the fun in that?
I understand where you're coming from though, I was the same way a few months ago. Built a rom from source, posted it, then realized how uninformed I was.
I am now improving my skillz by reading textbooks on Java ("Head First Java") and C ("The C Programming Language"), both available as pdf documents. I'm mucking around in kernels and am going to start writing apps as well. Its a good place to learn the framework. You could also get into theming, but that requires a little graphic design know-how.
Good luck man, and have fun with it
Sent from my Nexus One using XDA App
Me too would like to learn more about creating ROMs for android (Galaxy S I9000 here)
I do have java experience (quite a lot, actually) but I really have no idea where to start when creating a ROM
thanks
Did you ever get a kitchen going?
So, I've been a member for a while, and I've done my fair share of using everyone elses ROMs on my phones, starting from HeroC, to Moment, to Epic, to OG Evo, then on to TMo phones like the MT4G and Nexus S.
Now that I'm back on Sprint and rocking this beast of an Evo 3D, I'd like to actually CONTRIBUTE to the community. I give you Dev's/Chefs mad respect for what you do, and I'd like to be a part of that as well.
So, here's the actual questions for this Q&A thread: Is there any special programming knowledge I need to start cooking roms, or starting to dev? Do I need to know code? Do I need to be fearless with my own device? (lol) Is there a *For Dummies*-ish site/thread/forum that would be a good idea to read up on?
I realize that there are probably a million threads like this, spread all over the interwebz and these are PROBABLY some "OMG NOOB SEARCH" questions, but in my opinion the best place to go for information is directly from the source
Believe or not...the best source of info IS searching...not us...learn the basics...adb, java, XML, start small...learn Linux and learn, learn, learn....all great developers and chefs...are self taught...because what you learn on your own...you learn to ask questions to yourself,,,for yourself...it is either in you or not..a passion for knowledge in programming and or modifications of system cannot be taught for the drive..because if you search first and learn by doing with the tutorials...then and only then can you ask the right questions..
^^^ I've never seen so many ellipses. :s
@OP Yeah, I'm trying to do the same thing. I've picked up a book at B&N titled "Android Apps for Absolute Beginners", by Wallace Jackson. It's pretty up-to-date, and includes Honeycomb bits.
It's readable (as opposed to reference-able), and it's taught me quite a bit. I recommend you have a super basic background in Java (any object-oriented language would be good, but all the code in the book is Java and XML), something like Introduction to Computer Science or similar would do fine.
Good luck with that, and lemme know if you find any resources I should know about.
Zak Jones! said:
^^^ I've never seen so many ellipses. :s
@OP Yeah, I'm trying to do the same thing. I've picked up a book at B&N titled "Android Apps for Absolute Beginners", by Wallace Jackson. It's pretty up-to-date, and includes Honeycomb bits.
It's readable (as opposed to reference-able), and it's taught me quite a bit. I recommend you have a super basic background in Java (any object-oriented language would be good, but all the code in the book is Java and XML), something like Introduction to Computer Science or similar would do fine.
Good luck with that, and lemme know if you find any resources I should know about.
Click to expand...
Click to collapse
It's a bad habit.. I commend you on what you are doing...my background was I taught myself 8086 assembler for the at class back awhile ago. Nobody would help so I digested book after book and line after line of assembler and a language called Force. To make a Long story short, I wrote my first commercial assembler library with over 1600 functions! That's a lot of code. I was one person that wrote it, the manual and support over compuserve. I was very proud of and I believe no other language library even came near it. It was at the time the most feature rich one available with another library called Funcky II with around 1400+ functions. Both were C callable, large memory model. Today's hardware do not need that crap. Then eventually went into programming full time a little after that. So I speak from experience. It is one thing to ask for guidance and another for specific items. Every good programmer, without exception was self taught..yes they went to college for computer programming or others like me that did not..they shared a common theme which is self motivation and the discipline not to quit. I once asked a very good programmer what is the secret to becoming a great one and his reply was simply code and code away. A very good reference for programmers is in fact the library source. It is invaluable. Hope this helps a little bit. I did tout my horn, yes, but you needed to get a background so you would not think I was as my dad used to say "speaking out of my a?s".
life64x said:
It's a bad habit.. I commend you on what you are doing...my background was I taught myself 8086 assembler for the at class back awhile ago. Nobody would help so I digested book after book and line after line of assembler and a language called Force. To make a Long story short, I wrote my first commercial assembler library with over 1600 functions! That's a lot of code. I was one person that wrote it, the manual and support over compuserve. I was very proud of and I believe no other language library even came near it. It was at the time the most feature rich one available with another library called Funcky II with around 1400+ functions. Both were C callable, large memory model. Today's hardware do not need that crap. Then eventually went into programming full time a little after that. So I speak from experience. It is one thing to ask for guidance and another for specific items. Every good programmer, without exception was self taught..yes they went to college for computer programming or others like me that did not..they shared a common theme which is self motivation and the discipline not to quit. I once asked a very good programmer what is the secret to becoming a great one and his reply was simply code and code away. A very good reference for programmers is in fact the library source. It is invaluable. Hope this helps a little bit. I did tout my horn, yes, but you needed to get a background so you would not think I was as my dad used to say "speaking out of my a?s".
Click to expand...
Click to collapse
Nice, programming in assembler is no small feat. If you're familiar with Linux and Java you should have no problem figuring ROMs out. Dsixda has a kitchen he posted in the Android Chef's section that is very useful and apktool along with either WinMerge or Meld can be used to learn from the different ROMs.
It was a labor of love. I just seemed so cool in asm. Actually, what I want to write is a decompiler for the android with near perfect retrieval of code back. I seen the engine in smali and just do it for the heck of it. It has the parser in it..but I don't know java that well. Can't even write a hello world..) I was darn good in Delphi with windows and would be more comfortable with that. If somebody wrote simply a lexical for the small/ Bali output then that would all you would need for that type of program. I did not study java's reflection that good and it's another route. I want to give others who want develop the fun and passion I had. This was a hobby when I started. Years later, that hobby never left me. I respect the **** out of you and other developers out there, no matter what phone, tablet or computer because yes you are programming..you are giving something of yourself to others. Non programmers really do not know that developers for all the bugs and crap that comes with it...it is our soul, hearts and emotions that go into every line..every file we put out.
This you don't learn from a book..this you learn by making come alive what is inside our brains.
Thanks for the responses guys! Much appreciated. Looking forward to diving in head first!
Bigirish said:
Thanks for the responses guys! Much appreciated. Looking forward to diving in head first!
Click to expand...
Click to collapse
Have fun! I took xHausx suggestion and went to chefs central and it will help all new developers. Last night, went to the android forum section in there..hit last page of it and went backwards reading page by page and in that night investment..I found resources that are invaluable. I recommend you do the same. One thing I should tell you many out developer wanna bees out there...the only thing that sperates the ones who are and not is the simple fact..if they had a problem, they did give up. This may sound simple..but when you get frustrated...it is easy to throw in the towel.
i understand this question has been asked in similar ways but programming is quite broad so hopefully i can get a personalised response to help zone in on my learning.
bit of information about me:
ive been using computers all my life whilst doing a little bit of code tweaking for a variety of things such as; games(hex editting) web coding and even a bit of excel macro work.
i currently have no plans or commitments as of now and wanted to use my free days to learn something new that ive been intrested in since i was about 12 years old.
im looking for a base or a starting point in learning coding... i understand jumping straight into coding apps and things is way out of my reach but i guess i have to start somewhere! Im very much intrested in customisation and the ability to customise as much as possible on phones, games and applications but i have no idea where to start...
ive been looking around and people recommend learning all sorts of languages from:
php/css moving up to java
straight to java
python
c#
c++
c then progressing into c++
but id rather get an answer from a community that is notoriously skilled in the developing area so much so that i feel this is the best place to ask!
if there is anyone who also wishes to help me personally in helping me along the way and giving me some advice then please pm me as id be so grateful to have someone there to help me.
thanks in advanced for your responses im looking forward to learning and hopefully starting something that will be a major part of my life from now on.
Well, since this is a mainly Aneroid development website, and if you are interested in aneroid, I would just jump straight into Java. That's what I did at least... to learn Java just google "Beginner's guide to Java" or something. Hope this helps.
Sent from my Kindle Fire using XDA
i was hoping for more input then just one person, i would like to know what others feel is the best way to go about it so i can build up an idea of peoples opinions to see what i feel is the best strategy of learning.
i appreciate your input ballarous =)
penfold1992 said:
i was hoping for more input then just one person, i would like to know what others feel is the best way to go about it so i can build up an idea of peoples opinions to see what i feel is the best strategy of learning.
i appreciate your input ballarous =)
Click to expand...
Click to collapse
What are your development plans for? Do you plan on donning an apron and becoming a rom developer or do you plan on developing apps? You're setup will differ between the two but either way grab yourself a few good java books but understand it applies to Android differently than regular java. Learn the fundamentals of java, it's core rules etc but study googles open source api to see how you implement your phones system into regular java format. Here is a link to the Google source for developers (not source as in the source you sync to build Android, source as in how to implement phone apis into that source) http://developer.android.com/reference/packages.html
Here's some general app development guides that will broaden your understanding http://developer.android.com/resources/index.html
Sent from my Galaxy Nexus
From my experience...
It probably does not matter where you start... I personally started with web based languages like VBS, and javascript, then jumped into c++... I completely avoided Java until recently.
VBS or Visual Basic is used for excel macros so you already have some experience under your belt. It should be pretty simple for you to apply that same understanding to the different syntax of Java.
Hi All!
I want to learn to code Android Apps. I have no experience (aside from some BASIC coding back in school), but I have plenty of motivation.
I've found thenewboston website and the video tutorials looks really good, but they assume some coding knowledge which I need to get before proceding.
So, should I learn some C or JAVA first?
Or feel free to tell me otherwise.
I'd really like a plan of attack for the process of learning all this, as it's rather over whelming for a noob when presented with so much information and slightly differing opinions on what to learn first.
Thanks in advance.
Donald.
If you're focusing on Android 100% for now then pick up Java first. Also grab Android Studio as it's an excellent development tool that's replacing eclipse (Google is phasing out support for it later this year)
Sent from my XT1254
recommend the book "head first java"