DOLFIN is implemented as a C++ library and can be used either as a stand- alone solver, or as a tool for the development and implementation of new methods. To simplify usage and emphasize structure, DOLFIN is organized into three levels of abstraction, referred to as kernel level, module level, and user level, as shown in Figure 1.1. Core features, such as the automatic evaluation of variational forms and adaptive mesh refinement, are implemented as basic tools at kernel level. At module level, new solvers/modules can be assembled from these basic tools and integrated into the system. At user level, a model of the form is specified and solved, either using one of the built-in solvers/modules or by direct usage of the basic tools.
Read the rest of this entry »

• 0 Comments

Here’s how much of a Web 2.0 guy Mark Zuckerberg is: during the weeks he spent working on Facebook as a Harvard sophomore, he didn’t have time to study for a course he was taking, “Art in the Time of Augustus,” so he built a website containing all of the artwork in class and pinged his classmates to contribute to a communal study guide. Within hours, the wisdom of crowds produced a sort of custom Cliff Notes for the course, and after reviewing the web based crib sheet, he aced the test. Turns out he didn’t need to take that exam, anyway. Zuck (that’s what the cool kids call him) dropped out of Harvard later that year.
Read the rest of this entry »

• 0 Comments

This owner’s manual explains the basic instructions of this DVD video player. Some DVD video discs are produced in a manner that allows specific or limited operation during playback. As such, the DVD video player may not respond to all operating commands. This is not a defect in the DVD video player. Refer to instruction notes of discs.

“ ” may appear on the TV screen during operation. A “ ” means that the operation is not permitted by the DVD video player or the disc.
Read the rest of this entry »

• 0 Comments

This document outlines a chapter in the book Implementing Mobile Web 2.0 by Ajit Jaokar published by futuretext (Feb 2009). It is released separately as a stand-alone chapter. Here, we discuss the role of the next generation SIM (Subscriber Identity Module) card, referred to as SCWS (Smart card web server) SIM within Mobile Web 2.0. To explain the background, this document includes other sections from the book so that it becomes as complete document in itself.
Read the rest of this entry »

• 0 Comments

When I quit my day job in the summer of 2006 to bring an idea of mine to life as an Internet startup, I was faced with a huge number of questions and not a lot of clear answers. The excitement of starting a new project was soon tempered by the difficulty of choosing among the dizzying array of possible technical platforms and solutions. While the shelves were full of books focusing on each of the components of a web application, what I really wanted was a look at how all the pieces fit together.
Read the rest of this entry »

• 0 Comments

The concept of “Web 2.0” was born in the first Web 2.0 Conference organized by O’Reilly and MediaLive International in 2004. The concept was further elaborated in the article “ What is Web 2.0 Design Patterns and Business Models for the Next Generation of Software” published by Tim O’Reilly in 2005. Generally, Web 2.0 denotes the paradigm of employing the Web as the platform to deliver and use software. Nevertheless, what user experiences, design patterns and technologies Web 2.0 actually encompasses are not concretely bound and they keep evolving. As described in Wikipedia, “Given the lack of set standards as to what ‘Web 2.0’ actually means, implies, or requires, the term can mean radically different things to different people.”
Read the rest of this entry »

• 0 Comments

“Web 2.0” has become a catch-all buzzword that people use to describe a wide range of online activities and applications, some of which the Pew Internet & American Life Project has been tracking for years. As researchers, we instinctively reach for our spreadsheets to see if there is evidence to inform the hype about any online trend. What follows is a short history of the phrase, along with some data to help frame the discussion.
Read the rest of this entry »

• 0 Comments

“Commenting is a royal pain in the posterior” - “Comments are for weenies” - “I can understand my code quite well, thank you very much” - “Good code speaks for itself” - “No time for that, got to get that code out of the door”. Admit it, you have said some thing along these lines at least once during your coding career. Maybe you even now still are in this kind of frame of mind. Negative attitudes towards commenting may have several reasons:
Programmer’s hubris
Lazyness
No time left for documentation due to deadline constraints
Read the rest of this entry »

• 0 Comments