replace.intelliside.com | ||
ASP.NET Web PDF Document Viewer/Editor Control Library// A reference to Joe, Harry's number one Firefighter joe = new Firefighter { Name = "Joe" }; // Firefighter harry is really a firechief, with joe as his NumberOne FireChief harry = new FireChief { Name = "Harry", NumberOne = joe }; Firefighter harryAsAFirefighter = harry; // Harry is just a firefighter, so he can extinguish fires // but as a firechief he gets joe to do the work harry.ExtinguishFire(); // While as a firefighter he does it himself harryAsAFirefighter.ExtinguishFire(); The output we get now looks like this: random barcode generator excel, excel barcode generator open source, barcode add-in for excel free download, microsoft excel 2010 barcode add in, free download barcode font excel, barcode font for excel, barcode generator excel 2007 free, barcode font for excel 2013 free, how to get barcode in excel 2010, excel 2010 free barcode font,It s possible to combine several transformations by performing them in turn. When doing this, the ordering is important because all transformations are referring to the origin (0,0). For example, rotating always means rotating around the origin, so if you want to rotate a shape around a different point, you have to translate the center of rotation to (0,0), apply the rotation, and then translate the coordinate system back. Let s draw a rectangle at (0,0) that is, 70 pixels wide and -70 pixels high with the following line: painter.drawRect( 0, 0, 70, -70 ); Now rotate the coordinate system 45 degrees using the following line (the result is shown in Figure 7-22): painter.rotate( 45 ); Joe is putting out the fire! Harry is putting out the fire! By adding the ScriptManagerProxy control to the content page, you added the following code to the page; you can see this in the Source view: <asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <atlas:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server"> </atlas:ScriptManagerProxy> </asp:Content> Now you can simply add the scripts that you want to this page using the <Scripts> child tag in the same manner as you did with the ScriptManager control. Here s an example: <asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <atlas:ScriptManagerProxy ID="ScriptManagerProxy1" runat="server"> <Scripts> <atlas:ScriptReference ScriptName="AtlasUIDragDrop" /> </Scripts> </atlas:ScriptManagerProxy> </asp:Content> So now when you run the page, you will see that AtlasUIDragDrop has been included in this page: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> When we talk to our Harry object through a FireChief reference, he gets Joe to put out the fire. If we talk to the object through a Firefighter reference, he does it himself. Same object, but two completely different implementations. Why might we want to do that Let s say we had multiple fire chiefs on a job, but it is our policy that a chief acting as another chief s Number One is not allowed to delegate the job again. Our code models exactly this behavior, as shown in Example 4-7. Of course, whether that s desirable behavior is another matter entirely we ve ended up with such radically different approaches to putting out a fire that it might be better to separate them back out into functions with different names. When you go through a refactoring process such as this, it is a good idea to check that you re still happy with the semantic implications of your code. Ideally, you want to end up with a neat design, but a superficially neat design that makes no sense is not helpful. If you instead translate the coordinate system so that the center of the rectangle (35, -35) is the origin before rotating and then retranslating the coordinate system into place, you end up like Figure 7-23. The code for translating and rotating and then translating back is the following: painter.translate( 35, -35 ); painter.rotate( 45 ); painter.translate( -35, 35 ); // A reference to Joe, Harry's number one Firefighter joe = new Firefighter { Name = "Joe" }; // FireChief harry has joe as his NumberOne FireChief harry = new FireChief { Name = "Harry", NumberOne = joe }; FireChief tom = new FireChief { Name = "Tom", NumberOne = harry }; // Harry is just a firefighter, so he can extinguish fires // but as a firechief he gets joe to do the work harry.ExtinguishFire(); // But if Tom is asked to extinguish a fire, he asks Harry to do it // Our policy dictates that Harry has to do it himself, not delegate to // Joe this time. tom.ExtinguishFire(); Harry delegates to Joe when he is asked to do it himself, because we are calling through a reference to a FireChief. Tom is also a FireChief, and we are calling through a reference to him as a FireChief, so he delegates to Harry; but when Harry is asked to do it in his role as a Firefighter (remember, the NumberOne property is a reference to a Firefighter), he does it himself, because we are now calling the method through that reference typed to Firefighter. So our output looks like this: Joe is putting out the fire! Harry is putting out the fire! Figure 7-23. By translating back and forth, it is possible to rotate around the center of the rectangle. If you mix up the order of the translations, you end up with Figure 7-24 (you have rotated around the wrong point).
| ||