Am I completely stupid or is there no way to test anything you make in Atom in a browser?
You mean like: https://atom.io/packages/run-in-browser?
Am I completely stupid or is there no way to test anything you make in Atom in a browser?
I'm not sure I understand the question. You're editing files, right? Can you not just keep those files open in a browser?
Say I'm testing (like today) a sticky nav bar. I write it up and then with
CoffeeCup - I "preview in browser." It shows up in whichever browser I selected.
Brackets - I hit "live preview." It opens a Chrome window. I can then change the HTML/CSS and see it reflected.
Atom - ???
Say I'm testing (like today) a sticky nav bar. I write it up and then with
CoffeeCup - I "preview in browser." It shows up in whichever browser I selected.
Brackets - I hit "live preview." It opens a Chrome window. I can then change the HTML/CSS and see it reflected.
Atom - ???
So, clearly, I'm doing things all fucked up. In my defense, that's just how I used to do shit back in the late 90s and early aughts. So, can somebody with some front end experience tell me how a more modern workflow goes? With specific services, if possible.
- I open up a blank html doc in CC/Atom/Sublime/Whatevs
- I write out some HTML, CSS, JS (all I'll likely ever need)
- I now need to test it to ensure it's functional code, but don't want to reupload to my server with every change.
- ?????
- Profit?
So, clearly, I'm doing things all fucked up. In my defense, that's just how I used to do shit back in the late 90s and early aughts. So, can somebody with some front end experience tell me how a more modern workflow goes? With specific services, if possible.
- I open up a blank html doc in CC/Atom/Sublime/Whatevs
- I write out some HTML, CSS, JS (all I'll likely ever need)
- I now need to test it to ensure it's functional code, but don't want to reupload to my server with every change.
- ?????
- Profit?
$ cd [directory where your html file is in]
$ php -S 0.0.0.0:8888
First off, thanks guys. I'm relearning how to do things I used to know 15 years ago (and obviously learning everything I missed in the meanwhile). I do appreciate y'alls advice.
So, while I learn about gulp and the like (I'm on Windows, btw) I"m going to go with Tathanen's suggestion and just set the HTML default to a browser. If I have my own server (I do) what is the benefit to using a local server? Is there a way to edit HTML files right on a server?
Are the questions I'm asking pants on head stupid?
Brackets...well, it may not have started as an Adobe product, but it sure as hell is one now. Meaning, it's laid out in way that anybody familiar with their way of doing things can figure out. But like all Adobe products, it's slow and updates are a rarity.
So it looks like they build the youtube gaming platform with Polymer. Nice.
https://gaming.youtube.com
Too bad it performs like shit in Safari on Mac. What is IE saying? Anyone tried?
Anyway, I'm excited to see google finally using one of their fancy frameworks and can't wait to use fully fledged web components one day. (Did they ever use Angular for anything?)
For the moment I still rely on less fancy custom elements for my components.
So it looks like they build the youtube gaming platform with Polymer. Nice.
https://gaming.youtube.com
Too bad it performs like shit in Safari on Mac. What is IE saying? Anyone tried?
Anyway, I'm excited to see google finally using one of their fancy frameworks and can't wait to use fully fledged web components one day. (Did they ever use Angular for anything?)
For the moment I still rely on less fancy custom elements for my components.
So I have a client who's website is in WordPress, and the page they want to put up is going to be a total custom job. Does anybody know of a WordPress plugin that would allow me to build a page entirely custom, but use WordPress so it's integrated into the CMS and able to retain all the benefits of using said CMS? I know I can build a custom WP template, but I'm just looking to see if there's a way to shortcut that.
I'm starting to think the answer is 'no', but it seems weird that something like this wouldn't exist.
Sorry if this was already answered (I just looked through all 18 pages looking to see if there was a good answer), but is there a recommended physical book for learning JavaScript (and most likely, general coding)? I found a copy of JavaScript: The Definitive Guide at a garage sale, but 50 pages in, it seemed like I was expected to have some degree of background already, which I definitely lack. Looking through the thread, though, I found mentions of Eloquent JavaScript and JavaScript & JQuery, but I don't know if one comes more recommended over the other.
I already know HTML/CSS from Duckett's book on them, so would J&J be more of a natural extension in this case?
IE9 isn't that bad, the problem is, that it's almost 5 years old, which is an eternity in web development years
I mean, back then we had Firefox 3.x, try to build a modern website for this thing... it's not much better.
Anyway, I think IE9 is way less problematic than it's predecessors. You can't do all the fancy new JS-tricks with it obviously, but for the most parts of a modern websites graceful degradation works good enough and polyfills allow you to code like it's 2015.
XHR file uploads are a huge pita though. It's so easy to implement it for modern browsers and such a pain with all those flash and whatnot fallbacks. I tend to do the classic form post in older browsers, because I don't want to mess with all the hacks and libraries only to give IE9 modern uploads.
Adding to that list:List of worst things about web development:
- Clients
- Clients and their ideas
- Clients
- Shitty backends to code against
- Shitty frontends to code against
- Shitty content management systems (seriously, you haven't felt the pain until your method of serving the end product is uploading a .zip-file to clients CMS, which then takes 10-15 minutes to unzip)
List of worst things about web development:
- Clients
- Clients and their ideas
- Clients
- Shitty backends to code against
- Shitty frontends to code against
- Shitty content management systems (seriously, you haven't felt the pain until your method of serving the end product is uploading a .zip-file to clients CMS, which then takes 10-15 minutes to unzip)
Adding to that list:
- Browser inequalities
- MOBILE browser inequalities
- Initial choice of the system/technology: "Yes please, add more frameworks in a bi weekly intervall, i just don't have enough choice yet!"
It's the web developers very own "I don't have anything to play / I don't have anything to wear" first world problem...
Or why "responsive" does NOT mean you get the mobile version for free.
Eloquent Javascript is also available online: http://eloquentjavascript.net/
It'd say it's pretty good fit to a beginner: it kinda dives deep, but also explains many basic principles of programming in general
Huh, I don't know how I missed that there was an online equivalent for EJ. In that case, I'll probably just use its online version and buy the Duckett book so I have both. Luckily I'd much rather have a deeper understanding of the language, too, especially after occasionally spying anecdotes in the thread about other developers being completely lost once their tried-and-true methods stopped working.Yeah, go with the Duckett book. If the HTML & CSS one did the trick for you, it's probably your best bet. I used them to brush up on things recently, and I liked them both a lot.
I thought javascript gave me a headache but React/Flux is like wutface.
I thought javascript gave me a headache but React/Flux is like wutface.