Author: unmeshballal

How to Export Thunderbird Emails to Outlook

Please follow the steps if you have to export Thunderbird emails to Outlook:

1. Open the link in web browser: http://www.aid4mail.com/export-thunderbird-to-outlook.php

2. Download aid4mail free version and start the application

3. Click add folder and choose Thunderbird \ mail folder (you can find the top level folder Thunderbird is from Settings) 

4. Click Ok and then Next (Note the destination folder)

5. Click Next and then Start conversion of your Thunderbird emails to .eml files

6. Once done click Close

7. Now Download and install http://www.outlookfreeware.com/en/runtime.aspx?src=setup (you have to register to download)

8. Next Download and install http://www.outlookfreeware.com/en/products/all/OutlookMessagesImportEML/

9. start Outlook (2013 – could use same steps for other versions though haven’t tested)

10. Click Folder tab create new folder name it “backupemails” or anything you want

11. Click outlookfreeware.com from top menu and click “Import messages from eml format” link

12. For Source folder specify folder as noted in step 4

13. for Destination “old emails” as noted in step 10

14. Click Run

15. Verify all emails are showing in mail folder

16. Delete the folder from Step 4

17. Uninstall the installed utilities and you are done!

 

Advertisements

Agile Process for Web Applications Development

Developing agile enables rapid application development if all requirements are understood and documented before starting for the web application development project. Hence to reach an agile-able state there are a lots of prerequisites that need to understood and documented before the Agile sprint can be started:

Here is a process diagram that can be implemented to enable the rapid application development.

PMDevProcess

As you see that there are input documents for each phase of software development. Before the project starts most important being the Requirement Analysis. Requirement analysis accurately documents all necessary features in details and functionality desired. In web applications this is not enough because additionally a visual design is necessary to create how the app will actually be used by end user. The mock-up of all the pages and visual design gives a clear flow of the app.

Based on the visual design and requirements documentation its now possible to create a Product Test Plan. This test plan is actually used by the Tester/QA to start with Test Case development. As shown the Tester/QA engineer develops the Use Case document so all Test scenarios can be developed. All these documents are input documents for Detailed Technical Design document.

A detailed technical document is then reviewed and approved by all stakeholders. An Agile Scrum master is now ready to take this forward since all the detailed technical design and the tasks can be identified. Scrum Master then proceeds with a 10 day sprint cycle and delivers a demo at end of each sprint.

Using node.js to serve static html web pages

If you are a beginer for node here is the definition as per nodejs.org

It’s a platform built on chrome’s javascript runtime for easily building fast scalable network applications. Node.js uses and event driven, non-blocking IO model that makes it lightweight and efficient, perfect for data intensive real-time applications that run on distributed devices. 

I started with node hello-world app and quickly started comparing with the traditional web frameworks. Realised that to take advantage of node it should serve the basic needs of the typical internet application platform only then we can scale it to build advanced, seamless, complex and robust web applications. Hence I defined a first task to myself:  “Creating a WebServer serving static html web pages“.

Here is the brief tutorial to how to get that going: Install node from nodejs.org.

create package.json and add the following lines:

{
“name”: “static-web”
, “version”: “0.0.1”
, “private”: true
, “dependencies”: {
“requirejs”: “latest”
, “connect”: “2.7.0”
}
, “devDependencies”: {
“path”: “latest”
, “events”: “latest”
}
, “scripts”: {

}
}

run npm install on command prompt to install dependent packages. The server is created using http.createServer command and need to use the filesystem module and pass html files to the server requests. 

The code looks like:

http.createServer(function(request, response) {

var lookup = path.basename(decodeURI(request.url)) || ‘index.html’,f=’content/’ + lookup

}).listen(8000);

Once the server is configured run the following command to fire up the server

node server.js

you are done! server is up and running subsequently we can add many html files in this folders with links etc.. to server a static web server. Download complete code from github using the following command:

git clone https://github.com/uhbl92/node-static-server.git

 

Customizing Agile story using a custom template in JIRA

In Agile projects at times requirements are periodical and come in a specific format. The default story interface is a free flow text and do not allow customizations. Custom field’s options from JIRA enable us to achieve this task. Detailed instructions are here:
https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field
Hence for a web application or a web page now I can add fields like:
Page Title:
Layout template: (multicolumn/single column/grid) etc..
A sub-task module further simplifies task by adding multiple pages where now each page can be specified with multiple custom fields.

My prototype development experience with Magento

Magento is an ecommerce framework vendor where we recently developed a prototype. I started off with installing Magento Community Edition from http://www.magentocommerce.com/download

Magento offers demo data as optional installation. If you are installing for first time it’s recommended to also download the demo data.

Before installing you need a Wamp or XAMP installed on your windows machine. If you install the latest version it may not be supported as yet so do check the System Requirements from http://www.magentocommerce.com/system-requirements page before copying downloaded files in your web folder. Load the sample data in magento database and point to your browser to magento web folder. Rest of the installation is straightforward and once you setup the passwords you are done.

Browse to the admin panel and there are plenty of things to configure from extensions to add-ons to third party integrations. The crux of the magento is in these configurations. Once configured the payment method and other customizations you are done! Now next step is to add modify the product catalog. Since we loaded the sample data its already there. Your first magento application is now ready.

If don’t want to do even these steps there is a easier way out to directly go for hosted solution checkout http://go.magento.com/plans/

Conclusion: eCommerce app development couldn’t get easier than this!