ReText – Markdown Editor with Live Preview

ReText is a simple but powerful text editor for Markdown and reStructuredText.

It is written in Python using Qt libraries, able to run on any platforms.
You can read more about ReText in our FAQ.

You can now translate ReText using Transifex!

We now have a Transifex project. You can translate not only the app itself, but also additional files like desktop file and mime files. Please update your translation.



Get it

The best way to get ReText is to use the Files page. You can also use Git to get the more recent (and unstable) code.

See the Quick Start Guide for the list of dependencies.

Debian and Ubuntu users can install ReText using apt-get install retext command.

Help us test it

If you have some time, please go through our testing procedures and report any bugs you find.

If you don’t have a account, you can ask questions and report bugs at Launchpad.

Original URL:

Original article

Maqetta means mockup, Part 1: Design an HTML5 mobile UI

Need to prototype an HTML5 app? Forget coding.
Hand-eye coordination is just about all you need to
prototype with Maqetta,
a browser-based WYSIWYG tool for desktop and mobile applications.
This first article in a three-part series introduces this
free, open source project that runs in a browser and lets designers
drag and drop a rich set of widgets to build live UI mockups. In Part 1,
get to know Maqetta’s major functions and features while prototyping a
realistic mobile application.

Original URL:

Original article

Textus: An open-source platform for collaborating around collections of texts

What is TEXTUS?

In a nutshell it is an open source platform for working with collections of texts. It enables students, researchers and teachers to share and collaborate around texts using a simple and intuitive interface.

What does TEXTUS do?

TEXTUS currently enables users to:

  • Collaboratively annotate texts and view the annotations of others
  • Reliably cite electronic versions of texts
  • Create bibliographies with stable URLs to online versions of those texts

Where has TEXTUS been deployed?

The first instance of TEXTUS will be deployed as We are working closely with students from Goldsmiths University, the University of Oxford and a distinguished advisory board of philosophy academics to make sure that OpenPhilosophy meets the needs of the philosophical community.

How do I get involved with TEXTUS?

TEXTUS is an open source platform developed by the Open Knowledge Foundation. If you’d like to get involved you can:

Original URL:

Original article

Show HN: Paz – A Simple Docker PaaS Written in Node.js

Continuous deployment production environments, built on Docker, CoreOS, etcd and fleet.

Paz is a pluggable in-house service platform with a PaaS-like workflow.



  • Beautiful web UI
  • Run anywhere (Vagrant, public cloud or bare metal)
  • No special code required in your services
  • Built for Continuous Deployment
  • Zero-downtime deployments
  • Service discovery
  • Same workflow from dev to production
  • Easy environments


  • Web front-end – A beautiful UI for configuring and monitoring your services.
  • Service directory – A catalog of your services and their configuration.
  • Scheduler – Deploys services onto the platform.
  • Orchestrator – REST API used by the web front-end; presents a unified subset of functionality from Scheduler, Service Directory, Fleet and Etcd.
  • Centralised monitoring and logging.

Service Directory

This is a database of all your services and their configuration (e.g. environment variables, data volumes, port mappings and the number of instances to launch). Ultimately this information will be reduced to a set of systemd unit files (by the scheduler) to be submitted to Fleet for running on the cluster.
This service has a REST API and is backed by a database (LevelDB).


This service receives HTTP POST commands to deploy services that are defined in the service directory. Using the service data from the directory it will render unit files and run them on the CoreOS cluster using Fleet. A history of deployments and associated config is also available from the scheduler.

For each service the scheduler will deploy a container for the service and an announce sidekick container.


This is a service that ties all of the other services together, providing a single access-point for the front-end to interface with. Also offers a web socket endpoint for realtime updates to the web front-end.

Web Front-End

A beautiful and easy-to-use web UI for managing your services and observing the health of your cluster. Built in Ember.

Monitoring and Logging

Currently cAdvisor is used for monitoring, and there is no centralised logging. WIP.


Paz’s Docker repositories are hosted at, but they are public so you don’t need any credentials.

You will need to install fleetctl and etcdctl. On OS/X you can install both with brew:

$ brew install etcdctl fleetctl


Clone this repository and run the following from the root directory of this repository:

$ ./scripts/

This will bring up a three-node CoreOS Vagrant cluster and install Paz on it. Note that it may take 10 minutes or more to complete.

For extra debug output, run with DEBUG=1 environment variable set.

If you already have a Vagrant cluster running and want to reinstall the units, use:


To interact with the units in the cluster via Fleet, just specify the URL to Etcd on one of your hosts as a parameter to Fleet. e.g.:

$ fleetctl -strict-host-key-checking=false -endpoint= list-units

You can also SSH into one of the VMs and run fleetctl from there:

$ cd coreos-vagrant
$ vagrant ssh core-01

…however bear in mind that Fleet needs to SSH into the other VMs in order to perform operations that involve calling down to systemd (e.g. journal), and for this you need to have SSHd into the VM running the unit in question. For this reason you may find it simpler (albeit more verbose) to run fleetctl from outside the CoreOS VMs.


Paz has been tested on Digital Ocean but there isn’t currently an install script for it. It shouldn’t take much, just be sure to edit the PAZ_DNSIMPLE_* values in digitalocean/user-data. Stay tuned…


There is an integration test that brings up a CoreOS Vagrant cluster, installs Paz and then runs a contrived service on it and verifies that it works:

$ cd test
$ ./

Each paz repository (service directory, orchestrator, scheduler) has tests that run on (in StriderCD), triggered by a Github webhook.

Paz Repositories

The various components of Paz are spread across several repositories:

Original URL:

Original article

VLC Gets Extensions, Resume Playback, and Comes Back to iOS

Windows/Mac/Linux/Android/iOS: VLC is hands-down one of the best media players around and today it gets a little better by adding an in-app extensions store, playback resuming, and more. More importantly, the iOS version of the app returns to the App Store.

Read more…

Original URL:

Original article


There will be a temporary halt to new posts at Legal Informatics Blog until summer 2015, so that I can finish my dissertation. Many thanks for reading, and we’ll see you in a few months.

Filed under: Algorithms

Original URL:

Original article

Open Access and the Law Symposium—Dallas, TX

The University of North Texas–Dallas College of Law is sponsoring the annual symposium on topics relevant to Open Access initiatives which is being held May 18-19, 2015. The theme of this year’s symposium is “Open Access and the Law.” Invited speakers include colleagues working on electronic legal materials authentication and institutional repositories, among other topics. Information about […]

Original URL:

Original article

Unreal Engine 4 Is Now Free

jones_supa writes In 2014, Epic Games took the step of making Unreal Engine 4 available to everyone by subscription for $19 per month. Today, this general-purpose game engine is available to everyone for free. This includes future updates, the full C++ source code of the engine, documentation, and all sorts of bonus material. You can download the engine and use it for everything from game development, education, architecture, and visualization to VR, film and animation. The business scheme that Epic set in the beginning, remains the same: when you ship a commercial game or application, you pay a 5% royalty on gross revenue after the first $3,000 per product, per quarter. Epic strived to create a simple and fair arrangement in which they succeed only when your product succeeds.

Share on Google+

Read more of this story at Slashdot.

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: