text:
Antarctic sea ice set another record this past week, with the most amount of ice ever recorded on day 256 of the calendar year (September 12 of this leap year). Please, nobody tell the mainstream media or they might have to retract some stories and admit they are misrepresenting scientific data.
National Public Radio (NPR) published an article on its website last month claiming, "Ten years ago, a piece of ice the size of Rhode Island disintegrated and melted in the waters off Antarctica. Two other massive ice shelves along the Antarctic Peninsula had suffered similar fates a few years before. The events became poster children for the effects of global warming. … There's no question that unusually warm air triggered the final demise of these huge chunks of ice."
NPR failed to mention anywhere in its article that Antarctic sea ice has been growing since satellites first began measuring the ice 33 years ago and the sea ice has been above the 33-year average throughout 2012.
Indeed, none of the mainstream media are covering this important story. A Google News search of the terms Antarctic, sea ice and record turns up not a single article on the Antarctic sea ice record. Amusingly, page after page of Google News results for Antarctic sea ice record show links to news articles breathlessly spreading fear and warning of calamity because Arctic sea ice recently set a 33-year low.
Sea ice around one pole is shrinking while sea ice around another pole is growing. This sure sounds like a global warming crisis to me.
Update: To provide more perspective on global warming and Antarctica, I would like to update this column with some additional information:
As meteorologist Anthony Watts explains, new data show ice mass is accumulating on the Antarctic continent as well as in the ocean surrounding Antarctica. The new data contradict an assertion by global warming alarmists that the expanding Antarctic sea ice is coming at the expense of a decline in Antarctic continental ice.
The new data also add context to sensationalist media stories about declining ice in small portions of Antarctica, such as portions of West Antarctica and the Antarctic Peninsula (see here, for example). The mainstream media frequently publish stories focusing on ice loss in these two areas, yet the media stories rarely if ever mention that ice is accumulating over the larger area of East Antarctica and that the continent as a whole is gaining snow and ice mass.
Interestingly, a new NASA study finds Antarctica once supported vegetation similar to that of present-day Iceland.
"The southward movements of rain bands associated with a warmer climate in the high-latitude southern hemisphere made the margins of Antarctica less like a polar desert, and more like present-day Iceland," a co-author of the NASA study reports.


text:
Feb 16, 2016 | Carpet One Floor & Home
My clients love to travel through the European countryside, primarily Tuscany and Florence. They really wanted to have a bit of the old rustic feel reminiscent of kitchens they have seen throughout their travels; while still maintaining the modern, streamlined and functional aspects of today's kitchen spaces. They also entertain quite a lot, so it was extremely important to them that they have a space where friends can gather and enjoy a glass of wine while they prepare a meal.
Yes, we had a few challenges with this space, and went through several different designs before settling on this one. We were originally working with a narrow, long sub-division kitchen with an eat-in area. We were looking to remove the adjacent wall leading to their family room to create a large integrated kitchen and living space which would have been great for entertaining. However, we had a few structural and mechanical issues involved with the removal of that particular wall that made it not a feasible option for my clients within their given budget. Instead we decided to proceed with opening up that wall approximately 8' which gave a feel of a more open concept and integrated space, and allowed for the area we needed to design this wonderfully large center island that my clients really wanted. We also needed to ensure we had enough cabinetry and storage for our clients, which was tricky in this space as the remainder of the wall space to the right of microwave is all lost to windows and a walk-out.
I love to design kitchens, like bathrooms, they often go through such a dramatic change when renovated. I enjoy the challenge of creating a functional, timeless space for my clients. It's important for me when designing a kitchen that the space is efficient, comfortable and has a good flow. It should reflect current trends but not be exclusive to it. It's important to delivery on a client's "wish-list" however, it's equally important to have a clear understanding of their day to day needs and living style to ensure that the two work together well.
The floor is a great porcelain tile, 20" x 20" in size that amazingly resembles polished concrete. I loved the feel of texture and patina that it evokes, reminiscent of many of the old worn floors found in the European countryside. We had the tile installed with a seamless transition to the hardwood in the adjacent rooms. Personally, I prefer doing seamless floor transitions it's much more of a custom finish and also, when there is nothing interrupting the transition between two types of flooring it often can trick the eye in to feeling the space is larger.
The large island provides for them a great, uninterrupted work surface which was key. We relocated the plumbing, both the sink and dishwasher to the island, this allowed us to maximize the cabinetry on the wall, and also be able to have the space for a larger fridge. All the cabinets are outfitted with space saving storage solutions maximizing their efficiency. We were able to give them enough counter space between the fridge and slide-in range to allow for another workstation should they both be cooking together; and there's a comfortable amount of open space around the island for they both of them to be working at the same time, while still having guests sitting at the island.
I didn't want to design an all-white kitchen for this space, it's a very bright room with lots of natural light that can handle more color and texture. I wanted to design a space for my clients that incorporated that old "Tuscan" feel they were looking for. Many of these European kitchens have wonderfully eclectic pieces like old painted hutches, or an old painted farmhouse table with wood top. They sometimes have beautiful old hand-painted tiles, or vintage stone or brick walls. I wanted to design a space that incorporated these influences. The island was our primary focal point as it was designed as a space to gather around and socialize. That said, the deep charcoal color definitely made it stand out in this kitchen, and it complimented the walnut counter top and reclaimed brick backsplash beautifully.
The kitchen space has a great rustic vibe to it, but it still has a modern feel. I love the cantilevered walnut counter top on the island. The color blends well with the rest of the house and the fact that there are no legs at the island definitely makes for a more modern touch. The texture and old-world aspect of the floor and faux reclaimed brick back-splash add a nice charm to this kitchen.
There really isn't one specific thing. They love the walnut counter and the size of the island I've been told is perfect for entertaining, exactly what they wanted. The function of the kitchen has been wonderful for them as well, very easy for two cooks to work in here at the same time. And, I know they just love the tiles, both the floor and backsplash, the texture and vintage feel definitely evokes for them memories of the Tuscan countryside they loved so much.
Linda is a graduate of the University of Western Ontario, and started her entrepreneurial adventure in 1998. Pursuing design throughout her career in several different creative forms has given her a far-reaching knowledge and understanding of the field. Linda believes that good design should be timeless yet adapt to the needs of her clients. Her approach to design is a classic style blended with a bit of the unexpected, creating comfortable, functional and livable environments reflecting her client's own individuality and personality. She has a positive, caring energy that puts her clients at ease throughout the renovation process…whether the project is large or small, they know she truly cares and loves what she does. Linda has taken her passion for art and design and transformed it into the career it is today. In the media Linda contributes as an "Ask the Expert" designer at the National Home Show, and is a regular columnist in Condo Life Magazine, The Toronto Sun and various other publications. She supports various charities that are personal to her such as ALS, Sick Kids Hospital and The Canadian Red Cross. To learn more about Linda and view her design portfolio, please visit www.lindamazurdesign.com.

subset: commoncrawl


text:
In this section
Down syndrome
What are trisomies?
The term "trisomy" is used to describe the presence of three chromosomes, rather than the usual pair of chromosomes. For example, if a baby is born with three #21 chromosomes, rather than the usual pair, the baby would be said to have "trisomy 21". Trisomy 21 is also known as Down syndrome. Other examples of trisomy include trisomy 18 and trisomy 13. Again, trisomy 18 or trisomy 13 simply means there are three copies of the #18 chromosome (or of the #13 chromosome) present in each cell of the body, rather than the usual pair.
What is Down syndrome?
Down syndrome is a genetic disorder that includes a combination of birth defects, including some degree of intellectual disability, characteristic facial features and, often, heart defects, visual and hearing impairment, and other health problems. The severity of all of these problems varies greatly among affected individuals. Down syndrome is one of the most common genetic condition, affecting approximately one in 800 to 1,000 babies. In this country, there are approximately 350,000 individuals with Down syndrome, according to the National Down Syndrome Society. Life expectancy among adults with Down syndrome is about 55 years, though average life span varies.
The name "Down syndrome" comes from the physician, Dr. Langdon Down, who first described the collection of findings in 1866. It was not until 1959 that the cause of Down syndrome (the presence of an extra #21 chromosome) was identified.
What causes Down syndrome?
Normally in reproduction, the egg cell of the mother and the sperm cell of the father start out with the usual number of 46 chromosomes. The egg and sperm cells undergo cell division where the 46 chromosomes are divided in half and the egg and the sperm cells end up with 23 chromosomes each. When a sperm with 23 chromosomes fertilizes an egg with 23 chromosomes, the baby ends up with a complete set of 46 chromosomes, half from the father and half from the mother.
Sometimes, an error occurs when the 46 chromosomes are being divided in half and an egg or sperm cell keeps both copies of the #21 chromosome instead of just one copy. If this egg or sperm is fertilized, the baby ends up with three copies of the #21 chromosome and this is called "trisomy 21" or Down syndrome. The features of Down syndrome result from having an extra copy of chromosome 21 in every cell in the body.
Ninety-five percent of Down syndrome results from trisomy 21. Occasionally, the extra chromosome 21 is attached to another chromosome in the egg or sperm; this may result in what is called "translocation" Down syndrome (3 to 4 percent of cases). This is the only form of Down syndrome that can sometimes be inherited from a parent. Some parents have a rearrangement called a balanced translocation, where the #21 chromosome is attached to another chromosome, but it does not affect his/her health. Rarely, a form of Down syndrome called "mosaic" Down syndrome may occur when an error in cell division occurs after fertilization (1 to 2 percent of cases). These persons have some cells with an extra chromosome 21 and others with the normal number.
What does a child with Down syndrome look like?
A child with Down syndrome may have eyes that slant upward and small ears that may fold over slightly at the top. Their mouth may be small, making the tongue appear large. Their nose also may be small, with a flattened nasal bridge. Some babies with Down syndrome have short necks and small hands with short fingers. Rather than having three 'creases' in the palm of the hand, a child with Down syndrome usually has one single crease that goes straight across the palm, and a second crease that curves down by the thumb. The child or adult with Down syndrome is often short and has unusual looseness of the joints. Most children with Down syndrome will have some, but not all, of these features.
What types of problems do children with Down syndrome typically have?
- About 40 to 50 percent of babies with Down syndrome have heart defects. Some defects are minor and may be treated with medications, while others may require surgery. All babies with Down syndrome should be examined by a pediatric cardiologist, a physician who specializes in heart diseases of children, and have an echocardiogram (a procedure that evaluates the structure and function of the heart by using sound waves recorded on an electronic sensor that produce a moving picture of the heart and heart valves) in the first two months of life, so that any heart defects can be treated.
- About 10 percent of babies with Down syndrome are born with intestinal malformations that require surgery.
- More than 50 percent have some visual or hearing impairment. Common visual problems include crossed eyes, near- or farsightedness, and cataracts. Most visual problems can be improved with glasses, surgery, or other treatments. A pediatric ophthalmologist (a physician who specializes in comprehensive eye care and provides examinations, diagnosis, and treatment for a variety of eye disorders) should be consulted within the first year of life.
- Children with Down syndrome may have hearing loss due to fluid in the middle ear, a nerve defect, or both. All children with Down syndrome should have regular vision and hearing examinations so any problems can be treated before they hinder development of language and other skills.
- Children with Down syndrome are at increased risk of thyroid problems and leukemia. They also tend to have many colds, as well as bronchitis and pneumonia. Children with Down syndrome should receive regular medical care including childhood immunizations. The National Down Syndrome Congress publishes a "Preventative Medicine Checklist" which outlines which checkups and medical tests are recommended at various ages.
How serious is the intellectual disability that accompanies Down syndrome?
The degree of intellectual disability that accompanies Down syndrome varies widely, ranging from mild to moderate to severe. However, most intellectual disability falls within the mild to moderate range. Further, studies suggest that, with proper intervention, fewer than 10 percent will have severe intellectual disability. There is no way, however, to predict the mental development of a child with Down syndrome based on physical features.
What can a child with Down syndrome do?
Children with Down syndrome can usually do most things that any young child can do, such as walking, talking, dressing, and being toilet trained. However, they generally do these things later than other children. The exact age that these developmental milestones will be achieved cannot be predicted. However, early intervention programs, beginning in infancy, can help these children achieve their individual potential.
Can a child with Down syndrome go to school?
Yes. There are special programs beginning in the preschool years to help children with Down syndrome develop skills as fully as possible. Along with benefiting from early intervention and special education, many children can be integrated in the regular classroom, to some extent. The outlook for these children is far brighter than it once was. Many will learn to read and write and participate in diverse childhood activities both at school and in their neighborhoods. While there are special work programs designed for adults with Down syndrome, many people with the disorder can hold regular jobs. Today, an increasing number of adults with Down syndrome live semi-independently in community group homes where they take care of themselves, participate in household chores, develop friendships, partake in leisure activities, and work in their communities.
Can people with Down syndrome marry?
Some people with Down syndrome marry. Although there have been rare exceptions, men with Down syndrome cannot father a child. In any pregnancy, a woman with Down syndrome has a 50/50 chance of conceiving a child with Down syndrome, but many pregnancies are miscarried.
How is Down syndrome diagnosed?
Since Down syndrome is such a unique group of characteristics, physicians can sometimes determine simply by physical examination whether a baby has Down syndrome. To confirm the physical findings, a small blood sample can be taken and the chromosomes can be analyzed to determine the presence of an extra #21 chromosome. This information is important in determining the risk in future pregnancies. (Translocation Down syndrome and mosaic Down syndrome have different recurrence risks).
Chromosomal abnormalities such as Down syndrome can often be diagnosed before birth by analyzing cells in the amniotic fluid or from the placenta. Fetal ultrasound during pregnancy can also give information about the possibility of Down syndrome, but ultrasound is not 100 percent accurate, since many babies with Down syndrome may look the same on ultrasound as those without Down syndrome. A chromosome analysis, whether performed on a blood sample, cells from the amniotic fluid, or placenta, is over 99.9 percent accurate.
What are the maternal age risks for Down syndrome?
Maternal Age | Risk at Birth |
15 to 24 years | 1 out of 1300 |
25 to 29 years | 1 out of 1100 |
35 years | 1 out of 350 |
40 years | 1 out of 100 |
45 (and older) | 1 out of 25 |
What is the risk of parents of a child with Down syndrome having another child with Down syndrome?
In general, for women under 40 (after having one child with Down syndrome), the chance of having another baby with Down syndrome is 1 percent. The chance for Down syndrome is also known to increase with the mother's age and, after age 40, a mother would simply have the risk based on her age at delivery. It is important to know that about 75 percent of babies with Down syndrome are born to women under 35. This is due to the fact that women under 35 have more babies than women over 35. Your physician may refer you to a genetic physician or genetic counselor who can explain the results of chromosomal tests in detail, including what the recurrence risks may be in another pregnancy and what tests are available to diagnose chromosome problems before a baby is born.
Can Down syndrome be cured or prevented?
There is no cure for Down syndrome. We are not certain how to prevent the chromosomal error that causes Down Syndrome. To date, there is no reason to believe that a parent could have done anything to cause or prevent the birth of their baby with Down syndrome. However, a recent study suggests that some women who have had a baby with Down syndrome had an abnormality in how their bodies metabolize (process) the B vitamin folic acid. If confirmed, this finding may provide yet another reason why all women who might become pregnant should take a daily multivitamin containing 400 micrograms of folic acid (which has been shown to reduce the risk of certain birth defects of the brain and spinal cord).
Some claim that various high dose vitamins given to children with Down syndrome will improve the mental performance and lessen the intellectual disability. To date, however, there has not been a medical study to prove that this actually works. It is important for new families to talk to their physician, other families, and the National Down Syndrome Congress to learn what to expect with Down syndrome and to learn about things which may be helpful in raising a child with Down syndrome.
What research is being conducting on Down syndrome?
The March of Dimes is investigating why errors in chromosome division occur, in the hope of someday preventing Down syndrome and other birth defects caused by abnormalities in the number or structure of chromosomes. Other researchers are seeking to improve the outlook for children with Down syndrome. One example of this includes developing improved language intervention programs to help these children communicate more easily.
Where can families affected by Down syndrome get additional information?
There are organizations across the country that provide information and support for families with children affected by Down syndrome. Visit the Support Groups page of this Web for additional information.
Need assistance?
From out of town? The Access Center can provide assistance in coordinating appointments, insurance, etc. Use our online form or call: (414) 266-6300.


text:
Eli Has Two Rings, Peyton Has One; Time For Little 'Bro To Get More Respect?
After leading his New York Giants to a 21-17 victory over the New England Patriots last night, quarterback Eli Manning is now 2-0 in Super Bowl games.
That puts him ahead of older brother Peyton, who has taken the Indianapolis Colts to two Super Bowls and won one.
Injuries kept Peyton out of football this season and he may not be back. He's considered one of the best quarterbacks to ever play the game.
But now, Eli has one more Super Bowl ring than his brother and has been the MVP in both games he's played in. So it seems fair to ask whether it's time to talk about both Mannings as being among the best ever. Their career "quarterback ratings" aren't too close — 82.1 for Eli over eight seasons and 94.9 over 13 seasons for Peyton. But what do you think?
Meanwhile, the morning's other story line from the Super Bowl seems to be the fleeting finger of singer M.I.A. during the halftime show. We missed it, but she apparently flashed a middle digit as she performed during one of Madonna's songs. M.I.A. also may have added the F-word just to get her point across ("though it was hard to hear her clearly," The Associated Press says).
The NFL and NBC, which broadcast the game, are apologizing. A spokesman for the TV network says a system that should have digitally blurred the offending finger wasn't activated in time.


text:
ln A Global Economy, Why's It So Expensive To Transfer My Money?
When relocating to a new country, it's important to establish routines and traditions. My ritual here in London is spending an hour on the phone with the bank every day.
It's a strange thing about 2014 — we've got one collective foot planted squarely in the 21st century, while the other is stuck in back in the 19-something-or-others.
My email, Facebook, and Twitter accounts don't care whether I'm in Dublin or Dubai. I can jog along the Seine in Paris to the same music on Spotify that I listen to when I'm running along the Willamette River in Portland.
On WhatsApp, I send text messages to my friends every day at no cost, no matter where in the world I am. Skype is a snap. But banking is something else altogether. (Phone calls go in the same category as banking, but that's for another blog post.)
This is a universal experience, from what I can gather. Anyone living abroad wrestles with the arcane formulas and fees that go into converting an American salary to a British (or Brazilian, or Burmese) bank account.
Two weeks in London, and I've already found that American expats trade banking horror stories like crusty sailors comparing sharkbite scars.
My story, briefly, is this: In order to avoid a $35 Bank of America fee every time I move my paycheck to the United Kingdom, I devised a hopscotch as follows: Dollars leave Bank of America to an international transfer company. That company hands off the money to a Lloyds Bank International account. Lloyds International plops it into an account with UK Lloyds. Hardly simple, but at least the plan comes with no fees. Guaranteed.
The first transfer took three days longer than planned, and arrived with $600 less than the amount that left the U.S.
Related NPR Stories
Bank of America and Lloyds had changed the money from dollars, to pounds, to dollars again, all at unfavorable exchange rates. Lloyds pointed the finger at Bank of America. Bank of America pointed the finger at Lloyds.
When I started tweeting about my experience here in London, @MatthewWells replied, "Welcome to the shady world of international transfer."
@BetBrod called my (ahem) "Twitter meltdown...heartbreaking and probably all too familiar if you've ever moved abroad."
It all feels strangely anachronistic in this global economy. My NPR colleagues at Planet Money recently executed an eye-popping journalistic project, tracking the life of a T-shirt through the global marketplace from cotton to completion.
They crowd-sourced the funding and sent a shirt to anyone who donated enough money. The global machine in action, right? Well, almost.
The other day I was interviewing a man named Laurie Young on a street in London for this story on British telephone boxes. He enthusiastically told me about purchasing a Planet Money T-shirt online. But when it showed up at his door, it came with an import tax bill for 30 pounds. That's more than $45.
The Euro was supposed to solve this problem for most Europeans, at least. But Britain never joined the currency club. And now the U.K. is talking about pulling out of the European Union altogether. It seems there's not much hope for banking to join the modern age during my London tenure.
As for me, I'm $600 poorer but not necessarily $600 wiser. I'm about to have dinner with some American expats. I'm going to ask them to show me their banking scars. And then try to learn their tricks on how to avoid sky-high fees.
If you have any tips, let me know.


text:
You are here
Boating Safety for Little Kids
Boating Safety for Little Kids
Spending time with family and friends on a river, lake, or marina is a favorite summer activity. Follows these precautions to help children and adults boat safely.
Top Safety Tips
- Always have your children wear a U.S. Coast Guard-approved personal flotation device (PFD) while on boats, around open bodies of water or participating in water sports. Here's some more information on how to choose the right PFD.
- Remember that things such as water wings, noodles and other swimming aids are fun toys for kids, but they should never be used in place of approved PFDs.
- Explain some basic boat rules and have everyone follow them. Children need to understand and follow rules such as keeping their hands and feet inside the boat at all times and not running on a boat.
- Every child is different, so enroll children in swimming lessons when you feel they are ready.


text:
ALEXIS LLC ("Alexis", "we", "us" or "our") share your concern about the protection of your personal information online. This privacy policy ("Policy") is our policy that addresses how we maintain the privacy of personal information we collect online in connection with the Alexis website located at www.shop-alexis.com (the "Site").
This Policy describes our privacy practices and sets out your obligations and ours with respect to your use of the Site. This Policy applies only to the Site and does not necessarily apply to our off-line collection of information. By visiting the Site, you agree to abide by the terms of this Policy and the [terms of use] (the "Terms of Use").
We may need to change this Policy from time to time in order to address new issues and to reflect changes on the Site or in the law. We reserve the right to revise or make any changes to this Policy, and your continual use of the Site subsequent to any changes to this Policy will mean that you accept such changes. Therefore, please bookmark this page and review it periodically to assure familiarity with the most current version of this Policy. We will post all changes to this Policy on the Site so that you will always know what information we gather, how we might use that information, and when and how we will disclose that information. You can tell that this Policy has been updated by checking the last revised date posted on the top of this page. If due to such changes, you decide that you want to remove any portion of your personal information from our database, please notify us at email@example.com.
Information We Collect and Track.
Alexis collects and retains two types of information about Site visitors: (i) personal information that individual visitors provide when interacting on the Site, or voluntarily provide on certain other occasions (such as via forms or in emails); and (ii) tracking data, which is automatically collected from every Site visitor and recorded on our log files, (collectively, "Information"). The Information that we gather may include your name, title and address, telephone number, email address, birth date and credit card number as well as other elements of personal information.
In addition, if you contact us, we may keep a record of your correspondence, including any Information contained therein.
You may decline to provide any personal information, but please realize that you thereby may be unable to register on the Site or to participate in activities or services offered by Alexis on the Site.
The tracking data we record includes, without limitation, information regarding the number and frequency of visits to the Site, the items you viewed and/or purchased, the websites that you access before and after you visit the Site, the software used to access the Site, and your IP address and Internet service provider related information. The tracking data we record may include the location of your computer.
How We Use Your Information.
The Information that we collect and that you provide to us is used for our business purposes and the purpose for which you provided it, including, without limitation, to respond to your requests or correspondence. Alexis may also use the Information to contact you about the Site or to request your input regarding ways in which we might improve the Site. We may also use your Information to inform you about Alexis' activities, promotions, products, services and events in which Alexis thinks you may be interested. The Information may also be analyzed so that we can provide you with useful information and can serve you in the best manner possible through enhanced features and functions on the Site.
We will not disclose any personal information to third parties, except (i) to parties who perform a service for us, such as sending you mail or email, web hosting, credit card processing and other similar services; (ii) when we believe that such disclosure is required by law; (iii) to enforce this Policy or the Terms of Use; (iv) to protect the rights, property, security or safety of Alexis, Site users or the public; (v) to respond to an emergency; or (vi) as otherwise stated in this Policy. In addition, we may disclose Information to certain third parties if you have requested or authorized the disclosure of such Information.
We provide certain Information to third party service providers who perform specific functions on our behalf.
For example, we may share your mailing address and other contact information with our delivery partners, and certain of our service providers (i.e., web hosting, credit card processing, catalog management and others) may have access to all or parts of the Information we maintain. All such Information provided to third parties is limited to the Information needed to perform their functions. We seek to limit third-party use of Information; however, we are not responsible for such third-party use of Information that is not in compliance with this Policy.
Alexis may make certain Information, including, without limitation, your name address and email address, available to its affiliates and related companies. Our affiliates and related companies may contact you directly regarding certain promotions. This information is never sold, and if you would like to opt out of having Alexis share your name, title address and email address with its affiliates and related companies, please contact our Customer Service Department.
Alexis may use certain tracking data.
Tracking data information may be used for a variety of purposes, including but without limitation, to compile statistical, demographic or aggregated information about visitors to the Site generally, or for load balancing metrics and also may be used to create reports on user demographics and the traffic patterns of the Site. The reports that are generated from tracking data are used for a variety of purposes, including, for example, to improve the Site and our services.
User Postings.
You should be aware that any content posted by you to the Site may be read, collected or used by other Site visitors. Alexis is not responsible for the third-party use of any Information provided in such manner. By participating in the use of Site, you consent to Alexis' use or disclosure of any content that you submit.
Use of Cookies.
We use cookies to enhance your experience while using the Site. "Cookies" are small pieces of information that a website transfers to your computer's hard drive for record-keeping purposes. The use of cookies makes web surfing easier by performing certain functions such as saving your passwords and your personal preferences in connection with your use of a particular website. Many consider the use of cookies to be an industry standard. Your browser is probably set to accept cookies, but you are always free to decline our cookies if your browser permits. If you choose to have your browser refuse cookies, it is possible that some of the Services provided on the Site will not function properly.
Transfer of Information to Third Parties Upon a Sale or Change of Control.
We retain the right to transfer or assign all Information pursuant to a merger, sale, reorganization, purchase or other transaction relating to Alexis, its related companies or their assets if the assignee or purchaser agrees to abide by the terms of this Policy.
How Your Information Is Protected.
We take reasonable precautions to protect your Information from loss, misuse or alteration. We maintain reasonable physical, electronic and procedural safeguards for your Information. You should recognize, however, that there is no such thing as "perfect security" on the Internet, and we cannot guarantee the security of your Information. In addition, because Internet communication is unsecure, it is also possible that the information you supply to us or your access of any information via the Site will be intercepted during transmission. We are not liable for any breach of our systems or interception of our transmission, and we hereby disclaim, to the fullest extent provided under law, any liability associated with any claim relating to a breach of security, data or information.
Other Communications.
From time to time, we may email users of the Site information regarding marketing events or other developments at Alexis. We may also email users on occasion regarding the Site. Such emails may be sent to users of the Site even if they have not requested to receive any communication from us.
If a user elects to use our referral service to inform another person about the Site or Site features, we may request the name and email address of such other person. Alexis will automatically send a one-time email inviting such other person to visit the Site or to purchase items from Alexis. Alexis stores this information for the sole purpose of sending this one-time email.
Links to Third-Party Sites.
The Site may contain links to websites owned and operated by other parties. We are not responsible for and have no control over the privacy policies of those sites. We encourage you to review the privacy policies of those sites prior to providing them with any information.
Children Under the Age of 13.
Alexis is concerned about the privacy protection of children who access the Internet, and we comply with the Children's Online Privacy Protection Act (COPPA). Accordingly, the Site is not intended for use by anyone under the age of 13 without the supervision of a parent or guardian, and we do not knowingly collect Information from anyone under 13 years of age without the consent of a parent or guardian. If you are under the age of 13, please do not submit any personal information to us, you may rely on your parent or guardian to assist you.
Compliance With Laws. We reserve the right to disclose any Information to comply with any law, regulation, decree, judgment, order, subpoena or any other governmental order ("Order") without any obligation to contest or verify the accuracy of such Order.
Applicable Law. This Policy will be governed by and construed in accordance with the laws of the State of Florida, without regard to any principles of conflicts of law. You agree that any action at law or in equity that arises out of or relates to any use of the Site will be filed only in the state or federal courts located in Miami-Dade County, and you hereby consent and submit to the personal jurisdiction of such courts for the purposes of litigating any such action.
How You Can Update or Correct Your Information and Contact the Site. Please contact us via our Customer Service Department if you have any questions or concerns regarding the Site, this Policy or if you would like to update or correct you Information.


text:
Build a MacOSX Universal Hugin bundle with Xcode
The "normal" way of compiling Hugin is via Cmake. With the current versions of MacPorts, Fink and Cmake it is very difficult to make a universal bundle due to the way endianness is dealt with in MacPorts and Fink. This HowTo explains how to make a universal bundle with Xcode.
The creation of a bundle is actually a two step process:
- Build all libraries and binaries which Hugin depends on. This is done outside Xcode. From here on we will call these libraries and binaries "External Programs". To compile and build all "External Programs" as universal, we will follow a different process compared to the normal "straight-forward" process of building libraries with MacPorts or Finks as described in Hugin Compiling OSX. We do not need nor use MacPorts and/or Fink. Some may even prefer to put them "out of the way" in order to make sure we will not link with the libraries they provide. However, they provide convenient ways to install a few of the tools that we require in the later process and they should not be moved out of the way if they are where cmake is installed on your system. Some of the external package build scripts rely on cmake.
- Build Hugin and it's "internal" tools in Xcode and create the bundle. As the title suggests: This is done in Xcode.
Note: This Howto does not explain how to build a Hugin the "cmake way". Follow the Howto Hugin Compiling OSX.
You should have Mac OS X 10.4 or above. Older systems are not recommended and how to build on those systems will not be included in this document.
Download and install XCode
Download and install the latest version of XCode Tools for your Mac OS X: Xcode 2.5.x for Mac OS X 10.4 (Tiger), Xcode 3.1.x for 10.5 (Leopard) and XCode 3.2.x for 10.6 (Snow Leopard). We do not support 10.3.9 any longer. You need to register as a developer to be able to download XCode, but it is free and you will not be bugged by all kind of mails (unless you choose to receive them).
Subversion (SVN)
Leopard comes with SVN installed. The version is way too old though. This means that you need to install it yourself. The simplest way to get SVN is to use MacPorts or Fink. If you are on Tiger, you need to install it anyway. The simplest way to get SVN is to use MacPorts or Fink.
If you fancy a nice GUI you can download the Open-Source SVNX. You still need svn installed as it is only a graphical shell and I won't explain SVNX here (I only used it once, I still prefer the terminal).
You may also find SCPlugin handy for some quick operations.
Preparations for building the "External Programs"
Building the necessary "External Programs" (the libraries and binaries Hugin depends on) is completely scripted. This part describes not how to use "./configure" or "make; make install". It will explain (advise) how and where to create the necessary directory structure, configure the base environment script and, more or less, tell you in which order to run the package build scripts.
Installing Necessary Tools
Before start, we need to install couple of tools used in the process:
- Subversion
- GNU gettext
- cmake
You may use either binary distributions like MacPorts and Fink. You can also download the official version and manually compile and install ("./configure; make; sudo make install"). Note though that in that case you need to take yourself of all dependencies.
You first need to Install Macports (if you did not already do so) as described in Hugin Compiling OSX. Then you need to install:
$ sudo port install subversion gettext mercurial
If you use Fink:
$ sudo apt-get install svn gettext mercurial-py25
Note: mercurial is in the Fink "unstable" Source distribution. Set Fink to look for distributions in the unstable list. As of this writing there are three mercurial listings: mercurial-py24, mercurial-py25 and mercurial-py26. Py25 is presumably for python 2.5. The command python -V reports what python version is currently installed.
Start a fresh Terminal session before proceeding to the next steps. Otherwise the hg command may not be recognized.
Get Hugin from the Mercurial repository
For these instructions you need a folder named "development" residing at /Users/<your_username>. Create this folder in lowercase with the Finder if you do not already have it. This folder starts the path for what is called the development tree herein.
Tip: In subsequent instructions you will be entering folder path names and file names at the Terminal prompt. Instead of manually typing these in you can have Terminal provide the text for you by dragging the folder or filename item from an open Finder window into the Terminal window. When you do this Terminal deposits the name of the folder or filename you are dragging to the location you drop it in Terminal. For example in the following instructions you are to enter "cd development". Type in "cd " and then drag the development folder into the Terminal window to finish entering the text. You will find this technique is extremely convenient for the more involved path and file names.
Cd into your development tree and download hugin from the Mercurial hg repository like:
$ cd ~ $ cd development $ hg clone http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin hugin
Inside /Users/<your_username>/development, you will now have a directory hugin. The full path to your "External Programs" development tree will be /Users/<your_username>/development/hugin/mac/ExternalPrograms.
On subsequent retrievals from the Mercurial repository you simply cd into the hugin development directory on your mac and you issue the following two commands:
hg pull hg update
Location of the "External Programs" development tree
This part describes where we want to place the development tree for our "External Programs" that hugin depends on. Although the "External Programs" directory structure is placed inside the Hugin tree by default, this does not necessarily need to be in the same place as the Hugin source itself. The easiest way to place those files in custom places is to put symbolic link in the default place.
The first question is: where do you want to have your development tree? As you (might) know, the "normal" location is /usr/local, and MacPorts uses /opt/local by default and Fink, /sw. We do not want to use these locations!
Apart from the fact that it is a bad idea to mix up development trees, another drawback is that these directories are not in "user space", therefore always requiring a root authorization, e.g. "sudo make install" as a last step. When keeping the development tree in user space (e.g. /Users/<your_username>/development/ or /Users/Shared/development/), you don't need to "sudo". Note that the latter option also creates a development directory but keeps it away from your "normal" user data.
So, from this moment "we" have decided to build our development tree in user space.
Note: As mentioned before: If you position your development tree outside user space, you need to run everything as root user. The scripts are not tailored towards that "sudo" kind of use and need modification to work that way.
Inside hugin tree
The "External Programs" development tree is placed inside the hugin tree when you download Hugin. After you downloaded Hugin from Mercurial, you will find inside the hugin directory the following directory structure:
- /...other directories inside hugin
- /mac
- /Documents
- /ExternalPrograms
- /scripts
- /<more files inside mac>
- /...other directories inside hugin
Say you have downloaded hugin in /Users/<your_username>/development (Remember that "we" decided to keep it in user space?), than your "External Programs" build tree will be inside /Users/<your_username>/development/hugin/hugin/mac/ExternalPrograms/.
Note: You will also find a mac directory inside the platforms directory. This hugin/platforms/mac/ directory is not meant for compiling cross-platform tools, but for hosting platform specific tools like Erik Krause's droplet scripts, which you will find in platforms/windows.
Outside Hugin tree
Based on what I explained above you could also decide to place your build tree for the "External Programs" outside the hugin tree. An option might be /Users/<your_username>/development/ExternalPrograms/.
Pro's and Cons of "outside" Hugin tree
- You have your "External Programs" build tree separate from the hugin source. You can delete and recreate the Hugin directory anyway and anytime you want without touching your carefully built "External Programs".
- If you plan to build more universal software using this approach, you can share this directory (or just as well build another one).
- Many of the default paths assume the "inside" approach; you will have to map some of the directories with symbolic link.
Creation of the "External Programs" development tree
"Inside" approach
If you leave the "External Programs" development tree inside the Hugin SVN tree, you don't have to do anything and for simplicity this HowTo focuses on that way of working.
"Outside" approach
If you want to create it outside the hugin tree, I advise you to first create a development directory inside your home directory and then create the ExternalPrograms directory inside that development directory. Currently some part of hugin's Xcode project assumes the "binary repository" (explained below) is located at mac/ExternalPrograms/repository, inside the same directory as the source code you have downloaded with Mercurial's hg.
The recommended for "outside" approach is to:
- make your "External Programs" directory
- place symbolic link to the "binary repository" directory in your "External Programs" directory at /<path_to_hugin_source>/mac/ExternalPrograms/repository
- optionally place symbolic link to /<path_to_hugin_source>/mac/ExternalPrograms/scripts in your "External Programs" directory
$ myPathToHuginSource="/Users/<your_username>/development/hugin/hugin-hg" $ myExternalProgramsDir="/Users/<your_username>/development/hugin/ExternalPrograms" $ mkdir -p "$myExternalProgramsDir" $ mkdir -p "$myExternalProgramsDir/Repository-dynamic" $ ln -s "$myExternalProgramsDir/Repository-dynamic" "$myPathToHuginSource/mac/ExternalPrograms/repository" $ ln -s "$myPathToHuginSource/mac/ExternalPrograms/scripts" "$myExternalProgramsDir/scripts"
Building the "External Programs"
Prepare the build environment
Our build environment uses a lot of preset environment variables. The template of those variables can be found inside hugin/mac/ExternalPrograms/scripts, named "SetEnv-universal.txt" and "SetEnv-leopard.txt". SetEnv-universal.txt is for conventional 2-way universal binary, and SetEnv-leopard.txt is for 4-way universal binary with 64bit computing support. We take SetEnv-universal.txt in this document. Read #32bit versus 64bit for more info.
First, you should copy either of those files and name it "SetEnv.txt". In the top of this new file you will find the following two lines:
# has to be the absolute path from / myREPOSITORYDIR="/PATH2HUGIN/mac/ExternalPrograms/repository";
The path in the myREPOSITORYDIR variable needs to exactly match the path you use. This example show the (current) default one from the SVN. So, if you are Spiderman and you build inside your HOME directory you need to specify:
Check it, and check it again !!
You do not need to modify anything below this line, unless you cannot resist to customise something for yourself.
External Programs
The list of programs and their versions that you should compile are given in the hugin/mac/ExternalPrograms/readme.txt. Some libraries are recommended not to be compiled as dynamically linked library, but as statically linked library instead. The scripts for static build are found in hugin/mac/ExternalPrograms/scripts/static/.
Note: There is a good chance those build scripts not on the list are outdated and do not work.
Build the "External Programs"
Building the necessary libraries and binaries which Hugin depends on, the so called "External Programs" is now relatively easy.
- You cd into your ExternalPrograms subdirectory, like
cd /<path_to>/ExternalPrograms
- As mentioned in #Prepare the build environment we need to set our build environment before we can start compiling our libraries and binaries. This only needs to be done once at the start of the build process, so now would be a good time to do it:
$ source scripts/SetEnv.txt
Note: The above command does not work in the tcsh shell. Prior to entering the above source command switch to the bash shell first with the following:
$ bash
You may enter this following command to verify that SetEnv properly set myREPOSITORYDIR.
$ echo $myREPOSITORYDIR
- Download the necessary source packages (Google for them, copy them from your MacPorts and/or Fink base if available). The readme.txt in the ExternalPrograms directory lists the ones you need.
However, it's also a good idea to look at the corresponding script to verify the version number, as the scripts tend to be updated more often then the documentation. For example: The readme.txt might list Boost (1.39) when in fact the boost.sh script might have a line BOOST_VER="1_40" that causes the script to look for boost related file names with 1_40 instead of 1_39. Therefore you should be downloading boost version 1.40. As a general rule, check the scripts if you see if they indicate a more recent version to use than what is listed in the readme.txt file. The opposite is now true. The readme.txt currently (6/26/10) lists boost version 1.41.
- untar/unbzip2 the source packages. It's best to do this in the ExternalPrograms directory so that you will have all kind of subdirectories containing the source, like jpeg-6b, tiff-3.8.2, enblend, wxMac-2.8.7 and so on. Perhaps the easiest way to unpack the sources is to double click on the source packages in a Finder window. They can also be unpacked within the Terminal window:
As an example for libpng:
$ bunzip2 libpng-1.2.24.tar.bz2 $ tar -xvf libpng-1.2.24.tar
- Build and install the source package. The basic recipe is this:
$ cd <source code directory> $ sh ../scripts[/static]/<script_name>.sh $ cd ..
Here's what that looks like for libpng:
$ cd libpng-1.2.24 $ sh ../scripts/libpng.sh $ cd ..
- A recent addition to the project is a script named build-all.sh. This script has all the commands needed to build all of the tools. This script is highly recommended. Edit the script prior to using it to make sure it points to the correct external source folder names that you are using and to make sure it points to the scripts folder. Spiderman would edit the cd line in his version of build-all.sh to be: cd /Users/Spiderman/development/hugin/mac/ExternalPrograms/scripts
- The build-all.sh script writes a "<<<< building xxxxxxx >>>>>" line prior to starting each package build script. If you use Terminal, when this script is running or after the script has finished you can search (Edit Find) for the text "< building". This takes you to the beginning of each build process where you can see any errors that have occurred at the end of the prior build script or see any errors at the start of the next build. These two locations are the most likely spots where you can see that something that has gone wrong. You can keep a second copy of build-all.sh, renamed to build-user.sh, where you comment out all but the one package you may need to rebuild. So if a package does not build for some error like the version number is wrong, and you spot it soon enough, you can start a second Terminal session and run the specific build-user.sh for that package while the other build-all is still running on the other packages.
- After building all the tools, you need to download the Perl module Image-ExifTool-7.96 (source version), and extract the archive in the ExternalTools directory. Nothing else needs to be done for this program.
Tip: Maintain a folder outside of your development tree to stash the compressed external source packages you downloaded in case you need to start over with one of these. When necessary, rename the compressed file according to the package name and version.
Note: cmake is required for at least two of the packages, autopano and pano. Your system has to be able to find cmake. If it is at /opt/local/bin or /sw/bin then do not move those folders prior to building. Verify cmake's availability by entering "cmake -version" in the Terminal. You will be up the creek without a paddle if you do not get a cmake version response.
Order of building the "External Programs"
Some libraries and programs are dependent on other libraries. This means that these libraries need to be built first. As a rule of thumb, build your libraries in the following order (shell script names):
boost.sh, libexpat.sh, libiconv,sh, gettext.sh, libjpeg.sh, libpng.sh, libtiff.sh, wxmac28.sh, ilmbase.sh, openexr16.sh, pano13.sh, static/libexiv2.sh, lcms.sh, static/libxmi.sh, static/libglew.sh
And for the executables:
gnumake.sh, enblend31.sh, autopano-sift-C.sh, panomatic.sh
Note: You need to examine the scripts before executing them as some script use major and minor library numbers. These numbers are set from the script and need to be changed if your library version changes. For example libpng.sh contains a version number that may to be corrected.
Note 2: There is a build_all.sh script. This script will build all libaries and binaries and it will do that in the correct order. Please do check the versions of the source as they will relate to the folder names used in the script.
Cleaning up
Apart from the wxmac (wxwindows) source tree, you can remove every library source tree if you want to.
The wxmac source tree is necessary for the Xcode project. Xcode needs the "localization" source files.
When you are finished building you can also reinstate the Macports or Fink directories you had disabled (see #Get MacPorts and/or Fink out of the way).
Xcode compiling Hugin
First, you should edit the configuration file. Duplicate BuildConfig.xcconfig.orig and name the new copy "BuildConfig.xcconfig".
Inside, you will find variables that needs be matched with your External Programs configuration. Please edit at least the following variables accordingly:
If you have chosen to compile 4-way universal binary with 64bit support, uncomment RELEASE_ARCHS_64 line.
XCode basic walk-through
Note: This walk-through is base on XCode 2.4.x/2.5.x. The 3.x version has changed but in general this walk-through is still valid.
This HowTo will not discuss how to use Xcode. It will only explain some very basic steps to get you going. The rest is up to you (Xcode - the Final Frontier...............To boldly go where no man has gone before.) Sometimes small changes need to be made to the Xcode project due to added tools (matchpoint recently) or added or removed source files. These kind of actions will not be explained either in this HowTo.
When you double-click the hugin.xcodeproj, Xcode will start and show you the following screen:
In the Top section you see the Menu/Toolbar.
On the left side you see the navigation panel.
On the right side you see the File section.
In the left Navigation panel you see little triangles in front of the icons and their descriptions. These triangles can be used to open or close the sub-sections. Double-clicking the icons has another function and will bring you to the properties of that subsection. If you click the little triangle in front of Hugin, you see the directory structure of the files the Hugin project uses. Please note that this is not a real representation of the hugin directory but a user-created representation. Note however that the "files" in here are actually links to your real files. If you double-click them, the Xcode editor will open them for editing and save them back to the file system. | |
Below the Hugin icon/description, you'll find the Targets section. Here you need to define what needs to be compiled, linked, copied and so on to create a binary or library, or a bundle containing these binaries and libraries. In case of a complex build project like Hugin, you first need to compile underlying tools and libraries, than build hugin and link hugin against these underlying tools and libraries, and finally create the bundle including "some copy work" to get the "External Programs" like the PT* tools, enblend, enfuse, align_image_stack and the like inside the bundle. |
Other options in the Navigation panel are not relevant or interesting, although you might see the error panel quite frequently in your early attempts.
Checking Project Info
Double-click the blue icon before Hugin in the top-left corner of the Navigation pane. If you do this, the following screen will open.
This "General" tab defines the location where your Hugin.app, and the intermediate files, will be built. By default a build directory will be created in the same directory where your Hugin.xcodeproj resides. Changing this value is not recommended.
You can use Subversion with Xcode. It is a very handy feature to use in order to keep the files up-to-date and, especially with Xcode 3's improved Subversion integration, to commit changes back to repository. Follow the configuration of "SCM System".
The second tab is the "Build" tab (see below).
This is the list of master configuration of the project. The values that you have set in BuildConfig.xcconfig (above) are reflected, and referenced by other settings. All relative paths are relative to the location of the hugin.xcodeproj directory structure. You should not need to change anything, but do check. Please note some of the settings are different among "Configuration", e.g. Release, Debug, Development, etc. but paths should not be different among them.
The other tabs are not relevant, but feel free to expand your knowledge.
Compile and build our Hugin.app
Set the "Active Target" to "configure" and "Active Build Configuration" to "Release". Now click the "Build" icon. This will only take a few seconds or less. Please run this target for 2 to 3 times as it sometimes updates Xcode project setting itself and the updated variables are only used in the following execution.
In the status bar you will see the message concerning this step. It should say "Build succeeded" on the left and "Succeeded" on the right.
If this is the status message, you can really start building your Hugin.app.
This build target updates the pre-release version tags, and is not propagated (does not automatically run) from other targets. You should run this target after every SVN update. Also, before compiling anything that you give away to other people, make sure that you "Clean all targets" and then build this "configure" target first.
Building Apps
Set the "Active Target" to "Apps" and click "Build". Now this will take a very long time as it will build everything including Hugin.app.
Tips: If you have multiple Mac OS X machines, you may be able to distribute the compilation over multiple machines on the same network. Install Xcode Tools on all machines and check out the Preferences of Xcode, under "Distributed Builds".
If everything compiles and builds correctly, you will finally get a status message like:
Note that the build may have succeeded even though you see some error messages (in this screen dump). Double-click the "error" icon to display the errors.
If you did stick to all the "default settings", you will find your Hugin.app inside ../mac/build/Release among lots and lots of other files. All these other (intermediate build) files are not relevant. If built correctly, the Hugin.app is a completely portable application and everything is inside Hugin.app.
Testing Hugin.app
Now you need to test run your bundle. The first test is to see whether your application runs at all. Quick test can be done by "Run" (Cmd-R) within Xcode. If Hugin launches, it's a party time!!! So, go party and when you're finished come back for the next test.
"Run"ing in Xcode is useful for debugging with Xcode, but unfortunately using external executable within Hugin confuses the GDB and Xcode, so you cannot stitch or run autopano programs this way. If Hugin.app launches finely from Xcode, get to Finder and double-click the Huing.app icon and try to make a panorama. If that works fine, go for another glass of wine.
Now that you managed to get a working Hugin.app via Xcode we need to check if it is really a portable application. If you were completely successful in building your Hugin.app, than all binaries, tools and libraries should be "inside" the bundle and should know "how to find each other". The best way to test this is to copy the Hugin.app to another Mac and run Hugin.app there.
As this is not always possible, You could follow the following dirty technique:
Warning: This is not exactly a safe operation. Do at your own risk.
- Copy your Hugin.app to another location on your mac and rename
- your mac directory inside your hugin source directory to mac.org,
- your /opt/local to /opt/local.org (in case you have Macports),
- your /sw directory to /sw.org (in case you have Fink),
- your usr/local directory to /usr/local.org
(You can off course rename your directories to anything you like).
Renaming your directories will prevent Hugin from trying to link to the libraries inside these directories. If Hugin does it will crash and show an error message that Hugin tried to link to <path to>/ExternalPrograms/repository/lib/<some library> instead of the bundle library (or even worse for example to /opt/local/lib/<some library>, which means that you did not correctly #Get MacPorts and/or Fink out of the way).
The Complete-bundle.sh script mentioned in #Edit Complete-bundle.sh will alter the library paths inside Hugin and inside the libraries to "internal" paths relative to the executable location, using the install_name_tool, to make sure that they can find each other inside the bundle. If this did not work correctly (one of the non-fatal errors for Xcode), your Hugin.app will not run on another system as it will still try to use the libraries inside your build environment. This build environment is not available on another "Xcode and Hugin free" Mac.
To see errors directly you can start Hugin.app from the command line, e.g. from a terminal:
$ Hugin.app/Contents/MacOS/Hugin &
Alternatively you can double-click Hugin.app from Finder while following the (error) messages on /Applicatons/Utilities/Console.app.
Next to this you should check the logs (in case of crashes that is). You will find these in /Users/<user name>/Library/Logs/CrashReporter/. If "things" go wrong you can find there logs like Hugin.crash.log. These logs are not recreated but new error reports are just added to the log, making them bigger and bigger (But off course you won't run into errors). The same crash logs may be displayed by the CrashReporter immediately after Hugin crashes. You can configure the CrashReporter's behaviour with /Developer/Applications/Utilities/CrashReporterPrefs.app.
If everything worked fine you really made a portable application. Congratulations!
Have a big celebration and have a happy hacking Hugin time!
32bit versus 64bit
Tiger (Xcode 2.4) enables you to build universal binaries and libraries for PPC and i386. Leopard and Snow Leopard (XCode 3.x) enable you to build universal binaries for PPC and i386, but also for PPC64 and x86_64. If you want to do this, you should refer to SetEnv-leopard.txt. At this moment this is "experimental" as:
- some "Linux derived" libraries and binaries may not work properly.
- they are not well optimized for Core 2 processors.
- most users do not benefit from 64bit because it is required only when making a huge panorama (>2GB).
- 64bit part is only for (Snow) Leopard users on 64bit hardware (G5, Xeon, or Core 2). Those platforms can run 32bit anyway.
- almost doubles the binary size. The 2-part universal version alone weighs more than 100MB.
Use at your own risk.
Command line building with Xcode
Xcode has also a command line version named xcodebuild. If you prefer the command line than this tool is nice. You miss the nice integrated editor off course, so you need vi or pico (or some other editor) to change source code. (I use it for for remote ssh builds using vi as code editor).
Say you want to use (or experiment) with the command line builder, you need to cd into the mac directory and issue the following commands:
$ cd <path_to>/hugin/mac $ xcodebuild -project Hugin.xcodeproj -alltargets -configuration Release
Note: Even if you run the build from the command line, the complete environment will be opened. When finished, it will close again.
If you want more info just issue a xcodebuild --help for short help or a man xcodebuild for more extensive help. And you can read the docu/helpfiles from inside Xcode.
If you want to make automated nightly builds of Hugin you can easily script that with the command line version (svn refresh, command line build, command line creation of the dmg, ftp to website). You could even issue the svn, dmg creation and ftp commands from the Xcode project which means that you only have to script the xcodebuild.
Statically linked command-line tools
There are some command line tools in Hugin package and related tool chain that users would want to use independently of Hugin.app. The best way to make those command line tools is to build them statically linked of all non-standard libraries.
You need to (that's a lie, but let me simplify) compile another binary depository with this time compiling the second list in ExternalPrograms/readme.txt. If you have taken the 'outside' approach, you can just make another repository and proceed the next step. If not, the right location to have your repository will be given in the next step. That's all for tools that are built in External Programs manner including enblend and autopano-sift-c.
For Xcode, the trick is to make another folder that parallels mac/ in the Hugin source:
- Make a new folder next to mac/ and name it "mac-static".
- Copy BuildConfig.xcconfig, Version.xcconfig, and Hugin.xcodeproj files to the new folder.
- Make a new folder in mac-static/ named "ExternalPrograms".
- Either make the static repository here, or place a symbolic link named "repository" to the outside one.
- Edit BuildConfig.xcconfig and update the REPOSITORY_ABSOLUTE_PATH variable.
Now you are ready for Xcode. Just get the Hugin.xcodeproj open, run the 'configure' build target as usual, select the 'static tools' target or any specific 'static' tools, and build. You are done. If you check the compiled executable file with 'otool -L ', you should see only the libraries in standard OS X installation (that is, usually, ones in '/usr/lib').
External Links
- What is endianness.
- MacPorts set endianness read-only for the platform it's installed on.
- MacOSX online Darwin man pages from the HMUG user group.
- Cross-Development Programming Guide and Universal Binary Programming Guidelines, Second Edition– more about building fully compatible universal binaries on OS X


text: Demian Maia Science of Jiu-Jitsu Instructional DVD's Demian Maia is well known and respected in the Brazilian Jiu-Jitsu and Submission Grappling world and is now quickly rising the ranks of mixed martial arts due to his incredible skill set and technique. A 2007 ADDC 77 - 87KG weight division Champion as well as holding numerous world and grappling titles, Demian Maia is now one of the UFC's hottest new stars. Demian teaches an incredibly evolving Jiu-Jitsu that's beyond anything you've ever seen. Check out his Series below where you can view the full series information and download free video clips! |


text:
Internal functions are functions written in C that have been statically linked into the PostgreSQL server. The "body" of the function definition specifies the C-language name of the function, which need not be the same as the name being declared for SQL use. (For reasons of backwards compatibility, an empty body is accepted as meaning that the C-language function name is the same as the SQL name.)
Normally, all internal functions present in the server are declared during the initialization of the database cluster (initdb), but a user could use CREATE FUNCTION to create additional alias names for an internal function. Internal functions are declared in CREATE FUNCTION with language name internal. For instance, to create an alias for the sqrt function:
CREATE FUNCTION square_root(double precision) RETURNS double precision AS 'dsqrt' LANGUAGE internal STRICT;
(Most internal functions expect to be declared "strict".)
Note: Not all "predefined" functions are "internal" in the above sense. Some predefined functions are written in SQL.


text:
Unpatched Remote Access Tools: Your Gift To Attackers
Three-year old "TeamSpy" espionage campaign should be a wake-up call. Lock down your remote-access tools, or else.
March 22, 2013
Help desk teams love remote-control software. When employees call with computer problems, the IT department can remotely take control of the user's machine, copy over files and set all application and operating system wrongs to right.
Unfortunately, they're not the only group interested in putting TeamViewer, Symantec PCAnywhere, UltraVNC or other remote access software to work. Attackers love the software too, because it allows them to avoid sneaking complex Trojan malware onto a targeted PC. Instead, they use the already installed remote control software to do the heavy lifting for them, and even run attacks from memory, thus making the exploits more difficult to detect, trace or investigate.
Take the three-year old "TeamSpy" espionage operation, first publicly disclosed Wednesday, that's been targeting high-profile users of the TeamViewer remote control, desktop sharing and file transfer software, which counts over 100 million people as users.
[ You also need to worry about passwords. Read Cisco Password Fumble: Hardware Security At Risk. ]
The TeamSpy attack campaign -- thought to have targeted fewer than 1,000 people to date, but also still to be in operation -- highlights that one of the most effective techniques for spying on people's PCs isn't to code up complex malware. Instead, why not target known vulnerabilities in the remote-control softwarealready installed on PCs to remotely control that software and copy over required attack modules?
In fact, that's exactly what the group behind TeamSpy has done. "To avoid alerting the user that somebody is spying on him, the attackers dynamically patch TeamViewer in memory to remove all signs of its presence," according to researchpublished by Kaspersky Lab.
This type of attack is elegant, because it avoids leaving many of the tell-tale signs that would otherwise be present after a malware infection, such as back-and-forth communications between malware-infected "zombie" endpoints, command-and-control websites that issue instructions and other websites that are used as data dumps. "Using teamviewer as a RAT [remote access Trojan] builds an operational signature, but reduces the operators' fingerprint," said the Bangkok-based vulnerability broker who goes by the name "The Grugq," via Twitter.
"Amusing to see that my anti-forensic strategies (also counterintelligence tenets) are used in the real world," he said, linking to an article he wrote for hacking e-zine Phrack in 2004 that details techniques for creating attacks that leave few recoverable traces for digital forensic investigatorsto study, such as running attacks in memory -- rather than from malicious files -- and using utilities built into an operating system to provide needed functionality, such as a backdoor.
This isn't the first security warning to be sounded over unpatched remote-control software. Notably, Symantec in January 2012 took the unusual step of recommending that all pcAnywhere users disable the softwareuntil the company could issue a patch, which it did one month later.
Symantec's warning was made in the wake of revelations that attackers had successfully breached Symantec's systems in 2006, stealing source code that they might have analyzed to find zero-day attacks to crack the encryption or otherwise exploit the pcAnywhere application, which had remained largely unchanged in the intervening years.
Just as worrying as the threat of corporate PCs being remotely owned via Symantec's software was the fact that the source code theft took five years to detect, meaning that such attacks might well already have been practiced for half a decade.
Which raises this question: Is using remote control software worth the risk, given the security issues highlighted by the active TeamViewer attack campaign, as well as the five-year window in which pcAnywhere users may have been exploited?
As a priority, all TeamViewer users should at least review their systems for signs of a TeamSpy attack. TeamViewer spokeswoman Magdalena Brzakala told Dark Readingthat any business that uses TeamViewer should immediately scan all systems for the presence of a file named "avicap32.dll," which is TeamViewer-targeting malware installed by attackers. She also recommended that users immediately update their TeamViewer software to the latest version and ensure they were running antivirus software with the latest signatures.
Kaspersky Lab, meanwhile, said organizations can protect themselves against TeamSpy attacks by scanning all PCs for the presence of the "teamviewer.exe" application, then locking them down by blocking access to the command-and-control domains and IP addresses used by TeamSpy attackers, which are detailed in a related Kaspersky Lab research report. In addition, "implement a rigid patch-management plan throughout the organization," it said, which will help keep TeamViewer up to date, thus helping prevent attackers from exploiting well-known bugs contained in previous versions.
Even better: Use a firewall on every system to whitelist IP addresses that are allowed to control any and all remote-control software. Block all unapproved IP addresses. Also block all unapproved software. Because in the wake of the TeamSpy attacks, the mandate for any business that uses remote-control software should be clear: Lock it down, or lose it.
About the Author(s)
You May Also Like
The CIOs Guide to Enhancing GRC in 2024
June 20, 2024Enhance Cloud Security with Cloud-Native Security
June 25, 2024Search Capabilities with PostgreSQL: From Standard to Semantic
June 27, 2024


text:
Home - Shop by Vehicle - Gmc - Canyon (04-06)
No Image Available
AntennaX The Shorty (5-inch) ANTENNA for GMC Canyon
Replace your ugly factory (31 inch) metal shaft antenna with this stylish yet functional LOW PROFILE (5 inch) antenna. Made out of BILLET ALUMINUM and is POWDER COATED BLACK. This is a PLUG-N-PLAY antenna, which means it screws onto your existing antenna mount (a direct bolt-on part, no wiring involved) and takes a minute to do. 4 out of 5 reception with most people noticing no difference at all. As a general rule, strong stations will be fine and weak stations will be reduced.
- 758524801398
- AntennaX
- New
Shipping Information
- Item Requires Shipping
- Free Shipping
Customer Reviews
Total Reviews (0)
Write the First Review!
You must login to post a review.
- AntennaX Difference
- We are the Antenna XpertsAsk us anything. We are the professionals!
- Largest Antenna SelectionIf you don't find the part, we'll get it for you!
- Free USA Shipping On every order
- Have a QuestionAsk the Antenna Xperts 24/7
- Have a question? Ask the Pros
- Email UsGet answers from the pros


text:
There's no right loan for everyone. But there's a right one for you.
There are so many different loans out there, each with its own benefits and drawbacks. The great thing is that lenders are more competitive than ever and are constantly refining their products and releasing new ones. The problem is how do you find one that's right for you?
You have to know where to look. And that's what a broker is here for. We'll speak to you first to get to know you and get a better understanding of your needs. And then we look at options that suit those needs, to choose one that's right for you. And then, to make it even easier, we'll help you take care of the process. We'll help take care of the paperwork and manage the application process right through to approval.
When you're ready, why not talk to a broker about your next steps.
Here's a guide to common loan features and benefits
Of course, not all of these features will be available on every loan. You can ask us about any that interest you.
Interest Only Repayments
You only pay the interest on the loan, not the principal, usually for the first one to five years although some lenders offer longer terms. Some lenders give borrowers the option of a further interest-only period. Because you're not paying off the principal, your monthly repayments are lower. These loans are especially popular with investors who pay off the principal when the property is sold. This strategy is usually reliant on the property having achieved capital growth before it is sold.
Extra Repayments
If you pay more than the required regular repayment, the extra amount may be deducted from the principal. This not only reduces the amount you owe but lowers the amount of interest you repay. Making extra repayments regularly, even small ones, is the best way to pay off your home loan quicker and save on interest charges.
Weekly or Fornightly Repayments
Instead of a regular monthly repayment, you pay off your home loan weekly or fortnightly. This can suit people who are paid on a weekly or fortnightly basis, and will save you money because you end up making more payments in a year, cutting the life of the loan.
Redraw facility
This typically allows you to access any extra repayments you have made. Knowing you have access to funds can provide peace of mind. Be aware lenders may charge a redraw fee and have a minimum redraw amount. There might also be other restrictions on when funds can be redrawn.
Repayment holiday
You may be able to take a complete break from repayments, or make reduced repayments, for an agreed period of time. This can be useful for travel, maternity leave or a career change.
Offset account
This is a savings account linked to your home loan. Money paid into the savings account is deducted from the balance of your home loan before interest is calculated. The more money you save, the lower your regular home loan repayments. You can often access your savings in the usual way, by EFTPOS and ATMs. This is a great way to reduce your loan interest, as well as eliminate the tax bill on your savings. Be aware the account may have higher monthly fees or require a minimum balance or have other restrictions.
Direct debit
Your lender automatically draws repayments from a chosen bank account. Apart from ensuring there is enough cash in the account, you don't have to remember to make repayments.
All in one home loan
This combines a home loan with a cheque, savings and credit card account. You can have your salary paid into it directly. By keeping cash in the account for as long as possible each month you can reduce the interest charges. Used with discipline, the all-in-one feature offers both flexibility and interest savings. Interest rates charged for these loans can be higher.
Professional package
Home loans over a certain value are offered at a discounted rate, combined with discounted fees on other banking services. These can be attractively priced, but if you don't use the banking services you may be better off with a basic variable loan.
Portable loans
If you sell your current property and buy somewhere else you can take your home loan with you. This can save time and set-up fees, but you may incur other charges.


text:
Discussion on conservation, press releases, politics, current and future Legislation and any other matters that have the potential to affect recreational fishing
Use this control to limit the display of threads to those newer than the specified time frame.
Allows you to choose the data by which the thread list will be sorted.
Order threads in...
Note: when sorting by date, 'descending order' will show the newest results first.
Forum Rules


text:
Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
View source for BaSyx / WhatIsBasyx
You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page.
Return to BaSyx / WhatIsBasyx.


text:
What is CFC?
The Combined Federal Campaign is a way for military and federal employees to contribute to charities using a payroll deduction. Contributions to the Association of Gospel Rescue Missions can be made by designating CFC #10981 on your pledge card during campaign season. Look for charity fairs in your area during "open season" (September 1 to December 15). Your contribution will go to the work of the Association of Gospel Rescue Missions.What CFC is not: CFC will not allow you to designate a donation for a specific recipient. If you would like to give directly to a member rescue mission, you may use the map search to access their website. You may donate to a member mission directly via credit card, but not by payroll deduction.