The on-again, off-again deal by the two internet giants was signed back in July, but regulatory approval by the European Commission and the US Department of Justice only came through this week.

According to a joint statement made by the new Search Alliance, changes will start being implemented very soon. Microsoft is to power the search technology on both Bing and Yahoo but each site will continue to operate under its own identity;

“Implementation of the deal is expected to begin in the coming days and will involve transitioning Yahoo!’s algorithmic and paid search platforms to Microsoft, with Yahoo! becoming the exclusive relationship sales force for both companies’ premium search advertisers globally. Once the transition is completed, the companies’ unified search marketplace will deliver improved innovation for consumers, better volume and efficiency for advertisers and better monetization opportunities for web publishers through a platform that contains a larger pool of search queries.” From Yahoo’s official press release.

Microsoft CEO Steve Ballmer previously described the move as a way to provide “real consumer choice in a market currently dominated by a single company.” Unsurprisingly Google, which controls over two thirds of the search market in the US had tried to prevent a deal between its main search rivals. Back in 2008 when Microsoft bid almost $45bn to acquire all of Yahoo!, Google openly attacked the move as anti competitive and tried to sign its own deal with Yahoo Search Business. Google were eventually forced to pull out of that deal after the US Department of Justice questioned the antitrust implication of one company controlling what would have been an estimated 90% of the US search market.

Whether the new alliance will put a halt on Google’s burgeoning search market share remains to be seen. With a combined search market share less than half than that of Google, they certainly have their work cut out for them.

As the iPhone I got is the original iPhone I cannot compare the hardware as the iPhone 2G is about a year and a half older than the HTC Magic. What I can compare is the operating system though ( OS ) as the iPhone is updated to the very latest 3,12 version.

Mail, Calendar & Contacts
Before you do anything on Android it asks for your gmail account. As soon as your email credentials are confirmed your gmail, contacts and calendar start to synchronise. Any changes are synchronised between the google servers and your phone. What’s best is that gmail has push email similiar to the Exchange Activesync process or the Blackberry solution. Speaking of Exchange, the ROM’s I intalled came with the Exchange mail clients, making it easy to have work emails and calendar events pushed to your phone.

After booting the iPhone the first thing I did was click on the mail icon on the springboard. The google account was easy to configure and the account connected first time as expected. Then I was left a bit confused as to how to add the Exchange email account. After a bit of fiddling around I found the mail settings section where I could add the exchange account. It worked first time and push notifications was set “on” as default. The iPhone email account for gmail does not support push, instead the email client periodically checks the server for any new emails.

Exchange calendar  and contacts are automatically synced to the iPhone calendar application. Unfortunately the same is not true for the gmail calendar and contacts.

Browser

The iPhone sports a mobile Safari which is super fast. The two browsers load speeds are more or less on par. Browser rendering is also about the same, where the only difference is that the Android browser has an option to reformat the layout to fit the width of the browser. Safari does not do this but it has a very good scaling feature: pinch to zoom. It uses multi-touch gestures to scale the browser. The response is quite fast, even on the older hardware, and it gives the Safari browser an advantage over the Android browser which only offers scaling by using buttons.

User Interface

The iPhone user interface is well thought out. I found the small animations and attention to details  very helpful. The navigation is equally well thought out, letting one know that you headed into or out of a section. The one thing that makes this user interface works well is that almost all applications use the Cocoa standard UI elements, so navigation elements are generally consistent.

Because Android has physical menu and back buttons at the bottom it took me some time getting used to the navigation buttons within the iPhone apps. I grew frustrated as I kept hitting the bottom physical button on the iPhone to go back and got sent to the home screen.

I feel that the Android physical keys are quite useful as it gives the applications a standard way to navigate in and out of sections within the application as well as between applications.

One thing I did find annoying was the way that the iPhone OS had you navigate between applications. Since the iPhone does not support multitasking between 3rd party applications, you can run only one applications at a time. This improves the speed of the applications themselves, but at the same time prevents you from running applications in the background. This is a big let down for me and is actually a deal breaker.

Applications

The Apple App store is a much richer experience than the Android App market. It has much more applications , almost a 100 000 more. Because of this large number of applications there is an equally large number of high quality applications. I found quite a few duplicates between the two application stores showing that developers are creating apps for both platforms.

One thing that bothered me was that I had to sign up with my credit card before I could install any applications.

Apple applications are well designed and in some cases have much better features than their Android counterparts. The Apple applications have at least double the number of  options that the Android version have.

Finally

After spending about a week with an iPhone as my main phone I feel seriously disconnected. When I want to know if I have an email I have to unlock the phone and check the home screen. It does not have an alert light telling me when I have message . Yes, it does give a vibrate and an alert sound, but sometimes I don’t hear or feel those alerts. When in an application and you get an alert you would have to quit the application to go the home screen to check what the alert was for. Android’s notification system is a lot more elegant.  Android has a top drawer that has alert icons pop up when they arrive, you can then slide down this drawer to see more information and when pressed it would send you directly to the application.

I enjoy the nice user interface but that does not compensate for the lack of multitasking ability, or for the poor notification system.

If Apple wants to keep the iPhone as one of  the top smartphone OS’s in the future it will seriously have to rethink its notification system as well as the multitasking capabilities for 3rd party applications.

From 25th till the 31st january, the 3rd. edition of Campus Party Brazil took place in São Paulo. The event, that is said to be the biggest one in technologic innovation, internet and eletronic entertainment, has been held since 1997 and happens in four different countries annually: Brazil, Spain, Mexico and Colombia.

In Brazil, it started in 2008, after 12 editions in Spain, and it was the second country to host it. It receives about 6000 participants every year, most of them camping in the event and participating in talks and debates that happen 24 hour a day. It is divided in 12 areas of interest, including development, robotics and security.

It has had speakers such as Tim Berners-Lee and Steven Johnson. This year, there were 3 big international names: Kevin Mitnick, Scott Goodstein and Lawrence Lessig.

The first to speak was Kevin Mitnick on the second day of the event. Mitnick was a famous cracker that was arrested in 1995. At that time he was the most wanted computer criminal in the U.S. Today he has a security company, Mitnick Security, of course. His talk, entitled The art of Deception, was mostly about social engineering and how people should learn to say no.

The next day, it was Scott Goodstein’s turn. He was responsile for Barack Obama’s online campaign in 2008. He talked about the importance of cellphones in the campaign and defended the mobilization of small and specific groups so they can call friends and create something bigger.

Lawrence Lessig did the last presentation, Friday  afternoon. The Stanford Law School professor founded Creative Commons, an alternative license to copyright. He talked about intellectual property, how the internet changed access to culture and how current copyright law harnesses creativity.

Swat member, Rafael Dohms also gave a talk in the event, Awakening to PHP, an introduction to PHP.

Most videos of the event are available in their Youtube channel : http://www.youtube.com/campusparty (most of them in Portuguese).

Many interesting concepts and theories were discussed, but what stayed with me was that no matter what service or product you are providing or building, the focus should always be on the user. In fact, a consumer-oriented approach is the only way to build a long term competitive advantage (barring of course government-supported monopolies like Telkom, which is finally facing real competitive forces). This is why companies like Amazon, who are obsessive in their mission to please consumers and make every business decision based on whether the intended results are ‘good’ for these users, are streaking ahead of the competition.

Having a user-focused strategy, as opposed to a product/service-focused one, has several benefits:

• More time. Focusing on technologies and trends, which change quickly and are difficult to predict, causes companies to constantly chase the next big thing, and can cause stagnation when a standard is slow to emerge and market players stay on the sidelines before investing (as could be seen with the Bluray vs. HD-DVD battle). Focusing on user behaviour, which changes relatively slowly and is easier to predict, allows forward-thinking companies to focus their energies on satisfying user needs. For instance, in the case of the next-gen DVD saga, companies lost track about how user behaviour was shifting to wanting video anytime and anywhere (online, mobile and TV – the so-called ‘three screens’) while deciding which physical format to back.
• Network effects. Product-focused companies design a product with the aim to sell it – which is where it ends. As long as the user can be convinced to part with cash to purchase said product, the product cycle is completed. A better approach can be to build a product/service that harnesses network effects, i.e. the more users you acquire, the more benefit they derive from using your product or service. The classic example of direct network effects is an online auction service – the more buyers you have, the more sellers are attracted to the platform, which in turn attract more buyers as the number of items increase. Such networks are incredibly hard to break, which is why eBay in the US remains entrenched. As a bonus, indirect network effects in the form of complements can make your product even more valuable. Apple’s iPod, with its thousands of add-ons, and the iPhone, with its hundreds of thousands of applications, are much more desirable and valuable in the eyes of consumers because of these complements.
• Differentiation. When companies focus on product/service quality and number of features, there is a constant battle to be superior, have more, look better. This is both costly and difficult to maintain, especially when this is how your brand is defined (Sony again comes to mind). As Ranjay Gulati puts it, “In a marketplace like today, customers have more choices and more information, and services start to look like each other, in what we call a sea of sameness. If you don’t have an ability to transcend beyond the features and functionality of my product versus yours, then you have a problem.” User-focused companies don’t concentrate and obsess about rivals, but rather think about users and their needs. Instead of competing on a product-by-product, segment and geographical basis, they design their products and services around user habits and requirements. In the end, it’s your users you want to be happy, not your engineers or developers.

Gulati goes further to say that there are three keys to transcending the ’sea of sameness’ and become customer-centric:

1. Ask the right questions (i.e. “What problems are customers dealing with?” and “What are the issues happening in the life of my customers?”)
2. Make the creative leap – by asking the right questions to figure out the innovations that will best serve your customers.
3. Get your organization aligned around what customers want, rather than around product and geography.

So ask yourself: is your awesome new service with its long list of kick-ass features, or the shiny product that will change consumer electronics forever, actually satisfying some basic need? Will it delight your users, make their lives better or easier?

“The real power of the Semantic Web will be realized when people create many programs that collect Web content from diverse sources, process the information and exchange the results with other programs. The effectiveness of such software agents will increase exponentially as more machine-readable Web content and automated services become available. The Semantic Web promotes this synergy: even agents that were not expressly designed to work together can transfer data among themselves when the data come with semantics.”

Despite the ever-growing number of available  Web services, they are rarely described formally, which keeps them from joining the third phase of the Web. Service descriptions, if any, are typically informal, written in natural language and therefore available to human consumption only. Tim Berners-Lee highlights the need for semantically described Web services as follows:

“Many automated Web-based services already exist without semantics, but other programs such as agents have no way to locate one that will perform a specific function. This process, called service discovery, can happen only when there is a common language to describe a service in a way that lets other agents understand both the function offered and how to take advantage of it.”

Considering the above vision, it is reasonable to conclude that any given service should be offered the opportunity to join the Semantic Web, regardless of the technologies and protocols it relies on. There are basically two groups of services, namely RPC and RESTful. They represent completely different approaches to implementing Web services, but Semantic Web researchers should be able to address both equally.

The problem is that only RPC services have been covered by authors writing about the Semantic Web. In fact, the term Web Service is frequently used as synonymous with RPC. This may be the result of the strong SOAP protocol promotion carried out by the software industry, especially large enterprises such as IBM and Microsoft.

I would like to introduce a new concept: RESTful Semantic Web Services. The proposed set of protocols to formally describe a RESTful SWS includes HTTP, WADL, OWL-S, and URI. The following table compares this protocol stack with the one powering RPC SWS:

_

It is important to bear in mind that both semantic and syntactic descriptions have to be provided by any given service. Only then will the service be considered to be fully described. Semantics and syntax allows software agents to automatically discover and invoke the service.

The OWL-S protocol had to be extended in order to allow for RESTful SWS, because its original specification covered RPC SWS only. Fortunately, OWL-S defines an abstract layer that enables software engineers to create multiple grounding strategies. A more detailed description of OWL-S goes beyond the scope of this blog post, but grounding can be seen as an approach to mapping a semantic description to a syntactic one.

The extension proposed is classified as Web ontology, and it’s been named RESTfulGrounding. The page describing this ontology contains the full paper that introduced RESTful SWS to the academic community in 2009. It also contains the ontology description in OWL and a proof-of-concept on a Web service provided by Yahoo.

(Post also published at FullSemanticWeb.com)

The first item is the release of Apple’s Tablet. The impact of this device will be to make it abundantly clear to the consumer that the Web is to be had without the need for a typical computing device – no laptop required here. The Apple tablet will be an elitist device outside the US (as is the iPhone), but may turn out to be the poster child for convergence. As the delivery mechanisms for all content becomes IP networks, the consumer will cease to think of print, television and web content as different from each other – all will be one, as demonstrated by the Apple Tablet.

Microsoft’s Project Natal will be released into the wild. Forget augmented reality. This will be the first step towards extended reality, the blurring between virtual and real. The success of Avatar, the movie and the increasing availability of devices with three-dimensional displays will contribute to the acceptance of extended reality as an everyday reality, because the display techniques they use appear to intrude into the “real” world.  This will smooth the road towards wide adoption of extended reality as a user interface mode. (Finally – a replacement for the mouse.) 2010 will be the year we start adding reality to the “real world”.

And finally – this year will resolve the question of how the planet’s largest social and communications platforms can evolve to have viable business models. Both Twitter and Facebook have massive and growing user bases, but neither have a clear plan for exploiting this user base – the sheer number of users, and the wide global distribution of these users should offer unique opportunities. I believe that 2010 will be the year that a way is found to exploit the mega-nets – paving the way for planetary connectivity, and the giga-net.

In summary, my three (almost) sure things for the year:

• Convergence, convergence, convergence. The medium is changing, and so shall the message.
• Extended reality starts entering the mainstream.
• A way is found to exploit mega-sized social and communications networks commercially.

There are a number of other trends which I believe will have a significant impact on the web-as-we-know-it: semantic markup is becoming ever more ubiquitous without anyone really noticing; cloud computing is maturing; entirely new modes of internet usage is establishing itself in developing countries. Mobile internet usage continues to increase. Broadband penetration will continue to grow, enabling more and more users to join social and communications networks – we will see the rise of the giga-net within a very few years.

But I believe the three most significant  changes in the WAWKI will be triggered by the three events I listed here. Your mileage might vary – tell us about it.

Nimbuzz for Android.

Nimbuzz is a mobile instant messaging and social networking client available on most mobile phone handsets including Google Android. Skype, Windows Live Messenger (MSN), Yahoo Messenger, ICQ, AIM, studiVZ, GoogleTalk, Facebook, MySpace, Jabber and many more are supported.

News24 for Android

News24 is the number 1 news site in South Africa. Features of the Andoid app include:

• Up to the second news, sport, finance, motoring and entertainment news
• View current and 7 day weather forecast
• Local restaurant search
• Customisable homescreen widget – select content and set refresh rates
• Share content, provide feedback & choose start-up view
• Easy tabbed navigation
• Touchscreen or TrackBall interface – with haptic feedback (vibration) option
• Read stories in portrait or landscape mode

MXit for Android

MXit is an Instant messaging and social networking platform for mobile phones. Founded in South Africa it now has millions of users throughout the world.

This list of Android applications are all available to download in the Android Market Place. As the various companies develop and release new Android applications it will be updated here.

Let me give you a glimpse of what the event tries to accomplish and tell you what came out of it in 2009. MSWDS is all about communication. It is a yearly event that allows Microsoft to get in touch with key players in the PHP community and interact with them on various levels. This means they get to ask us questions, and we rant and ask them questions. It is a an effective way of getting Microsoft and PHP to do better business together, which in turn means getting better tools and better performing PHP applications on Microsoft platforms. Both sides get to know more about how the other operates.

Over 3 days Microsoft and the PHP community shared notes, discussed various products and opinions and shared quite a few beers and dinners at the Redmond Commons Campus.

Microsoft has been very active in the PHP area and even though this is often received with skepticism by the overall community their actions are generating a lot of benefits for the PHP community specifically and Windows users in general. You cannot be right all the time, so Microsoft is still making some mistakes, but it is worth looking at some of what they shared with us. The final day of the conference was held under a non-disclosure agreement and is therefore not included here.

One of the highlights of the event was a project led by Garrett Serrack describing the process and plans for making PHP and associated libraries easier to compile from source on Windows – a project that could give Windows a push as a viable platform for PHP, since custom PHP compilations are a big part of PHP sites. Also very interesting were the news of WebPI and IIS. IIS is working on being a centralized dashboard for system developers and administrators and new tools like the SEO toolkit are laying down a new track for innovation. The road ahead for this is still long, but Microsoft got a lot of feedback on the kind of deploy and maintenance oriented services we developers would like to see such as imporvements to WinCache to offer more features and make it share the spotlight with APC.

The WebPI project made life for PHP application users a breeze – its simplicity and the application gallery makes it very simple to install a complete web platform and get a site up and running. The same is not true for developers. Solutions were gathered to address developer needs – amongst these are multiple side-by-side versions of PHP and other applications, automated testing and closed cycle solutions that can contribute back to our applications as well as make our life deploying and testing before releases much easier on this platform.

During our airing of grievances many topics came up which Microsoft really needs to address. The long lead time to new projects and solutions and all the bureaucratic red tape that needs to be cut was the starting point and showed Microsoft they are the ones slowing themselves down. We also highlighted the areas of the world that need more attention from Microsoft evangelists. Recurring topics such as drivers for SQL Server and better developer tools for IE7 and IE8 came up as well.

One matter that generated heated arguments was the Codeplex Foundation. The discussion was triggered by ill-timed and not unplanned comments of an “info-mercial like” nature. Unfortunately Microsoft is still a huge corporation and parts of it still does not understand that the developer community does not want marketing pitches. The message hit home and some sessions reverted from that format, but the Codeplex idea was still not palatable tomost of the people present. The topic was later brought up in a round-table discussion and disagreements were addressed, showing that Microsoft is willing to correct some mistakes.

Some sessions had .NET solutions at their heart and were not very effective in communication, some were interesting enough to generate in us the desire to copy them, but in my opinion these were not really in their right place for the objective of this event. New technologies such as PowerShell, Azure and Silverlight got lots of attention and showed some in the room that these could be much more useful than they thought it could be.

Silverlight triggered further discussion with its use in Bing Maps – the latter is now live with very striking visual effects. Microsoft’s skill for naming projects was criticised many times especially after we figured out that the “ASP.NET Ajax Toolkit” was an ajax library that had nothing to do with ASP.NET. This was dully noted by MS for future naming.

Microsoft also had an opportunity to listen to the main players in the PHP community about the community itself, Ramsey went over some concepts of user groups and I talked about the new organization of user groups in Brazil (simple slides). We also had sessions by Marco and Keith on uncons and community participation, as well as a few sessions on tools and frameworks/closed apps.

One of the sessions explained how we can get in touch with Microsoft and gave us some insight on the internal structure and roles of all Microsoft related posts. This session was great and also opened the floor to questions from both sides.

The end result of the summit was very positive, even though we may only start seeing concrete results in a few months or even a year. The important message i got out of the conference is that Microsoft is working hard on matching Linux as a viable deploy platform and development platform, but more than that they are looking to go one better and innovate. Investing in professionals that develop PHP and its related libraries is also a way that Microsoft can help PHP to be even more viable on Windows. I guess it is becoming more viable and you should give it a try.

I look forward to some of the new tools and features of current products that were showcased in open and closed sessions – I believe Microsoft has a chance of doing great things for the PHP community.

For the team that organised MSWDS all I can say is that you did more then an awesome job: the hotel was great, social events were a great opportunity to get into more detailed talks about the day’s topics. The whole event went down without a glitch – thank you very much for all the hard work.

For those not familiar with Scrum, let me summarise the key principles quickly:

1. A project team is setup usually consisting of between 5 and 9 resources.
2. The resources within the team have the set of skills needed to develop products.
3. There are defined roles within this setup, namely

• The Product Owner: Manages a list of product features that require development. These features are prioritized by the Product Owner.
• The Scrum Master: Ensures that the processes are followed and helps the team deliver the product features by removing any impediments that prevent them from delivering.
• The Team: Self organises around the product features and collectively work together to deliver these product features.

I’m simplifying the roles here of course – there are further responsibilities that are played by each role, but this is the essence.

4. The team produces working demonstrations of the product features at regular intervals (typically every two weeks).
5. These working demonstrations are visible to the business, allowing the business to get a view on where the product is going and whether it needs refinement or a complete change in direction.
6. The refinements or improvements are then fed back into the team, prioritised by the Product owner and driven through to demonstration once again.

The framework is agile in nature. Problems are quick to identify, and quick to change. Traditional project management methodologies would allow a project to proceed down a long and drawn-out development path and if the up-front analysis had not been 100% accurate, or if external factors had required a change to the project during development, this would be very difficult to accommodate. The Scrum process by contrast makes sense – it is a simple, logical way of delivering projects and caters for changing requirements.

That said, the question of how to setup the Scrum team and environment remains. As a new team, we are facing these questions and trying to figure out the best path to creating the esteemed “High Performance Team“. There are two schools of thought here. Let me deal with the first.
As competent and experienced team members, there is a sense of “doing things right, from the start”. This includes everything from ordering the right development hardware, deciding on what software is appropriate, defining the practices and principles the team is going to follow, which languages are best suited for the projects that need to be developed, and what the collaboration environments need to look like. All good stuff, and completely necessary. The planning also includes discussion and decisions around how to test the code that is developed, how it is documented, how much of this is automated versus manual, which tools are best suited for testing, how new issues get logged and fed back into the team, and how much test coverage is considered acceptable. Again, all good stuff, and all appropriate to the work that is being done within the team. It is also a good idea to get the overall context of the project defined up front so that broad architecture decisions can be made. Where the team needs to be careful however, and we are all sometimes guilty of this, is when it comes to over-engineering a solution up-front. Chances are that this picture is changing, or will eventually change. Nothing wrong with good architecture up-front, but trying to understand too much detail too soon is probably wasted effort.

Lets take a look at the second school of though for a moment. The principles of Scrum and Agile development methodologies and practices suggest that the value lies in delivering small, incremental features, regularly. Mistakes and changes to project scope are inevitable and it is the ability of the team to correct these mistakes, and accept the changes in scope that makes them “High Performance Teams”. Through continuous feedback and team “retrospectives”, the gaps get filled, and the holes get plugged. The team continues to improve as a result and the delivery continues to speed up – well, from the initial stages anyway. Its a situation in which the team adapts the principles of Agile software development to suit their unique environment, the individual strengths and weaknesses and their team characters.

The point that I am trying to make here, is that there are two ways to try and achieve the “High Performance Team”. There is the “Lets build the 6-foot armour-plated robot with Augmented Reality vision”, or, the “Lets build the stick man and determine what he needs next” approach. There is a fine line between setting up a team that does everything right from the start, and a team that is setup to learn how to do what is right for them.

I was recently made aware of an agile development team based in the UK that has been together for the past 60 months. They deliver code weekly, have a number of visible metrics for how many bugs are in their system and how quickly they are resolved, what the velocity (capacity for delivery) of the team is, converted into monetary value, and a number of other “reporting” metrics. Incredibly useful information, and a sign that they are a “High Performance Team”, but I wonder how much of that was setup from the start, and how much of it “evolved” as the team progressed through their 60 months of development together?

To take the analogy used above, whilst it is important to have a team vision in place and to follow best practices where ever possible, I firmly believe that it is best to create the stick-man from day one, and get him running in an agreed direction, rather than spend too much time thinking and planning the 6-foot robot that potentially is only capable of taking a few steps at a time, and hopefully, in the right direction.

That being said, our team is in a good place. We are positioned nicely and are moving forward as a unit. Hopefully the discussions that our team have had, and the conclusions drawn here, can help you position and setup your own team.

Have you ever come across a website and saw some really interesting aspects of the user interface ? Maybe it was a site design that looks like a flash site but was not? Or maybe you came across a site that had a visually appealing menu.

Coming from mostly a backend-development background I get this feeling often. Last week it happened when I saw the Hide option on Facebook. I have seen it a hundred times before but on that day I found myself wondering, so I recreated the sample in my own way from scratch.

The following questions came to mind while looking at Facebook’s implementation:

1. how to make the hide option, appear next to feed item that the mouse is hovering over.
2. how to make the ‘menu’ item under the hide option appear and stay there when the Hide button is clicked
3. how to remove the selected options from the list without having to refresh the whole page
4. how to send the filter option to the server without posting back the whole page

I decided that I will use styling and jQuery to complete steps 1 – 3 and use a ajax call via jQuery to post the selected filter option back to the server.

Note that you will need some prior knowledge of jQuery selectors in order to follow the code sample. See the following urls for some background information on this:

• http://woorkup.com/2009/10/05/jquery-lesson-series-introduction-to-selectors/
• http://docs.jquery.com/Selectors

The following are the steps I completed to make these options work:

Create the folder structure:

1. Download the latest query plug-in (jquery.js in the screenshot) from http://jquery.com/
2. Create your project with necessary files. See the screen shot for my folder structure:

Import the style sheets and javascript files:

1. Place the following statements in the index.php file to reference the style sheets and javascript files

<html>
    <head>
        <title>How did they do that: Facebook Hide</title>
        <link type="text/css" rel="stylesheet" href="styles/default.css" />
        <script type="text/javascript" src="js/jquery.js"></script>
        <script type="text/javascript" src="js/jquery.feedfilter.js"></script>
        <script type="text/javascript" src="js/hidebutton.js"></script>
    </head>
<body>

Create the news feed items:

1. The sample only shows one of the news feed entries for clarity sake. Repeat item-container div for each additional item you want.
2. Note the following things when reviewing the snippet
   1. The class name for the feed item is item-container.
   2. Hide-button is a child element of item-container
   3. Hide-menu-header and hide-button-options are child elements of hide-button.
   4. The hide-menu-header relates to the Hide button on the screen shot and hide-button-options relate to the menu item under that.
   5. The custom user attribute on the span. This is the id (in our case a fictional id x) of the user’s events that must be filtered. This is the value that will be posted back to the server during the ajax call.

<body>
    <center>
        <div class="item-container">
            <div class="left">
                <div class="left">
                    <a class="left" href="/profile/sampleprofile">
                        <img class="profile-pic" src="images/avatar.png" width="55px" height="55px" />
                    </a>
                    <div style="clear:both"></div>
                </div>
                <div class="info">
                    <p>
                        <strong>
                            <a href="/profile/sampleprofile">Bruce Banner</a>
                        </strong> posted on twitter
                    </p>
                    <div class="detail">
                        <a href="#">8 hours ago</a> | <a href="#">comment</a> | <a href="#">like</a>
                    </div>
               </div>
           </div>
           <div class="hide-button">
               <div class="hide-menu-header">
                   <input type="button" value="hide"/>
               </div>
               <span class="hide-button-options" user="x">
                   <input  type="button" value="Bruce Banner" />
               </span>
          </div>
      </div>
...
<center>
<body>

Link up all the events to the appropriate elements:

Add script to hidebutton.js. The $(document).ready(…) construct is used to ensure that the initialization is only run once the full DOM is loaded. Note that $(document).ready(…) will run as soon as index page is loaded because it is imported in index.php and is not wrapped by any functions.

The script calls three methods that in turn use jQuery selectors to find the appropriate elements by class name or id and then links events to them.

• initializeFeedItemHoverEvent: adds the hover event to all elements that contain class item-container (news feed entries). There are 2 functions in this method. The first is fired when a mouse cursor is moved over the element and the second is fired when the mouse is moved away from the element
• initializeHideMenuClick: adds a click event to all hide-menu-header (hide menu button) items. It uses $(…).parent and $(…).find to find the appropriate elements relative to the current element. $(this) in this method relates to the hide menu button. It also uses removeClass and addClass to toggle the selected and unselected appearance of the hide menu button.
• initializeHideSubMenuClick: Calls the feedfilter() method (explained in the next step) on the appropriate hide button sub menu element. The feedfilter() method will use ajax to post the filter back to the server.

//file: hidebutton.js
$(document).ready(function() {
    initializeFeedItemHoverEvent();
    initializeHideMenuClick();
    initializeHideSubMenuClick();
});

//Initialise the hover events over the newsfeed entries function initializeFeedItemHoverEvent(){
//Find all newsfeed items that have a class called item-container
$('.item-container').hover(function() {
        //Show the hide button when the mouse moves onto the item
        $(this).find('.hide-button').show();
    },
    function() {
        //When the mouse cursor leaves the newsfeed item,
        //hide the hide button and reset the styling to original
        var hideButton = $(this).find('.hide-button');
        hideButton.hide();
        resetStyles(hideButton);
        //Hide the submenu of the hide button
        $(this).find('.hide-button-options').hide();
    })
}

//Initialise the click on the hide menu item
function initializeHideMenuClick(){
    //Find the hide button the user clicked and toggle (show/ hide) submenu
    $('.hide-menu-header').click(function() {
        //Find parent with class 'hide-button' of the current element
        //from there find the child of the found element called 'hide-button-options'
        var element = $(this).parent('.hide-button').find('.hide-button-options');

        //Find out which class is set on the current element
        //and based on that set a different class
        if ($(this).attr('class') == 'hide-menu-header'){
            $(this).removeClass('hide-menu-header');
            $(this).addClass('hide-menu-header-selected');
            element.show();
        }
        else {
            $(this).removeClass('hide-menu-header-selected');
            $(this).addClass('hide-menu-header');
            element.hide();
        }
    })
}

//Initialise the click event on the hide sub menu
function initializeHideSubMenuClick(){
    //When the user clicks on the menu option then
    //call the feedfilter method in the  jquery.feedfilter.js file
    if ($(".hide-button-options").length > 0) {
        $(".hide-button-options").feedfilter();
    }
}

//Hide the menu button and its sub menus
function resetStyles(hideButton){
    var menuHeader = hideButton.find(".hide-menu-header-selected");
    if (menuHeader != null){
        menuHeader.removeClass('hide-menu-header-selected');
        menuHeader.addClass('hide-menu-header');
    }
}

Complete the server post back:
The following section describes the code that fires when a user clicks on the hide button sub menu option. It first extracts the user id that is stored in the custom user attribute and posts it back to the specified page.

Note the if (response == “success”) {..} section. It finds all the news feed items with a sub element that has a user attribute with the same value as the news feed item that the user chose to hide.

//jquery.feedfilter.js

//Specifiy the feedfilter function definition
//What must happen when the user clicks the sub menu item
(function($) {
	$.fn.feedfilter = function() {

		this.click(function() {
			//Call setFeedfilter
            setFeedfilter($(this));
			return false;
		})

		function setFeedfilter(obj) {

            //Get the value of the user attribute on the current element
            //as the user clicked on the hide sub menu the current element is
            //the hide sub menu
            var user = obj.attr("user");
            var container = obj;
            var originalContent = container.html();

			$.ajax({
		    	type: "POST", //post back method
		    	url: "ajaxpostback.php", //page to post back to
		    	dataType: "json",
		    	data: {"userId": user}, //additional parameters
		    	beforeSend: function(xmlhttprequest) {
                                //change the content of the sub menu button to appear as a
                                //loading animated gif
		    		container.html('<img src="\" alt="\"loading\"" />')
		    	},
		    	complete: function(xmlhttprequest, textStatus) {
                               //add any code here that should fire once the post back
                               //is completed
		    	},
		    	success: function(response) {
                               //add any code that must run once the postback is completed and
                               //successfull
		    		if (response == "success") {
                        $(".item-container .hide-button-options").each( function() {
                               var data = $(this).attr("user");
                               if (user == data)
                               {
                                   $(this).parent('div').parent('.item-container').hide();
                               }
                            }
                        );
		    		}
                    else
                    {
		    			alert(response);
		    		}
		    	},
		    	error: function(xmlhttprequest,status,error) {
		    		alert("There was a problem with filtering events.");
                    container.html(originalContent);
                    }
		    })
		}
	}
})(jQuery)

What happens on the post back page?

I have not implemented the actual persisting of the filter setting but have shown how to retrieve the parameter value passed from the client side.

<?php
    //Persist $_POST["userId"];
    echo json_encode(array("success"));
?>

View the result

Browse to the index.php page and you should get something similar to the screenshot shown below.

What’s next?

• Styling can be refined. I used some inline styles etc that can be moved to the style sheets.
• Content is static at the moment. The news feed items would normally be generated from a data store of some sort
• Add additional error handling
• I used inline php and markup together to simplify the example. Best practice though, is to split your php code and markup. One approach would be to implement the Model View Controler (MVC) design pattern. A good option for this is to use the Zend Framework (http://framework.zend.com/). It implements the MVC pattern and has loads wrapper classes that wraps commonly used functionality to promote reuse.