In this meeting i had chat with Dr.Al-Nuaimy and others student.
In this meeting we talk about our project and Dr.Al-Nuaimy tell us about what should we do.
1.Meeting in Friday 10:00 AM Every week.
2.Always work with logbook.
3.Blog should be open.(Here it is.)
4.Specification Report Form.
There Specification Report Form should have four part!
1.why?
Project Rationale and Industrial Relevance
2.what?
Project Description
3.How?
Methodology
4.When?
Project Tasks and Milestones
And there also show what result should be when finish this project!
Friday 28 September 2012
Friday 14 September 2012
【Amazing】Virtual Keyboard！
Like in move!
I want this in my Raspberry Pi
I want this in my Raspberry Pi
Put the future at your fingertips with our virtual laser keyboard.
Revolutionary laser technology projects a virtual keyboard on any flat surface
Advanced optics track your fingers like magic
Connect via Bluetooth® wireless technology
Easily pair the laser projection keyboard with your smartphone, laptop or tablet
Compact, keychain design makes our virtual keyboard super portable
Rechargeable li-ion battery (USB cord included)
Only at Brookstone
You touch, it types.
Don’t let the keychain fool you, inside advanced optics are hard at work tracking your fingers like magic.
Laser projection keyboard transforms flat surfaces.
Our virtual keyboard transforms a flat surface into an instant work station. So you can type up a storm any time you want.
Bluetooth® wireless technology.
Because it is Bluetooth enabled, the laser projection keyboard pairs quickly and easily with tablets, smartphones and most laptops.
Rechargeable, lithium ion battery.
Comes with a USB cord for easy recharging. Lasts for up to two hours of continuous typing.
Order your Virtual Laser Projection Keyboard from Brookstone today.
The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. and any use of such marks by Brookstone is under license.
Thursday 6 September 2012
【 SVN version control】 VisualSVN Server configuration and method of use
http://www.visualsvn.com/server/getting-started/
Add Solution to Subversion
First you need to place your solution under Subversion control. There are only two main steps to do this: execute the “Add Solution to Subversion” command and commit your solution to the repository.
Executing the “Add Solution to Subversion” command
Open or create new solution in Visual Studio. Then choose Add Solution to Subversion from the VisualSVN menu command and the wizard will open.
Now you should choose the repository where your code history will be stored. VisualSVN can add your code to a new or an existing repository. When VisualSVN creates new repository it creates the default structure with branches, tags and trunk folders. Initially your code will be stored in the trunk folder.
Now you choose the directory where your code will be stored. VisualSVN can add your code to a new or an existing repository. When VisualSVN creates new repository it creates the default repository structure with branches, tags and trunk folders. Initially your code will be stored in the trunk folder.
Please note that when adding your code to an existing repository you can choose any remote repository. For example, you can easily add your solution to a hosted repository provided by services like Google Code. Just enter the repository URL in the corresponding field in the dialog.
After this operation is finished all source files and folders in your solution will be marked as added to Subversion. Added files will be indicated by yellow icons in Solution Explorer. But all changes are still local and have not been sent to the target repository yet. This allows you to review the results of adding your solution to Subversion before the operation is finished.
After you committed your solution to Subversion you should see green icons in Solutions Explorer indicating that your code is controlled by Subversion and you have no local changes. You are ready to work!
Add Solution to Subversion
First you need to place your solution under Subversion control. There are only two main steps to do this: execute the “Add Solution to Subversion” command and commit your solution to the repository.
Executing the “Add Solution to Subversion” command
Open or create new solution in Visual Studio. Then choose Add Solution to Subversion from the VisualSVN menu command and the wizard will open.
Now you should choose the repository where your code history will be stored. VisualSVN can add your code to a new or an existing repository. When VisualSVN creates new repository it creates the default structure with branches, tags and trunk folders. Initially your code will be stored in the trunk folder.
Now you choose the directory where your code will be stored. VisualSVN can add your code to a new or an existing repository. When VisualSVN creates new repository it creates the default repository structure with branches, tags and trunk folders. Initially your code will be stored in the trunk folder.
Please note that when adding your code to an existing repository you can choose any remote repository. For example, you can easily add your solution to a hosted repository provided by services like Google Code. Just enter the repository URL in the corresponding field in the dialog.
After this operation is finished all source files and folders in your solution will be marked as added to Subversion. Added files will be indicated by yellow icons in Solution Explorer. But all changes are still local and have not been sent to the target repository yet. This allows you to review the results of adding your solution to Subversion before the operation is finished.
Commit Solution to Subversion
To commit your solution to Subversion, select VisualSVN | Commit menu item, enter a comment and click OK. The first versions of your source files will be sent to the target Subversion repository.
[Report]bug reporting template
http://www.noverse.com/images/noverse-bug-reporting-template.txt
Noverse Bug Reporting Template
==============================
Title:
Class:
e.g. "Feature Request", "System Error", "Serious Bug"
Date:
Reported By:
Email:
Product: Version:
Platform: Version:
Browser: Version:
URL:
Is it reproducible: Yes / Occasionally / One Time / No
Description
===========
Steps to Produce/Reproduce
--------------------------
Expected Results
----------------
Actual Results
--------------
Workarounds
-----------
Attachments
-----------
Other Information
-----------------
Noverse Bug Reporting Template
==============================
Title:
Class:
e.g. "Feature Request", "System Error", "Serious Bug"
Date:
Reported By:
Email:
Product: Version:
Platform: Version:
Browser: Version:
URL:
Is it reproducible: Yes / Occasionally / One Time / No
Description
===========
Steps to Produce/Reproduce
--------------------------
Expected Results
----------------
Actual Results
--------------
Workarounds
-----------
Attachments
-----------
Other Information
-----------------
Subscribe to:
Posts (Atom)