birt ean 13

birt ean 13

birt ean 13

birt ean 13

birt ean 13

birt ean 13,

birt ean 13,
birt ean 13,
birt ean 13,

birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,

birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,

birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,
birt ean 13,

The hangman application, shown in Figure 3-3, takes advantage of the GtkDrawingArea widget that you learned about in the previous chapter. The character, border, and current puzzle are drawn on the GtkDrawingArea widget. Next, a table of buttons, one for each of the alphabetic characters, is placed along the bottom of the window. Each button becomes insensitive when clicked.

11 12 13 14 15 16 17 18 19 20 21

In our master page, we want to display a common logon widget. If the user isn t logged in, it should display a Login link. Otherwise, it can display common information about the current user, such as username and email, as well as a link to the user s profile. But we don t want to put the burden on every action that might somehow render this master page to supply this extra information. The profile information might need to be pulled from a persistent store, such as a database or session, so we don t want to use a partial to do all of this. In listing 10.4, we use the Action method to render the LogOnWidget action of the AccountController. Action is similar to other action-based HtmlHelper extensions, such as ActionLink, but Action will render the results of that action inline. Because Action will create another request to ASP.NET MVC, we can encapsulate complex widgets into a normal MVC pattern. Authoring a child action is similar to other normal actions, as shown in listing 10.5.

Figure 13-3. A hangman game using GtkDrawingArea The important thing to remember about drawing areas is that you will want to connect the widget to the expose-event signal. Every time the user resizes the window, changes focus, or moves the window, the widget will be cleared. In the hangman application, the drawing area had to be reconstructed every time an expose-event occurred. Within this callback function, gdk_draw_lines() was used to draw the border around the window from a set of points. Next, gdk_draw_polygon() was used to draw the scaffolding from a set of points. Notice in the solution that the third parameter of this function is set to TRUE, which causes the polygon to be filled in with the color specified in the widget s style.

[ChildActionOnly] Ensures only callable public ViewResult LogOnWidget() via RenderAction { bool isAuthenticated = Request.IsAuthenticated; Profile profile = null;

Then, the current puzzle string is added to a PangoLayout, where any characters that are not yet discovered are set as the period character. The puzzle is aligned in the center of the border according to its width, since its size will vary depending on the current puzzle. The layout is drawn to the drawing area s GdkWindow with gdk_draw_layout(). Lastly, gdk_draw_line() and gdk_draw_polygon() are again used to draw the actual character, although what is drawn depends on how many wrong guesses the user has made. When a letter is clicked, the callback function loops through the current puzzle, revealing any of the characters that have been found. If no matches are found, another appendage is added to the hangman. If the state reaches 5, the user loses. If the whole solution was filled, then the user wins.

void openVault() { // Opens the vault } main() { if (checkPassword()) { openVault(); printf ("Vault opened!"); } }

if (isAuthenticated) { Looks up var username = HttpContext.User.Identity.Name; user profile profile = _profileRepository.Find(username); if (profile == null) { profile = new Profile(username); _profileRepository.Add(profile); } } Renders var model = new LogOnWidgetModel(isAuthenticated, profile); view return View(model);

In 6, you learned how to use GIOChannel to communicate with applications through pipes. A ping utility application is displayed in Figure 13-4; it allows the user to ping an address a specific number of times or continually until the application is stopped.

Although the logic behind rendering a logon widget is complex, we can encapsulate that complexity behind a normal controller action. In our child action, we check to see if the user is logged in C. If so, we pull up their profile using the IProfileRepository D. Finally, we render a strongly typed view by building up a LogOnWidgetModel