Building your own tools makes you a better programmer. Seriously. There is nothing more satisfying than the feeling of pressing a single button instead of doing some annoying job that you used to do before by hand and YOUR program or script runs off to do all your work for you and then it says:
All done, task took 35 milliseconds
Continue reading “On building your own tools”
I’m currently tasked with the revision of some lecture material for basic HTML, CSS and PHP studies, so I thought I should give gitbook a try.
It’s a super sweet generator for creating an interactive website, a pdf and even epub from a loosely structured bunch of MarkDown files. You can imagine I love that. Continue reading “Creating books with Gitbook”
I’ve tried out Github’s Atom Editor shortly and I must say, they’ve come up with a pretty cool thing.
If you want to try it out, drop a comment, got 3 invites. At the moment only for Mac OS.
Here a couple of screenshots, thanks to Mikkel for providing hardware so I could try it out 😉 Continue reading “Github’s Atom Editor tried out”
I have a quite terminal based workflow. I needed a way to copy the HTML version of a MarkDown file, straight to my clipboard. I love writing in my favourite text editor and I know a lot of other people do. They don’t want to bother with browser windows and their lack of key bindings and shortcuts. Projects like GHOST certainly make things easier for people like me, but I still have a majority of my blogs running WordPress. Continue reading “Copy MarkDown HTML to Clipboard from the Terminal / Shell”
I just wanted to show, quite quickly, what combination of windows I’ve been looking at a lot in the past months.
Basically I’ve been writing the book I’ve been talking about in gVim, which is a GUI frontend for vim. With it I use the Tomorrow Theme and Adobe’s Source Code Pro.
Git for Book writing
Git is amazing and I love it. I’ve been using it to write the book and to track my MarkDown source files. It’s been really easy to figure out when I did what, which is great when you’re dealing with several releases of software and you have to adjust things. It flags everything you change, everything you add, everything you take away. It’s nice to know that no matter what you do, you can always go back, you have a history in many small, but meaningful pieces.
Editing and Revisions
The editing was done in regular office software like Word and Libre Office/Open Office to correct mistakes, elaborate, clarify, etc.
It’s very reasonable and it’s been a struggle for me once in a while, because I have a hard time using desktop publishing and home office products. They crash, are buggy and just don’t offer a very good writing experience. This I think was the hardest part!
Poet is a great little node.js based project that allows you to start a blog in no time.
The description of the project by the author made me smile, so I’ll just quickly share this quote: Continue reading “Poet – a node.js blogging platform”
Retext is a great MarkDown editor for beginners and is widely available on the Linux platform.
After introducing Uberwriter I thought it would be time to introduce Retext, which focuses on different features.
Retext features that are most valuable to me are the display of files in split view and PDF export. It’s a solid editor for both MarkDown and plain text files and I think it’s great for beginners to check the MarkDown syntax right away.
Having said that, it’s much like Mou, my favourite MarkDown editor on Mac OS X, but not as feature rich.
Features I’d love to see in Retext
- custom CSS for PDF export
- theming support for the editor itself
- changing the “copy HTML” functionality so it only exports the body, without surrounding
Retext is available in most package managers, called
retext, so for Debian / Ubuntu you would run:
sudo apt-get install retext
On Arch Linux you currently have to remember to install
python-markdown with it, since it is not automatically required as a dependency:
sudo yaourt -S markdown-python retext
Writing from a developers point of view and writing from a PBA studies examinators point of view are very different things. Developers want to write code and slam documentation into MarkDown files they can track with git (assumption). PBA examinators want a footnote drenched, printable document, that belongs back in the 1970s (fact).
For my last hand-in I’ve created a quick & dirty script, that does just that to your MarkDown files. Continue reading “Quick & Dirty: MarkDown to PDF”
When I first learned of MarkDown I was torn between having to write academical papers in software like Microsoft Word or Apple’s Pages. Both are surely functional Programs, even though I’d always preferred Open or Libre Office, for the sake of standards and an open world.
In my studies as a Multimedia Designer in Denmark I even handed in some papers that were written in HTML and compiled to PDF.
That clearly was not the most practical, but for me the most bearable of these alternatives. Plain text is just great, especially for people who write a lot or the ones that code on a somewhat daily basis. Continue reading “Why I believe in MarkDown”
Yesterday I’ve installed Uberwriter, which is a MarkDown editor I quickly want to tell about. It’s a very nice looking application and something that is my replacement for Mou, which I’ve come to love on my Mac.
Continue reading “UberWriter: a MarkDown Editor for Linux”