Category: Java Based Projects

Magic Bouncing Ball

For the Game the displaying window is Frame. The Frame is window is imported from java.awt.Frame API. Some of the important methods in Frame class are setVisible and setSize without these two methods frame won’t be visible and the size will not be defined. The other methods used are setLocationRelativeTo(null) and     setResizable(false). The method setLocationRelativeTo(null) is used to display the frame in the center of the display screen. And the method setResizable(false) Will ensure the frame size is fixed you cannot minimize or maximize it. The background color of the frame is black.

Drawing the Ball:

We will be using paint method to draw a ball. The initial x and y co-ordinates are 0, 0. The diameter is 40, 40.

publicvoid paint (Graphics2D g) {

g.fillOval(x, y, DIAMETER, DIAMETER);

}

the moveBall() method we are incrementing the “x” and “y” co-ordinates with 1.

Which will move the ball from its position and by using repaint() we are achieving it.

super.paint(g) cleans the screen.if its hidden this what going to happen.

Score is displayed: it is displayed in a textfield which keeps on changes as the number of times the ball makes contact with the shaft below once it misses then the game is ended and a dialog box appears saying end of game and after clicking ok button the frame is closed.

g2d.setRenderingHint(RenderingHints.KEY_ANTIALIASING,RenderingHints.VALUE_ANTIALIAS_ON); it makes the border of the ball smoother.

In the below section of code we see that there are two properties “xa” and “ya”, which represents the speed in which the ball is moving. If xa = 1, the ball moves to the right, one pixel every round, if xa = -1, the ball moves to the left. In the same way ya = 1 moves the ball down and ya = -1 moves the ball up. This is do ne with the lines, “x = x + xa” and “y = y + ya” of the moveBall( ) method.

When the ball reaches the right border or when (x + xa > getWidth() – 30), what we`ll do, is to change the direction of the movement on the “x” axis or what is the same we assign -1 to “xa”; “xa = -1”.

Events used:

Use of MouseEvent:

addMouseListener(new MouseListener() {

publicvoid mouseReleased(MouseEvent arg0) {

setBackground(Color.gray);

}

publicvoid mousePressed(MouseEvent arg0) {

setBackground(Color.green);

}

publicvoid mouseExited(MouseEvent arg0) {

setBackground(Color.gray);

}

publicvoid mouseEntered(MouseEvent arg0) {

setBackground(Color.blue);

}

publicvoid mouseClicked(MouseEvent arg0) {

setBackground(Color.cyan);

}

});

 

All 5 methods of Mouse Listener is used here for changing the background color of the frame.when the mouse enters the frame the color changes to blue and when the mouse is exited from the frame the color changes to gray.

addKeyListener(new KeyListener() {

publicvoid keyTyped(KeyEvent e) {

}

publicvoid keyReleased(KeyEvent e) {

racquet.keyReleased(e);

}

publicvoid keyPressed(KeyEvent e) {

racquet.keyPressed(e);

}

});

KeyEvent:

addKeyListener(new KeyListener() {

publicvoid keyTyped(KeyEvent e) {

}

publicvoid keyReleased(KeyEvent e) {

racquet.keyReleased(e);

}

publicvoid keyPressed(KeyEvent e) {

racquet.keyPressed(e);

}

});

publicvoid keyReleased(KeyEvent e) {

xa = 0;

}

publicvoid keyPressed(KeyEvent e) {

if (e.getKeyCode() == KeyEvent.VK_LEFT)

xa = -1;

if (e.getKeyCode() == KeyEvent.VK_RIGHT)

xa = 1;

}

In the keypressed method as you can the see the event object gets the key code which might be left,right,up,down. So based on the it is compared to KeyEvent.VK_LEFT if it it is equal it will move the shaft to left or Right. Based on the xa value.

ActionEvent:

b1.addActionListener(new ActionListener(){

publicvoid actionPerformed(ActionEvent e) {

Racquet.buttonClicked(e);

}

});

b2.addActionListener(new ActionListener(){

publicvoid actionPerformed(ActionEvent e) {

Racquet.buttonClicked(e);

}

});

publicstaticvoid buttonClicked(ActionEvent e)

{

if(e.getActionCommand().equalsIgnoreCase(“<<“))

xa=-1;

if(e.getActionCommand().equalsIgnoreCase(“>>”))

xa=1;

}

publicvoid buttonIdeal(ActionEvent e)

{

xa=0;

}

For the buttons b1,b2 when have two action events when you press any of the button the method getActionCommand will get the text on the button and will match it with the equals method text which is << ,>> whichever is matched it will move the shaft to that direction based on the xa value.

ItemEvent:

                 It is added to combo box where you are given an option to select the level you want to play. It will only display the JOptionPane instead of switching to the next level.

final JComboBox combo=new JComboBox();

combo.addItem(“LEVEL1”);

combo.addItem(“LEVEL2”);

combo.addItem(“LEVEL3”);

final String speed=null;

combo.addItemListener(new ItemListener() {

publicvoid itemStateChanged(ItemEvent ie) {

if(combo.getSelectedItem().equals(“LEVEL1”))

{

1. showMessageDialog(null, “Level Increased 1”);

return;

}

if(combo.getSelectedItem().equals(“LEVEL2”))

{

JOptionPane.showMessageDialog(null, “Level Increased 2”);

return;

}

if(combo.getSelectedItem().equals(“LEVEL3”))

{

JOptionPane.showMessageDialog(null, “Level Increased 3”);

return;

}

}

});

WindowEvent:   In the program we have used Frame so we must write the closing frame code for closing the frame. windowClosing() will be used to close the frame.

frame.addWindowListener(new WindowListener() {

publicvoid windowOpened(WindowEvent arg0) {   }

publicvoid windowIconified(WindowEvent arg0) {}

publicvoid windowDeiconified(WindowEvent arg0) {         }

publicvoid windowDeactivated(WindowEvent arg0) {       }

publicvoid windowClosing(WindowEvent arg0) {

1. exit(0);

}

publicvoid windowClosed(WindowEvent arg0) {                 }

publicvoid windowActivated(WindowEvent arg0) {           }

});

Introduction:

This Automatic Remark Notice Generation project deals about generating an automatic notice about the mistakes made by a student. Earlier in all educational institutions when a student commits a mistake they used to manually maintain record of the students mistake and generate notices manually.

But with the “Automatic remark notice generator” we maintain a database which consists all the details of the student and the mistakes done by the student.

Once the data is entered into the remark database a notice is generated automatically and posted to his/her respective department and to the administrative office.

Every college has rules and regulations which every student must follow, and these generally fall in two categories.

One is ‘general college rules’ and the other is ‘examination rules’.

Our project is about maintaining records of the student in a database that violate the above rules and generating a notice.

Once the notice is generated, this notice is automatically mailed to the corresponding head of the department and to the administrative office.

A notice is generated only when a student commits a serious mistake.

Existing System:

Many educational institutions maintain the details of the student as hard copy.

In the existing system a person should manually generate a notice every time the student commits a mistake.

Generating such notices needs lot of human intervention and time.

Drawbacks of Existing System:

1. Maintaining these records as hard copies is a tough task.

2. Generating a notice manually is a time taking process.

3. To analyze how many times a student made a mistake is tough.

Proposed System:

1. Stores the mistakes made by the student in a database.

2. Based on the mistake a notice is generated automatically.

3. The generated notice is automatically mailed to respective department.

The purpose of this Recipe Publishing Management System Project is to define scope and requirements for recipe publishing tool  to be developed for Specialty food chain. This chain has become popular in various kinds of cuisines across country.

A brief background for this initiative goes back to company’s marketing strategy of sharing their most popular recipes on their website. Recipes added to the site did not appear in the Google’s recipe search of content with rich snippets. They lacked the necessary format for narrowing down search based on parameters like Ingredients, calories, cooking time etc.

On analysis of their implementation it was discovered that the recipes were published in a plain HTML, whereas Rich Snippets required adherence to the Microdata format as mentioned in www.schema.org.
Recipe Publishing Management System will provide:

1 . Simple interface to enter recipes.
2 . Automatically generate the recipe html for publishing on the website.
3 . The recipes published as Rich Snippets, will comply with the Microdata
format requirements of Google’s recipe view.
This document is the primary input to the development team to architect a solution for this project.

System Users:

The Chefs and the food chain’s Management will be users of the tool.

Requirements:

The recipe tool is required to capture and store the recipes in a format understood by the Google’s recipe search. The following layout is a sample search result of a popular Indian dessert ‘Kheer’.

The recipe view displays the content in Rich Snippet format providing information about the name of the recipe, website, preparation time, a brief description. The left panel displays the options for narrowing down the search ingredient or calorie count wise.
Create/Maintain Recipes:

The tool will display an intelligent form for capturing required recipe details to ensure automatic HTML publishing, compliant with recipe micro format by construction.

The form will include the Rich Snippet fields such as Picture, Preparation time, Cooking Time, Overall Time, Key ingredients, and Calorie count. It also allows classification of the Recipe as ‘Entrée, Main Course or a Dessert’. In addition, it includes information like Name of the Dish, Recipe Published date, Summary, Nutrition information, Ingredients, Steps to prepare the dish, and a Video if available.

The recipes can be saved as draft and published once the information entered is complete. The user can modify the recipes once they have been published.

The HTML will be published in the directory based on the category of the recipe. For example, under HTML root there can be directories like “entrée”, “main-course” and “dessert”.
For testing purpose, set-up a simple web server and point it’s HTML root so that it maps to the recipe’s category directory structure.
About Microdata:

While HTML tells the browser how to display the content, Microdata format adds semantics to the content being published by HTML. With these additional tags, search engines are able to recognize the underlying meaning of the content.

Using Microdata you can help search engines and other applications better understand your content and display it in a useful, relevant way. Microdata is a set of tags, introduced with HTML5, which allows you to do this. Read more about Microdata on http://www.schema.org/docs/gs.html.
Recipe specific schema can be found at http://schema.org/Recipe URL. Google’s guidelines for recipe may be found at http://support.google.com/webmasters/bin/answer.py?hl=en&answer=173379 URL

About Rich Snippets:

Rich Snippets make the search results meaning full for the user by providing highlights of the entry in a manner that either meets the user’s expectation or invokes interest to click on the link and get to the details. Referring to the recipe view shown earlier in the document, analysis of the search results shows each entry is displaying the key highlight of the dish e.g. Picture of the dish, brief description, preparation time, review ratings, calorie count etc. This kind of information contributes towards making a Rich Snippet of the Recipe. You may read more on
http://googlewebmastercentral.blogspot.in/2009/05/introducing-rich-snippets.html URL.
Testing Guidelines:

The published HTMLs must be validated using Google’s Rich Snippets Testing Tool available at http://www.google.com/webmasters/tools/richsnippets URL.

Development Environment:

Recipe Publishing System will be developed as a web application using Java/JSP and DB2 database. Eclipse will be used as the IDE for the same. Knowledge of XML is a must for this project.

INTRODUCTION:

The Health Record Management System is used in order to simplify the conventional way of checking in patients where we can increase the availability and usage of the information in the record, improve the quality of information as well as health care and benefit each patients checking in as well as the whole of medical community.

MOTIVATION:

We choose this area of interest because it helps us maintain and store the records of the total health care management inclusive of patients, doctors, nurses as well as the pharmacists.

MODULES:

• Registration
• Case Records
• Daily Entries
• Drug Store

PROJECT GOAL:

The main motto behind this project is to generate the automated information of the patients there by checking the previous history of the patients and reducing the time consumption.