Tuesday, February 7, 2012

Google Maps images downloader


Google Maps images downloader



Google Maps is a tool you can use via your Internet browser. You can find maps filled with great amounts of detail, yet it only works when you are online, and there are no built-in features to save a particular map.

The 'Print' option is one way to save a map (in PDF format) within Google Maps – the downside of this method is that one can only print what is actually on-screen. If you wish to capture a bigger physical area, you may have to zoom out multiple times, thus losing the location's minute details. Conversely, if you want to show accurate detail, you would have to zoom in and lose the rest of the expanse.

How can you capture a large area or map and still have a good amount of detail? This article will show you how, without using a Google Maps images downloader.

Tools Needed:

  • Notepad
  • Mozilla Firefox Internet Browser
  • Firefox ScreenGrab Extension – This utility can capture what appears on-screen: the image in a window, a specific selection, a frame, or the whole page. It stores Web pages as images. These images may be saved as files or saved on the clipboard.

Instructions:

Log on to the Net using the Firefox browser. Download and install ScreenGrab.

Go to this URL: http://maps.google.com/ and access the map location you want to capture.

Manipulate Google Maps' zoom feature based on the image you want to capture and the amount of detail you need (depending on your prospective use for the map). Do not worry about the map size at this stage.

Go to 'Link' at the upper right portion of the map. Open that link, and click on the 'Customize and preview embedded map' option in the small pop-up panel that emerges.

One can adapt the map size according to the user's needs through another pop-up panel. After choosing the option 'Custom', type in the final map's dimensions (height and width in pixels). If the values are changed to 2000 x 800, for example, the preview map will adjust to show the new size.

HTML code will appear under the map preview. Take note of the code if the current map size is what you need.

Access the Notepad program and paste the HTML code from the previous step. There are no specifics to follow for naming the file, just make sure that it is saved with an '.html' extension. Your file name may be 'hometown.html', for example. Append one quotation mark before the first character and another after the last character of the file name. This ensures that Notepad stores the file with the '.html' extension (and not '.txt').

Access the HTML file from the previous step within the browser. The map will appear in the size you have chosen. The map will most likely be physically larger that your screen, so shift the map left, right, up, and down to check the 'unseen' portions.

You now have a map in the size you have specified. All that remains is to capture that map and store it as an image. Firefox ScreenGrab now comes into play. Once ScreenGrab has been installed, click on its icon in your Firefox browser. Select 'Complete Page/Frame' to save. Save the picture as any of these two file formats: PNG or JPG.

Your Google Map has been downloaded and ready for printing!

Monday, January 23, 2012

How to capture the parallel port's output

How to capture the parallel port's output (PRN:, LPT1:, LPT2: .. LPT9:)

On Unix and Linux systems, redirecting the print output to a file is a very easy task, but on some old DOS or Windows Console Mode applications, the programmer did not give the end user this ability.

In this case you can redirect the LPT output to a file for Printfil, even if a parallel printer is physically connected to that port (for example a Windows-only Laser printer), and even if the parallel port is not physically installed on the PC (on new machines, the parallel ports are no more included nowadays).

Printfil can capture an LPT port by using 4 different tecniques (Mode 0, 1, 2, 3) on NT-based systems (Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 2008, Windows 7). On Windows 95/98/ME only Mode 1 is available


Friday, January 20, 2012

Thursday, January 19, 2012

Open source Web Appointment Scheduler System

 Overview of WASS

http://sourceforge.net/projects/wass/files/wass.4.0.1/


The WASS system supports appointment scheduling over the web.  Unlike traditional scheduling systems, which allow people to specify when they are busy (e.g., when they have meetings), WASS allows people to specify when they are free.  WASS allows appointments to be scheduled only for these free times, which WASS  refers to as "blocks". 

The way WASS works is as follows:

1.       Someone who wants to be available for appointments (let's call her "PROFESSOR SMITH") goes into WASS and  creates a calendar for themselves (they only need to do this once).  They then add blocks of available time to that calendar.  They can add or delete such blocks whenever they like.  The blocks can either be single blocks              (a block of time on a specific date) or recurring blocks (e.g., every Tuesday from 9:30 to noon between a start  and end date).  Each block corresponds to a date and time when PROFESSOR SMITH is available to met with other people  (e.g., their "office hours").  PROFESSOR SMITH can divide any of these block into individual appointment "slots", or  treat them as a monolithic unit (first-come, first-served).  PROFESSOR SMITH can also assign various kinds of access limits to the blocks (e.g., restrict access to specified users and/or to users in specified courses).

2.       A person wishing to make an appointment (let's call her "STUDENT JANE") with PROFESSOR SMITH goes into WASS, looks up PROFESSOR SMITHS's calendar, finds a block of available time that is covenient for her, and schedules an appointment with PROFESSOR SMITH at that time.  STUDENT JANE can only schedule an appointment  during one of the blocks of available time that PROFESSOR SMITH has added to her calendar.  If the block she selects has been divided into appointment "slots" by PROFESSOR SMITH, then STUNDENT JANE must select an available slot.  PROFESSOR SMITH can set limits on how many appointments an individual student can sign up for, as well  as the total number of appointments for a given block.

3.       STUDENT JANE and PROFESSOR SMITH each receive email notifications and reminders about the appointments,                 and they can go into the system to view and/or cancel these appointments at any time. What differentiates WASS from standard calendar/scheduling systems is its ability to allow people to specify  their availability.  This is useful in situations such as office hours scheduling (the professor is only available on specific dates for specific periods of time).  It can also be used to schedule things such as specialized equipment (which has limited aviability) or rooms (e.g., squash courts).  WASS is useful in cases where a person or resource is available only on specific days during specific periods of time.  It is not intended to replace a standard calendar system (such as Outlook), but can be used an an adjunct to such systems (WASS can generate iCal streams which can be imported into systems such as Outlook).

 

The WASS system is fundamentaly asymetric.  It consist of a set of calendars created by people who hold office hours  (e.g., professors, deans, advisors), and appointments made by people who meet with the calendar owners (e.g, students).  Students do not need to create calendars; only people who hold office hours create calendars.  WASS also supports the notion of managers, people who manage a professor's calendar.   It should be noted, however, that WASS does not enforce any kind  of role assignment.  Anyone who can authenticate to the system can create a calendar.  Thus a student could create a calendar that other people would access to make appointments with the student (e.g., a student who was the leader  of a student organization could create a calendar on which they indicate their avaialbility for appointments with other students  who wish to meet with them).  A given user could use WASS both to publish their availability, and to make appointments with other users.  For example, a professor who has a calendar in the system could use WASS to schedule an appointment with another professor who has a calendar in the system.  In the interests of security, you should probably move this text file out of the WASS admin directory and into a directory that  is not accessible to web users.  It is not needed by the running WASS system.

Open source Web Appointment Scheduling System (WASS)


Overview of WASS

 

The WASS system supports appointment scheduling over the web. Unlike traditional scheduling systems, which allow people to specify when they are busy (e.g., when they have meetings), WASS allows people to specify when they are free. WASS allows appointments to be scheduled only for these free times, which WASS refers to as "blocks". The way WASS works is as follows:

 

1.      Someone who wants to be available for appointments (let's call her "PROFESSOR SMITH") goes into WASS and creates a calendar for themselves (they only need to do this once). They then add blocks of available time to that calendar. They can add or delete such blocks whenever they like. The blocks can either be single blocks (a block of time on a specific date) or recurring blocks (e.g., every Tuesday from 9:30 to noon between a start and end date). Each block corresponds to a date and time when PROFESSOR SMITH is available to met with other people (e.g., their "office hours"). PROFESSOR SMITH can divide any of these block into individual appointment "slots", or treat them as a monolithic unit (first-come, first-served). PROFESSOR SMITH can also assign various kinds of access limits to the blocks (e.g., restrict access to specified users and/or to users in specified courses).

 

2.      A person wishing to make an appointment (let's call her "STUDENT JANE") with PROFESSOR SMITH goes into WASS, looks up PROFESSOR SMITHS's calendar, finds a block of available time that is covenient for her, and schedules an appointment with PROFESSOR SMITH at that time. STUDENT JANE can only schedule an appointment during one of the blocks of available time that PROFESSOR SMITH has added to her calendar. If the block she selects has been divided into appointment "slots" by PROFESSOR SMITH, then STUNDENT JANE must select an available slot. PROFESSOR SMITH can set limits on how many appointments an individual student can sign up for, as well as the total number of appointments for a given block.

 

3.      STUDENT JANE and PROFESSOR SMITH each receive email notifications and reminders about the appointments, and they can go into the system to view and/or cancel these appointments at any time. What differentiates WASS from standard calendar/scheduling systems is its ability to allow people to specify their availability. This is useful in situations such as office hours scheduling (the professor is only available on specific dates for specific periods of time). It can also be used to schedule things such as specialized equipment (which has limited aviability) or rooms (e.g., squash courts).

 

WASS is useful in cases where a person or resource is available only on specific days during specific periods of time. It is not intended to replace a standard calendar system (such as Outlook), but can be used an an adjunct to such systems (WASS can generate iCal streams which can be imported into systems such as Outlook).

 

The WASS system is fundamentaly asymetric. It consist of a set of calendars created by people who hold office hours (e.g., professors, deans, advisors), and appointments made by people who meet with the calendar owners (e.g, students). Students do not need to create calendars; only people who hold office hours create calendars. WASS also supports the notion of managers, people who manage a professor's calendar. It should be noted, however, that WASS does not enforce any kind of role assignment. Anyone who can authenticate to the system can create a calendar. Thus a student could create a calendar that other people would access to make appointments with the student (e.g., a student who was the leader of a student organization could create a calendar on which they indicate their avaialbility for appointments with other students who wish to meet with them).

 

 A given user could use WASS both to publish their availability, and to make appointments with other users. For example, a professor who has a calendar in the system could use WASS to schedule an appointment with another professor who has a calendar in the system. In the interests of security, you should probably move this text file out of the WASS admin directory and into a directory that is not accessible to web users. It is not needed by the running WASS system.

 

Source: README.txt, updated 2011-10-13

Create an AJAX Application Using JSON and Java Servlets

How to Create an AJAX Application Using JSON and Java Servlets?

In this article I would like to show how JSON (JavaScript Object Notation) and Java servlet can be used together in a little AJAX (Asynchronous JavaScript and XML) application.

http://itspice.net/cms/web-internet/ajax-json-application-java-servle


Tuesday, January 17, 2012

Creating & Parsing JSON data with Java Servlet/Struts/JSP

Creating & Parsing JSON data with Java Servlet/Struts/JSP





java logo

http://viralpatel.net/blogs/2009/02/creating-parsing-json-data-with-java-servlet-struts-jsp-json.html

JSON (JavaScript Object Notation) is a lightweight computer data interchange format. It is a text-based, human-readable format for representing simple data structures and associative arrays (called objects). The JSON format is specified in RFC 4627 by Douglas Crockford. The official Internet media type for JSON is application/json.

The JSON format is often used for transmitting structured data over a network connection in a process called serialization. Its main application is in AJAX web application programming, where it serves as an alternative to the traditional use of the XML format.