text:
Results 1 to 30 of 151
January 22nd, 2007 #1
Last Man Standing 2 Final Round
Official Last Man Standing 2 Website and Match Index
271 initial contenders over 4 rounds of randomly paired mayhem. 396 new pieces of artwork. 1 winner. And not one 1-on-1 battle.
The Round Breakdown:
Round I: 271 initial contenders in 3 (one 4) man battles
Round II: 90 contenders in 3 man battles
Round III: 30 contenders in 6 man battles
Final Round IV: 5 contenders, one winner.
This is the grand finale, what you 5 have worked your way through 265 other competitors to get to. Blow our minds, ladies and gentlemen.
Some of the top industry talent this fine forum has to offer will be judging each round and deciding who advance to the next round. The match is a final 5 man battle so the scoring will be a bit different this time. The voting will be a point system; 6 points for 1st place, 4 for 2nd, and 3 for 3rd, 2 for 4th, 1 for 5th.
Judges for Round Four:
Dan Dos Santos
Greg Manchess
Irene Gallo
more to come...
On to the big show.
Last edited by strych9ine; January 23rd, 2007 at 10:28 AM.
Hide this ad by registering as a memberJanuary 22nd, 2007 #2
Nicolas' Entry
Entry 01: Nicolas
January 22nd, 2007 #3
Shelly Wan's Entry
Entry 02: Shelly Wan
January 22nd, 2007 #4
Icon's Entry
Entry 03: Icon
January 22nd, 2007 #5
Vyle's Entry
Entry 04: Vyle
January 22nd, 2007 #6
Poshspice's Entry
Entry 05: Poshspice
January 22nd, 2007 #7
It's been a long, crazy ride ladies and gentlemen. It's amazing to me how dedicated you've all been to producing such phenomenal work for a dome started just for fun.
To everyone that was a part of this dome and especially to you last 5 domers here in the final round, thanks for making this the hell of a dome it turned out to be.
I'll work on finalizing judges for this all important round, so until then hold tight. Congrats on making the final round.
January 22nd, 2007 #8
Holy crap guys and gals. NICE WORK!! All five pieces are dynamic, entertaining, and beautiful in their own right. Judges, good luck.
Shawn Adomanis
"Pay no attention to that man behind the curtain!" The Wizard of Oz
January 22nd, 2007 #9
Wow... Nicolas, that army is wonderful. You're brave, I'm routing for you! Sw33t contibutions from the rest as well! What a clever take on the theme Poshspice^^
No pain, no gain.
January 22nd, 2007 #10
excellent work guys
January 22nd, 2007 #11
Outstanding work all but Shelly's is in a class of its own
Last edited by draw; January 23rd, 2007 at 01:03 AM.
January 22nd, 2007 #12
I get the feeling that nobody wanted to do the obvious, so the powerful, blood and thunder stuff I thought I might see isn't here. None the less, it's all amazing work.
Nicolas - Great character design and rendering
Shelly - The most beautiful piece here, and the best composition
Icon - Beautiful lighting, and I love the framing with the tentacles
Vyle - Great feel and emotion, you really get a sence of Don Quixote's madness here and how he sees the world
Posh - Hilarious play on 'Charge' perfectly done as always. The guys at Mad Magazine need you desperately
Nathan's Journal
January 22nd, 2007 #13
I love them all!
- Nicolas: Great palette and typography. Nice subtle rainbow happening with the sketchy army.
- Shelley Wan: Magnificent composition and rendering, another great palette. I'm intrigued by the shape - it almost looks like the image could wrap around a vase or similar, perspective notwithstanding.
- Icon(ophobian): Great water, interesting light source. It looks like a lot of thought went into the sweeping curves of the image. I love the way the image is framed in the corners by tentacles.
- Vyle: Insane textures and values, very contrasty image but it works well. Instantly recognisable brush style. Nice discreet skull windmill.
- Poshspice: Best interpretation of topic. Trademark rendering, good values and good illumination from unconventional light sources. Couldn't help but notice that her hair is electrified and her hairspray is flammable...
Last edited by Snarfevs; January 22nd, 2007 at 09:51 PM.
January 22nd, 2007 #14
I am completely overwhelmed by your piece shelly wan. I fell in love with it.
I'll come back later with better comments, but I had to say it.
January 22nd, 2007 #15
i love all of you....
nicely done! nicely done indeed.
There is no "I" in team, but there is an "I" in pie. And there's an "i" in meat pie. Meat is the anagram of team...~Shaun "Shaun of the Dead"
January 22nd, 2007 #16Registered User
- Join Date
- Sep 2002
- Location
- Posts
- 1,188
- Thanks
- 785
- Thanked 666 Times in 165 Posts
- Follows
- 0
- Following
- 0
oh wow, amazing, thank you! those pictures really crown the challenge and honor everyone who participated... all pictures are just over the top and crazy and cool in their own ways! I don't see how there can possibly be a judgment on those... hard time for judges.
It's been an honor competing against you in the last round, Nicolas, glad to see you accelerating your momentum with a final charge (oops that was cheap). This piece is just amazing, so great graphic design and composition and all. The guy is way cool and so full of character, great balance. It's fun because, when I saw I was against you last round, I thought, "damn, this guy is so hype and stylish that he could win even with a stick figure".. and here they come . Good luck to you!
Shelly Wan : waw, that's fabulously elegant. This odd format gives it a great art deco touch, like it's meant to be a painting on a wall, or perhaps a fan. The colors and light are absolutely lovely, and .. and ... I'm wondering how I will end up this reply without spending all the superlatives I know. Anyway, the graphic design you incorporated is great too, I especially like how the water waves feel slightly embossed.. it gives a delicate touch. Great job on the different materials too, the skin, cloth, metal, wall shading are spot on.
Good luck to you!
Icon : the composition is just terrific in your picture, I love this central character, and the dynamic in the piece is very well thought out. The palette is super-cool too, those harpies coming from the dark blue tones to the warm water of the sea-folk, great. Good luck!
Vyle : heyy that's crazy cool David, great use of your rock skills again, and super cool intepretation of the theme.. Good luck to you, you're representing the "Neo team" in a magistral way!
Poshspice : haha excellent, great to see that you went for another meaning of the theme. The pinup / B-movie thematic is again greatly mastered, the picture you made there is just plain fun to look at, a lot of little cool details (love the troll!), and the frankenstein groupie is delicious (if you forget the stitches...). Good luck!
And last and not least : Cody, BIG thanks for organizing this thunderdome, it was totally awesome, so much great artworks just for fun and fame On to the next one!! reveeeeeenge
Last edited by m@.; January 22nd, 2007 at 09:38 PM.- 2007 sketchbook -
- old sketchbook -
- exclusive sketchbook - <~ New brushes
January 22nd, 2007 #17
Good luck judges
* Help a CA artist! Visit the Constructive Critique section! *
January 22nd, 2007 #18
That is definitley pushing the digital medium... Canvas shapes like that, it beats normal rectangles... That is definitley a pioneering move!!! Way to go all of you!
Posh, that is a GREAT idea... very original kind of "Charge" haha!
January 22nd, 2007 #19
The shape of Shelly's piece is usually used for murals in arches over a door, I think.
Nathan's Journal
January 22nd, 2007 #20
...nic's piece is crazy...everything about it is damn crazy!
January 22nd, 2007 #21
good luck, guys!
they are all beautiful.
- Dan Dos Santos
January 22nd, 2007 #22
my NEW sketchbook
Bleeding hands of art
Asoir * Blanquish * Dile * OldNoobie
craig houghton
January 22nd, 2007 #23
Wow, you guys pulled out all the stops on this one... and I'm really glad I didn't make it to this round....
Shelly..... your piece made me gasp the way you see people do in the movies when they've been underwater for what seems like hours, and they finally surface and suck in the air so hard you can't tell whether or not the breath they just took saved their life or burned even more than if they had drowned.
I had a brand new James Jean wallpaper up today too, and your painting instantly replaced it.
Last edited by Mike Dutton; January 22nd, 2007 at 09:58 PM.
January 22nd, 2007 #24
I hate you all!!!!!!
Even though Nic put up an AMAZING fight the last few rounds, I called it for Shelly since the Round 1 entries were posted. Shelly all the way
Awesome job everyone. Now hurry up and submit them all to Spectrum before the deadline comes and goes.
January 22nd, 2007 #25
p.s. Cody, thanks again for all the hard work in putting together LMS2. Also, I love the graphic design for this one: the cropping of each piece put side by side creates a new piece that stands on its own, despite the unique style each finalist brought forth in the final round.
p.s.s. I remember you saying that, Arkady.
January 22nd, 2007 #26
Poshspice gets my vote.
January 22nd, 2007 #27
Tristan Elwell
**Finished Work Thread **Process Thread **Edges Tutorial
Crash Course for Artists, Illustrators, and Cartoonists, NYC, the 2013 Edition!
"Work is more fun than fun."
-John Cale
"Art is supposed to punch you in the brain, and it's supposed to stay punched."
-Marc Maron
January 22nd, 2007 #28Registered User
- Join Date
- May 2003
- Posts
- 128
- Thanks
- 5
- Thanked 61 Times in 13 Posts
- Follows
- 0
- Following
- 0
Phenomenal work all five of you!
Thank you sincerely.
Thank you for the smile, the inspiration and the references images I can pull from on the day when I forget why I should draw rather than play the video game.
All because of your efforts.
January 23rd, 2007 #29
...so my wife walks in with a black-powder 1890 Navy issue .45, loaded and cocked, points it generally in the direction of my left ear and tells me to take a shower because the cats are afraid to come in any room I'm in...
Then I come out here, open this thread, and piss my pants. Thanks a fuckin' big ho-dad lot, everybody...as soon as I find your addresses, I'll show my appreciation in person...
Nice damn job, everybody!
No position or belief, whether religious, political or social, is valid if one has to lie to support it.--Alj Mary
Ironically, the concept of SIMPLICITY is most often misunderstood by simple-minded people. --Alj Mary
January 23rd, 2007 #30
Well I'm a bit speechless, (not that that's unusual.)
Just amazingly good pieces from each of you
Members who have read this thread: 1


text:
WASHINGTON D.C. – U.S. Senator Bob Casey (D-PA), Chairman of the U.S. Congress Joint Economic Committee (JEC), released the following statement on the Bureau of Labor Statistics' August 2012 jobs report showing that the unemployment rate dropped slightly to 8.1 percent:
"Today we learned that the economy added 96,000 jobs in August, marking 30 consecutive months of private sector job growth. Even though the economy added jobs last month, too many Americans are still struggling to find work. When Congress returns next week, Democrats and Republicans should immediately begin to work together on legislation that will create jobs and boost economic growth right away. "

subset: commoncrawl


text:
Lauren Nicole Fordham of Snow Hill and Steven Andrew "Drew" Sowers of Walstonburg were united in marriage at 5:30 p.m. Dec. 14, 2013, at Bethel FWB Church in Kinston. The Rev. Chris Truett was the officiating minister.
Escorted by her father and given in marriage by her parents, the bride is the daughter of Gregory and Bernice Fordham of Snow Hill. She is the granddaughter of the Rev. Gordon and Mary Lou Jones Sebastian of Wilson and Barbara Fordham of Kinston.
A graduate of Bethel Christian Academy, she received a bachelors degree in Family and Community Services from ECU. She is a Financial Services Representative with State Employee's Credit Union.
The groom is the son of Steve and Kaye Sowers of Walstonburg. He is the grandson of Cindy Moye, also of Walstonburg.
A graduate of Greene Central High School, he received an associates degree in Construction Management from Pitt Community College. He is a foreman with Barnhill Construction.
The bride wore an ivory A-line dress in Parisian Silk Chiffon by Martina Liana featuring a dramatic textural skirt. Encrusted Swarovski crystals, diamantes and freshwater pearls adorned the scalloped sweetheart bodice. She wore a headpiece by Bel Aaire and carried a bouquet of ivory and white peonies and hydrangeas.
Brianna LouRae Jones, cousin of the bride, of Snow Hill was maid of honor.
Bridesmaids were Bridgette Wiggins Becton of Deep Run; Julie Christina Gray, Ashley Lauren Huggins and Kimberly Rae Taylor, all of Kinston; and the groom's cousin, Amy Moye Wiggins of Wilson. The bride's cousin, Briley Paige Jones of Snow Hill was a junior bridesmaid.
Meredith Lynlee Kennedy of Hookerton was the flower girl.
The groom's father served as his son's best man.
Groomsmen were Weslyn Moye Sowers, brother of the groom of Walstonburg; Donald Rudolph Blizzard Jr. and Ashton Blake Sutton, both of Snow Hill; Zacharia Harris Wiggins of Wilson; Justin O'Neal Fordham, brother of the bride of Snow Hill; and Matthew West Gay of Walstonburg.
The groom's cousin, William Moye Wiggins of Snow Hill was ring bearer.
Wedding music was provided by violinist Sarah Wall.
Register and program attendant were Brandi Jones Holland and Jamie Martin Kennedy, respectively.
The wedding was directed by Margie Thurman, Lisa Sowers and Paula Smith.
Following a wedding trip to Charleston, S.C. the couples resides in Snow Hill.
Immediately following the ceremony the bride's parents hosted a reception at Frenchman's Creek in Kinston. Greeting guests were Ronnie and Pat Moye.
On March 16, 2013, a monogram shower was given by Mona Barfield, Christie Mozingo, Meredith Rouse and friends of the bride.
Sept. 20-22, 2013, a bachelorette weekend was held in Wilmington, and given by Julie Gray, Bridgette Wiggins and Ashley Huggins.
On Oct. 4, 2013, an engagement party was hosted by Mike and Debbie Gay, Pat and Sherri Harris, Donnie and Kathy Blizzard, Luke Blizzard, Laurie and Sammy Gay, Jeff and Carol Lynn Heath, Dennis and Allison Horton, and Zack and Amy Wiggins.
On Oct. 6, a church shower given by Wendy and Lauren Wiggins, Lisa Sowers, Joy Williams, Alice Boone, Marilyn Wiggins, Loretta Campbell, Teresa Sutton and Pam Farmer, was held at Bethel FWB Church.
On Nov. 16, 2013, a Christmas shower was given by Ashley and Angela Huggins, Bridgette Becton, Sharon Wiggins, Lori Tyndall, Debbie Tripp, Paula Smith, Susan Bland, Julie Gray and Kimberly Taylor.
On Nov. 22, 2013, a couples shower was hosted by Tim and Kathy Fordham, DeWitt and Missy Jones, Rusty and Tammy Fordham, Elwood and Bobbie Harrison, and Simon and Vicky Cox.
On Nov. 23, 2013, a bridal luncheon was hosted by Mary Lou Jones Sebastian and Brianna LouRae Jones.
On Nov. 30, 2013, a church shower hosted by the groom's church, Howell Swamp OFWB, was given by Kaye Sowers and friends of the family.
On Dec. 13, 2013, the parents of the groom hosted a rehearsal dinner.


text:
Dr. Flint earned his medical degree from Emory University School of Medicine. He completed internships in internal medicine and general surgery, and a residency in orthopaedic surgery at Emory University affiliated hospitals in Atlanta. He is board certified in orthopaedic surgery and is active in the American Academy of Orthopaedic Surgeons and the American College of Surgeons.
Prior to joining Piedmont Physicians, Dr. Flint practiced for 18 years at Blue Ridge Regional Hospital in Spruce Pine, North Carolina, where he was chief of surgery for 15 years and the medical director of physical therapy.
Dr. Flint is a native of Cherokee County. He graduated valedictorian from Cherokee High School and Phi Beta Kappa from Emory University with highest honors. When not working he enjoys woodworking, music and outdoor sports.
Dr. Flint is accepting new patients and welcomes most major insurance plans.
Dr. Flint's office hours are Monday - Friday 8:30am - 5:00pm.


text:
One day on our campus could change your
life. Over the past 26
years, Lee has grown like wildfire-from just over 1,000 students to
almost 5,000. Twenty-five buildings have been added to our 110 acre
campus, and new programs are launched every year. One hundred percent of
our faculty are both gifted scholars and committed Christians. Our
students come from all 50 states and 58 countries. We want you to
first-hand why Lee University is one of the nation's fastest-growing
Christian universities. It's definitely something to get fired up about.
Click here for more informationSave
1120 N Ocoee Street
Cleveland, TN 37320-3450


text:
News from WTOP
News from the AP
Mike Causey
Shows & Panels
Shows & Panels
- Agency of the Month
- Business of Government Hour
- The CFO Agenda: Delivering value from financial transparency and audit efforts in the public and private sector
- Cloud-Driven Data Insights in Government
- CXO Surveys
- Disaster Resilience for America
- Federal News Countdown
- Government Perspectives on Mobility and the Cloud
- Reducing Risk in the Cloud
- Reimagining the Next Generation of Government
Shows & Panels
- AFCEA Answers
- American Readiness: Renewable Power and Efficiency Technologies
- Ask the CIO
- The Business Case for Cloud Computing in Government
- Cloud-Driven Data Insights in Government
- Connecting the Dots: Digital Authentication in Government
- Cybersecurity Game Changer: Real-Time Event Processing in Government
- Data-Centric Approaches to Government in the Cloud
- Delivering the Digital Government Mission
- Federal Executive Forum
- Federal News Radio's National Cyber Security Awareness Month Special Panel Discussion
- Federal Tech Talk
- The Future of Government Data Centers
- Government Perspectives on Mobility and the Cloud
- Industrialized, Interoperable and Insight-driven Federal Health Panel
- Innovation and Tech Superiority through Acquisition Reform
- Mitigating Insider Threats in Virtual & Cloud Environments
- Moving Agency Applications to the Cloud with PaaS
- Reducing Risk in the Cloud
- Security in the Age of Targeted Attacks
- Air Traffic Management Transformation Report
- The Business of Cloud
- Cloud First Report
- Data Driven Cloud Series
- Disaster Resilience for America
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- The Intersection: Where Technology Meets Transformation
- Modern Mission Critical Series
- National Cybersecurity Awareness Month
- The New IP for Federal IT
- The Social Platform Solution for the Department of Veterans Affairs
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
- Cloud-Driven Data Insights in Government
- Disaster Resilience for America
- F-35 Lightning II Program
- Government Perspectives on Mobility and the Cloud
- On DoD
- Pentagon Solutions
- Reducing Risk in the Cloud
- Reimagining the Next Generation of Government
- Transforming Business Operations at the Defense Department
Monday - Friday, 4-7 p.m.
In Depth with Francis Rose features daily interviews with top government executives and contractors. Listen live from 4 to 7 p.m. or download his archived interviews below.
DoD's plans to boost cyber workforce could hit hiring, training snags
Tuesday - 1/29/2013, 7:20pm EST
The Defense Department plans to boost the ranks of cybersecurity professionals, increasing cyber staff at U.S. Cyber Command by more than five times to some 4,900 employees, according to a recent report in The Washington Post.
The staff-up involves three tiers of cyber pros: Those to protect critical infrastructure, protection forces designed to safeguard DoD's own networks and "combat mission forces," which will provide offensive cyber capabilities.
But DoD's plan is daunting in more ways than one. The job qualifications and skills needed for the kinds of positions the Pentagon wants are rare and often require years of training and hands-on experience. And even if DoD looks outside the confines of the Pentagon to fill these roles, it's not entirely clear where the new cyber pros would come from.
People and skills
"This isn't a discussion about lots of new money," said Alan Paller, director of research for the SANS Institute in an interview on the Federal Drive with Tom Temin and Emily Kopp. "It's a discussion about people and skills."
When Cybercom was first stood up three years ago, the command hoped to staff up with some 3,000 cyber professionals from each of the military services, Paller said. But the services "literally laughed," he said. They couldn't even provide 300 personnel members.
One of the reasons why cyber personnel can be elusive is because of the highly technical nature of the job, Paller said. Cyber pros need to be capable of protecting DoD networks, have a deep understanding of cyber threats, the ability to write code, and be proficient at analyzing network traffic for possible intrusions and software for possible flaws and vulnerabilities.
'Huge shift' in training?
Paller said DoD's announcement signals a "huge shift" in training expectations and how DoD defines a cybersecurity expert.
"You can't just take anybody and make them into a cyber person," Paller said. "There's a certain way the brain works that allows you to look at systems from the flaw perspective rather than from the functional perspective. So the real key is ... to have a talent search among all the existing workers to find the people who have these skills."
Paller said it appears DoD is ramping up its training to essentially grow its own cyber professionals as opposed to looking outside the organization.
"They're not able to hire them; the contractors can't find them either," Paller said. "So they can build this talent within. And it's a huge effort. And I don't mean hugely expensive. It may be that as well. But sometimes there are just things that are hard to do. And this is really hard to do."
If the Pentagon did decide to hire from outside the government, that would bring with it its own set of problems, according to Ron Marks, senior fellow for George Washington University's Homeland Security Policy Institute.
"The kind of guys you might want to recruit for this are not necessarily the ones you're going to get through the clearance process so easily, which under the best of circumstances takes six months to a year," Marks said in an interview on In Depth with Francis Rose.
"You have a pot of people out there who are perfectly capable of hacking and engaging in that kind of activity," he added. But they may not easily pass the security-clearance process at the top-secret level.
Those factors mean it will probably be difficult for the Pentagon to build up its cyber force quickly, Marks said.
"It's going to be hard a hard slog," Marks said, even if Cyber Command plans to implement its personnel goals over a number of years.
The latest cyber build-up at DoD follows a number of recent moves by agencies seeking to staff up their cyber-operations shops.
Earlier this month, the Air Force announced it would hire an additional 1,000 cyber professionals to keep up with potential cyber rivals, such as Iran.
In November, an internal Homeland Security Department advisory committee recommended the department hire 600 cyber experts.
DHS urged to hire 600 cyber ninjas


text:
There are currently no items in your cart.
A Chorus Line Sheet Music: 2 items found
A Chorus Line
(The Movie). Composed by Marvin Hamlisch. For Guitar, Piano/Keyboard, Vocal. Vocal Selections. 88 pages. Published by Hal Leonard (HL.383313)
Usually leaves our warehouse: Within 3 to 5 business days
What I Did For Love - From 'A Chorus Line'
For Guitar, Piano/Keyboard, Vocal. Piano Vocal. Broadway, Movies and Traditional Pop. Difficulty: medium. Single. Vocal melody, piano accompaniment, lyrics, chord names and guitar chord diagrams. 4 pages. Published by Hal Leonard (HL.382547)
Usually leaves our warehouse: Within 24 hours
A Chorus Line


text:
Joseph Paul Eder MD
Professor of Medicine (Medical Oncology)
Biographical Info
I was the principal clinical investigator of the Harvard UO1 Phase I program in 1995, uniting the clinical efforts at the DFCI, BWH, MGH and BIDMC. In 1998, I became the Clinical Director of the Experimental Therapeutics Program for the Dana-Farber/Harvard Cancer Center. As Clinical Director, I assumed overall responsibility for the trials performed at the DF/HCC. In 2004 I assumed the responsibilities as the Clinical Director of the DFCI General Cancer Research Center at the Dana-Farber/ Brigham and Women's Hospital. These clinical and basic research activities have involved collaboration with clinical and basic scientists at Harvard and elsewhere, the Cancer Therapy Evaluation Program of the National Cancer Institute, presentations at national and international meetings, and correspondence with a number of leaders in the field of cancer drug development.
At AstraZeneca PLC, I was the Medical Science Director for AstraZeneca's Boston site, responsible for the medical and clinical aspects of development of agents from chemical lead identification through clinical proof of concept in phase II. I was responsible for the design and interpretation of the entire clinical development plan for five agents. This position had global responsibilities with clinical trials in the US, Canada, European Union, Japan and Korea. I was a member of the Strategic Planning & Business Development as an ad hoc member and was the global Disease Area Clinical Expert for Hematology.
Education & Training
- Georgetown University School of Medicine (1978)
- Residency
- Georgetown University Hospital, Internal Medicine (1979 - 1981)
- Fellowship
- Georgetown University Hospital, Medical Oncology (1981 - 1982)
- Fellowship
- Beth Israel Hospital, Oncology/Hematology (1982 - 1985)
- Board Certification
- Internal Medicine, Board Certified (1981)
- Board Certification
- Medical Oncology, Board Certified (1983)
- Board Certification
- Hematology (Internal Medicine), Board Certified (1984)
Honors & Recognition
- Who's Who Madison


text:
Consciousness and the Double-slit Interference Pattern
Six Experiments
by Arnaud Delorme, PhD, Karla Galdamez, Leena Michel, Dean Radin, PhD, Robert Rickenbach, and Paul Wendland
A double-slit optical system was used to test the possible role of consciousness in the collapse of the quantum wavefunction. Each test session consisted of 40 counterbalanced attention-toward and attention-away epochs, and data was contributed by 137 people in six experiments, involving a total of 250 test sessions. The results appear to be consistent with a consciousness-related interpretation of the quantum measurement problem.


text:
The IRB has responded angrily to Paul Honiss's comments that players should talk more to referees and question decisions.
The New Zealand referee, who is on the IRB's 12-man referee panel for the World Cup, has been told by the world governing body that his comments were "against IRB policy".
"The message from the IRB has not changed," said IRB CEO Mike Miller. "Back-chat and arguing with a match official will not be tolerated, nor will any attempt to influence a referee or slow down the match through questioning the referee. Players who overstep the mark will be penalised accordingly and the IRB has reiterated this policy to the referee panel.â€
"Paul Honiss's comments encouraging players to verbally engage the referee more were out of line. He has been reprimanded by the IRB referee manager [fellow Kiwi Paddy O'Brien] and he has been told that such actions will not be tolerated moving forward. He has been reminded about his responsibilities as a Test match referee and he has accepted that his actions were contrary to IRB policy."
O'Brien added; "The referee's decision is final on the field of play. Nowhere in the game's laws does it say that players can question the referee or try to influence his decision making. We allow captains to talk to the referee but only at appropriate moments and it is not a given right.â€


text:
It s now legal to possess up to one ounce of marijuana in Washington state, but you can t smoke it in public.
At least for now, Seattle Police plan to look the other way on the latter part until people get used to the new law.
People gathered for indoor and outdoor celebrations across the state at 12:01 a.m. to light up in celebration. A small group celebrated outside Seattle s Hempfest Central.
At Seattle s Space Needle, it had a feel of New Year s Eve with marijuana users counting down to midnight and lighting up.
In Pictures:Facts about marijuana and the new law
Here's the number you need to know before driving stoned
In an email to officers, the department told them they should only issue verbal warnings in cases of public marijuana use until further notice.
Police spokesman Jonah Spangenthal-Lee wrote on the SPD Blotter that officers will be advising people to take their weed inside.
Or as Spangenthal-Lee put it: The police department believes that, under state law, you may responsibly get baked, order some pizzas and enjoy a `Lord of the Rings' marathon in the privacy of your own home, if you want to.
Once police start actually enforcing the law, it will be a $50 fine.
You can still get fired for smoking pot
Seattle PD marijuana blog gets national praise
Voters in Washington and Colorado last month made those the first states to decriminalize and regulate the recreational use of marijuana.
The law does not mean that you can grow or sell your own pot, which means there s no legal way to obtain it in Washington. The state is working on implementing a system to change that.
The state s medical marijuana law is not affected by the new law.


text:
There are currently no items in your cart.
"L7": 3 items found
Pretend We're Dead
By L7. Pop; Rock. GTRCHD. 2 pages. Published by Hal Leonard - Digital Sheet Music (HX.136065)
Available Instantly
Sonate per Clavicembalo Volume 5 Critical Edition
(Sonatas for Harpsichord). Composed by Domenico Scarlatti (1685-1757). Edited by Emilia Fadini. For Piano. Piano Collection. 260 pages. Ricordi #ER2753. Published by Ricordi (HL.50103470)
...Includes "Sonata L7 K302" in the song list
Usually leaves our warehouse: Within 24 hours
200 Sonatas - Volume 2
(Piano Solo). Composed by Domenico Scarlatti (1685-1757). Arranged by Gyorgy Balla. For Piano. EMB. SMP Level 9 (Advanced). 165 pages. Editio Musica Budapest #Z8268. Published by Editio Musica Budapest (HL.50511639)
...Includes "Sonata L7 K302" in the song list
Usually leaves our warehouse: Within 3 to 5 business days


text:
At a Glance
Why Get Tested?
To determine if you have, or recently had, a parvovirus B19 infection if you are at increased risk of complications from this viral infection; if a fetus is at high risk of contracting parvovirus B19 from a mother who is infected or has been exposed
When to Get Tested?
When a pregnant woman has a parvovirus B19 infection or has been exposed to someone with the virus; when someone, especially an immune-compromised person, has persistent or severe anemia
Sample Required?
A blood sample drawn from a vein in your arm for parvovirus B19 antibody testing; to detect the virus itself, the sample tested may be blood or, rarely, bone marrow; in certain cases, fetal cord blood or amniotic fluid may be collected to test for fetal parvovirus B19 infection.
Test Preparation Needed?
The Test Sample
What is being tested?
Parvovirus B19 is a virus that causes a common childhood illness, also called "fifth disease" or "erythema infectiosum." The virus is found in respiratory droplets during an infection and is easily transmitted to others through close physical contact. Parvovirus can also be passed from a pregnant woman to her fetus and transmitted through exposure to blood and blood products.
In the United States, as many as 50% of adults and 85% of the elderly have been infected with parvovirus B19, usually as children or young adults. The infection typically has an incubation period of several days to 2-3 weeks, is active for a short period, and then begins to resolve.
For most people, parvovirus B19 infection is indistinguishable from other mild illnesses that develop and go away within a short time period. Many who are infected have no symptoms or have mild flu-like symptoms such as fatigue, a slight fever, headache, or an upset stomach, and many may not know that they have had a parvovirus B19 infection. The majority of people do not experience any significant symptoms or health problems and once the initial infection resolves, the person becomes immune and will not get the infection again.
Some children with the infection develop a characteristic and distinctive bright red "slapped-cheek" rash on both cheeks and a raised lacy rash on the torso and extremities. The rashes may come and go for several weeks, reappearing and/or intensifying with exposure to heat and sunlight and with stress. By the time the rash appears, the child is no longer considered infectious. Parvovirus is sometimes called fifth disease because it is the fifth of six common childhood illnesses that can cause rashes.
Less commonly, some adults become infected and may develop "gloves and socks syndrome" with painful swelling of joints and reddening of the hands and feet that typically ends abruptly at the wrists and ankles. This condition usually resolves within a few weeks. Symptoms of arthritis may also occur in adults and children, but like "gloves and socks syndrome," tends to resolve a few weeks after infection. Some severe cases, however, have been tied to chronic arthritis and even to the development of rheumatoid arthritis.
Parvovirus B19 can cause major health problems in three types of patients:
- People with iron deficiency anemia or a condition that affects or shortens the life of red blood cells (RBCs), such as sickle cell anemia or thalassemia, may develop severe acute anemia during a parvovirus B19 infection. Parvovirus B19 targets cells in the bone marrow that become RBCs and disrupts the production of new RBCs, which can more severely affect those with underlying blood disorders.
- Women who are infected during pregnancy can pass the infection to their babies. Most fetuses will be fine, but a small percentage will develop severe anemia and a few may have an inflammation and infection of the heart muscle (myocarditis). These conditions can cause miscarriage, congestive heart failure in the fetus, hydrops fetalis (associated with fluid accumulation), and sometimes stillbirth. The greatest risk for fetal complications is during the second trimester of pregnancy.
- In those with compromised immune systems, a parvovirus B19 infection may cause chronic anemia and be challenging to resolve. This includes people with HIV/AIDS, those who have had organ or bone marrow transplants, and those undergoing chemotherapy treatment for cancer.
Parvovirus B19 testing is not typically used to screen the general population and is not deemed necessary in most cases of infection because symptoms are mild and time-limited. It is usually ordered to determine whether someone is currently, or has recently been, infected with parvovirus only if they are at risk of complications. It may also sometimes be ordered to determine whether someone has ever been exposed to parvovirus. Testing involves either a measurement of parvovirus antibodies—immune proteins produced in response to parvovirus B19 exposure—or the detection of the genetic material of the virus itself (its DNA) during an active infection.
How is the sample collected for testing?
The sample required depends on whether testing is being done to determine the presence of antibody or to detect the virus itself as well as on the health status of the patient. Antibody testing requires a blood sample, obtained by inserting a needle into a vein in the arm. Viral detection may be done on blood or, more rarely, on a sample of bone marrow collected through a bone marrow aspiration or biopsy.
In the case of a pregnant woman at risk of passing infection to her baby, fetal cord blood or amniotic fluid may be collected for testing. Fetal cord blood is obtained by guiding a needle into the vein of the umbilical cord with the assistance of ultrasound imaging. Amniotic fluid is obtained through amniocentesis, or inserting a needle into the amniotic sac surrounding the fetus and removing a small sample.
NOTE: If undergoing medical tests makes you or someone you care for anxious, embarrassed, or even difficult to manage, you might consider reading one or more of the following articles: Coping with Test Pain, Discomfort, and Anxiety, Tips on Blood Testing, Tips to Help Children through Their Medical Tests, and Tips to Help the Elderly through Their Medical Tests.
Another article, Follow That Sample, provides a glimpse at the collection and processing of a blood sample and throat culture.
Is any test preparation needed to ensure the quality of the sample?
No test preparation is needed.
The Test
Common Questions
Ask a Laboratory Scientist
Form temporarily unavailable
Due to a dramatic increase in the number of questions submitted to the volunteer laboratory scientists who respond to our users, we have had to limit the number of questions that can be submitted each day. Unfortunately, we have reached that limit today and are unable to accept your inquiry now. We understand that your questions are vital to your health and peace of mind, and recommend instead that you speak with your doctor or another healthcare professional. We apologize for this inconvenience.
This was not an easy step for us to take, as the volunteers on the response team are dedicated to the work they do and are often inspired by the help they can provide. We are actively seeking to expand our capability so that we can again accept and answer all user questions. We will accept and respond to the same limited number of questions tomorrow, but expect to resume the service, 24/7, as soon as possible.
Article Sources
NOTE: This article is based on research that utilizes the sources cited here as well as the collective experience of the Lab Tests Online Editorial Review Board. This article is periodically reviewed by the Editorial Board and may be updated as a result of the review. Any new sources cited will be added to the list and distinguished from the original sources used.
Sources Used in Current Review
De Jong E.P et. al. (May 2006). Parvovirus B19 infection in pregnancy. PubMed. Available online at http://www.ncbi.nlm.nih.gov/pubmed/16488187 through http://www.ncbi.nlm.nih.gov/pubmed. Accessed July 2013.
Sampedro Martinez A. et. al. (Dec. 2011). Diagnosis of congenital infection. PubMed. Available online at http://www.ncbi.nlm.nih.gov/pubmed/22305665 through http://www.ncbi.nlm.nih.gov/pubmed. Accessed July 2013.
Moore, TL. (July 2000). Parvovirus-associated arthritis. PubMed. Available online at http://www.ncbi.nlm.nih.gov/pubmed/10910181 through http://www.ncbi.nlm.nih.gov/pubmed. Accessed July 2013.
Cennimo, D. J. (Updated 30 Mar 2012). Parvovirus B19 Infection. Medscape. Available online at http://emedicine.medscape.com/article/961063-overview through http://www.edmedicine.medscape.com. Accessed July 2013.
Sources Used in Previous Reviews
Pagana, K. D. & Pagana, T. J. (© 2007). Mosby's Diagnostic and Laboratory Test Reference 8th Edition: Mosby, Inc., Saint Louis, MO. Pp 708-709.
Clarke, W. and Dufour, D. R., Editors (© 2006). Contemporary Practice in Clinical Chemistry: AACC Press, Washington, DC. Pp 1232.
Mayo Clinic Staff (2008 January 12). Parvovirus infection. MayoClinic.com [On-line information]. Available online at http://www.mayoclinic.com/print/parvovirus-infection/DS00437/DSECTION=all&METHOD=print through http://www.mayoclinic.com. Accessed July 2009.
Kwon, K. (Updated 2009 March 19). Pediatrics, Fifth Disease or Erythema Infectiosum. Emedicine [On-line information]. Available online at http://emedicine.medscape.com/article/801732-overview through http://emedicine.medscape.com. Accessed July 2009.
O'Reilly, D. (2007 September 28, Updated). Fifth Disease. MedlinePlus Medical Encyclopedia [On-line information]. Available online at http://www.nlm.nih.gov/medlineplus/ency/article/000977.htm. Accessed July 2009.
(2007 April). Fifth Disease in Pregnancy. March of Dimes [On-line information]. Available online through http://www.marchofdimes.com. Accessed July 2009.
Cunningham, D. (Updated 2006 November 9). Parvovirus B19 Infection. Emedicine [On-line information]. Available online at http://emedicine.medscape.com/article/961063-overview through http://emedicine.medscape.com. Accessed July 2009.
(Revised 2005 November). Erythema Infectiosum (Fifth Disease; Parvovirus B19 Infection). Merck Manual for Healthcare Professionals [On-line information]. Available online at http://www.merck.com/mmpe/sec19/ch280/ch280b.html?qt=parvovirus&alt=sh through http://www.merck.com. Accessed July 2009.
Servey, J. et. al. (2007 February 1). Clinical Presentations of Parvovirus B19 Infection. American Family Physician [On-line information]. Available online at http://www.aafp.org/afp/20070201/373.html through http://www.aafp.org. Accessed July 2009.
Hillyard, D. and Litwin, C. (Reviewed 2008 July). Parvovirus B 19 – Parvo. ARUP Consult [On-line information]. Available online at http://www.arupconsult.com/Topics/InfectiousDz/Viruses/Parvo.html through http://www.arupconsult.com. Accessed July 2009.
Klein, J. (Reviewed November 2007). Kids Health for Parents: Fifth Disease. Available online at http://kidshealth.org/parent/infections/bacterial_viral/fifth.html# through http://kidshealth.org. Accessed August 2009.


text:
Consistent shots require consistent, quality cues. You can find everything you need to keep your pool cues in like-new condition at PoolCueShark.com. For the billiard room sharpshooter, we carry Tiger Sniper laminated boar hide cue tips, these professional tips are guaranteed to never mushroom and give you the least deflection possible.
Do-it-yourselfers will love the value of our Sterling pool cue repair kit. Featuring replacement tips and ferrules, a cue tip clamp and cement, and much more; this kit has everything you need to get the most out of your pool cues for years to come! Browse our selection of Le Professionel, Elk Master, and Everest Pool Cue tips and accessories today!


text:
The KISS principle is a highly quoted design mantra. The aim of this principle is to stamp out unnecessary complexity on a project. This is a good thing, saving time, energy and money. It can lead to a relatively stress free implementation and a simple, elegant, maintainable end product.
A lot of discussion on KISS provides mechanisms to simplify requirements, design and implementation. Things that spring to mind include: avoid scope creep; simple obvious design and code; minimal run-time dependencies; refactoring to maintain simplicity; etc.
However there are a lot of implicit things that we do to KISS. Examples: small team sizes; minimal management layers; tidy desk; mastery of a single IDE; clear concise error messages; scripts to automate/encapsulate tasks; etc
What KISS practices do you apply? How have they benefited you? I'm especially interested in non-obvious practices.


text:
|Kite4Kids Water Sports Festival to Benefit All Children's Hospital
Come out to the Kite4Kids 2011 Water Sport Festival on Saturday, November 5th from 10:00 a.m.-4:00 p.m. on Treasure Island Beach. This event promises to be a fun filled family day with activities for all ages and all levels of water sports enthusiasts. Food and beverages will be available and there will be plenty of live music. All proceeds from the event will benefit All Children's Hospital. For more information please contact Julie Anderson at firstname.lastname@example.com.


text:
First Known Use: 1607
verb emas·cu·late \i-ˈmas-kyə-ˌlāt\
: to make (a man) feel less masculine : to deprive (a man) of his male strength, role, etc.
: to make (something) weaker or less effective
Full Definition of EMASCULATE
transitive verb
: to deprive of strength, vigor, or spirit : weaken
: to remove the androecium of (a flower) in the process of artificial cross-pollination
— emas·cu·late \-lət\ adjective
— emas·cu·la·tion \-ˌmas-kyə-ˈlā-shən\ noun
— emas·cu·la·tor \-ˈmas-kyə-ˌlā-tər\ noun
See emasculate defined for English-language learners
See emasculate defined for kids
Examples of EMASCULATE
- He plays the role of a meek husband who has been emasculated by his domineering wife.
- Critics charged that this change would emasculate the law.
Origin of EMASCULATE
Latin emasculatus, past participle of emasculare, from e- + masculus male — more at male
Related to EMASCULATE
Rhymes with EMASCULATE
abbreviate, abominate, accelerate, accentuate, accommodate, acculturate, accumulate, adjudicate, adulterate, affiliate, agglomerate, alienate, alleviate, alliterate, amalgamate, ameliorate, amyl nitrate, annihilate, annunciate, anticipate, apostolate, appreciate, appropriate, approximate, arpeggiate, articulate, asphyxiate, assassinate, asseverate, assimilate, associate, at any rate, attenuate, authenticate, barbiturate, bicarbonate, calumniate, capacitate, capitulate, catholicate, certificate, coagulate, coelenterate, collaborate, commemorate, commiserate, communicate, compassionate, concatenate, conciliate, confabulate, confederate, conglomerate, congratulate, consolidate, contaminate, cooperate, coordinate, corroborate, deactivate, debilitate, decapitate, decelerate, decerebrate, deconcentrate, deconsecrate, decorticate, decrepitate, de-escalate, defibrinate, defoliate, degenerate, deliberate, delineate, demodulate, denominate, depopulate, depreciate, deracinate, deregulate, desegregate, desiderate, detoxicate, devaluate, diaconate, dilapidate, discriminate, disintegrate, disseminate, dissimulate, dissociate, domesticate, effectuate, ejaculate, elaborate, electroplate, eliminate, elucidate, emaciate, emancipate, encapsulate, enumerate, enunciate, episcopate, equivocate, eradicate, etiolate, evacuate, evaluate, evaporate, eventuate, eviscerate, exacerbate, exaggerate, exasperate, excited state, excogitate, excoriate, exfoliate, exhilarate, exonerate, expatiate, expatriate, expectorate, expostulate, expropriate, extenuate, exterminate, extrapolate, facilitate, felicitate, fish or cut bait, garrison state, gesticulate, habilitate, habituate, hallucinate, humiliate, hydrogenate, hypothecate, illuminate, impersonate, inactivate, inaugurate, incarcerate, incinerate, incorporate, incriminate, indoctrinate, inebriate, infatuate, infuriate, ingratiate, ingurgitate, initiate, inoculate, inseminate, insinuate, instantiate, intercalate, interpolate, interrelate, interrogate, intimidate, intoxicate, invalidate, investigate, invigorate, irradiate, Italianate, Korea Strait, lanceolate, legitimate, luxuriate, mandarinate, manipulate, matriarchate, matriculate, Merthiolate, necessitate, negotiate, noncandidate, obliterate, officiate, Orange Free State, orientate, originate, oxygenate, participate, particulate, patriarchate, patriciate, perambulate, peregrinate, perpetuate, pontificate, precipitate, predestinate, predominate, prefabricate, premeditate, preponderate, prevaricate, procrastinate, prognosticate, proliferate, propitiate, proportionate, quadruplicate, quintuplicate, reciprocate, recriminate, recuperate, redecorate, reduplicate, reeducate, refrigerate, regenerate, regurgitate, reincarnate, reintegrate, reiterate, rejuvenate, remunerate, repatriate, repudiate, resuscitate, retaliate, reticulate, revaluate, reverberate, scholasticate, second estate, self-flagellate, self-immolate, self-pollinate, seventy-eight, sextuplicate, Singapore Strait, sophisticate, subordinate, substantiate, syllabicate, tergiversate, transliterate, triangulate, vanity plate, variegate, vaticinate, vituperate, vociferate
transitive verb emas·cu·late \i-ˈmas-kyə-ˌlāt\ (Medical Dictionary)
Medical Definition of EMASCULATE
—emas·cu·la·tion \-ˌmas-kyə-ˈlā-shən\ noun
Learn More About EMASCULATE
Next Word in the Dictionary: embalePrevious Word in the Dictionary: EmarginulaAll Words Near: emasculate
Ask The Editor Videos
Seen & Heard
What made you want to look up emasculate? Please tell us where you read or heard it (including the quote, if possible).


text:
On View: Toilet Dish in Two Parts in the Form of a Fish
A container for cosmetics or possibly medical ointment, this covered dish represents a tilapia fish. The tilapia symbolized fertility and wa...
Hiroshige's One Hundred Famous Views of Edo
Hiroshige's 118 woodblock landscape and genre scenes of mid-nineteenth-century Tokyo, is one of the greatest achievements of Japanese art.
Ray Komai's molded plywood chair was manufactured in Brooklyn in 1949, using the latest American technology. Although European designers suc...
200 Eastern Parkway
Brooklyn, New York 11238-6052
Eastern Parkway/Brooklyn Museum
Wednesday: 11 a.m.–6 p.m.
Thursday: 11 a.m.–10 p.m.
Friday–Sunday: 11 a.m.–6 p.m.


text:
- Musician's Friend Best Selection, Price & Service. Guaranteed.
Call our Gear Heads
at: 800-449-9128
Call our Gear Heads
at: 800-449-9128
A unique, beautiful and eccentric line of guitar straps.
The GORGI Guitar Strap from Get'm Get'm is a stylish and comfortable alternative to your everyday guitar strap. A unique glitter pattern, beautiful color combinations, quality fabrics, genuine leather tips and metal hardware give you form and function. It's also adjustable up to 54", which makes it perfect for all players no matter how big or small.
Get yours today!
Reviewed by 1 customer
Best Uses
Comments about Get'm Get'm GORGI Guitar strap:
Get'm Get'm makes some fantastic straps that should suit all tastes for those looking for high quality, easy to use and adjustable for players of all sizes from small to large.
Our product catalog varies by country due to manufacturer restrictions. If you change the Ship-To country, some or all of the items in your cart may not ship to the new destination.


text:
sony vaio, touchpad behaving badly ?
by AA90278 - 6/16/07 3:53 PM
I have a sony vaio SZ48, it is 4 months old, it came pre-loaded with vista business -
Recently I have noticed that if I am using a USB mouse, things seem fine, but If i am using the touch-pad, the cursor on the screen seems to move in the total opposite direction to what I want..
That is, if I scroll up, it goes down.. if i scroll right, it goes left ?
Has anybody else had this issue ? any solutions ?
Please help..... thankyou.


text:
Writing Installation XML Files
What You Need
Your editor
In order to write your XML installation files, you just need a plain text editor. Of course it's always easier to work with color coded text, so you might rather want to work with a text editor having such a feature. Here is a list of free editors that work well :
- Jext : http://www.jext.org/
- JEdit : http://www.jedit.org/
- classics like Vim and (X)Emacs.
If you are a developer and tend to write your own patches, extension or features to IzPack sources, or, if you wish to debug your compilation, installation and uninstallation, we recommend these IDE:
- IntelliJ IDEA : http://www.jetbrains.com/idea/
- Eclipse : http://www.eclipse.org/
- Netbeans : http://www.netbeans.org/
For the first one, JetBrains has granted us an Open Source License. All project members can ask the Licence Key to one of the project manager.
The other ones are well know open source projects (Just like us ). We provide a tutorial on how to develop/debug IzPack using Eclipse in the chapter Getting Started > How to develop and debug IpPack using Eclipse
Writing XML
Though you might not know much about XML, you have certainly heard about it. If you know XML you can skip this subsection as we will briefly present how to use XML.
XML is a markup language, really close to HTML. If you've ever worked with HTML the transition will be fast. However there are a few little things to know. The markups used in XML have the following form :
<markup>. Each markup has to be closed somewhere with its ending tag :
</markup>. Each tag can contain text and other markups. If a markup does not contain anything, it is just reported once :
<markup/>. A markup can contain attributes like :
<markup attr1="123" attr2="hello !"/>. Here is a sample of a valid XML structure :
You should be aware of the following common mistakes :
markups*are case sensitive :
<markup> is different from
you*must close the markups in the same order as you create them :
<m1><m2>(...)</m2></m1> is right but
<m1><m2>(...)</m1></m2> is not.
Also, an XML file must start with the following header :
<?xml version="1.0" encoding="iso-8859-1 standalone="yes" ?>. The only thing you should modify is the encoding (put here the one your text editor saves your files to). The
standalone attribute is not very important for us.
This (brief !) introduction to XML was just meant to enable you to write your installation specification. For a better introduction there are plenty of books and articles/tutorials dealing with XML on the Internet, in book stores, in magazines and so on.
Variable Substitution
During the installation process IzPack can substitute variables in various places with real values. Obvious targets for variable substitution are resource files and launch scripts, however you will notice many more places where it is more powerful to use variables rather then hard coded values. Wherever variables can be used it will be explained in the documentation.
There are three types of variables:
- Built-In variables. These are implemented in IzPack and are all dynamic in nature. This means that the value of each variable depends on local conditions on the target system.
- Environment variables. These are provided by the operating system the installer is run on.
- Variables that you can define. You also define the value, which is fixed for a given installation file.
You define your own variables in the installation XML file with the
<variable> tag. How to do this is explained in detail later in this chapter.
Please note that when using variables they must always appear with a '
$' sign as the first character, even though they are not defined this way.
The Built-In Variables
The following variables are built-in :
$INSTALL_PATH: the installation path on the target system, as chosen by the user
$INSTALL_DRIVE: the drive letter part of the installation path on the target system, set on Windows systems, only (for instance
$APPLICATIONS_DEFAULT_ROOT: the default path for applications
$JAVA_HOME: the JavaTM virtual machine home path
$CLASS_PATH: the Class Path used mainly for Java Applications
$USER_HOME: the user's home directory path
$USER_NAME: the user name
$APP_NAME: the application name
$APP_URL: the application URL
$APP_VER: the application version
$ISO3_LANG: the ISO3 language code of the selected langpack.
$IP_ADDRESS: the IP Address of the local machine.
$HOST_NAME: the HostName of the local machine.
$FILE_SEPARATOR: the file separator on the installation system
$DesktopShortcutCheckboxEnabled: When set to true, it automatically checks the "Create Desktop Shortcuts" button. To see how to use it, go to `The Variables Element
<variables>Be careful this variable is case sensitve !
$InstallerFrame.logfilePath: The path to the install log. This file contains the paths of all installed files. If set to "default" then the "$INSTALL_PATH/Uninstaller/install.log" path will be used. To see how to use it, go to `The Variables Element
<variables>. If this variable is not set, no install.log will be created.
Environment Variables
Environment variables can be accessed via the syntax
}. The curly braces are mandatory. Note that variable names are case-sensitive and usually in UPPER CASE.
Example: To get the value of the OS environment variable "CATALINA_HOME", use
Dynamic Variables
Dynamic variables can be defined in the installation XML with the
<variable> tag inside the
<dynamicvariables> element. The value of dynamic variables will be evaluated every time a panel is switched, i.e. between the panels. Dynamic variables can have a condition which will be evaluated first. If it's true, the value would be assigned, otherwise nothing happens to the variable.
As and addition to normal variables, the value of a variable can either be defined by using the value attribute or by using a child element called value.
Example1: To change a certain directory based on user input, use the following
<variable name="test" value="/test/${USER_INPUT}" condition="hasuserinput" /> The condition has userinput has to be specified in the condition section of installation XML.
Example2: To comment out something in a xml file if a certain pack with id mycoolfeature is not activated, you could use "two" dynamic variables to create a xml comment or not.
The condition izpack.selected.mycoolfeature is generated automatically when a pack with id mycoolfeature was specified. You would now use
${XML_Comment_Start} and
${XML_Comment_End} in a file which should be parsed.
Parse Types
Parse types apply only when replacing variables in text files. At places where it might be necessary to specify a parse type, the documentation will mention this. Depending on the parse type, IzPack will handle special cases such as escaping control characters correctly. The following parse types are available:
plain- use this type for plain text files, where no special substitution rules apply. All variables will be replaced with their respective values as is.
javaprop- use this type if the substitution happens in a Java properties file. Individual variables might be modified to function properly within the context of Java property files.
java- use this type for Java files.
xml- use this type if the substitution happens in a XML file. Individual variables might be modified to function properly within the context of XML files.
shell- use this type if the substitution happens in a shell script. Because shell scripts use
$variablethemselves, an alternative variable marker is used:
at- use this type if the substitution must occure on files where paramters are marked with leading AT characters. The example:
ant- use this type if the substitution must occure on files where parameters are surrounded with AT characters (similar to ANT filters, hence the type name). The example:
Unless using braces to surround variable's name (
${variable} or
%{variable}}, the variable name can contain following characters: letters, digits, dots, dashes , underbars (_). Example:
If you want to have two variables separated by character that is allowed to appear in variable name, for example:
$major-version.$minor-version, then you must use braces, and the above example should look like:
The IzPack Elements
When writing your installer XML files, it's a good idea to have a look at the iZPACK installation DTD.
The Root Element
The root element of an installation is
<installation>. It takes one required attribute :
version. The attribute defines the version of the XML file layout and is used by the compiler to identify if it is compatible with the XML file. This should be set to 1.0 for the moment.
The Information Element
This element is used to specify some general information for the installer. It contains the following elements :
<appname>: the application name
<appversion>: the application version
<appsubpath>: the subpath for the default of the installation path. A variable substitution and a maskable slash-backslash conversion will be done. If this tag is not defined, the application name will be used instead.
<url>: the application official website url
<authors>: specifies the author(s) of the application. It must contain at least one
<author>element whose attributes are :
name: the author's name
<uninstaller>: specifies whether to create an uninstaller after installation, and which name to use for it. This tag has the
writeattribute, with default value
yes. If this tag is not specified, the uninstaller will still be written. The
nameattribute can be used to change the default name of the generated uninstaller, i.e.
uninstaller.jar. The
conditionattribute can be used to specify a condition which has to be fullfilled for creating the uninstaller. The
pathattribute can be used to define the destination path where the uninstaller is written to, i.e.
<javaversion>: specifies the minimum version of Java required to install your program. Values can be
1.4, etc. The test is a lexical comparison against the
java.versionSystem property on the install machine.
<requiresjdk>: (yes or no) specifies wether a JDK is required for the software to be installed and executed. If not, then the user will be informed and given the option to still proceed with the installation process or not.
<webdir>: Causes a web installer to be created, and specifies the URL packages are retrieved from at install time. The content of the tag must be a properly formed URL.
<summarylogfilepath>: specifies the path for the logfile of the `SummaryLoggerInstallerListener`.
<writeinstallationinformation>: (yes or no) specifies if the file .installinformation should be written which includes the information about installed packs. The default if not specified is yes.
<pack200/>: adding this element will cause every JAR file that you will add to your packs to be compressed using Pack200 (see http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/pack200.html). As a special exception, signed JARs are not compressed using Pack200, as it would invalidate the signatures. This makes the compilation process a little bit longer, but it usually results in drasticaly smaller installer files. The decompression is relatively fast. Please note that Pack200 compression is destructive, i.e., after decompression a JAR won't be identical to its original version (yet the code in the class files remains semantically equivalent).
<run-privileged/>: adding this element will make the installer attempt to launch itself with administrator permissions. Il also supports a
conditionattribute to reference a condition id so that the elevation is not always attempted (e.g., you may want to activate it only for Windows Vista). This is not supported on all platforms, in which case a message will be provided to the user before continuing the installation. You can disable this feature for the uninstaller by specifying
uninstaller="yes"as an attribute. Only use this feature if you really need to be an administrator as part of your installation process.
<rebootaction>: defines what to do if there were pending file operations left which require a reboot; otherwise any of the options below will be ignored. Possible values are:
ignore(default): Doesn't reboot at all even if there are pending operations. Pending operations can be recognized only on the installer command line output (for all options).
notice: Doesn't reboot, but notices the user interactively at the end of an installation, which must be confirmed. Notification works only for interactive installation types (no auto-installation).
ask: Reboots only if the user confirms it interactively at the end of an installation.
always: Reboots always without any confirmation at the end of an installation.
- The usage of
<rebootaction>is bound to using the attribute blockable_ with the values
forceat least in one of the elements
<fileset>, for being able to recognize blocked files before IzPack tries to overwrite them (which would result in a failing installation of the file). See the documentation of these elements later.
<rebootaction>works and makes sense only on Windows, where target files (as device drivers, EXE or DLL files) might be blocked during an installation. On other platforms than Windows the
<rebootaction>element will be ignored.
<rebootaction>supports the
conditionattribute to limit reboot processing on particular conditions.
- Without setting at least one attribute blockable =
autoor blockable =
forcerebootaction will not have any effect.
See also the description of the blockable_ attribute.
For getting more information see the chapter Advanced features.
- The usage of
Here is an example of a typical
<info> section :
Here is one where the privileges elevation is attempted on Windows Vista and Mac OS X :
The Packaging Element
This element allows to specify packaging options. If not specified, the default will be to create an all in one installer. This element will usually be used to create an installer which spans over multiple volumes, e.g. the output will be two CDs. The packaging-element contains the following elements:
<packager>: specifies options used by the packager. The packager tag has the
classattribute, which specifys the class to use for packaging. Currently two implementations are available (com.izforge.izpack.compiler.packager.impl.Packager, com.izforge.izpack.compiler.packager.impl.MultiVolumePackager). The packager-element can contain the
<options>element which can have different attributes for the different implementations of packagers. For the MultiVolumePackager, it can have the following attributes:
volumesize: the size of the volumes
firstvolumefreespace: free space on the first volume used for the installer jar and additional resources like readme-files etc.
<unpacker>: specifies which unpacker class should be used. Currently there are two unpacker implementations (com.izforge.izpack.compiler.UnPacker, com.izforge.izpack.compiler.MultiVolumeUnPacker).
Here's an example how to specify an installer which will create multiple volumes. In this example the volumes shall be CDs with 650 megabytes. There will be an additional free space of 150 megabytes on the first volume. This will result in the creation of an installer.jar and multiple installer.pak* files. The installer.jar plus installer.pak plus the additional resources have to be copied on the first volume, each installer.pak.<number> on several volumes.
The Variables Element
This element allows you to define variables for the variables substitution system. Some variables are built-in, such as
$INSTALL_PATH (which is the installation path chosen by the user). When you define a set of variables, you just have to place as many
<variable> tags in the file as needed. If you define a variable named
VERSION you need to type $VERSION in the files to parse. The variable substitutor will then replace it with the correct value. One
<variable> tag take the following attributes :
name: the variable name
value: the variable value
Here's a sample
<variables> section :
Here's a precise sample on how to use desktopshortcutcheckboxenabled and InstallerFrame.logfilePath variables:
The dynamic Variables Element
This element allows you to define dynamic variables for the variables substitution system. In contrast to the static
<variables, dynamic variables will be evaluated every time, a panel switch is done.
When you define a set of variables, you just have to place as many
<variable> tags in the file as needed. Normally you would use the condition attribute to specify, when a certain value will be set.
<variable> tag take the following attributes :
name: the variable name
value: the variable value
condition: a condition for this variable, which has to be true to set the value
Here's a sample
<dynamicvariables> section :
The Conditions Element
This element allows you to define conditions which can be used to dynamically change the installer, e.g. the panels shown, the variables set, files parsed, files executed and much more. When you define a condition it will get a type and an id. The id has to be unique. Conditions can be referenced based on this id (e.g. with the
There are several built-in types of conditions. At the time of writing this, Izpack has the following built-in types:
VariableCondition: a condition based on the value of a certain variable
PackSelectionCondition: a condition based on a pack selected for installation
JavaCondition: a condition based on a static java field or method.
CompareNumericsCondition: a condition based on the comparison of a certain variable with a given value and operator.
There are also boolean types to combine more than one condition:
AndCondition: both conditions have to be true
OrCondition: only one of both conditions has to be true
XOrCondition: one condition has to be true, the other one has to be false
NotCondition: the condition has to be false
When you define a set of conditions, you just have to write as many
<condition> tags as you like. A condition can take the following attributes:
type: the type of the condition. For built-in types, this is the lowercase portion of the condition class
- : name without condition appended (variable,packselection,java, ...). Custom condition types should be referenced by the full qualified class name, e.g. de.dr.rules.MyCoolCondition.
id: the id of the condition. This will be used to refer to this conditions in other elements
The condition element can have several child elements depending on the type of this conditions. E.g. the VariableCondition has a name and value child element to specify, which variable should have a certain value to fullfil this condition.
This is an example which defines four conditions, two VariableConditions, a JavaCondition and a AndCondition which will refer to two of the first conditions.
Note, from IzPack 3.11 on normally, you don't have to define the compound conditions because you can use a simple expression language. The language has the following operators:
- {+}: an operator for the Andcondition
|: an operator for the OrCondition
- {{}}: an operator for the XOrCondition
!: an operator for the NotCondition
Neverthless if you define really complex conditions it's much easier to define them using the xml structure.
More types of conditions can be defined by inheriting com.izforge.izpack.Condition class.
Built-in conditions
A number of built-in condition IDs are available for you.
The OS is Windows (any variant)
The OS is Windows XP
The OS is Windows Server 2003
The OS is Windows Vista
The OS is Windows 7
The OS is Linux (any variant)
The OS is Solaris (any variant)
The OS is Solaris (any x86 variant)
The OS is Solaris (any Sparc variant)
The Installer Requirements Element
This element allows to specify requirements for running the installation. This will be done based on conditions defined in the conditions section.
An installer requirement consists of a condition and a message which will be shown if the condition is not fulfilled. If so, the installer will show the message and exit after that.
installerrequirement: specifies a single installer requirement. You can define an unlimited number of them.
Installerrequirements have the following attributes: -
condition: an id of a condition defined in the conditions section -
message: a message text or a langpack key defining which message should be shown before exiting the installer in case of a missing requirement.
The GUI Preferences Element
This element allows you to set the behavior of your installer GUI. This information will not have any effect on the command-line installers that will be available in future versions of IzPack. The arguments to specify are :
resizable: takes
noand indicates whether the window size can be changed or not.
width: sets the initial window width
height: sets the initial window height.
Here's a sample :
Starting from IzPack 3.6, the look and feel can be specified in this section on a per-OS basis. For instance you can use the native look and feels on Win32 and OS X but use a third-party one on Unix-like platforms. To do that, you have to add some children to the
guiprefs tag:
laf: the tag that specifies a look and feel. It has a
nameparameter that defines the look and feel name.
- Each
lafelement needs at least one
ostag, specified like in the other parts of the specification that support this tag.
- Like you can add
oselements, you can add any number of
paramelements to customize a look and feel. A
paramelements has two attribues:
The available look and feels are:
- Kunststoff:
- Liquid:
- Metouia:
- JGoodies Looks:
- Substance:
If you don't specify a look and feel for a particular operating system, then the default native one will be used: Windows on Windows, Aqua on Mac OS X and Metal on the Unix-like variants.
The Liquid Look and Feel supports the following parameters:
yesmeans that it will render the frames in Liquid style
yesmeans that it will render the dialogs in Liquid style
The JGoodies Looks look and feel can be specified by using the
variant parameters. The values can be one of:
windows: use the Windows look
plastic: use the basic Plastic look
plastic3D: use the Plastic 3D look
plasticXP: use the Plastic XP look (default).
Here is a small sample:
The Substance look and feel toned-down themes can be specified using the
variant parameter, with the value being one of:
business, business- blue, business-black, creme, sahara, moderate, officesilver. We have reduced the choice to the toned-down themes since they are the only ones to actually look decent (the other families colors are way too saturated). Please consult https://substance.dev.java.net/docs/skins/toneddown.html for a gallery of the different toned-down themes.
Starting from IzPack 3.7, some characteristics can be customized with the
<modifier> tag. There is a separate description in the `Advanced Features` chapter paragraph `Modifying the GUI`.
The Localization Element
This element is used to specify the language packs (langpacks) that you want to use for your installer. You must set one
<langpack> markup per language. This markup takes the
iso3 parameter which specifies the iso3 language code.
Here's a sample :
The supported ISO3 codes are :h3. h4. h4. h4. h2. ISO3 code Language h4. h4. h4. cat Catalunyan chn Chinese cze Czech dan Danish glg Galician deu German eng English eus Basque fin Finnish fra French hun Hungarian ita Italian jpn Japanese mys Malaysian ned Nederlands nor Norwegian pol Polnish por Portuguese (Brazilian) prt Portuguese (European) rom Romanian rus Russian scg Serbian spa Spanish svk Slovakian swe Swedish ukr Ukrainianh3. h4. h4.h3. The Resources Element
<resources> h3. Several panels, such as the license panel and the shortcut panel, require additional data to perform their task. This data is supplied in the form of resources. This section describes how to specify them. Take a look at each panel description to see if it might need any resources. Currently, no checks are made to ensure resources needed by any panel have been included. The
<resources> element is not required, and no
<res> elements are required within. The
<resources> element is the only element besides the
<packs> element that is taken into consideration in referenced pack-files (see
`<packs> element`_ for more info)
You have to set one
<res> markup for each resource. Here are the attributes to specify :
src: the path to the resource file which can be named freely of course (for instance
id: the resource id, depending on the needs of a particular panel
parse: takes
no(default is
no) - used to specify whether the resource must be parsed at the installer compilation time. For instance you could set the application version in a readme file used by
type: specifies the parse type. This makes sense only for a text resource - the default is
plain, other values are
javaprop, xml, plain, java, shell, at, ant(Java properties file and XML files)
encoding: specifies the resource encoding if the receiver needs to know. This makes sense only for a text resource.
Here's a sample :
Please note that in general a resource
id is unique. Thus if you define multiple resources with the same
id the later definition (e.g. a resource defined in a referenced pack-file) will overwrite the previous definition. However there is an exception for
packsLang.xml_xyz files (see `Internationalization of the PacksPanel`). If multiple packsLang-files were defined, all files will be merged into a single temporary file. This allows
refpack files to provide their own internationalization-information.
You can define bundles of resources by using
<bundle> You have to set a unique id for the bundle
id. One bundle can be marked to be default:
You need to define a variable to set the name of the SystemProperty:
Here's a sample:
; <variables>
... <variable name="resource.bundle.system.property" value="BUNDLE_NAME" />
</variables> ... <resources> <
Unable to render embedded object: File (-- bundle 1 --> <bundle id="bundle1" default="yes"> <res id="Heading.image" src="path1/HeadingImage.png" /> <res id="installer.langsel.img" src="path1/langselImage.png" /> </bundle> <) not found.
-- bundle 2 -> <bundle id="bundle2"> <res id="Heading.image" src="path2/HeadingImage.png" /> <res id="installer.langsel.img" src="path2/langselImage.png" /> </bundle> <!- common resources --> <res id="resource.id" src="path.to.resource" /> ...
Resources will be then be loaded in the following order:
The Panels Element
<panels> h3. Here you tell the compiler which panels you want to use. They will appear in the installer in the order in which they are listed in your XML installation file. Take a look at the different panels in order to find the ones you need. The
<panel> markup takes the following attributes:
classname: which is the classname of the panel.
id: an identifier for a panel which can be used e.g. for referencing in userinput panel definitions.
condition: an id of a condition which has to be fullfilled to show this panel
jar: jar file where the classes for this panel can be found. This attribute is optional. If it is empty (jar="") the classes for this panel must be murged using the <jar> tag.
Here is a sample :
The following sections describe the tags available for a
<panel> section.
<help> - optional file for a help h3. The content of the help file is shown in a small window on the panel, when User clicks on the help button. The button is only shown, when a help in the language exists.
<help> takes the following attributes :
iso3: iso3 representation of the language the help is written
src: path to the help file to display
Here's a sample :
<validator> - optional validation on idata h3. This validation is done, when going on for the next panel. It is also done in case of an automatic installation. The class must implement the interface com.izforge.izpack.api.installer.DataValidator.
<validator> takes the following attributes :
classname: The class implementing com.izforge.izpack.api.installer.DataValidator
Here's a sample :
<actions> - optional actions for the panel h3. Here you can define multiple actions that are done during the lifetime of the panel. The class must implement the interface com.izforge.izpack.installer.PanelAction. The actions are also called during an automated installation.
<actions> tag has no attributes but has
<action> markups with the following attributes :
stage: The stage when the action should be triggered. Possible values are
classname: The class implementing com.izforge.izpack.installer.PanelAction
Here's a sample :
The Packs Element
<packs> h3. This is a crucial section as it is used to specify the files that need to be installed. The
<packs> section consists of several
<refpack> and
<refpackset> tags.
<pack> takes the following attributes :
name: the pack name
required: takes
noand specifies whether the pack is optional or not.
os: optional attribute that lets you make the pack targeted to a specific operating system, for instance
macand so on.
preselected: optional attribute that lets you choose whether the pack is by default selected for installation or not. Possible values are
no. A pack which is not preselected needs to be explicitly selected by the user during installation to get installed.
loose: can be used so that the files are not located in the installer Jar. The possible values are
false, the default beeing
false. The author of this feature needed to put his application on a CD so that the users could run it directly from this media. However, he also wanted to offer them the possibility to install the software localy. Enabling this feature will make IzPack take the files on disk instead of from the installer. Please make sure that your relative files paths are correct !
id: this attribute is used to give a unique id to the pack to be used for internationalization via
packImgId: this attribute is used to reference a unique resource that represents the pack's image for the ImgPacksPanel. The resource should be defined in the
<resources>element of the installation XML using the same value for the
idattribute of the
condition: an id of a condition which has to be fullfilled to install this package.
hidden: takes
falseand specifies whether the pack shall be shown in the packs panel. The bytes of such a hidden pack will be used to calculate the required space, but the pack itself won't be shown. A hidden pack can be selected conditionally. So you have to specify a condition to enable it for installation. The default for this attribute is
<refpack> takes only one attribute
file, which contains the relative path (from the installation compiler) to an externally defined packs-definition. This external packs definition is a regular IzPack installation XML. However the only elements that are used from that XML file are the
<packs> and the
<resources> elements. This enables a model in which a single developer is responsible for maintaining the packs and resources (e.g. separate
packsLang.xml_xyz files providing internationalization; see `Internationalization of the PacksPanel`) related to the development-package assigned to him. The main install XML references these xml-files to avoid synchronization efforts between the central installation XML and the developer-maintained installer XMLs.
<refpackset> tag can be used in situations were there is no predefined set of
<refpack> files, but a given directory should be scanned for
<refpack> files to be included instead. This element takes the following parameters:
dir: the base directory for the refpackset (relative path)
includes: a pattern of files in
<refpack>format that must be included
An example:
Internationalization of the PacksPanel h3. In order to provide internationalization for the PacksPanel, so that your users can be presented with a different name and description for each language you support, you have to create a file named
packsLang.xml_xyz where
xyz is the ISO3 code of the language in lowercase. Please be aware that case is significant. This file has to be inserted in the resources section of
install.xml with the
id and
src attributes set at the name of the file. The format of these files is identical with the distribution langpack files located at
$IZPACK_HOME/bin/langpacks/installer. For the name of the panel you just use the pack
id as the txt
id. For the description you use the pack
id suffixed with
An example:
packsLang.xml_eng file: file:
The following sections describe the tags available for a
<pack> section.
<description> - pack description h3. The contents of the
<description> tag describe the pack contents. This description is displayed if the user highlights the pack during installation.
<depends> - pack dependencies h3. This can be used to make this pack selectable only to be installed only if some other is selected to be installed. The pack can depend on more than one by specifying more than one
<depends> elements. Circular depedencies are not supported and the compiler reports an error if one occurs.
This tag takes the following attribute:
packname: The name of the pack that it depends on
<os>- OS restrictions h3. It is possible to restrict a panel to a certain list of operating systems. This tag takes the following attributes:
family: unix, windows or mac
name: the exact OS name (ie Windows, Linux, ...)
version: the exact OS version (see the JVM
arch: the machine architecture (see the JVM
<updatecheck>h3. This feature can update an already installed package, therefore removing superfluous files after installation. Here's how this feature author (Tino Schwarze) described it on the IzPack development mailing-list:
> Each pack can now specify an
<updatecheck> tag. It supports a subset of ant fileset syntax, e.g.:
> If the paths are relative, they will be matched relative to
$INSTALL_PATH. Update checks are only enabled if at least one
<include> is specified. See
com.izforge.izpack.installer.Unpacker for details.
<file> - add files or directories h3. The
<file> tag specifies a file (a directory is a file too) to include into the pack. It takes the following attributes:
src: the file location (relative path) - if this is a directory its content will be added recursively. It may contain previously defined static variables (see
targetdir: the destination directory, could be something like
os: can optionally specify a target operating system (
unix, windows, mac) - this means that the file will only be installed on its target operating system
override: if
truethen if the file is already installed, it will be overwritten (use
falseotherwise). Alternative values:
askfalse-ask the user what to do and supply default value for non-interactive use. Another possible values is
update. It means that the new file is only installed if it's modification time is newer than the modification time of the already existing file (note that this is not a reliable mechanism for updates - you cannot detect whether a file was altered after installation this way.) By default it is set to
blockable: Defines whether and how blocked target files on Windows should be recognized. This might result in pending file operations which require a system reboot. The reboot behavior at the end of an installation for pending file operations can be set using the nested rebootaction_ in the
infoelement. See above for possible reboot options. Possible values:
none(default): No recognition of blocked target files will be done at all, this is the default behavior of previous IzPack versions.
auto: Automatic recognition of a blocked target file by the operating system, resulting in leaving a pending file operation to be finished after system reboot. Using
autothis applies only for files that are really blocked, the other files are copied normally, which can result in mixed, old and new target files at the end of the installation, unless the system won't be really rebooted.
force: Forces target file to be always assumed a blocked, resulting in leaving a pending file operation to be finished after system reboot. Using
forcethis applies for each file, regardless whether it is really blocked during installation. This makes sense if you don't want to mix files old and new files at the end of the installation to not disturbing a running process, but having the complete set of target files installed after system reboot.
- Using
blockabledoes not necessarily force you to limit such files on Windows systems. For multi-platform installations there is a compiler warning thrown that
blockablewill be ignored on non-Windows systems.
- The native library
WinSetupAPImust be explicitely included using this feature.
For setting up the according reboot behaviour see the rebootaction_ element.
For getting more information see the chapter Advanced features.
- Using
unpack: if
trueand the file is an archive then its content will be unpacked and added as individual files
condition: an id of a condition which has to be fullfilled to install this file
<additionaldata>h3. This tag can also be specified in order to pass additional data related to a file tag for customizing.
<key>: key to identify the data
<value>: value which can be used by a custom action
<singlefile>- add a single file h3. Specifies a single file to include. The difference to
<file>is that this tag allows the file to be renamed, therefore it has a
targetattribute instead of
src: the file location (relative path). It may contain previously defined static variables (see
target: the destination file name, could be something like
os: can optionally specify a target operating system (
unix, windows, mac) - this means that the file will only be installed on its target operating system
override: see
<file>for description
blockable: see
<file>for description
condition: an id of a condition which has to be fullfilled to install this file
<additionaldata> tag can also be specified for customizing.
<fileset>: add a fileset h3. The
<fileset> tag allows files to be specified using the powerful Jakarta Ant set syntax. It takes the following parameters:
dir: the base directory for the fileset (relative path)
targetdir: the destination path, works like for
casesensitive: optionally lets you specify if the names are case-sensitive or not - takes
defaultexcludes: optionally lets you specify if the default excludes will be used - takes
os: specifies the operating system, works like for
override: see
<file>for description
blockable: see
<file>for description (applied for all files in the fileset)
includes: comma- or space-separated list of patterns of files that must be included; all files are included when omitted. This is an alternative for multiple include tags.
excludes: comma- or space-separated list of patterns of files that must be excluded; no files (except default excludes) are excluded when omitted. This is an alternative for multiple exclude tags.
condition: an id of a condition which has to be fullfilled to install the files in this fileset
You specify the files with
<include> and
<exclude> tags that take the
name parameter to specify the Ant-like pattern :
* : means any subdirectory
- : used as a wildcard.
Here are some examples of Ant patterns :
<include name="lib"/>: will include
liband the subdirectories of
<exclude name="
.java"/>: will exclude any file in any directory starting from the base path ending by
<include name="lib/
.jar"/>: will include all the files ending by
<exclude name="lib/
"/>: will exclude any file in any subdirectory starting from
libwhose name contains
There area set of definitions that are excluded by default file-sets, just as in Ant. IzPack defaults to the Ant list of default excludes. There is currently no equivalent to the <defaultexcludes> task. Default excludes are:
<additionaldata> tag can also be specified for customizing.
<parsable> - parse file(s) after installation h3. Files specified by
<parsable> are parsed after installation and may have variables substituted.
targetfile: the file to parse, could be something like
$INSTALL_PATH/bin/launch-script.shA slash will be changed to the system dependant path separator (e.g. to a backslash on Windows) only if no backslash masks the slash. No longer mandatory as a fileset of files can be used.
type: specifies the type (same as for the resources) - the default is
encoding: specifies the file encoding
os: specifies the operating system, works like for
condition: an id of a condition which has to be fullfilled to parse this file
One or more fileset tags can be used inside parsable to specify multiple files at once.
<executable> - mark file executable or execute it h3. The
<executable> tag is a very useful thing if you need to execute something during the installation process. It can also be used to set the executable flag on Unix-like systems. Here are the attributes :
targetfile: the file to run, could be something like
$INSTALL_PATH/bin/launch-script.shSlashes are handled special (see attribute
targetfileof tag
class: If the executable is a jar file, this is the class to run for a JavaTM program
jar(the default is
stage: specifies when to launch :
postinstallis just after the installation is done,
neverwill never launch it (useful to set the +x flag on Unix).
uninstallwill launch the executable when the application is uninstalled. The executable is executed before any files are deleted.
neveris the default value.
failure: specifies what to do when an error occurs :
abortwill abort the installation process,
ask(default) will ask the user what to do and
warnwill just tell the user that something is wrong
os: specifies the operating system, works like for
keep: specifies whether the file will be kept after execution. The default is to delete the file after is has been executed. This can be changed by specifying
condition: an id of a condition which has to be fullfilled to execute this file
<args> tag can also be specified in order to pass arguments to the executable:
<arg>: passes the argument specified in the
valueattribute. Slashes are handled special (see attribute
targetfileof tag
<os>- make a file OS-dependent h3. The
<os>tag can be used inside the
<executable>tags to restrict it's effect to a specific operating system family, architecture or version using the following attributes:
unix, windows, macto specify the operating system family
name: the operating system name
version: the operating system version
arch: the operating system architecture (for instance the Linux kernel can run on i386, sparc, and so on)
Here's an example installation file fragment:
The Native Element
<native> h3. Use this if you want to use a feature that requires a native library. The native libraries are placed under
bin/native/... There are 2 kinds of native libraries : the iZPACK libraries and the third-party ones. The IzPack libraries are located at
bin/native/izpack, you can place your own libraries at
bin/native/3rdparty. It is possible to place a native library also into the uninstaller.
It is usable from CustomActions. If one or more are referenced for it, the needed support classes are automatically placed into the uninstaller. To place it only on operating systems for which they are build, it is possible to define an OS restriction. This restriction will only be performed for the uninstaller. The markup takes the following attributes :
name: the library filename
stage: stage where to use the library (install|uninstall|both)
src: source directory where to find the library to build the installer
Note for developers:
com.izforge.izpack.util.Librarian.loadLibrary() must be used to load custom native libraries, as it performs some housekeeping.
<os> - make a library OS-dependent h3. The
<os> tag can be used to restrict the inclusion into the uninstaller to a specific operating system family, architecture or version. The inclusion into the installer will be always done.
Here's a sample :
The Jar Merging Element
<jar> h3. If you adapt iZPACK for your own needs, you might need to merge the content of another jar file into the jar installer. For instance, this could be a library that you need to merge. The
<jar> markup allows you to merge the raw content of another jar file into the installer and the uninstaller. It is necessary that the paths in the jars are unique because only the contained files of the jar are added to the installer jar, not the jar file self. The attributes are:
src: the path at compile time
stage: stage where to use the contents of the additional jar file (install|uninstall|both)
A sample :
XInclude-style constructs
The xi:include element is used to include xml or text documents in your configuration files.
The xi:include element can be used anywhere in pretty much any of the xml files used by IzPack. It is supported by the javax DocumentBuilder. It follows the XInclude recommandation produced by the W3C (http://www.w3.org/TR/xinclude/) and should be able to be used as decribed in that document.
To use the xi:include, you have to specify the namespace xmlns:xi="http://www.w3.org/2001/XInclude" in your xml.
If a logical error appear in an included file, the line number shown will indicate the xinclude element in the main xml file.
The xi:include element has the following attributes:
- href
The location of the file to include. If this is a relative path (e.g. href='../bob.xml') then the file is resolved relative to the document that includes the xinclude element. The href element can be a remote url (e.g. href='http://example.com/file.txt') but this is not recommended.
- parse
Indicates that the included file should be treated as xml, forcing the included file to be parsed (which results in all xinclude elements in the included file to also be included), or as text which includes the specified file as a text node. It can have a value of 'xml' or 'text' and defaults to 'xml' if ommitted.
- xpointer
In case in parse="xml", you can use xpointer to get a part of the included xml. The details of the xpointer framework can be found http://www.w3.org/TR/2003/REC-xptr-framework-20030325/.
- encoding
This is used when the parse attribute is 'text' to specify the character encoding of the included text document. It has no effect if parse is 'xml'.
- accept
Used if the href attribute specifies a url accessible via HTTP. The value of this attribute will be added as the accpet header on the HTTP request. The fallback element h3. The xi:fallback element is used to provide a fallback if the xi:include element fails. It can be empty or can contain a valid xml. If it is empty then a failure to include the specified document is supressed. If it contains a xml then a failure to include the specified document causes the xml specified in the fallback is parsed (evaluating nested xinclude elements) and inserted into the document in its place.
For example the following use of xi:include
will result in
if the file 'does-not-exist.xml' does indeed not exist. The xfragment element h1.
The xfragment element allows document fragments (xml documents without a single top level element) to be included. Simply use the xfragment as the top level element in the included document. It will be removed when the document is included.
e.g. If I want to use xi:include to include a file containing the following fragments:
I could use the xfragment element to enable it
For replacing Maven properties in attributes to xi:include in the standard notation of IzPack you need to prepare your POM as follows:
Example: Packaging type
pom is used in the POM:
and compile the installer from
${project.build.outputDirectory}/izpack-resources instead of src/main/izpack/.


text:
scienceBookmark This
The Learning and Behavioral Center, LLC
18663 Ventura Blvd suite 301
Tarzana, CA
DescriptionLearning & Behavioral Center, LLC is an organization dedicated to providing Applied Behavior Analytic treatments to children ages 18 months – 18 years of age. We are amongst the most experienced organizations effectively treating children with various disabilities including Autism, A.D.D., A.D.H.D., O.C.D., mental retardation and more. LBC is now offering unpaid internship positions for motivated, energetic, and caring individuals interested in working with children! Hours are very flexible.
ResponsibilitiesInterns will be trained and expected to take part in:
1:1 Therapy
Group Therapy
Parent Training
Staff Development
Home Sessions
School Sessions
Empowerment Workshops


text: The following reply was made to PR ports/152373; it has been noted by GNATS. From: Edwin Groothuis <edwin at FreeBSD.org> To: dierk at blaxxtarz.de Cc: bug-followup at FreeBSD.org Subject: Re: ports/152373: Update port: multimedia/ffmpegthumbnailer - Update to 2.0.4 Date: Thu, 18 Nov 2010 18:00:25 UT Maintainer of multimedia/ffmpegthumbnailer, Please note that PR ports/152373 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/152373 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin at FreeBSD.org