Ellzord

I designed and prototyped an artificial life framework for simulation (or games) in Java 8. When I was happy with what I had made and how it could be used the first thing I thought about was making it open source. Actually getting to the point where anyone can use or contribute to it was a right nightmare (had no doc at all)!

I think my open source framework would be really useful to students or to anyone going open source. Here is why:

• JALSE is on GitHub: this means you really have to learn git (I'd like to know why any new project wouldn't use git). Source control systems seem like a unnecessary thing when you're working solo but as a team its 101. GitHub makes it easy by having everything visually available to you (and it's pretty). JALSE GitHub
• JALSE is built by gradle: It really doesn't matter what you use to build as long as it makes your life easier (and for me that's gradle). It's clean and easy to read what's happening and it's the best parts of Ant,

tan3

#
# browserweiche 
#

[browser = msie] AND [version = <8]
  page.includeCSS.iehacks = fileadmin/templates/css/patches/iehacks.css
[global]


#

koenbollen

using Microsoft.Xna.Framework;
using System.Linq;


namespace Screens
{
    /// <summary>
    /// This is a screen that can be added to the ScreenManager. Extend it and add components 
    /// to it in the Initialize() method. You can also override the Update() and Draw() method.
    /// </summary>

wp-kitten

<?php
/**
* WordPress Query Comprehensive Reference
* Compiled by luetkemj - luetkemj.com
*
* CODEX: http://codex.wordpress.org/Class_Reference/WP_Query
* Source: http://core.trac.wordpress.org/browser/tags/3.3.1/wp-includes/query.php
*/
 
$args = array( 

ruario

Install docker via your distro's package manager and configure it for your user.

Use the "vivaldibld.docker" docker template file as follows, to build an appropriate Docker image:

docker build -t vivaldibld - < vivaldibld.docker

After this completes successfully, you can run the docker image, like so:

afmicc

DataTable.net - serverside processing

DataTable.net - Implementation of serverside processing in .net Core MVC with ef core dynamic query to paging, sorting and searching

Integralist

Set-up remote git repository on a standard server

The first thing to do is to install Git on the remote server.

Once you do that the rest of the process is split into three sections:

1. Server set-up
2. Local set-up (push commits)
3. Server (pull commits)

Snugug

What if controlling your media queries was as easy as adding on to a Sass list? What if I told you it now is?

This snippet comes from a modified version of mixins in the Aura Responsive Framework and came from me hijacking the respond-to mixin namespace but still wanting to use it for custom media queries. It's a little ugly and requires Sass 3.2+ (for now, (sudo) gem install sass --pre), but it works a charm.

There are two fairly mundane caveats to this method. First, every media query needs to be named. Second, every media query needs a size and assumes min-width and screen. If you want to change min-width, simply add your operator as another option, but if you want to change screen, you need to also include your operator even if you want it to be min-width.

Also, I haven't built in warnings yet for when you do bad things, so bear that in mind.

Without further adue, tada.

dvddarias

/************************************************************
 * Better Singleton by David Darias
 * Use as you like - credit where due would be appreciated :D
 * Licence: WTFPL V2, Dec 2014
 * Tested on Unity v5.6.0 (should work on earlier versions)
 * 03/02/2017 - v1.1 
 * **********************************************************/

using System;
using UnityEngine;

greim

How you can help reduce node_modules bloat

This recent reddit thread reveals discontent among the web development community about the sheer volume of stuff in a typical node_modules dir. 140MB in this case!

Is it a design flaw in npm?

Opinions in the thread varied from "I'm surprised npm even works" to "everything is fine". I'm not going to offer an opinion, just these two observations:

1. node_modules dirs typically do contain lots of stuff that doesn't need to be there.
2. The latest version mitigates overall size by flattening the dependency tree, but some of the bloat is beyond npm's control.