Monday, May 31, 2010
How Many Calories In Plain Chow Mein
Some details of the central carpet of sand, to 11 days of Corpus
Thursday, May 20, 2010
Sitting Stomach Feet Face
UML, UML
The post Aggregation and Composition raised another question (as always seems to happen , and I always give the debate to something else). The question comes on the side of the difference between Association and Aggregation in code. It argues that it is something conceptual, which is not represented in code. My answer is that it is 50% correct. Because, as I mentioned before (the label design is more about it), the Association came first, and aggregation would be a particular type of association. Ergo ... Aggregation "IS-A" partnership item for you! . First we see the UML diagram
Now let the code of the class Person (Note: Imagine that generics blogspot takes them as tags, so do not appear)
The main differences are that:
Well, I hope I cleared any doubts, and to open:) Greetings.
The post Aggregation and Composition raised another question (as always seems to happen , and I always give the debate to something else). The question comes on the side of the difference between Association and Aggregation in code. It argues that it is something conceptual, which is not represented in code. My answer is that it is 50% correct. Because, as I mentioned before (the label design is more about it), the Association came first, and aggregation would be a particular type of association. Ergo ... Aggregation "IS-A" partnership item for you! . First we see the UML diagram
Now let the code of the class Person (Note: Imagine that generics blogspot takes them as tags, so do not appear)
import java.util.List;
public
class Person {private String
name;
private String name;
private Photo photo;
private List lugaresFrecuentes;
List private communications;
public String getName () {return name;} public void
setNombre (String name) {this.name = name;}
getApellido public String () {return name;} public void
setApellido (String name) {this.apellido = name;}
/ / public
Photo Picture Association getFoto () {return photo;} public void
setFoto (Photo photo) {this.foto = photo;}
/ / public List getLugaresFrecuentes () {return lugaresFrecuentes;}
/ / public void setLugaresFrecuentes (List lugaresFrecuentes) {this.lugaresFrecuentes = lugaresFrecuentes;}
/ / public void
agregarLugar Aggregation (Place place) {
lugaresFrecuentes.add (location);
} public boolean
quitarLugar (Place place) {return
lugaresFrecuentes.remove (location);}
/ / public void
setComunicaciones Association (List communications) {
this.comunicaciones = communications;}
getComunicaciones public List () {return
communications;
}}
The main differences are that:
- The Aggregation are always collections or arrays ! Or something that serves as a container for "add" more than one object, but add one. (If no setter and would not add, add)
- The Aggregation has two methods : one for "add" one object to the list, and the other to remove the same.
- Aggregation can, of course, be the setter and getter methods , while the Association always have that place and get a reference variable of the same type of variable or class instance, in this
List case.
Well, I hope I cleared any doubts, and to open:) Greetings.
Tuesday, May 18, 2010
Planet Pin Ball At Funbraine.com
I photo competition: The Carpet Acts
Date: 15/04/2010 to 28/05/2010
Photo Contest Rules
JURY. The jury will be composed of persons appointed by the Association Carpet Villa de La Orotava, whose names will be announced on record once again failed prizes.
CUSTODY AND CONSERVATION OF WORKS. The winning works will be held by the Association Carpet Villa de La Orotava, which reserves the right to reproduce in the future, in the form and dimensions that may be necessary; for it in the envelope containing the participant's data shall be entered as follows: "In the course of winning the" I PHOTO CONTEST: THE CARPET OF OROTAVA "I give the property to the Association Carpet Villa de La Orotava, which reserves all rights on the work. "
The award winning pieces may be withdrawn within 30 days counted from the end of the exhibition of work. Once said period without the works have been withdrawn, be deemed to relinquish copyright ownership of the same on behalf of the Association of Carpet Villa de La Orotava, which may be spent on what it deems most appropriate.
All works will be displayed in the places listed above on the 4th day June 18, 2010.
The organization will have the greatest care in preserving the works, but not responsible for any damage that may occur over time under their custody.
Taking part implies knowledge and acceptance of all contest rules. PARTICIPANTS
people to participate, all they want, living in Spain and over 16 years. THEMATIC
Photographs submitted must contain and deal only and exclusively the subject of rugs Corpus de la Villa de La Orotava, which refers to those held in Corpus Infraocatva in this town, and any other photo being discarded not belonging to this area. WORK
will be two categories: Photographs
"old" since the beginning of our carpets in this town until 1979. Photo
"modern": from the year 1980 and even today.
Each participant may submit a maximum of three photos per category. PRESENTATION
Entries should be submitted without identifying the author, stating the title of the work in the back of the photograph. The work will be accompanied by a sealed envelope containing a card with the complete personal data (name, surname, ID number, address, telephone number, date of birth), and the title and a brief description of the work, year type of carpet, where they quoted the picture ....
Photos must be submitted on photographic paper, a size 30 x 40, with support of white foam board or black 35x45 cm. Delivery
Pictures:
The Carpet Museum, from 10:00 to 13:00. And from 16:00 to 18:00 hrs. Monday through Friday, located on Calle San Francisco n º 5, stating on the outside of the envelope, "I PHOTO CONTEST: THE CARPET OF OROTAVA." This address will be provided by the photographs submitted by post. FILING DEADLINES
The organization sets the date of delivery limits of the photographs on May 28, 2010, and the time and place above collection. The works submitted by post will not enter into competition if they reach the Carpet Museum after this time.
AWARDS
Association Carpet Villa de La Orotava awarded a prize by category:
Category old photographs:
1 st PRIZE: 200 €
Category Modern Photography:
1 st PRIZE: 300 €
The jury is entitled to award second prize or special mention to those papers submitted that based on the quality of them and considered.
The jury's verdict and award ceremony will take place at the opening ceremony of the photo exhibition that in fact the competition draw to be held in the courtyard of the Museum of Carpets and interior arcades in the courtyard of the Hon. Ayto de la Villa de La Orotava. The opening ceremony and awards ceremony will be held on Friday, June 4, 2010 in the municipality of Villa de La Orotava, at 20:30.
awards can be declared void, if the jury, no work had satisfied the conditions required or deemed poor quality of the photographs submitted. 
Date: 15/04/2010 to 28/05/2010
Photo Contest Rules
JURY. The jury will be composed of persons appointed by the Association Carpet Villa de La Orotava, whose names will be announced on record once again failed prizes.
CUSTODY AND CONSERVATION OF WORKS. The winning works will be held by the Association Carpet Villa de La Orotava, which reserves the right to reproduce in the future, in the form and dimensions that may be necessary; for it in the envelope containing the participant's data shall be entered as follows: "In the course of winning the" I PHOTO CONTEST: THE CARPET OF OROTAVA "I give the property to the Association Carpet Villa de La Orotava, which reserves all rights on the work. "
The award winning pieces may be withdrawn within 30 days counted from the end of the exhibition of work. Once said period without the works have been withdrawn, be deemed to relinquish copyright ownership of the same on behalf of the Association of Carpet Villa de La Orotava, which may be spent on what it deems most appropriate.
All works will be displayed in the places listed above on the 4th day June 18, 2010.
The organization will have the greatest care in preserving the works, but not responsible for any damage that may occur over time under their custody.
Taking part implies knowledge and acceptance of all contest rules. PARTICIPANTS
people to participate, all they want, living in Spain and over 16 years. THEMATIC
Photographs submitted must contain and deal only and exclusively the subject of rugs Corpus de la Villa de La Orotava, which refers to those held in Corpus Infraocatva in this town, and any other photo being discarded not belonging to this area. WORK
will be two categories: Photographs
"old" since the beginning of our carpets in this town until 1979. Photo
"modern": from the year 1980 and even today.
Each participant may submit a maximum of three photos per category. PRESENTATION
Entries should be submitted without identifying the author, stating the title of the work in the back of the photograph. The work will be accompanied by a sealed envelope containing a card with the complete personal data (name, surname, ID number, address, telephone number, date of birth), and the title and a brief description of the work, year type of carpet, where they quoted the picture ....
Photos must be submitted on photographic paper, a size 30 x 40, with support of white foam board or black 35x45 cm. Delivery
Pictures:
The Carpet Museum, from 10:00 to 13:00. And from 16:00 to 18:00 hrs. Monday through Friday, located on Calle San Francisco n º 5, stating on the outside of the envelope, "I PHOTO CONTEST: THE CARPET OF OROTAVA." This address will be provided by the photographs submitted by post. FILING DEADLINES
The organization sets the date of delivery limits of the photographs on May 28, 2010, and the time and place above collection. The works submitted by post will not enter into competition if they reach the Carpet Museum after this time.
AWARDS
Association Carpet Villa de La Orotava awarded a prize by category:
Category old photographs:
1 st PRIZE: 200 €
Category Modern Photography:
1 st PRIZE: 300 €
The jury is entitled to award second prize or special mention to those papers submitted that based on the quality of them and considered.
The jury's verdict and award ceremony will take place at the opening ceremony of the photo exhibition that in fact the competition draw to be held in the courtyard of the Museum of Carpets and interior arcades in the courtyard of the Hon. Ayto de la Villa de La Orotava. The opening ceremony and awards ceremony will be held on Friday, June 4, 2010 in the municipality of Villa de La Orotava, at 20:30.
awards can be declared void, if the jury, no work had satisfied the conditions required or deemed poor quality of the photographs submitted.
Friday, May 14, 2010
Howto Edit Licence.dat
Orotava Day Museum Calendar of Events
The days of the Museum of La Orotava, to celebrate International Museums Day (May 18) will start from Friday the 14.
So until 18 the entrance to Carpet Museum [San Francisco Street # 5, next to the Casa de los Balcones] is free (normally costs 2 €). The facility will be open between 10:00 and 14:00 hours.
On Friday and Monday, two days are devoted to primary schools, and high school in the municipality.
Saturday will be the turn of the Third Age of the town, and Sunday from 10:00 am is the day of the family. So, that day in our museum, we have various workshops at 11:00 and a performance of magic at 12:30. Also this day, there will tours.
The musical performance will be Monday 17 (TBD) at 20:30.
On Tuesday [18] is the International Museum Day , with regular scheduled visits free.
So until 18 the entrance to Carpet Museum [San Francisco Street # 5, next to the Casa de los Balcones] is free (normally costs 2 €). The facility will be open between 10:00 and 14:00 hours.
On Friday and Monday, two days are devoted to primary schools, and high school in the municipality.
Saturday will be the turn of the Third Age of the town, and Sunday from 10:00 am is the day of the family. So, that day in our museum, we have various workshops at 11:00 and a performance of magic at 12:30. Also this day, there will tours.
The musical performance will be Monday 17 (TBD) at 20:30.
On Tuesday [18] is the International Museum Day , with regular scheduled visits free.
Thursday, May 13, 2010
Bluntville Blunt Wraps
Association and Aggregation, Aggregation and Composition
Vincentian I've seen too many discussions about the differences between aggregation and composition in UML class diagrams. Indeed, every so often, someone comes and asks me what the difference in the code and explains his own theories on this issue, this debate is almost as extensive as that of extends and includes the use cases.
Let us begin, we must always remember that one of the biggest criticisms we get UML is that it has saved many ambiguities ... But not all! there are still concepts that lend themselves to dual interpretations, do not know if this will be one of them, but it looks like it discussed. On the other hand, we can make a little history, recalling that first existed the association, then there is the aggregation to represent a structural relationship container / contained and then as an "extension" of the latter composition is born.
To explain my point of view I'll take his hand, the class diagram I have used in another post and then I'll put the Person class code, which is what takes all the burden of the discussion
The code refers only to this model, and is very detailed, even with unnecessary things, or merely theoretical, but what I want is to fix a position, specific and definitive on the subject of relationships.
important thing to keep in mind is that an object exists (say, alive, but this is not technically correct because it is not a thread) while there is a reference variable "point" (also correct that no java has pointers, heh) to the object in memory. Ie, they become eligible for deletion by the garbage collector when there is no variable "point" to that object.
The class usually begins with the declaration of instance variables. Where profiles and lugaresFrecuentes are two collections, but quietly could be arrays. to be transformed into containers of items. As properties have getters and setters (accessors and mutators), which have nothing to do with the aggregation and composition.
Now let's see what are the methods that characterize the relationship AGGREGATION
public void
The first is that the class contains two methods one that adds items to the collection and another that it eliminates . I have something important here ... objects are passed as parameter have not been instantiated in the method, ie we have not made the new object. "Born" elsewhere and we've been through parameter the method to be added to the list lugaresFrecuentes. In other words, the object could die, and the object AHUN could maintain an active reference in any other part of our code so their life cycles are not tied streaks. Not born or dies within the Person.
What is the Difference STRUCTURE?
"the new object is performed within the method to add"
Profile 
Vincentian I've seen too many discussions about the differences between aggregation and composition in UML class diagrams. Indeed, every so often, someone comes and asks me what the difference in the code and explains his own theories on this issue, this debate is almost as extensive as that of extends and includes the use cases.
Let us begin, we must always remember that one of the biggest criticisms we get UML is that it has saved many ambiguities ... But not all! there are still concepts that lend themselves to dual interpretations, do not know if this will be one of them, but it looks like it discussed. On the other hand, we can make a little history, recalling that first existed the association, then there is the aggregation to represent a structural relationship container / contained and then as an "extension" of the latter composition is born.
To explain my point of view I'll take his hand, the class diagram I have used in another post and then I'll put the Person class code, which is what takes all the burden of the discussion
The code refers only to this model, and is very detailed, even with unnecessary things, or merely theoretical, but what I want is to fix a position, specific and definitive on the subject of relationships. important thing to keep in mind is that an object exists (say, alive, but this is not technically correct because it is not a thread) while there is a reference variable "point" (also correct that no java has pointers, heh) to the object in memory. Ie, they become eligible for deletion by the garbage collector when there is no variable "point" to that object.
import java.util.LinkedList;
import java.util.List;
public class Person {private String name;
private String name;
private List profiles = new LinkedList (); Private List
lugaresFrecuentes = new LinkedList ();
/ / Getters and Setters public String
getName () {return name;} public void
setNombre (String name) {this.name = name;} public String
getApellido () {return name;} public void
setApellido (String name) {this.apellido = name;}
/ / OJO not confuse these are just setters and getters for properties
getPerfiles public List () {return profiles; } public void
setPerfiles (List profiles) {this.perfiles = profiles;}
getLugaresFrecuentes public List () {return lugaresFrecuentes;} public void
setLugaresFrecuentes (List lugaresFrecuentes) {this.lugaresFrecuentes = lugaresFrecuentes;}
The class usually begins with the declaration of instance variables. Where profiles and lugaresFrecuentes are two collections, but quietly could be arrays. to be transformed into containers of items. As properties have getters and setters (accessors and mutators), which have nothing to do with the aggregation and composition.
Now let's see what are the methods that characterize the relationship AGGREGATION
public void
agregarLugarFrecuenta (Place place)
{if (! lugaresFrecuentes.contains (place)) {
lugaresFrecuentes.add (location);
}} public void
removerLugarFrecuenta (Place place) {
if (lugaresFrecuentes.contains (place)) {
lugaresFrecuentes. remove (place);
}}
The first is that the class contains two methods one that adds items to the collection and another that it eliminates . I have something important here ... objects are passed as parameter have not been instantiated in the method, ie we have not made the new object. "Born" elsewhere and we've been through parameter the method to be added to the list lugaresFrecuentes. In other words, the object could die, and the object AHUN could maintain an active reference in any other part of our code so their life cycles are not tied streaks. Not born or dies within the Person.
What is the Difference STRUCTURE?
agregarPerfil public void () {
Profile p = new Profile ();
perfiles.add (p);}
/ / public void overload
agregarPerfil (String name) {
Profile p = new Profile (name )
perfiles.add (p);}
removerPerfil public void (int index) {
perfiles.remove (index); / / Here we remove it from the list}
Well ... the composition also has methods to add and delete. But ... "the new object is performed within the method to add"
instantiation of the object p is made within the add and the reference method does not return (that is void or boolean), the local reference variable will cease to exist once the method finishes running, and the life cycle of that particular instance will be tied to the list, and therefore the Person. Once the object is being referenced person not more (or die, although technically it is not) the object list be no reference, and therefore its elements as well. Furthermore the method is not static, it must first create an instance of Person, then you can add a profile. Starting and to "bind" the life cycle of a profile, that of a person. As for the method
removed, there is nothing extraordinary, simply remove an item from the list.
Deepening and playing with the theory, so that finally we tie the cycles of life, lugaresFrecuentes variable should not be property, and the Profile class should be an Inner Class . In
removed, there is nothing extraordinary, simply remove an item from the list.
getting paranoid theory of paranoia
Deepening and playing with the theory, so that finally we tie the cycles of life, lugaresFrecuentes variable should not be property, and the Profile class should be an Inner Class . In
Inner case of class, we do this so that they have to use an instance of the class "Outer" and then get an instance of class Inner. For example if in our code, the class profile, has an Inner class public class Person (means no, "that is within the file that Persona.java) to get Profile instance out of class person would to do:
Person person = new Person ();
Persona.Perfil persona.new profile = Profile ();
Profile
And the kind exist as long as the instance of person. (Life cycles tied)
For instance variable that should not have lugaresFrecuentes public getters and setters, this is because no other class, except for the Person class, should have the opportunity to hold a live reference to an object container. And much less get all the list from the outside! A Profile object lives and dies with the person!
this also may release other delusions, such as questions of inheritance and the like.
But again, and I will not tire of saying ... This is an extreme!, it's just to chat with friends, or boast with a professor, there is nothing practical, or real, except in specific cases.
"They thought we were done? can be even more paranoid!! much has been discussed on these issues, and much was paranoia theoretical. The following is something that will take them to your friends and teacher to say, "... well but that's crazy"
override the finalize () method of class Person, which is a method that all classes inherit Object, and is invoked just before an object is erased from memory by the garbage collector for java.
unreferenced In each of the items in the list a second before the object type person disappears from memory, a millisecond, or something! finally tying the birth and death, the life cycle of a content item with its container.
But again! PARANOIA IN THE CODE IS NOT GOOD! only serves those nights of binge drinking among programmers, which closed bowling and paint stay home with friends.
I rescue all this biri-biri that "the new method is performed within the" and nothing more!
But again, and I will not tire of saying ... This is an extreme!, it's just to chat with friends, or boast with a professor, there is nothing practical, or real, except in specific cases.
Paranoia Paranoia of
"They thought we were done? can be even more paranoid!! much has been discussed on these issues, and much was paranoia theoretical. The following is something that will take them to your friends and teacher to say, "... well but that's crazy"
override the finalize () method of class Person, which is a method that all classes inherit Object, and is invoked just before an object is erased from memory by the garbage collector for java.
public void finalize () {
for (Profile p: profiles) {
p = null;
}}
unreferenced In each of the items in the list a second before the object type person disappears from memory, a millisecond, or something! finally tying the birth and death, the life cycle of a content item with its container.
But again! PARANOIA IN THE CODE IS NOT GOOD! only serves those nights of binge drinking among programmers, which closed bowling and paint stay home with friends.
I rescue all this biri-biri that "the new method is performed within the" and nothing more!
Wednesday, May 12, 2010
How To Full Version Easyshare
few weeks ago after I decided to pay the Java 1.6 SCJP certification. The truth is that initially, I was half confused and difficult. But after As I studied the book of Revelation and translated it, because the only version that exists is in English, and also the test is in English, I acquired a higher rate for the resolution of the exercises. I have learned a lot of things to know about language. This is very good and super aconcejable, so they have a time (Notec I said no time and little time) can be entrusted with this campaign. There is plenty of info on the web on how to surrender, or extensive googling "SCJP Java 1.6" for toparce with forums, blogs and pages that contain PDF manuals, algununos simulators, juices etc. What is not in plain view is tips and strategy to tackle the exam.
In my own case, and talking with some friends who had already surrendered, I realized that the primary key is the time, again in my personal case, and do not know if all versions of the review are the same, but had with 60 questions, and a maximum time resolution of 3 hours. That if we have the fingers gives us a total of 3 minutes per question. Well, there are questions ExED far this time, and code that have long, confusing and, if we add that there are way too tramoposas questions in the examination, so even though we "don java" if we sleep for a second we will spend some import or semicolon or something. I did not know what would be the length, or how many questions would have, because every page was a different length, so I decided to train with resulución with a time of 4 minutes per question, questions of the book, and not well managed AHUN resolve them all. Come the day, and realizing that he had only 3 minutes, I decided not to dig in both questions, and if they had "cheated" so be it. The hypothesis was that would be less. And for my first attempt, I got certified. Furthermore I'm about 15 minutes to make a quick review of the test where reveer achieve 30% of the questions and save 2.
Some useful data in Argentina:
- Running Time: 3 hours (180 min)
- Total Questions: 60
- Score to pass: 58% (35 Questions)
- Eye with drag and drop questions can be reset
- Code of exam: 310-065
- Paper (PDF): Sun Certified Programmer for Java 6 - Study
Guide - Book Paper: Sun Certified Programmer for Java 6 - Practice Exams (Do not bother to look at PDF, leaving only the paper version, and no longer available, so if someone has it in PDF so I could enable .
- Simulators: Wizlabs, Sybex, intrepid
- 1 Blog: http://scjp-sun.blogspot.com/
- Games to practice: http://faq.javaranch.com/java/ScjpMockTests
- info on Certification: http://osum.sun.com/
- Where to register to pay:
www.prometric.com
Lic Ariel Diaz Molina
Certified Java Programmer
Monday, May 10, 2010
Swollen Gums And Streph Throat
, 2010
We have already started work on the natural sand rug in the Plaza del Ayuntamiento de La Orotava, and will shortly publish a photo gallery. It will include a sketch of the tapestry, as snapshots of the early days of work. With this, we will continue to monitor the work of this carpet.
Here are key dates to consider by tod @ sl @ s Carpet:
We have already started work on the natural sand rug in the Plaza del Ayuntamiento de La Orotava, and will shortly publish a photo gallery. It will include a sketch of the tapestry, as snapshots of the early days of work. With this, we will continue to monitor the work of this carpet.
Here are key dates to consider by tod @ sl @ s Carpet:
- Thursday May 27, 2010 : Parish House Meeting organized by the parish priest Antonio Hernández. It projected the photographs of carpets 2009, e serve a little toast.
- Friday May 28, 2010: Ends the deadline for submission of photographs I PHOTO CONTEST: Carpets of La Orotava.
- Friday June 4, 2010 : Opening and Awards Ceremony I PHOTO CONTEST: Carpets of La Orotava, in the courtyards of the City of La Orotava (at 20:30).
- Saturday June 5, 2010 : Carpet Children's Day, from 10:00 am around the Conception Parish.
- Wednesday June 9, 2010: Concert FIESTA DE LAS FLORES. Theobald Power Auditorium (at 21:00)
- Thursday June 10, 2010: Octave of Corpus Christie. BIG DAY
CARPETS - -7:15 hours .- Mass of the carpets. Then chocolate.
-7:30 hours .- Top making the Flower Carpet by the usual route.
-18:30 hours .- THE CELEBRATION OF THE EUCHARIST CORPUS CHRISTI procession back to the travel and subsistence carpeting SDM blessing from the balcony of City Hall.
Subscribe to:
Comments (Atom)