xaritas
This is the bug: Scrolling causes the page to reload. Not even joking. Seems to happen on all pages.
Anyway, I took a look on my desktop and it works fine there. I might even sign up a few of my clients. Just not with my phone.
<div class="greeting-container" data-lift="SayHello"><span class="greeting">lorem ipsum</span></div>
And a transformation: ".greeting *" #> "Hello World"
The output will be: <div class="greeting-container"><span class="greeting">Hello World</span></div>
See http://exploring.liftweb.net/master/index-5.html#entry-CSS-T... et aliaWith this technique, your designers can create pure HTML and assets, with no logic in the templates. Basically they create static mock-ups and then the developers "enliven" them.
I prefer this but I don't imagine it will ever become mainstream.
React's JSX is also (as far as I can tell) node based, but with a lot less power (you can really only do insert operations, and the operations don't really compose well).
- Java / Scala / Clojure
- Go
- Erlang (add Elixir if you are comfortable with its maturity)
Not meant to be an exhaustive list of languages. Celery is great but there are plenty of situations where chucking units of work into a job queue or running a cron job feels like an incomplete solution.http://bitfountain.io/course/ios-design/?couponCode=general
For people who purchased the iOS 8 course based on Swift, there is a further discount to $39 until Monday (not sure if this applies to people who haven't yet purchased the course, so caveat emptor).
I would also assume that by "slaves" he means, legal status aside, what would be called "the help" in a different era, i.e., the most visible members of a wealthy person's household and retinue. I'm sure that nobody was socially shunned because their salt-miners and ice-cutters were hideous to behold.
Graecia capta ferum victorem cepit et artes intulit agresti Latio. - Ep. II.i.156
"Greece, once conquered, herself conquered the artless victor, and planted the banner of civilization in the farmlands of Rome."
I have translated freely and taken considerable license.
By Aurelius' time, familiarity with Greek for the ruling classes was a given; as a matter of preference, it is a more supple language and probably more comfortable to use for putting abstract reasoning to words.
Web Development with Clojure: Build Bulletproof Web Apps with Less Code (https://pragprog.com/book/dswdcloj/web-development-with-cloj...)
Luminus: http://www.luminusweb.net
Edit: argh italics
See also, Borges; not usually considered a science fiction author, I suppose for reasons having to do with the connotations of being a genre author.
http://www.antipope.org/charlie/blog-static/fiction/accelera...
I agree that the structure and pacing is odd if taken as a single corpus (which is hard not to do in its book form!) I wasn't surprised to learn after reading it that it was published serially over the course of three years. I suspect that the sequence was not mapped out fully.
Edit: Heh. When I refreshed I didn't see the response from the author confirming this.
Nevertheless, I in fact did not know about M-. so thank you for your contribution. For those interested, I found it described here: http://www.aboutlinux.info/2005/08/bash-shell-shortcuts.html
It's not a comprehensive list, it omits one of my favorites, C-/, which gives you undo on the command line. Well, until you hit return, anyway.
At a high level, I can see how there might have been a bit of friction in trying to implement Wagtail on top of Mezzanine. Mezzanine's features, admin interface, and content model are fairly tightly integrated (I hope I'm not misrepresenting Mezzanine here, I think that this is an affirmative goal of the project). It provides a lot for the developer and the site admin out of the box—usable templates, basic page types, a blog, an image library. On the other hand, Wagtail core offers surprisingly little—the wagtaildemo project is a nice starting point for some basic content types, but it's just another user of the Wagtail API.
For me, the killer features of Wagtail are: deep integration with ElasticSearch, a moderation based workflow, content revision tracking, document library. It's feature list is like a love letter to institutional clients. However, that's a lot of code that is not integral to Mezzanine, and I don't think it fits with the maintainer's philosophy of "it's integrated, but not a kitchen sink." [Note: I made up this quote.]
To both maintainers, nice work, and thanks.
(Having said that, the rich text editor is in Wagtail really is rich and can support inserting images from the image library and links to documents in the document library, as well as oEmbed stuff, so it has some wriggle room).
The two schools of thought ("each page is designed ahead of time with structured content in mind" vs "each page is a collection of content objects") have their adherents. Personally I prefer the Wagtail and Mezzanine approach, but the right answer depends on what the client needs and the nature of your relationship with them.
I played with it and found it to be pretty Rails-like, even including several moments of "what foul sorcery is this?"
In Zotonic a single Erlang VM hosts multiple sites (equivalent to Django projects), which can be nice for certain uses. Like most Erlang frameworks it is a little better at handling concurrency and AJAX-y ("realtime") websites than some of the more popular web frameworks, to support this the template language is extended to allow wiring UI elements to controllers without explicitly writing the JavaScript.
Having said that it's not "just a CMS," it is in fact pretty awesome for building simple marketing/brochure mostly-static-but-with-a-contact-form-and-blog type websites. Individual websites can be hot loaded into the running daemon, and started, stopped, and rebuilt from a git repo through a web based interface. I host a couple local business sites for some recurring income and I'm strongly considering porting my existing clients to it and using it for similar sites in the future.
Despite that simple use case, I wouldn't dismiss it for more complex projects, as long as, e.g., its data model (a triplestore built on top of postgres) works for you.
In summary, in my opinion it has some caveats but is as good as Django. :)
Yes, I purchased my LED bulbs in anger. We'll see if I've been had.
For the project I have in mind, the client wants an HTML5 web app, not an App Store delivered container. On the docs, you state:
"Since mobile browsers often exhibit issues while in browsing mode that don't show while running under a "wrapped" native app, we recommend running all Ionic examples in a Desktop browser, PhoneGap or another native wrapper."
Can you elaborate on this a bit? What issues am I likely to see if I just deliver my project as an offline capable single page web app?
I always wondered if the ω glyph developed when lazy monks sloppily doubled up oo to make the o-mega… but I never investigated whether this is true.
Links of interest: http://en.wikipedia.org/wiki/Iambic_trimeter and http://en.wikipedia.org/wiki/Trochaic_tetrameter
Interesting facts about ancient Greek: in contrast to English poetry, stress is indicated by the length of the vowel, rather than how forcefully it is pronounced; and vowels are accented by rising or falling pitch rather than stress. My professors said that ancient Greek probably sounded more like Chinese (which I gather follows similar rules) than a modern western language.
They both block the thread and any other go-blocks that happen to be mapped to it. I think you get 2 x NUM_CPU threads in the dedicated pool for channels, so either of these is a mistake. (Aside: I'm not sure why you were down voted for saying this.)
When you need to wait inside of a go-block, the correct way is to use (timeout millis), which creates and then closes a channel.
This has some nice examples: https://github.com/clojure/core.async/blob/master/examples/w...
Rather, turned from a framework into a library. I only recently started with Clojure and found Luminus pretty easy to pick up. It just generates a simple scaffolding project which cherry-picks some good libraries into a project.clj file and gives you a basic "Hello world" web page to get started. Primarily it uses lib-noir on top of Compojure, so pretty much anything that was in Noir, you get here (I guess, I never used Noir directly). Luminus has a pretty good tutorial to cover basic notions of handlers, databases, etc.
No, it's not Rails or Django, and no it doesn't do anything you could do yourself from scratch pretty easily. It is, however, a nice starting point and may help you get over the "I have to wire everything together myself" hump.
Of course, this is guess from a priori reasoning. I would be genuinely interested if somebody tried file-based comments for a WordPress (or a similar platform) based site and it fell over or failed in some way.
Based on yeoman (http://yeoman.io), which I used briefly for the first time a few days ago, and it seems like a nice system. It already has pretty good integration with the AngularJS seed project.
You could probably roll something together using middleman (http://middlemanapp.com) too, with a bit more legwork.