Well, yeah. If you're into that kindof thing (proprietary, costly software).
My post assumed some kindof LAMP stack.
Sorry, I didn't realize only homebrew-scale projects were allowed here.
I hope none of you use TFS or SVN.
I'm using TFS for a school project and SVN for work.
It's miserable...
How would you rate their stuff for development? I've used some of their courses before for more design based programs (Photoshop etc) and some of the courses were incredibly boring at times.
Has anyone tried any of the courses over at Udemy?
I hope none of you use TFS or SVN.
I couldn't even conceive of doing modern web development on Windows. You will spend more time fighting to get command line tools to work than you will actually coding. Especially if you are working on large projects with other dveleopers. You may as well dual-boot into a Linux OS if you're not willing to get a Mac. I see Windows devs struggle all the time. It's not worth it. If web development is your primary source of income, consider seriously Mac or Linux.
I hope none of you use TFS or SVN.
I hope none of you use TFS or SVN.
For CMS in the OP, I'd throw in Expression Engine. It's not as beginner friendly as say Wordpress (you'd want to get familiar with Code Igniter to get the most out of it), but it's very flexible when it comes to front end design/creating your own design templates.
I've made a few production apps with cordova/phonegap, and it's been an overall good experience.Has anyone here used PhoneGap for development of native apps across multiple mobile OSs?
What do you think? What are its strengths and weaknesses?
Has anyone here used PhoneGap for development of native apps across multiple mobile OSs?
What do you think? What are its strengths and weaknesses?
I hope none of you use TFS or SVN.
I use SVN. It's what my company has always used. I can understand preferring Git but what do you dislike so much about SVN?
Has anyone here used PhoneGap for development of native apps across multiple mobile OSs?
What do you think? What are its strengths and weaknesses?
Has anyone here used PhoneGap for development of native apps across multiple mobile OSs?
What do you think? What are its strengths and weaknesses?
In September we introduced a new breed of Chrome Apps that work offline by default and act like native applications on the host operating system. These Chrome Apps are currently available on all desktop platforms. Today we're expanding their reach to mobile platforms with an early developer preview of a toolchain based on Apache Cordova, an open-source mobile development framework for building native mobile apps using HTML, CSS and JavaScript.
The toolchain wraps your Chrome App with a native application shell and enables you to distribute your app via Google Play and the Apple App Store.
If you're looking at PhoneGap then this might be of interest. posted today on the Chrome blog.
http://blog.chromium.org/2014/01/run-chrome-apps-on-mobile-using-apache.html
thanks for the advice. i'm only interested in phonegap for making a very simple app that can be viewed on Desktop and a whole range of mobile devices. No intensive tasks or graphics requiredI've made a few production apps with cordova/phonegap, and it's been an overall good experience.
The strengths are mostly that you can use html/css/js and get "native" apps across many platforms quickly, which lets web developers use what they know instead of having to learn other languages.
The shortcomings are that you don't have easy (or sometimes any) access to some native apis. And the more demanding apps aren't as performant - don't make a 3d game with phonegap.
There are more little issues here and there, but the important stuff to consider is, what do you need your app to do? If all you need is some basic UI with access to some of the supported phone apis, then phonegap is wonderful. If you want to make a robust game with all the native game features, maybe phonegap isn't the right choice.
Anyone know the best way to handle automatically skipping to the next field on form entry for something like a credit card number? I should probably just make them hit the tab key or just use a single field but I thought it would be nice to have it do it automatically.
I've got it working with the following Javascript function which is called on key press, but it doesn't work for the case when the user tabs back to a previous field and starts entering numbers to replace the numbers in the field. It requires you to hit backspace or delete before you can re-enter numbers in a field.
function AccountNumberEntry(currentSection, maxLength, nextSection) {
if (window.document.getElementById(currentSection).value.length == maxLength) {
window.document.getElementById(nextSection).focus();
}
}
Anyone know the best way to handle automatically skipping to the next field on form entry for something like a credit card number? I should probably just make them hit the tab key or just use a single field but I thought it would be nice to have it do it automatically.
I've got it working with the following Javascript function which is called on key press, but it doesn't work for the case when the user tabs back to a previous field and starts entering numbers to replace the numbers in the field. It requires you to hit backspace or delete before you can re-enter numbers in a field.
function AccountNumberEntry(currentSection, maxLength, nextSection) {
if (window.document.getElementById(currentSection).value.length == maxLength) {
window.document.getElementById(nextSection).focus();
}
}
Just to be clear, what 'doesn't work' when you tab back to a previous field?
From what I understand, when the CC field is validated (on key press), you want to jump to the next field automatically - but something doesn't work when a user 'tabs back to a previous field'. When you say previous field to mean tabs back to the credit card field, or tabs back to a field BEFORE the credit card field? And when you say 'it doesn't work' do you mean that if you go back to the CC input, this function no longer fires? Would it be possible for you to show some more code?
Anyone know the best way to handle automatically skipping to the next field on form entry for something like a credit card number? I should probably just make them hit the tab key or just use a single field but I thought it would be nice to have it do it automatically.
I would maybe check to see if the field is valid and if it is, move to the next field with the next function along with focus function. You also need to specify what to do if there are no more inputs to 'skip' to.Anyone know the best way to handle automatically skipping to the next field on form entry for something like a credit card number? I should probably just make them hit the tab key or just use a single field but I thought it would be nice to have it do it automatically.
I've got it working with the following Javascript function which is called on key press, but it doesn't work for the case when the user tabs back to a previous field and starts entering numbers to replace the numbers in the field. It requires you to hit backspace or delete before you can re-enter numbers in a field.
function AccountNumberEntry(currentSection, maxLength, nextSection) {
if (window.document.getElementById(currentSection).value.length == maxLength) {
window.document.getElementById(nextSection).focus();
}
}
JSFiddle is godtier. I probably wouldn't have been able to make my little JavaScript only webapp without it or StackOverflow to help me debug problems or see functioning examples of something.Edit: And JSfiddle!
Anyone else have a chance to play with Sencha Architect yet?
http://www.sencha.com/products/architect/
I went to a workshop last week with it and was pretty impressed! I'm not too big on Dreamweaver type IDEs, but this was super slick. During the workshop we actually built up a mobile responsive site using their framework from scratch in less than an hour.
My biggest concern is the pricing, it's $1000 to get in the door then there's an extra charge for modules (like packaging out to Android, iOS, etc).
Can anyone recommend something similar?
I hope none of you use TFS or SVN.
The internet, as a network, is designed to be tolerant of faults. If parts of the network fail, the damage gets routed around and things keep working. HTML is designed to be tolerant of faults. If a document has unrecognised tags, or only partially downloads or is structured weirdly, the browser will do its best to keep displaying as much of that page as it can without throwing errors. CSS is designed to be tolerant of faults. If a selector doesn’t match or a property is not supported, or a value is unrecognised, the browser steps over the damage and keeps going.
JavaScript is brittle and intolerant of faults. If a dependancy is missing, it stops. If it hits unrecognised syntax, it stops. If the code throws an error, in some cases it stops there too. If part of the script is missing, it likely won’t even start. As careful as we are to code defensively within our JavaScript, it counts for nothing if the code doesn’t run.
[...]
It used to be that progressive enhancement was the accepted ‘best practise’ (ugh) way to do things. If you’re building a site today you’d generally make it responsive. Any new site that isn’t responsive when it could be is considered a bit old-hat and a missed opportunity. So it used to be with progressive enhancement. If you built a site that depended on JavaScript, chances are you were a cowboy and didn’t really know what you were doing – a skilled developer wouldn’t do it that way, because they know JavaScript can break.
Somewhere along the line that all got lost. I’m not sure where – it was still alive and well when jQuery launched with it’s find something, do something approach (that’s progressive enhancement). It was lost by the time AngularJS was ever considered an approach of any merit whatsoever.
When did the industry stop caring about this stuff, and why? We spend hours in test labs working on the best user experience we can deliver, and then don’t care if we deliver nothing. Is it because we half expect what we’re building will never launch anyway, or will be replaced in 6 months?
Perhaps I’m old fashioned and I should stop worrying about this stuff. Is it ok to rely on JavaScript, and to hell if it breaks? Perhaps so.
I hope none of you use TFS or SVN.
Anyone else have a chance to play with Sencha Architect yet?
http://www.sencha.com/products/architect/
I went to a workshop last week with it and was pretty impressed! I'm not too big on Dreamweaver type IDEs, but this was super slick. During the workshop we actually built up a mobile responsive site using their framework from scratch in less than an hour.
My biggest concern is the pricing, it's $1000 to get in the door then there's an extra charge for modules (like packaging out to Android, iOS, etc).
Can anyone recommend something similar?
In the real world people use whatever is at work.
something to think about. I still believe progressive enhancements is the way the web should work. Unless you're doing something that specifically requires one of these technologies (say, a game using WebGL) then the information you put online should be accessible in some form and you should plan accordingly.
http://allinthehead.com/retro/367/why-is-progressive-enhancement-so-unpopular
Why is Progressive Enhancement so unpopular?
something to think about. I still believe progressive enhancements is the way the web should work. Unless you're doing something that specifically requires one of these technologies (say, a game using WebGL) then the information you put online should be accessible in some form and you should plan accordingly.
bonus -> http://motherfuckingwebsite.com/
http://allinthehead.com/retro/367/why-is-progressive-enhancement-so-unpopular
Why is Progressive Enhancement so unpopular?
something to think about. I still believe progressive enhancements is the way the web should work. Unless you're doing something that specifically requires one of these technologies (say, a game using WebGL) then the information you put online should be accessible in some form and you should plan accordingly.
bonus -> http://motherfuckingwebsite.com/