link 1
========
========
link 2
=======
=======
http://www.planetarypositions.com/notes/2006/02/clarifications-on -manglik-dosha.html
link 3
=======
=======
link 4
=======
=======
Tuesday, July 29, 2008
kundli milan : mangalik dosh : facts and myths
Now this is really interesting. In indian culture the life of people is governed by few pieces of paper.
The highest point of ignorance, is you are supposed to marry a person whose kundli matches with you.When a persons kundli matches with other persons kundli , and the families are ok with them getting married , then only the to be bried and groom are allowed to meet each other that too inthe presence of others. The only first time these bride and groom talk to each other as people is after getting married. And if after all this if the marriage does not survives its the sole responsibility of these two people who got married.
To those who arrived late kundlis are the parchment of paper which a pandit makes at the birth of child according to the planetry positions,the date and time of birth. There are some characterstics defined in this kudli along with dosh or the defects like sarpdosh,mangaldosh, kaldosh etc etc.
These points are taken in consideration when someone is getting married or is about take some very important decision.
So much for the indian mythology.
Dont get me wrong. All this which i stated above is vaild and true to an extent. But the only issue with indian society is they take everything on face value and refuses to see the intellectual and the practical side of the ritual and traditions which have been followed till now.
When indian society was under construction if you allow me to say that there were hardly any educated people around. there used to be alot of things which were getting hard for the intellectuals and the informative people to tell to everyone.
so they took the easy way out . They started getting these traditions into the daily practicse of the people without letting them know why they are doing it.
for example prohibition of ladies from going into kitchen when they are in periods.
It was very difficult to tell the ignorant one what the mensuration cycle is why it happens and what precautions have to be taken. It was too complex for them. But along with this it was also important to take care of this situation and control it before it gets out of control. The personal hygiene and proper rest of the woman under going mensuration cycle was the top priorty in the mind of the intellectuals. So they made this tradition so that woman can get some rest also and can have proper hygiene. But with time it became a curse for woman and they started treating periods as very bad thing and still they are not over it.
Same is with kundli milan. Earlier when there was not so freedom of intermixing of opposite sex, getting them married and keep that marriage healthy was a very tidious task. So to overcome that a bit of study was done and characterstics were defined for people taking birth under certain conditions. A match of those conditions was a sound formulae for getting married. So it was done for the benefit of people. But with time as the intellects never bothered to tell the scientific reason behind matching these kundlis and the proper way to do it, it also become one of the most followed tradition without any knowledge and now its on the way of becoming a curse for the new indian generation.
There are lots and lots of other traditions which are just followed for the sake of just being dragged. I do so because my forefather used to do so is the common thinking of normal indian. Anyone who tries to rationalise is thought as a rebel and is outcasted.
Am also posting some very useful links here related to indian myths, kunli milan and manglik dosh and facts.
But most important is this picture which am going to put here. Our so called pandits who match kundlis have seem to miss this chapetr while studying all the jyotish and astrology.
The highest point of ignorance, is you are supposed to marry a person whose kundli matches with you.When a persons kundli matches with other persons kundli , and the families are ok with them getting married , then only the to be bried and groom are allowed to meet each other that too inthe presence of others. The only first time these bride and groom talk to each other as people is after getting married. And if after all this if the marriage does not survives its the sole responsibility of these two people who got married.
To those who arrived late kundlis are the parchment of paper which a pandit makes at the birth of child according to the planetry positions,the date and time of birth. There are some characterstics defined in this kudli along with dosh or the defects like sarpdosh,mangaldosh, kaldosh etc etc.
These points are taken in consideration when someone is getting married or is about take some very important decision.
So much for the indian mythology.
Dont get me wrong. All this which i stated above is vaild and true to an extent. But the only issue with indian society is they take everything on face value and refuses to see the intellectual and the practical side of the ritual and traditions which have been followed till now.
When indian society was under construction if you allow me to say that there were hardly any educated people around. there used to be alot of things which were getting hard for the intellectuals and the informative people to tell to everyone.
so they took the easy way out . They started getting these traditions into the daily practicse of the people without letting them know why they are doing it.
for example prohibition of ladies from going into kitchen when they are in periods.
It was very difficult to tell the ignorant one what the mensuration cycle is why it happens and what precautions have to be taken. It was too complex for them. But along with this it was also important to take care of this situation and control it before it gets out of control. The personal hygiene and proper rest of the woman under going mensuration cycle was the top priorty in the mind of the intellectuals. So they made this tradition so that woman can get some rest also and can have proper hygiene. But with time it became a curse for woman and they started treating periods as very bad thing and still they are not over it.
Same is with kundli milan. Earlier when there was not so freedom of intermixing of opposite sex, getting them married and keep that marriage healthy was a very tidious task. So to overcome that a bit of study was done and characterstics were defined for people taking birth under certain conditions. A match of those conditions was a sound formulae for getting married. So it was done for the benefit of people. But with time as the intellects never bothered to tell the scientific reason behind matching these kundlis and the proper way to do it, it also become one of the most followed tradition without any knowledge and now its on the way of becoming a curse for the new indian generation.
There are lots and lots of other traditions which are just followed for the sake of just being dragged. I do so because my forefather used to do so is the common thinking of normal indian. Anyone who tries to rationalise is thought as a rebel and is outcasted.
Am also posting some very useful links here related to indian myths, kunli milan and manglik dosh and facts.
But most important is this picture which am going to put here. Our so called pandits who match kundlis have seem to miss this chapetr while studying all the jyotish and astrology.
Indian Caste System : facts ,myths and reforms : an insight
This is one of the social cause which is very close to my heart. I have always failed to understand why we have caste systems and why we need it. In my earlier days i always use to wonder why some guy coming to my house always sits outside of our main sitting area , or why do he gets served in seperate utensils which used to be kept always seperate not to be use by the family members in future.
Now when i have started understanding the basics of this caste system , I have come to know a shocking truth. This caste system which was made in very early days was for the benifit of the indian society. But just because of few greedy and selfish people it has become an epidemic for indian society.
Before i move forward , i would like to tell that i myself am a brahmin boy by the caste.
Here i will be putting some facts and information gathered from various resources :
"Any religion that refuses to reform with the times will be relegated to oblivion and insignificance. We have classic examples of this natural phenomenon in India itself in Buddhism and Jainism. A simple and clear reform, not affecting the basic nature, is the need of the hour if Hinduism is to find its place as one of the best ways of life in twenty first century."
A clear mismatch exists between the classical four tier Caste system mentioned in the scriptures and the present day Hindu society. We find thousands of castes and sub-castes instead of a clear cut division into four. Across India, we find only the Brahmins having some similarity but other groups are let to choose their Castes according to the political and economic clouts.
For example, in Kerala, no one knows who are the Kshatriyas, Vysyas and Sudras. We have always considered Namboothiris to be the Brahmins in Kerala but there have never been a consensus on the other three castes. Other categories of people like Nairs, Ezhavas, Thiyas, Parayas, Pulayas etc. etc. have been classified under various castes in various times according to different scholars. The situation is very much similar in other states as well.
I strongly feel that we can positively utilize this mismatch between the classical four tier Caste system and the hundreds of castes that exist now. It is possible that we are confused between Gothras and Castes. All these present day categories like Jats, Rajputs, Nairs etc., etc., are essentially Gothras and are akin to the tribes in Africa and Arabia. Even if some scholars feel otherwise, I feel a lot of our problems can be solved if we define it that way. The present day names can continue as such provided they are considered as Gothras (or some other new name) instead of Castes. At one stroke, we can continue with the present naming systems and social groupings but can do away with the Caste problems.
Now when i have started understanding the basics of this caste system , I have come to know a shocking truth. This caste system which was made in very early days was for the benifit of the indian society. But just because of few greedy and selfish people it has become an epidemic for indian society.
Before i move forward , i would like to tell that i myself am a brahmin boy by the caste.
Here i will be putting some facts and information gathered from various resources :
"Any religion that refuses to reform with the times will be relegated to oblivion and insignificance. We have classic examples of this natural phenomenon in India itself in Buddhism and Jainism. A simple and clear reform, not affecting the basic nature, is the need of the hour if Hinduism is to find its place as one of the best ways of life in twenty first century."
A clear mismatch exists between the classical four tier Caste system mentioned in the scriptures and the present day Hindu society. We find thousands of castes and sub-castes instead of a clear cut division into four. Across India, we find only the Brahmins having some similarity but other groups are let to choose their Castes according to the political and economic clouts.
For example, in Kerala, no one knows who are the Kshatriyas, Vysyas and Sudras. We have always considered Namboothiris to be the Brahmins in Kerala but there have never been a consensus on the other three castes. Other categories of people like Nairs, Ezhavas, Thiyas, Parayas, Pulayas etc. etc. have been classified under various castes in various times according to different scholars. The situation is very much similar in other states as well.
I strongly feel that we can positively utilize this mismatch between the classical four tier Caste system and the hundreds of castes that exist now. It is possible that we are confused between Gothras and Castes. All these present day categories like Jats, Rajputs, Nairs etc., etc., are essentially Gothras and are akin to the tribes in Africa and Arabia. Even if some scholars feel otherwise, I feel a lot of our problems can be solved if we define it that way. The present day names can continue as such provided they are considered as Gothras (or some other new name) instead of Castes. At one stroke, we can continue with the present naming systems and social groupings but can do away with the Caste problems.
Reform
Since the four tier system is referred in our scriptures at various places and cannot be undone or wished away, all that is required is a different way of looking at the Caste system. I propose a system in which all of us Hindus live through the Sudra, Kshatriya, Vysya and Brahmin Castes as different stages in our lives.
If one goes back to the origins of Caste system, it is nothing but a scientific and systematic structuring of the then society according to the tastes and talents of the people. The hereditary principle which created bad blood in later years is nothing but a clever move on the part of Brahmins to keep the power within their kith and kin. We find this no longer valid and practical. Most children of Brahmin parents do not study scriptures, do not practice rituals and do not live like Brahmins. So how can they continue to ‘enjoy’ and monopolize Brahminhood? Similar is the case with all other castes, as they are classified now.
In the classical definition of Caste System, the different qualities attributed are as follows :
Brahmin – Learned & Spiritual
Kshatriya – Strong & Fighting
Vysya - Intelligent & Creates Wealth
Sudra – Average & Assists all others
Essentially all of us are Sudras at birth and it is evident from the qualities attributed. It is something like starting on a clean slate. The average age of a human being is now 80 years and it is logical to assume that we exhibit Sudra like qualities until one fourth of our lifetime i.e till the age of 20. In the next phase i.e till the age of 40, we are strong, physically active and exhibit qualities of a Kshatriya. This is the period most of us marry and rear children. Strong and fighting qualities are required to protect the family and feed them. In the next phase i.e 41 to 60, we all become worldly wise and participate in one form or other of wealth creation for the family and society, which makes us good Vysayas. And finally, in the last phase, we tend to concentrate on spiritual activities and get ready to depart. We all try to become ideal Brahmins in the age group above 60.
Thus all of us Hindus, irrespective of our Gothras, pass through the four tier Caste system as envisaged in our scriptures and live an ideal life fulfilling all the necessary conditions required at various phases. It is this minor reinterpretation of the Caste system that will bring about drastic changes in the way Hindu society would think. All that we need is disassociating the classical Caste system from the present arrangement we have.
Advantages
The distinct advantage of such a reinterpretation of the Caste system is the little or minimum changes that will result in the present social symbols. All the present day laws and rules can continue as such if Caste is replaced by Gothra in the statute. For example, Scheduled Castes and Scheduled Tribes will merge and change to Scheduled Gothras. And they can enjoy the same reservations they are entitled to. The bad name attributed to Hinduism on account of the caste discrimination will vanish in one stroke. All present day names and surnames can continue without any change, but no Gothra will be automatically associated with any one of the four castes. This means nobody is a Brahmin or Kshatriya or Vysya or Sudra throughout his or her life. It all depends on age and qualities. In the long run, the bad blood generated so far would fade out and Hindu society would be much more harmonious and stronger.
Remarks
Success of all this depends on the approval and blessings of the prominent religious leaders and institutions. It would be one of the most popular and progressive decisions anywhere in the world, if one ‘Dharm Sansad’ is called specifically to endorse such a viewpoint and root out causes of caste discrimination once for all from the mind of modern Hindus. It is high time the nationalist and patriotic forces in our country realized the importance of such a reform is equal to that of the Ram temple at Ayodhya, if not more.
Thursday, July 24, 2008
programming android
wont be saying much today. this android thing is literally bogging me down in every way. Each day i learn something new in it with breaking at least on coding convention each day. The UI development in it is so fast that you can show anything as a demo to anyone within few hrs of discussion. Also its expandable ,flexible and you can manuever it in any way. The interaction of ui components with in themself is awesome.
The video speaks for itself. i developed it as a demo for my client with in few days.
Thursday, July 03, 2008
building j2me project with preprocessor blocks in eclipse
Do i sound bit thrilled , hell i am. I was trying to build my j2me code in eclipse with preprocessor support for last one week and , cant really tell you that i dint left a single stone upturned but still was not able to solve this mystery.
But now the big day is here and i have solved this mystery of the millienium( god i like this stuff).
Anyways am trying to get serious here and will be letting you all people know how i did it.
The thing which i was trying to do was , i had a simple code which you can say i had a helloworld program in j2me build perfectly fine in eclipse using the eclipseme plugin, which itself was using wtk kit which i had got already installed on my machine.
Now what i wanted to do was add some preprocessor tags to it and make conditional several builds for different different condition sets in a single build process.
For all those who are new to preprocessing , you can understand it well if you have done a bit of C programming.
What a preprocessor does is that it analysis your code before building , and in return genrates a code according to the conditions defined in it. lets take a example.
This is my hellowrld.java file .
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
System.out.println("BT is supported");
System.out.println("GP is supported");
System.out.println("WMA is supported");
System.out.println("S60 is supported");
}
}
As you can see its a very simple midlet which does nothing , just prints out four statements on your console.
Now what i wanted to make seperate build of this code according to the following conditions.
1. BT and GP supported (BT means bluetooth and GP means GPRS)
2. WMA and S60 supported.
I could have done that with conditional if else block and have the code copy and pasted in them but I also wanted to reduce the jar size. That is i wanted my jar to contain only those things which are required. For that we can use preprocessor tags which processes the code before building and comments out anything which does not matches its prescribed criterias. so i put some preprocessor tags in it, and now my code looks like this.
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
System.out.println("WMA is not supported");
//#endif
//#ifdef S60
System.out.println("S60 is supported");
//#else
System.out.println("S60 is not supported");
//#endif
}
}
the "//# if" is known as a preprocessor. it gets processed before the code is build and compiled.
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
This block means that if the BT is defined then build the if block else comment out the if block and build the else block.
Now this BT can be defined in two ways.
We can put a "// # define BT" at the very beginning of the code like this :
//# DEFINE BT
public class hello extends MIDlet {we can also assign some value to it and it will work. so lets first put it that way only. the code will look like this :
//#define BT
//#define GP
//#define WMA
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
System.out.println("WMA is not supported");
//#endif
//#ifdef S60
System.out.println("S60 is supported");
//#else
System.out.println("S60 is not supported");
//#endif
}
}
and after u have build it if you go to your project folder , you can see the processed code in the ".processed folder". The processed code will look like this :
//#define BT
//#define GP
//#define WMA
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
//@
//@ System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
//@ System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
//@
//@ System.out.println("WMA is not supported");
//#endif
//#ifdef S60
//@ System.out.println("S60 is supported");
//@
//#else
System.out.println("S60 is not supported");
//#endif
}
}
You can see that in this processed code everyting is commented out which is not needed or has not been defined. The @ symbol lines are never processed so they never goes into the final build and keeps the jar file light . thats the main crux of using preprocessors. If everything goes fine you will be seeing this output on your console :
Running with storage root DefaultGrayPhone
BT is supported
GP is supported
WMA is supported
S60 is not supported
Execution completed.
703621 bytecodes executed
8 thread switches
740 classes in the system (including system classes)
3601 dynamic objects allocated (100244 bytes)
2 garbage collections (86440 bytes collected)
So much for this preprocessors, so finally we have got it running but this happens to be very crude method and if we happen to be defining preprocessors on the go then we are doomed for it.
The better way to do it is using build.xml and antenna. I will be telling you about it in next post.
But now the big day is here and i have solved this mystery of the millienium( god i like this stuff).
Anyways am trying to get serious here and will be letting you all people know how i did it.
The thing which i was trying to do was , i had a simple code which you can say i had a helloworld program in j2me build perfectly fine in eclipse using the eclipseme plugin, which itself was using wtk kit which i had got already installed on my machine.
Now what i wanted to do was add some preprocessor tags to it and make conditional several builds for different different condition sets in a single build process.
For all those who are new to preprocessing , you can understand it well if you have done a bit of C programming.
What a preprocessor does is that it analysis your code before building , and in return genrates a code according to the conditions defined in it. lets take a example.
This is my hellowrld.java file .
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
System.out.println("BT is supported");
System.out.println("GP is supported");
System.out.println("WMA is supported");
System.out.println("S60 is supported");
}
}
As you can see its a very simple midlet which does nothing , just prints out four statements on your console.
Now what i wanted to make seperate build of this code according to the following conditions.
1. BT and GP supported (BT means bluetooth and GP means GPRS)
2. WMA and S60 supported.
I could have done that with conditional if else block and have the code copy and pasted in them but I also wanted to reduce the jar size. That is i wanted my jar to contain only those things which are required. For that we can use preprocessor tags which processes the code before building and comments out anything which does not matches its prescribed criterias. so i put some preprocessor tags in it, and now my code looks like this.
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
System.out.println("WMA is not supported");
//#endif
//#ifdef S60
System.out.println("S60 is supported");
//#else
System.out.println("S60 is not supported");
//#endif
}
}
the "//# if" is known as a preprocessor. it gets processed before the code is build and compiled.
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
This block means that if the BT is defined then build the if block else comment out the if block and build the else block.
Now this BT can be defined in two ways.
We can put a "// # define BT" at the very beginning of the code like this :
//# DEFINE BT
public class hello extends MIDlet {we can also assign some value to it and it will work. so lets first put it that way only. the code will look like this :
//#define BT
//#define GP
//#define WMA
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
System.out.println("WMA is not supported");
//#endif
//#ifdef S60
System.out.println("S60 is supported");
//#else
System.out.println("S60 is not supported");
//#endif
}
}
and after u have build it if you go to your project folder , you can see the processed code in the ".processed folder". The processed code will look like this :
//#define BT
//#define GP
//#define WMA
public class hello extends MIDlet {
protected void destroyApp(boolean arg0) throws MIDletStateChangeException {
// TODO Auto-generated method stub
}
protected void pauseApp() {
// TODO Auto-generated method stub
}
protected void startApp() throws MIDletStateChangeException {
// TODO Auto-generated method stub
//#ifdef BT
System.out.println("BT is supported");
//#else
//@
//@ System.out.println("BT is not supported");
//#endif
//#ifdef GP
System.out.println("GP is supported");
//#else
//@ System.out.println("GP is not supported");
//#endif
//#ifdef WMA
System.out.println("WMA is supported");
//#else
//@
//@ System.out.println("WMA is not supported");
//#endif
//#ifdef S60
//@ System.out.println("S60 is supported");
//@
//#else
System.out.println("S60 is not supported");
//#endif
}
}
You can see that in this processed code everyting is commented out which is not needed or has not been defined. The @ symbol lines are never processed so they never goes into the final build and keeps the jar file light . thats the main crux of using preprocessors. If everything goes fine you will be seeing this output on your console :
Running with storage root DefaultGrayPhone
BT is supported
GP is supported
WMA is supported
S60 is not supported
Execution completed.
703621 bytecodes executed
8 thread switches
740 classes in the system (including system classes)
3601 dynamic objects allocated (100244 bytes)
2 garbage collections (86440 bytes collected)
So much for this preprocessors, so finally we have got it running but this happens to be very crude method and if we happen to be defining preprocessors on the go then we are doomed for it.
The better way to do it is using build.xml and antenna. I will be telling you about it in next post.
Subscribe to:
Posts (Atom)