text:
You are hereHome ›
Narrow Search
Now showing results 1-7 of 7
This textbook chapter presents a real case study involving the the logging of an old stand forest from three perspectives, that of the environmentalists, the wood products industry, and a politician. An associated writing activity engages students... (View More) in reviewing the different viewpoints, and writing a "letter to the editor" for or against the logging of old growth forest. This is chapter 3 in the unit, A New World View, which introduces global systems science, emphasizing the concepts of environmental diversity, Earth as a system, and sustainability. The resource includes a textbook chapter, integrated hands-on and inquiry activities, links to current news articles, and a suite of pre- and post-unit assessments. A teacher's guide supports classroom use. The resource is part of Global Systems Science (GSS), an interdisciplinary course for high school students that emphasizes how scientists from a wide variety of fields work together to understand significant problems of global impact. (View Less)
Materials Cost: Free
Students will learn about satellites that gather data about Earth systems by reading a NASA press release and viewing a NASA eClips™ video segment. Then students will practice dividing multi-digit numbers using satellite data related to the... (View More) Earth's ozone layer. Common Core State Standards for Mathematics and English Language Arts are identified. This activity is part of the Space Math multi-media modules that integrate NASA press releases, NASA archival video, and mathematics problems targeted at specific math standards commonly encountered in middle school textbooks. The modules cover specific math topics at multiple levels of difficulty with real-world data and use the 5E instructional sequence. (View Less)
Materials Cost: Free
In this field activity, students observe clouds, and are introduced to dichotomous key to classify cloud types. Students also make weather observations of current weather and record and track changes in weather over time. Materials/equipment needed... (View More) include weather instruments (thermometers and barometers) and graph paper. A student self-assessment rubric, vocabulary linked to an on-line glossary, a list of elementary level trade books on weather, and teacher notes and class management suggestions are provided. This hands-on activity is related to NASA CERES Students' Cloud Observations Online (S'COOL) project. (View Less)
Materials Cost: $10 - $20 per group of students
This resource complements a planetarium experience. However, the accompanying educator's guide and companion guides - with lessons on observing and investigating the Moon - are available to download for independent classroom use. The hands-on... (View More) activities, which take up where the show leaves off, motivate students to use their cooperative learning skills to design a self-sufficient lunar station. Working in teams, students develop critical thinking skills, problem-solving techniques, and an understanding of complex systems as they discuss solutions to the essential questions they are presented. (View Less)
This is an activity about the magnetic fields of the Sun and Earth, and the interplanetary magnetic field, or IMF. Learners will engage in a question and answer dialogue, make connections using bar magnet examples and overhead transparencies, and... (View More) ultimately write an assessment of concepts learned. This is Activity 1 in Session 3 of the Exploring Magnetism in the Solar Wind teachers guide. (View Less)
Materials Cost: $1 - $5 per group of students
This is an activity about auroras and the scientific terminology used to describe them. Learners will read an article that provides an introduction to specific terms and concepts related to auroras and auroral substorms and examine photographs of a... (View More) 2003 aurora and descriptions of an 1859 aurora to identify the various phases of auroral substorms. This is activity 11 from Exploring Magnetism: Magnetic Mysteries of the Aurora. (View Less)
Materials Cost: Free
This is an activity about Earth's magnetism. Using polar coordinates and several sets of provided information, learners will plot the position of the magnetic north pole to investigate its movement over time. This is the sixth activity in the... (View More) Exploring the Earth's Magnetic Field: An IMAGE Satellite Guide to the Magnetosphere educators guide, pages 23 to 28. (View Less)


text:
Republican lawmakers on Tuesday approved vastly different plans to fund public assistance for the poor and protect children from abuse and neglect, with a House panel voting to cut more than 1,000 state jobs, or nearly 9 percent, from the Michigan agency that handles welfare, food stamps and foster care.
Republican lawmakers on Tuesday approved vastly different plans to fund public assistance for the poor and protect children from abuse and neglect, with a House panel voting to cut more than 1,000 state jobs, or nearly 9 percent, from the Michigan agency that handles welfare, food stamps and foster care.
A Senate subcommittee later approved a Department of Human Services budget with 270 fewer funded positions than in the current fiscal year. That version is closer to Gov. Rick Snyder's proposal — which would trim about 30 jobs — and the Senate's job reductions in the child protective services division would not happen if the state has trouble meeting caseload-to-staff ratios required under a court-ordered mandate.
Differences must be resolved after the spending plans clear the full House and Senate and before lawmakers' June deadline to pass the next state budget.
"This is a pretty hard body blow when we've made significant inroads here over the last couple years across all programs and platforms of this agency," DHS spokesman Dave Akerly said of the House budget. "We don't feel that it's in any way, shape or form a realistic budget."
Three juvenile justice facilities also would close and the youth offenders sent to private facilities under the House plan, which is in stark contrast to what the Republican governor proposed. The proposal drew criticism from Democrats who said caseloads would rise 7 percent for already stressed workers and warned the budget would hamper Michigan's ability to comply with a legal settlement mandating that it improve conditions for children needing foster care and protective services.
"We cannot afford to have any more children under our care killed or abused or neglected. It's our responsibility as a state," said Rep. Rashida Tlaib, a Detroit Democrat.
The cuts to the 12,000-worker agency are needed because Republicans will not support Snyder's call for a surcharge on all power bills to cover emergency energy aid for low-income residents, said Rep. Peter MacGregor, a Republican from Kent County's Cannon Township and chairman of the House human services budget subcommittee.
"The governor wants a surcharge. My caucus will not support a surcharge," he said. "So we have to find the money within the budget, and that's what I did."
He said the detention facilities for juvenile offenders are too expensive and money can be saved by turning over their care to private operators. The facilities are in Escanaba, Grayling and Whitmore Lake.
MacGregor also said DHS managers could handle overseeing more front-line caseworkers.
Sen. Bruce Caswell, a Hillsdale Republican and head of the panel in charge of the Senate's human services spending plan, said he found a way to cover most of the $60 million cost of the low-income heating assistance program without Snyder's proposed surcharge on energy bills. His plan would shift federal money into the program, avoiding the amount of cuts proposed by the House.
The Senate proposal also would not close the three detention centers.
"Intelligent people can differ. That's why we have the process in place that we have. The governor has a budget — the House, the Senate. We'll reach compromises and come up with the best ideas from all three," Caswell said.
Ray Holman, spokesman for United Auto Workers Local 6000, the union for many DHS workers, said Michigan should not eliminate jobs of caseworkers charged with protecting children from abuse and neglect along with employees who determine eligibility for Medicaid and other safety-net programs.
"We're just getting stabilized now on child welfare issues. This budget is regressive and puts us back in a place where kids are going to be at risk," he said.
A March report by monitors appointed by a federal judge found that Michigan had reduced the number of child welfare caseloads per worker, thanks to a hiring blitz in 2011. The report also said the state had trouble determining how many children are living under one roof.
A 2006 lawsuit by New York-based Children's Rights led to an agreement to make changes at the child welfare agency.
House Bill 4217: http://1.usa.gov/149B7Xm
Senate Bill 192: http://1.usa.gov/16NQAYQ

subset: commoncrawl


text:
Little Erin Merryweather
Dir. David Morwick
The grisly murders of several students at a quiet college campus tie in with recent sightings of a red-hooded figure creeping around the local woods. Student Peter Bloom decides to investigate, and before long realises that the killer, who has a connection to the school library, is also obsessed with fairytales. Peter must act quickly to figure out the bizarre modus operandi and stop the killer before she strikes again…
'A flash of red... Then you're dead.'
I bought Little Erin Merryweather for £1 in a local discount shop. I wasn't really expecting much; so was pleasantly surprised when it actually turned out to be not half bad. It's not a great film, but it has its fair share of interesting moments and startling imagery. And it was £1.
An intriguing opening sets the fairytale-image drenched scene, as a young college student is lured into the woods by a mysterious figure in a red cape, only to be set upon and gutted. Even though we don't see the act, the utilisation of queasy sound effects leaves little to the imagination. The red-caped figure and snow-covered woods ensure the fairytale connotations practically drip off the screen…
He foolishly threw caution to the wind:
See how simple it is to creep,
When playing this game of hide and seek?
Slice the belly – what did she see?
Not a trace of father; completely empty.
She gave him his fill, though not so clever,
To make him a prisoner in his garden forever…"
The tale of Red Riding Hood has been adapted and reinterpreted for film before, in titles such as Freeway, the forthcoming Red Riding Hood and The Company of Wolves. It has often been interpreted as the documentation of the blossoming of female sexuality – the big bad wolf standing in for (aggressive) male desire; innocence encountering primal, guttural lust. Angela Carter ain't got nothin' on me. Little Erin Merryweather updates the tale to feature Red Riding Hood as a serial killer with severe psychological hang-ups originating from her molestation as a child. The 'big bad wolf' in her past, being her father. As fucked up as it sounds, the film is fairly subtle in its approach to these themes, with flashbacks depicting the girl's abuse leaning on suggestiveness rather than crass explicitness. Indeed, the flashbacks have a strangely giallo-esque feel to them, with an emphasis on nursery rhymes and disturbing children's drawings exhibiting an obsession with 'dirty handed men.'
All grown up now, Erin Merryweather is a timid university librarian by day, and a frenzied, red-hooded and be-caped slasher villain by night. She begins offing the male populace on campus when memories of her childhood are triggered – mainly when she encounters men with dirty hands. And as bad luck would have it, the guys on this campus obviously need to brush up on basic hygiene… Leading the tender-footed investigation, as the cops seem as inept as most horror movie cops, are student Peter Bloom (writer/director David Morwick) and student reporters Sean and Teddy (Marcus Bonnée and Brandon Johnson). When they realise the killer's calling card is filling the stomachs of her victims with stones, they begin to uncover an unhealthy obsession with fairytales that may help them solve the case. Luckily they have their gravel-voiced lecturer Dr Paula Sheffield (Elizabeth Callahan) on hand to prompt debate and tell them to fuck off to the library and do some research. Turns out she's a former criminal psychologist. Natch. Being students and prone to intellectual debate, various scenes feature conversations about trauma, deviant behaviour, childhood and debates about when victims become victimisers… This all of course ties in with the murder mystery at the heart of the film.
The fairytale images that pepper the narrative are as striking as you'd expect – a discarded broken doll here, a shock of blood or a red cape on white snow there. Despite the low budget the film looks rather beautiful, and it often feels much older than it actually is. And then there are the sketches drawn by the titular character – Grimm-like illustrations that give us a further peek into her warped mindset. Murderous Erin is portrayed sympathetically by stage actress Vigdis Anholt. At times she seems to be a little girl trapped in a woman's body; at other times she is revealed to be manipulative and obviously unhinged. The script often calls for her to be the 'weird girl' on campus, and she can usually be seen skulking about in a red cloak and acting all 'mysterious,' i.e. wide-eyed and distant. Anholt's big expressive eyes, conviction to the role and steadfastness in avoiding obvious histrionics ensure the audience feel sympathy for the disturbed and pathetic Erin.
What sets Little Erin Merryweather apart from many recent horrors is the lack of female protagonists (aside from our villainess and the gravel-voiced lecturer). Also unexpected is the unveiling of the killer at the beginning of the film, stripping many of the later events of any tension or mystery. We know who the killer is, why she kills; but we have to wait until the characters figure out what we know, in order for the action to move forward. Maybe this is tension. Maybe not. Morwick makes a number of strange choices – not all of which are successful – though he seems to be making them in an attempt to subvert convention, and his flashes of creativity aren't restricted by the often workmanlike story or plot developments. While events verge on the ludicrous, his competent direction keeps things ticking over just enough to retain your attention – even if you do see what's coming from a mile off. This isn't your average straight to DVD slasher movie though.
A strikingly shot, if somewhat by-the-numbers thriller that is elevated from the doldrums by a dedicated cast and intriguing premise.


text:
I'd like to say that I'm not sure that defining synchronous and asynchronous are going to help us very much. I'd like to offer a quote from a book Phil Bernstein and I wrote in 1997 on transaction processing ("Principles of Transaction Processing," page 74): "TP application programs communicate with each other when they run in a distributed setting on different computers. Even on a single computer, for modularity reasons, it's often convenient to break up the application programs into separate processes. Application programs therefore have to communicate between processes, which means the programs have to exchange messages. There are three ways to do this: 1. Use remote procedure calls, which mimic the behavior of local procedure calls within a single process. When a program in one process calls a program in another process (in another address space), it does so by calling a procedure and getting a value returned just as if the two procedures were running within a single address space. 2. Explicitly send and receive messages, called peer-to-peer messaging. Rather than use a procedure call with a return, application programs issue operations that send and receive messages. 3. Move messages among queues. An application sends a message from one program to another by putting the message in a queue. The queue is a third object, with which both programs communicate. One program enqueues the message to the queue, and sometime later the receiver program dequeues the message from the queue. These communication paradigms apply to all distributed applications, not just in TP. ..." I think this approach is much clearer and more helpful than trying to define how the technology works under the covers, or describing the messaging systems on which these paradigms are based. It's clearly possible to use a synchronous protocol to implement a message queuing paradigm, and possible to implement a remote procedure call paradigm using peer-to-peer. If we look at the capability of Web services based communication technology from this perspective, we can fairly easily decide which of these paradigms it really supports, and how, rather than argue over synchronous vs. asynchronous, which is really a detail rather than an indication of application level behavior. Eric -----Original Message----- From: Champion, Mike Sent: Sunday, March 16, 2003 11:18 AM To: email@example.com Subject: Friendly amendment to friendly amendment (was RE: Friendly amendm ent #2c [Re: Straw poll on "synchronous" definitions] -----Original Message----- From: Anne Thomas Manes [mailto:email@example.com] Sent: Saturday, March 15, 2003 6:12 PM To: Walden Mathews; Christopher B Ferris; email@example.com Subject: RE: Friendly amendment #2c [Re: Straw poll on "synchronous" definitions] The biggest issue I have with Ugo's definition (and all the others) is that they tie synchrony with blocking versus non-blocking. Synchronous means "at the same time". Asynchronous means "not at the same time". Whether or not the sender has to wait idly for a response is a separate issue. An interaction (one-way, two-way, or multi-way) is synchronous if the sender and receiver must communicate at the same time (the reciever must be available to receive the message when the sender sends it). A one-way message is asynchronous if the sender and receiver do not need to communicate at the same time (the message may be stored and delivered at a later time). I must say that I like Anne's wording that synchronous means that "the receiver must be available to receive the message" better than notions of blocking or simultaneity. What about changing Ugo's suggestion to: Asynchronous: A request/response interaction is said to be asynchronous when the request and response are chronologically and procedurally decoupled. In other words, the client agent can process the response at some indeterminate point in the future when its existence is discovered, for example, by polling, notification by receipt of another message, etc. Synchronous: A request/response interaction is said to be synchronous when the client agent must be available to receive and process the response message from the time it issues it issues the initial request until it is actually received or some failure condition is determined. The exact meaning of "available to receive the message" depends on the characteristics of the client agent (including the transfer protocol it uses); it may, but does not necessarily, imply tight time synchronization, blocking a thread, etc.Received on Sunday, 16 March 2003 11:58:04 UTC
This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:05 UTC


text:
Contact: Vicky Wong
Tel: +86-523-80235941
Fax: +86-523-80235286
Mobile: +86-13852631280
Email: firstname.lastname@example.com
Facebook: https://www.facebook.com/aokaifilter
Twitter :https://twitter.com/aokai88
Contact NowWater and Oil Proof and Anti-static Polyester Membrane Filter ClothWater and oil proof and anti-static polyester membrane filter cloth Water proof treatment Polyester water and oil repellent filter cloth can be applied in the environment with high moisture,such as iron and steel plant, cement plant, power plant .polyester water and oil repellent filter cloth...Read More
Contact NowWater and Oil Proof and Anti-static Polyester Membrane Needle FeltWater and oil proof and anti-static polyester membrane needle felt can be applied in the environment with moisture such as iron and steel plant,cement plant,power plant. polyester water and oil repellent filter cloth has...Read More
Contact NowNormal Temperature and Cheap Price and High Cost Performance White Color Polyester Needle FeltNormal temperature and cheap price and high cost performance white color polyester needle felt JiangSu AoKai concentrate in manufacture Polyester(PET) Non-woven needle felt for 15 yeas,Polyester(PET) Non-woven fabric needle felt has many coating,membrane...Read More
Contact NowHigh Temperature and Water and Oil Proof Aramid Needle FeltHigh temperature and water and oil proof aramid needle felt is a economic products for the operating temperature due 200℃ to 240℃,according to the different work environmental do the treatment such as: water oil repellent, membrane.Read More
Contact NowWater Proof Acrylic Needle FeltWater proof Acrylic needle punched felt is made of PAN(polyacrylonitrile) fiber through needling production process. Air permeability is 14 m3/m3.min,operation temperature is 125 degree C, surge temperature is 150 degree C.Read More
Contact NowWater Proof Aramid Filter ClothWater proof aramid filter cloth Metamax filter cloth is a kind of high temperature gas filtration material,it is the collectively name of nomex fiber American and conex fiber japan.Metamx fiber is belong to aramid Polymide fiber.its biggest feature than polyester filter cloth is excellent high...Read More
Contact NowWater and Oil Proof PPS Filter ClothWater and oil proof PPS filter cloth has high temperature resistance,high strength and excellent chemical resistance,it can keep excellent filtration performance and longer use life.PPS filter cloth can not be used in high oxygen content.Read More
Contact NowNormal Temperature Acrylic Needle FeltNormal temperature acrylic needle felt is used where polyester is not suitable.It has a higher tensile strength than polyester felt. Acrylic needle felt produced by Germany international advanced equipment and select excellent flow fine denier fiber, mixing the fiber uniform...Read More
Contact NowHigh Temperature Nomex Filter ClothHigh temperature Nomex filter cloth has a high tensile strength and a maximum continuous working temperature of 204ºC.Nomex filter cloth selects the No.1 international fiber brand Dupont nomex fiber USA,The cross section of the fiber is different shape,average line density and...Read More
Contact NowWater repellent Aramid Filter ClothWater repellent Aramid Filter Cloth Face to the practical working condition of our industrial ,the normal Aramid Filter Cloth can not satisfy the customer's demand in some high moisture occasion .our company can do the after treatment of water and oil repellent to form the water and oil repellent...Read More
Address: No.80, Fuqian Road, Chengbei Industrial Park Economic Development Zone, Jingjiang City, Jiangsu Province, China
Tel: +86-523-80235941
Fax: +86-523-80235750
E-mail: email@example.com


text:
rhodee necesitaba un nuevo diseño de logotipo y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 201 diseños de 35 diseñadores freelance.
For starters we (Denis, Jeremy, Omkar) decided to start a company and "Go Social."
We think technology should allow anyone to share ONE goal (that they would be willing to spend time implementing) and ask ONE question (are you a causemaker?) with anyone.
So what is a Causemaker? They are a community of 'design & do' types that don't go on new adventures with old plans.
Causemakers.com is angling to be the global "doing" platform for Causemaking-types.
So we are creating a platform with the following benefits:
1. Users and NGOs 'agree' on how volunteer time is spent and when they volunteer, and
2. Users can start volunteer projects quickly by tapping their social networks and other Causemakers to create, collaborate and implement volunteer projects.
Our audience are "Internet-Enabled Volunteers".
Some characteristics they share are:
1. Gender-majority female,
2. Age-between the ages of 16 and 54 years old
3. Internet-Have access to the internet via mobile or traditional devices
4. Service-Have spent time, unpaid, doing something that aims to benefit the environment or individuals or groups other than (or in addition to) close relatives for an organization or informally in the last year
We are looking for a mark and typeface (of our brand name). The logo will display prominently on our site. Your vision will be used for physical applications too (stickers and stationary). It will travel with us on our social networks.
General Expectations
1) The logo must have three colors max-and one of them is white.
2) We want a logo where the mark or typeface can be freestanding if need be.
3) We are open to the use of nodes, spokes, hubs, quadrangles or circles
There are some things we would rather not see for either the mark or brandname:
1) The use of kawaii illustration, shadows, cursive letters, speech bubbles, megaphones, badges or buttons.
Desirable Brand Name Typeface
1) Causemakers should appear as a compound word.
2) We are interested in our brand name being built from the following fonts: myndraine or delicious and/ spinach. They are all free and links to these fonts can be found on http://www.fawnt.com.
3) We want to see the word "Cause" drafted with the myndraine or delicious font.
4) "Makers" should be in spinach font.
5) For the word "makers" please show us a pixel effect.
6) The pixels could be circles or squares and the individual elements you choose should have a margin greater than 1. The elements should not share borders.
Summary + Inspiration
We want a logo that reflects the boldness of our brand name and the spirit of collaborative disruption.
To get a sense of the space here are some URLs: crowdrise.org, dosomething.org and onebrick.org. Also, here are sites that we like: loggly.com, gigaom.com.
Here is a CHALLENGE: Our logo must represent volunteering in the 21st century ---social benefit in a technology-driven world. We'd like to see how you blend those two concepts.
To give you an idea of representative icons we've attached two images. One is the wi-fi icon. The other a pixelated white glove.
Can you create a mark blending the two images?
Original vector artwork (Color / Grayscale / Mark-only / Type-Face)
Font names that were used.
We are excited and grateful that YOU are sharing your time, talent and treasure with us. Who knows-you may be Causemaker in the very near future!
Descubre cómo funciona un concurso de diseño u obtén más información sobre nuestros servicios de diseño de logo.


text:
Does virtualisation hamper security in your organisation?
Speak your brains in our latest survey
What's not to like about server virtualisation? You can consolidate infrastructure to save money, stand up new servers quickly and without scrabbling for hardware budget, and generally improve the flexibility of your IT environment.
Past reader research studies, however, have highlighted some of the less desirable side effects of virtualising your server estate – VM sprawl, keeping dormant VMs properly patched and configured, backing up virtual landscapes, and so on.
In our latest survey of systems security and access, we are picking up on this and asking whether VM configuration, control and management challenges have an impact from a security perspective.
After all, if you don't have a proper handle on which VMs exist, what they are used for and what their patch level is, that's a bit of a security black hole. And what about VMs that actually contain data – how do you make sure security and privacy are protected when they are shut down then spun up again in a different context?
Some of the respondents in our survey so far have quite firm views on such things, but what's your experience?
Let us know you thoughts on these and other matters by clicking here.


text:
Picked up a nice bunch of asparagus yesterday from a not-quite local but nearby source. And, because I could, I decided to roast it.
Roasting asparagus is pretty simple, and you can turn it into an awesome gratin by just topping it with bread crumbs, or blue cheese or Parmesan, or whatever else you like. (There's a discussion of this here and, as it's asparagus season, you might also want to look at this Mini, if you haven't already.)
But I happened upon the tiniest piece of guanciale in my freezer. When I say "tiny" I mean, less than two ounces; maybe one. So I took the easy way out. Peeled the asparagus (they were fat), and put them in a cast iron skillet with the diced guanciale, salt, pepper, and – because there was so little guanciale – a little bit of olive oil.
I roasted that for about 20 minutes, shaking the pan after 10 and 15. And talk about impact: it tasted like a meat dish. Made me wonder what other treasures are lying around in my freezer…


text:
JasonAndrewWrobel necesitaba un nuevo diseño de logotipo y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 154 diseños de 35 diseñadores freelance.
Jason Wrobel
The new logo is a cornerstone in a completely new branding process. I, Jason Wrobel, am a nationally-renowned certified organic gourmet raw foods chef taking my identity, personality, and presence into the mainstream media this year, with a new interactive website and television show in the works. I am the first green, organic raw food chef to appeal to a mainstream American audience – teenage skateboarders in California really enjoy my yummy food as well as middle-aged Midwestern housewives who want to feed their families healthy, delicious, beautiful food.
The logo and the new brand will encompass the essence of my personality – fun, sexy, engaging, entertaining, hilarious, and informative – and meld it with the nature of my food – healthy, organic, raw, light, nutritious, tasty, and easy-to-prepare. My specialty is healthy, amazingly delicious desserts.
Check out my Youtube TV Channel to see me in action, slinging the healthiest decadence in the known Universe:
Also, for images of me and my food creations, dig this:
The mainstream, baby! This food is no longer fringe, as many people across the world are desiring healthy, sustaining foods without sacrificing taste, texture, or indulgence.
I've played to crowds of hundreds at events and conventions, with middle-aged housewives who want the best cheesecake ever cheering me on, to tattooed punk rock musicians who really dig my mint chocolate chip ice cream sundaes. Truly, I'm bridging some wide target markets with the power of my personality and the mainstream media.
The logo has to bring the fun and the funk to everyone! Dig? I'm an entertaining, outrageous, yet very loving and approachable guy. Your little cousins would want to hang with me and your Grandma would love to pinch my cheeks. Let the logo be an extension of that essence to my fans and audience.
The new logo must convey the elements listed above. The design I'm looking for must be clean, professional, simple, engaging and accurately convey my essence to a wide, mainstream audience and market.
Images that immediately came to my mind are (playing on the name Jay-Sun): the sun, sun/solar rays, leaves, flowers, fruits, vegetables, nature, electric sparks, etc. Something visually that will appeal to the mainstream without looking too "granola" or "hippie". This cuisine is way beyond the counterculture and so must be the logo and new branding.
If you're feeling REALLY ambitious, draw or create a caricature, line drawing, silhouette, or picture of me for the logo. That would be cool to see - me as a cartoon!
If you really want a frame of reference, check out the logo for mad food scientist and world-traveling Food Network star Mr. Alton Brown:
So, in essence, like Alton's logo, I'm looking for my name to be incorporated into the logo – Jason Wrobel – along with some unique, dynamic visual elements – for the new design.
Be elegant, be simple, be radically creative, but most of all, be effective in conveying my essence and personality to a wide-ranging audience.
The sky's the limit! Show me what you've got and thanks for taking this project on!
All the best of luck to you!
Descubre cómo funciona un concurso de diseño u obtén más información sobre nuestros servicios de diseño de logo.


text:
Ever have a favorite "hot!" book you kept by your bed, riddled with dog-eared pages marking the best parts? Some scenes, whatever the reason, seem to have the staying power to follow us through a lifetime.
My favorite sex scene of all time (no laughing, now!), is in Anne McCaffrey's young adult book, Dragondrums. Part of her Harper Hall Trilogy, this book continues the saga of Menolly and Sebell, two harpers on the planet Pern, a land of soaring dragons and their enchanting miniatures, the fire lizards.
I read Dragondrums for the first time about a million years ago. My pre-teen heart had fallen for Sebell from the start, and through three books, I'd waited to see what would happen with him and Menolly. The big moment came as the two were stuck on a becalmed boat, with their miniature dragons mating above them.
I don't think the entire sex scene could have been much longer than a paragraph, and in the way of young adult books, there was a lot more metaphor than detail. But it was the first sex scene I'd ever read, and I was hooked. Wow! Now this, this was the good stuff!
As my sister gleefully reminded me recently (in front of my husband and teen daughters), I carefully dog-eared the page of that fateful scene, and drew a cheerful little star next to the appropriate chapter number. My girls (who've read the book themselves) got a big kick out of that one. And my husband laughed even louder. Sisters can be a mixed blessing.
But my sister's tongue-in-cheek comment that Dragondrums may be part of the reason I ended up writing erotic romance might not be far from the mark. Some scenes have staying power, and for me, that was one of them.
What about you? Any sex scenes, sweet or wild, that have followed you over the years? Any favorite bedtime books stashed away in your bedside table drawer? Maybe a juicy quote you want to share?
Happy reading!
Eden Rivers
My Blog


text:
I just finished reading The Emotion Machine: Commonsense Thinking, Artificial Intelligence, and the Future of the Human Mind by Marvin Minsky It was a really interesting book which I really recommend. I would like to highlight this part from the first chapter "Falling in Love"
On the surface such statements seem positive; they're all composed of superlatives. But note that there's something strange about this: most of those phrases of positive praise use syllables like 'un–', '–less', and 'in-'un-', '-less', and 'in-'—which show that they really are negative statements describing the person who's saying them!
Wonderful. Indescribable,
—— (I can't figure out what attracts me to her.)
I scarcely can think of anything else.
—— (Most of my mind has stopped working.)
Unbelievably Perfect. Incredible.
—— (No sensible person believes such things.)
She has a Flawless Character.
——(I've abandoned my critical faculties.)
There is nothing I would not do for her.
—— (I've forsaken most of my usual goals.)
Positive statements might hide what we really are thinking about. Did you heard in a wedding someone saying "He's a very lucky man for marring her"? What that person probably meant was something like: "He's lucky because I can't understand how a woman like her could marry a man like him" or "He's lucky because she could find a better man"
Reading about iOS7 Design Resources in the iOS Human Interface Guidelines I found a similar approach comparing iOS 7 and iOS 6. Look at the screenshot:
This looks wrong. One thing is to talk about the improvements of iOS 7 and the changes they made, and another thing is to trash your previous product. They are not doing it explicitly, but they are doing it indirectly.
- Deference. The UI helps users understand and interact with the content, but never competes with it. (The previous design competed with the content and wasn't clear)
- Clarity. Text is legible at every size, icons are precise and lucid, adornments are subtle and appropriate, and a sharpened focus on functionality motivates the design. (Icons weren't precise and adornments were not appropriate)
- Depth. Visual layers and realistic motion impart vitality and heighten users' delight and understanding. (Previous design lacked vitality and was hard to understand)
These three positive statements would be just fine if they were announcing iOS 7 as a new product for the first time. In that case the listener wouldn't have a previous model to compare with and would use the hidden negative statements on the competition. But comparing in this way your current product with the previous one is just trashing your previous work. That damages the credibility of what Apple continually claims about their products, depicting them as the best in the market. How could they say they have the best Mobile OS if they are trashing it when the next version comes out.
I think that the right thing to do should be to avoid direct comparisons between your own products and only point out the evolution, the improvement, the new features instead of sending subliminal messages to costumers saying "today we sell you gold and tomorrow we will call it shit".


text:
Author Notes:
The humble Necci is a sort of crepe made with chestnut flour, eaten plain or warm with a dollop of fresh sheep's milk ricotta cheese. The recipe comes from the forest-filled Tuscan region of the Garfagnana, near Lucca, where chestnuts have been a traditional staple for centuries.
Chestnut flour is gluten-free and also has a naturally low moisture content, which means it keeps well. It has a naturally sweet taste and falls apart easily when cooked, so is often mixed with other flours or olive oil to help hold it together.
There is something very medieval about making Necci the traditional way. To start with, you need a good fireplace with a roaring fire and glowing coals and a pair of cast-iron "testi" – two flat, heavy iron plates, about 25 cm in diameter, with long flat handles. Nothing says "Medieval" like cast-iron.
What's unusual about these necci is that rather than spread the batter and flip it like a pancake, the batter is spooned onto the lightly greased "testo" and is spread and flattened by placing the other testo on top. With both hands, the testi simply get flipped over the fire together until both sides are cooked evenly. The necci are then piled between chestnut leaves until the batch is ready to eat.
The simple batter – water and flour – is traditionally eaten alone or with some ricotta, but it also lends itself well to savory fillings of prosciutto and cheese, or sweet fillings such as nutella. My personal favourite is a bit of ricotta and a drizzle of chestnut honey. But you can be inventive...
The recipe couldn't be simpler but it's the flipping that's tricky if you don't happen have a pair of testi handy. While the traditional recipe calls only for chestnut flour and some tap water to make a slightly thick batter (thicker than crepe batter), I find that if you're going to make it on a regular pan and attempt to flip it over, you'll need to add a little olive oil to the mixture to stop it from simply falling apart as soon as you touch it. Greasing in between each neccio really helps too.
As with most street food, it always seems to taste better when you're standing on the street eating it, so where I go to get my Necci fix in Florence where I live is the Santo Spirito market, the 2nd Sunday of the month. The elderly couple that still prepare Necci the traditional way and cook them on the spot with cast-iron testi seem like a postcard from another era. And for 2.50 euro each with fresh ricotta, it's a snack I never pass up when I see it. - Emiko
The humble Necci is a sort of crepe made with chestnut flour, eaten plain or warm with a dollop of fresh sheep's milk ricotta cheese. The recipe comes from the forest-filled Tuscan region of the Garfagnana, near Lucca, where chestnuts have been a traditional staple for centuries.
Food52 Review: This sweet, nutty, slightly funky crepe couldn't be easier to make (the batter has only 3 ingredients) and, filled with ricotta and drizzled with chestnut honey (or whatever honey, really), it makes for a delicious -- and gluten-free -- breakfast or dessert.
Note: If your batter is so thick it's misbehaving, shoot for Emiko's helpful visual description (it should be slightly thicker than crepe batter). - kristen miglore —Kristen Miglore
Serves: 2 greedy people
ounces Chestnut flour (about 2 cups)
cup water
tablespoon olive oil
olive oil for greasing
a tablespoon of ricotta for each neccio
a drizzle of chesnut honey (optional)
- In a large bowl, mix the flour with enough water to get a smooth, dense batter, slightly thicker than crepe batter. Add olive oil and a pinch of salt and mix again. Heat and lightly oil a frying pan. Add a couple of spoonfuls of the batter to the pan and tilt slightly to evenly coat the pan (note that this batter does not move as fluidly as crepe batter).
- Cook for about 2 minutes or until you see that the top of the batter looks dry. Loosen with a spatula, flip over and cook the other side for one minute. Set aside and keep warm. They can be eaten plain, as is, or try them with a spoonful of fresh ricotta spread on each, roll them up and serve drizzled with honey.
- This recipe is a Community Pick!
- This recipe was entered in the contest for Your Best Street Food
More Great Recipes:
Crêpe|Tuscan|Chestnut|Honey|Ricotta|Cheese|Make Ahead|Vegetarian|Gluten-Free|Appetizer|Snack


text:
enter your email address and we'll send you your shopping cart:
Robby's room looked like a scene from a sci-fi movie. Vials filled with strange purple powder; a small mountain of rock crystals in all the colors of the rainbow. Robby and his friend Chuck sat in the center of it all, with lab coats, goggles, and bunsen burners flaming.
"Hand me Particle Specimen 154-A." Robby instructed. Chuck typed a few numbers into his laptop and then reached into the sock draw, pulling out a baggie filled with Pop Rocks Candy. Robby grabbed it from his hands quickly, examining the small pieces of bubble gum with a microscope. Just then there was a knock on the door. A woman entered.
"Oh, sorry dear. I didn't realize you two were still playing in here." She closed the door, sighing to herself. She wondered when her husband would stop playing with the powder candy and maybe do some dishes.


text:
Comments on Responsive Images: How they Almost Worked and What We Need
by Mat Marquis
77 Reader CommentsBack to the Article
What does the author think of solutions like Sencha io.src?
A nice solution to harness <video>-like functionality. But rather than some new element like , I'd rather see the <img> element accept multiple sources like video does.
This really hits the nail on the head - the responsive web should live in markup! Developers shouldn't have to rely on various forms of scripting to achieve what, in theory, is a pretty simple (and increasingly necessary) task.
In all honesty I would hope by the time something like this was implemented bandwidth limitation issues would be nil; though, all the mobile bandwith caps out there are telling me I'm an idiot.
Hi there,
there's a mailing list here: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034494.html but without my latest proposal (http://novolo.de/blog/2012/01/19/what-happened-to-responsive-assets/).
So picture element wouldn't work best as described in mailing list. And we don't even need a new element in my mind but need only to do it my second way (described in my article). My first approach with attributes would work, too, but is not that pretty.
So, let's hope that one of the good solution is coming up soon to the spec. And, by the way, also recognize my CSS3/4 approach which would do the same for layouted styles.
I've heard several people say they are against using user agent detection. Could anyone elaborate as to why?
Just as HTML/CSS needs to mature to better adapt to different devices, it seems like if the user agent strings matured and became more descriptive they would be extremely useful.
I first ran into this issue about 10 years ago while developing content for mobiles, and about 6 years ago while developing a social network aimed at (pre-smartphone) mobile devices I started using user agent detection as this was the only viable solution I could come up with. I know there's a lot of them but there are ways around this, with the most obvious one being WURFL and a bit of server-side scripting to keep the database updated.
The platform I use for building websites now automatically detects the device type (and any needed media size properties) and stores them for the life of the user session (either in a cookie or in a session query string matched to a database record for devices that don't support cookies) which allows me to implement responsiveness in markup by only ever serving the right image size in the HTML img tags in the first place (as well as sorting out which type of video embed to use, if any).
Related to this is the subject of bandwidth. One of the key issues I've had in building mobile-suitable sites is not actually bandwidth (although this is always an issue), it's how large a page (combined HTML, markup and images) a device can actually display, with the most visible one being the old Motorola Razr v3. Some versions of this handset had a whole 10k of RAM available for rendering pages. Device detection allowed me to cater for even this restriction by automatically breaking large pages into smaller chunks for delivery to such devices by detecting the device in advance from the user agent.
However with most modern devices now reporting screen sizes (or easily derivable screen sizes based om generic user agent strings) and it very rare that a non-smartphone is being used to access the sites I build I'm actually finding less need for specific device detection at all.
These are some fantastic methods. As a backend guy, I can plan for and supply the frontend with whatever fields they like, but knowing the possibilities is more important. Thanks for a great article!
@matudnorthrup: I think the article says this in so many words, but while UA detection is probably the best tool for this task at the moment, that doesn't negate the need for implementation of a standards, simple, front-end approach to this problem. UA is a tool that should never be ignored, but it's an increasingly complicated tool to use for negotiating situations like this one, especially when you're trying to build against future browsers rather than working around known issues of past ones. As Mat mentioned, the video and audio elements have already set a nice example of how markup alone can address this very problem, and if we can follow that model, it'll greatly simplify our job as developers down the road.
Hey Mat,
have you seen http://adaptive-images.com/
can you give your thoughts on that method as well.
thanks for the great article!
Another similar proposal also was made by Bruce Lawson in late 2011: http://www.brucelawson.co.uk/2011/notes-on-adaptive-images-yet-again/. I dig it—hope we get something supported natively by the browser soon .
Interesting. I wound up doing the same thing with data attributes and javascript, and learned screen size isn't always a good proxy for how big the images should be. (I have at least one page where the tablet-range layout actually needs a bigger photo.)
So if we're going to ask for a pony, how about the one we really want: an API (both js and media query, please) to determine bandwidth.
Especially as Apple ships devices with denser and denser screens, we're going to start seeing lot's of small devices that actually *do* want high res images. On the other side, it'd make a lot of sense of serve high res images to tablets while they're on WiFi and allow a little fuzziness while they're on 3G, or dial down image quality for people on overshared coffeeshop connections.
Obviously it makes an article stronger to make definitive statements such as you would "never" want an image to be larger than the screen displaying it. However, far from never wanting to present an image larger than the screen space available it is perhaps more common to want to display an image which is larger than 1280*720 (currently a large mobile resolution) should such a size be available.
For example when viewing a number of e-commerce websites I like the ability to zoom into an image to see in finer detail an item I wish to purchase, especially if the item is second hand where detailed portions of the image can be important in the purchase decision. I for example always switch to "classic" mode in ebay in order to make informed purchasing decisions because the mobile images are too low quality.
Other examples would include re-sharing images between devices (e.g. emailing from a mobile to a desktop machine), printing images to a different sized device, which are severely impacted by serving specific image sizes to mobile devices.
Your statement is primarily only true when the images are of very little importance to the end user task and perhaps mainly decorative in nature.
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034494.html is wrong in suggesting that the device width will always be more important than the semantic value of the image!
I did experience problems with the Boston Globe image size and portrait / landscape switching on a Samsung Galaxy S 2.3.5 stock browser and images becoming pixelated when they were not pixeled in Chrome on Windows 7.
Not sure I have seen a site with "responsive webdesign" that was superior to the "desktop" version, In most cases I regularly use the desktop version of sites on my mobile device.
Again your suggestion of a bandwidth detector is also problematic for a number of reasons.
1. Bandwidth is to an extent site specific
2. Bandwidth does not remove the importance of the nature of the task. Just because the download is slow does not mean the person is not happy to wait for a full resolution image.
The only real solution is an image format that is designed to download progressively to a specified size and potentially use spare bandwidth to download higher detail levels to allow for smooth scrolling. Essentially images would appear to work in a similar way to Google maps but all image behaviour is contained within the original image file and the code to download the appropriate level of detail is controlled by the server and the browser and is outside the general control of the developer.
Some great theories in here and although none of them can be said to be 'good' they are undoubtably preferable to loading a 1000px+ image in to a 320px window :)
My one concern is the bandwidth/connection-type attributes you propose for the img/picture tag. If I'm tethering my mobile with my laptop through Edge,3G,etc (no-so-often) or if I'm doing some heavy up/downloading (often), there may be occasions when I'm patient enough to wait for the full experience. I would at the very least like the option. A device-width query inside the tag (like the video tag) works great for me.
That said, if the bandwidth/connection-type attributes did get browser support, there's nothing stopping browsers having a UI 'Fast Loading On/Off' option which overrides the attribute value…
Nothing to stop the image formats getting smarter and taking a leaf out of the "icon" book.
As the decision about bandwidth is actually one for the user - sometimes difficult to tell whether they are on a fat pipe with a tiny device or other way round - much better to let the browser decide what it thinks is best and make an indexed-based request for the bitmap. Get this added to webp, the most bandwidth-friendly image format, and you're halfway there.
It's great to read something that doesn't just highlight problems, but actually proposes a workable solution. Hopefully the W3C take note.
Re your current problem of mobile image appearing before the full sized. What about sizing the mobile image using it's "intrinsic ratio":http://www.alistapart.com/articles/creating-intrinsic-ratios-for-video/ , and then front loading the full size over the top, so it effectively becomes more detailed rather than changing size.
Wouldn't fix the bandwidth issue, but could be less jumpy!
Thanks the the article, great read!
I arrived at the same conclusion. In my own frustrating attempts at mobile-first-avoid-redundant-downloads-design, I concluded that I needed a video-like element with multiple src elements, as well. I implemented the design using divs and allowed JavaScript to dynamically swap out images based on window dimensions. It works, but I would certainly welcome an official W3C construct.
i love the picture tag idea with multiple sources. I'm not sure "picture" is the right word, i always think of photograph, landscape etc when hearing that word. Not applicable for a logo.
the problem i've had with responsive design on this note is that we got away from separating design and content when CSS really took off. Now, to make sites responsive we're back tracking a little by placing images in the mark up again when they could be background images.
that said, its not the end of the world.
If however we're going to go this far, by having a new "picture" tag, and multiple sources. It would be nice to go the extra mile by taking a que from style tags. Meaning, a version of media="screen" for the source tags. Shouldn't be too much to ask I dont think. If a new tag has to be adopted might as well go the distance. media="small", media="medium", media="large", media="xsmall", media="xlarge" etc etc.
If the goal is to load images based on screen size for the sake of loading speed, why not make the job easier on ourselves by being able to force certain ones to load at certain times, and bypassing the rest.
Those are my thoughts.
I'll be at An Event Apart ATL. Looking forward to all the responsive discussions!
A long, long time ago the "lowsrc":http://lists.w3.org/Archives/Public/www-html/2002Nov/0136.html attribute would handle something very similar to this. It would be nice to have it back again to quickly load an image on any browser, then once everything is in place start working on high res if possible. A non-js implementation would be ideal, as you wrote towards the end of your post better fallbacks and conditional loading would be wonderful. Some other options for responsive loading were discussed on "quirksmode":http://www.quirksmode.org/blog/archives/2011/09/responsive_desi.html ,
I think this idea of a element.
One thing that caught my eye was the repeated idea of:
<source src="mobile.jpg">
Wouldn't it be nicer to simply use [img]big-img.jpgqkkpzsy6mQVMexX8WGEGJoSySLA1sM2ltypography_img_src_end media="min-width:800px"> as the standard image so you only need to declare it once and add alternative images?
<source [/img]
This design pattern should be broken out for all media really:
<video src="high-res.webm" media="min-width:800px" />
<video src="low-res.webm" />
[img]medium.pngqkkpzsy6mQVMexX8WGEGJoSySLA1sM2ltypography_img_src_end media="min-width:600px;"> has been a closed tag forever, why not just allow the tag to be opened and use a format like.
<source [/img]
<source src="full.png" media="min-width:960px;">
No new tag, older content still works, and we get real responsive images.
In my mind, this approach has the added advantage of a super-fast initial display for everyone (including desktops), since they only have to download the teeny images at first. From what I've seen, many people will be okay with a progressive image load if it makes the site faster.
The <img> tag can't be opened up because of the way legacy browsers treat it as a self-closing tag.
more stuff
The </img> tag would be treated as another img element in the DOM. And none of the contents between the <img> and the </img> would be considered as child elements. And a </img> with no src would hurt performance. See http://www.nczonline.net/blog/2009/11/30/empty-image-src-can-destroy-your-site/
You have to have a new tag.
Why not use Data URI or even just a blank image and then use Javascript to decide what image to use?
It is becoming clear to me that "responsive" design leaves all layout choices in the hands of the designers (where it should be) and "adaptive" requires more consultation with the developers, and the best result will probably be a combination of them. I would like to see the web change to offering as much control over layout and content to the front end developers as possible, but we're not there yet.
For a simple page that only contains content you want to display anywhere, if the images can be delivered as CSS background images then surely @media queries would be way to go, specifying a different image depending on screen size.
If the design has been created in that quaint, print-focussed, Photoshop-a desktop-design-first approach, then a mobile site may have to be assembled with a controller selecting a different set of models and views depending on the user agent.
Right now I'm advocating adaptive techniques as a fall back, and they are often the only way to effectively "mobilize" an old-fashioned web site reasonably quickly. The benefit of this is that the client will soon want their desktop site to be as efficient and user-friendly as the mobile version.
Keep the pressure
Certainly the news is only grim for client-side approaches. For those of us with CMSes or access to php, the outlook has to be more positive.
I'd strongly encourage everyone to read "Jason Grigg's article on responsive images":http://www.cloudfour.com/responsive-imgs/ (which Mat linked to.)
Which means on the first connection, you don't know anything about the browser, so you can't send "the right image" to it. If you want to try to figure out some of the capabilities of the browser before you send the first page of data, you have to rely on UA sniffing. UA sniffing is fragile and requires constant updating of your UA database.
So, yes, you can build server-side solutions into a CMS, but that UA-sniffing code will never be as robust as a native HTML solution could be. Personally, I'd like to try to build a server-side solution that uses a Future Friendly markup with the element.
I really like it. The time is right.
bq. Some of our first iterations involved <noscript> tags and document write. I still have nightmares about dynamically-injected base tags. These were desperate times, and we left no stone unturned.
What problems did you find while using the <noscript> tags? I have spent quite some time with this technique, and so far it is the best method I have used to deliver proper images based on browser sizes.
I made a script for using the noscript tag technique without any pain. It is small and fast, but yet flexible. Please give it a spin:
Anyway, let's hope that browsers will implement a clean solution for this any time soon.
Fantastic work on a tricky problem. I agree that JS should not handle img sizing and server side tricks are just not applicable, I can imagine many situations where server side programmers are gonna get well pissed with front end guys requesting, new and different solutions. However, I believe CSS to be the route that should be used, after all CSS is presentational whilst mark-up describes content and in this context I would regard imgs as presentational.
What about the <object> tag? I have to admit, I've never used <object> to post an image, and I've only had other programs generate its sloppy markup for me. But displaying images is one of its purposes, as listed in the spec. It also has a built-in and well-documented fallback.
I wonder if something like that could work.
What about using a user agent query in the htaccess instead of the cookie. Basically redirect image requests for only mobile browsers. Now I know using User Agent Strings to detect something like an iPhone isn't best way to do it, because User Agents can be spoofed but realistically aren't those edge cases, like ie5 visits :)
There is also another problem related with images. Lazy loading. With HTML5 we got async attribute to script element but no way to postpone image loading, force client to wait until image is really needed. For example imagine CSS3 based carousel with 10, 100 KB each sized images. We need to fallback to JS code to inject images to the page. In my opinion there should be something like test.png, when visible browser should request it and then apply all css rules (including effects, like transitions).
Personally I love the approach being presented in the article. I have often found that many developers over-complicate solutions when something could be just as simple as a picture tag.
It would be nice to find a solution for responsive images that really works and is accepted cross browser.
Even if something like this were to be come standard, how long would it be till most browsers were implementing it?
Mat's essay mentions that the work-around hacks by his team and others fails when 'newer' (and unmentioned) browsers may, upon parsing a link or via markup, proactively download things.
Work-arounds that rely on cookies and/or script-replacement may see issues, as the Boston Globe does now.
A semantic note: a pre-_fetch_ is, at present, a request to pre-load resources, on an individual basis. One HTML file, one image, etc. I do not believe any browsers parse said HTML and load its referenced resources when in this mode. A pre-_render_, on the other hand, loads a page and all its content, but keeps it hidden. At the moment, "it only happens on Chrome":http://code.google.com/chrome/whitepapers/prerender.html . These are different from a _DNS_-pre-fetch, which simply resolves IP addresses for faster browser-to-server first-contact.
When Firefox pre-fetches content (at the behest of the referrer page's markup), it sends the following header with the request: @X-moz: prefetch@
Safari does similarly, using: @X-Purpose: preview@. According to "this ticket":http://code.google.com/p/chromium/issues/detail?id=58459 , Chrome does, too.
For pre-rendering, Chrome does not send any header whatsoever to the client. Instead, one must use the "Page Visibility API":http://code.google.com/chrome/whitepapers/pagevisibility.html, in JS.
*What to do*
In most circumstances, a pre-fetch ought not to be initiated on a mobile browser without a lot of forethought. If you think said mobile browsers will hold to that idea (and I hope you're right), you can watch for the HTTP pre-fetch headers, and make sure to load the full-size image for that request.
The various browsers need to be lobbied for an opt-out, too. While at the time, I thought the "effectively-mandated":http://www.alistapart.com/articles/beyonddoctype IE-8 @X-UA-Compatible@ header was horrendous, at least it put the capacity for control in the hands of an individual site. As browser-makers add whiz-bang features to their products, we as site builders need mechanisms to deliberately opt-out of those that would negatively affect user experience.
The DNS-prefetch implementors did this right. The @X-DNS-Prefetch-Control@ header allows a site-owner to opt-out gracefully.
Remember the early days of the web, watching interlaced GIFs load, bit by bit, as though looking through a window whose blinds were being slowly opened? No? Get off my lawn.
Through a different methods, progressive image loading is supported by PNG and JPEG, as well. I don't see anything regarding the new kid, WebP.
Imagine, for a moment, a single image file that would look correct on browsers of any size and connectivity. In theory, this is possible when interlaced images are handled properly.
A 800x800px image has four times as many pixels as its imaginary mobile-sized counterpart, which clocks in at 400x400px. Now imagine this larger image is a progressive image. In order to display this image well at the smaller, mobile size, *one could theoretically load only one-quarter of the original image*.
(Yes, I know there are overheads to progressive images. An image file, when saved progressively, is usually slightly larger than a non-progressive file. _"There can be no progress, no achievement without sacrifice…"_ -James Allen)
That sounds like a good future, doesn't it? Because the browser understands the rendering intention (size), it can load only as much of the image as it needs to display it well. A _really_ intelligent browser would consider this a partial download, and remember the file offset in case it wanted an even bigger image and decided to resume download.
The best of all worlds, without new markup.
Now if only _someone_ would support JPEG2000, which is supposed to do an even better job at interlacing.
It seems to me that any technique that requires web developers to implement additional complex markup is only ever going to have a low takeup. If a device can only render a low res image it should probably make that clear in the headers of its request, and then web servers can scale images before sending them. This kind of approach can be implemented transparently and would work with existing sites and markup.
Detective work is not an easy thing to accomplish, but the image element replaced with an audio/video like approach is brilliant. Not only do we need to detect for resolution/screen size for imagery, but also scripts and libraries that are not needed for certain devices.
The Filament Group implemented EnhanceJS which is brilliant and totally useful for detection, but as of today there isn't a ton of interest on their google code page. Also currently Modernizr also wont detect the max-device-width media query for its load property.
Too bad these options and solutions are not bringing in attraction as we seemed to be concerned with image sizes rather than the whole ball of wax. Thanks for the deep thoughts and share :)p
In keeping with new media tags, why not just "<image>"?
Hey Mat, really good article on image options for mobile first development. I was very curious on how we, as designers and developers, could get in on the conversations with WHATWG and the like about implementing better options for images in HTML markup.
Is there an easy way to join the conversation and would it be helpful to have more people in on it?
Guys, thank you very much for all the feedback! This is the only way to get this topic in the right direction and to get a working code.
As a result I've spend some hours reading, analyzing the comments and sorted out. This is what is valuable feedback (sorry, I sorted out all the duplicates of code-element-names etc.): "See my updated article":http://novolo.de/blog/2012/01/19/what-happened-to-responsive-assets/#update1
@Mat: What do you plan on the WHATWG list? I'd recommend moving the topic forward in W3C's "public-html"-list where the topic is already in list here: "[whatwg] add html-attribute for responsive images":http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/thread.html#34494
So please don't open up a new duplicate while another topic has already run through the WHATWG lists and moved to W3C's list. Thanks!
If you have questions, please don't hesitate to contact me.
I haven't read all of the responses here but I've been thinking over this. I would love to see a 'path' option that could be included as part of the CSS and be a distinction in the media query. So for a normal 960 or larger view you could have img path:fullsize; and that could switch for tablets and mobile depending on the media query to be path:tablet; or path:mobile; as needed which would pull the appropriate image source from the folder that is being called. It is a bit of work easily solved through resizing actions. Much less work than what is currently needed with video and the various formats that are needed to degrade properly.
@my ad: As far as I understood you're talking about a solution to solve the responsive image problem inside CSS, too. This is something you can read in my proposal here: "see blog article":http://novolo.de/blog/2012/01/19/what-happened-to-responsive-assets/.
I like the idea of being responsive in either way — informational elements in HTML, non-informational/styling-elements in CSS.
Is that what you've been thinking of? If not, please clarify so we can sort this out.
@anselmh Yes, I would like to see the solution come through CSS as I think it is the best way to approach it for the long term. Adding in javascript workarounds seems messy to me as we look into the future and think it only serves as a crutch to the bigger issues.
Thinking this through over the morning I've found various issues with my original thought and what could be solutions or could lead to complications. Below is a breakdown of how it could work changing around how a few things are currently structured.
Through the img tag you would nolonger specify an full path to the asset as it is currently structured. ie, img src="folder/logo.jpg"
This would be handled through the CSS file using 'path' or some other specifier. So the document would now look as follows.
img src="logo.jpg"
img { path: desktop; }
This would lead the logo.jpg to be pulled from an image folder named 'desktop' and retrieve the full size asset.
This can be changed using media queries to pull the different size assets from a different source folder as follows.
@media screen and (max-width: 480px) {
img { path: mobile; }
If a person doesn't like to have all images coming out of one directory you could pull images out of various folders through a class element.
img.company { path: company; }
img.products { path: products; }
resulting in - img class"company" src="logo.jpg"
and so on.
You could specify where the assets are coming from depending on the different scenarios that are being designed for. As we look ahead screen sizes and resolutions are going to keep multiplying and we'll very soon be taking into account televisions adding more complexities.
Using this approach front end devs that are not concerned with responsive design can still use the traditional path structure without specifying path: ; in the CSS - img src="folder/logo.jpg" and it would work as expected.
The part that I'm not fond about is having to create various sizes of the same image however this also opens up a number of design opportunities as you can customize images depending on which display it is being viewed on.
I see this providing designers a lot of potential to customize how a page would look and deliver images to that specific device instead of needing to use the same image for every instance and simply scaling it.
This approach keeps the current responsive principles and allows for additional customization but my favorite part of this solution is it only adds one piece of code and leaves the rest of the styled elements via CSS as is.
I should clarify when I say 'I would like to see the solution come through CSS'. Ideally the best solution would be native HTML enhanced by CSS. The HTML would be a fall back to an enhanced CSS solution.
I still think that that there should be an all emcompassing <media> tag that would allow the browser to gracefully degrade from <video> to <img> to any other element you could use for that area (and dependent on a standard media attribute). It seems like the video tag is only scratching the surface of the power of graceful degradation via HTML, why stop there? What about using a shorter headline or paragraph text if the viewport is smaller? Why not give us the option of giving a html alternative for an image versus relying on basic text in an alt tag?
Too many tags, not enough scalability.
As our mobile-large screen responsive evolution presses on at warp speed… those on the crest of the wave are held back by seemingly simple technological hurdles. We have to remember the large screen in the equation as brand channels will begin to immerge with one feed -> mobile-large screen.
Our frustrations are but a small slice in time. What may seem like a solution today, may be an obstacle in only a matter of months.
I so love your suggested solution. It absolutely makes sense - today… and is evolution enabled.
Well said and good luck in persuading the powers that be to enable these markup improvements.
Responsive image nirvana.
Commenter #11 asked about this but I didn't see a response from Mat. Any thoughts on this approach?
This is excellent article in the way it expresses what developers go through in battling how things change and evolve on the web and whereby most designers don't ever really get the intricacies that developers have to deal with.
I think it's not enough for designers to just study design, they need to study structure and code as well. The reverse is equally important but I think there's plenty of momentum lately for developers to understand the importance of great design. Full disclosure, as a former developer, I may be biased in who I think needs to work harder. :) Nevertheless, nice article!
I'd like to propose a new tag: IMG
I think it's a good method. Not all people can think of ideas as great as the ones mentioned above.
fantasy, coins, gold, silver, copper, D&D, role, playing, currency, money, campaign
All these approaches put to much of a burden on developers! They're clunky, prone to breakage and force the use of more markup. But maybe worst of all they force you to define fixed dimensions where you switch the image and to maintain multiple versions of the image!
I'm really quite astonished that no one so far has mentioned that JPEG 2000 together with the JPIP protocol handles this use case already… Store the image on the server in the maximum resolution you want to offer, but just download a size appropriate for the user's display. Open source JPIP servers are available… (Djatoka for instance can serve 'regular' formats from a jp2 file, providing a fallback.) Better native support for JPEG 2000 in browsers would be nice of course.
Some experiments need to be done on how best to use inline JPEG 2000 for responsive images. I suppose one approach could be sending a scaling factor (or max size) with a cookie and do some URI rewriting on the server side to get the desired image size. CSS can still be used to downscale the image for a perfect fit. It's not optimal, but the main point is to just work with one image and let the server handle the scaling.
Yes, JPEG 2000 requires encoders/decoders that are complex and more computationally 'demanding'. But there has to be a tradeoff somewhere.
And let's not forget that JPEG 2000 offers many other useful features.
I wrote the comment above in a hurry and forgot to clarify that of course no browser currently implements the JPIP protocol. However I still think using a JPEG 2000 server over HTTP could be a very interesting method towards solving the problem of responsive images. And it would certainly help push native implementations of the JPEG 2000 standard.
What about an approach of using the CSS media type to control the image source? No JavaScript involved, but it does assume that mobile devices come up with a media type of handheld. You probably can't use the img tag, but maybe a div tag. Then again it changes the function of the div tag and is not semantically correct. A change to the markup to support images like videos would still be the best option.
I've been experimenting with this, . I watched the resources as I expanded the window and the different image for the widest display isn't requested until that CSS is triggered by the window reaching each specified width. (I cused different images so I could see the change easily).
No Javascript at all.
@media screen and (orientation:landscape) and (min-width:480px){
@media screen and (orientation:landscape) and (min-width:1024px){
I agree, a picture tag was perfect to solve this problem, we have a solution for this, but this solution is not easy to implement, and, at this time, we have to care about many device sizes more and more. Hey W3C, look this post! :P
@Marc Diethelm: This is entirely the best solution. I've written about it as the "perfect solution" in my blog post. The problem is, that JPEG2000 isn't that good of a format for graphics. So we would need ideally WebP/WebM to be able to progressively download and serve responsive images. Until that is implemented in all browsers (haha!) you will still need another approach, so that's why we proposed the HTML5 solution for interim.
@JCOELHO, @yeosteve: A CSS only solution wouldn't work as it's not semantic and doesn't work valid. It still should be possible to do via CSS for non-semantic (styling/layout) purposes, too. Mailing list of W3C didn't care about this very much ;)
@Anserson Schmitt: We (Mat and I) are currently discussing on WHATWG lists and if we have a solution over there, it will move to the W3C list. So be sure we do our best W3C cares about this problem :)
@ NatCk: adaptive-images.com is only a polyfill solution and uses some technique not very good for a standard-solution.
Since we're talking about changing the browser's behavior anyway, why not actually make it offer up the information to properly solve this problem server-side? Let's have the browser send the information that is available to the "css media queries":http://www.w3.org/TR/css3-mediaqueries/ in the HTTP GET request headers caused by the one-and-only whatever.png tag or CSS url("whatever.png").
To wit:
X-Media: "screen color:24 resolution:120dpi orientation:portrait device:640x480 viewport:500x300"
(obviously, the aspect-ratio and device-aspect-ratio can be computed, color-index seems meh)
The nice thing about this is that it is really up to the user-agent's current needs to determine what should be displayed, thus what should be requested. If someone zooms in, the user-agent can ask for a bigger version. If they switch to print view, we can ask for the monochrome version in higher DPI and all is warm and fuzzy. If the server doesn't care, it serves up the one-true-image. If the server cares, it can serve specific versions. Cache logic can be driven by the standard content-negotiation logic (and left non-cached until it is).
The best part of ALL of this is that the CSS can just reference an image, the html can just include a img tag, etc… and the browser's request can be driven by what it knows already about the size/placement/device of the image.
Use JavaScript stylesheet manipulation. All responsive images should be rendered in an <img> with a token classname, such as 'responsive', and should have fallback 'src' value. In <head>, JS will add a stylesheet rule to 'display:none' all such elements (to avoid requesting the wrong image resource), then will determine the appropriate screen size category. Script block at the bottom of the page will alter 'src' values of all responsive <img>s according to screen size category, per some naming convention, and then update stylesheet rule to 'display:inline' all such elements.
This may cause flicker, more noticeable when HTML is generated/delivered slowly. This can be mitigated by encapsulating the responsive <img> in some server-side component that also emits a script block right after each <img> to do the 'src' attribute manipulation and displaying.
The 'resize' event will be handled to perform this logic in case different images need to be re-rendered (can be short-circuited if new image would have lower quality).
If UA doesn't support JS or doesn't support stylesheet manipulation, there will be flicker or simply the fallback content is rendered.
Is there a reason why you can't just use images as the source in the video tag with the image MIME type, as in the following example??
<source src="high-res.jpg" media="min-width:800px" type="image/jpeg">
<source src="low-res.jpg" type="image/jpeg">
This one is an inspiration personally to uncover out rather more related to this subject. I must confess your information extended my sentiments as well as I am going to proper now take your feed to stay updated on every coming blog posts you would possibly possibly create. You are worthy of thanks for a job perfectly carried out!
"Web Design Company":http://www.sminfosoft.com
"Technology News":http://update-technologynews.blogspot.in/
What do you think of my responsive images proposal?
The "Responsive Content":http://stephanfowler.github.com/responsive-content/ jQuery plugin is an approach which works in a "coarse grained" way, ajax-loading an entire HTML fragment into the page, given current window width (and pixel density). It can be used to tell the server to supply appropriately sized image src URLs etc.
It's a fork of Github's Pjax loader. It does not rely on User Agent or cookies - just window width.
Correstion. Correct url:
But, Do I Need Responsive Website For Growth of My Business?
How do would you appreciate these 2 solutions to download only the small images when needed (Smartphone, iPhone, Android)
1) Use $_SERVER('HTTP_USER_AGENT') in the server script to detect that it is not a PC
2) Have a main page that detects the screen size and pass it in the URI for subsequent pages.
A great solution to <video>-like functionality. Wondering if a similar functionality can make <img> element accept multiple sources like video does.
@dojo4 we developed something similar, but make the choice about which images to download not based on screen width, but on bandwidth - https://github.com/ahoward/jquery.bires


text:
The depiction of God as a shepherd goes back to Genesis. When Jacob (or Israel) was on his deathbed, he blessed two of his sons in the name of "the God in whose presence my fathers Abraham and Isaac walked, the God who has been my shepherd from my birth to this day" (Gn 48:15).
In his final testament, Jacob described God as "the shepherd, the rock of Israel" (Gn 49:24). The prophets also referred to God as a shepherd, as when Isaiah declared, "Like a shepherd he feeds his flock; in his arms he gathers the lambs, carrying them in his bosom, leading the ewes with care" (Is 40:11).
Psalm 23, written by King David, is the best-known depiction in the Jewish scriptures of God as the shepherd who provides physical nourishment, spiritual refreshment and continual guidance and protection, concluding: "And I shall dwell in the house of the Lord for endless days" (Ps 23:6).
All of these references form the background to today's Gospel, which recounts Christ's "good shepherd" discourse, given shortly after he had healed the blind man (cf. Jn 9). That miracle had further escalated tensions between Jesus and the Pharisees (cf. Jn 8:59; 10:31-39).
Thus, Jesus' words about shepherding were uttered in the middle of deadly discord. They are, in a real way, an expansion on Psalm 23 and David's statement: "Even though I walk in the dark valley, I fear no evil; for you are at my side." What is the source of conflict? The very person and mission of Jesus, as St. John points out in his prologue: "He came to what was his own, but his own people did not accept him" (Jn 1:11). The religious leaders recognized that Jesus had been making exclusive, astonishing claims, as when he said, "Amen, amen, I say to you, before Abraham came to be, I am" (Jn 8:58).
In using the imagery of the sheep and shepherd, Jesus continued to assert his uniqueness, not only by describing himself as the "good shepherd" (Jn 10:11) and thus highlighting the bad shepherding of the Pharisees and scribes, but also by declaring, "I am the gate for the sheep. ... Whoever enters through me will be saved, and will come in and go out and find pasture. A thief comes only to steal and slaughter and destroy; I came so that they might have life and have it more abundantly." There is little doubt that Jesus had in mind the scathing rebuke uttered by the prophet Ezekiel against the bad and corrupt shepherds of Israel (Ez 34).
Jesus is the only way to salvation, the Lord of life. "I am the way and the truth and the life," he stated at the Last Supper, "No one comes to the Father except through me" (Jn 14:6). And the way to the Father is through the cross; it comes through humility, suffering and even death. The head apostle, Peter, learned that lesson the hard way, and then he proclaimed it with fearless conviction on Pentecost: "Let the whole house of Israel know for certain that God has made him both Lord and Messiah, this Jesus whom you crucified" (Acts 2:36).
Just as Jesus warned of thieves and robbers, Peter warned, "Save yourselves from this corrupt generation." Along similar lines, the first pope, in his first epistle, reminded his readers that they had once "gone astray like sheep, but you have now returned to the shepherd and guardian of your souls" (1 Pt 2:25). Peter knew what it was like to go astray; he also knew of the salvation and restoration offered by the shepherd (cf. Jn 21:15-19).
Carl E. Olson is the editor of Catholic World Report.
Copyright © 1996-2019 Our Sunday Visitor, Inc.


text:
Immune Systems Of Untreated HIV Individuals Deteriorates Fast
The immune systems of untreated HIV-infected individuals appear to deteriorate faster than previously thought, according to preliminary results of a small clinical trial. This finding suggests that clinicians may need to monitor people with recent HIV infection as closely as they monitor people with more advanced disease, the study investigators postulate.
Known as the SETPOINT study, or A5217, the trial was designed to compare the point at which the amount of HIV in the blood levels off in two groups of people with recent HIV infection: those who receive a 36-week course of antiretroviral therapy (ART), and those who receive no therapy until they meet immunologic, virologic or clinical criteria for starting ART. The amount of HIV in the blood is thought to reach a plateau, known as the viral setpoint, and remain there for years after infection. The level of this setpoint is thought to influence the severity of the course of HIV disease. The SETPOINT investigators wanted to learn whether early treatment lowers the viral setpoint.
In the final analysis, the difference in viral setpoint between the two groups could not be statistically evaluated because too few viral setpoints were directly measured. However, the study investigators discovered that those who did not receive the 36-week course of ART progressed to the point of needing continuous ART more quickly than anticipated. The median CD4+ T cell count in the deferral group at study entry was 556 cells per cubic millimeter (mm3). Since it is commonly thought that people with untreated HIV infection lose approximately 60 CD4+ T cells/mm3 per year, and since U.S. guidelines recommend starting ART when the CD4+ T cell count drops below 350 cells/mm3, the study team expected at least two to three years would elapse before members of the deferral group would need treatment.
Thus, it was surprising that 20 of 39 members of the deferral group needed treatment within one and a half years. Close observation of a larger population of individuals with recent HIV infection will be necessary to validate this finding, which could have implications for future clinical trial design and public health policy.
The SETPOINT study has been conducted by the Acute Infection and Early Disease Research Program and the AIDS Clinical Trials Group, both funded by the National Institute of Allergy and Infectious Diseases (NIAID), part of the National Institutes of Health. The principal investigator is Christine Hogan, M.D., an assistant professor at the Medical College of Wisconsin and an adjunct assistant professor of clinical medicine at Columbia University.
The trial has been stopped ahead of schedule because, during a routine interim review, an independent data and safety monitoring board (DSMB) determined that the early treatment group had a superior outcome largely driven by HIV disease progression in the deferral group. The DSMB also found that more than half of the deferral group needed to initiate continuous ART before the viral setpoint could be measured at 72 weeks. As a result, the trial was unable to demonstrate a meaningful difference in measured viral setpoints between the two groups.
The DSMB recommended ending the SETPOINT trial early because continuing it would not likely change the outcome or yield additional clinically useful information. The DSMB also recommended that study staff offer antiretroviral drugs for up to 36 weeks to anyone in the early treatment group who had not yet completed his or her 36-week course of medication. NIAID concurred with these recommendations.
The study team is working with the participants who started ART during the trial and their physicians to ensure a smooth transition to clinical care outside the study. The team also is providing ART for up to 36 weeks to volunteers in the early treatment group who have not finished their 36-week course of therapy and wish to complete it.


text:
Imagine your dream tiny house. Is it rustic? Chic? Filled with interesting nooks and crannies? All of the above? Then have we got a treat for you.
Humble Houses has created what is best described as a tiny living masterpiece: The 12-by-40-foot (3.65-by-12.19-meter) Dreamwood model. Dependent on the chosen finishes, this lovely dwelling is bound to please anyone looking for their ideal abode.
Sounds like a treat, right? Come with us for a closer look.
The outside is welcoming and homely. If you look closely, you'll notice the panel behind those entry steps conceal the Dreamwood's wheels away from view.
A dark brown tinge contrasts with the sleek wooden siding and chic outside furniture to create a well-rounded sense of elegance.
As you can probably tell, there's nothing humble about those interiors. An open-plan interior design, with plenty of natural and inner lighting, has been used to create a space that looks ample and fresh.
Rustic wooden walls, antique-inspired decor and modern fittings aptly blend together to create a wonderfully luxurious living space.
The kitchen embraces modernity, with luscious countertops being the winning feature of this area.
Those counters look even more spacious when you catch a glimpse from the other side. Cabinets, a dishwasher and a sink have been fitted with precision.
Further ahead, you can see that space has been maximized to fit a full-size fridge, even more cabinets, as well as a stove and oven. Magnetic knife holders and utensil hangers also add to the kitchen's efficiency.
Walk straight across into the cozy corridor to find a discreet laundry space, plus two doors leading to the bathroom (on the right) and bedroom.
Kindred textured patterns feature on the bathroom basin and shower, giving this room the stylish flair it well and truly deserves.
The bedroom consists of an outside door, ample closet space, and lovely little decorative details that tie everything together.
Modern and elegant on the outside, luxurious and rustic on the inside - what's not to love about the Dreamwood? If you want to snag one of these for yourself, keep your eyes peeled: Two variations on this model, measuring eight-by-24-foot (2.43-by-7.31-meter) and eight-by-28-foot (2.43-by-8.53-meter) are currently in the works. Humble Houses also does custom builds upon request.


text:
Connect with your Social Network
Password will be e-mailed to you.
We recommend you check the details of Pricing Plans before changing. Click Here
Do you want to change pricing plan?
Proceed Here
Pay Per Listing
365 Days
Unlimited Days
View on map
Click To See What Open Now
Click To GET
Click To See Your Best Match
Provider Of Experienced Nurse, Aya, Baby Sitter & Maid Service