Testing Categorized Blog from Email 2

The category shortcode will match the start of category titles, as well as category IDs. For example:

Will match ‘Holiday’ and ‘Food’. Note that categories must already exist on your blog and spaces between the commas are not important.

CodeCharge Studio 4.1

Starting at only $139.95 (Personal Edition)

Visual Rapid Web Application Development and Web Reporting Tool.

Whether you’re developing data-driven interactive Web
sites or enterprise Internet and Intranet systems, CodeCharge Studio
provides the fastest way to build your applications with support for
virtually all databases, web servers and web technologies.
With new features like AJAX, Web Reporting, Flash Charts, Menu Builder,
Online Calendar and Gallery Builders, it’s now easy to harness the full
power of the Web.

We also offer a professional Web-based
Customer Support Suite created with CodeCharge Studio which you can
use in your business and as an example for your Web projects.

Features Visual IDE and Code Generator Rapidly build web applications by generating robust, scalable programming code in ASP.NET (C#), ASP, PHP, Java Servlets, JSP, ColdFusion and Perl. Database-to-Web Converter Convert any database into a Web application in just a few minutes. Web Reports, Calendars, Galleries, Charts, Ajax and more… Transform yourself into a Web guru by using our powerful development environment for quickly creating advanced Internet applications. Pre-built Solutions Customize and enhance any of the examples included with CodeCharge: Community Portal Online Store Task Management System Employee Directory Bug Tracker Forum / Message Board

Benefits Reduce Development Time Eliminate time-consuming programming tasks and build scalable, robust Web Applications in a fraction of the time. Minimize Errors Avoid costly programming errors and misspellings by generating consistent, well-structured code. Reduce Learning Curve Analyze and modify generated code to learn web technologies and take on programming projects in any environment. Sample Applications

CSS Fundamentals (Part 1)

There are three fundamental building blocks in any CSS files:

   1. Element.
   2. Class.
   3. ID.

Element
An Element is a reference to all of a particular HTML element in the website.

For example:

p
{
text-align: justify;
}

When this applied to website, the CSS formatting will apply to a justified alignment to all <p> tags in the HTML code.

If some paragraphs (<p>) should be center alligned, then we should use classes.

Class
with classes, one can set a class of an element to have different formatting than other classes of the same element.

p.centerAlign
{
text-align: center;
}

this will apply to paragraphs that use class centerAlign.

ID
ID is similar to classes in CSS in that it references a special case of an element. The main difference is that an ID can only be used ince at your HTML document code. For example, they can be used for headers or footers where there should be only one ID per page.

#centerAlign
{
text-align: center
}

DIV doesn’t contain all content in ASP.NET

I faced this problem when I created a DIV and contents inside such DIV increase. I found contents goes outside the DIV in the output. To solve this problem, simply apply this option to DIV:

overflow: auto

Done !!

Introduction

In this series of blogs, I’m summarizing the very powerful programming language Ruby. I’ve selected this language after I discovered that it’s powerful enough for many purposes, including web development, scripting and other general-purposes. So, Let’s discover it.

Using Helpers in Rails Applications

What is a helper

Helper is a module containing methods that assist a view. Helper methods are used to generate HTML, XML or Javascript. So, the helper extends the behavior of a template.

Each controller gets its own helper module. If the controller is named BlogController, then Rails will look for the helper BlogHelper in the file blog_helper.rb. However, this is generated automatically using the controller generation script.

ICONLook

ICONlook: icon search engine from Download Squad by Jay Hathaway When it comes to tracking down some icons for a project — nothing real fancy, and preferably under some kind of open license — image searching on Google doesn’t always do the trick. ICONLook is a search site that you can try instead: it’s specifically for icons, and it has some useful features that make it worth a peek if you’re in a pinch. These are generally OS-type icons, for stuff like apps, documents and search buttons, so don’t get your hopes up for anything too fanciful. Heck, we couldn’t even find anything as wild and crazy as a cat icon on ICONLook. Selection is not ICONLook’s strong point. Even within the categories it’s designed for, there’s not a lot of variety. On the plus side, many of the icons are available in a number of different sizes, and there are links to the source and the license for each one. This puts to rest any worries that this might be some kind of hack job, or the work of nefarious icon pirates. Instead, what you get is a legitimate, middle of the road selection of licensed icons that will hopefully expand to become more useful.

[How to] Merge branches in eclipse

1- Select Team – Merge

d
<!–[if gte vml 1]><v:shapetype
id=”_x0000_t75″ coordsize=”21600,21600″ o:spt=”75″ o:preferrelative=”t”
path=”m@4@5l@4@11@9@11@9@5xe” filled=”f” stroked=”f”>

<v:shape id=”_x0000_i1025″ type=”#_x0000_t75″ style=’width:414.75pt;
height:250.5pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image001.png”
o:title=”"/>
<![endif]–>

2- The merge wizard open as shown:

<!–[if gte vml 1]><v:shape id=”_x0000_i1026″
type=”#_x0000_t75″ style=’width:342.75pt;height:333pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image003.png”
o:title=”"/>
<![endif]–>

3- In the first field (Branch or
version to be merged (end tag)), select browse and select the latest tag for
the main trunk (in this case, dot16e_main_trunk_build_0001), then press OK.

<!–[if gte vml 1]><v:shape id=”_x0000_i1027″
type=”#_x0000_t75″ style=’width:337.5pt;height:243.75pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image005.png”
o:title=”"/>
<![endif]–>

4- For the second field, select
browse and choose the tag you have just made (the latest tag for your branch).

<!–[if gte vml 1]><v:shape id=”_x0000_i1028″
type=”#_x0000_t75″ style=’width:337.5pt;height:243.75pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image007.png”
o:title=”"/>
<![endif]–>

5- Now, you have selected the
start and end tags for the merge process

<!–[if gte vml 1]><v:shape id=”_x0000_i1029″
type=”#_x0000_t75″ style=’width:342.75pt;height:333pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image009.png”
o:title=”"/>
<![endif]–>

You now have two options as shown
in the above dialog

<!–[if gte vml 1]><v:shape id=”_x0000_i1030″
type=”#_x0000_t75″ style=’width:319.5pt;height:36pt’>
<v:imagedata src=”file:///C:\DOCUME~1\AHMEDA~1\LOCALS~1\Temp\msohtmlclip11\clip_image011.png”
o:title=”"/>
<![endif]–>

The first option lets you approve
changes that will be made to your branch while the second option performs merge
automatically and then you fix conflicts manually.

The First option is
recommended while merging to save the updates made to your local branch.

[Tech Note] How Does Rails Processes An Incoming Request?

In a Rails application, incoming requests are processed as follows:

1. Incoming request is sent to a router.
2. The request is divided into parts by the router (parsed) to identify a particular method (action) somewhere in the controller code.
1. The router takes the first part as a controller name
2. The router takes the second part as a method name (action).
   
3. The action might look at data in the request itself or interact with the model or may invoke another action. Eventually, the action prepares information for the view.
4. the view renders something to the user.
   

[TECH NOTE] Models, Views and Controllers (MVC) Architecture

In 1979, Trygve Reenskuage created a new architecture for developing interactive applications. In this architecture, applications are broken into three types of components:

1. Models.
2. Views.
3. Controllers

The Model
The model is respoinsible for maintaining the state of the application. However, it’s not just some data, it also contains the rules which enforce all the business rules that apply on that data.

Example
If a discount shouldn’t be applied on orders of less than $20, the model should contain and apply that constraint.

So, including all rules in the model ensure that nothing else in the application can make the data invalid. i.e. the model is acting as a gatekeeper and a data store.

The View
The view is responsible for generating the user interface based on data in the model.

Example
The online store has a list of products to be displayed on a catalog screen. This list will be accessible via the model. However, the view will access the data, format it to be displayed to the user.

It should be noted that the view doesn’t manipulate the incoming data, the view only works on displaying the data.

There may be many views that access the same model data for different purposes.

Example
In the online store, there will be a view that displayes product information on a catalog page and another views to add and edit products. Both views access the same data.

The Controller
The controller controls the overall application. Controllers receive events from the outside world, interact with the model and display the view to the user.