What are cons to write and manage CSS in notepad? in compare to any css IDE?
specially in team environment? How much it will effect to project timeline if we are forced to use notepad.
should we always use an IDE for CSS?
No Auto-intelligence
Need to remember each keyword and syntax
No Formatting and alignment
No Rapid Development
No Syntax Highlighter
No CSS Checker and Validator
No CSS Beautifier
No Code collapse functionality
I use Notepad++ for editing my CSS and one of the things it does better than Notepad is syntax highlighting and occassionally formatting and indentation.
Syntax highlighting isn't that important for CSS but at least having an editor with that does cut down on typo errors.
If it's only cons:
you're not able to automatically format your CSS code
you will need to do indentation yourself
prone to errors
nobody writes perfect codes, and without an IDE, chances is there will be errors here and there
No inline code hinting
you probably need to know what to type, for there are no hinting what values are able to be entered for that property.
no syntax highlighting
stop straining your eyes!
But for me, time is precious. I'll rather open CSS files and edit them in Notepad, rather than spending some time opening, saving code and closing an IDE just to edit few lines of CSS code.
Related
Is there any way to hide or otherwise make inaccessible a web pages proprietary CSS code? I know about minification but a minified css file can easily be unpacked.
Thank you for your help,
Marc
Aside from minification and perhaps base64 encoding, there is nothing you can do to mask your CSS text. And those are easily reversible.
There is no way to make it unreadable, as the browser has to be able to read it in order to display it, therefore the user can read it if they want to.
I think you are tackling the wrong problem. Your problem shouldn't be "how do I prevent users from seeing my proprietary css code" it should be "Why does my CSS code have anything proprietary in it."
It really shouldn't, and if it does you should fix that.
No. The browser needs to be able to access the CSS in order to display the page correctly.
You could unpack the elements from the CSS and apply them inline instead. Not sure if that would solve your question though.
Is there a way to disable syntax highlighting in Atom.io?
I have searched a bit and ended up creating my own syntax package (https://atom.io/themes/no-syntax-highlighting-syntax), but maybe there is a better way.
NB: I just want to disable syntax highlighting (ideally keeping only comments and code in a different color), but I still want the other language-related features of Atom.io working. Like language completions, language snippets, language closure/bloc detections, auto-indent, etc.
(Some people argues against syntax highlighting, stating it might be actually harmful to developer productivity. I wanted to try that. Ie. http://www.linusakesson.net/programming/syntaxhighlighting/ and https://www.robertmelton.com/2016/03/21/syntax-highlighting-off/)
You can use Ctrl+Shift+L (or press button bottom right) to select proper language. In your case it would be Plain Text.
Second option is install package https://atom.io/packages/file-types and add in config.cson:
'file-types':
'YOURS EXTENSION': 'text.plain'
Haven't found a better solution yet.
If you are trying to do the same thing as I was - disabling syntax highlighting in Atom.io while keeping comments differentiated, language completions, language snippets, language closure/bloc detections and auto-indent - I would just recommend to install the theme I've created: https://atom.io/themes/no-syntax-highlighting-syntax
Set the file syntax to plain text. You can do this with control alt L or something like that.
I find very convenient to edit a CSS from Chrome, and then saving my edits directly.
But then I need a way to take this changes back to SASS by hand, and I think that may be there is a tool to do this more easily.
I understand that it is difficult to have a tool that automatically does that, but may be there is some tool that can at least do a comparison between the SASS file and the CSS file (like a diff) and let me see the SASS in the right pane and the CSS in the left pane, in a synchronized view ?
Sass Sleuth is a tool that will solve this problem for you.
Alternatively you could use FireSass for Firefox, or Sass Inspector for Chrome.
You might want to try this nifty online service which does just that: https://css2sass.heroku.com/ or the code: https://github.com/jpablobr/css2sass
I've been re-writing my resume from scratch (good way to start the new year, I think,) and I'm doing it as a webpage. Naturally I want all the HTML, CSS & Javascript in one file, so it'll be portable.
While working on it in Vim, I have the CSS, HTML, & Javascript sections of the document open in separate tabs. But as soon as I open a second tab, the syntax highlighting for the CSS turns off. The HTML and Javascript continue to be highlighted properly.
I'm not a Vim expert by any means, so I apologize if this is too basic a question, but I couldn't find any documentation (or existing posts on Stackoverflow) that address this issue.
Thanks in advance for any insight.
Because vim doesn't start looking for highlighting at the "top" of the file, but rather a few hundred lines up from the current on-screen view, you can sometimes get the highlighting to work by scrolling around a little.
If this works, you can tweak the syntax highlighting controls so that you don't have to waste your time scrolling around; for full details, see :help syn-sync. There's several options:
Forcing vim to start recognizing syntax from the very start of the file every time. This might lead to significant performance problems on huge files but that might also be an indication that your source could be better split apart.
:syntax sync fromstart
Increase the number of lines that are parsed. This reduces the chances of bad syntax recognition without necessarily incurring the expense of reparsing the entire file from the start each time.
:syntax sync minlines=200
Pick a number that is large enough to work almost all the time without significant performance penalties. This is probably the best approach to take, even 500 lines ought to be alright on most computers from the last decade.
If you're editing C-style code, vim can easily resynchronize using C-style comments. (Note, not the // newfangled variety but /* the original style */.) Probably not the best choice for HTML, CSS, JavaScript, but perhaps your code makes it more feasible:
:syntax sync ccomment
The fourth method uses "sync patterns", similar to the C-style comments, but more applicable to other environments. It has enough extra complications that I don't think describing it here is worth the effort -- :help syn-sync-fourth has all the details for the curious.
Any of these configuration options can be added to your ~/.vimrc file:
syntax sync fromstart
You can change the behavior based on what kind of files you're editing. Just leave off the leading : when adding lines to the file. Use autocmd to define it for types like this:
autocmd BufNewFile,BufRead *.html syntax sync fromstart
These may become relevant to provide an answer
what version of vim are you using? I'm assuming you're using Vim 7.3 (if not, you should - most linux distors have it, and there's an exe for Windows and MacVim for osx). It could be that your installation is old or broken.
Any plugins? A simple check will be to temporarily remove all your plugins, restart vim and see if this still happens.
Anything special in your .vimrc? If you customized it yourself then there are probably not too many surprises, but if you borrowed from someone else, you can do the same thing you did with the plugins folder (empty or bare-minimum file).
Hope this helps - good luck!
Is there a way to add a comment/uncomment css line/s button to the menu in the VS2008 css editor? Other than adding a macro. Thanks.
There is not a way, quite a few people have wondered why they'd leave this out. Here's the most detailed way I've seen to add a macro by Brian Schmitt. I know it's not what you want, but he also outlines how to add it as a keybind, meaning you could make the Ctrl+K,Ctrl+C work for commenting lines in CSS files just like it does in code files now. It's a little work to setup, but if you're used to the Ctrl+K, Ctrl+C it's really nice to have it work everywhere.
I believe it's the closest you can come to what you're after until they add it as a built in keybind.