///usr/bin/env jbang "$0" "$@" ; exit $? | |
//DEPS org.jpos:jpos:2.1.8-SNAPSHOT | |
//REPOS mavenCentral,jpos=https://jpos.org/maven | |
import org.jpos.iso.ISOMsg; | |
import org.jpos.iso.ISOUtil; | |
import org.jpos.iso.packager.GenericPackager; | |
import org.jpos.util.Logger; | |
import org.jpos.util.SimpleLogListener; |
/* | |
* dropbox_ext4.c | |
* | |
* Compile like this: | |
* gcc -shared -fPIC -ldl -o libdropbox_ext4.so dropbox_ext4.c | |
* | |
* Run Dropbox like this: | |
* LD_PRELOAD=./libdropbox_ext4.so ~/.dropbox-dist/dropboxd | |
*/ | |
/** | |
_____ _____ _ | |
| __ \ / ____| | | | |
| | | | ___| | _ __ _ _ _ __ | |_ ___ _ __ | |
| | | |/ _ \ | | '__| | | | '_ \| __/ _ \| '__| | |
| |__| | __/ |____| | | |_| | |_) | || (_) | | | |
|_____/ \___|\_____|_| \__, | .__/ \__\___/|_| | |
__/ | | | |
|___/|_| | |
*/ |
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 7668
lines of CSS (and just 2 !important
).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
- SUIT CSS naming conventions + SUIT CSS design principles;
- PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
- Flexbox is awesome. No need for grid framework;
- Normalize.css, base styles and variables are solid foundation for all components;
This is a compilation of various open-source Unity plugins, codebases, or utility scripts that may aid in expediting the development process.
"ProbePolisher is a Unity Editor plugin for editing light probes. It works both on Unity Basic (free) and Unity Pro."
import java.io.IOException; | |
import java.net.URLClassLoader; | |
import java.nio.file.Files; | |
import java.nio.file.Paths; | |
import java.nio.file.Path; | |
/** | |
* Example demonstrating a ClassLoader leak. | |
* | |
* <p>To see it in action, copy this file to a temp directory somewhere, |
try | |
{ | |
// Something | |
} | |
catch (error) | |
{ | |
var spoon = Packages.org.pentaho.di.core.gui.SpoonFactory.getInstance(); | |
spoon.messageBox( | |
error.message, error.name, | |
true, Packages.org.pentaho.di.core.Const.INFO |
import UnityEngine | |
class Vibration(MonoBehaviour): | |
private viblator as AndroidJavaObject | |
def Start(): | |
unityPlayer as AndroidJavaClass = AndroidJavaClass("com.unity3d.player.UnityPlayer") | |
currentActivity as AndroidJavaObject = unityPlayer.GetStatic[of AndroidJavaObject]("currentActivity") | |
viblator = currentActivity.Call[of AndroidJavaObject]("getSystemService","vibrator") |
The BugHerd sidebar can be configured to override some of its default behaviour as well as display extra information in any tasks that you pass in from a configuration object called BugHerdConfig
.
When setting up BugHerd for the first time, you probably already know you need to add the following code to your site:
<script type="text/javascript">
(function (d, t) {
var bh = d.createElement(t), s = d.getElementsByTagName(t)[0];
bh.type = 'text/javascript';
bh.src = '//www.bugherd.com/sidebarv2.js?apikey=YOUR-API-KEY-HERE';