Find The Correct Download Link

Find The Correct Download Link:

Valentine's Day and George Ferris' 154th Birthday

Valentine's Day and George Ferris' 154th Birthday:


Date: Feb. 14, 2013

Romance and amusement parks often go hand in hand. In many places a carnival, fair or circus is a popular destination for a thrilling and action-packed date. Coincidentally, George W.G. Ferris Jr., the creator of the Ferris Wheel was born on Valentine’s Day in 1859. This year seemed like a golden opportunity to combine our celebration of love with the birthday of the engineer whose mechanical invention has filled so many hearts with wonder.

Rough concept sketches. At one time a dragon and a piece of bread (toast?) were going to have a great time together.

Early in the process we decided on depicting a scene with two, side-by-side Ferris Wheels among a landscape of other amusement park rides. Then when two Ferris Wheel carts happened to stop across from each other we thought that was the perfect moment for two characters to have a love at first sight moment. We thought this would be the best way to highlight the Ferris Wheel in its natural habitat and provide a clever way to introduce some valentines to each other. Plus, we thought it would be fun to push a big button to generate a whole series of combinations.

An outtake from the early interactive mock-ups. The characters are featureless blobs but the basic ideas are there.

The greater challenge turned out to be determining who would be riding these Ferris Wheels. What pairs would we create? How silly should we be? Chocolate and peanut butter? An astronaut and an alien? A blog post and a troll? After they see each other, would they jump out of their carts and ride the roller coaster? Or would we show their life story from youth to old age?

We ultimately decided that our cast of characters should all be animals and the result of their initial encounter should be a date. At first we assigned circus jobs to all the animal characters. For example, the monkey was a clown, the bear was a trapeze artist, the frog was a sword swallower, and so on. But why would they be riding the Ferris Wheel? Shouldn’t they all be performing? And would people understand that the turtle was wearing a helmet and goggles because he was in the cannonball act? In the end, we simplified the characters and focused on making the animals as engaging, colorful and personable as possible without worrying about their day jobs.

Sketches for the animal characters.

Final animal character illustrations.

For the resulting dates, we used newspaper comic strips and their 3-panel composition as inspiration for style and narrative structure. The comic strip format gave us room to tell a wide variety of stories and the horizontal format worked nicely in our layout. Once we decided on comics, the date scenarios really just starting writing themselves. As always, we had more ideas than time to illustrate and animate.

The napkin sketch for the octopus and bear date.

The draft sketch.

The final comic.

We hope you enjoyed the final interactive doodle and perhaps learned a little bit about love, life and Ferris Wheels.


- Brian Kaas, Doodler

Location:


Canada,

Turkey,

Qatar,

Italy,

Czech Republic,

Kenya,

Indonesia,

Kuwait,

Hungary,

Lithuania,

France,

Congo [DRC],

Rwanda,

Slovakia,

Ireland,

Argentina,

Norway,

Nigeria,

Ecuador,

Macedonia [FYROM],

Ghana,

Brunei,

Australia,

Algeria,

Singapore,

Austria,

Slovenia,

Guatemala,

Germany,

Bosnia and Herzegovina,

Chile,

Puerto Rico,

Jordan,

Iraq,

Kazakhstan,

Poland,

Spain,

Ukraine,

India,

Netherlands,

Colombia,

Libya,

Greece,

Oman,

Tanzania,

Finland,

United States,

Philippines,

Serbia,

Vietnam,

Croatia,

South Korea,

China,

Thailand,

Switzerland,

New Zealand,

Russia,

Denmark,

Bulgaria,

Greenland,

Palestinian Territories,

Estonia,

Portugal,

Morocco,

Tunisia,

Hong Kong,

Mexico,

Lebanon,

Sweden,

South Africa,

United Kingdom,

Malaysia,

Senegal,

Latvia,

Mozambique,

Uganda,

United Arab Emirates,

Burundi,

Japan,

Taiwan,

Cyprus



Tags:

Horse,

Dolphin,

Monkey,

Fox,

Frog,

Romance,

Elevator Drop,

Stars,

Elephant,

Dating,

Bird,

Go-Cart,

Holiday,

Squirrel,

Chameleon,

Bear,

George Ferris,

Tiger,

Birthday,

Rabbit,

Animals,

Roller Coaster,

Carnival,

Night,

Octopus,

Interactive,

Turtle,

Love,

Carousel,

Circus,

Goose,

Amusement Park,

Ferris Wheel,

Hippopotamus

Puttu Pattu

Fabrice Bellard: Portrait of a super-productive programmer (2011)

Fabrice Bellard: Portrait of a super-productive programmer (2011):

Fabrice Bellard: Portrait of a Super-Productive Programmer

Posted by Cameron Laird on Mon, Mar 21, 2011 @ 03:28 AM

Hollywood portrayals of computing superstars are more rooted in comic-book super-heroics than the realities of software development. Except that in programming, superpowers do exist. Fabrice Bellard has them.
Computing in the movies is hard to recognize: Typographical errors are non-existent, crackers break through tested defenses in seconds, and practitioners create twenty-function-point programs in fewer keystrokes than the count of bullets whizzing by their heads. Hollywood portrayals are more rooted in comic-book superheroics than the realities of software development.
Except that in programming, superpowers do exist. Fabrice Bellard has them.

Serial achiever

What other description can there be when one man successively produces a dozen important and widely-used software applications? Look at the (partial) record:

• 1997: Publication of Bellard’s formula for computation of digits of pi

• 2000: Calculation of the largest-known prime. (Make sure you read this one—the source code is only 438 bytes long.)

• 2001: A self-compiling compiler of a subset of C that fits in 3 kilobytes of memory

• 2004: TinyCC Boot Loader

• 2005: DVB-T computer-hosted transmitter

• 2009: et world record for calculation of the digits of pi

Every one of these would be a proud accomplishment in any programming career. To produce so many, and so consistently, is very, very rare.
A bit of background provides the context to understand this record clearly. It’s common in programming folklore to talk about how a particular program was pulled together in one intense weekend, or during a vacation interval. Many of these tales are true, as far as they go; several of the best-known programs were first launched with a specific effort of just a few days. This leads some to expect that those few days define the life cycle of program development: A sufficiently clever programmer can create the Linux kernel this holiday season, take the next weekend off to invent the Ruby programming language, build an award-winning iPad game the following month, and so on.
It’s not so. Just because top sprinters finish a hundred meters in under ten seconds doesn’t mean they sustain that pace for the duration of a marathon. When Bellard wrote LZEXE, for example, he created a program that performed the data compression he needed at one particular time (it was the first widely-used executable file compressor for MS-DOS).
What’s notable is that he also invested the follow-up effort to ensure the software was engineered well-enough to work on other computers and on multiple operating systems, could be understood and maintained by others, was adequately documented, licensed to be useful, and so on. All those apparently secondary activities typically  take orders of magnitude more time than the original coding at the heart of a successful program.
Bellard isn’t unique as much for being a smart guy who has clever ideas about programs—although he certainly is and does—but for his achievement in refining and crafting those ideas into programs that make sense to others. He consistently creates applications that other programmers want to use and enhance.
Think about QEMU, for example. Like all Bellard’s best-known programs, it’s freely-available under the GNU Public License (GPL) or a close relative, originally developed under Linux, broadly portable, and now mostly maintained by others. Several programs preceded QEMU and roughly fit its description as “a generic and open source machine emulator and virtualizer;” QEMU, though, like many of Bellard’s creations, combines performance, robustness, portability, and flexibility in a way that none of its ancestors or rivals matched. Bellard’s contribution wasn’t to create the idea of a machine emulator, but to envision how to engineer one well enough to move it from the classroom or laboratory to “working-class” developers’ and testers’ toolboxes. It’s now indispensable to many testing teams, who can leverage QEMU to manage hundreds of distinct computing environments from a single underlying physical computer.

Finding a balance

Bellard seems to balance nicely between extremes that threaten productivity. His techniques are modern without being faddish, and careful, yet not neurotic. While he moves every few years into new and fertile unconquered territory, he exercises  patterns that have served him well over and over: cleanly-styled C, data compression, numerical methods, signal processing, pertinent abstractions, media formats, open-source licensing, and “by-hand parsing.”
Bellard doesn’t appear to promote himself—he politely declined to be interviewed for this profile, for example—but others enthusiastically adopt his creations. Among the 654 Copyright notices QEMU 0.13.0 source code embeds, 216 are his. To put that another way: He was successful enough with QEMU during its first few years to entice others to put in over twice as much work (by this crude measure) as he has!

Bellard, born in 1972, began practicing his own coding techniques first on a TI-59 scientific calculator, at the beginning of the ‘80s. Many of the projects listed above, along with others in his portfolio, originated as student assignments at l'École Polytechnique, where he matriculated in 1990. TinyGL, for example, derives from the VReng Virtual Reality Engine distributed 3D application he began in 1998. Based on this experience, he eventually created and released in 2002 TinyGL as a very fast, very compact re-implementation of a substantial subset of OpenGL.
Similarly, his recent and relatively well-publicized calculation of several trillion (!) digits of pi was performed on a single desktop computer. Previous record-setting calculations of this class were done on million-dollar supercomputers. Bellard made it seem natural to pull together his mathematical insight, broad experience at instruction-level coding, and careful engineering to advance the field this way. The roots of the achievement reflect back to his experiments on a hand-held programmable calculator at the age of nine .
To describe fully even one of the projects already mentioned is beyond the scope of an article such as this; it would take several books to capture all that Bellard has already contributed, and at least another to explain how he works. A few broad conclusions are possible, though:

• As has often been observed before, the very best programmers are far, far more productive than the average, able to produce multiples of the usable output of others;

• While it’s unrealistic to predict how programming would look without Fabrice Bellard or open-source licensing, there can be no doubt that such programs as QEMU, LZEXE, and FFmpeg are in pervasive use thousands of times each day around the world now; and

• If there’s a secret to this superhero-level productivity, it appears to have less to do with comic-book mutation and radioactivity, and far more with discipline, confidence, rigor, and many years of practice.

Mass media make it easy, especially in the United States, to believe that only “clashes of the Titans” matter. That is, the mindset is that progress with computers has to do with million-dollar budgets, celebrity announcements, and courtroom jousting. That’s a dangerously narrow view, dangerous because it neglects the creativity and insight of sufficiently dedicated individuals. While Fabrice Bellard seems unlikely ever to hire a publicist or otherwise elevate his profile in the public eye, he shapes our use of computers more indelibly than corporate executives and industry analysts.
How do you use FFmpeg or QEMU or his other productions?  Tell me about it in the comments.  Even more important: What great program will you write next?  What obstacles to superproductivity do you face?
See also:

• Top 5 Developer Skills That Will Get You Hired or Promoted
• What Wayland Means for Developers
• 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star

Siebel – Useful Business Services

BS NAME	METHOD	DESCRIPTION	WHERE TO USE
FS Holiday API Service	GetElapsedBusinessTime	Returns business time taken to accomplish task.	It is used when you want to work on some date or date related information
	GetResponseTime	Returns commited time based on service calander and exception calander
	IsHoliday	Returns TRUE or FALSE if given day is holiday and return next working day
Workflow Process Manager	RunProcess	Used to run a workflow	Used either explicitly or internally to run a workflow
SLM Save List Service	LoadPopupApplet	Used for displaying a pop applet at run time. Details-The Applet Used should have type standard and contain the class as  CSSSWEFrameListPopup. If you are facing any problem creating the applet then just copy the vanilla applet - FINS Service Request Order ID Popup Applet and then customize it according  to the requirement	To show a pop applet at run time
ISS Add Attachment Service	AddAttachment	AttachmentFieldName (Lit)( AccntFileName)BusinessComponent(Lit)( Account Attachment)BusinessObject(Lit)(Account)File(Lit)(Path of the attch)HeaderBusinessComponent(Lit)(Account)ObjectIdHere – Lit – means – Literal – OR – hard coded value.AttachmentFieldName – is the name of the field on which we want to add the attachment. In our case it is AccntFileNameBusinessComponent – Name of the Business Component to which the field belongs. In our case we have chosen - Account Attachment – as the Business Component.BusinessObject - Name of the Business Object to which the chosen Business Component belongs. In our case we have chosen - Account Attachment – as the Business Component. In this case Business Object is Account.Object Id – Row id of the record.All these are input arguements to the method and there is NO Output arguement from the method.	Used to add the attachment when required to any of the business component
SIS OM PMT Service	Set Profile Attribute	Used to set and get the Profile Attribute	Profile Attributes are used For Global purpose
	Get Profile Attribute
FINS Goto View Service	GotoView	Used to navigate to different view	When you want to navigate to different view
FINS Teller UI Navigation	RefreshCurrentApplet	Used to refresh the current applet	Used when we want to refresh the current applet without breaking the sequence
	GotoView	Used to go to a view you want	Nevigate to a view you want
FS Verify Entitlement	GetBestResponseTime	If you want to get the response time from entitlement matrix by passing  the priority and the entitlement id  and entitlement name as input but it will not take calendar into consideration. It will give calendar id as an output.	Used in service request to get the committed time based on the entitlement matrix. It is one of the block in the Vanila  workflow FS – Verify Entitlement SR.
Data Validation Manager	Validate	Used to Validate a rule set  present in Administration-Data Validation.This returns the result code and result message which means the message in the validation messages - associated with the rule set and can work by passing the rule set name only.It can be called from either from workflow or from the run time event	Scenario- In an insurance company, claim adjusters are required to enter a closed date whenever they close a claim. If the adjuster tries to close a claim without a closed date, an error message appears and the claim record is not committed to the database.
SiebelUserProfileService	GetProfileAttribute	Used to set the profile attribute and get the profile attribute	To set and get profile attribute