conventions

Is there a standard guideline of what order the CSS properties should be in? This would be to decide if I should use this code p {font-size: 14px; color: purple} or this code instead p {color: purple; font-size: 14px} Edit I am now using The CSS Box Model Convention There is no widely adopted convention. There is no difference between either example, so you should choose the convention you prefer. If you must really satisfy the hobgoblins, choose alphabetical or the order it affects the box model. There is, indeed, no widely agreed-upon convention. I prefer writing Concentric CSS where I list

I came across an interesting comment in php.net about serialize data in order to save it into the DB. It says the following: Please! please! please! DO NOT serialize data and place it into your database. Serialize can be used that way, but that's missing the point of a relational database and the datatypes inherent in your database engine. Doing this makes data in your database non-portable, difficult to read, and can complicate queries. If you want your application to be portable to other languages, like let's say you find that you want to use Java for some portion of your app that it makes

I need to convert a traditional J2EE web application into a new Maven web project. In traditional project JSPs are under WebApp/jsps folder, JavaScript & CSS files under WebApp/scripts folder, image under WebApp/images folder, .properties files under WebApp/resources folder. In the Maven project where would each of those file types go? Should I create folders under src/main/webapp such as: src/main/webapp/jsps , src/main/webapp/images , src/main/webapp/resources … etc and copy the files from old project? Or is there any standard structure to follow? Can't Tell Take a look at this article on

I'm fairly new to R, and I have been defining some of my own functions in script files. I'm intending for others to re-use them later, and I can't find any guides on R function commenting conventions. Is there any way for me to make help("my_function_name") show some help? If not, do I just document the function in the script file, so that someone has to print out (or open the source of) a script to see the comments? Thanks, Hamy The canonical way to document your functions and make them accessible to others is to make a package. In order for your package to pass the build checks, you have to

Hi when I started doing web development, I realized javascript event names were all in lower case with no separators, i.e. "mousedown" , "mouseup" , etc. And when working with the jQuery UI library, I noticed they also use the same convention; i.e. "dropdeactivate" as in the following example javascript $( ".selector" ).on( "dropdeactivate", function( event, ui ) {} ) While this works well for names that are only 2 or 3 words, it is really awful for names with more words on it. Despite of this I followed that convention too when I have to fire custom (synthetic) events that I created, until

I'm in the process of refactoring some logic built into a Rails application into middleware, and one annoyance I've run into is a seeming lack of convention for where to put them. Currently I've settled on app/middleware but I could just as easily move it to vendor/middleware or maybe vendor/plugins/middleware ... The biggest problem is having to require the individual files at the top of config/environment.rb require "app/middleware/system_message" require "app/middleware/rack_backstage" or else I get uninitialized constant errors on the config.middleware.use lines. That could get messy very