text:
Q: Using while loop statement create a program that enter 5 numbers and determine if it is a prime or not and then display the prime numbers only In my code I can only input 1 number. How to enter 4 additional numbers and determine if it's a prime or not and then display only the prime numbers.
#include<stdio.h>

int main()
{

    int n, c = 2, f = 1;

    printf("Enter a number:");
    scanf("%d", &n);

    while(c < n)
    {
        if(n%c == 0)
        {
            f = 0;
            break;
        }
        c++;
    }

    if(f) printf("%d is prime number\n\n", n);

    return 0;
}

Here is my output, using the code above:
Please enter a number:2

...Program finished with exit code 0
Press ENTER to exit console.

And here is the expected output:
Please enter a number:1

Please enter a number:2
2 is a prime number.

Please enter a number:3
3 is a prime number.

Please enter a number:4

Please enter a number:5
5 is a prime number.

A: Let's say you want to check 5 numbers whether they are prime or not.
The approach you followed, you just have to do the same for rest of the numbers.
To do that, you can run an additional loop. For example,
int inputSize = 5;
while(inputSize--)
{
    printf("Enter a number:");
    scanf("%d", &n);

    // now check if the number is prime or not
}

Note: Don't forget to initialize the values in proper place.
Sample code:
#include<stdio.h>

int main()
{
    int inputSize = 5;
    while(inputSize--)
    {
        int n, c = 2, f = 1;

        printf("Enter a number:");
        scanf("%d", &n);

        while(c < n)
        {
            if(n%c == 0)
            {
                f = 0;
                break;
            }
            c++;
        }

        if(f) printf("%d is prime number\n\n", n);
    }

    return 0;
}

Check out the following resource to know more about primality of a number
https://www.studytonight.com/c-programs/c-program-to-check-whether-a-number-is-prime-or-not

A: You need to read the numbers in a loop. You also need to check that the input really is a number. The function scanf returns the number of successfully read values. Try this:
#include <stdio.h>

int main(void)
{
    int c, ch, i, m, n;

    i = 0;
    while (i < 5) {
        printf("Enter a number: ");
        m = scanf("%d", &n);
        if (m == 1) {
            c = 2;
            while ((c < n) && (n % c != 0)) {
                c++;
            }
            if (c == n) {
                printf("%d is prime number\n", n);
            }
            putchar('\n');
            i++;
        } else {
            fprintf(stderr, "Not a number\n\n");
            do { ch = getchar(); } while (ch != '\n');
        }
    }
    return 0;
}

If the input is invalid we can give the user another chance. In this case we first need to read past the unread characters which represents the invalid input.
Also note that the algorithm can be improved by only inspecting numbers up to the square root of n.

A: It is evident that you need a loop with 5 iterations to enter 5 numbers.
As the notion of prime numbers is defined for natural numbers then you need to use an unsigned integer type to store entered numbers.
And your code is incorrect because for numbers 0 and 1 it outputs that they are prime numbers.
The program can look the following way.
#include <stdio.h>

int main( void )
{
    const size_t N = 5;

    for ( size_t i = 0; i < N; i++ )
    {
        printf( "Please enter a number: " );

        unsigned int n = 0;

        if ( scanf( "%u", &n ) == 1 )
        {
            int prime = n % 2 == 0 ? n == 2 : n != 1;

            for ( unsigned int i = 3; prime && i <= n / i; i += 2 )
            {
                prime = n % i != 0;
            }

            if ( prime ) printf( "%u is a prime number.\n", n );
        }
        else
        {
            while ( getchar() != '\n' );
        }

        putchar( '\n' );
    }
}

The program output might look like
Please enter a number: 1

Please enter a number: 2
2 is a prime number.

Please enter a number: 3
3 is a prime number.

Please enter a number: 4

Please enter a number: 5
5 is a prime number.


More than seventy years ago, five Nazi scientists embarked upon an expedition into the frozen Himalayas in search of the origins of the Aryan race. What they found instead was something beyond their wildest imaginations, a secret they would sooner take to their graves than risk releasing upon an unsuspecting world.
Now nearly a hundred years old, Johann Brandt, the lone surviving member of the original party, shares his discovery with Jordan Brooks, an evolutionary anthropologist, who launches his own expedition into one of the most dangerous environments on the face of the planet in search of the evidence Brandt claims to have left behind.
If Brooks and his team hope to find the proof, they'll have to follow the historical footsteps of the Germans into the hunting grounds of a species that evolved in utter geographical isolation, and their only hope for survival lies in uncovering the truth about the ill-fated Nazi expedition…for those who don't learn from the past are doomed to repeat it.
Live links will be posted tomorrow, August 5th!
This entry was posted on August 4, 2014 by evilanche. It was filed under Uncategorized and was tagged with Fearful Symmetry, Thunderstorm Books.


text:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<!--
	Ref [1] - http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/ClusterSetup.html#Installation
	Ref [2] - http://www.cloudera.com/content/cloudera/en/documentation/cdh5/v5-1-x/CDH5-Installation-Guide/cdh5ig_hdfs_cluster_deploy.html?scroll=topic_11_2_1_unique_1
-->
<!-- Put site-specific property overrides in this file. -->
<configuration>
	<!-- file system properties -->
	<property>
		<name>fs.defaultFS</name>
		<value>hdfs://namenode1:8020</value>
	</property>
	<property>
		<name>dfs.permissions</name>
		<value>false</value>
	</property>

	<!-- OOZIE proxy user setting -->
	<property>
		<name>hadoop.proxyuser.oozie.hosts</name>
		<value>*</value>
	</property>
	<property>
		<name>hadoop.proxyuser.oozie.groups</name>
		<value>*</value>
	</property>

	<!-- Proxy settings for History Server -->
	<property>
		<name>hadoop.proxyuser.mapred.groups</name>
		<value>*</value>
	</property>
	<property>
		<name>hadoop.proxyuser.mapred.hosts</name>
		<value>*</value>
	</property>

</configuration>

redpajama_set_name: RedPajamaGithub


wind chime stained glass sunflower chimes fused decorating tips and tricks.
best table settings decorations and centerpiece ideas for your christmas pictures decorating trends 2019 uk tables.
wrought iron windmill vintage retro black wall hanging home decor wal.
ten window box planter ideas with free building plans under flower boxes for brick.
screw hole plugs for doors i.
nautical and tropical ceiling fans fan khaki canvas blades previous in all blade.
white shutters on three small square windows in laundry room for sale.
metal wall art headboard living room decor outdoor w and sculptures.
wall decor above fireplace art over the decorations within.


text:
How to create a mailing list in Gmail
It's not a proper substitute for Mailchimp though.
Mark O'Neill
Emails are not always a one-on-one affair. Sometimes it's necessary to bring other people into the discussion, and Gmail makes this very easy. However, these days, with the rise of Slack, Asana, and other collaboration apps, group emailing is beginning to go out of vogue. Nevertheless, if you're holding on for dear life to the old ways, here's how to create a mailing list in Gmail, as well as group emails.
Also: 10 best email apps for Android to manage your inbox
To manually add email addresses to a new email, it's good practise to add them as BCC contacts. To do this, start typing in the BCC field all of the required emails, separated by a space. Alternatively, click the BCC field to the left, which will open up your Google Contacts. Tick the ones you want, and they will be auto-populated in the email. You can also set up a mailing list in Google Contacts and simply type the name of the mailing list into the email.
JUMP TO KEY SECTIONS
Adding email addresses manually to a new email window
Create a mailing list in Gmail and Google Contacts
If it's just a few email addresses you need to add to an email, it's faster to just manually type them in. You can do this by first opening up the BCC field in the email. Entering the email addresses as BCC means that they won't be revealed to the other email recipients. Type in each address, separated by a space.
Alternatively, if you don't know all of the email addresses from memory, click Bcc on the top left hand side, and it opens up your Google Contacts. Tick the people you want to add to the email.
If there's a group of people you email on a regular basis, you can make a kind of mailing list inside Google Contacts. Then when you want to email that group of people, just type the name of the list into the email window. It's a huge timesaver, and you can add or remove people from the list as and when necessary.
Gmail calls this mailing list feature contact labels. This is because all you're essentially doing is setting up a label in Contacts and attaching peoples email addresses to that label. The label is then the "mailing list" and you just type the name of the label into your email window.
In Contacts, on the left-hand side, select Create label.
You'll then be prompted to name your label. I decided on Work Colleagues. Click Save and you'll now see your new label appear next to Create label in the sidebar.
Now select the contacts you want to add to that label by ticking the boxes next to them.
At the top of the screen, to the left of the envelope icon is the icon to add the contacts to a label. Click that and select the label you want to add the contacts to. Click Apply to save your changes, and then click on the label in the sidebar to make sure the contacts are all there.
Now when you send an email to that group, just type the name of the label into the Gmail window, and it will auto-populate with all the email addresses.
Read more: How to add a signature in Gmail
Is there a maximum number of email recipients in a Gmail mailing list?
According to Google, you cannot email anymore than 500 people in one email.
What happens if you exceed the maximum number of email recipients in a Gmail mailing list?
Google will temporarily block your Gmail address for an unspecified period. If you persistently offend, they will shut down the Gmail address.
Can Gmail replace paid mailing list services such as Mailchimp or Mailerlite?
No. There's a reason you're paying for professional mailing list services such as Mailchimp. They have specialized features for mass emailing, including easy unsubscribing and advanced spam protection. Gmail doesn't offer such features.
GmailGoogle

redpajama_set_name: RedPajamaCommonCrawl


text:
Ereignisse
 1624: Die Niederländer gründen die Siedlung Neu-Amsterdam, (Nieuw Amsterdam) am Hudson River (heute New York City).
 Dreißigjähriger Krieg (1618 bis 1648).

Persönlichkeiten
 Ludwig XIII., König von Frankreich und Navarra
 Armand-Jean du Plessis, duc de Richelieu, Kardinal
 Ferdinand II., Kaiser des Heiligen Römischen Reiches Deutscher Nation, König von Ungarn, König von Böhmen
 Philipp IV., König von Spanien, Neapel, Sizilien und Portugal
 Georg Wilhelm, Herzog von Preußen und Kurfürst von Brandenburg
 Urban VIII., Papst
 Gregor XV., Papst
 Osman II., Sultan des Osmanischen Reiches und Kalif
 Mustafa I., Sultan des Osmanischen Reiches und Kalif
 Murad IV., Sultan des Osmanischen Reiches und Kalif
 Kösem Mahpeyker, Valide Sultan des Osmanischen Reiches
 Kyrillos I. Lucaris, Ökumenischer Patriarch von Konstantinopel
 Michael I., Zar in Russland
 Karl I., König von England, Schottland und Irland
 Jakob I., König von England, Schottland und Irland
 Sigismund III. Wasa, König von Polen und Großfürst von Litauen
 Jahangir, Großmogul von Indien
 Shah Jahan, Großmogul von Indien
 Chongzhen, Kaiser von China
 Tianqi, Kaiser von China
 Meishō, Kaiserin von Japan
 Go-Mizunoo, Kaiser von Japan

Weblinks

redpajama_set_name: RedPajamaWikipedia


Patterned Carpet In Living Room – This Best Patterned Carpet In Living Room Gallery wallpapers was upload on April, 14 2018 by admin. Here latest Patterned Carpet In Living Room wallpapers collection. Download other design about Patterned Carpet In Living Room in our other posts. Click on wallpapers to download Best Patterned Carpet In Living Room Gallery in high resolution.
You can download this Best Patterned Carpet In Living Room Gallery photos for your collection. Don't forget to rate and comment if you interest with this Patterned Carpet In Living Room design. Please contact us if it contains a copyright.
Related Post "Best Patterned Carpet In Living Room Gallery"


50G HAND DYE BY DYLON, 24 COLOURS AVAILABLE.
WHOLESALE DYLON HAND DYE - 50G, 24 COLOURS AVAILABLE MASSIVE BULK BUY DISCOUNTS!
This will include 12 Lace Anchors allowing you to complete 6 shoes. Other No tie shoelace locks require elastic shoelaces or other unattractive devices attached to the top of your shoes in order to function.
Les différents hauteurs réglables évitent au pied de glisser dans la chaussure. Confortables et discrètes en gel silicone. Soyez sûr de vous ! Gel siliconé très confortable. Confortables et invisibles.
In vendita n°1 patch Adidas ricamata. MISURA cm 8X8.
Limited Edition Troye Sivan Bloom T-Shirt M. Das T-shirt ist praktisch neu, d.h. einmal anprobiert. Ich habe es in Troyes Onlineshop gekauft. Versand innerhalb Deutschlands als Paket für 4.99€ inkl. Versicherung und Sendungsverfolgung. The T-Shirt is virtually new, I only tried it on once. I bought it in Troye's EU Onlinestore. International Delivery for €9.99. If you wish additional insurance and tracking, do not hesitate to contact me.
Les différents hauteurs réglables évitent au pied de glisser dans la chaussure. Confortables et discrètes en gel silicone. Soyez sûr de vous ! Pour tout type de chaussures. Confortables et invisibles.
Ce type de fumigène libère un mur de fumée de couleur en 20 secondes. Ce fumigène n'a pas été conçu pour être gardé en main pendant la combustion. Ce fumigène est essentiel dans l'arsenal d'un joueur d'airsoft ou de paintball.
Lot de 30 paires chaussettes toutes tailles.
NEW Oakley Jawbone/Racing Jacket Large Nose Pieces. Never used, in perfect new condition.
100th Anniversary Red WING LACE KEEPERS . Two (2) pairs . Shipped with USPS Priority Mail.
Neues Angebot100th ANNIVERSARY RED WING LACE KEEPERS Five (5) pairs. New never used.
100th ANNIVERSARY RED WING LACE KEEPERS Three (5) pairs. New never used.. Shipped with USPS Priority Mail.
Neues AngebotAdult Baby Waterproof-towelling-quilted bib with binding and ties.
Neues Angebot100th Anniversary Red WING LACE KEEPERS . Two (4)pairs. New never used.
100th Anniversary Red WING LACE KEEPERS . Two (4)pairs. New never used.. Shipped with USPS Priority Mail.
Dangle MK: 1.25"w x 0.75"h; Approx.
Dangle MK: 1.25"w x 0.75"h; Approx. 7.25" strap has lighter tan color.
Neues Angebot100th ANNIVERSARY RED WING LACE KEEPERS Three (3) pairs. New never used.
100th ANNIVERSARY RED WING LACE KEEPERS Three (3) pairs. New never used.. Shipped with USPS Priority Mail.
Very nice authentic Marc Jacobs dust protection bag for handbags, totes, shoes, etc. I have 2 sizes: 19"w x 17"h (2 ea.). and 22" x 22" (1 ea.).
Shoe Goo is like rubber in a tube. It is used to repair worn down heels on shoes, reattach soles to shoes, make shoes non-slip, and as a general adhesive (among others). Shoes will wear down and eventually fall apart.


The following announcement was just sent from NIST's Jeremy Grant, with important updates on the coming NSTIC funded pilots and plans for constituting a Steering Group, among other updates.
We'll be providing information on these items and more over the next several days. Looks like 2012 will be the year NSTIC begins true implementation.
After several months of planning, I am pleased to announce that the National Strategy for Trusted Identities in Cyberspace (NSTIC) is moving forward on a number of fronts. The next two months will be marked by several major events and initiatives designed to further the implementation of NSTIC's vision for an Identity Ecosystem!
Today NIST released a new Federal Funding Opportunity (FFO) for pilot programs to support the NSTIC. The FFO can be found here and also at and www.grants.gov.
This $10 million pilot program FFO marks a key step towards implementing the Strategy and establishing the Identity Ecosystem. As with all NSTIC activities, the success of these pilot programs will rely heavily on your participation, innovations, and efforts.
The goal of this new grant program is to test or demonstrate new solutions, models or frameworks that do not exist in the marketplace today, and that will advance the NSTIC vision: that individuals and organizations utilize secure, efficient, easy-to-use, and interoperable identity credentials to access online services in a manner that promotes confidence, privacy, choice, and innovation.
Specifically, the NSTIC National Program Office is interested in funding pilot projects with innovative approaches to address some or all of the barriers that have hindered past federated identity efforts, and do so in a way that aligns with and advances the NSTIC's four guiding principles – that identity solutions will be privacy-enhancing and voluntary, secure and resilient, interoperable, and cost-effective and easy-to-use. These pilots can thus provide a foundation upon which the Identity Ecosystem can be constructed.
Read and review the Federal Funding Opportunity available at http://www.nist.gov/nstic/2012-nstic-ffo-01.pdf, then spread the word to friends, colleagues, and co-workers.
Participate in our Proposer's Day which will be hosted on February 15, at the Department of Commerce Auditorium from 9:00am-12:00pm. This event will give potential applicants the opportunity to learn more about the new pilot program and to meet and interact with other Stakeholders interested in supporting NSTIC pilots. It will also be webcast live at www.nstic.gov for those who can't attend in person, with questions being accepted via Twitter (at #nstic) to support long distance Q&A.
Collaborate with fellow stakeholders, either through our Proposer's Day event, or through outside venues, such as workshops, conferences, and online forums. We highly encourage the creation of consortia and teams to develop wide-reaching and effective pilot programs.
Submit project proposals that will help to build the Identity Ecosystem and accelerate adoption of the NSTIC. The Identity Ecosystem's success will be built upon the foundation of private sector innovations, technologies, and standards. Abbreviated proposals are due March 7; a limited number of proposers will be selected from these and invited to submit full proposals.
In the next two weeks, we also expect to release a set of recommendations for establishing a privately-led Steering Group to lead implementation of the Identity Ecosystem. This long-awaited document will detail the results of responses to a Notice of Inquiry we published last year, and lay out a clear path forward for a governance structure to tackle the difficult standards and policy issues associated with creating the Identity Ecosystem.
RSA Conference: On Wednesday, February 29 from 3-5pm in Room 121 of the Moscone Center in San Francisco, we'll be holding a NSTIC update featuring White House Cybersecurity Coordinator Howard Schmidt and NSTIC National Program Office Manager Jeremy Grant. The event will provide stakeholders with an update on NSTIC implementation activities including the pilots and Steering Group, and offer an opportunity to ask questions.
The next few months will be an exciting and busy time for NSTIC, the NPO, and our stakeholders. We appreciate your continued interest and efforts – and look forward to working with you as we continue to implement NSTIC and the Identity Ecosystem!
Previous PostPrevious ID Collaboration Day Will Happen in San Francisco the Monday before RSA !


I was reading this post by Nova Spivack when I finally understood that there are two semantic webs. Nova calls them The Intelligent Web and The Data Web. (I think this is in some way related to the longstanding debate about Semantic Web vs. semantic web, which never really made any sense to me before). To put a slightly different spin on it, I like to think of these as the Orderly Semantic Web and the Chaotic Semantic Web.
The Intelligent Web is what one might imagine when reading the scenario at the beginning of the famous Scientific American article. I believe that part of the story is meant to get the imagination flowing, more than anything else. People who take it too literally have had trouble buying into that idea of the Semantic Web, not because the technology is so far-fetched, but because it seems to require a sort of Utopian information society where all information is free and everyone has agreed on a common descriptive language to communicate that information. If people see that as a prerequisite for the success of the semantic web, it's easy to see why they'd dismiss it as "never gonna happen".
Read a little more deeply and you'll discover a more realistic vision: The Data Web is a semantic web that's more like the familiar World Wide Web, in that it can be distributed and you don't need consensus. People can create whatever content and information they want and meaning can emerge later, when there's enough data for new processes to dig into that data in significant ways. Google is the game-changing Web 2.0 tool that arrived to make sense of the wild west that was Web 1.0, at the time. Similarly, it may turn out that the tools that will truly make sense of Web 3.0 (in other words, The Data Web) won't emerge until some future phase – let's call it Web 4.0, just for fun.
So why did I rename these two models? It makes it a little easier for me to state this: the Orderly Semantic Web (roughly analogous to what Spivack calls The Intelligent Web) is never going to happen. Universally agreed upon upper ontologies? Not likely. All data open and free, and never misused? No chance. The totality of human intelligence expressed using nothing more than syllogisms and first order logic? Set your mind at ease, Clay Shirky, this won't be necessary.
The Chaotic Semantic Web is the one I'm interested in. All we need to make it happen is for people to start generating and exposing more data and metadata. We don't need agreement, and we don't need to understand how it will all be used. Some time in the future all this data will be useful in ways we can't currently anticipate, and I'm OK with that.
Sure, this is a less predictive approach, and more faith-based. I'm not saying that we don't have to seriously consider all the challenges and issues, I'm saying we shouldn't let the fact that we don't have answers stop us from proceeding. Personally, I love the messiness at the fringes of things, and I'm pretty sure that that's where the value in all this is going to come from.
I wonder why people keep pointing to the Scientific American article, which is where we laid out the vision of the data web, as the opposing view.Not only don't we argue for some sort of agreed upon consensus model of AI and some sort of syllogistic model, but the article actually builds an opposing view to that — the idea is that local ontologies, built by any group of users, can be used to organize and integrate parts of the data on the data Web.I wish people criticizing our article, especially Shirky, had actually read it..
This has been said elsewhere , but just to be clear; the "Chaotic Semantic Web" is what the idea has always been.
The "Orderly Semantic Web" is a straw man. Nobody thinks that everyone is just going to magically agree on a few ontologies or even a few data formats; it's going to be a "fractal mess" (to quote Tim Berners-Lee) for a long time to come.
I don't know where the idea that the SemWeb is about the straw man comes from, but it seems to have taken a better hold on people than the truth.
Actually, Tim Berners-Lee predicts exactly what you call the "Chaotic Semantic Web". If you refer to his book "Weaving the Web", in the chapter where he's describing the Semantic Web vision (I think it was 13) you would realize that Berners-Lee is expecting pretty much the same thing: agreement on ontologies and meanings will emerge as people will use the said technologies (RDF, OWL) more and more. There is no need for an agreement on terms as a prerequisite for the semantic web – it's basically a process.
It's not 2 different things – it's one semantic web that may evolve (hopefully) into something more orderly as more and more people and organizations begin to use the same terms (=ontologies) to describe things. In the meantime, people will just point from one ontology to another.
So for example, if I have an ontology that defines the properties of a 'Person' entity, I may have a 'last name' property.
Your ontology can have a similar notion of a Person, but with a property named 'surname'.
So now, when we want our two programs to cooperate, we would only need to point from 'last name' to 'surname' saying that these 2 properties actually mean the same thing. There's no need for an actual agreement on terms for our programs to cooperate.
Thanks for your comments, Lior.
Based on your reaction – and James Hendler's, the force of which sort of surprised me – I fear that I didn't give the proper context to this post. I didn't mean to say that Tim Berners-Lee, James Hendler, & and Ora Lassila have this rigid view of what the Semantic Web should be. Their body of work clearly shows that they don't – for anyone who has read it.
What I meant is that the Scientific American article starts out by painting a picture that oversimplifies the concept, and many people never get beyond that. I've noticed this over and over in my own conversations with people, and I'm trying to find a way to get beyond those preconceptions. In my experience, most of the people who dismiss the concept of the Semantic Web do so on the grounds that they think the intention is that it be The Intelligent Web.
By nature, I break things down and define them. If I have to split the Semantic Web into two parts, two phases, or two models in order to explain it better to people, then that's what I'm going to do. Just because I'm trying to aknowledge and respond to these misguided notions, doesn't mean I fall into the camps that believe them.
I've left a more comprehensive response to your post over on your blog, but here let me just say that I did not mean to mischaracterize your article. I am responding more to the preconceived notions of people that I have actually spoken to about their understanding of the Semantic Web. Now, perhaps some of those people read the article and didn't get much further than the tale of Pete and Lucy, or perhaps they didn't read it at all.
I'm not saying that the ideas in the article are anything short of brilliant – I'm saying there's still a need to bring these ideas into terms that the mainstream can relate to. Unfortunately, the part of the article that attempts to do this overreaches a little (in my opinion) and as a result, has caused some of the misguided notions that you, yourself, are so rightfully concerned about.
I totally agree with you that "Nobody thinks that everyone is just going to magically agree on a few ontologies or even a few data formats" and I think I pretty much said so in my article. But the fact is that there are people who think that that's the intention and they, therefore, think the Semantic Web is impossible.
I set out to present those people with another view of the semantic web, in hopes that it would clarify some things and dispell some myths. Instead, I seem to have sparked some controversy among people who, as far as I can tell, already share my perspective.
Hi Rachel, ok, hopefully I've corrected my mistake (changed title of my post), thanks.
Actually, I think your original title was correct. The part I question is the idea that Hendler is refutting criticisms of the semantic web. While that's partially true (especially in the case of Shirky & O'Reilly, it seems), his post is mostly about adamantly denouncing things that I said that he actually agrees with.
Pingback: Jim Hendler on the Chaotic Semantic Web « The "Meta" Internet: The genesis of a "virtual" Silicon Valleys leveraging the power of the Internet.


text:
THE HISTORY OF FASHION. . . MOSTLY.
Sarah C. Byrd, Guest Book Reviewer
Kimberly Chrisman Campbell, Guest Book Reviewer
Amanda Kramp, Guest Contributor
Ariele Elia, Guest Contributor
Nadine Stewart, Exhibition Reviews
Tamsen Young, Guest Contributor
Friends and Colleagues
Knitting & Yarn Arts
California & The West
Interwar Years (1920s-1930s)
Current Events and Fashion History, Uncategorized
Revisiting a "mini history of the maxi dress"
Jezebel is re-promoting a maxi dress article they published in 2015 that mentions something I'd written on the subject from 2008. The 1,000+ comments (and counting) on that post are a gold-mine in terms of how attitudes have changed in just four short years.) In the nearly 11 years since I wrote on the maxi, the dress has maintained its perennial prominence in the summer zeitgeist. In my article for Monica Sklar's former Worn Through blog, I said
Geraldine Chaplin as Tonya in "Dr. Zhivago". Phyllis Dalton received an Oscar in 1965 for best costume designer.
"One of the earliest appearances of the "Maxi-Dress" was in 1968. The New York Times highlighted a cotton lace version by Oscar de La Renta he created for Elizabeth Arden Salon. More notable designers such as YSL, Dior, Cardin, Biba, Halston, and others would latch on to the style as well. Maxi-lengthed skirts had begun to outdo the mini skirt in 1967, and the dress (as well as the maxi coat) soon followed. Maxi styles quickly grabbed hold in London. Doctor Zhivago (1965) is often credited with igniting the craze for the Maxi style (along with the tandem trend for 'Midi' style skirts) due to its use of large flared coats over suit trousers. However, it was not until the 1970s that the maxi dress lodged itself firmly in the American mind (in all its polyester splendor), along with similar caftan and boho styles. By the late 1970s, it had become associated with the unfashionable and out of date (such as Mrs. Roper on Three's Company)"
But there is more to this story than that, as I recently found out.
As I noted in 2008, the maxi style in general, got its start in popular culture with Doctor Zhivago in 1965. Set in pre-revolutionary Russia, costume designer Phyllis Dalton created "Cossack blouses with neckband collars and wide billowy sleeves, and coats trimmed with fur from head to toe; and the maxi, or ankle-length, skirt" (Halsey 1986, 595). The film was released theatrically on Dec 22, 1965.
A short seven days later, on December 29, 1965, a little-known Parisian couturier named Jacques Syma photographed what might be considered an early version of a maxi dress as a part of his forthcoming spring collection.
Geraldine Chaplin in "Doctor Zhivago" 1965 MGM Cinema Publishers Collection
Dec. 29, 1965 – Noticing her youth and charm, Jacques Syma chose Laura Ulmer, daughter of the famous author and composer Georges Ulmer, as his inspiration for his Spring collection. "Merida", a long toile sleeveless dress with a large stripe along the hemline and a smaller stripe higher up, is low-cut in the back. (Credit Image: Keystone Pictures USA/ZUMAPRESS)
In March 1966, the Paris Spring collections appeared in Vogue magazine, and the cover showed Barbra Streisand in a floral print maxi. Inside, Paris showed off its Spring couture in a fashion feature photographed by Richard Avedon, and including many long dresses worn by models and actresses Jean Shrimpton, Marisa Berenson, Minnie Cushing, Françoise Rubartelli and Geraldine Chaplain (one of the stars of Doctor Zhivago) designed by Balmain, Lanvin, and Ricci. ("Fashion: THE YUM-YUM TREE IN PARIS." 1966. and Delvin 1966). These dresses were in stark contrast to the mini-skirts and micro-mini's popular at the time.
Lanvin and Ricci designed long dresses from Vogue, March 1966.
One of the first time the word 'maxi' appeared in American newspapers was a July 1966 syndicated report from Paris focused on Jacques Syma's collection that included the micro-mini skirt and its counterpart the maxi skirt. It appeared in newspapers across the United States (De la Fontaine 1966), helping to spread the style(s) further. Laura Ulmer, Syma's counter-part was a model, singer, and Ye–Ye Girl (Young, camp-y, French Pop icons of the 1960s) (Deluxe 2013).
The New York Times later explained that the maxi began "gaining ground" alongside the mini on the streets of New York and Paris beginning in 1966 (Emerson 1968, E4). It became a part of the 1960s Youthquake and had been established in the mainstream by the 1970s. Some might argue that it's trajectory and popularity coincided with the feminist movement of the era. It would make sense then, to see it re-emerge (and have staying power) in the current cultural climate.
Heather Vaughan Lee is the founding author of Fashion Historia. She is an author and historian, whose work focuses on the study of dress in the late 19th through the 20th century. Covering a range of topics and perspectives in dress history, she is primarily known for her research on designer Natacha Rambova, American fashion history, and the history of knitting in America and the UK. Her new book, Artifacts from American Fashion is forthcoming in 2020 from ABC-CLIO. More posts by the Author »
Halsey, William Darrach and Emanuel Friedman. 1986. Collier's Encyclopedia, with Bibliography and Index, Volume 9. Macmillan Educational Company. Accessed April 1, 2019. https://books.google.com/books?id=KMUJAAAAIAAJ&q=Dr.+zhivago+maxi+dress&dq=Dr.+zhivago+maxi+dress&hl=en&sa=X&ved=0ahUKEwiA9pGj9a_hAhUTO30KHX_tDlcQ6AEIPjAE.
"Fashion: THE YUM-YUM TREE IN PARIS." 1966. Vogue, Mar 15, 78-78, 79, 80, 81. http://ezproxy.montclair.edu:2048/login?url=https://search-proquest-com.ezproxy.montclair.edu/docview/897870673?accountid=12536.
Devlin, Polly. 1966. "Fashion & Features: INSTANT BARBRA." Vogue, Mar 15, 68-68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 152, 154. http://ezproxy.montclair.edu:2048/login?url=https://search-proquest-com.ezproxy.montclair.edu/docview/897870648?accountid=12536.
de la Fontaine, Yvette. 1966. "Hemlines are Long-long, Short-short." Women's News Service. July 22. https://www.newspapers.com/image/144995582/?terms=%22Maxi%2Bskirt%22
de la Fontaine, Yvette.1966. "'Ye-Ye' Modes Favorites in Paris." Women's News Service. Jan. 16. https://www.newspapers.com/image/144160376/?terms=%22Jacques%2BSyma%22
Emerson, Gloria. 1968. "Fashion: Alas! The Poor Mini." New York Times (1923-Current File), Feb 04, 1. http://ezproxy.montclair.edu:2048/login?url=https://search-proquest-com.ezproxy.montclair.edu/docview/118326156?accountid=12536.
Deluxe, Jean-Emmanuel. 2013. Yé-yé!: the girls of '60s & '70s French pop music. Los Angeles, California: Feral House.
Books & Resources, Friends and Colleagues, Interwar Years (1920s-1930s), Uncategorized
Best Laid Plans: What I hope to read this summer
As a part of my need to play catch up (I took on too many projects recently), I'm starting a summer series to share the giant stack of new books that have come through my front door. And you'll be happy to know that I'm focusing on the good ones! I (and a few contributors), will be covering everything from the fashion illustration history, some major new works cover 20th century fashion history, new works on the field of dress, Hair (and more as the books roll in!) Stay tuned !
First on my list of 'must read's' this summer is the giant, beautiful and highly informative Fashion and the Art of Pochoir: The Golden Age of Illustration in Paris by April Calahan and Cassidy Zachary (Thames & Hudson, November 2015). The fact that the book is dedicated to Dr. Lourdes Font ("whose passion and vast knowledge have inspired an entire generation of fashion historians"), tells me that these authors are on point and know their stuff (#FontFan over here!)
Highly illustrated and beautifully designed, the book appears to be a happy marriage of style and substance, full of interesting looking, well-documented essays (yeah for footnotes in a legible size!). The book covers 1908-1925, and focuses on the "centuries-old hand-stenciling technique known as pochoir," though it does include a good many photographs for garment comparison. I love this time period, and love that this book is an easy reference to the well-loved and such famous illustrations and artists. I can't wait to dig in !
"Collectively, the ten publications featured in this book document a fashion revolution, in terms of both the clothing depicted and the practice of fashion illustration itself. The groundbreaking illustration styles seen in the pages of these albums and magazines were born out of the need to represent the rapid modernization of fashionable dress that occurred in the first two decades of the century."
Want more? Support the authors and Buy The Book
Heather (Vaughan) Lee is an author and historian, whose work focuses on the study of dress in the late 19th through the 20th century. Covering a range of topics and perspectives in dress history, she is primarily known for her research on designer Natacha Rambova, American fashion history, and the history of knitting in America. More on Heather's career can be found here.
Founded in 2011, Fashion Historia explores the history of fashion (and related events and exhibitions) with a focus on California and the West Coast. It includes book reviews, historical research, theoretical discussion and invites feedback from other scholars in the field. Contact Me Here.
Books & Resources, Interwar Years (1920s-1930s), Uncategorized
Holiday gift books (Part 1): "Jean Patou: A Fashionable Life"
Released just a few weeks ago, Jean Patou: A Fashionable Life by Emmanuelle Polle highlights the extensive private archives of the Patou heirs for the first time. This oversize monograph from Flammarion that Polle spent two years researching, features 250 color and black-and-white illustrations, including the much of the early days of fashion photography (such as those by Baron de Meyer).
The book is divided into three sections: a biography of Jean Patou, his work in Paris, and his work in the United States. Pages are covered from edge to edge with fashion sketches, photographs of garments (sportswear, swimwear, day-wear, etc, gowns), fashion photographs (including both street fashion and studio photographs), focused on the 1920s and 1930s – the height of his powers. It also includes information related to his famous perfumes-Joy and Que Sais-Je.
In New York in 1924, Jean Patou poses in one of the eighty-odd suits he claimed to own.
Though his career lasted a short fifteen years, his use of embroideries, jersey, and interest in day pajamas, and sportswear made him a rival of Chanel. The book also includes discussion and visual representation of the inspiration he gained during World War I-even including some garments he collected and kept as inspirational pieces. The book discusses his clientele, his friends, his lovers and gives an in-depth look at the man and his design work (much of which researched from private letters, diaries, and other previously unpublished material).
This book is a welcome addition to fashion history literature – as it is the first book to focus solely on the short but substantial career of Jean Patou since the 1980s. Jean Patou: A Fashionable Life is one of those rare gems that will be of interest to both established fashion historians, archivists, libraries, museums and fashion enthusiast alike. Especially those interested in Paris, and the Art Deco period.
For a 'sneak peak' of the interior, check out the small gallery below.
© Francis Hammond, "Florentin" evening dress in Persian blue, coral, and worn-gold silk lamé, with cashmere palm frond and floral motifs, 1926 (ensemble).
Jean Patou Archives, Fashion drawing by Madeleine Jeannest, 1932.
© Francis Hammond, Jean Patou's designs owe much to his large collection of textiles from all over the world.
© Francis Hammond, The Jean Patou label bore a reproduction of the couturier's signature.
Jean Patou Archives, "Fleurs du mal" coat in caramel silk velvet, back embroidered with flowers, 1921. It wasn't unusual for the names of Jean Patou's designs to carry literary references. This one reflects the couturier's taste for the poetry of Baudelaire.
In New York in 1924, Jean Patou poses in one of the eight-odd suits he claimed to own.
* © Francis Hammond, "Declaration" evening top in pale pink silk tulle over matching silk chiffon, embroidered all over with white and silver satin tubes in a geometric diamond motif, Winter 1935. This garment, which belonged to the Princesse Nilfur, was worn under a tuxedo suit with a long skirt and jacket in black satin, lined in the same pink color as the top.
About Fashion Historia
Heather Vaughan Lee is an author and historian, whose work focuses on the study of dress in the late 19th through the 20th century. Covering a range of topics and perspectives in dress history, she is primarily known for her research on designer Natacha Rambova, American fashion history, and the history of knitting in America and the UK.
Founded in 2011, Fashion Historia explores the history of fashion (and related events and exhibitions) with a focus on California and the West Coast. It includes book reviews, historical research, theoretical discussion and invites feedback from other scholars in the field and interested enthusiasts.
Heather Vaughan Lee is also the Author/Contributor/Editor of:
November 2019 (forthcoming):
October 2012:
Artifacts from American Fashion (6)
Books & Resources (186)
California & The West (196)
Current Events and Fashion History (7)
Friends and Colleagues (99)
History in the Making (35)
Interwar Years (1920s-1930s) (107)
Knitting & Yarn Arts (34)
Museums & Exhibitions (129)
Archives Select Month December 2019 (2) November 2019 (5) October 2019 (2) July 2019 (1) June 2019 (1) April 2019 (2) March 2019 (1) July 2018 (1) May 2018 (1) March 2018 (1) January 2018 (1) August 2017 (1) June 2017 (1) April 2017 (2) February 2017 (3) December 2016 (1) October 2016 (2) July 2016 (1) June 2016 (4) May 2016 (2) April 2016 (4) March 2016 (1) December 2015 (1) November 2015 (2) October 2015 (2) August 2015 (3) June 2015 (1) May 2015 (1) April 2015 (5) March 2015 (1) February 2015 (2) October 2014 (3) September 2014 (3) August 2014 (3) July 2014 (2) June 2014 (2) May 2014 (3) April 2014 (3) February 2014 (1) January 2014 (1) December 2013 (1) November 2013 (7) October 2013 (6) September 2013 (3) August 2013 (4) June 2013 (2) May 2013 (3) April 2013 (2) March 2013 (3) February 2013 (6) January 2013 (6) December 2012 (2) November 2012 (7) October 2012 (6) September 2012 (2) August 2012 (1) July 2012 (9) June 2012 (11) May 2012 (17) April 2012 (14) March 2012 (9) February 2012 (14) January 2012 (8) December 2011 (14) November 2011 (18) October 2011 (19) September 2011 (16) August 2011 (14) July 2011 (14) June 2011 (15) May 2011 (13)
Fashion Historia RSS
Artifacts from American Fashion: Ruth Cohn's Shirtwaist dress by Rudolf Gowns
The Way We Wore
Dress Address
Costume Society of America Western Region
1920s 1930s Aesthetic dress American History Art Deco Belle Epoch Fashion Book Review California Fashion Costume Design Costume Designers Costume History craft domestic arts Donna Reed dress Embroidery Fashion fashion as art Fashion Book Review fashion history Film Costume Film History French Fashion Gender Hawaii History hollywood Jean Patou Knitting Knitting History Luxury Museums museums and fashion Old West Fashion Paris Patriotism Redding Shirtwaist Smithsonian Textile History textiles Weaving World War II WWI WWII
Fashion Historia


text:
Obama outraged by slaying of abortion provider George Tiller
By Stan Finger and Joe RodriguezMcClatchy Newspapers
President Obama said he was "shocked and outraged" by the killing of abortion doctor George Tiller, who was shot Sunday while attending church in east Wichita. The suspect is a 51-year-old male. Police did not release the suspect's name.
WICHITA, Kan. � President Obama said he was "shocked and outraged" by the killing of abortion doctor George Tiller, who was shot Sunday while attending church in east Wichita.
Wichita Deputy Police Chief Tom Stolz said at a news conference late Sunday afternoon that a suspect in the shooting was in custody and on his way back to Wichita.
"However profound our differences as Americans over difficult issues such as abortion, they cannot be resolved by heinous acts of violence," the president said in a statement issued by the White House.
The suspect, a 51-year-old male, was arrested without incident on Interstate 35 in Johnson County, Kan., about three hours after the shooting, Stolz said.
Police did not release the suspect's name.
The investigation is in its "infancy stages," Stolz said. He said the shooting appeared to be an isolated act.
Tiller, 67, was shot once just after 10 a.m. in the lobby of Reformation Lutheran Church, where he was a member of the congregation.
Stolz said Tiller was shot in the foyer of the church. There were three or four eyewitnesses, he said. Six to 12 people were in the foyer at the time of the shooting.
Two men attempted to apprehend the suspect, but he pointed a gun at them and threatened them before fleeing, Stolz said.
The suspect's car � a powder blue Ford Taurus registered to an owner in Merriam � was spotted just south of Gardner by two Johnson County Sheriff's deputies. The Sheriff's Office had suspected that the man would be coming back to his home on I-35, and the deputies waited for him.
As the car was spotted going north on the highway, the deputies followed and were quickly joined by three other sheriff's patrol cars.
Lt. Mike Pfannenstiel of the Johnson County Sheriff's Office said officers pulled the car over just south of the main Gardner, Kan., exit and got out with guns drawn. The man then got out of his car with his hands up.
"We took him down without incident," Pfannenstiel said, adding that the man appeared to be driving the speed limit and made no attempt to elude the deputies.
Stolz said police anticipate the suspect will be charged with murder and two counts of aggravated assault. Investigators will present the case to the Sedgwick County District Attorney's Office on Monday.
The District Attorney's Office will determine what charges will be filed, Stolz said. Federal charges are also a possibility, he said.
Tiller was serving as an usher at the church, one of six ushers listed in the church bulletin. He was handing out bulletins to people going into the sanctuary minutes before being shot.
Tiller's family issued a statement through Wichita attorneys Dan Monnat and Lee Thompson:
"Today we mourn the loss of our husband, father and grandfather. Today's event is an unspeakable tragedy for all of us and for George's friends and patients.
"This is particularly heart wrenching because George was shot down in his house of worship, a place of peace."
Wichita police Capt. Brent Allred said that several law enforcement agencies � including the FBI and the Kansas Bureau of Investigation � have been called in to help with the case.
(EDITORS: STORY CAN END HERE)
Allred said the 10 a.m. church service had already begun at the time of the shooting.
Homicide detectives and Sedgwick County District Attorney Nola Foulston arrived at the church after the shooting.
Members of the congregation who were inside the sanctuary at the time of the shooting were kept inside by police, and those arriving were ushered into the parking lot immediately after the shooting.
Witnesses later were transported downtown for interviews and other members of the congregation were slowly released from inside the sanctuary.
By 12:30 p.m., what appeared to be a body was taken away in an SUV with a patrol car behind it.
At about 12:40, a police dog was taken to check out a black SUV. An investigator wrote down the tag number on the vehicle.
Tiller has long been a focal point of protest by abortion opponents because his clinic, Women's Health Care Services at 5107 E. Kellogg, is one of the few in the country where late-term abortions are performed.
"It's a terrible loss. I'm just really sad about the whole thing," said a former employee of the clinic who asked not to be identified. "He was a great guy. I understand people were against a lot of what he did, but for those who he helped, they'll never forget the kind of person he was."
Mark Mitchell, who lives near where the shooting occurred, said he knew Tiller attended Reformation Lutheran Church because of the periodic protests there and media coverage.
He said the protests would sometimes be as large as two dozen people. The last protest he can remember there was in the fall.
"We are shocked at this morning's disturbing news that Mr. Tiller was gunned down," anti-abortion group Operation Rescue said in a statement on its Web site. "Operation Rescue has worked for years through peaceful, legal means, and through the proper channels to see him brought to justice. We denounce vigilantism and the cowardly act that took place this morning. We pray for Mr. Tiller's family that they will find comfort and healing that can only be found in Jesus Christ."
Protesters blockaded Tiller's clinic during Operation Rescue's "Summer of Mercy" protests during the summer of 1991, and Tiller was shot by Rachelle Shannon at his clinic in 1993. Tiller was wounded in both arms, and Shannon remains in prison for the shooting.
The clinic was bombed in June 1986, and was severely vandalized earlier this month. According to the Associated Press, his lawyer said wires to security cameras and outdoor lights were cut and that the vandals also cut through the roof and plugged the buildings' downspouts. Rain poured through the roof and caused thousands of dollars of damage in the clinic. Tiller reportedly asked the FBI to investigate the incident.
No arrests were made in the 1986 bombing.
Sgt. Bart Brunscheen of the Wichita Police Department said earlier Sunday that there had been no activity at Tiller's clinic, although security crews were being brought in to make sure the building was secure. Officials also were going to check the clinic's security cameras to see if there was any activity over night.
Tiller and his clinic have faced continuous threats and lawsuits. A Wichita jury ruled in March that he was not guilty on 19 criminal charges he faced for allegedly violating a state law requiring an "independent" second physician's concurring opinion before performing later term abortions. Immediately following the ruling in this criminal case, the Kansas State Board of Healing Arts made public a similar complaint against Tiller that was originally filed in December 2008.
Former Kansas Attorney General Phill Kline, who conducted an investigation into Tiller, said in a statement he was "stunned by this lawless and violent act which must be condemned and should be met with the full force of law. We join in lifting prayer that God's grace and presence rest with Dr. Tiller's family and friends."
Gainesville Sun ~ 2700 SW 13th St., Gainesville, FL 32608 ~ Privacy Policy ~ Terms Of Service
Preps Sports
Gatorsports
Pat Dooley


text:
/* Generated By:JJTree: Do not edit this line. ASTVarNode.java */

package sage.jep;

import java.util.*;
/**
 * Variable Node
 */
public class ASTVarNode extends SimpleNode {

  private String varName;

  public ASTVarNode(int id) {
    super(id);
    varName = "";
  }

  public ASTVarNode(Parser p, int id) {
    super(p, id);
  }

  /**
   * Accept the visitor.
   */
  public Object jjtAccept(ParserVisitor visitor, Object data) {
    return visitor.visit(this, data);
  }

  /**
   * Sets the name of the variable.
   */
  public void setName(String varName_in)
  {
    varName = varName_in;
  }

  /**
   * Returns the name of the variable.
   */
  public String getName()
  {
    return varName;
  }

  /**
   * Creates a string containing the variable's name and value
   */
  public String toString()
  {
    String temp = "Variable: \"" + getName() + "\"";

    return temp;
  }
}


text:
"We're all part of this worldwide yearning for peace!" Charles Carney tells 20 nuke protesters near the National Security Campus May 25.—Photo by Tom Fox
June 7, 2020 June 6, 2020 PeaceWorks KC Economic justice, Nuclear weapons, PeaceWorks events
Carney takes hope from 'everyday people creating a new narrative'
Twenty persons gathered across the road from the National Security Campus in Kansas City, Mo., protesting the making of parts for nuclear weapons at the NSC. Most of the attendees were part of a CARE-a-van from mid-KC to south KC for the "Human Care, Not Warfare" event on Memorial Day, May 25.
Charles Carney, a social worker on the PeaceWorks Board and a member of the Poor People's Campaign in Kansas, said at the NSC entry, "We're living in very dark times" with funds rising for nuclear weapon production while the coronavirus kills people and intensifies joblessness and homelessness.
During this first year that the costs top $1 billion for operating the National Security Campus, Carney warned NSC operator Honeywell about "the groundswell 'Me Too' movement of everyday people creating a new narrative." Carney declared, "It's easy to overlook this grassroots movement. But farmers ARE steeped in biodiversity, bringing healthy food to our tables. Women and people of color and their allies ARE creating new opportunities and smashing glass ceilings. The prisons ARE closing and the classrooms ARE opening."
Carney carried on: "Is this a pipe dream? Well, it's a pipe dream until it isn't anymore. Who would have thought 5 years ago that we'd have 36 of the 50 countries needed to sign onto the UN Treaty on the Prohibition of Nuclear Weapons? It calls for an end to developing, testing, and stockpiling nuclear weapons. We're all part of this worldwide yearning for peace!"
Laughing and holding out hope for decreased funds for nuclear weapons, Carney said, "Honeywell, you may have to change your name to Honey-Baked and hold a bake sale to support yourself!" His listeners roared in response.
Tagged Charles Carney, Honeywell, Memorial Day, National Security Campus, nuclear
Published by PeaceWorks KC
View all posts by PeaceWorks KC
Christopher Overfelt, of Vets for Peace, calls for health care for all
Open letter from PeaceWorks-KC


This month's TOC theme is "formats." Even though our customers still tend to favor PDF it's clear that mobi and EPUB are the formats with all the momentum. In order to get the scoop on EPUB I decided to go right to the source. The IDPF is the organization that develops and maintains the EPUB standard and Bill McCoy is the IDPF's Executive Director. Bill was kind enough to sit down and talk with me about the current state of EPUB and where it's heading.
HTML5's impact — EPUB3 is based on HTML5 and brings with it all the rich functionality that HTML5 has to offer. Global language support and accessibility are two very important improvements in EPUB3.
Why do we need both EPUB3 and HTML5? — Bill points out that EPUB is a "reliable container" within which HTML5 content can be distributed. EPUB also allows you to step back from HTML5 coding and focus more on the structure of the document itself.
Fixed layout — PDF is designed with fixed layout in mind whereas EPUB not only supports fixed layout but it also offers the reflowable option as well as a hybrid solution for those situations where both fixed and reflowable are needed in the same product.
12 years in the making — I'm puzzled over why it's taking so long for EPUB3 support to show up on devices and in apps. Bill reminds me it was a pretty significant jump from EPUB2 to EPUB3 but that we're already seeing signs of significant progress.
Beyond today's EPUB3 — Bill prefers to focus on EPUB3 but I did manage to pry a few details from him about what we can expect in the future: Advanced fixed layout (e.g., Manga), adaptive layout (page templates), dictionaries, indexes and annotations.
You can listen the entire interview in the audio player below.
Our TOC theme for August was platforms and we transition to the theme of formats in September. In a couple of earlier interviews we talked about the future of iOS and Android as publishing platforms. I also wrote a piece about how the ultimate winner isn't actually a platform at all. It's time to bring in an expert and tell us whether HTML5 really is the future of publishing, both as a platform and a format.
I picked one of the smartest people I know for the job. His name is Sanders Kleinfeld and he's a publishing technology engineer here at O'Reilly. That's a fancy way of saying he knows digital publishing inside out. Sanders has worked extensively with HTML5 and is the author of our free ebook, HTML5 for Publishers.


text:
Foveal Sensitivity and Morphology in Major and Macular Branch Retinal Vein Occlusion
Hidetaka Noma*, 1, Katsunori Shimada 2, Tatsuya Mimura 3
1 Department of Ophthalmology, Yachiyo Medical Center, Tokyo Women's Medical University, Chiba, Japan
2 Department of Biostatistics, STATZ Institute Inc., Tokyo, Japan
3 Department of Ophthalmology, Medical Center East, Tokyo Women's Medical University, Tokyo, Japan
© Noma et al.; Licensee Bentham Open.
open-access license: This is an open access article licensed under the terms of the Creative Commons Attribution Non-Commercial License (http://creativecommons.org/licenses/by-nc/3.0/) which permits unrestricted, non-commercial use, distribution and reproduction in any medium, provided the work is properly cited.
* Address correspondence to this author at the Department of Ophthalmology, Yachiyo Medical Center, Tokyo Women's Medical University, 477-96, Owada-shinden, Yachiyo, Chiba 276-8524, Japan; Tel: 81-47-450-6000; Fax: 81-47-458-7047; E-mail: noma-hide@umin.ac.jp
To determine whether foveal thickness, foveal volume, visual acuity, and foveal sensitivity after intravitreal injection of triamcinolone acetonide (IVTA) are influenced by the extent of occlusion (major versus macular branch retinal vein occlusion (BRVO)).
In this interventional case series, 22 eyes of 22 BRVO patients with macular oedema were treated by IVTA. Patients were divided into 2 groups according to the site of occlusion, with the Major group having occlusion of a major retinal vein and the Macular group having occlusion of a macular venule. Foveal sensitivity was measured by microperimetry before IVTA and 3 and 6 months after IVTA. Visual acuity was converted to logarithm of the minimal angle of resolution (logMAR) values. Foveal thickness and macular volume were measured by optical coherence tomography before IVTA and 3 and 6 months after IVTA.
Foveal thickness and foveal volume showed significant improvement from before to 3 and 6 months after IVTA in both groups (all P<0.001). Visual acuity also showed significant improvement from before to 3 and 6 months after IVTA in both groups (P=0.001 and P=0.022, respectively). Moreover, foveal sensitivity was significantly improved from before to 3 and 6 months after IVTA in the Major group (P<0.001). Foveal sensitivity also increased from before to 3 and 6 months after IVTA in the Macular group, but not significantly. There were no significant differences in the trend profiles of foveal thickness, foveal volume, visual acuity, and foveal sensitivity between the Major and Macular groups.
These results suggest that IVTA may be effective for improving foveal morphology, visual acuity, and foveal sensitivity in BRVO patients regardless of the site of occlusion.
Keywords: foveal thickness, foveal sensitivity, triamcinolone acetonide, branch retinal vein occlusion, macular oedema, site of occlusion.
In patients with branch retinal vein occlusion (BRVO), macular oedema is the complication that is most likely to threaten vision [1]. An increase of pressure in the macular capillaries leads to impairment of the endothelial blood-retinal barrier and increases vascular permeability, resulting in the onset of macular oedema [2]. Clinically, BRVO is classified into major (first-order) and macular (second-order) subtypes based on the site of occlusion [3, 4]. In many respects, the clinical and angiographic findings of patients with macular BRVO resemble those of patients with major BRVO. The severity of major BRVO depends on the vein that is occluded and there can be a wide range of complications. While patients with macular BRVO are unlikely to develop neovascularization because of the smaller area of the retina affected, they frequently suffer from macular oedema and visual impairment [5].
Macular oedema in BRVO patients can be treated by the intravitreal injection of anti-VEGF agents [6] or triamcinolone acetonide (IVTA) [7], as well as by grid laser photocoagulation [8] and pars plana vitrectomy (PPV) [9]. All of these methods have been reported to improve both visual acuity and macular oedema. However, previous studies evaluated visual function on the basis of visual acuity alone, although macular oedema usually involves the macula beyond the fovea, suggesting that an objective and reproducible method of measuring retinal function could provide more accurate assessment of the response to treatment. The Micro Perimeter 1 (MP-1) is an instrument that measures retinal sensitivity and it combines digital fundus imaging with automated perimetry [10]. We previously demonstrated that retinal thickness and retinal volume are more closely associated with retinal sensitivity than with best-corrected visual acuity (BCVA) in BRVO patients who had macular oedema [11]. Thus, visual acuity (which only reflects foveal function) may be an inadequate parameter for evaluating the response of these patients to treatment, and it is possible that the functional prognosis could be better assessed by measuring retinal sensitivity with the MP-1. However, little is known about the influence of the site of occlusion on retinal sensitivity in BRVO patients after IVTA. Accordingly, we investigated whether foveal thickness, foveal volume, visual acuity, and foveal sensitivity after IVTA were influenced by the site of occlusion (major versus macular) in patients with BRVO.
We studied 22 consecutive patients (22 eyes) who had macular oedema with BRVO and were treated with IVTA. Between July 2008 and August 2011, these 22 patients with a mean age of 69.4 ± 9.4 years (15 women and 7 men) were prospectively enrolled in this uncontrolled study at the Department of Ophthalmology of Tokyo Women's Medical University. Each patient received a comprehensive ophthalmologic examination, including the measurement of BCVA and intraocular pressure (IOP), indirect ophthalmoscopy, and slit-lamp biomicroscopy with a contact lens before IVTA and at 3 and 6 months after treatment. We graded nuclear, posterior subcapsular, and cortical cataract according to the new World Health Organization Simplified Cataract Grading System, and subjects with cataract≥grade II (nuclear, posterior subcapsular, or cortical) were defined as having cataract [12]. This study was approved by the Institutional Ethics Committee and adhered to the tenets of the Declaration of Helsinki. Informed consent was provided in writing by each patient.
The inclusion criteria were eyes with a foveal thickness greater than 300 μm and a visual acuity equal to or less than 20/33.3. The following 8 exclusion criteria were employed: prior ocular surgery, diabetes mellitus with diabetic retinopathy, prior macular laser photocoagulation, prior intravitreal treatment with anti-VEGF agents or prior IVTA, prior ocular inflammation, severe retinal haemorrhage (including bleeding that involved the intrafoveal or subfoveal spaces), coexisting epiretinal membrane or glaucoma, and retreatment during the 6-month follow-up period. Patients with severe retinal haemorrhage were excluded because of possible bias when assessing visual function. Among the 22 patients, 13 had superior BRVO and 9 had inferior occlusion. The patients were divided into 2 groups according to the site of venous occlusion; Major group (occlusion of one of the major branch retinal veins) and Macular group (occlusion of one of the macular venules) [3, 4].
Treatment by IVTA
In all 22 patients, IVTA was delivered under local anaesthesia. Each patient received 4.0 mg of triamcinolone acetonide in a volume of 0.1 ml. Both groups were assessed according to the same study protocol. Injection was done through the pars plana (3-4 mm posterior to the limbus) with a sterile technique, and prophylactic topical antibiotics were applied for 1 week afterward. Patients were followed for at least 6 months. Recurrence of macular edema was defined as an increase of foveal thickness by >100 μm compared with that at 3 months after IVTA in patients whose foveal thickness had decreased to <300 μm at 3 months [13]. Macular oedema recurred in 4/22 eyes (18%) from the Major group, but these 4 patients refused further treatment.
Fundus Examination
At baseline ophthalmoscopy and biomicroscopic examination using a slit-lamp with a fundus contact lens were performed. Patients also underwent standard fundus color photography and fluorescein angiography, using a Topcon TRC-50EX fundus camera, image-net system (Tokyo Optical Co. Ltd., Japan), and preset lens with a slit-lamp.
To assess ischaemic retinal vascular occlusion, the ischaemic area of the retina was measured angiograms by a masked grader using Scion Image public domain software [14-16]. In brief, the optic disc was outlined with a cursor and its area was measured. Then the nonperfused part of the retina was outlined and its area was determined, after which the nonperfused area was divided by the disc area to calculate an index of retinal ischaemia. Thus, we used the disc area as a unit to evaluate the ischemic area.
Measurement of BCVA
Each patient underwent measurement of BCVA in decimal units on a Landolt chart by an orthopticist using an SC-2000 System (Nidek, Gamagori, Japan). Chart brightness was set at 80-320 cd/m2 and contrast was set at more than 74%. Data were converted to the logarithm of the minimum angle of resolution scale (logMAR).
An OCT 3000 Zeiss or Cirrus HD-OCT instrument (Carl Zeiss Meditec, Dublin, CA, USA) was used to measure the foveal thickness. Measurement was done in the vertical cross-section with the instrument centered on the fovea and in the fast macular thickness mode. The foveal thickness was defined as the distance between the inner surface of the neurosensory retina and the retinal pigment epithelium. Foveal thickness and foveal volume were respectively calculated as the average retinal thickness and volume within a circle of 500 μm radius centered on the fovea. These measurements were automatically performed by computer software.
Microperimetry
Fundus-monitored microperimetry was done with an MP-1 system (Nidek, Gamagori, Japan), using an infrared fundus camera controlled by software that automatically tracked movement of the fundus (evaluating shifts in the x and y directions with respect to a reference frame obtained at the start of examination). In all examinations, Goldmann III stimuli were randomly presented according to a 4-2-1 double staircase strategy. Stimulus intensity was varied from 0 to 20 decibels (dB) (0 dB corresponded to the strongest signal intensity of 127 cd/m2) in 1-dB increments, and the stimulus duration was set at 200 ms. The size of the target for fixation was varied according to the patient's visual acuity. Background illumination was set at 1.27 cd/m2. Foveal sensitivity was calculated as the average retinal sensitivity within a circle of 500 μm radius centered on the fovea, and was determined at five locations covering the central 4° field [11].
All analyses were performed with SAS System 9.1 software (SAS Institute Inc., Cary, North Carolina, USA). Results are presented as the mean ± SD or as the frequency. One-way or two-way repeated measures ANOVA and a post-hoc t-test with Bonferroni's correction were used to evaluate changes of foveal thickness and volume, visual acuity, and foveal sensitivity. Two-tailed P values of less than 0.05 were considered to indicate statistical significance.
The characteristics of the Major and Macular groups are summarized in Table 1. Among the 22 patients with BRVO, 15 were assigned to the Major group and 7 to the Macular group. The mean age, female/male ratio, prevalence of hypertension, systolic blood pressure, diastolic blood pressure, prevalence of hyperlipidaemia, and duration of BRVO were similar in the Major and Macular groups (P=0.230, P=0.448, P=0.823, P=0.131, P=0.839, P=0.899, and P=0.094, respectively), but the nonperfused area was significantly larger in the Major group than the Macular group (P=0.006).
Baseline Clinical Features of the Two Groups
Major (N=15)
Macular (N=7)
Age (years) 67.7±9.4‡ 73.0±9.0‡ 0.230
Gender (female/male) 11/4 4/3 0.448
Systolic blood pressure (mmHg)
Diastolic blood pressure (mmHg) 10
133±13‡
84±12‡ 5
85±13‡ 0.823
Hyperlipidemia 9 4 0.899
Duration of BRVO (months) 3.6±1.6‡ 5.4±3.3‡ 0.094
Nonperfused area (disc areas) 50.6±37.0‡ 6.2±12.0‡ 0.006
BRVO=branch retinal vein occlusion
‡ Mean ± standard deviation (SD).
In both groups, foveal thickness and foveal volume showed a significant decrease from before IVTA to 3 and 6 months after IVTA (all P<0.001, one-way repeated measures ANOVA). Foveal thickness and volume decreased significantly from before IVTA to 3 or 6 months after IVTA in both groups (all P<0.01, post-hoc t-test with Bonferroni's correction) (Fig.1A, B). However, foveal thickness and volume both increased from 3 to 6 months after IVTA in the Major group, although not significantly (P=0.152 and P=0.135, respectively, post-hoc t-test with Bonferroni's correction) (Fig. 1A, B). There were no significant differences in the trend profiles of foveal thickness and volume between the Major group and the Macular group (P=0.457 and P=0.476, respectively, two-way repeated measures ANOVA) (Fig. 1A, B).
Trend profiles of foveal thickness and volume after intravitreal injection of triamcinolone acetonide (IVTA) in BRVO patients with macular oedema. (A) In the Major group and the Macular group, the foveal thickness decreased significantly from before IVTA to 3 and 6 months after IVTA (P<0.001 and P<0.001, respectively). There was no significant difference in the trend profile of foveal thickness between the two groups (P=0.457). (B) In the Major group and the Macular group, the foveal volume decreased significantly from before IVTA to 3 and 6 months after IVTA (P<0.001 and P<0.001, respectively). There was no significant difference in the trend profile of foveal volume between the two groups (P=0.476).
Trend profile of visual acuity and foveal sensitivity after intravitreal injection of triamcinolone acetonide (IVTA) in BRVO patients with macular oedema. (A) In the Major group and the Macular group, visual acuity improved significantly from before IVTA to 3 and 6 months after IVTA (P=0.001 and P=0.022, respectively). There was no significant difference in the trend profile of visual acuity between the two groups (P=0.640). (B) In the Major group, the foveal sensitivity increased significantly from before IVTA to 3 and 6 months after IVTA (P<0.001). Although foveal sensitivity increased from before IVTA to 3 and 6 months after IVTA in Macular group as well, the changes were not significant (P=0.456). There was no significant difference in the trend profile of foveal sensitivity between the two groups (P=0.502).
In the Major group and the Macular group, visual acuity showed significant improvement from before IVTA to 3 and 6 months after IVTA (P=0.001 and P=0.022, respectively, one-way repeated measures ANOVA) (Fig. 2A). In the Major group, foveal sensitivity also showed a significant increase from before IVTA to 3 and 6 months after IVTA (P<0.001, one-way repeated measures ANOVA). Although foveal sensitivity increased from before IVTA to 3 and 6 months after IVTA in the Macular group as well, the changes were not significant (P=0.456, one-way repeated measures ANOVA) (Fig. 2B). There were no significant differences in the trend profiles of visual acuity and foveal sensitivity between the Major and Macular groups (P=0.640 and P=0.502, respectively, two-way repeated measures ANOVA) (Fig. 2A, B).
Up to 6 months after IVTA, two of the 22 patients (9%) showed an increase of IOP, but this could be controlled by a change of medication. Neovascular glaucoma was not detected in any of the patients. At baseline before treatment, none of the patients had cataract(grade II. There were also no new cases of cataract or progression of existing cataracts and no infectious endophthalmitis after IVTA.
This study showed that foveal thickness and foveal volume were significantly improved from before IVTA 3 and 6 months after IVTA in both the Major group and the Macular group. Triamcinolone acetonide is thought to improve macular oedema by decreasing retinal capillary permeability via its effect on tight junctions [17], or it may inhibit the signaling cascade for VEGF and the VEGF receptor that increases microvascular permeability [18, 19]. Corticosteroids also prevent the production of various inflammatory molecules [20, 21] that promote leukocyte adhesion and breakdown of the blood-retinal barrier [22]. Accordingly, IVTA may have led to a decrease of retinal capillary permeability. However, the foveal thickness and foveal volume of the Major group both increased from 3 to 6 months after IVTA, although not significantly. This may have been because the Major group included four patients with recurrence of macular oedema. In addition, the nonperfused area of the retina was significantly larger in the Major group than the Macular group. We previously reported that vitreous fluid levels of VEGF and sICAM-1 were significantly higher in major BRVO compared with macular BRVO [23]. Therefore, it is possible that higher levels of cytokines in the Major group reduce the response to IVTA over time so that foveal thickness and volume increased from 3 to 6 months in these patients. Because there were no significant differences in the trend profiles of foveal thickness and foveal volume between the Major and Macular groups, our results suggest that the response of foveal thickness and volume to IVTA is similar in patients with either major or macular BRVO. Thus, IVTA seems to improve foveal thickness and volume in BRVO patients regardless of site of the occlusion.
We also found that visual acuity showed significant improvement from before IVTA to 3 and 6 months after IVTA in both groups, and that foveal sensitivity also improved significantly at these times in the Major group. As mentioned above, IVTA may decrease macular oedema, so that visual acuity and foveal sensitivity also improve. However, foveal sensitivity was not significantly increased from before IVTA to 3 or 6 months after IVTA in the Macular group. This may have been because of the small number of patients or else may have been due to a lesser change of foveal sensitivity, because the region involved is small in the Macular group. Interestingly, there were no significant differences in the trend profiles of visual acuity and foveal sensitivity between the Major and Macular groups after IVTA. These results suggest that visual acuity and foveal sensitivity showed a similar response to IVTA in patients with both major BRVO and macular BRVO. Thus, visual acuity and foveal sensitivity were improved by IVTA regardless of the site of occlusion. The improvement of visual acuity and foveal sensitivity in both groups may have been related to restoration of the integrity of the inner segment/outer segment (IS/OS), because Ota et al. reported that integrity of the foveal photoreceptor layer is associated with visual acuity after the resolution of macular oedema [24]. However, we could not evaluate the relation between visual acuity or foveal sensitivity and the IS/OS ratio because we used Stratus OCT in 21 patients and spectral domain OCT in only 1 patient. Accordingly, a larger prospective and randomized study is needed to clarify the relation between visual acuity or foveal sensitivity and photoreceptor layer integrity in BRVO patients with macular oedema.
Other limitations of this study were a short follow-up period, small sample size, and lack of a control group. Cataract progression may not have occurred because the follow up period was too short in the present study, so a longer follow up period might reveal progression of cataract with an influence on macular function. Thus, further investigations will be needed to clarify the relationship between foveal function and the site of venous occlusion (major versus macular) in patients with BRVO.
There were no significant differences in the trend profiles of foveal thickness, foveal volume, visual acuity, and foveal sensitivity between the Major and Macular groups. These results suggest that IVTA can improve foveal morphology, visual acuity, and foveal sensitivity regardless of the site of occlusion in BRVO patients with macular oedema.
Contributions of Authors: H.N. was involved in the design and conduct of study; collection and management of the data were done by H.N.; analysis and interpretation of the data by H.N., K.S., and T.M.; preparation of the first draft of the manuscript by H.N., and review and approval of the manuscript by K.S., and T.M.
[1] Michels RG, Gass JD. The natural course of retinal branch vein obstruction Trans Am Acad Ophthalmol Otolaryngol 1974; 78: OP166-77.
[2] Noma H, Funatsu H, Sakata K, et al. Macular microcirculation and macular oedema in branch retinal vein occlusion Br J Ophthalmol 2009; 93: 630-3.
[3] Orth DH, Patz A. Retinal branch vein occlusion Surv Ophthalmol 1978; 22: 357-76.
[4] Lim JW. Intravitreal bevacizumab and cytokine levels in major and macular branch retinal vein occlusion Ophthalmologica 2011; 225: 150-4.
[5] Joffe L, Goldberg RE, Magargal LE, Annesley WH. Macular branch vein occlusion Ophthalmology 1980; 87: 91-8.
[6] Brown DM, Campochiaro PA, Bhisitkul RB, et al. Sustained benefits from ranibizumab for macular edema following branch retinal vein occlusion: 12-month outcomes of a phase III study Ophthalmology 2011; 118: 1594-602.
[7] Scott IU, Ip MS, VanVeldhuisen PC, et al. A randomized trial comparing the efficacy and safety of intravitreal triamcinolone with standard care to treat vision loss associated with macular Edema secondary to branch retinal vein occlusion: the Standard Care vs Corticosteroid for Retinal Vein Occlusion SCORE study report 6 Arch Ophthalmol 2009; 127: 1115-28.
[8] The Branch Vein Occlusion Study Group. Argon laser photocoagulation for macular edema in branch vein occlusion Am J Ophthalmol 1984; 98: 271-82.
[9] Tachi N, Hashimoto Y, Ogino N. Vitrectomy for macular edema combined with retinal vein occlusion Doc Ophthalmol 1999; 97: 465-9.
[10] Yamaike N, Kita M, Tsujikawa A, Miyamoto K, Yoshimura N. Perimetric sensitivity with the micro perimeter 1 and retinal thickness in patients with branch retinal vein occlusion Am J Ophthalmol 2007; 143: 342-4.
[11] Noma H, Funatsu H, Mimura T, Harino S, Shimada K. Functional-morphologic correlates in patients with branch retinal vein occlusion and macular edema Retina 2011; 31: 2102-8.
[12] Thylefors B, Chylack LT Jr, Konyama K, et al. A simplified cataract grading system Ophthalmic Epidemiol 2002; 9: 83-95.
[13] Noma H, Funatsu H, Mimura T, Shimada K. Macular sensitivity and morphology after intravitreal injection of triamcinolone acetonide for macular edema with branch retinal vein occlusion Retina 2012; 32: 1844-52.
[14] Noma H, Funatsu H, Yamasaki M, et al. Pathogenesis of macular edema with branch retinal vein occlusion and intraocular levels of vascular endothelial growth factor and interleukin-6 Am J Ophthalmol 2005; 140: 256-61.
[15] Noma H, Minamoto A, Funatsu H, et al. Intravitreal levels of vascular endothelial growth factor and interleukin-6 are correlated with macular edema in branch retinal vein occlusion Graefes Arch Clin Exp Ophthalmol 2006; 244: 309-15.
[16] Noma H, Funatsu H, Yamasaki M, et al. Aqueous humour levels of cytokines are correlated to vitreous levels and severity of macular oedema in branch retinal vein occlusion Eye 2008; 22: 42-8.
[17] Antonetti DA, Wolpert EB, DeMaio L, Harhaj NS, Scaduto RC Jr. Hydrocortisone decreases retinal endothelial cell water and solute flux coincident with increased content and decreased phosphorylation of occludin J Neurochem 2002; 80: 667-77.
[18] Zhang X, Bao S, Lai D, Rapkins RW, Gillies MC. Intravitreal triamcinolone acetonide inhibits breakdown of the blood-retinal barrier through differential regulation of VEGF-A and its receptors in early diabetic rat retinas Diabetes 2008; 57: 1026-33.
[19] McAllister IL, Vijayasekaran S, Chen SD, Yu DY. Effect of triamcinolone acetonide on vascular endothelial growth factor and occludin levels in branch retinal vein occlusion Am J Ophthalmol 2009; 147: 838-46. 846 e1-2
[20] Kurtz RM, Elner VM, Bian ZM, Strieter RM, Kunkel SL, Elner SG. Dexamethasone and cyclosporin A modulation of human retinal pigment epithelial cell monocyte chemotactic protein-1 and interleukin-8 Invest Ophthalmol Vis Sci 1997; 38: 436-5.
[21] Mizuno S, Nishiwaki A, Morita H, Miyake T, Ogura Y. Effects of periocular administration of triamcinolone acetonide on leukocyte-endothelium interactions in the ischemic retina Invest Ophthalmol Vis Sci 2007; 48: 2831-6.
[22] Miyamoto K, Khosrof S, Bursell SE, et al. Prevention of leukostasis and vascular leakage in streptozotocin-induced diabetic retinopathy via intercellular adhesion molecule-1 inhibition Proc Natl Acad Sci USA 1999; 96: 10836-41.
[23] Noma H, Funatsu H, Mimura T, Eguchi S, Shimada K. Inflammatory factors in major and macular branch retinal vein occlusion Ophthalmologica 2012; 227: 146-52.
[24] Ota M, Tsujikawa A, Murakami T, et al. Association between integrity of foveal photoreceptor layer and visual acuity in branch retinal vein occlusion Br J Ophthalmol 2007; 91: 1644-9.


text:
/** @constructor */
ScalaJS.c.scala_runtime_Tuple3Zipped$ = (function() {
  ScalaJS.c.java_lang_Object.call(this)
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype = new ScalaJS.inheritable.java_lang_Object();
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.constructor = ScalaJS.c.scala_runtime_Tuple3Zipped$;
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.map$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__O = (function($$this, f$7, cbf$3) {
  var nonLocalReturnKey1 = new ScalaJS.c.java_lang_Object().init___();
  try {
    var b = cbf$3.apply__O__Lscala_collection_mutable_Builder(ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).repr__O());
    var elems2 = ScalaJS.as.scala_collection_IterableLike($$this.$$und2__O()).iterator__Lscala_collection_Iterator();
    var elems3 = ScalaJS.as.scala_collection_IterableLike($$this.$$und3__O()).iterator__Lscala_collection_Iterator();
    ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).foreach__Lscala_Function1__V(new ScalaJS.c.scala_scalajs_runtime_AnonFunction1().init___Lscala_scalajs_js_Function1((function(b$1, elems2$1, elems3$1, f$1, nonLocalReturnKey1$1) {
      return (function(el1) {
        if ((elems2$1.hasNext__Z() && elems3$1.hasNext__Z())) {
          return b$1.$$plus$eq__O__Lscala_collection_mutable_Builder(f$1.apply__O__O__O__O(el1, elems2$1.next__O(), elems3$1.next__O()))
        } else {
          throw new ScalaJS.c.scala_runtime_NonLocalReturnControl().init___O__O(nonLocalReturnKey1$1, b$1.result__O())
        }
      })
    })(b, elems2, elems3, f$7, nonLocalReturnKey1)));
    return b.result__O()
  } catch ($jsexc$) {
    if (ScalaJS.is.scala_runtime_NonLocalReturnControl($jsexc$)) {
      var ex = $jsexc$;
      if ((ex.key__O() === nonLocalReturnKey1)) {
        return ex.value__O()
      } else {
        throw ex
      }
    } else {
      throw $jsexc$
    }
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.flatMap$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__O = (function($$this, f, cbf) {
  var nonLocalReturnKey2 = new ScalaJS.c.java_lang_Object().init___();
  try {
    var b = cbf.apply__O__Lscala_collection_mutable_Builder(ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).repr__O());
    var elems2 = ScalaJS.as.scala_collection_IterableLike($$this.$$und2__O()).iterator__Lscala_collection_Iterator();
    var elems3 = ScalaJS.as.scala_collection_IterableLike($$this.$$und3__O()).iterator__Lscala_collection_Iterator();
    ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).foreach__Lscala_Function1__V(new ScalaJS.c.scala_scalajs_runtime_AnonFunction1().init___Lscala_scalajs_js_Function1((function(b$2, elems2$2, elems3$2, f$2, nonLocalReturnKey2$1) {
      return (function(el1) {
        if ((elems2$2.hasNext__Z() && elems3$2.hasNext__Z())) {
          return ScalaJS.as.scala_collection_mutable_Builder(b$2.$$plus$plus$eq__Lscala_collection_TraversableOnce__Lscala_collection_generic_Growable(ScalaJS.as.scala_collection_TraversableOnce(f$2.apply__O__O__O__O(el1, elems2$2.next__O(), elems3$2.next__O()))))
        } else {
          throw new ScalaJS.c.scala_runtime_NonLocalReturnControl().init___O__O(nonLocalReturnKey2$1, b$2.result__O())
        }
      })
    })(b, elems2, elems3, f, nonLocalReturnKey2)));
    return b.result__O()
  } catch ($jsexc$) {
    if (ScalaJS.is.scala_runtime_NonLocalReturnControl($jsexc$)) {
      var ex = $jsexc$;
      if ((ex.key__O() === nonLocalReturnKey2)) {
        return ex.value__O()
      } else {
        throw ex
      }
    } else {
      throw $jsexc$
    }
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.filter$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__Lscala_Tuple3 = (function($$this, f, cbf1, cbf2, cbf3) {
  var nonLocalReturnKey3 = new ScalaJS.c.java_lang_Object().init___();
  try {
    var b1 = cbf1.apply__O__Lscala_collection_mutable_Builder(ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).repr__O());
    var b2 = cbf2.apply__O__Lscala_collection_mutable_Builder(ScalaJS.as.scala_collection_TraversableLike($$this.$$und2__O()).repr__O());
    var b3 = cbf3.apply__O__Lscala_collection_mutable_Builder(ScalaJS.as.scala_collection_TraversableLike($$this.$$und3__O()).repr__O());
    var elems2 = ScalaJS.as.scala_collection_IterableLike($$this.$$und2__O()).iterator__Lscala_collection_Iterator();
    var elems3 = ScalaJS.as.scala_collection_IterableLike($$this.$$und3__O()).iterator__Lscala_collection_Iterator();
    ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).foreach__Lscala_Function1__V(new ScalaJS.c.scala_scalajs_runtime_AnonFunction1().init___Lscala_scalajs_js_Function1((function(b1$1, b2$1, b3$1, elems2$3, elems3$3, f$3, nonLocalReturnKey3$1) {
      return (function(el1) {
        if ((elems2$3.hasNext__Z() && elems3$3.hasNext__Z())) {
          var el2 = elems2$3.next__O();
          var el3 = elems3$3.next__O();
          if (ScalaJS.uZ(f$3.apply__O__O__O__O(el1, el2, el3))) {
            b1$1.$$plus$eq__O__Lscala_collection_mutable_Builder(el1);
            b2$1.$$plus$eq__O__Lscala_collection_mutable_Builder(el2);
            return b3$1.$$plus$eq__O__Lscala_collection_mutable_Builder(el3)
          } else {
            return ScalaJS.modules.scala_runtime_BoxedUnit().UNIT__Lscala_runtime_BoxedUnit()
          }
        } else {
          throw new ScalaJS.c.scala_runtime_NonLocalReturnControl().init___O__O(nonLocalReturnKey3$1, ScalaJS.modules.scala_runtime_Tuple3Zipped().scala$runtime$Tuple3Zipped$$result$1__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_Tuple3(b1$1, b2$1, b3$1))
        }
      })
    })(b1, b2, b3, elems2, elems3, f, nonLocalReturnKey3)));
    return this.scala$runtime$Tuple3Zipped$$result$1__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_Tuple3(b1, b2, b3)
  } catch ($jsexc$) {
    if (ScalaJS.is.scala_runtime_NonLocalReturnControl($jsexc$)) {
      var ex = $jsexc$;
      if ((ex.key__O() === nonLocalReturnKey3)) {
        return ScalaJS.as.scala_Tuple3(ex.value__O())
      } else {
        throw ex
      }
    } else {
      throw $jsexc$
    }
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.exists$extension__Lscala_Tuple3__Lscala_Function3__Z = (function($$this, f) {
  var nonLocalReturnKey4 = new ScalaJS.c.java_lang_Object().init___();
  try {
    var elems2 = ScalaJS.as.scala_collection_IterableLike($$this.$$und2__O()).iterator__Lscala_collection_Iterator();
    var elems3 = ScalaJS.as.scala_collection_IterableLike($$this.$$und3__O()).iterator__Lscala_collection_Iterator();
    ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).foreach__Lscala_Function1__V(new ScalaJS.c.scala_scalajs_runtime_AnonFunction1().init___Lscala_scalajs_js_Function1((function(elems2$4, elems3$4, f$4, nonLocalReturnKey4$1) {
      return (function(el1) {
        if ((elems2$4.hasNext__Z() && elems3$4.hasNext__Z())) {
          if (ScalaJS.uZ(f$4.apply__O__O__O__O(el1, elems2$4.next__O(), elems3$4.next__O()))) {
            throw new ScalaJS.c.scala_runtime_NonLocalReturnControl$mcZ$sp().init___O__Z(nonLocalReturnKey4$1, true)
          }
        } else {
          throw new ScalaJS.c.scala_runtime_NonLocalReturnControl$mcZ$sp().init___O__Z(nonLocalReturnKey4$1, false)
        };
        return ScalaJS.bV(undefined)
      })
    })(elems2, elems3, f, nonLocalReturnKey4)));
    return false
  } catch ($jsexc$) {
    if (ScalaJS.is.scala_runtime_NonLocalReturnControl($jsexc$)) {
      var ex = $jsexc$;
      if ((ex.key__O() === nonLocalReturnKey4)) {
        return ex.value$mcZ$sp__Z()
      } else {
        throw ex
      }
    } else {
      throw $jsexc$
    }
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.forall$extension__Lscala_Tuple3__Lscala_Function3__Z = (function($$this, f) {
  return (!this.exists$extension__Lscala_Tuple3__Lscala_Function3__Z($$this, new ScalaJS.c.scala_scalajs_runtime_AnonFunction3().init___Lscala_scalajs_js_Function3((function(f$5) {
    return (function(x, y, z) {
      return ScalaJS.bZ((!ScalaJS.uZ(f$5.apply__O__O__O__O(x, y, z))))
    })
  })(f))))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.foreach$extension__Lscala_Tuple3__Lscala_Function3__V = (function($$this, f) {
  var nonLocalReturnKey5 = new ScalaJS.c.java_lang_Object().init___();
  try {
    var elems2 = ScalaJS.as.scala_collection_IterableLike($$this.$$und2__O()).iterator__Lscala_collection_Iterator();
    var elems3 = ScalaJS.as.scala_collection_IterableLike($$this.$$und3__O()).iterator__Lscala_collection_Iterator();
    ScalaJS.as.scala_collection_TraversableLike($$this.$$und1__O()).foreach__Lscala_Function1__V(new ScalaJS.c.scala_scalajs_runtime_AnonFunction1().init___Lscala_scalajs_js_Function1((function(elems2$5, elems3$5, f$6, nonLocalReturnKey5$1) {
      return (function(el1) {
        if ((elems2$5.hasNext__Z() && elems3$5.hasNext__Z())) {
          return f$6.apply__O__O__O__O(el1, elems2$5.next__O(), elems3$5.next__O())
        } else {
          throw new ScalaJS.c.scala_runtime_NonLocalReturnControl$mcV$sp().init___O__Lscala_runtime_BoxedUnit(nonLocalReturnKey5$1, ScalaJS.modules.scala_runtime_BoxedUnit().UNIT__Lscala_runtime_BoxedUnit())
        }
      })
    })(elems2, elems3, f, nonLocalReturnKey5)))
  } catch ($jsexc$) {
    if (ScalaJS.is.scala_runtime_NonLocalReturnControl($jsexc$)) {
      var ex = $jsexc$;
      if ((ex.key__O() === nonLocalReturnKey5)) {
        ex.value$mcV$sp__V()
      } else {
        throw ex
      }
    } else {
      throw $jsexc$
    }
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.hashCode$extension__Lscala_Tuple3__I = (function($$this) {
  return $$this.hashCode__I()
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.equals$extension__Lscala_Tuple3__O__Z = (function($$this, x$1) {
  var x1 = x$1;
  matchEnd4: {
    if (ScalaJS.is.scala_runtime_Tuple3Zipped(x1)) {
      var jsx$1 = true;
      break matchEnd4
    };
    var jsx$1 = false;
    break matchEnd4
  };
  if (jsx$1) {
    if ((x$1 === null)) {
      var Tuple3Zipped$1 = null
    } else {
      var Tuple3Zipped$1 = ScalaJS.as.scala_runtime_Tuple3Zipped(x$1).colls__Lscala_Tuple3()
    };
    return ScalaJS.anyRefEqEq($$this, Tuple3Zipped$1)
  } else {
    return false
  }
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.scala$runtime$Tuple3Zipped$$result$1__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_Tuple3 = (function(b1$1, b2$1, b3$1) {
  return new ScalaJS.c.scala_Tuple3().init___O__O__O(b1$1.result__O(), b2$1.result__O(), b3$1.result__O())
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.scala$runtime$Tuple3Zipped$$result$1__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__ = (function(b1$1, b2$1, b3$1) {
  return this.scala$runtime$Tuple3Zipped$$result$1__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_collection_mutable_Builder__Lscala_Tuple3(b1$1, b2$1, b3$1)
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.equals$extension__Lscala_Tuple3__O__ = (function($$this, x$1) {
  return ScalaJS.bZ(this.equals$extension__Lscala_Tuple3__O__Z($$this, x$1))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.hashCode$extension__Lscala_Tuple3__ = (function($$this$2) {
  return ScalaJS.bI(this.hashCode$extension__Lscala_Tuple3__I($$this$2))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.foreach$extension__Lscala_Tuple3__Lscala_Function3__ = (function($$this$3, f) {
  return ScalaJS.bV(this.foreach$extension__Lscala_Tuple3__Lscala_Function3__V($$this$3, f))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.forall$extension__Lscala_Tuple3__Lscala_Function3__ = (function($$this$4, f$2) {
  return ScalaJS.bZ(this.forall$extension__Lscala_Tuple3__Lscala_Function3__Z($$this$4, f$2))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.exists$extension__Lscala_Tuple3__Lscala_Function3__ = (function($$this$5, f$3) {
  return ScalaJS.bZ(this.exists$extension__Lscala_Tuple3__Lscala_Function3__Z($$this$5, f$3))
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.filter$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__ = (function($$this$6, f$4, cbf1, cbf2, cbf3) {
  return this.filter$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__Lscala_collection_generic_CanBuildFrom__Lscala_Tuple3($$this$6, f$4, cbf1, cbf2, cbf3)
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.flatMap$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__ = (function($$this$7, f$5, cbf) {
  return this.flatMap$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__O($$this$7, f$5, cbf)
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.map$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__ = (function($$this$8, f$6, cbf$2) {
  return this.map$extension__Lscala_Tuple3__Lscala_Function3__Lscala_collection_generic_CanBuildFrom__O($$this$8, f$6, cbf$2)
});
/** @constructor */
ScalaJS.inheritable.scala_runtime_Tuple3Zipped$ = (function() {
  /*<skip>*/
});
ScalaJS.inheritable.scala_runtime_Tuple3Zipped$.prototype = ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype;
ScalaJS.is.scala_runtime_Tuple3Zipped$ = (function(obj) {
  return (!(!((obj && obj.$classData) && obj.$classData.ancestors.scala_runtime_Tuple3Zipped$)))
});
ScalaJS.as.scala_runtime_Tuple3Zipped$ = (function(obj) {
  if ((ScalaJS.is.scala_runtime_Tuple3Zipped$(obj) || (obj === null))) {
    return obj
  } else {
    ScalaJS.throwClassCastException(obj, "scala.runtime.Tuple3Zipped")
  }
});
ScalaJS.isArrayOf.scala_runtime_Tuple3Zipped$ = (function(obj, depth) {
  return (!(!(((obj && obj.$classData) && (obj.$classData.arrayDepth === depth)) && obj.$classData.arrayBase.ancestors.scala_runtime_Tuple3Zipped$)))
});
ScalaJS.asArrayOf.scala_runtime_Tuple3Zipped$ = (function(obj, depth) {
  if ((ScalaJS.isArrayOf.scala_runtime_Tuple3Zipped$(obj, depth) || (obj === null))) {
    return obj
  } else {
    ScalaJS.throwArrayCastException(obj, "Lscala.runtime.Tuple3Zipped;", depth)
  }
});
ScalaJS.data.scala_runtime_Tuple3Zipped$ = new ScalaJS.ClassTypeData({
  scala_runtime_Tuple3Zipped$: 0
}, false, "scala.runtime.Tuple3Zipped$", ScalaJS.data.java_lang_Object, {
  scala_runtime_Tuple3Zipped$: 1,
  java_lang_Object: 1
});
ScalaJS.c.scala_runtime_Tuple3Zipped$.prototype.$classData = ScalaJS.data.scala_runtime_Tuple3Zipped$;
ScalaJS.moduleInstances.scala_runtime_Tuple3Zipped = undefined;
ScalaJS.modules.scala_runtime_Tuple3Zipped = (function() {
  if ((!ScalaJS.moduleInstances.scala_runtime_Tuple3Zipped)) {
    ScalaJS.moduleInstances.scala_runtime_Tuple3Zipped = new ScalaJS.c.scala_runtime_Tuple3Zipped$().init___()
  };
  return ScalaJS.moduleInstances.scala_runtime_Tuple3Zipped
});
//@ sourceMappingURL=Tuple3Zipped$.js.map


text:
package net.mojeto.timelapsecalc.app;

//import net.mojeto.timelapsecalc.app.fragments.FrameRateFragment;

import java.util.HashMap;
import java.util.Map;

/**
 * Created by honza on 21.6.14.
 */
public enum ValueForChange
{

    CAMERA_FRAME_DURATION(0),
    CAMERA_RECORD_DURATION(1),
    VIDEO_FRAME_RATE(2),
    VIDEO_DURATION(3),
    CAMERA_FRAMES(4),
    VIDEO_FRAMES(5);

    private static Map<Integer, ValueForChange> enumMap = new HashMap<Integer,ValueForChange>(6);
    private int code;

    static {
        for (ValueForChange value: ValueForChange.values() ) {
            enumMap.put(value.getCode(), value);
        }
    }

    public static ValueForChange getInstanceForCode(int code) {
        return enumMap.get(code);
    }

    private ValueForChange(int code) {
        this.code = code;
    }

    public int getCode() {
        return code;
    }

}