donum

Because of that, I am also comfortable now with the CLI: Sublime Merge uses git terminology and made me understand a lot of details about git that I can transfer to the CLI. Things like using stash, cherry picking, tagging or rebasing are all very easily doable in Sublime Merge and if you choose to use one of those features, you automatically get familar with the CLI commands you'd need to use. Brilliant.

I'm not familiar with the whole feature set of the CLI, but I'm not missing much during day-to-day work in Sublime Merge.

PS: Clearly when it comes to more specific issues to fix, there is still the option to use the CLI for that.

Interesting bits here:

Usage of the aspect-ratio property which you cannot use yet, because support is still lacking. (using the padding-bottom trick works fine though!)

And the absolute most amazing CSS feature coming to our browsers soon: Container queries! Cannot fkn wait to use these!

Here is a list of all recorded talks of the RC3 (online conference, kinda replacing the 37c3): https://media.ccc.de/c/rc3

VoDs of past talks are already being uploaded here: https://media.ccc.de/c/35c3

There is also a free iOS app with the whole schedule and live streaming included https://itunes.apple.com/de/app/congress-35c3/id941205524

Android version here (although I don't know about streaming in this one): https://play.google.com/store/apps/details?id=info.metadude....

  Mein Vater erklärt mir jeden Sonntag unsere neun Planeten.

For me it looks like the overall amount of ice in the alps shrank a lot 10.000 years ago. Since then it remained relatively constant with the last 50 years giving it the final straw.

[1]: https://vimeo.com/294517816

1. VR costs a lot

2. The technology needs to be better (higher resolution)

3. There's not a lot of VR content available yet.

Two weeks ago, Gabe Newell and his SteamVR team talked openly about these issues in an interview. [1]

They say:

- The price will go down and the tech will become better. He said VR will be a new reason for CPU/GPU manufacturers to up their game again. (2018/2019)

- Valve is currently making three different full VR games (2017/2018)

- There should be an open VR standard

[1] https://www.youtube.com/watch?v=kMpQWSqQFK0

Although you have to say the product had its flaws on larger scales.

Within the abstraction, each of our "Elements" has his own XSL stylesheet containing the whole transformation of it. So for developers, it's easy to navigate the code. All elements are compatible with each other.

We've a task running in the background that groups all element into a single XSL stylesheet.

Within Apache Cocoon, you can setup a transformation pipeline. The "elements" will be applied in one step, other steps take care of i18n, i10n and "custom pages"/widgets.

Our documentation is written in that setup, too. We've also setup automated tests for our ~60 custom written EXSLT functions.

While I love it, I always wonder if others might think I am crazy.

It's german though.

Even if drugs may help in the short term to act ‚more open’ — everything you do when you're drunk is because of you and not caused by the drug!

Be concious and open and people will be open to you. The world around you is a mirror of yourself!

http://www.reddit.com/r/askscience/comments/42u57e/how_can_a...

This is a fine basic styling file, but I wonder how it is a "Framework". There are no options and no helpers like a grid (except the horizontal navigation which defaults to just that) or error states.

Why has it pixel values like 2.16px and 6.3px?

It might be a "framework" in the sense of being a good structure to start your work almost from scratch.

[1] http://images.apple.com/live/2015-mar-event/images/d02cd9e29...

I work together with a bunch of developers on a website that renders its HTML output with XSLT. What you address is architecture.

What we basically did is we have one XSL file for each "element". Elements are: button, image, headline, etc. Each of those elements inputs "our own" XML syntax with wisely chosen defaults (some HTML attributes like class,id,style get just passed through) and outputs Twitter Bootstrap HTML. Writing responsive websites in our framework is extremely easy. So each element has a XSL file where the magic happens, an XML file with documentation and tests and additional files like scass/css/js files with the same name. Accessing them is extremely easy when you use something like Sublime Text (what we all do).

All those different templates get written into just one XSL file automatically with the help of node.js' gulp.

The website gets delivered in Apache Cocoon which has a pipeline concept similar to gulp. Once a page got rendered, it is cached until the next update (except for pages with dynamic content of course).

The whole frameworks documentation is basically a website written in this framework with automated tests.

We use XSLT 1.0 + EXSLT and have written around 30 (EXSLT) functions to make sure everything works like we expect.

Everybody in our team loves it.

Just recently I had the chance to do a rewrite. What I did is I created "my own HTML". Basically every module of Twitter Bootstrap has it's own XSLT template. That means you have a very easy XML "HTML" syntax, but the output is Twitter Bootstrap. And every piece of output HTML is defined just once in the whole application so it's easy to maintain.

With the help of XSLT you can abstract a lot of things. One example: I have an element called <colgroup/>. It can contain up to 12 <col/> elements. if I set the @size attribute to one of the columns, the @size attribute for the others will be calculated automatically and the output matches the Twitter Bootstrap CSS classes.

I have to say, I love it. I can't imaging writing the whole mess of Twitter Bootstrap plain HTML in a template anymore.