text:
Henry J. Vaux Distinguished Professor of Forest Policy
Henry J. Vaux Distinguished Professor of Forest Policy
- Ph.D. Sociology of Agriculture and Natural Resources, Cornell University, 1988
- MSc. Sociology of Agriculture and Natural Resources, Cornell University, 1983
- B.A. Anthropology, Friends World College, 1978
political ecology/resource policy and politics/forests/agrarian change/property and access
My students and I study the social processes that affect the management of land-based resources, using ethnographic, historical, and other broadly sociological research methods. My work explores various dimensions of resource access, use, and control, while comparing and contrasting local, national, and international influences on management structures and processes. I ground my analysis of contemporary resource management policy and practice in local and regional histories. I am particularly interested in how social difference – ethnic identity, class, gender – affects resource access and control. How do government and non-government institutions and actors define, make claims upon, contest, and attempt to manage natural resources?
In my early research on forest and agrarian politics and socio-environmental change in Indonesia, I studied trade in non-timber forest products in East Kalimantan, village-state conflicts in the teak and montane forests of Java, the role of forestry and social forestry in state formation, and changes in forest management practices and resource rights among indigenous swidden cultivators in West Kalimantan. The scope of my research has expanded In the past ten years to include the projects discussed below.
Current Projects
The History of Political Forests in Southeast Asia
Violence, Territorialization, and the Production of Landscape
I am currently working on a book that examines the entanglements of violence and territoriality in landscape history in West Kalimantan, a province in Indonesian Borneo where I began doing fieldwork in 1990. Communal violence between Dayaks and Madurese erupted seven years later, engulfing my research sites. The book draws on ethnographic fieldwork I conducted before and after the violence, as well as on archival and secondary sources. It examines how conjunctures of violence, territoriality, and landscape production have reshaped access to and control over agrarian and political resources.
I use multiple versions of history gathered in my research to make a series of broad claims about relations between violence, territory, and landscape. My contention is that landscapes, as working, material domains of practice and sites of remembrance, are territories. The production of territories through practice and representation, or "territorialization," is a mode of claiming. This aspect of claiming differentiates territorialization from "place-making." As territories are produced and multiply, they become contested sites of identity production, resource control, and historical representation. In twentieth-century West Kalimantan, competing territorialities have led to repeated incidents of state and communal violence. In the wake of violence or its threat, those people remaining in place have produced new landscapes and new representations of their identities and histories, as part of their own and others' territorializing projects.
Selected Professional Activities
- Chair, Division of Society and Environment, Dept. of ESPM 2006-2009
- Program Co-Director, Berkeley Workshop on Environmental Politics, July 2004 - present.
- Associate Editor, Annals of the Association of American Geographers, 2003 - 2009.
- Chair, Center for Southeast Asian Studies, U.C. Berkeley, July 2001 - December 2002.
- Associate Editor, Global Environmental Politics, 1999 - present.
- Editor-in-Chief, Common Property Resource Digest, 1994-1998.
Books and Monographs
2012 Peluso, Nancy Lee and Christian Lund (eds). New Frontiers of Land Control. Taylor and Francis. Book version of Peluso, Nancy Lee, and Christian Lund (eds). 2011. Special Issue of Journal of Peasant Studies 38:4 (Sept.) 667-681.
Nevins, Joseph, and Nancy Lee Peluso (eds). 2008. Taking Southeast Asia to Market: Commodities, People and Nature in a Neoliberal Age. Ithaca: Cornell University Press.
Peluso, Nancy Lee. (translated by Landung Simatupang). 2006. Hutan Kaya, Rakyat Melarat: Penguasaan Sumberdaya dan Perlawanan di Jawa. Yogyakarta: Konphalindo. Printed by INSISTPRess. Indonesian Translation of Rich Forests, Poor People with a new introduction.
Padoch, Christine, and Nancy Lee Peluso. 2003. Borneo in Transition: People, Forests, Conservation, and Development. Kuala Lumpur: Oxford University Press. Includes new introduction and updated article, both by: Peluso, Nancy Lee, and Christine Padoch, "Resource Rights in Managed Forests of West Kalimantan, Indonesia." [second edition].
Peluso, Nancy Lee, and Michael Watts. 2001. Violent Environments. (Ithaca: Cornell University Press).
Peluso, Nancy Lee. 1992. Rich Forests, Poor People: Resource Control and Resistance in Java. Berkeley, CA: University of California Press. (Paperback 1994).
Refereed journal articles and book chapters
n.d. Kelly, Alice, and Nancy Lee Peluso. "Frontiers of commodification: State lands and their formalization." Society and Natural Resources. In Press.
2014 Peluso, Nancy Lee, and Peter Vandergeest. In Susanna B. Hecht, Kathleen D. Morrison and Christine Padoch (eds), " Jungles, Forests and the Theatre of Wars: Insurgency, Counter-insurgency, and the Political Forest in Southeast Asia," in The Social Lives of Forests: Past, Present, and Future of Woodland Resurgence. Chicago and London: University of Chicago Press.
2013 Peluso, Nancy Lee, and Michael Watts. "Resource Violence." Chapter 19 in Carl Death (ed.), Critical Environmental Politics. London: Routledge.
2012 Peluso, Nancy Lee. "Situer les 'political ecologies' : l'exemple du
caoutchouc." pp 37-64 in Gautier, Denis and Benjaminsen, Tor A. (eds.) Environnement, Discours et Pouvoir. L'approche 'Political Ecology. Versailles, France: Quae.
2012 Peluso, Nancy Lee. "What's Nature Got to Do With it? A Situated Historical Perspective on Socio-natural Commodities." Development and Change, 43(1): 79-104.
2011 Peluso, Nancy Lee, and Christian Lund. "New Frontiers of Land Control: Introduction." In New Frontiers of Land Control, Nancy Lee Peluso and Christian Lund, eds. Special Issue of Journal of Peasant Studies 38:4 (Sept.) 667-681.
2011 Peluso, Nancy Lee. "Emergent Forest and Land Regimes in Java." In Journal of Peasant Studies 38:4 (Sept.) 811-836.
2011 Peluso, 2011 Minkoff-Zern, Laura-Anne, Nancy Peluso, Jennifer Sowerwine, and Christy Getz. "Race and Regulation: Asian Immigrants in California Agriculture," pp. 65-86. In Cultivating Food Justice: Race, Class, and Sustainability, Alison Hope Alkon and Julian Agyeman, eds. Cambridge: MIT Press.
Nancy Lee, Edi. Suprapto, and Agus Budi Purwanto. "Urbanizing Java's Political Forest? Agrarian Struggles and the Reterritorialization of Natures," pp. 157-178. In Revisiting Agrarian Transformations in Rural Southeast Asia, Peter Vandergeest and Jonathan Rigg, eds. Singapore: NUS Books.
2011 Peluso, Nancy and Peter Vandergeest. "Taking the Jungle out of the Forest: Counter-Insurgency and the Making of National Natures," pp. 254-284. In Global Political Ecology, Richard Peet, Paul Robbins, and Michael J. Watts, eds. New York: Routledge.
2011 Peluso Nancy Lee, and Peter Vandergeest. "Political Ecologies of War and Forests: Counterinsurgencies and the Making of National Natures." Annals of the Association of American Geographers 101:3 (May) 587-608.
2010 Vandergeest, Peter, and Nancy Lee Peluso. "Political Violence and Scientific Forestry: Emergencies, Insurgencies, and Counterinsurgencies in Southeast Asia" pp. 152-166. In Knowing Nature: Conversations at the Intersection of Political Ecology and Science Studies, Mara J., Goldman, Paul Nadasdy, and Matthew Turner, eds. New York: Routledge.
2009 Cramb, R.A., Carol J. Pierce Colfer, Wolfram Dressler, Pinkaew Laungaramsri, Quang Trang Le, Elok Mulyoutami, Nancy L. Peluso, and Reed L. Wadley. "Swidden Transformations and Rural Livelihoods in Southeast Asia." Human Ecology 37:3 (June) 323-346.
2009 Fox, Jefferson, Yayoi Fujita, Dimbab Ngidang, Nancy Peluso, Leslie Potter, Niken Sakuntaladewi, Janet Sturgeon, and David Thomas. "Policies, Political Economy, and Swidden in Southeast Asia." Human Ecology 37:3 (June) 305-322.
Peluso, Nancy Lee. "Rubber Producing Rights, Rubber Erasures." Special Issue of Development and Change on Property and Authority, Christian Lund and Thomas Sikor, eds. Peluso Rubber Erasures
Peluso, Nancy Lee, Suraya Afiff, and Noer Fauzi Rachman. 2008. "Claiming the Grounds for Reform: Agrarian and Environmental Movements in Indonesia." Journal of Agrarian Change 8:2-3:377-408.
Peluso, Nancy Lee. 2007. "Enclosure and Privatization of Neoliberal Environments: Some comments." In Neoliberal Environments. Nick heynton, James McCarthy, Scott Prudham and Paul Robbins, eds. Routledge.
Vandergeest, Peter, and Nancy Lee Peluso. 2006. "Empires of Forestry: Professional Forestry and State Power in Southeast Asia, Part 1. Environment and History 12 (1):31-64. PDF
Vandergeest, Peter, and Nancy Lee Peluso. 2006. "Empires of Forestry: Professional Forestry and State Power in Southeast Asia, Part 2. Environment and History 12 (4):359-393. PDF
Hart, Gillian, and Nancy Lee Peluso. 2005. "Revisiting Rural Java: Agrarian Research in the Wake of Reformasi: A Review Essay." Indonesia Number 80, October, 2005:177-197.
Peluso, Nancy Lee. 2005. "Seeing Properties in Land Use: Local Territorializations in West Kalimantan, Indonesia. Geografisk Tidsskrift: Danish Journal of Geography, V. 105, No. 1.
Ribot, Jesse, and Nancy Lee Peluso. 2003. "A Theory of Access." Rural Sociology 68 (2): 153-181 PDF
Peluso, Nancy Lee. 2003. "The Politics of Specificity and Generalization in Conservation Matters." Conservation and Society, 1 (1): 61-64.
Peluso, Nancy Lee. 2003. "Weapons of the Wild: Strategic Deployment of Violence and Wildness in Borneo Rainforests of Indonesia." In Candace Slater, ed. In Search of the Rainforest. Duke University Press.
Zinoman, Peter and Nancy Lee Peluso, Guest Editors. 2002. Asian Survey 42 (4) July-August: 545-549. Co-authored Special Issue Introduction (and co-edited the issue): "Rethinking Aspects of Political Violence in Twentieth Century Indonesia and East Timor."
Peluso, Nancy Lee and Peter Vandergeest, 2001. "Genealogies of the Political Forest and Customary Rights in Indonesia, Malaysia, and Thailand." The Journal of Asian Studies, Vol. 60, No. 3, (Aug., 2001), pp. 761-812. PDF
Peluso, Nancy Lee and Emily Harwell. 2001. "Territory, Custom, and the Cultural Politics of Ethnic War in West Kalimantan Indonesia." In, Violent Environments. Nancy Lee Peluso, Michael Watts, eds. Ithaca: Cornell University Press.
Fairfax, Sally K., Fortmann, Louise P., Hawkins, Ann, Huntsinger, Lynn, Peluso, Nancy Lee, and Wolf, Steven A. 1998. "The Federal Forests Are Not What They Seem: Formal and Informal Claims to Federal Lands." Ecology Law Quarterly. 25(4):630-646.
Peluso, Nancy Lee. 1998 "The Role of Forests in Sustaining Smallholders," in John Gordon, Ralph Schmidt, and Joyce Berry, eds., Creating Integrated Forest Strategies. New Haven: Yale University Press.
Christine Padoch and Nancy Lee Peluso, eds. 1996. Borneo in Transition: People, Forests, Conservation, and Development. Kuala Lumpur: Oxford University Press. (Second edition 2003).
Peluso, N.L. 1996. "Fruit trees and family trees in an Anthropogenic rainforest: Property rights, ethics of access, and environmental change in Indonesia." Comparative Studies in Society and History 38 (3):510-548.
- Sarlo Award for Graduate Student Mentoring 2012
- Henry J. Vaux Distinguished Professorship in Forest Policy - College of Natural Resources - 2009- present
- National Endowment of the Humanities Fellow - National Endowment of the Humanities - 2006
- John Simon Guggenheim Fellow - John Simon Guggenheim Foundation - 2006
- Humanities Research Institute Fellow - Humanities Research Institute, UC_Irvine - 2000
- Outstanding Scholarly Contribution - Rural Sociological Society - 1995
- N299 - Individual Research
Contact details
Nancy Lee Peluso
On Sabbatical Spring 2015
UC Berkeley
130 Mulford Hall #3114
Berkeley, CA 94720


text:
CSS3 — Understanding the CascadeBy Adam Roberts
Having an understanding of the idea of the cascade is important when dealing with CSS, because many CSS development problems are due to styles being unintentionally applied to an element.
How does the browser decide which styles to apply?
So how does the browser understand our intentions? When more than one rule can be applied to the same element, the browser uses the cascade to determine which style properties to apply.
Our example has a general style rule focused on paragraph elements, and then a more specific rule aimed at one or more particular paragraphs.
Both style rules target paragraphs, but the more specific rule overrides the general rule in the case of matching paragraphs.
p {
color: #0000FF;
.sidebar>p {
color: #ffffff;
There are four factors that the browser uses to make the decision: weight, origin, specificity, and source order.
The weight of a particular style declaration is determined by the use of the keyword
!important. When the keyword appears after a property value, that value can't be overridden by the same property in another style rule, except in very specific circumstances. Using
!important in your stylesheets has a huge negative impact on maintainability, and there's often little call for it anyway. If you'd like to know more, you can read about it in the SitePoint CSS Reference.
There are three possible stylesheet origins: the browser, the author, and the user. We will focus on what are called author stylesheets; that's stylesheets written by the web page creator—you! We've mentioned the browser internal stylesheet that provides the default styles for all elements, but styles in author stylesheets will always override styles in the browser default stylesheet. The only other possible origin for stylesheets are user stylesheets—custom styles written by the browser users — and even these are overridden by the author stylesheet except in rare circumstances.
The two parts of the cascade that will affect your daily CSS work the most are specificity and source order. The rule of specificity ensures that the style rule with the most specific selector overrides any others with less-specific selectors.
To give you an example of how this works, consider this simple snippet of HTML markup:

This is an important message.
Now consider the following style rules that are to be applied to this HTML:
p { color: #000000; }
.message { color: #CCCCCC; }
p.message { color: #0000FF; }
#content p.message { color: #FF0000; }
These four selectors all match the paragraph element in the example HTML and set the text color. What color will be applied to the paragraph? If you guessed
#FF0000, or red, you'd be right. The
p type selector (any
p element) has the lowest level of specificity, with
.message (any element with
class message) coming next. The selector
p.message (any
p element with
class message) then has a higher level of specificity. The highest is the selector
#content p.message (any p element with
class message that is a child of the element with
id content).
Longer selectors aren't necessarily more specific. An ID selector, for example, will always have a higher specificity than an element
type or
class selector. It becomes trickier the more complex your selectors are.
If two or more style rules are still applicable to an element, the order in which the rules appear — the source order—is used. The last rule to be declared is applied. This is also true if you declare more than one style rule with the same selector; for example,
.message in your stylesheet. It will be the second instance of the rule that will be applied to the element.
There are a number of detailed articles online explaining cascade and specificity. These include a series on SitePoint's CSS Reference, which are highly recommend once you've a good grasp of some of the basics.
This is an excerpt from The CSS3 Anthology, 4th Edition, by Rachel Andrew

subset: commoncrawl


text:
SailNet Community (http://www.sailnet.com/forums/)
- Her Sailnet Articles (http://www.sailnet.com/forums/her-sailnet-articles/)
- - Cruising Preparation (http://www.sailnet.com/forums/her-sailnet-articles/21004-cruising-preparation.html)
Cruising Preparation

Many years ago, I was 20 years old, alone on my boat with 15,000 miles laid under the keel toward completing a single-handed circumnavigation. There was still plenty of water left to cross, nearly half the planet, with a reserve of learning opportunities as bottomless as the sea itself. Off the coast of Sri Lanka, en route for Djibouti, once again an event reminded me of what can happen when manuals aren't consulted and instructions aren't properly followed.

Maybe you should be sailing instead of studying how to get out here.

The stuffing box popped out of the stern tube and the Indian Ocean became the unwelcome teacher, wedging her nasty foot in my companionway door. A screwdriver and a pocketknife lost to the bilge later, I got rid of the foot by cramming the stuffing box back into the tube and tightening the hose clamp that held it theretemporarily. Intent on driving the lesson home, for more 2,000 miles of westward progress, every time I put the engine into gear, the stuffing box escaped, and the Indian Ocean forced its way back in.

The fault was all mine. I had literally invited her over and when she arrived, I called her an intruder. Some host I was. The stuffing box problem had nothing to do with the corrosive effects of time, or the routine breakdown of sacrificial parts that weren't meant to last. I knew it was completely due to a lack of attention, a sort of carelessness that happened to be essential to my unintentional yet stubbornly applied method of learning by making a mistake first, then cleaning up the mess. Easily overwhelmed by mechanics, I could only admire from afar the merit of a more proactive approach, and the stuffing box had never made the grade on my maintenance list.

Once it had declared itself needy and seized itself onto the shaft, I consulted the engine manual which clearly stated that it should have been greased regularly via a small nipple. In hindsight, I could remember staring down at the protrusion with absolutely no idea as to how the grease would get transferred and what tool would ever affix itself onto that piece, if it could even be found. The obstacles between me and proper maintenance created a minefield of potential pitfallsgrease guns incompatible with nipples, greases of uncertain viscosity, trips to too many hardware stores with clerks shaking their headswhich had been enough to help me completely ignore the stuffing box until the day it copped an attitude because of my neglect.

However, the subsequent days of attempted repairs in ill-equipped countries and the amount of inconvenience and worry that it gave me outweighed the relatively small investment of time it would have taken to prevent the whole aggravation. It also forced me to pay attention, to really investigate and become familiar with the operation of a stuffing box and its relationship to the shaft and propeller in a way I would have never understood as fully as I did when it stopped working. I ought to be the poster girl for the alternative, experiential education of learning from mistakes.

Some people are really good at absorbing and understanding theories and applying them to real-life models. Others need to experience the real-life model before beginning to understand the abstraction of the theory, and this path requires a lot of room for error. It was the route I took then; it is the route I still take now, despite all the chances I've been given to change direction.

Following the sun westward teaches more about the rotation of the earth than can be gleaned from a book.

Take the subject of celestial navigation as another example. During the year before I set sail, I took a course in a classroom full of guys who nodded thoughtfully and intelligently after only one demonstration of a tilting plum orbiting around an orange while my brain got hotter and hotter. I didn't get it at all. Declination? Azimuth? Greenwich hour angle? I flunked the course so big time that I can't even remember taking the final exama moment to forget.

I shrugged my shoulders and photocopied my father's dummy manual with the calculation process broken down into an easy-to-follow formula without all the theory. I was only 18 and hadn't scared myself witless often enough yet to not trust that I would be able to figure it out. Being in the middle of the ocean and not knowing my position will be the best motivation to learn, I told myself. Sure enough, after several passages spent working with the formula daily and getting lost and found, I finally did come to understand what the instructor had been talking about in that classroom of humming fluorescent lighting.

I have often thought about those guys who took the class with me, wondering if their frames of reference only consisted of dividers, rulers, and trigonometric lines and angles. Or had they been able to visualize the sun chasing and leading a boat west as it cast shadows on the water through patches of clouds? Could they have been seeing the moon rising over the horizon to brighten a windy, dark night? Were they able to feel the oppressive heat when the sun's declination matched the latitude? Did bedtime get later every night until it got recalibrated by the next time zone? I couldn't have learned to navigate any other way, without actually living, sleeping, and eating by the progress of the heavenly navigational aids and I now know this would hold true for many others as well. It's just another method of learning, visual and tactile rather than intuitive.

Just messing around in your home waters after a little instruction may be your ticket to a world cruise.

Several times a year, I lead learn-to-sail flotillas for women and try to impart some of what I have learned. To a novice, the points of sail and how course and sail trim are interdependent are as incomprehensible as Local Hour Angle once was for me. No matter how many times I talk our way around the circle, from head winds to beam winds, to jibing through tail winds, to beam winds on the opposite side, and tacking back through head winds, the quizzical and frustrated looks persist. Physically tacking and jibing these charter boats full of nomenclaturesheets, booms, blocks, winches, bows, sternsthrough the points of sail can make it even more confusing. I usually end the lessons by saying, "Look. Forget the words and theory. What you need to do now is rent a little daysailer and muck about in your area. You need to feel the wind, play with the sails and the tiller, and see how the three interact." For many of us, no amount of sophistry will make a jibe or a backwinded jib more understandable than repetition of the actual experience and mistakes.

The way I learned about stuffing boxes, navigation, and points of sail used to make me feel guilty and defensive, as if preparation and study had been an option for me, as if it were a matter of the right and wrong way. I've come to realize it isn't. If I had insisted on preparing by the book first, and if I had worried about everything the books say, I'd still be in the armchair trying to understand the words. Real-life messes have taught me how to be a good sailor, navigator, mechanic, and ultimately, a great troubleshooter. Each one has taught me what different problems look like and then, how they may be fixed, or avoided, in order to clear the decks for unannounced visits from new troublesome guests because, you know, they've got my number and, boy, do they keep coming.

|All times are GMT -4. The time now is 10:41 PM.
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
(c) Marine.com LLC 2000-2012


text:
Linda Ronstadt: Just Tracks (Karaoke CDG)
Linda Ronstadt: Just Tracks (Karaoke CDG) country. Karaoke CDG. Published by Pocket Songs (PS.JTG178).
Sing the songs of country/rock superstar, Linda Ronstadt! She has earned multiple Grammy Awards, an Emmy Award, numerous certified gold, platinum and multiplatinum albums, as well as a Tony Award and Golden Globe nominations. A singer-songwriter and record producer, she is better known as a definitive interpreter of songs. She has recorded over 30 studio albums, and has made guest appearances on over 100 other albums! Ronstadt has been certified by the RIAA for sales in excess of 50 million albums worldwide and 30 million albums sold in the U.S. alone and she was also the first female in music history to score 4 consecutive platinum albums and ultimately racked up a total of 8 consecutive platinum albums. This 17-song collection includes hits from such albums as 'Heart Like A Wheel' and 'Prisoner in Disguise'.
Each JTG album contains background tracks only. CDG discs can be played on a regular CD player but require a CDG player to see the graphics.


text:
Smith: Census Must Be Independent
Ranking Member Lamar Smith (R-Texas) today joined other House Republicans in urging the Obama Administration to maintain an independent Census Bureau. Recent news reports indicate that the Obama White House is considering an unprecedented shift in management of the 2010 census by requiring the Director of the Census Bureau to report directly to political appointees in the White House.
Ranking Member Smith issued the following statement regarding the need for accountability in the 2010 Census:
"The Constitution requires that the populations of each state be determined every 10 years and that Representatives shall be apportioned to the states according to their numbers. The census plays a central role in determining how many representatives each state receives, where district lines are drawn, and how much federal funding goes to each state. Politicizing or abusing this non-partisan system is nothing short of an attack on democracy.
"The Administration claims that there is precedent for shifting control of the census from the Census Bureau to the White House. So we contacted the Congressional Research Service to check that statement, and they have found no written record that any previous Administration shifted control of census determinations from the Commerce Department to the White House. There simply is no precedent to excuse this blatant power grab by the Obama Administration.
"There will be no accountability if management of the census is moved to the White House. The Administration will simply claim executive privilege and any misuse or politicization of the census will go unexposed.
"Last Congress, the Judiciary Committee held over 70 hearings looking into allegations that the Bush Administration politicized the Justice Department. But the politicization of the Census Bureau is far worse than any allegations regarding the removal of several U.S. Attorneys. It threatens our democracy."
Republican Leader John Boehner (R-Ohio) and Oversight & Government Reform Ranking Member Darrell Issa (R-Calif.) led today's press conference announcing a Census Task Force to conduct oversight of the Obama Administration's decision. Ranking Member Smith will serve as a member of that Task Force to ensure that there is no politicization of the 2010 census.
Source: http://lamarsmith.house.gov/Read.aspx?ID=1135


text:
Red Herring Light green bonded lace shift dress
Item No.1030208342
Item No.1030208342
This light green bonded lace shift dress from our womenswear range by Red Herring has a scoop neck with a V shaped back and an exposed rear zip fastening.
Sunday to Friday - order by 9pm
Saturday - order by 6pm
Monday to Sunday - order by midnight
Orders over £20 - FREE
Orders under £20 - £2
Show full delivery details
Subject to exceptions, Debenhams is happy to exchange or refund your purchase within 28 days of delivery. Please check here for more details on our returns policy and exceptions.
Open a Debenhams Credit Card today and receive:
Please note: if the amount you pay on your card is less than £500 after the 10% discount is applied, the 0% interest offer will not be available.
Credit available from NewDay Ltd to over 18s only
*Terms & Conditions apply.Find out more & apply now


text:
Game added to 'MY GAMES'.
Multiplayer Bomberman, survive to win the match!
Challenge all animals from the zoo and bring home the cup!
Enter a multiplayer arena of fidget spinners!
The stick figures are back! Beat them and claim the title!
Color Switch Challenges edition, try to pass all 100 levels!
Crush zombies while driving a combine harvester at insane speeds!
Fight against thousands of real-time opponents in this action space combat game.
Run your own farm full of cuddly creatures.
Command a massive mid 20th century naval fleet.
Build and manage your own holiday resort!
Grab a glider and show the world a penguin can fly!
Save your undead friends by turning all humans into toast.
Blow up funny looking creatures using a variety of rockets.
Create natural disasters and crush all eggs on the screen.
Dig a way towards the center of the earth!


text:
There is some news about the UC browser — the important one that nobody but me has ever heard of. (OK, that's an exaggeration — but not by much.) Astonish your peers by being better informed than them.
The mobile world.
| Amazon | App stores | Apple | BlackBerry | Connection speed | Facebook | Firefox Mobile | Google | HTML5 apps | Microsoft | Mobile testing | Mobile web dev | Nokia | Opera Mobile/Mini | Payments | Samsung | UC | webOS |
There is some news about the UC browser — the important one that nobody but me has ever heard of. (OK, that's an exaggeration — but not by much.) Astonish your peers by being better informed than them.
15 December 2015
Permalink | in Firefox Mobile
Last week, after reading this article, I tweeted that Firefox OS is dead. There was some pushback, since despite some important updates the OS will continue to be developed. However, an OS can be functionally dead without development being ceased, and that's what I meant in my tweet.
21 July 2015
Permalink | in Firefox Mobile
Last week the news broke that Acadine Technologies, a Hong Kong start-up led and peopled by mostly ex-Mozillians, raised venture capital to create H5OS, a Firefox OS fork. I believe the political motivations behind this move have been underreported.
Yesterday, in reaction to pointer events becoming a W3C recommendation, Tim Kadlec published an important piece about Apple's huge influence on the mobile web.
I agree with him to the extent of writing this extended Me-Too entry. It is increasingly becoming necessary to do something about Apple, its absolute refusal to talk to anyone, and its dickish way of bending the mobile web to its desires. Personally, I became tired of Safari quite a while ago, and I wouldn't mind taking Apple down a notch.
So let's do it.
25 November 2014
Permalink | in Mobile web dev
Another fine day at the QuirksMode test labs, where we test browsers so you don't have to. Today's topic is CSS gradients, and the subtle ways in which the various Android devices fuck them up. Also, the not-so-subtle ways in which Android devices fuck up screenshots of said gradients.
25 September 2014
For at least a year now I've held to the theory that the huge uptake in Chrome we're seeing on the mobile web is mostly due to Samsung using its own version (based on Chromium 28) in its high-end smart devices from the Galaxy S4 on.
Yesterday Krijn started tweeting about mobile stats he had, and it turned out he was willing to share. He gave me data on about 100K mobile and tablet hits in Q2 on a project of his he's worked on for
ages five years. I took the data gratefully and created a table.
Conclusion: Of Chrome users, 25% uses Samsung Chrome — this amounts to about 5% of all mobile visits to the site. On the one hand this proves that Samsung Chrome is a Thing — on the other hand I had expected a much higher percentage. So my theory isn't right, but Samsung Chrome is still important.
In February 1999, when my very first salary as a web developer arrived, I bought two things I wanted but so far couldn't afford: a CD player and a watch. The CD player is still around somewhere in my new house, waiting to be connected. The watch, curiously, stopped working pretty soon after I stopped working for employers. Freelancers don't need timekeeping, apparently. That was in 2002, and I haven't worn a watch since.
Now there's the Apple Watch. (Also a whole slew of Android Wear watches, but guess which type gets most attention?) I don't really see the use case, but that might be my lack of imagination. Anyway, my job is not to discuss use cases, but browsers — or rather, the lack of them.
A month ago Nokia announced its Nokia X product line which runs Android as its operating system. This is an interesting development because nobody expected Nokia to turn to Android — especially not now, when it's about to be taken over by Microsoft after gambling (and losing) its independent existence on Windows Phone.
I have a theory about the Nokia X that I'd like to share with you. It may be nonsense, but it fits the currently available facts and makes sense, so it could be true.
Three weeks ago I wrote about installable web apps. Last weekend I found an interesting case study. It's not exactly what I wrote about, but it give valuable insight in what site owners (and possibly consumers) currently want.
Yesterday I replied to a tweet by Marcos about "add to home screen," and that kicked off a long and rather interesting conversation about installable web apps. This post gives my view.
As Bruce explained in his Fronteers 2013 session, bookmarking something in a mobile browser should mean adding an icon to the device's home screen instead of making an entry in an otherwise undistinguished bookmark file. As soon as Bruce said this I knew he was right.
22 November 2013
Permalink | in Mobile web dev
This week I ran an eight-question survey of media query use, responsive web design fundamentals, and one viewport question. 1251 web developers reacted. This entry presents the results.
Most important conclusions:
5 November 2013
Last week Luke Wroblewski published an important article in which he said that web developers practising responsive design rely too much on a device's screen size to determine which device it is.
28 May 2013
Permalink | in HTML5 apps
Just now I noticed a Twitter discussion on packaged web apps and their purpose. The same question was asked during the Mobilism panel, and I still regret not speaking up and explaining. So here it is.
The point of a packaged web app is to allow for its peer-to-peer transfer from device to device.
A user has a nice web app and proudly shows it off to friends. They also want it, so the user opens a Bluetooth connection (or NFC or whatever) and just sends it to his friends' devices. They tap it, it installs itself, and they can use the app straight away.
6 April 2013
Permalink | in Chrome, Opera Mobile/Mini
A few more Blink-related links. (This article's title was
stolen borrowed from Thomas van Zuijlen.)
13 February 2013
Permalink | in Opera, Opera Mobile/Mini
OK, so Opera is going to move to WebKit. I didn't see that coming, despite the recent news about a WebKit-based browser on iOS (can't port Presto there, so of course it's WebKit).
What does all this mean? Hard to tell. Here are a few thoughts and guesses.
15 November 2012
| in Mobile web dev
9 comments (closed)
Currently I'm working on a media query test suite, and I've run into one of those weird things: the proper syntax of
@media not.
Note that I'm only interested in the @media syntax. I cannot use the rest because I can't fit it into my test suite.
7 November 2012
| in Connection speed
5 comments (closed)
Today I finally have the time to continue with the connection speed measurements. For those joining the discussion only now, first read part 1 and part 2. See also the draft spec; especially for the
metered property.
I'm trying to distill a few principles for measuring the connection speed. I give them in the form of statements; be sure to speak up if you disagree with one of them.
A later article will return to the nasty details of reading out the connection speed. Today we're only concerned with broad outlines.
6 November 2012
Permalink | in Mobile web dev
Now that we have the iPad Mini, web designers waste no time in wanting to distinguish between it and the iPad 2. Tough luck.
Yesterday Max Firtman explained in detail why that is not possible. Briefly, no JavaScript or CSS property, variable or media query is different on the iPad 2 and the iPad Mini. Both are 1024x768, neither has a retina screen, etc.
Incidentally, it appears that native developers can distinguish between the two, making the playing field for the grand match between native and web unleveled (disleveled?). If you wish you can blame Apple.
That's not what I want to write about, though. Instead, it's about web developers' expectations and physical units in the W3C spec.
26 October 2012
| in Connection speed
6 comments (closed)
Well, there were some interesting comments on my last post about connection speed in browsers. This post continues the conversation by giving my replies to a few notes, thoughts, and concerns.
24 October 2012
Permalink | in Mobile web dev
In the past week I've done the viewport tests on the latest crop of devices, and things are definitely looking better. The visual viewport dimensions are now well-supported, and a consensus on position: fixed is in the making.
23 October 2012
| in Connection speed
16 comments (closed)
I've said it before and I'll say it again: browsers, especially mobile ones, should give information about the speed of the connection they're on, so that we know whether to send the high-res images or lowsource ones.
Currently no browser gives any sort of information about connection speed — they don't even have access to it. Still ... well, let's say that it's possible that this will change in the future. But we need to figure out exactly how the system should work.
So this post asks a few questions, and the comments are open.
15 October 2012
Permalink | in Mobile web dev
I held a JavaScript library poll in the last three weeks, and it's time to publish the results. At least 3,350 people responded. With nearly 155,000 responses in total, and nearly 1,700 for the least-answered question, I believe this poll is fairly representative of my readers and the readers of my readers, and therefore gives genuinely useful information about current JavaScript library use.
8 October 2012
Permalink | in Mobile web dev
Two weeks ago I published a poll about the use of JavaScript libraries. So far it had 97,500 responses, but I'd like to make that 100,000 or more. So here's the poll again, and I request you to answer as many questions as you can stand.
24 September 2012
| in Mobile web dev
5 comments (closed)
When I spoke at From the Front I was asked what I thought was the worst case of thoughtless copy/pasting I saw going on around the web. My answer: jQuery.
I feel that jQuery, even the mobile version, and in fact all current JavaScript libraries, are too heavy for mobile. I think it's time for a re-evaluation of the libraries' good and bad parts. I followed up in this tweet, which caused quite a few reactions.
Yesterday Mark Zuckerberg said (paraphrased):
The biggest mistake we made as a company was betting too much on HTML5. While building native apps that were basically just a wrapper for the mobile web standard let it experiment quickly, it made the apps run way too slow. We burnt two years.
Two quick notes:
So all in all, this remark doesn't say as much as you'd think; only that Facebook will switch from web to native on Android because the Android browser does not allow web to emulate native.
But will they also create BlackBerry, Windows Phone, Symbian, bada, and S40 apps? I think not.
BTW: here is the full quote. Facebook to forget about HTML5? Nah.
Oh, and one reason Zuckerberg said this is because investors want to hear this. Investors are a bunch of clueless people who only run after buzzwords, and Facebook's delicate position on the stock market makes it necessary to placate them.
In preparation for tomorrow's iPhone announcements I'd like to repeat something I said last October: the iPhone 3GS will be produced for many years to come, and its price will drop a little every year.
Update: Well, it seems I was wrong here. The 3GS has been nixed. Pity.
OK, so now we have the rumour that Facebook is going to buy Opera. That would be unexpected. And interesting.
In this entry I'm going to pretend the news is true, even though that's not certain yet, because it is a good starting point for some serious strategic thinking.
Back in October 2010 I was very glad to receive a mail from the people behind the Samsung Dolfin browser, who turned out to work from Bangalore, India, asking for my cooperation in making it better and even offering to pay me for it. Unfortunately, by now it turns out that they're a bunch of fucking assholes who don't do as they promise. This is to serve as a warning to others NEVER to do business with them.
It should be noted that the engineers are perfectly all-right and reasonable and can easily be talked to. It's the fucking bureaucratic assholes in "HR" that are the enemy who've fucked up my life in the last year or so.
Update: This post helped. I received my money, while I was convinced I'd never get it. So that's arranged now, and my dealings with SISO are at an end.
At first sight the new iPad 3 seems to be a vindication of Moore's Law. Apple wanted to significantly increase the pixel density of the screen, and had to wait until the components were cheap enough to sell the iPad for its usual price. Now, apparently, that wait has ended and the iPad 3 with Retina is here.
Still, not all is well with the iPad 3. Put simply, what Apple forgot here (or deliberately decided to overlook) is that Moore's Law doesn't go for data connections; especially not for mobile ones. Increasing a wireless data network's speed doesn't really depend on cheaper hardware: it's a matter of bandwidth, frequencies, and more cell towers.
In addition to the quality of their web environment, there's another factor that will decide whether or not mobile web players are going to survive: the quality of their developer relations outreach. Here's a quick and dirty look at the current state of affairs.
And yes, I admit that this overview is based almost solely on my own experiences in finding sponsors and panelists for Mobilism, and I also admit that I'm writing this post because I'm very frustrated right now.
This is getting frustrating.
The official CSS WG blog:
Discussed problem of WebKit monopoly on mobile and the consequent pressure for other engines to implement -webkit- properties.
Webkit monoculture: threat or menace?
Guys, stop it. This is simplistic us vs. them thinking. It's not helpful.
Now if you would say there's an iPhone monoculture among web developers, you'd be right. But whose fault is that?
10 February 2012
Permalink | in BlackBerry, Conferences
Belatedly, and snowed under by other news, here are my BlackBerry DevCon slides of Wednesday. Once more the Future of the Mobile Web, but I think it was the best Future session I gave so far. And I use new cat and fisherman pics.
More in general, the conference was excellent; much, much better than I thought. There was ample web content sprinkled through a solid core of BlackBerry-centric sessions, but even part of the BB sessions were in fact about web technologies and related topics.
9 February 2012
Permalink | in Mobile, Standards/W3C
This is one of those weeks where everything happens simultaneously. I think that the vendor prefix discussion is the most important topic, so that's what will get my attention.
Daniel Glazman, co-chair of the CSS WG, posted a call for action that warned of the dire consequences of web developers using only
-webkit-prefixed CSS declarations: IE, Mozilla and Opera would also implement
I will argue that the proposed solution of making web developers aware of the problem may be technically and ideologically correct, but does not address the true causes of the problem: the developer-hostility of vendor prefixes, and the lack of mobile test devices.
It's a new year, and we're supposed to make some predictions. So I'll try to order my thoughts about the post-Android market, although I should warn you I won't make a true prediction but will be a bit wishy-washy and vague.
So HP open-sources webOS. That may sound like good news, but I doubt it.
Today's hot story seems to be the supposedly Google-initiated howtogomo.com website. I heard some complaints, and decided to take a look myself.
Oh. My. God.
Over the past week or so I found I have seriously misjudged the iPhone 4S announcement, and I'd like to set the record straight. After reading a few interesting pieces I realised I'd misunderstood Apple's patterns and cycles, and I saw how brilliant the 3GS move is.
I decided to write this little summary to firmly plant Apple's pattern of cycles in my mind. No original thoughts here — I just collate ideas from other sources.
If you're not into blog posts that state the blindingly obvious, skip this one. It explains why Google's whole Dart idea will fail miserably as a "structured language for web programming." Most people will have already figured this out by themselves, but for those few who haven't, here's why:
JavaScript is already there. On a couple of billion devices.
That's it, really; there's little else to say. Still, since a blog post is supposed to be longer than two paragraphs, I'll say a bit more.
Back in May I went on record saying that Apple would announce two iPhone models this year. It didn't. I also said I'd eat crow in public if I was wrong, so even though I don't think anyone actually remembers my promise, I owe you this.
... munch ... crunch ... [spit out feather] ... bleeh ... munch ...
Dear Amazon Silk team,
You released a marketing campaign disguised as a technical talk about your new Silk browser for the Kindle.
Web developers are very interested in what you have to offer, and would love to study the solutions you've created for browsing in connection-challenged environments, but currently that's impossible due to lack of information.
That lack is understandable: right now you're hurrying to get all last-minute fixes applied in time for the release and don't have time for answering detailed technical questions.
Still, the emphasis you put on Silk's use of completely new concepts makes web developers very nervous and has them scramble for any information. Browser vendor had completely idiotic ideas before and tried to sell them as the Next Big Thing. We'd like to know for sure that Amazon is not one of those vendors.
Therefore I have a few questions for you, which are detailed below.
I would also very much like to get in touch with a Silk developer relations manager.
Oh, and next time, please don't pretend all these concepts are totally new and utterly astounding. They're not. Opera has been doing this for years. Your solution may be technically better, but the onus of proving that is on you.
Thanks, ppk
So Amazon has announced its Kindle Fire tablet, and it will not be an iPad killer. It runs Android, but not the standard Android, but rather a special Amazon port that does not include any standard Google apps. Notably, Amazon will have its own app store.
Update: I've asked a few questions of the Silk team. Now let's hope we get an answer.
The Kindle Fire will also sport its own browser: Silk. Kudos to Amazon for actually giving their browser a name. That helps a lot.
So. Samsung will open-source bada next year so that developers can improve it and other device vendors use it. The Register does not believe the news, while GigaOM correctly points out that Samsung won't gain anything by open-sourcing bada.
Meanwhile, the HP board dumps CEO Apotheker and instates Whitman, who vows to retain Apotheker's strategies, even though it was exactly those strategies that got Apotheker fired. The spin-off of the PC unit may be cancelled, even though it constitutes about 90% of the current strategy. The webOS team is rumoured to be downsized, which does not make sense at all if HP wants to do something useful with it.
Oh my.
Samsung will not buy MeeGo but instead focuses on bada. Meanwhile HTC confirms it is considering buying its own OS, but "won't be rushed" — unlike certain other large Android vendors we could mention.
Time to update last week's overview. #15 is the first new one.
It is with great pleasure that I saw that I was included in the latest Carnival of the Mobilists with my Twelve steps for saving webOS.
If you don't know it, Carnival of the Mobilists is a linklist of the best mobile writing of the past month. It appears on a different blog every month, and this time it's Dennis Bournique of WAP Review who plays host. I discovered the Carnival about a year ago and have been hooked ever since.
The beauty of the format is that very different articles end up on one page; a bit like Linkbait, but with much more variety. There are articles about the mobile city, a new ad network that might replace AdMob, recommendations for encouraging India's mobile services ecosystem, the reason why Martha's Vineyard's inhabitants love Obama's visits, and more.
One of the rules of the Carnival is that you do not link to any of the individual posts, but only to the Carnival itself. So if you'd like to read one of the articles, go there!
So Samsung won't buy webOS after all. Instead, it is said to be interested in MeeGo, which Intel may want to sell. And HP will not sell the webOS team, which has been transferred from the PC division, which will be sold, to a strategy division, which will stay. Good, HP can use some strategy. As can Samsung.
That thud you heard? I fell because my head is spinning.
Well, the webOS saga has already entered a new phase. The Next Web reports that Samsung is seriously considering buying webOS (in addition to hiring a former HP VC for marketing their PCs.)
So it's outright sale, and not licensing. And it's Samsung. Neither is unexpected; I predicted both a week ago. (And I must admit I'm very happy to finally get something right, even though it wasn't a particularly complicated prediction.)
I've been thinking a lot about the future of webOS, and have decided it does have one, maybe even a glorious one, provided the new owner or licensee reaches out to web developers, as Palm should have done back in 2009.
So here are twelve steps the new owner should take in order to get webOS to thrive.
HP kills off webOS. However, I do not believe this is the end of webOS. On the contrary, I think it's the start.
The quote from the press release:
HP reported that it plans to announce that it will discontinue operations for webOS devices, specifically the TouchPad and webOS phones. HP will continue to explore options to optimize the value of webOS software going forward.
How do you optimize the value of webOS software without producing webOS devices? By selling it.
HP was already in talks with Samsung, so that's one definite option. HTC is another. Basically anyone who needs a good mobile OS does.
Anyway, HP did something very clever (or lucky) by announcing this just after the MotoGoogle bombshell. "Dear discontented Android vendors, if you're doubting your eternal and undying allegiance to Google, we have a shiny OS for sale for you. No strings attached. Place your bids."
HP had no fucking clue what to do with a progressive mobile OS. It's likely that webOS's future owners will perform better. They can hardly do worse.
Opinions abound on the Motorola acquisition. A quick rundown is in order.
So Google buys Motorola. What does this mean?
Personally I feel this heralds the high-water mark of Android's OS market share. That's not the same as its developer mindshare, or customer satisfaction, but I don't think the other Android vendors are going to be thrilled, and that we're going to see that in Q1's sales stats. Android will drop slightly, and one or more new OSs will take its place.
Samsung now has two major operating systems for the smartphone market: Android and its own bada. (We can ignore Windows for now.) Very cleverly, it is stealing the spotlights with its Android devices, while steadily building bada in the background, creating a developer ecosystem and upgrading the OS until it can somewhat compete with iOS and Android.
The reason for this dual strategy is that Samsung does not want to be beholden to Google for its OS. A strong bada will allow Samsung to discontinue Android in the future, and stake everything on its own OS where it owns the entire stack, from hardware to app store. It's not certain that Samsung will in fact do this, but it wants to keep its options open.
Just today I received a shiny new Palm Pre 2. Now Palm WebKit is notoriously underrepresented in my mobile research because up until now I didn't have a device (except for a short and unhappy period in early 2010). Besides, webOS is the only OS that can give iOS a run for its money UX-wise. Reason enough to study it carefully.
Before being allowed to actually use the phone, though, I had to go through a user sign-up process that's so amazingly hostile that I decided to record my adventures in the faint hope that someone at Palm will read it and make changes.
A few more thoughts on Nokisoft.
OK, so the deal is done. Nokia partners with Microsoft and trades in MeeGo for Windows Phone 7, I failed my test as a mobile analyst, and 2011 will make 2010 look like child's play when it comes to disruption. Here's a quick reaction to those aspects I find most interesting. No claim to completeness here.
For web developers this is bad news. Windows Phone 7 has the worst default browser of all modern smartphone OSs: IE7 (though, in fairness, Microsoft is working on an IE9 port). MeeGo was supposed to have a Gecko-based default browser, just as its precursor Maemo did.
This Friday Nokia will hold a strategy and financial briefing in London, with major announcements about operating systems being expected. This will impact the mobile browser market, so it's important to web developers. A bit of background is in order.
Two factual errors, one serious critique and a bunch of new facts and figures about operator billing.
It's said that Twitter and Facebook play an important role in the current Egyptian revolution, and that closing down the Internet was the best step the beleagured government could take. I don't believe it.
25 January 2011
Permalink | in App stores
App stores, pioneered by Apple, aim to provide ease of payments and discoverability to developers and consumers. However,
Belgium is investigating whether Apple's recent changes to its subscription policies for newspaper apps are an abuse of its dominant market position. Apple no longer allows newspapers to provide free digital versions to their print subscribers. This could possibly lead to a new antitrust affair.
This story seems to play only in Belgium and the Netherlands for now; readers from other countries may not know it. That's why I wrote this special report.
18 January 2011
Yesterday Horace Dediu tweeted:
A browser is an infinitely flexible interface, but is it the best interface for everything? Apps allow experiments in new interaction models
The browser is not the most advanced interface there is. It's too easy to build the wrong features into something as flexible as a browser, and once a badly-designed feature gains traction it's impossible to get rid of it. (See HTML5 drag and drop.)
One of the major changes 2011 is going to bring is the start of operator billing on the web. It will provide a user-friendly way of making mobile (and web) payments without those silly credit cards that are preventing the majority of the world to participate.
Operator billing is nothing new. Premium SMS (see for instance Verizon's FAQ) , where the user pays something extra to receive news items or ringtones, or vote in a TV show, has existed for ages. The price is automatically charged to your operator account.
The most advanced country on earth when it comes to mobile payments is Kenya. About 50% of the population handles about 20% of GDP by mobile phones these days. The social consequences are profound, and operator Safaricom became the biggest bank in East Africa in the process.
Update: I finally found a good description of the system.
Banks and credit card companies of the world, be very afraid. The operators will come to take your business away.
4 January 2011
Permalink | in App stores
App stores, so it is assumed, will allow developers to forge a direct link to consumers, which causes consumers to directly pay developers for their hard work. Thus they're secretly seen as a shortcut for the hard work of a start-up, that (ideally) also forges such links.
This monetisation argument is the fetish of the current age. Unfortunately it is utter and complete rubbish. The fundamental problem, as I calculated months ago, is that there's just not enough money in the app store economy to support a meaningful number of independent developers.
29 December 2010
Via John Gruber I stumbled on The Unbearable Inevitability of Being Android, 1995. The article ignores key facts of the mobile market because they don't fit the point the author wants to make.
People have the right to participate in re-enactments of historical platform wars, but they should not confuse them with reality.
17 December 2010
| in BlackBerry, Mobile web dev
8 comments (closed)
Three news items that have nothing to do with each other, except they caught my eye yesterday and today, and might be of interest to others, too.
14 December 2010
Just now A List Apart published my Smartphone Browser Landscape article. Despite having written for ALA for more than ten years, this is only my fifth or so article. But it's a nice one.
I started on this article back in July by writing down absolutely everything that web developers had to know about the smartphone market. It was about twice as long as it is now. ALA rejected this draft — and with good reason. It took me from July to October to figure out which bits web developers didn't have to know right away, and that was a useful process.
Anyway, enjoy the article. No comments here; you'll have to go to ALA for that.
8 November 2010
| in Firefox Mobile, Linkbait, Nokia, webOS
6 comments (closed)
For those who follow the mobile market:
There's a ruckus in the Microsoft world following Mary-Jo Foley's contention that Microsoft is going to abandon Silverlight in favour of HTML5. If that were true it would be great news for web developers. It is in fact not true, but still great news for web developers.
Ewan MacLeod is spot on:
It's important to recognise that whilst most of the Western media reckons Nokia is completely screwed, this is also not the case.
The company continues to ship a million handsets a day (or thereabouts) and each one of those devices contributes a tiny bit of profit along with a heck of a lot of cash throughput that keeps bankers smiling very, very widely.
Believe it or not, folk actually queued for the N8. Just not in San Francisco or London. So it might as well not have happened as far as the West is concerned.
Sadly the reality is that ... well ... perception is reality. It's 0% reality and 100% perception in the case of Nokia from the point of view of the West.
22 September 2010
Recently Mike Rowehl, a mobile developer with relatively little knowledge of the web world, confessed to being baffled by the attitude of web developers interested in mobile.
This is the last part of my reply. In parts one and two we talked about what web developers are doing wrong; now we're going to talk about the errors of the mobile world.
21 September 2010
Recently Mike Rowehl, a mobile developer with relatively little knowledge of the web world, confessed to being baffled by the attitude of web developers interested in mobile.
This is part two of my reply, and we're going to talk about progressive enhancement now. (See also part one)
Like me, Mike was impressed by Bryan Rieger's excellent presentation in which progressive enhancement plays a crucial role. However, it's important to realise that Bryan's presentation is the start of the dicsussion, and not the end. Lots of work remains to be done.
20 September 2010
Recently Mike Rowehl, a mobile developer with relatively little knowledge of the web world, confessed to being baffled by the attitude of web developers interested in mobile.
He feels there's a disconnect between what web developers do, what they're supposed to be doing, and the tools mobile vendors make available to them.
Mike is completely right. There is a whole series of disconnects right now in mobile web development, and most of them are the web developers' fault. Unfortunately the web world is hard to understand for an interested outsider.
John Gruber picked up my Nokia post, and makes an interesting comment.
After quoting my "Why on earth wouldn't Nokia be able to maintain two operating systems?" he says:
I shouldn't have written "mobile devices"; I should have written "smartphones."
To me, that doesn't make any difference. I count both MeeGo and Symbian as smartphone operating systems, so if John had written "smartphones" I would have made exactly the same comment.
That doesn't mean John's wrong, though. He just defines smartphones differently than I do. As I see it, he defines a "smartphone" as what I call a "high-end smartphone" (iOS, Android, MeeGo, webOS, likely Windows Phone 7 and BlackBerry OS6, too).
Last week Nokia CEO Olli-Pekka Kallasvuo (OPK for short) was replaced by the first non-Finn to lead the company, Stephen Elop, head of Microsoft's business division (mainly Office). This is big news that might change Nokia's perception as well as its strategy.
OPK's tenure as Nokia chief was not lucky. Barely in office he was confronted with the launch of the iPhone, and this issue overshadowed the rest of his career. For the full story of OPK, see, as always, Tomi Ahonen.
After four years of doing little except producing one of the worst touchscreen phones in history, the N97, Nokia was perceived as a loser, and pressure on OPK to resign was growing. Last Friday things came to a head when Elop's anointment as his successor was announced.
(This article has been translated into Spanish.)
A truly outstanding presentation by Bryan Rieger. Learn it by heart.
3 September 2010
| in Mobile testing
4 comments (closed)
Yesterday I was visited by a browser tester's worst nightmare: when testing BlackBerry WebKit I found I made a mistake in my touch event research. I have to re-do all these tests in all browsers because my current results don't take one variable into account.
That variable is preventing the event default. While writing my test page I left out the
return false at the end of the test event handler, simply because I didn't think of including it. The test results seemed fine, so I didn't notice the mistake for months and months. (Meanwhile I added a setting for preventing the default.)
Over the weekend I created a mobile market overview in the form of a sortable table. I hope it gives you some insights; it certainly did for me.
For a complete overview knowledge of the current market share stats is necessary; fortunately Tomi Ahonen provides the latest. My table doesn't yet contains these stats; I still have to figure out exactly how to display them (not to mention making time to implement a new feature).
Anyway, take a look and let me know what you think. And if you have some extra facts, please provide them.
I have updated the mobile browser page. It now contains 18 browsers, and in addition I added some lists about which browser runs on which OS, and which device vendor uses which OS. However, I need your help in making the list exhaustive.
I have now firmly decided to test and describe only those browsers that run on one or more of the ten smartphone OSs (Android, bada, BlackBerry, iOS, LiMo, MeeGo, Phone 7, Symbian, webOS, Windows Mobile). There are just too many other OSs, but they're either feature phone only, or they've fallen out of the race.
My question to you is to review the list and rack your brain for more data.
If you do, please leave a comment with a useful link (to the browser vendor's homepage, or to a news item that mentions device vendor A selling smartphone OS B).
14 August 2010
jQuery announced the jQuery mobile project, which aims at bringing jQuery to mobile browsers. All mobile browsers; not just Safari iPhone and Android WebKit.
Here are four interesting mobile articles that caught my eye in the past 24 hours:
28 July 2010
| in Opera Mobile/Mini
14 comments (closed)
In the mobile browser space all the advanced browsers are based on WebKit. That's fine — WebKit is an excellent rendering engine — but if all browsers were based on WebKit I would start to worry about a monoculture. At least some browsers should be based on other rendering engines, as far as I'm concerned.
The only serious mobile candidate for "other rendering engine" is Opera. But I'm starting to wonder whether it can keep up with the WebKit browsers. With the recent release of Samsung Dolfin Opera Mobile has firmly dropped from third-best to fourth-best mobile browser on my list.
The problem is not that Opera isn't innovating. It is. But I'm starting to wonder about the direction that innovation is taking.
This is just in: Google seems to be taking steps to allow operator billing. If that's true it's huge news.
Note from the outset that the article doesn't say in so many words that operator billing is coming, although it certainly gives that impression, and plenty of publications translate it as such.
The basic idea of operator billing is very simple: if you want to buy an app, or access to online content, the price is automatically added to your operator bill (or, I assume, deducted from your pre-paid account).
26 July 2010
Back in early June I got a Samsung Wave that runs the brand-new bada OS and did some brief tests of the native Dolfin browser. In the past few days I've done some more extensive testing, and the verdict is in: good browser, well on the way to becoming excellent.
(Oh, and Dolfin ought not to be confused with Dolphin, which is a skin for Android WebKit.)
It's Samsung's philosophy that it will not compete in a market unless it belongs to the top three of that market. In the case of the mobile browsing market Samsung has succeeded: from nothing, Dolfin has become the third-best mobile browser in the world. Only iPhone and Android are better.
If you're keeping track of the mobile browser landscape you should add Dolfin to your A-list. It's easily good enough, and Samsung has big plans with the bada operating system. Somewhere in 2011 the installed base of Dolfin will pass that of Safari iPhone, and bada might even become a competitor to Android. (Samsung sure hopes so.)
I have updated my mobile pages with Dolfin data. (By the way, I also tested Android 2.2 while I was at it: few changes. There's not a single difference with 2.1 in my great WebKit table.)
Apple continues to startle me, and I do not mean by its iPhone 4. (I haven't yet seen it, so I can't say anything useful about it.) No, what I mean is the ongoing Antennagate problems, and even there I do not mean the actual problem, but Apple's way of dealing with it. And even there I do not mean Antennagate as an isolated PR incident, but as yet another chapter in how Apple spends 2010 to piss off the world at large.
Vision Mobile just released its Mobile Developer Economics report in which it presents the result of a poll of 401 mobile developers across the eight main platforms: Android, iPhone, BlackBerry, Symbian, Windows Mobile, Flash, Java ME, and the mobile web.
If you're interested in the mobile developer world, download and read the report. It's free, though a valid email address is required. Below I treat some interesting aspects of the research, including the quote from me Vision Mobile decided to publish.
On Thursday I got a Samsung bada test phone (the Wave) that runs the latest installment of Samsung WebKit, and of course I subjected it to various tests. The verdict is clear: excellent browser. As far as I'm concerned it ousts Opera Mobile from my personal top three.
Back in November I started complicated research into measuring the widths and heights of various interesting elements in mobile browsers. This research kept me occupied for months and months; and frankly I became a bit afraid of it because the subject is so complicated.
Besides, when I re-did some tests in March I pretty quickly figured out I'd made some nasty mistakes in my original tests. Back to the drawing board.
However, after a review round by some browser vendors and some rewriting it's done now.
Today I present
A tale of two viewports — part one.
I explain CSS vs. device pixels, the viewport, several interesting JavaScript properties,
and the media queries
width and
This piece is about the desktop browsers, because the mobile story is much easier to follow if you know exactly what happens on desktop. Later on I'll publish part two, which is exclusively about mobile.
The acquisition battle has come and gone, and it's HP that's become Palm's new owner. In general this news has been greeted with glad cries, despite (or maybe because) it was so unexpected. In general everybody assumes that the marriage of Palm software and HP hardware will be a good one, and that HP will also release a webOS-based tablet device.
However, there's an interesting dissenting opinion on VisionMobile (a blog I highly recommend, by the way). Guest author Michael Valukenko sees few synergies between Palm and HP, and pinpoints three problems besetting the new hPalm combination:
Yesterday John Gruber wrote about the upped pixel density in the upcoming iPhone (960x640 instead of 480x320), and why Apple did this. He also wondered what the consequences for web developers would be.
Now I happen to be deeply engaged in cross-browser research of widths and heights on mobile phones, and can state with reasonable certainty that in 99% of the cases these changes will not impact web developers at all.
14 April 2010
| in Apple, Microsoft, Nokia, webOS
1 comments (closed)
Some updates on a few developing stories in the mobile space.
This is just in: HTC is said to be considering taking over Palm. That would be an interesting development, since HTC is one of the few parties we can trust not messing up webOS but actually using it as it's supposed to work.
Palm has an absolutely first-rate product in webOS, especially its user interface. As far as I'm concerned the Palm Pre is the only phone that's (almost?) on a par with the iPhone when it comes to UI, although the system is completely different (and has supported multitasking from the start, not partially and as an "exciting" novelty).
8 April 2010
| in Mobile testing
19 comments (closed)
I have made a list of the fifteen mobile browsers I currently test. This will give you some insight in the current mobile browser market, which is volatile, complicated, and sometimes shrouded in mystery.
One of the commonest questions I get is "Which mobile browsers should I test?" The hidden question here is which devices you should own. It's time to attempt an answer.
6 April 2010
| in Apple, HTML5 apps
15 comments (closed)
Cameron Moll is worried about a future in which we'll all write Objective-C for the iPhone OS instead of writing web standards for the mobile web.
At one point in time, J2ME (now Java ME) and WAP were the starting points for a discussion on mobile strategy and the web. Then, for a brief period of time, you talked about HTML/CSS. Now, for a growing majority of mobile strategies that don't require a global presence on widely varying devices, the discussion begins with iPhone.
Emphasis mine. Strategy and presence are the clue, and they're the reasons I think the situation will not be quite as bad as Cameron fears.
2 April 2010
| in BlackBerry
9 comments (closed)
An interesting study caught my eye. When taken at face value, it proves that in order to really make money with apps you have to switch to the BlackBerry platform.
30 March 2010
| in Apple, Google, Market share
10 comments (closed)
AdMob, the mobile advertiser that was bought by Google some months ago, has released its latest market share figures for the mobile browsers.
Their main findings have already been discussed extensively:
The AdMob report, however, is not about browser market share but about ad impressions. And that may matter a lot. Unfortunately we don't know how much it matters.
In response to my HTML5 apps argument a few people came back to how the payment thingy is missing from my idea, and how it will (apparently) be worthless because of that. I've been thinking about that a lot in the past few days, and I'm increasingly of the opinion that the payment argument is nonsense.
Sure, everybody who does iPhone apps, or who's glancing cursorily at the mobile market without trying to gain in-depth knowledge, currently believes that the App Store concept is going to be a huge success because of the opportunity for developers to earn some money. But they're just wrong.
I did some back-of-napkin calculations and found that, macro-economically speaking, iPhone app development costs money right now. And yes, an individual developer can strike it rich, but that's getting rarer and rarer. I do not want to build a new app ecosystem based on arguments from developers who just want to take a gamble in the App Store roulette. Gamblers' arguments are not real arguments.
8 March 2010
| in HTML5, HTML5 apps
23 comments (closed)
Right now nobody's interested in a mobile solution that does not contain the words "iPhone" and "app" and that is not submitted to a closed environment where it competes with approximately 2,437 similar mobile solutions.
Compared to the current crop of mobile clients and developers, lemmings marching off a cliff follow a solid, sensible strategy. Startling them out of this obsession requires nothing short of a new buzzword.
Therefore I'd like to re-brand standards-based mobile websites and applications, definitely including W3C Widgets, as "HTML5 apps." People outside our little technical circle are already aware of the existence of HTML5, and I don't think it needs much of an effort to elevate it to full buzzwordiness.
Technically, HTML5 apps would encompass all websites as well as all the myriads of (usually locally installed) web-standards-based application systems on mobile. The guiding principle would be to write and maintain one single core application that uses web standards, as well as a mechanism that deploys that core application across a wide range of platforms.
18 February 2010
| in BlackBerry, Google, HTML5 apps, Mobile, Nokia, Opera Mobile/Mini, Samsung
8 comments (closed)
Yesterday evening I returned from my fourth foreign trip this year. This time I went to the Mobile World Congress, the annual Barcelona-based get-together of the mobile industry, and I can tell you, it's something else.
This post gives an overview of announcements by mobile players that might be of interest to web developers. There's an incredible lot of it, too, because every single major mobile player except Apple feels that MWC is the ultimate forum for major announcements.
If you know of more news, or have links to additional information, please leave a comment.
I was there because Vodafone had invited me to sit on a
panel in a technical "embedded
conference" about W3C Widgets and related technologies.
The concept can use some fine-tuning; I'm hoping to do some of that in the future.
I was there mainly to stress that the mobile browser situation is not as simple as it looks. THERE
While I was at it I also invented guerilla browser testing.
8 February 2010
| in Apple, HTML5 apps
149 comments (closed)
Since my attempts at capturing web developers' hearts and minds by publishing fundamental research have failed miserably but my thirst for attention continues unabated, today I will once more shout at iPhone developers. That's proven to work.
More specifically, today I will shout at web developers who think that delicately inserting an iPhone up their ass is the same as mobile web development.
Before we start, a little thought experiment. Suppose I proposed the following:
Would you agree with those sentiments, even if we're back in 2000 and IE6 is really the best browser we have?
Or would you reply that our sites should work as well as they can in all browsers through the use of web standards, progressive enhancement, and all the rest of the best practices we've been preaching for the past ten years?
I distinctly remember a time when we web developers cared about such concepts. But those times are long gone.
B. is an old friend of mine who owns an old Nokia. And when I say old, I mean really old. It was released somewhere in 2000 or so (the Nokia, not the friendship). It's not a smartphone, to put it mildly, and B. does not use the mobile Web.
Pretty soon, however, B. is going to spend a few months in the outlying parts of Indonesia, and during that time he has to be able to access his business bank account. He was wondering if a modern mobile phone would fit this use case, and, if so, which one.
When he told me all that I whipped out my iPhone. "Something like this, you mean?" He was suitably impressed, and when I told him I regularly have six to twelve phones lying around on my desk he practically begged for an opportunity to come by and try them all in order decide what kind of phone he wants.
That was of course fine by me. User testing is never to be despised, and since B. is not technical and has no experience with touchscreens to speak of, he is the perfect test subject.
Last week we held our session, and this entry is the report.
Tested phones: Nokia N97, Samsung M1, HTC Touch Pro (Windows Mobile), SonyEricsson W960i, Nokia E71, BlackBerry 9500, HTC Pioneer (Android), LG M900, Nokia N900, iPhone.
25 November 2009
I have several more things to say in the Web apps vs. native apps debate, and I've decided that a few smaller posts treating just one subject would be the best form. Today we kick off with the Cocoa Touch framework.
John Gruber wants me to mention the Cocoa Touch framework. He feels that its excellence is an important factor in the success of native iPhone apps.
Point is, although Gruber's probably right, he ought to be wrong.
Well, that was an interesting ride. Besides passionate agreements, my previous post also elicited passionate disagreements.
My post could be construed as a rant. Hell, parts of it were a rant. (Nobody said this blogging stuff is easy, especially when you're passionate about something. But if I can't speak my mind here, what's the point of having a blog?)
Several people I respect a lot said that I'd made a stupid mistake and was just plain wrong. After some thought I decided they are right.
I was wrong about Web apps being able to replace native apps right now. I was wrong about the iPhone developers' mindset. They aren't stupid.
23 November 2009
| in Apple, HTML5 apps
110 comments (closed)
In his "Apple's mistake" essay Paul Graham makes an unwarranted assumption; an assumption everybody who's currently involved in the Great App Store Debate seems to be making.
The fundamental problem on the iPhone is not Apple's App Store approval policies, but the iPhone developers' arrogant disdain for Web technologies.
It was only last Friday I told a roomful of Web developers that Apple is evil, and a spontaneous applause erupted. Since then, however, I have changed my mind completely. The Web developers and I were wrong.
Apple is not evil. iPhone developers are stupid. Their problems with the App Store approval process are entirely their own fault and they deserve no commiseration.
I hope the App Store approval process sticks around for a loooooooong time.
Update: I was wrong about Web apps being able to replace native apps right now. I was wrong about the iPhone developers' mindset. They aren't stupid. Read my follow-up post.
13 October 2009
| in Apple, Chrome, Google, Safari, Samsung
12 comments (closed)
When I reviewed the reactions to my There is no WebKit on Mobile post, it became pretty clear that few had expected its conclusion that there is no single WebKit on Mobile. Overall, it seemed that most people were pretty surprised, and hurried to revise their ideas of the mobile browser market. That was the point of the article, so I was happy.
(I'm still tinkering with the interface, by the way, and I didn't have the time to finish my current revision. So the coloured bars are temporarily gone, but they'll return in the future.)
7 October 2009
| in Apple, Chrome, Google, Mobile, Safari, Samsung
32 comments (closed)
Last week I spent a lot of time on WebKit in order to produce a comprehensive comparison of all WebKits. My purpose was to prove there is no "WebKit on Mobile," and to gain some more insight in the complicated relations between the various WebKits.
Therefore I now present the Great WebKit Comparison Table. In it I compare 19 different WebKits on 27 tests.
Having tested mobile phones for the last seven months or so, I have become pretty well inured to odd, or even disastrous, results. Still, after encountering the following bug on the Android, even I started to doubt my sanity.
I don't usually spend a blog post on a single browser bug, but this time I break that rule because this is doubtlessly the weirdest bug I found so far, and possibly also the most serious one.
width may be unreliable on the Android — in certain situations.
14 September 2009
| in Mobile testing
18 comments (closed)
After seven months of mobile testing (as well as a wealth of inventive invective aimed at mobile devices) I think it's time to share some of my experiences with others who are inclined to violent self-punishment.
Welcome to my world! Bring your whip, bring a first-aid kit, and let's have some fun punishing ourselves.
Today we'll discuss the process of testing mobile browsers. We will not talk about the test results or their interpretation, we'll leave that gorefest for another time.
As everybody who's even slightly interested in mobile knows, the creation of the Apple App Store has caused a perfect flurry of activity among everybody else having to do with the mobile web.
Currently I'm making a list of all existing app stores. I've found a few, but I'm reasonably certain that I missed a few, too. So I'd like to ask you if you know of an app store I've forgotten. I'm especially looking for information on T-Mobile and HTC.
Last week I've done the DOM Core tests in new browsers: IE8 final (in both IE8 and IE7 mode), Firefox 3.5b4, Safari 4.0, Chrome 1 and 2, and Opera 10a. I found no surprises.
After that I decided to continue with mobile browsers, of which I have 15 lying around on my desk. Unfortunately I could not test IE Mobile (old) because it supports only inline event handlers, Skyfire because it does not allow you to remove alerts, and the Opera runtime in the Vodafone widget manager for terrifyingly complicated reasons I still have to describe properly.
Still I managed to test the other twelve and found a few surprises.
20 April 2009
| in HTML5 apps
13 comments (closed)
As I said before, I'm currently working for Vodafone on mobile browser compatibility and W3C Widgets. I've discussed some mobile browser problems, and you can look over my shoulder while I'm at work dissecting their odd behaviours. If you want the latest scoops on my mobile adventures, you can follow me on Twitter.
The time has come to talk about the W3C Widgets part of my job. Exactly what is a widget, how do you create one, why would you want to, and which systems support them?
Personally I firmly believe that widgets are the future of the mobile web. They are easy to create, they're based on open standards, they save the end user quite a bit of network traffic, and many people around the world already know how to create them.
In contrast to other recent publications about widgets, I'll tell you the whole story — or rather, a condensed version thereof.
16 March 2009
| in Mobile testing
14 comments (closed)
Since my previous post about mobile browser testing I've had four days in Düsseldorf to play with mobile phones, and I've once again unearthed quite a few problems that mobile browser testers will encounter. So this post is mostly about how the situation is even more complicated than we thought.
You can look over my shoulder while I'm testing, as far as I'm concerned, as long as you remember that every bit of data is provisional and may change radically without warning.
If you're interested in real-time raw test results, follow me on Twitter. I regularly post my findings there, and it's already delivered me some excellent feedback.
In this entry we'll look at first-line and second-line browsers, mobile support for basic CSS, Opera's two modes, the failure of
@media handheld, Vodafone "content adaptation," the Nokia
keyCode problem, and we'll close off with a few fun browser facts.
The crucial question of the moment is: who asserts supreme control over the way a website looks on a mobile phone? Currently I'm arguing the author should, but Opera and Vodafone assert vendor control, with Opera also giving the user a modicum of control.
6 March 2009
| in Mobile testing
23 comments (closed)
About a month ago the software department of Vodafone Internet Services, based in Düsseldorf, Germany, asked for my help in creating mobile widgets according to the W3C Widgets specification. In particular, they'd noticed there are differences between browsers even on mobile phones (imagine my surprise), and decided they needed advice from a specialist (that would be me).
Better still, it quickly turned out that they were willing to pay me for doing serious mobile browser compatibility tests and publishing them on this site. The payment thingy is quite unusual, I can tell you (though not entirely unique).
This is easily the best job offer I've gotten in my entire freelance career, so I hurried to accept it. Meanwhile I've done mobile tests for five days; enough to offer some guidance for setting up a doctrine for mobile browser testing.
As far as I'm concerned you can look over my shoulder while I'm working, but please PLEASE remember that everything I say may change radically without notice after I've tested the same browsers on other devices.
Right now I've only done a few tests of functionality that's basic to the mobile experience, and even these basic tests will likely have to be expanded. Besides, right now getting a general feeling for mobile testing and its manifold problems is more important than running lots and lots of tests.
1 August 2008
| in Apple, Coding techniques, Content, Touch events
14 comments (closed)
Yesterday I walked into the local phone store because the "Temporarily Unavailable" sign had been removed from their "Get your iPhone here" poster. To my utter surprise they had six (6!) entire iPhones for sale, and no, there was no waiting list. I walked back home with a shiny new gadget, impatient to start testing it.
Meanwhile I've done some tests; now it's time for a report.
Before we continue, let's get the bad CSS news out of the way: Safari on the iPhone does not support
position: fixed. Certain Other Browsers were ridiculed for this lack; Safari won't be.
I've updated the CSS Table, the Core Table and the Events Table. In this entry I'm going to talk about JavaScript events on the iPhone. They're — interesting.
This is the blog of Peter-Paul Koch, mobile platform strategist, consultant, and trainer.
You can also follow
him on Twitter.
Atom RSS
I'm around at the following conferences:


text:
Rc Racing Sweatshirts are an Idakoos specialtiy! Idakoos has many things to offer. Whether you want to get a Rc Racing Sweatshirt for a special occasion, give a Rc Racing Jumper as a present or need to represent with a funny Rc Racing Crewneck Sweatshirt during Holidays or Family and Friends get-togethers, Idakoos is sure to have the right Rc Racing Sweatshirt for you! Even if it turns out you can't find the right Rc Racing Pullover with the perfect design for your mother, father or children (or friends!); Idakoos offers all of its men's women's and children's Rc Racing Sweatshirts as Custom Rc Racing Sweatshirts. Personalize any Rc Racing Crewneck Sweatshirt the way you want to ensure the perfect gift.
Showing 1 - 24 of 472 Sweatshirt


text:
KUALA LUMPUR (Feb 5): Patimas Computers Bhd, still the most active stock, fluctuated between lower and flattish levels for most part of today on profit taking and investor doubt over the future of the company.
Early yesterday, the stock leapt as much as 38% to 16.5 sen per unit after the firm said its new substantial shareholders planned to call for an extraordinary general meeting (EGM) to remove existing directors and appoint new ones.
But at close yesterday, it fell 4 sen or 33.3% to 8 sen per unit on trades of 385 million shares on profit-taking.
At 4.21pm today, Patimas share was flat at 8 sen on trades of 86.8 million shares, after fluctuating to a high of 9 sen and a low of 7.5 sen earlier.
Patimas said last Friday it had received notice from Syawaras Sdn Bhd and CPE Growth Capital Ltd requesting for an EGM for the removal of Datuk Ng Back Heang, Robert Daniel Tan Kim Leng and Law Siew Ngoh. The three jointly hold less than 1% stake in Patimas.
Syawaras and CPE, collectively own some 12% in Patimas, want to appoint Datuk Seri Abdul Azim Mohd Zabidi, Datuk Nur Jazlan Mohamed, and Lawrence Kwan Ho Ma to the board of the firm.
Nur Jazlan is the chairman of property developer UDA Holdings Bhd while former UMNO treasurer-general Abdul Azim owns Syawaras that holds 7% in Patimas. Hong Kong-based CPE has become a substantial shareholder in Patimas after acquiring 5.2% in the latter.
Chinese newspaper Nanyang Siang Pau reported today the trio have agreed to join hands to take control of Patimas. It was reported that the group intends to get government-linked IT projects for Patimas.
But a senior dealer told theedgemalaysia.com: "Investors took profit yesterday after the news. It continued today as they are unsure about the future of the company."
Investors' doubt stems from the fact that the new comers did not come out with any solid business plan to help the Practice Note 17 company out of its current predicament.
Patimas' huge share volatility in the past month has not helped either. The stock had risen sharply from 3.5 sen early January to 21 sen in mid-January, followed by a plunge to current levels amid wild swings in prices.
Bursa Malaysia had on January 17 warned investors to exercise caution in trading of the stock, reportedly to be one of the stocks under manipulative play by syndicates which the authorities still have not identified.


text:
Closet Cases
Like most other kids, I got my fill of cartoons every Saturday morning. In hindsight though, my television proclivities leaned toward the sitcom and somewhat frighteningly so. I remember feeling sorry for Edith Bunker because she was so meek. I was disturbed when George Jefferson would walk on British neighbor Harry's back to get the kinks out. I wondered why that robot kid in Small Wonder wasn't particularly cute. Some shows did me right without noticeable (until now) undertones. One was The Odd Couple. I never knew about the play or Neil Simon, just that this show was funny and that I could relate my OCD to Felix Unger. I saw the play finally a couple of years ago and gasped at all the subtext. Was I hearing right? Were Felix and Oscar really a closeted couple and even they didn't know it? It was all so clear and yet so shattering...because everything was innocent when we were kids. Right? Shattered. At least it was still funny. Tell me what you think when you catch ONSTAGE in Bedford's production of Neil Simon's The Odd Couple Friday and Saturday at the Trinity Arts Theater, 2819 Forest Ridge Dr. in Bedford. Tickets are $10 to $12. Call 817-354-6444 or visit onstageinbedford.org.
Fridays, Saturdays, 8 p.m.; Saturdays, 2 p.m. Starts: May 11. Continues through May 26
Get the Things to Do Newsletter
Sign up for our weekly guide to events in Dallas, and never be bored again. With suggestions for every day of the week, our recommendations will keep you busy on any budget.
Popular Stories
Upcoming Events
Event #13 Mega Satellite for Cash
TicketsSun., Jul. 23, 9:00am
Event #14 Ladies No Limit Hold?em
TicketsSun., Jul. 23, 12:00pm
The Bodyguard
TicketsSun., Jul. 23, 1:30pm
Event #15 $50,000 Guarantee No-Limit Hold'em
TicketsSun., Jul. 23, 2:00pm
Sponsor Content


text:
On evolution of an information dynamic system and its generating operator
- First Online:
- Received:
- Accepted:
DOI: 10.1007/s11590-011-0325-z
- Cite this article as:
- Belavkin, R.V. Optim Lett (2012) 6: 827. doi:10.1007/s11590-011-0325-z
- Citations
- 83 Downloads
States of a dynamical information system can be represented by points on a statistical manifold—a subset of a vector space endowed with an information topology. An evolution of such a system is considered here with respect to changes in information rather than changes in time, because differences between states are represented by an information distance. Here we consider an optimal system maximizing a utility of an abstract information resource, and then analyze properties of information such that an optimal system is described by an evolution operator or a semigroup. The latter is generated by an operator that can be interpreted as a utility, payoff or a fitness function. We discuss the advantages and applications of the proposed approach.
KeywordsUtility of information Evolution operator Semigroup Monotone operator
Unable to display preview. Download preview PDF.


text:
Welcome from the swamp. Enjoy.
Hey, 19 year old college student here. I'll be 20 in april
I've always been interested in guns, hunting, and things of that nature but coming from the nothern part of the state no one around me is really into any of this stuff. Infact, It seems like 95% of people around me believe there is no need for a gun, or are just plain scared of them!
My state has a "may-issue" law which is basically a big fat NO to carrying a hand gun. I wish this would change, but i dont see it happening anytime soon. Either way, I plan to apply for one when I turn 21 in around a year.
I like to research things before I buy them, so I figured i'd sign up early and start learning now.
I've only personally shot 2 guns before... a 22 and a springfield 1911 45
Both were awesome guns, obviously I'd prefer the springfield though
My friend just got his permit so we've been searching and reading reviews for his first gun. I'm sure i'll be shooting with him shortly
Take care!
Welcome from the swamp. Enjoy.
Welcome from the mountian top in North Carolina. Take the time to get a basic handgun training class and enjoy.
Welcome aboard from the sandpile. I was born and raised in N.J (exit 105). I left about 5 years ago. I know what you're going through dealing with the idiot system up there. Stick it out and go the correct route to get your firearms. I gave up, then moved to Fla.
There is a member here who may be able to help you. He signs on as Robanna. He's near Exit 135. Maybe that's not too far from you and maybe "youse" guys can hook up.
Also, scroll down the main page of this forum, find the area marked "Regions", and see if you can find someone in the New Jersey section.
Jump in. Enjoy. That's what the forum is all about.
Welcome from another in NC.. I'm 39 and new to handguns (but if it's long, bolt action and good for going to war with tasty deer-delskies I'm comfy with it).. but now with a couple little tikes.. I've decided I need some bad medicine at hand with the recent break-ins locally recently.. Plus I just plain want the experience and enjoy shooting, whatever it is.. including arrows.
Either way, I want a handgun as a hobby and HD
Welcome from a Texas newby. I have in-laws in Howell and Whiting. I worked in NY for a few years and lived in Clifton. Sure was glad to move back home to a warmer climate. I actually liked my brief stay in NJ, met a lot of good folks.


text:
Ships Free to USA*!
Master Whisk, variable speed, non-detachable, immersible whisk length 10", whisks up to 5 gallon, beats up to 50 egg whites, w/10' cord and plug, 350 watts, 300 to 900 R.P.M., overall length: 25-1/2. 115V.
- Dynamic manufactures an extensive line of high quality hand held mixers, food cutters, salad spinners, and other commercial food service and restaurant equipment.
Are you familiar with this product? Be the first to review this item!


text:
possible trade 19x9.5 22 offset
hey guys i just purchased a new set of csl wheels and i think the front offset is a liltle bit aggressive maybe wondering if anyone might be interested in trading my 19x9.5 22offset for their 19x9.5 30 offset
trade will include tires hoping they are in same condition.
possibly money on top
looking for a clean no curbage wheels since mine are new
lmk located sfv
Do you have any pics? Would you sell without a trade? What brand are the wheels?
i think if i cant find a trade i might just add a spacer in the rear so the rear looks just as aggressive
Keep em! i have VMR v701s 19x9.5 +22 all around. Put some 225/25s or 235/35 all around and youll be set!
Im running em on a dropped e46 sedan btw, you can definitely make em fit!
Man thats a aggressive the idea though ^^^^ any pics???
|All times are GMT -5. The time now is 06:49 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
(c) 1999 - 2016 performanceIX Inc - privacy policy - terms of use