This work (my description and pictures of my contraption here) is in the Public Domain.  That means you can use it however you like – I’m sharing it!

What do you do with your physical photographs in the Facebook age?  It’s a real problem for me, because on the one hand I almost never look through the photo albums of physical photos sitting on my self.  Probably no more than once every six months or so, and usually then I spend no more than five minutes at it.

But on the other hand, I can hardly stand to throw them all out.  I’ve scanned all them, but still hate to just throw them all away.

So I decided to throw together a “photo holder” for the lid of my laptop, using duct tape and cardstock.  This way I can enjoy a photo for a week, swap it out for another at the end of the week, and feel comfortable about throwing it out because I’ve enjoyed it for a week.  It also creates a conversation topic, and spruces up my otherwise-plain laptop some.

This is a project you can do in about 5 minutes, for no cost if you have the materials lying around.

Here are the photos of the project:

This is all you need - duct tape, cardstock, scissors, and a photo

Cut triangles from the cardstock

Use the photograph itself to space the cardstock corners correctly, and tape the cardstock to the laptop

The photo slips in pretty easily. I gave my holder a tilt to make it more dynamic.

In case you were wondering, the photo in the laptop photo holder is of my friends and I goofing off after giving out free milk and cookies around Finals time at UC Davis when we were students there.

Let me know if you have other creative ways of using old photographs!

JavaScript ist eine funktionale Sprache, es gibt aber auch Objekte und eine Art Vererbung – die Programmiererin muss selbst darauf achten, gewisse Dinge einzuhalten oder sich entsprechende Hilfsfunktionen definieren oder noch besser, gleich ein geeignetes Framework einsetzen. Hier möchte ich auf die einfachste Vererbung in JavaScript eingehen – Frameworks kommen später

Im einfachsten Fall habe ich also eine Objektschablone Animal und eine davon erbende Objektschablone Dug.

function Animal(name, outputId) {
  /* public */
  this.Name = name;
  this.OutputNode = document.getElementById(outputId);
}
function Dug(name, outputId) {
...
}
Dug.prototype = new Animal();

Durch die außerhalb der Vorlage Dug angegebene Anweisung Dug.prototype = new Animal(); findet die Vererbung statt. Genauer gesagt erhält die Objektschablone Dug einen Link auf die Objektschablone Animal. Der Konstruktor, d.h. die Funktion Animal wird damit ausgeführt und Dug hat die öffentlichen Eigenschaften Name und OutputNode. Ich sehe in diesem Ansatz folgende Nachteile:

• Die Parameter name, outputId können nicht direkt an den Konstruktor der Superklasse Animal übergeben werden.
• Prinzipiell kann jede von außen die Schablone Dug oder Animal verändern. Dies kann auch für einzelne Instanzen erfolgen:
  • var donald = new Dug(); donald.Hello = function() {alert(‘Hello’);} //nur die Instanz donald kennt Hello
  • Dug.prototype.Fly = “Ich fliege”; //alle Instanzen von Dug haben nun die Eigenschaft Fly

Am zweiten Problem kann man nichts ändern, dies ist “by Design”, also so gewollt. Für das Konstruktorproblem gibt es zwei Ansätze:

1. Einführung einer öffentlichen Eigenschaft, die auf die Superklasse zeigt.
2. Verwendung von .constructor

Für beide Varianten, auch wenn Variante 1 vielleicht anderes suggeriert,  bleibt die Anweisung außerhalb der Objektschablonen
Dug.prototype = new Animal();  zur Definition der Vererbung notwendig.

Variante 1:

<pre>function Dug(name, outputId) {
  this.base = Animal; //Zeiger auf Definition Animal, base ist ein frei wählbarer Bezeichner
  this.base(name, outputId);
...

Ich muss also zweimal definieren, dass Animal meine Superklasse sein soll, hm.

Variante 2:

function Dug(name, outputId) {
  this.constructor(name, outputId);
...

Eigentlich ziemlich genau, was ich möchte, wenn auch nicht unbedingt intuitiv. ABER, wenn ich nun vergesse, mit Dug.prototype = new Animal(); die Vererbung zu deklarieren, dann wird nicht, wie ich es vermutet hätte, der Konstruktor von Object ausgeführt, sondern der tatsächliche Konstruktor, nämlich Dug. Man landet dann in einer Endlosschleife. Warum? Für jede Objektschablone, erzeugt JavaScript, per default, folgende Definition:

  Dug.prototype = new Object();
  Dug.prototype.constructor = Dug; //alle Instanzen von Dug haben nun die Eigenschaft .constructor = Dug!

Erst das Überschreiben von prototype überschreibt auch den Konstruktor entsprechend.

Fazit

Es gibt Vererbung in JavaScript. Wenn ich jedoch tatsächlich mehrere von einander erbender Objekte brauche, dann werde ich Hilfsfunktionen wie bei MooTools oder anderen implementieren, die mir die Fehlerwahrscheinlichkeit reduzieren. Zu MooTools gibt es eine gute Einführung von Peter Kröner. Es lohnt sich auch, den Quellcode von MooTools anzusehen!!!

Explicit keyword is used in c++ one parameter constructors generally to preserve the semantic meaning of the program.

Conside the example :

class object{

private:

int val;

public:

object (int value) { val = value;}

int read() const { return val;}

void write(int value) {val = value;}

};

Now if an object is created and then assigned a value like this:

object a ;

a = 2;

the compiler will not give the error and the code will run correctly. Semantically this is wrong because the types on the both side are different and hence default copy assignment constructor will not handle this. The code runs correctly because compiler inserts a temporary statement in between and instruction is executed as following:

object temp = 2;  this assignment is possible only in one parameter constructor case

object a ;

a = temp;

Now the default copy constructor can handle this statement because type is same on the both sides.

To remove this ambiguity , EXPLICIT keyword is added in the constructor declaration so that compiler will not change the type by itself and it will throw an error in this case telling about type mismatch.

explicit object(int value) { val = value;}

Reference: F1.com

Reference: f1.com

Reference: F1.com

Provisional Results blog live in a min – http://wp.me/pF7qv-dA

19 weeks until the F1 2010 session starts – 133 days that is

That concludes the 2009 season – Check back during the next few weeks for Analysis and reviews

WOW Jenson Swearing alert

If red bull had a Double diffuser at the start of the year where would we be now?????

Get in there webber Red Bull 1 – 2

Brawn 3 and 4

What a fight ohh

Webber purple S1

webber’s lead down to 0.7 to button

webber’s lead down to 1.3 to button

webber’s lead down to 2.2 to button

L47 Vett now 17secs ahead of Webb

Jenson closing on webber by half a sec a lap – gap down to 3 sec

webber’s lead down to 3.6 to button

fight possible between 4th, 5th, 6th

Vettel, Webber, Button is what the podium looks like atm

Vettel and Button pitted

Rosberg overtakes Kubica who spins fighting with Buemi

Rubens and Nick in and out, that was quick

Webber in and out of the pits – option tyres

Kubica in and out of the pits with option tyres

Rosberg in – First 2 stopper to switch to option tyres studying lap times now I think

brb before 2nd stops

Kob News: Understeer, using the front flap max 6th place is possible

Force India fighting

Speed Trap data:

Kov – 322

Rubens, Liu and Sut – 320

Fisi and Button – 317

Alonso pits – 8.2 sec puts option tyres on

Top 3 look set now to finish in them positions – Webber and button may pit on the same lap with Vettel has 1 more lap of fuel

3 wins in a row for Red Bull Japan Vet, Brazil Webber, That is looking likely

Kov, Fisi, Gro and Liuzzi in the pits

Sutil killing the bollard

Fisi to get drive though pen for speeding in the pit lane

Kob lovely stop now on the option tyres

Kimi just pitted lets see how he will take the option tyres

Fisi just pitted the only driver to have used the option tyres

All 2 stoppers now pitted 1 stoppers should pit soon

Jamie went to pit stop at the wrong pit (stopped at Red Bull not STR, easy mistake) then ran out of fuel in the next lap very slow on that lap

Lewis: Couldn’t stop the car, right rear breaks, failure maybe???

Red Bull 1 -2 now both of them in my FR team with Sutil and Buemi go go go !! lol

Button nearly lost it again

1 stoppers now mixing with the front runners – Kob for points???

Silly Jamie trying to stop in the Red Bull pit with problem stopped on the circuit now

Yellow flag S3 STR stopped – Turn 11

Lewis in the pit again – He is out NOOOOOOOOOOO first retirement  and he is in my Fantasy Racers team

McLaren clearing space in the pit lane

STR running slow

Lewis: Could have a right rear break problem

Webber in pits, also Truill, Buemi, Rosberg in

Hamilton and Button in the pits, all safe out of the tunnel into clear air

Ferrari not use tyres all the time because of a heat issue

Kubica and Rubens in and out of the pits staying on the prime (Medium) tyres

Button is lewis’ threat now

Red Bull 1 -2 is looking likely

Back Kob looking good for a chance of points

i will brb pit stops start in 2 laps time

2 stoppers need to be at least 1.5 sec every lap quicker than all the one stoppers otherwise they could lose position and get in traffic

Lewis lost .8 of a sec oops Now lewis has to run and overtake Vettel in the 2nd part of the race

Lewis is smashing everyone in S2 half a sec quicker

1 stoppers on good pace

Top 5 pace within 2 tenth of a sec

Lewis Radio: Vettel quicker, losing most time in S3 and a bit in S1

Lewis not doing enough, grip not there atm, also it’s tyre heat low atm

Lewis half a sec quicker than anyone thought S2

Jenson 6 sec back from the leader Lewis

Lewis needs to get the gap to Vettel to over 5 secs or he will lose the place after the pit stops

Soz about that had to set dad sat nav

Rubens has a damaged car – Confirmed

Remember the fastest lap from this race will be the lap record

Jenson jumped rubens

Kubica jumped Truill

Button Quick with lots of grip

Rubens may have lost downforce from the front wing

GRO in front of Alonso

Lewis not sprinting atm

Kubica to stop about lap 15/16

Truill and Kubica fighting

Webber and Rubens have touched

The lights are out

Fisi on the option tyres for the start

Parade Lap is go go go

I am listening to BBC during the race today not 5live, what is everyone else listening to?

The grid is clearing

Ready?

Track Temp 33 c
Air Temp: 31 c
Air speed: 3.9 mps

Is everybody set, I have blog, Live commenting and blog post Comments

If u have a question, comment, idea or if i miss something please put a comment on any of my posts

Not good for Brawn and Kubica on pit stops

YAY Ron Dennis back on the grid thats very nice to see

9 Minutes to go

Martin and DC in a 2 seater love it

Loving the tunnel

Luca on the grid lol if he was quicker maybe he would be in the car for this race

End of grid walk today loved it like normal under 15 minutes to do to lights out

JC – Look at him lol – He is quick at the Top Gear track tho

I like Mark Webber, Webber Lewis and Jenson for podium

Lewis Interview WOOP WOOP Best car on the grid today

Grid walk time with Martin and Eddie YAY

WOW I wish i was a racing driver now, I have missed my chance of f1 as u have to start karting at about 7/8

I think jake will do well

Jake racing yay

half a hour to lights out can’t wait

Ferrari – a very ruff year for them, big crash, few podiums not what they looking for

I am wearing my F1 t-shirt today, lets hope it gives jenson and lewis some luck for 2 brits on the podium

McLaren: I thought they would be mega this year, lots of charactor building i think this year for lewis

BMW – I was quoted saying last winter they were my tip for success this year race wins and a challenge for the championship

Fernando to Ferrari 2010

What a year for them

Renault Renault Renault

Here is the grid:

Lewis, Seb, Mark, Rubens, Jenson,

Alonso out in Q1 – love Quail features

Buemi is in one of my  Fantasy Racers teams so Go Go Buemi

maybe I would love for STR to get points today with Buemi

I am loving the BBC intro love that song, look at that pretty car (BGP 001)

Jenson Button – 2009 World Drivers Champion don’t forget

BBC Intro is go go go, Remember after the race the bbc do a race forum today it will not be on freeview just Sky red button, Online and Virgin media (i think). I will add live comments on the forum into this live blog

Who will crash into the tunnel on the pit lane exit first, if any?

Will Lewis run away in the first stint

From the fuel weights we see the top 10 2 stopping and the last 10 1 stopping with Renault stacking the car with fuel

Afternoon All, under 10 minutes until the BBC coverage starts!

The first day/night qualifying session proved a complete success on the dramatic new Yas Marina circuit in Abu Dhabi, where Lewis Hamilton’s pace in the McLaren surprised Red Bull duo Sebastian Vettel and Mark Webber. This trio seems to have a small but crucial advantage over the Brawn duo of Rubens Barrichello and Jenson Button.

For the record, the fuel weights were: Hamilton, 658.5 kg; Vettel 663, Webber 660, Barrichello 655, Button 657, Toyota’s Jarno Trulli 661, BMW Sauber’s Robert Kubica 654.5, BMW Sauber’s Nick Heidfeld 664, Williams’ Nico Rosberg 665 and Toro Rosso’s Sebastien Buemi 661.5.

McLaren
Lewis Hamilton, 1m 40.948s, P1
Heikki Kovalainen, 1m 40.983, P13, will start P18
Hamilton was delighted with the MP4-24, saying it felt the best it had all season. He used KERS for all it was worth, and said things just got better and better as he regained the advantage from the speedy Red Bull duo. Kovalainen’s chances were damned straight away in Q2; he had just set the first fast time when he suffered a gearbox failure. The unit required replacement, leaving him with a grid-place penalty that dropped him from 13th to 18th.

Red Bull
Sebastian Vettel, 1m 41.615s, P2
Mark Webber, 1m 41.726s, P3
Vettel admitted that he and Webber were surprised by Hamilton’s pace, especially when it transpired that he wasn’t that much lighter on fuel. Both felt they got the best from their RB5s and said the cars were working well. They also thought that McLaren’s KERS was particularly advantageous here.

Brawn GP
Rubens Barrichello, 1m 41.786s, P4
Jenson Button, 1m 41.892s, P5
Barrichello said he was happy with the way his car improved as the temperatures dropped for qualifying. Button was very quick all through practice and Q1 and Q2, but with a fuel load in Q3 he started to get serious vibrations which led to debilitating understeer.

Toyota
Jarno Trulli, 1m 41.897s, P6
Kamui Kobayashi, 40.777s, P12
Trulli felt he got things right in all of the sessions and was happy with sixth, especially as Button only marginally improved on his time. Kobayashi had hoped to make Q3 in his first fully dry Formula One qualifying. In the end he was philosophical to miss out by just a couple of tenths.

BMW Sauber
Robert Kubica, 1m 41.992s, P7
Nick Heidfeld, 1m 42.343s, P8
Kubica rued Friday’s loss of time after his second session engine failure and said that the lower track temperature in qualifying had a deleterious affect on his F1.09’s handling. Heidfeld was quite happy on the greater fuel load and said that his marginal chance of a final improvement might have been frustrated when he came across Webber late in the lap.

Williams
Nico Rosberg, 1m 42.583s, P9
Kazuki Nakajima, 1m 41.148s, P14, will start P13
Rosberg made the top 10 again in his final race for Williams, and felt that ninth was the best he could have expected as his FW31 struggled on the open sections of the circuit. Nakajima didn’t manage to get his last lap together in Q2.

Toro Rosso
Sebastien Buemi, 1m 42.583s, P10
Jaime Alguersuari, 1m 41.689s, P15, will start P14
Buemi admitted that he had hoped for better than 10th after shining all through practice, but said he was happy overall given his fuel load. Alguersuari lost valuable track time when he didn’t run at all in the morning, for reasons the team didn’t divulge, and never managed to catch up.

Ferrari
Kimi Raikkonen, 1m 40.726s, P11
Giancarlo Fisichella, 1m 42.184s, P20
Once again Raikkoinen got the most out of the ageing F60, and Fisichella didn’t, and prospects for regaining third place in the constructors’ championship from McLaren appear weak.

Renault
Fernando Alonso, 1m 41.667, P16, will start P15
Romain Grosjean, 1m 41.950s, P19
Renault struggled throughout practice and qualifying here, and 16th and 19th indicated the depth of the problem.

Force India
Vitantonio Liuzzi 1m 41.701s, P17, will start P16
Adrian Sutil, 1m 41.863s, P18, will start P17
Liuzzi was really happy with his VJM02 on his first run in Q1 and believed he had the pace to get through to Q2. But the second set of soft tyres changed its behaviour for the worst as it lost grip. Sutil also complained of oversteer.

Reference: F1.com

Lewis Hamilton looks in superb shape to take a third victory of the season at the Formula 1 finale in Abu Dhabi on Sunday.

The McLaren driver was on pole by a margin of nearly 0.7 seconds and he was still half a second clear when the amount of fuel in the cars was taken into account – an astonishing margin in a season that has been so close.

The cars in the top 10 qualifying shoot-out are not allowed to refuel between qualifying and the race, so the amount of fuel they carry dictates their pace on Saturday as well as when they will make their first pit stops on Sunday.

So grid positions can be misleading until the fuel weights are published and the ramifications of that calculated. Assessing those figures underlines just how strong Hamilton is looking.

This is BBC Sport’s fuel-adjusted Abu Dhabi Grand Prix grid, with projected first pit stops:

1 Lewis Hamilton (lap 17)
2 Sebastian Vettel +0.496secs (lap 19)
3 Mark Webber +0.721 (lap 18)
4 Jarno Trulli +0.854 (lap 18)
5 Rubens Barrichello +0.971 (lap 16)
6 Jenson Button +1.001 (lap 17)
7 Nick Heidfeld +1.186 (lap 19)
8 Robert Kubica +1.196 (lap 15)
9 Nico Rosberg +1.388 (lap 19)
10 Sebastien Buemi +1.651 (lap 18)

Because he has two laps’ less fuel on board, Hamilton’s fuel-adjusted margin over the Red Bulls is not as large as it was on the track but at nearly half a second it is still more than big enough for the race to look like it is his for the taking.

It seems as if the Abu Dhabi track could have been made for the McLaren.

There are two long straights for them to get the most out of their Kers power-boost system, which gives them an extra 80bhp for 6.7 seconds a lap.

And the track abounds in the slow- and medium-speed corners in which the car is so strong, while lacking the high-speed bends in which it struggles – and in which the Red Bull is the class of the field.

Not only that, but it should ensure he is unpassable on the first lap, so he should be able to lap at his own pace for the first stint.

If Hamilton has any rivals for victory, it looks like being the Red Bull drivers.

They are making their first pit stops a little later than Hamilton – Vettel on lap 19, compared to Hamilton’s 17, and Webber on 18 – but, as long as the Englishman maintain his superior speed into the first stint of the race, it is hard to see Vettel or Webber being able to make up enough time to leapfrog him.

More likely is that the Red Bull drivers will be engaged in a tight battle with the Brawn drivers and Jarno Trulli’s Toyota behind Hamilton.

With regards to Vettel and Brawn’s Rubens Barrichello, that means a fight for second place in the championship as well as in the race – the German has a two-point advantage heading into the grand prix.

But just as they are fighting for the crumbs left by Jenson Button in the championship, they look certain to be doing the same behind Hamilton in the final race of the season.

Reference: BBC Sport F1

Lewis Hamilton will stop just one lap earlier than main rival Sebastian Vettel in tomorrow’s race, making the Briton’s excellent pole position lap in qualifying this evening even more impressive. The 2008 champion went two thirds of a second quicker than second-placed Vettel, but the publication of the post-qualifying fuel weights revealed that the pair would stop just one lap apart on laps 18 and 19 respectively, hitting Red Bull’s victory hopes in the process.

With Vettel going just one lap longer than Hamilton, the German’s chances of leapfrogging the McLaren driver during the pitstops are now very slim, especially with Hamilton having KERS at his disposal to easily re-pass Vettel should he be behind. Webber is equally disadvantaged, stopping on lap 18, the same lap as Hamilton.

Behind the leading trio, Brawn’s Barrichello and Button will stop on laps 17 and 18, or possible earlier, with Jarno Trulli set to pit for the first time on lap 19. BMW Sauber’s Robert Kubica has the lightest car on the grid with just 16 laps of fuel on-board, with Heidfeld, Rosberg and Buemi all stopping in or around lap 20.

While all the top-ten runners are geared up for two-stop strategies, the entire latter half of the grid have the option of stopping just once, depending on tyre wear. Both Ferraris are the lightest cars in the bottom 10 with 30 laps of fuel, while the heaviest are the Renaults, with Alonso and Grosjean set to go 36 and 37 laps respectively before stopping.

Reference: Manipe F1

Warning, major n00bness ahead.

I’m not a big user of C++, but recently some work I have had to do with .NET has made me use C++/CLI, the .NET version of C++.

The API I work have a well defined and consistent Alloc/Use/Free cycle. This has gave me an incentive to learn to use RAII (via DrMax) to elegantly wrap the required cleanup operation in my code.

The following class around Windows GlobalAlloc is an example of such a wrapper.

    // RAII friendly wrapper over Win32 GlobalAlloc.
    class Memory
    {
    private:
        bool m_isAlloc;

    public:
        HGLOBAL Ptr;
        SIZE_T Size;

        void Alloc(UINT flags, size_t dwBytes)
        {
            if (IsAlloc()) Free();
            Size = dwBytes;
            Ptr = GlobalAlloc(flags, dwBytes);
            if (Ptr == 0)
                throw gcnew OutOfMemoryException();
            m_isAlloc = 1;
        }

        void Free()
        {
            if (Ptr) GlobalFree(Ptr);
            m_isAlloc = 0;
            Size = 0;
            Ptr = 0;
        }

        bool IsAlloc()
        {
            return m_isAlloc;
        }

        Memory(UINT flags, size_t dwBytes)
        {
            Alloc(flags, dwBytes);
        }

        Memory()
        {
            Ptr = 0;
        }

        ~Memory()
        {
            if (Ptr) GlobalFree(Ptr);
        }
    };

Expert eyes will obviously see that this code lacks 2 important things:

• there is no copy constructor
• there is no assignment operator

I’m not very experienced in C++ so I don’t the reflexes that make C++ programmers write those things when the define a class, and I don’t yet know when the implicit copy constructor and assignment operator are called. I’ve found that the easiest way to discover that is to to prevent them from being usable by the clients of the class. In the case of my small class above, I needed to make 2 functions private.

class Memory {
...
private:
    Memory& operator=(const Memory& mem);
    Memory(const Memory& mem);
...

This makes the compiler freak out when compiling my program…

...Memory::operator =' : cannot access private member declared in class 'Memory'...

The compiler has helpfully pointed to me out which place in my code those functions needs to be called.

Oops, so I really need that assignment operator after all.

This Saturday we went to see the progress in Tourteron. Although we were kept informed by Stepháne on a regular basis, we were not sure what to expect. In the end, even the three-and-a-half-hour drive does make us feel a bit helpless. It’s the same with any construction project: being there at least speeds the workmen.

Sanding Mess

When we arrived, the whole place was barricaded with hardboard. All the windows were closed and covered with black plastic. The larger ones were even covered with wooden panels. We couldn’t enter the house by the front door. We had to take the second door uphill. Entering bedroom 3, we stepped into one big, dirty cloud of grey dust. It instantly grabbed our throats. What happened here? Throughout the house the floor was covered with a 5 cm-thick layer of black crystal sand. OK, they have been sanding the wood. In the bare light coming through some holes in the roof and windows we could see the result. All of the wooden beams had become this beautiful light-brown, rough oak colour. Fantastic!
The second fantastic thing that happened was this: the water meter had been moved from the inside of the house to the outside. As strange as it sounds, the meter was originally installed in the middle of bedroom 3. That can be quite unhandy when you need to check something while people are renting. So Monsieur de l’Eau Official came, dug a hole, and placed the meter outside of the house. This resulted in a completely hidden water system. I love it!
The third thing I love about this update is the letters from the officials. The first letter  came from S.P.A.N.C.; it’s the official note telling us we have to wait another two weeks before we’ll know if we can install the new 4000-liter eco-friendly septic tank where we want it. Why does that make me happy? Because it means they have at least approved it! There’s another bureau involved who’ll have a final say, but this is a good start.
The second letter has not arrived yet. Why does that make me happy? It means we have to wait one more week. No news here means the complete building permit has been approved and we can start on the roofs and windows in one week.

Our plan is to open for rental guests the third week of March. Saturday March 20 will be the first time somebody can rent the first Super Gîte. That’s right before the Easter holidays.

In the next weeks we’ll have a reservation module online at the official supergites.com site, but any early birds who really can’t wait should contact us here: marco AT artmiks . nl . Because we would appreciate the risk you’d take by making a reservation on a project that isn’t even finished, we’ll have a very nice proposal waiting for you.

And you probably wonder what rent costs at the mill. A full week’s stay–Saturday 14.00 hours to Saturday 10.00 hours–will be 1200 euro in high season and 800 euro in low season. This includes double fireplace, four bedrooms each with its own bathroom, a 90-square meter living room, designer kitchen, and a warm welcome. It does not include electricity, wood for the fireplace, or cleaning. So, who’ll be our first guests?

Related articles by Zemanta

• What Does Septic Mean? (healthhype.com)

CATEGORII DE CURATENIE :

1. CURATENIE  DUPA CONTRUCTOR
2. CURATENIE  INDUSTRIALA
3. CURATENIE  EXTERIOARA SI/ SAU INTERIOARA
4. CURATARE  COVOARE, MOCHETE
5. TRATAMENTE  MARMURA, GRESIE, GRANIT,LINOLEUM,PARCHET
6. RECONDITIONARI

cateva detalii:

• Curatenie dupa constructor

curatare resturi si strangerea molozului

curatare mecanizata, spalare, lustruire a suprafetelor dure si a parchetului

spalare interior-exterior geamuri accesibile ,pervazuri,tocarie

spalare si dezinfectare gresie, faianta, grupuri sanitare, igienizari

curatare interioara a lifturilor

curatarea caloriferelor,prizelor, plintelor si balustradelor

evacuarea gunoiului si a resturilor in locuri amenajte si indicate de beneficiar

• curatarea interioara

aspirare si spalare pardoseli

spalare gresie,faianta,oglinzi,grupuri sanitare

stergerea prafului

stergerea exterioara a obiectelor electrocasnice

curatare vitralii, balustrade,usi,tocuri,intrerupatoare,tablouri,lustre etc

tratarea mobilierului si echipamentelor de birou cu solutie antistatica

curatare, lustruire parchet cu solutii special adaptate tipului de parchet

curatare,lustruire mozaic, marmura

aerisire si odorizare incaperi

degajarea gunoiului menajer

• curatenia industriala

aceasta se efectueaza in special in hale industriale unde este necesar a fi curatate de praf si pete tavane, grinzi, tubulaturi de aerisire, corpuri de iluminat, pardoseli sipereti

• tratamente marmura ,gresie, granit, linoleum, parchet

se folosesc metode de intretinere si curatenie adaptate tipului de pardoseala si folosind solutii dedicate acestora

lucrari curente:

spalarea si lustruirea pardoselilor rezistente la apa

decaparea ,ceruirea si lustruirea pardoselilor

curatarea mecanizata si tratarea cu polish acrylic a pardoselilor neporoase din PVC ,gresie neglazurata, marmura, linoleum, granit

• reconditionari suprafete deteriorate ale marmurei, granitului, parchetului, gresiei
• curatarea covoarelor si mochetelor

curatare de ultima tehnologie cu spuma uscata

produse ecologice

produse ce permit uscarea rapida a tesaturii si care preintampina aparitia mirosuriloe neplacute

• curatenie exterioara

curatare si intretinere parcuri, alei, parcari

curatare si intretinere spatii verzi

taierea gardului viu, a gazonului, a crengilor arbustilor si copacilor

deszapezirile aleilor si parcarilor in timpul iernii

evacuarea gunoiului aflat in cosurile de gunoi

ingrijirea plantelor naturale de interior si exterior

Detalierea mai sus efectuata nu are pretentia de a fi una completa; de aceea, daca aveti nevoie de unele servicii pe care nu le regasiti mai sus, nu ezitati sa intrebati. Cu siguranta vom avea capacitatea si competenta de a va satisface  solicitarile.

De asemenea,  oferim

• servicii de inchiriere personal pentru curatenie sau prestari servicii cum sunt: ajutor pentru petreceri, evenimente etc.
• servicii menajere cum ar fi : calcat rufe, efectuarea de cumparaturi in baza listei clientului , plata facturilor la utilitatile lunare

En The Kneeslider hay un post de  conversiones off-road sobre HD. Una vez más se confirma que hay gente “pa to”, Christian Dubreucq, jefe de Kilometre 66, es el autor de ésta. Una Sportster 1200 anda sobre los 230 kg., la Sportrack LB 12 anuncia 160 kg. en seco. Me gusta más el resultado de la transformación a SM de la Africa Twin.

Más info akí.

Someone mentioned to me that they couldn’t use PHP5-style object constructors when using the WP Widget API. I looked into it, and it turns out it does work. Example:

class My_Widget extends WP_Widget {
	function __construct() {
		$widget_ops = array( 'classname' => 'css-class', 'description' => 'Description' );
		parent::__construct( 'css-class', 'Title', $widget_ops );
	}
	// Rest of your widget subclass goes here
}

The key is using parent::__construct() instead of $this->WP_Widget().

When we arrived at the crime scene it was close to 10 a.m. We expected someone to be there, but the house was locked. We headed back to the car to pick up the keys and to grab our phone. “Why is nobody here?” we wondered. The builders should have been there working–they promised to start at 8:00. But there were no sounds of drilling or hammering; the property was deserted.

After Sara opened the door we were confronted with a scene of delict. Next to the stairs there was a broken cup, a splash of coffee, a smudge of blood, a trace of driblets, and a Stanley knife. Grissom said, “This can’t be right. Something’s missing.” We looked around and followed a small trail of blood to the locked front door. “The victim is still alive,” Grissom observed. He continued with his findings. “There must have been two people, as the door is locked without any smudging of blood. But where did the blood on the floor come from? Did the victim cut himself or was he attacked?” The Stanley knife did not look as if it had just been used–the blade was pulled back. I picked it up. “No blood on the knife,” I announced.

Grissom went up the stairs to investigate the situation. I followed him admiringly. “What if someone fell down, losing his mug, and fell onto something sharp like…?” I went over the movements. “Like a shard of mug?” “We only follow the facts!” Grissom said with certainty. “Assumptions have many shapes, reality only one.” Smart guy. I bucked up.

We needed to find Stephane or Jamal, his assistant. Either one should know what had happened. We walked up the hill to Stephane’s house and we ran into Arthur, a fairy-blond boy with deep blue eyes–the 7-year-old son of Stephane. I gave him my regular greeting, “Bonjour Arthur, çava?” “Bien merci,” came his weary reply. “Ou est ton papa?” I asked him. “Au l’hopital.” He answered without a wink and continued his play.

There are moments you just wish you could speak all languages of the world. D’accord. Stephane is at the hospital. Not good. The blood must be his.

To make a long story short, Stephane did fall off the stairs and cut his hand deeply. Jamal took him to the hospital in Reims where he had to stay for two days. He needed surgery since he’d cut himself quite deeply and hit a tendon. He can’t use his right hand for some time: the delay will be at least three weeks.

No High Fives for Stephane.

“Oh well, we need to wait for the building permit anyway.”

This work (my description and pictures of my contraption here) is in the Public Domain.  That means you can use it however you like – I’m sharing it!

In one of Aesop’s fables, a fox tries to jump for some grapes he’d like to eat.  After realizing they’re too high for him to reach, he gives up and walks away, muttering that they were probably sour anyway.

What he should have done, of course, was get me on the job!  Because I was faced with a similar problem last year in the form of some tantalizing coconuts about 15 feet out of reach. And you had better believe I didn’t walk away frustrated.

At hand were some construction materials – a long piece of bamboo, a long 2×4, some bricks, a wire, a shipping pallet, plenty of sand, a tire, and a hammer.  How would you use these to get the coconuts down?

First my family and I tried using the bamboo pole and the 2×4 (both of which were long enough to reach the coconuts) to knock them off.  The 2×4 was far too heavy to be wielded easily, though, and the bamboo wasn’t strong enough to knock the coconuts off.  We decided throwing bricks probably wouldn’t work, and wasn’t advisable considering that there were buildings around.

Finally I had an idea.  I made a loop of wire around the end of the bamboo pole, then maneuvered the loop around one of the coconuts.  Once it was over the top of the coconut, I could pull on the stem of the coconut, and the wire would tighten around it.  I tugged down, which yanked the coconut off.  Voila!  We had our fill of coconuts that day.  Can you think of other ways to get the coconuts down given the materials at hand?

This got me thinking about how to create a fruit picker that I could use in future years.  Y’see, my family comes to Hawaii every year, and we always pick lots of local fruit – mangoes, coconuts, breadfruit, papayas, passion fruit, guavas, etc.  There are usually many tasty-looking fruit far out of reach.  I didn’t think I could count on finding a long piece of bamboo near every fruit tree that caught my eye, and knew we couldn’t fit anything nearly that long in our car.  What to do?

My first thought was to buy some pipes and pipe fittings so I could screw together a long pole.  That way I could fit it in my suitcase, and reassemble it whenever I wanted.  That seemed like a decent solution, except that I didn’t really want to spend more than about $15, or more than 30 minutes, making my solution.  Was there a cheaper way to do this?

I realized, finally, that a pole like the bamboo pole we initially found (or like the screw-together pole I envisioned) actually has two important properties which needn’t be part of the same object.  The first property is rigidity – something rigid to get the loop of wire up to the desired fruit.  The second property is tensile strength – the ability to pull down on the fruit.  A pole has both, but there are other possibilities.

I realized that a tent-pole is collapsible, lightweight, and easily provides the necessary rigidity.  And a rope is lightweight, and provides the necessary tensile strength.  I could tie a loop of wire to the end of a tent pole, and tie a rope to the loop of wire.  I could lift the loop with the tent pole, then pull on the fruit with the rope!

Upon searching my tent bag, I realized all my tent-poles were 4-way tent-poles, not single tent poles, so they wouldn’t work.  I ended up using PVC pipe segments instead.  (I drilled a hole in the end of one pipe segment for the wire to loop through.)

Then it was easy to loop together a wire and rope to pull down all the fruit I could handle!

Me with PVC

I used 2-foot lengths of 1/2-inch PVC pipe

1/2-inch couplings hold the pipes together, but it’s just a friction fit, which is why the PVC doesn’t provide the necessary tensile strength.

The pole is made up of 6 segments (12 feet total), so combined with my height and reach, I can reach almost to 20 feet off the ground!

The pole bundles down to a pretty small size.

Since I already own rope and wire, the whole project cost me $6.50. If I had had a suitable tent pole, it would have been free.

Here's the loop of wire with the rope tied to it.

This jackfruit is no match for my harvester!

Here I'm getting a breadfruit down. I've already positioned the loop of wire, and I'm pulling on the rope. This breadfruit was attached firmly enough that I had to drop the pole (letting it hang) and pull the rope with both hands.

Well, back to JAVA

Hmm, so an Initialization Block – the name itself suggests that it has something related to initialization – of what? Of Objects.

Of Objects because whenever we create an object in Java using “new” keyword the constructor is called and basically constructor is meant for initialization of instance(member)(Object) variables.

Let’s take a look at a very simple example

class Parent

{

static { System.out.println(“Parent static 1″);}    //#1

{ System.out.println(“Parent Instance Block 1″);}          //#2

static { System.out.println(“Parent static 2″);}

{ System.out.println(“Parent Instance Block 2″);}

Parent()

{

System.out.println(“Parent constructor”);

}

}

class InitializationBlocks

{

public static void main(String args[])

{

Parent p1=new Parent();

}

}

Now look above we have some blocks of code…

Some are marked static and some are simply lying with no keyword attached to them…

The one marked static (see comment #1) are Static Initialization Blocks, they are loaded

when the class is loaded. Well, you can use them to initialize your static variables. Nice na?

And the one marked …marked? Have I marked them? (Oh c’mon see comment #2) those are Instance Initialization Blocks, they are basically called when you create objects of your class. Suppose if you want a similar work to be done for all the objects then you can put it in Instance IB.. Just Try It..!!

Static IB will be called only once when the class is loaded and Instance IB will be called every time when you create an object of your class.

And finally Constructor will be called.

Hey why don’t you look at the output of the above program?

Parent static 1

Parent static 2

Parent Instance Block 1

Parent Instance Block 2

Parent constructor

Now what if we have an inheritance tree…

In that case …do you know how the constructors are called in case if you have an inheritance tree??

grandparent, parent and then child…m I rite?

So just remember this sequence…

First grandparent will be loaded then parent and then child will be loaded ….so

Static IB will run…

Then Instance IB of grandparent followed by constructor of grandparent

Next Instance IB of parent followed by constructor of parent

Finally, Instance IB of child then constructor of child

Here is the code..

Have a look..

//Initialization Blocks

class GrandParent

{

GrandParent()

{

System.out.println(“GrandParent constructor”);

}

static { System.out.println(“GrandParent static 1″);}

{ System.out.println(“GrandParent Instance Block 1″);}

static { System.out.println(“GrandParent static 2″);}

{ System.out.println(“GrandParent Instance Block 1″);}

}

class Parent extends GrandParent

{

Parent()

{

System.out.println(“Parent constructor”);

}

static { System.out.println(“Parent static 1″);}

{ System.out.println(“Parent Instance Block 1″);}

static { System.out.println(“Parent static 2″);}

{ System.out.println(“Parent Instance Block 2″);}

}

class Child extends Parent

{

Child()

{

System.out.println(“Child constructor”);

}

static { System.out.println(“Child static 1″);}

{ System.out.println(“Child Instance Block 1″);}

static { System.out.println(“Child static 1″);}

{ System.out.println(“Child Instance Block 2″);}

}

class InitializationBlocks

{

public static void main(String args[])

{

Child c1=new Child();

}

}

Ok so what will be the output its simple right?

Isn’t it?

If you have understood this topic then you can put the output in comment…please do this

favour so that I can save my keystrokes….lol

Regards,

Faraah Dabhoiwala.

ဟိုေန႔က ကြၽန္ေတာ္တို႔ Instant constructor အေၾကာင္းသိခဲ႔ျပီးျပီ။ Constructor လို႔ဆိုလိုက္တာနဲ႔ programmer ေတာ္ေတာ္မ်ားမ်ား ေျပးျမင္မီၾကတာလည္း ဒီ Instant Constructor ပါပဲ။ အသံုးအမ်ားဆံုးနဲ႔ မသံုးမျဖစ္ Constructor လည္းျဖစ္ပါတယ္။ Instant Constructor အျပင္ တျခား လူသိနည္းတဲ႔ constructor ၂ ခုရွိပါေသးတယ္။ အဲ့ဒါေတြကေတာ့ Private Constructor နဲ႔ Static Constructor တို႔ပါပဲ။ Instant Constructor ကို public constructor လိုလဲ ေခၚပါေသးတယ္။ constructor ရဲ႕ ေရွ႕မွာ public keyword ကိုေရးေပးရပါတယ္။ ဘာလို႔လဲ ဆိုေတာ့ class ကို object ေဆာက္ဖို႔အတြက္ တျခား class ေတြ ထဲမွာ ေခၚသံုးလို႔ ရေအာင္ပါ။ private လို႔ေရးလိုက္လို႔ရွိရင္ေတာ့ အဲ့ဒီ private constructor ပါတဲ႔ class ကို object ေဆာက္လုိ႔ မရေတာ့ပါဘူး။ ဒါေၾကာင့္ object မေဆာက္ေစခ်င္တဲ႔ class ေတြမွာ private constructor ကိုေရးေပးေလ့ရွိပါတယ္။ ဥပမာ…

using System;
class Constant
{
    private Constant()
    {}
    public static string DeveloperName = "Sevenlamp";
}
class Program
{
    static void Main()
    {
    //Constant c = new Constant(); // error
        Console.WriteLine(Constant.DeveloperName);
        Console.Read();
    }
}

ဒီ program ေလးမွာ private constructor ေၾကျငာထားလို႔ Constant class ကို object ေဆာက္လို႔ မရပါဘူး။ ဒါဆိုရင္ အဲ့ဒီ class ထဲမွာ ရွိတဲ႔ member data ေတြကို ဘယ္လို ျပန္ေခၚသံုးမလဲ။ ဟုတ္ကဲ႔ ကြၽန္ေတာ္တို႔ private constructor ရွိတဲ႔ class ေတြထဲက member ေတြကို ျပန္သံုးလို႔ ရေအာင္ အဲ့ဒီ member ေတြကို static keyword နဲ႔ တြဲ႔ျပီး ေၾကျငာေပးရပါမယ္။ ဟုတ္ျပီ အဲ့ဒီ variable ေတြကို static variable တနည္းအားျဖင့္ class variable လို႔ေခၚပါတယ္။ အဲ့ဒီ class variable ေတြကို ေခၚဖို႔အတြက္ သူရွိေနတဲ႔ class ကုိ object ေဆာက္စရာ မလိုပါဘူး။ program မွာ ေခၚထားသလို class name ကေနတဆင့္ ေခၚသံုးလို႔ ရပါတယ္။ ေနာက္ constructor တစ္မ်ိဳးကေတာ့ static constructor ပါ။ class တစ္ခုအတြင္းမွာ ရွိတဲ႔ static member ေတြအလုပ္မလုပ္ခင္ အရင္ဆံုး static constructor က အလုပ္လုပ္ေလ့ရွိပါတယ္။ ခုန program ေလးကိုပဲ static constructor ေလးထည့္ျပီး ျပန္ run ၾကည့္ရေအာင္။

using System;
class Constant
{
    private Constant()
    {}
    static Constant()
    {
        Console.WriteLine("print from static constructor");
        DeveloperName = "Sevenlamp";
    }
    public static string DeveloperName;
}
class Program
{
    static void Main()
    {
        Console.WriteLine(Constant.DeveloperName);
        Console.WriteLine(Constant.DeveloperName);
        Console.Read();
    }
}

Program run လိုက္ရင္ “Sevenlamp” ဆိုတဲ႔ စာသားကို မရိုက္ျပခင္မွာ “print from static constructor” ဆိုတဲ႔ စာသားကိုအရင္ ရိုက္သြားတာ ေတြ႔ရမွာပါ။ ဒါေပမယ့္ တစ္ခုသိထားရမွာက static constructor က static member ေတြကို မေခၚခင္ ပထမဆံုး တစ္ၾကိမ္ပဲ အလုပ္လုပ္ပါတယ္။ ဒါေၾကာင့္ ကြၽန္ေတာ္က developername ကို ၂ ၾကိမ္ရိုက္ျပထားေပမယ့္  “print from static constructor” ကေတာ့ တစ္ၾကိမ္ပဲ ေပၚလာမွာျဖစ္ပါတယ္။ ကဲ ဒီေလာက္ဆို ကြၽန္ေတာ္တို႔ constructor ေတြ အေၾကာင္း နည္းနည္းနားလည္လာျပီ ထင္ပါတယ္။

ေနာက္ပိုဒ့္မွာ static member နဲ႔ instant member အေၾကာင္း ဆက္ေျပာပါ့မယ္။