import patty | |
import strformat | |
import strutils | |
import sugar | |
include karax / prelude | |
include karax / kdom | |
include karax / kajax | |
type |
include karax / prelude | |
import strutils | |
type | |
Model = object | |
counter*: int | |
Dispatch = proc(model: Model): void | |
proc init(): Model = | |
result = Model(counter: 0) |
I want to talk about different approaches in writing mobile apps. I will tell you when it is a good idea to pretend that your responsive website is an app. Also about evolution of this idea from basecamp and DHH - turbolinks. I will tell you about my lovely ReactNative and the problems it has. When you can't avoid writing apps in native sdk and what difficulties you may face going this way.
Last year I used to write apps in objective-c. My open source works mostly around react native but my heart is with Ruby on Rails.
As websites become more JavaScript heavy, it's harder to automate things like screenshotting for archival purposes. I've seen examples and suggestions to use PhantomJS for visual testing/archiving of websites, but have run into issues such as the non-rendering of webfonts. I've never tried out Selenium until today...and while I'm not thinking about performance implications yet, Selenium seems far more accurate than PhantomJS...which makes sense since it actually opens a real browser. And it's not too hard to script to do complex interactions: here's an [example of how to log in to Twitter, write a tweet, upload an image, and send a tweet via Selenium and DOM element selection](https://gist.github.com/dannguyen/8a6fa49253c1d6a0eb92
$ pip install https://bitbucket.org/pypa/setuptools/downloads/setuptools-8.0b1.zip
$ pip install -U git+git://github.com/dstufft/pip@use-packaging
Try to install / uninstall projects, see if you can generate any errors and let me know how it's worked. This represents a big reworking of how version
This is just a few thoughts on the topic of writing technical guides. This was intended for Basho's engineering team, but this may apply to open source projects in general.
It's commonly preached that the first step in writing is to identify your audience; to whom are you writing? This is the most well known, most repeated, and most overlooked step of writing in general and technical writing in particular. Take this document, for example. My audience is technical people who need to communicate technical information, and not teenagers, so I shy away from images of pop icons and memes. I use jargon and words like "identify" rather than "peep this".