Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
After studying how to use objective C for the previous months I realise actually you can create an app using HTML 5, CSS 3 and JavaScript. Just want to know which method got more advantage than the other. Objective C or a combined usage of HTML 5, CSS 3 and JavaScript to create an iPhone app.
You can create good HTML5 apps for iOS; absolutely. The HTML5 browser is very performant on newer iOS devices. That can mean that it is good for simple apps. However, if you want a native looking app (one that looks like it belongs on the platform) especially since iOS 7 released, you're going to have to go with native code. It will allow you to look native and have higher performing apps.
Objective-C as long as it's native to the iOS platform. Non-native apps are always quite sloppy and non-performant.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to start with desktop development, i am student and i have been working on web development, searching i found some tools and frameworks
AppJS
Node-Webkit
Titanium
Sciter
Awesomium
chromiumembedded
And others... I don't know which one I must use, i don´t want to have problems in the future, so I need the better one with great support and functionality.
Thanks!
We use Electron as container for web based multiplatform app
http://electron.atom.io
And the container is that must to have for desktop applications written in html + js + css. Electron is similar to node-webkit (nw) you mentioned.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm a sw engineer but I have almost zero experience in web development. I have noticed recently few interesting websites and I'm curious how they are built.
The first example is
http://www.google.com/nexus/5/
I'm really excited about the way page reacts when you get to the mid part where it describes the camera.
Today I saw that Microsoft has a similar website for their new CEO
http://www.microsoft.com/en-us/news/ceo/index.html
Since this is Microsoft, I'm guessing that it uses completely different web technology.
So, my question is, if I were to build a website like this for myself, where would I start first? I'm guessing that Google's website is relying heavily on JavaScript, but are there any open libraries/frameworks that I could use to achieve this effect?
Parallax scrolling for the scroll effects.
The jQuery library of javascript and of course using HTML / CSS for styling and structuring your pages. This is where you can start off.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
looking at applications like Adobe's Brackets, how did they manage to make the javascript / html stack behave like a desktop app? In other words, what's the underlying magic that makes it work?
Well, there are a few options really:
There's HTML Applications, but they're pretty much dead and gone.
There are Chrome Apps too
Special frameworks (such as TideSDK) also exist, which act in a similar manner to PhoneGap
In addition to BenM's list, there is also the Adobe AIR technology:
Adobe AIR is a cross-platform runtime that enables you to use your
existing Flash/ActionScript or HTML/JavaScript development skills and
tools to build and deploy applications, games, and videos outside the
browser and on mobile devices.
I only can make a guess how they work, but I think that some "mini-browser-engines" are embedded within a windows frame and glued together.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I know Knockout.JS and Angular.JS at the intermediate's level. It is great for building Single Page applications. However, my new project is going to be very large and would last almost 3 years building it (approximately 50 pages). I am pretty sure Single Page application concept is not going to fit here due to the complexity of the project and large number of pages that have varied functionality.
My question: How would these frameworks help me in building large scale application? Should I bind Controllers/ViewModel on per page basis? Also, should I consider combining all the scripts or should I load them on per page basis? Basically I am not sure how to architect my application.
You can use Knockout.js for multi page applications
There are several options for handling this type of thing that are detailed here: Example of knockoutjs pattern for multi-view applications
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I come from desktop application background and now I am working on web based application. So I am fairly new to client side script like Javascript.
I have a question that what set of standards we need to follow to make sure that our Java script code will work.
Any link for the same will be really helpfull.
That depends on what browsers you want to support. If you want to support pretty much everything, use the ECMAscript 3 standard. If you just want to support relatively recent browsers, you can use the ECMAscript 5 standard. Any features other than that and you can use this site to see about compatibility.
EDIT: For any other functionality that you think might not be very widespread, you can always check MDN as well.