]]>
]]>
]]>a group of volunteers throughout the world began creating an open, free, online Japanese-English dictionary. The form and content of the dictionary are decided by the participants in the project. Among its features are the following: * Definitions that explain the meaning of words as completely as possible * As many examples as possible of each word in real contexts * Photographs and other illustrations, especially for entries about uniquely Japanese things * No restrictions on the type or range of vocabulary * No restrictions on the length of entries The dictionary has been named jeKai (je海), pronounced "jay-kai" or ジェーカイ.
souriretalked about many many things including my first, but hardly my last, attempt to make him explain RDF to me.
]]>
This poster (800×1000mm) was designed to summarize and explain the summer holiday of 2009: a roadtrip/ moving house expedition undertaken by my partner Marthe and I, from Norway to England and back.
IN ONLY 11 INDIVIDUAL LESSONS this WordPress Theme Tutorial is going to show you how to build a powerful, up-to-date, WordPress Theme from scratch. As we go along I’ll explain what’s happening including (for better or worse) my thinking on certain techniques and why I’m choosing one path over another. Essentially, I’ll be teaching you everything you need to know about WordPress Theme development.
Not infrequently, the menus on blogs, created with WordPress, having static links. This may initially seem easier and less trouble, but if changes or maintenance by users who have no knowledge or access to the templates occur, it is cumbersome and error prone. Therefore I prefer to use the necessary template tags and using the help of parameters that are not desirable (exclude) or desired (include) pages load. In addition, you can add content via the Hook, which I will explain briefly.
It was originally my intention to produce an issue of the Compleat Anachronist pamphlet series which would enable an armourer with fairly average skills to produce a good Japanese armour. The idea has grown to the point where it’s probably too unweildy for such a publication. Also, using the Web to present the information allows me to use color photographs and color illustrations to clarify things that are simply not well presented in a black-and-white printed document. There was another problem, though: specifically, the issue of what constitutes “proper” Japanese armour for use in the Society for Creative Anachronism. Unfortunately, many aspects of Japanese armour fly in the face of thirty-odd years of SCA-style combat. What this means is that, in many instances, a decision will have to be made — namely, are you making armour for combat or for dress? I will present dress armour primarily, as I am a firm believer in authenticity of appearance. Where concessions for SCA combat must be made, I will explain the necessary diversions and provide explanations on how to finish the armour in either functional or authentic form.
The document at: [...] validates as XHTML 1.1 plus MathML 2.0.
I made the appropriate changes for the doctype and the content-type to convert to being a HTML 5 document. [...] I get 2 types of repeating errors [...] I have no idea what the second error is complaining about.
I need an HTML 5 language lawyer to explain what is wrong and how to fix these errors.
Pauvre hère, il a cru les bobards comme quoi HTML 5 était compatible avec XHTML !
If someone doesn't know anything about HTML or other mark-up languages, will such an explanation make sense? Or is there a better way to explain the differences between structural and presentational mark-up to clients and new Web designers?
communicate something online by recording a sketch, optionally with your voice speaking. Any sketch can then be embedded on your blog/ homepage for people to play-back, and you can also point people to your sketchcast channel here (or let them subscribe to your sketchcast RSS feed). Create a tutorial explaining how boomerangs work (and why they don't always return). Draw a doodle of your ex. Explain a math formula. Create a cartoon (you can use the eraser tool to make place for several panels of the cartoon). Get a partner and explain a concept together... voice recording doesn't have to be used by only one person! Write a love letter with lots of sketching inbetween. Create an online Chinese course and explain Pinyin writing. Create a masterpiece and show others how to draw. Explain baseball to Europeans... or explain soccer to Americans! Create a riddle for kids: draw something and the kid has to guess while you're drawing. Draw a manga action scene. Or many other drawing ideas.
This article will explain the actual concepts of Backward Propagation Neural Networks - in such a way that even a person with zero knowledge in neural networks can understand the required theory and concepts very easily. The related project demonstrates the designing and implementation of a fully working 'BackProp' Neural Network library, i.e, the Brain Net library as I call it. You can find the theory, illustration and concepts here - along with the explanation of the neural network library project - in this article. Also, find the full source code of the library and related demo projects (a simple pattern detector, a hand writing detection pad, an xml based neural network processing language etc) in the associated zip file.
Less uses existing css syntax. This means you can migrate your current .css files to .less in seconds and there is virtually no learning curve. The best way to explain Less is to show you some code, so please go ahead and check out the examples below:
The term “2D Barcode” is the name given to the next generation of the barcodes we are used to on everyday packaging and products. Before digging into 2D barcodes, we need to explain the history of 1D barcodes and how we arrived at this point. 1D barcodes are the traditional barcodes we see everyday, they are called one-dimensional because their pattern of thick and thin vertical bars is read in only one direction, from left to right.
text explain it > draw explain it > text explain it > draw explain it > ... Some are hilarious!
While trying to help Dare make his MovieFinder page run in Firefox, I ran into an issue that can make developing AJAX applications a pain: when testing your pages, you need to host them in the same domain as your services. I explain the details of the problem and how the "XMLHttpRequest - Bypass Security" Greasemonkey user script solves it. Note: this script is meant for development only, as it gives the page access to a potentially dangerous API. The default @include is "file:///*", but feel free to restrict it even further to the path for the pages you're trying to tweak. You should never have to @include an http ur
Explain This Image Have you ever seen a picture that simply makes no sense. Here we have collected pictures from around the web that left us scratching our heads and saying "wut". See if you can explain what’s going on in the photos and read the explanations that other people write.
I listen more attentively. I feel more like I am standing next to the participant as opposed to opposite to them. We compensate participants not only with money but also with respect, candidness, and humanness. We adopted their language to explain that we value them and their obstacles; both sides are “participants” in the research.
The central idea we were working on was this idea of de-localized information — information for which I didn't care what computer it was stored on. It didn't depend on any particular computer. I didn't know the identities of other computers in the ensemble that I was working on. I just knew myself and the cybersphere, or sometimes we called it the tuplesphere, or just a bunch of information floating around. We used the analogy — we talked about helium balloons. We used a million ways to try and explain this idea.
LORD OF THE CLOUD
John Markoff and Clay Shirky talk to David Gelernter
An Edge Roundtable
Twitter-Streetart: This demonstrates perfectly just how stupid and pointless twitter is!
twitterstreetart
Twitter-Streetart von Questionmarc (via Urban Prankster) mit einem bemerkenswerten Kommentar darunter.
Das ist schon sehr, sehr lustig. Es ist ja nicht nur so, dass ein paar Journalisten Twitter nicht verstehen und darauf rumhacken. Es ist auch so, dass sobald man irgendetwas über Twitter schreibt, steht mindestens einmal der Kommentar „Dieses Posting ist der perfekte Beweis dafür, wie unglaublich belanglos und banal Twitter doch eigentlich ist.“ Jetzt könnte man sich ja denken, diese Twittmeckermentalität wäre ein deutsches Phänomen – da sah ich obige Streetart und darunter der Kommentar „This demonstrates perfectly just how stupid and pointless twitter is!“ Von wegen deutsch, das ist schlicht ein mentales Filterproblem der Rezipienten. Wenn ich die Worte „Fashion“ oder „Ballett“ lese, dann lese ich gar nicht erst weiter und ich schreibe erst Recht nicht einen Kommentar wie „Dieses Posting ist der perfekte Beweis dafür, wie unglaublich belanglos und banal Ballett doch eigentlich ist.“
Ich glaube, dieser Satz offenbart die komplette Absurdität solcher Kommentare. Geht auch so: „Dieses Posting ist der perfekte Beweis dafür, wie unglaublich belanglos und banal Blogs doch eigentlich sind.“ Bullshit. Ich kaufe mir auch keine Geflügelzüchtermagazine und beschwere mich dann, dass diese voller Geflügelzüchtercontent sind. Wenn man sich gerne und ausschließlich lange Abhandlungen zur Außenpolitik von Papua Neuguinea durchliest, wird man wohl schwerlich ein Fan von Twitter. Aber dann: Don’t fucking read it!
Ansonsten empfehle ich immer noch Julies Anleitung zum Glücklichtwittern: Twitter ist unnütz.
[update] Von Jeriko grade in den Kommentaren gepostet, auch sehr schön:
it’s a lesson in how the future of music is working -
fans are literally (and i mean that….literally) lining up at the signing table after shows and HANDING me cash, saying “thank you”.
i had to EXPLAIN to the so-called “head of digital media” of roadrunner australia WHAT TWITTER WAS. and his brush-off that “it hasn’t caught on here yet” was ABSURD because the next day i twittered that i was doing an impromptu gathering in a public park and 12 hours later, 150 underage fans - who couldn’t attend the show - showed up to get their records signed.
no manager knew! i didn’t even warn or tell her! no agents! no security! no venue! we were in a fucking public park!
life is becoming awesome.
]]>VizEdu is a Telezent visual platform. Our objective is to explain Social Media, Web2.0, Search and Emerging technologies visually. We make learning visual, fun, simple and actionable. In this blog we have a “Zero Text” policy. We use interactive Flash, videos, pictures and presentations only.The human mind is hardwired for pictures. Visuals and diagrams help us understand complex concepts very easily and they stay with us for a long time. Educating people is our passion and this lead to the creation of VizEdu which means Vizual Education.
HTTP Compression is a wonderful technology that accomplishes a lot of different things. It allows faster page serving to clients and lower server costs due to lowered bandwidth (these two being enough for me to implement). There are a handful of articles out there that explain how to implement HTTP Compression in Internet Information Server (IIS) 6.0, but I haven’t been able to find a nice step-by-step article, so I decided to set one up. In this how-to, I’ll briefly explain what HTTP Compression is and how it works in IIS 6.0, and then provide step-by-step instructions on how to implement it because it’s not as simple as flipping a switch. In fact, there are many things in multiple places on the server you have to properly configure to implement HTTP Compression.
A little-understood corner of Unicode is its handling for bidirectional text (The spec is a little dry). While English languages are read left-to-right, plenty of scripts (notably Arabic and Hebrew) are read from right to left. When only a single direction of text is used in a document, it's fairly straight forward, but when texts with different directions are mixed in one document, some difficulty arises in determining direction. This document attempts to explain how bidirectional text in Unicode works and what this means for the web.