Engineers Inn

In association with Káráchi Schỏlars Schỏỏl.

Engineers Inn is proud to present its Introductory course for programming with Python with the cooperation of Káráchi Schỏlars Schỏỏl.

We are also starting an introductory Java course in cooperation with Káráchi Schỏlars Schỏỏl.

We are starting an introductory C # course this Ramazan in association with Káráchi Schỏlars Schỏỏl. Hope to see all the students who have already registered and those who are going to.

Students taking the course "Introduction to OOP and Android" in Ziauddin University, join the Edmodo group with the group code : k6gzt6

It will have all the necessary material for you in this course.

Ziauddin University College of Bio-Medical Engineering in Collaboration with Engineers Inn cordially invites all its participated students to attend the 1st lecture of the short course on the Topic "Introduction to Android Programming”
Speaker: Engr. S Arham Abbas.
Duration of Course: 2 Months (24 Credit Hours).
1st Lecture: 24th September 2016 (Saturday)
Class Timings: 9:00 am to 1:00 pm
Kindly please be on time.
Venue: Ziauddin University College of Bio-Medical Engineering.
City Campus F-103, Block ‘B’, North Nazimabad,
Karachi. Tel: 021-36644153, 021-36648237-9 Ext: 334
For Further Information and Details kindly contact: Engr. Mehwish Faiz and Engr. Adnan Baig.

These are the necessary software for developing applications in a 3D engine.

Unity is very user-friendly [due to its GUI based designing and development method and ] and programming can be done in C # and Javascript [Unityscript]. It is mainly used to create games and simulations but given its ease of use and ability to develop applications for multiple platforms due to the Monodevelop project, it is a great platform for beginners to learn programming for Android, iOS, Windows, etc without the need to learn platform-specific languages.

1. Unity - https://store.unity.com/

Unity - Store Unity is the ultimate game development platform. Use Unity to build high-quality 3D and 2D games, deploy them across mobile, desktop, VR/AR, consoles or the Web, and connect with loyal and enthusiastic players and customers.

Using Unity, C # and Visual Studio to create games on your desired platforms.

Beginning Game Programming with C# - University of Colorado System | Coursera Beginning Game Programming with C # from University of Colorado System. The Beginning Game Programming with C # course is all about learning how to develop video games using the C # programming language. Why use C # instead of C++, Java, ActionScript, or some other programming language you may have hear...

This course on Coursera informs you on various passive and active methods of learning. It is awesome and will help you gain knowledge faster and retain it for longer. What is stopping you from not taking it?

Learning How to Learn: Powerful mental tools to help you master tough subjects - University of California, San Diego | Coursera Learning How to Learn: Powerful mental tools to help you master tough subjects from University of California, San Diego. This course gives you easy access to the invaluable learning techniques used by experts in art, music, literature, math, science, sports, and many other disciplines. We’ll learn a...

A beginners guide to Unity Programming. By Unity Technologies.

Unity - Coding in Unity for the Absolute Beginner In this session we will introduce coding in C # to the absolute beginner. This class is for someone who wants to get started, but doesn't know where to begin. We will discuss the very basics of coding, including variables, functions and classes and how to use them. We will also discuss using the most...

A summary of the development and deployment process of applications on the Android platform against the iOS platform.

Android vs. iOS: Comparing the Development Process of the GQueues Mobile Apps A quick search for "android vs. ios" will turn up many articles arguing the benefits of one platform over the other, with most focusing on ...

Q) What are the differences between the C programming languages: C, C++, C #, and Objective C?

A)1.
C is like the first car that came out. It does everything but you have to work at it. It has no roof so if you make mistake (like going out in a thunderstorm) you will get wet. Of course you can fix that but you need to do work to add an umbrella.

C++ is still based on C. Its just got additions to make life easier like a roof and maybe more gears so you can go slower or faster and save some fuel. You still need to work at it. Its still manual (shift stick I think in American).

Objective C is a car from another manufacturer, they took the original design but added other bits to it. So its not C++ but maybe adds wider tires and rear seats and maybe automatic gears. Over time this manufacturer borrowed from C++ and added others bits.

C # then is Tesla. They came along and said that they wanted to keep the original idea but make huge changes. It's still a car but it runs on different fuel. They also wanted to make things easier and remove direct control by adding autopilot but allowing you to still feel comfortable with what you know.

2.
Programming is hard, and it used to be much harder. Once upon a time, you had to write all of your programs in a machine-specific variant of Assembly language. The code I wrote for a PDP-11 wouldn't run on a different type of computer. Worse, Assembly languages generally required a very thorough knowledge of the specific CPU architecture.

That's inconvenient. There were a number of "high level languages" out there- COBOL, Fortran, LISP, and while they might be fine for day to day work, they were terrible choices for what we call "systems programming"- doing something like writing an operating system, or interfacing directly with a piece of hardware. But they were portable (a COBOL program could run on any computer that had a COBOL compiler), and they were much easier to program.

What was needed was a high level language that could easily be translated into Assembly (and machine code), but wasn't as abstract or distant from the hardware as languages like COBOL. Something that was basically "user friendly Assembly", that had the benefits of portability. That language was C.

C was used to write Unix, and quickly became on of the dominant languages for writing software. It was fast, it was powerful, and it was everywhere. Its syntax became what programming is. Even languages that have no relationship to C at all, like JavaScript, use a similar syntax. So when programming philosophies began to change, and ideas like "Object-Oriented Programming" rose to ascendance, people took the approach of grafting these new concepts onto a C-like syntax.

Enter C++ and Objective-C. Both of these languages introduce a new high-level abstraction: the object. They encourage you to write your programs as models of real-world systems. If you're managing a bank, you'll have an actual object in code called "BankAccount", and it has both behavior (things it can do) and attributes (data).
That's the key difference between these languages and plain-old C (although how they handle memory is also an important difference). As far as the difference between C++ and Obj-C, that difference is how they designed their object-oriented concepts. Obj-C lifted all of its features from a different language called Smalltalk. Essentially, Obj-C is what happens when Smalltalk and C have a baby (and, while there are some interesting features in it, let's be honest: it's an ugly baby). The goal of Obj-C was to retain all the best parts of both, and it partially succeeded.

C++, on the other hand, took an approach to managing objects that was closer to C-style syntax. Of the two, C++ became the dominant choice- it had speed similar to C, but objects were a useful abstraction.

Phew. Okay, finally, that brings us to C #, and to understand C #, we have to understand Java. Back in the 1990s, we were dealing with portability again. While a C program can be ported between computer architectures more easily than Assembly, it's not instant. You often have to customize the code, and even if you don't, you have to compile that code for each architecture. So the folks behind Java had a bright idea: what if we ran all our programs in a virtual machine- a "in memory" computer that we simulate? The idea was that they could port Java itself to different architectures, and then programmers could write a Java program that would run any place Java worked, without having to ever modify their program or compile it for different architectures. Java lifted most of its syntax from C++ with heavy modifications.

Fast forward to the early 2000s. Microsoft has been releasing its own Galapagos-mutant version of C++ for ages now, and it also has this ugly bastard language called Visual Basic, which is weirdly popular but… just terrible. They've been watching what's happening in the Java space, and decide, "Goddamn, I want some of that action." So using the concepts of Java as a starting point, they create .Net. .Net, like Java, has a concept similar to a virtual machine. C # is a language that lifts features from Java and C++ (and a number of others) and creates code that can run on the .NET Common Language Runtime.

3.
C is quite old. Back when every company that sold computers made them quite differently, the "operating system" was very specific to the computer as well. In the early 1970s, Dennis Ritchie and Ken Thompson worked on what would become the UNIX operating system. UNIX was created for the PDP-11 computer, and in order to make it work on other computers, UNIX had to be portable (modifiable so that it works on other platforms). Dennis Ritchie started out with the programming language BCPL for this task, which already had the purpose of making portable programs. He continued tweaking the compiler and adding features to the language, and eventually ended up inventing C. As UNIX grew popular in academic and business circles, so did C: everything in UNIX was written in C, UNIX came with the source code and a C compiler, and there was an amazingly effective tutorial for C (co-written by Brian Kernighan).

Meanwhile, and also long before C and UNIX, other programming languages were developed with different focuses. One of them was Simula, which was developed in the mid-1960s. This language was mostly made to simulate (hence the name) how groups of 'objects' communicate with each other. Other programming languages built upon these ideas.

Objective C and C++ were created around the same time (in the 1980s), as a way of combining the very well-known programming language C and the very useful style of thinking in 'objects'. While the latter was already possible in C, it wasn't very convenient.
Many other variations on C were created, but very few of them are as well-known as the one you listed. For instance, in the late 1990s, Microsoft had Simple Managed C (SMC), which they used to write most of their "class libraries" (the basic tools they need to make programs). Probably because it had become hard to write software using SMC in a way that makes it easy to maintain, a team within Microsoft decided to create a new language. Eventually, they settled on the name C #.

Many of the practical differences between these languages come from their history. C is quite old, and to make sure that all different C compilers understood programs written in "C", it was standardised early on. The goal of C is to write portable software (and yet, its goal is also to write non-portable software... long story), and even though there are some new versions of this standard, C really sticks to what it originally did. Old code works on new compilers, and to some extent, new code works on old compilers. But because of this, C is very limited in what you can conveniently do with it.

Objective C and C++ are very similar in what convenient extras they offer, but they offer them in a very different way. The main difference is in how you write it down; it's similar to the difference between speaking German and speaking Japanese.
C #, is quite a different beast. Like its predecessor SMC, it is a "managed" programming language: the compiler usually doesn't translate C # into machine code -- the language that your computer's processor understands -- but into bytecode -- a language that a virtual or 'fake' processor understands. A virtual machine "manages" the ex*****on of the program, rather than letting the real processor read it directly. Because of this difference, you suddenly don't have to worry about "portability" anymore: you're always running on the same type of (fake) hardware! In many ways, this changes what a programmer can and should do; from asking the processor what an object's structure is really like (known as "reflection", which is pratically impossible to do in the other languages) to simply sending the bytecode rather than the source code (written in C #) to people who want to use your program on very different computers or operating systems.