Beautiful Device Templates to Help Showcase Your App When you’ve poured your heart and soul into designing a truly stunning app, it’s important to help show it off as best as you can. And what better way to show the look and feel of your app than by showing how it would appear running on a device? Whether it’s an iPhone, iPad, Android or desktop app or website, showing it in use gives it some context, adds some visual appeal and can help to make your landing page look smarter and more professional. Of course, it can take a surprisingly large amount of work to create a mockup of a phone, tablet or laptop in Photoshop, but fortunately there are some incredibly talented designers out there who have generously released some templates that they’ve created for free. We’ve put together a collection of some of our favourite device templates – each of these look stunning, and range from intricate and highly detailed, to flat and minimalist. Android Devices by Ian Mintz Flat Apple Templates by Pierre Borodin Perspective App Screens iPhone 6 Infinity
Defcon 2010 - Crawling BitTorrent DHTs for Fun - Scott Wolchok - Part.mov DEFCON 20: Bypassing Endpoint Security for $20 or Less DATA: Data Resources DATA: Data Resources The FERET Database Much of the material on this web site is based upon studies that used the FERET data. The FERET data comes as a 2 CD set containing 14,051 images, of which 3,816 are frontal images. Most previous work on FERET data has focused attention on the frontal images. The FERET data is available for research purposes. The FERET Database website. This site also contains important information about the images, including an overview of how the FERET database is structured. Face Data Preprocessing: Normalization. The FERET 1996/97 studies pre-processed the raw face data. Commonly Used Data Partitions The FERET 1996/97 studies used several important subsets of FERET images. One point of interest is the overlap between these sets, both in terms of people, and in terms of images. This overlap information summarized on our Partitions Overlap Page.
OpenCV History[edit] Advance vision research by providing not only open but also optimized code for basic vision infrastructure. No more reinventing the wheel.Disseminate vision knowledge by providing a common infrastructure that developers could build on, so that code would be more readily readable and transferable.Advance vision-based commercial applications by making portable, performance-optimized code available for free—with a license that did not require to be open or free themselves. The first alpha version of OpenCV was released to the public at the IEEE Conference on Computer Vision and Pattern Recognition in 2000, and five betas were released between 2001 and 2005. The second major release of the OpenCV was on October 2009. In August 2012, support for OpenCV was taken over by a non-profit foundation, OpenCV.org, which maintains a developer[2] and user site.[3] Applications[edit] OpenCV's application areas include: Programming language[edit] OS support[edit] Windows prerequisites[edit]
BSD licenses BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the redistribution of covered software. This is in contrast to copyleft licenses, which have reciprocity share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. Two variants of the license, the New BSD License/Modified BSD License (3-clause),[1] and the Simplified BSD License/FreeBSD License (2-clause)[2] have been verified as GPL-compatible free software licenses by the Free Software Foundation, and have been vetted as open source licenses by the Open Source Initiative,[3] while the original, 4-clause license has not been accepted as an open source license and, although the original is considered to be a free software license by the FSF, the FSF does not consider it to be compatible with the GPL due to the advertising clause.[4] Terms[edit] Previous license[edit] See also[edit] References[edit]
Socket Class Socket provides access to the underlying operating system socket implementations. It can be used to provide more operating system specific functionality than the protocol-specific socket classes. The constants defined under Socket::Constants are also defined under Socket. For example, Socket::AF_INET is usable as well as Socket::Constants::AF_INET. See Socket::Constants for the list of constants. What's a socket? Sockets are endpoints of a bidirectionnal communication channel. Sockets have their own vocabulary: domain: The family of protocols: Socket::PF_INETSocket::PF_INET6Socket::PF_UNIXetc. type: The type of communications between the two endpoints, typically Socket::SOCK_STREAMSocket::SOCK_DGRAM. protocol: Typically zero. hostname: The identifier of a network interface: a string (hostname, IPv4 or IPv6 adress or broadcast which specifies a broadcast address)a zero-length string which specifies INADDR_ANYan integer (interpreted as binary address in host byte order). Quick start¶ ↑
Using the Emulator The Android SDK includes a virtual mobile device emulator that runs on your computer. The emulator lets you prototype, develop and test Android applications without using a physical device. The Android emulator mimics all of the hardware and software features of a typical mobile device, except that it cannot place actual phone calls. It provides a variety of navigation and control keys, which you can "press" using your mouse or keyboard to generate events for your application. It also provides a screen in which your application is displayed, together with any other active Android applications. To let you model and test your application more easily, the emulator utilizes Android Virtual Device (AVD) configurations. The emulator also includes a variety of debug capabilities, such as a console from which you can log kernel output, simulate application interrupts (such as arriving SMS messages or phone calls), and simulate latency effects and dropouts on the data network. Overview
P’unk Avenue — Calendars & Re-, Re-Inventing the Wheel | Philadelphia PA | 2013 In the mad shuffle to push front-end browser technology beyond the limits of sanity, we forgot about calendars. The calendar grid is a common design element, sometimes relegated to a "widget" in a sidebar and other times filling up the screen with excruciating detail about the current month. It's useful: the grid is a design pattern we've translated to the web from the old days of printed calendars (remember those?) So why are they difficult to create? I'm not here to advocate putting more calendar grids out there. What's the deal? My first project at P'unk Ave involved developing an event system for a client. So I hacked and I hacked. The markup in the plugin I chose was written with javascript strings (clearly it was not meant to be edited). I realized two things: Implementation is tied heavily to design. Yikes. Calendars are difficult to build because they involve so much date-crunching. I have a solution I've thought hard about this issue.
CLNDR.js How does it work? CLNDR takes your template and injects some data into it. The data contains everything you need to create a calendar. Here's what you get: Most notable is the days array, which contains an entire grid. We can loop through it in our template to make all of the markup: <% _.each(days, function(day) { %><div class="<%= day.classes %>"><%= day.day %></div><% }); %> Automatic Mouse Events CLNDR looks for next and previous buttons in your template. <div class="clndr-controls"><div class="clndr-previous-button">‹</div><div class="month"><%= month %></div><div class="clndr-next-button">›</div></div><% _.each(days, function(day) { %><div class="<%= day.classes %>"><%= day.day %></div><% }); %> Event Sorting CLNDR takes an array of event objects and weaves them into the days array in your template. If you're looking to get all the events for the month in one array, you've got eventsThisMonth as well.
QtWebKit Un article de Wikipédia, l'encyclopédie libre. QtWebKit est le nom du module de la bibliothèque logicielle Qt qui utilise le moteur de rendu HTML WebKit pour interpréter les différents formats utilisés sur le Web. Présent depuis la version 4.4 de Qt, ce module intègre différentes classes totalement intégrées à la bibliothèque et supporte différents standards du W3C tel que HTML, XHTML, SVG et CSS. Un interpréteur JavaScript est également présent. La version de Qt pour les environnements embarqués, Qtopia, profite également de ce module. Depuis la version de 4.6 de Qt le moteur obtient 100 % au test Acid3. Sécurité[modifier | modifier le code] Il est reproché à QtWebkit de ne pas avoir une politique de sécurité suivie et facile à mettre en place[1]. Références[modifier | modifier le code] Liens externes[modifier | modifier le code] Portail de l’informatique
iOS Quick Tip: From Novice to Expert Even though it's possible to learn the essentials of iOS Development in a weekend, it will take much longer to master the craft. The question then is how do you transition from a novice to an expert? In this quick tip, I will provide you with a breadcrumb trail that may help you on your way to becoming a great iOS developer. 1. Practice, Practice, Practice There are no shortcuts. 2. One of the best strategies to improve your skills and to adopt best practices is to learn from other people's code. Whenever you dive into a library, such as AFNetworking or Magical Record, it is key to not be overwhelmed by the code you read. In addition to learning from other people's code, it is a good learning experience to create your own libraries. 3. This brings me to another key aspect of learning the right way: don't mindlessly copy and paste code. It goes without saying that this doesn't apply to libraries or frameworks that are actively maintained. 4. 5. 6. Bonus: Learn Other Languages Conclusion