That seems very useful. Objective-C syntax is pretty weird compared to other OOP programming languages. What is this game engine that you're using though? Can you provide some details? It would be great to be able to code in a different language like Java.
Anyone else hate not being a programmer?
- Thread starter mpbiz
- Start date
That seems very useful. Objective-C syntax is pretty weird compared to other OOP programming languages. What is this game engine that you're using though? Can you provide some details? It would be great to be able to code in a different language like Java.
It's Unity 3d. Natively it allows 3 languages, C#, unityscript (.NET jscript), or Boo.
Then it does other languages via plugins and it requires the pro version which isn't cheap. But then you build a .jar for android or dll for windows, or obj-c for ios, and can communicate with them from the .net based scripting languages(C# is popular).
This is a crude prototype made today using one of several computer vision SDKs for tracking an image based target (cube) and uses the game engine for the rest of it, rendering, physics, scripting, etc.
[ame=http://www.youtube.com/watch?v=ahT06-NH840]clip from work - YouTube[/ame]
Same deal with the MS kinect SDK, compile VS project into .dlls and can communicate with them in Unity from C#, jscript, or boo. It also compiles unityscript (jscript) if you use that and allegedly it's the same speed as C#.
Bump.
The big nerd ranch book got confusing as fuck in the objective-c review so I put it aside and jumped into an iOS dev video course. I definitely absorb more info during the videos especially when typing along with the instructor and having the visual element as well.
So far so good. It's the perfect mix of building apps using the object library that comes with xcode, and I'm also learning some objective-c but only what I need so no information overload yet.
Going to try and get another 8 hours of iOS video course + actual xcode work in by Sunday. Then another 8 on Monday.
I started programming 17 days ago, and have actually spent time learning and coding for 16 with a grand total of 60 hours and 30 minutes logged.
My goal is to be able to create basic apps from scratch without needing to look back at my resources or references for help within the next 2 weeks.
The big nerd ranch book got confusing as fuck in the objective-c review so I put it aside and jumped into an iOS dev video course. I definitely absorb more info during the videos especially when typing along with the instructor and having the visual element as well.
So far so good. It's the perfect mix of building apps using the object library that comes with xcode, and I'm also learning some objective-c but only what I need so no information overload yet.
Going to try and get another 8 hours of iOS video course + actual xcode work in by Sunday. Then another 8 on Monday.
I started programming 17 days ago, and have actually spent time learning and coding for 16 with a grand total of 60 hours and 30 minutes logged.
My goal is to be able to create basic apps from scratch without needing to look back at my resources or references for help within the next 2 weeks.
You will always be needing to look back at references, to some extent. One of the most important things to learn is how to read API documentation, because they all roughly follow the same format, and it is a skill that will carry over to other platforms. It is good to be organized at this stage; makes it easy to quickly find what you are looking for in your old code if you know you did something before, but don't remember the details.
This is another SDK for facetracking using just a plain rgb webcam.
I mocked it up for trade shows for a helmet company where you can switch helmets and see what they look like by standing in front of a kiosk that is basically a TV with a micro computer and webcam:
[ame=http://www.youtube.com/watch?v=MVZt3p9RKsw]Face tracking with webcam - YouTube[/ame]
Also have used the kinect in 2 shipped products, one in combination with the occulus rift and the other a slot machine that you trigger by pulling an invisible lever with the kinect.
Also can make multiplayer games easily, anything from fps to "draw something" type apps.
Mocked this up in 1 day from scratch, just reading through documentation adding piece by piece:
[ame="http://www.youtube.com/watch?v=Rya4Mqfs15E"]multiplayer animal demo - YouTube[/ame]
^^ all clients connect through cloud server, movement/rotations are all synced across all clients, projectiles are synced across clients, etc
I used to work construction, now I have my dream job from stuff I learned outside of school. And I actually get paid to learn new SDKs and do R&D most of the time.
The only way to learn how to code, is to code. You need to work on something that you need/want to make work.
With that in mind, perhaps a collaborative WF project could help fill that void? A project that members would want to get together and build and learn. I have no idea what this would look like. I would imagine some seasoned coders might even be willing to occasionally help with problem areas. Or they would simply flame the shit out of the group.
It depends on your operation, scale, skills etc.
Example: I just automated some windows software that builds links. My script takes my projects, enters them into the software, then runs the software, then checks it all works. 24 hours per day.
Haven't read the whole thread, but I just started using UBot Studio 5 on Monday and already have a process that used to take an hour and a half of my personal time daily down to 15 minutes. The automation runs while I'm eating breakfast. Working on some getting some other processes automated now...
Did I fail to mention it would be a bit Coin project?
Edit: now we be making all kinds of gains, all kinds
Appreciate the input.
Definitely going to keep detailed notes on specific blocks of code and what they do.
codebox looks like a perfect fit for this.
Doxygen: Main Page is another good tool. If you use formatted comment sections before function definitions, you can run doxygen to pick them up and generate your documentation. It takes some getting used to, because running it with the default settings will usually produce a lot of junk. But you can use it to generate searchable documentation in html, pdf, other formats. You can also link your editor/IDE to it so it will display the method signatures and descriptions right there.
There is a member here who wrote his own IDE, but I forget who.
Having a version control system may help, also. I run a local SVN server, and a couple times it has saved my ass when I have lost or overwritten code.
That sounds really slick. It would definitely be nice to have all of the descriptions right there while coding.
Bump.
I'm really glad I took 2 quick courses in C and Objective-C. Definitely helps because I've been recognizing things in other tutorials I'm going through now specific to iOS programming. Just being familiar with and recognizing the syntax helps a lot, but I'm realizing that you can prepare all you want but once you're actually putting together a real app for the first time it's completely different.
I got used to printing out everything in the console, now I'm working with an interface and objects and making everything work together and I got kind of overwhelmed.
So I decided to go through several app building tutorials, and make checklists of the different steps taken for each of them. This just helped a lot and made a ton of lightbulbs go off for me.
I'm starting to realize that yes, this stuff is complicated in some ways, but at the same time a lot of it is really simple.
Here are the basic steps that I've noticed are in every app's creation process:
1. Build the interface.
2. Decide which interface objects are OUTLETS and which ones are ACTIONS.
3. Type your ACTION objects code inside the header file.
4. Type your OUTLET objects code inside the header file.
5. Connect the interface objects with their corresponding code that you just typed in the header file. This is really simple and just involves control-clicking and dragging.
5. Type your ACTION objects code inside the main file.
6. Type your OUTLET objects code inside the main file.
That pretty much sets up the entire foundation for every app. At least the ones I've been working with. From there, you just need to fill in the gaps and build on the foundation with function specific code for all the different things you need which really could be done by using google and stackoverflow.
I'm starting to see how someone could just understand the basics above, and do serious damage just by knowing how to ask questions correctly on stackoverflow.
Pretty stoked about all of this. I'm going to finish the current iOS video course I'm going through, but now that I figured out the above I think I'm going to just build my first app that I really want to build as soon as I'm done with the course.
If anyone would like to add some advice or input, or if you disagree with the conclusion I came to above I would really like to hear from you.
Lesson Learned: Learn the basics that go into all apps, then figure out how to fill in the gaps for the specific app your building by using references and stackoverflow.
I'm really glad I took 2 quick courses in C and Objective-C. Definitely helps because I've been recognizing things in other tutorials I'm going through now specific to iOS programming. Just being familiar with and recognizing the syntax helps a lot, but I'm realizing that you can prepare all you want but once you're actually putting together a real app for the first time it's completely different.
I got used to printing out everything in the console, now I'm working with an interface and objects and making everything work together and I got kind of overwhelmed.
So I decided to go through several app building tutorials, and make checklists of the different steps taken for each of them. This just helped a lot and made a ton of lightbulbs go off for me.
I'm starting to realize that yes, this stuff is complicated in some ways, but at the same time a lot of it is really simple.
Here are the basic steps that I've noticed are in every app's creation process:
1. Build the interface.
2. Decide which interface objects are OUTLETS and which ones are ACTIONS.
3. Type your ACTION objects code inside the header file.
4. Type your OUTLET objects code inside the header file.
5. Connect the interface objects with their corresponding code that you just typed in the header file. This is really simple and just involves control-clicking and dragging.
5. Type your ACTION objects code inside the main file.
6. Type your OUTLET objects code inside the main file.
That pretty much sets up the entire foundation for every app. At least the ones I've been working with. From there, you just need to fill in the gaps and build on the foundation with function specific code for all the different things you need which really could be done by using google and stackoverflow.
I'm starting to see how someone could just understand the basics above, and do serious damage just by knowing how to ask questions correctly on stackoverflow.
Pretty stoked about all of this. I'm going to finish the current iOS video course I'm going through, but now that I figured out the above I think I'm going to just build my first app that I really want to build as soon as I'm done with the course.
If anyone would like to add some advice or input, or if you disagree with the conclusion I came to above I would really like to hear from you.
Lesson Learned: Learn the basics that go into all apps, then figure out how to fill in the gaps for the specific app your building by using references and stackoverflow.
Quick question: to use Object Orientation in PHP - yes or no? I use straight procedural code for my AJAX called scripts and they are fast. I read that OO slows things down a bit. Does anyone have an opinion on this based on what they've experienced?
If it is for anything else than for a small script, absolutely yes. Maintainability > a small speed increase.
Also avoid 99% of the tutorials out there, they are crap. Good luck bro.
I'm someone that has, after over a decade in the space, decided to learn be proactive in a lot of the tasks and menial shit that I need done. I've been spending time on it every night for the past few months, and I can pretty much accomplish all I need/want at this point. I still have a team of US developers that I work with, but it helps to be able to just make those slight changes you want in the middle of the night while everyone else is asleep.
Too many times have I sat there and said "but I know this would take you two seconds, just don't prioritize it right now."
I may get bashed for this, but if you want to learn from the absolute beginning sign up for one month of Treehouse. It's boring, elementary and childish, but it'll establish the absolute basics of programming that you can continue into whatever language you so desire.
From there, choose your paths and courses of action that best suit your needs.
Too many times have I sat there and said "but I know this would take you two seconds, just don't prioritize it right now."
I may get bashed for this, but if you want to learn from the absolute beginning sign up for one month of Treehouse. It's boring, elementary and childish, but it'll establish the absolute basics of programming that you can continue into whatever language you so desire.
From there, choose your paths and courses of action that best suit your needs.