Commit 332d1011 by roshka

se agregaron archivos

parents
Seleccionar cada archivo y darle Run File para que ejecute ese archivo.
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8"?>
<!-- You may freely edit this file. See commented blocks below for -->
<!-- some examples of how to customize the build. -->
<!-- (If you delete it and reopen the project it will be recreated.) -->
<!-- By default, only the Clean and Build commands use this build script. -->
<!-- Commands such as Run, Debug, and Test only use this build script if -->
<!-- the Compile on Save feature is turned off for the project. -->
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
<!-- in the project's Project Properties dialog box.-->
<project name="Ejercicio01" default="default" basedir=".">
<description>Builds, tests, and runs the project Ejercicio01.</description>
<import file="nbproject/build-impl.xml"/>
<!--
There exist several targets which are by default empty and which can be
used for execution of your tasks. These targets are usually executed
before and after some main targets. They are:
-pre-init: called before initialization of project properties
-post-init: called after initialization of project properties
-pre-compile: called before javac compilation
-post-compile: called after javac compilation
-pre-compile-single: called before javac compilation of single file
-post-compile-single: called after javac compilation of single file
-pre-compile-test: called before javac compilation of JUnit tests
-post-compile-test: called after javac compilation of JUnit tests
-pre-compile-test-single: called before javac compilation of single JUnit test
-post-compile-test-single: called after javac compilation of single JUunit test
-pre-jar: called before JAR building
-post-jar: called after JAR building
-post-clean: called after cleaning build products
(Targets beginning with '-' are not intended to be called on their own.)
Example of inserting an obfuscator after compilation could look like this:
<target name="-post-compile">
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
For list of available properties check the imported
nbproject/build-impl.xml file.
Another way to customize the build is by overriding existing main targets.
The targets of interest are:
-init-macrodef-javac: defines macro for javac compilation
-init-macrodef-junit: defines macro for junit execution
-init-macrodef-debug: defines macro for class debugging
-init-macrodef-java: defines macro for class execution
-do-jar: JAR building
run: execution of project
-javadoc-build: Javadoc generation
test-report: JUnit report generation
An example of overriding the target for project execution could look like this:
<target name="run" depends="Ejercicio01-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
Notice that the overridden target depends on the jar target and not only on
the compile target as the regular run target does. Again, for a list of available
properties which you can use, check the target you are overriding in the
nbproject/build-impl.xml file.
-->
</project>
Manifest-Version: 1.0
X-COMMENT: Main-Class will be added automatically by build
build.xml.data.CRC32=b4dbee64
build.xml.script.CRC32=04e8461a
build.xml.stylesheet.CRC32=8064a381@1.80.1.48
# This file is used by a NetBeans-based IDE to track changes in generated files such as build-impl.xml.
# Do not edit this file. You may delete it but then the IDE will never regenerate such files for you.
nbproject/build-impl.xml.data.CRC32=b4dbee64
nbproject/build-impl.xml.script.CRC32=bf139476
nbproject/build-impl.xml.stylesheet.CRC32=830a3534@1.80.1.48
compile.on.save=true
user.properties.file=C:\\Users\\Lucas Maidana\\AppData\\Roaming\\NetBeans\\8.2\\build.properties
annotation.processing.enabled=true
annotation.processing.enabled.in.editor=false
annotation.processing.processor.options=
annotation.processing.processors.list=
annotation.processing.run.all.processors=true
annotation.processing.source.output=${build.generated.sources.dir}/ap-source-output
build.classes.dir=${build.dir}/classes
build.classes.excludes=**/*.java,**/*.form
# This directory is removed when the project is cleaned:
build.dir=build
build.generated.dir=${build.dir}/generated
build.generated.sources.dir=${build.dir}/generated-sources
# Only compile against the classpath explicitly listed here:
build.sysclasspath=ignore
build.test.classes.dir=${build.dir}/test/classes
build.test.results.dir=${build.dir}/test/results
# Uncomment to specify the preferred debugger connection transport:
#debug.transport=dt_socket
debug.classpath=\
${run.classpath}
debug.test.classpath=\
${run.test.classpath}
# Files in build.classes.dir which should be excluded from distribution jar
dist.archive.excludes=
# This directory is removed when the project is cleaned:
dist.dir=dist
dist.jar=${dist.dir}/Ejercicio01.jar
dist.javadoc.dir=${dist.dir}/javadoc
excludes=
includes=**
jar.compress=false
javac.classpath=
# Space-separated list of extra javac options
javac.compilerargs=
javac.deprecation=false
javac.external.vm=true
javac.processorpath=\
${javac.classpath}
javac.source=1.8
javac.target=1.8
javac.test.classpath=\
${javac.classpath}:\
${build.classes.dir}
javac.test.processorpath=\
${javac.test.classpath}
javadoc.additionalparam=
javadoc.author=false
javadoc.encoding=${source.encoding}
javadoc.noindex=false
javadoc.nonavbar=false
javadoc.notree=false
javadoc.private=false
javadoc.splitindex=true
javadoc.use=true
javadoc.version=false
javadoc.windowtitle=
main.class=ejercicio01.Ejercicio01
manifest.file=manifest.mf
meta.inf.dir=${src.dir}/META-INF
mkdist.disabled=false
platform.active=default_platform
run.classpath=\
${javac.classpath}:\
${build.classes.dir}
# Space-separated list of JVM arguments used when running the project.
# You may also define separate properties like run-sys-prop.name=value instead of -Dname=value.
# To set system properties for unit tests define test-sys-prop.name=value:
run.jvmargs=
run.test.classpath=\
${javac.test.classpath}:\
${build.test.classes.dir}
source.encoding=UTF-8
src.dir=src
test.src.dir=test
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://www.netbeans.org/ns/project/1">
<type>org.netbeans.modules.java.j2seproject</type>
<configuration>
<data xmlns="http://www.netbeans.org/ns/j2se-project/3">
<name>Ejercicio01</name>
<source-roots>
<root id="src.dir"/>
</source-roots>
<test-roots>
<root id="test.src.dir"/>
</test-roots>
</data>
</configuration>
</project>
package ejercicio01;
import java.util.Scanner;
public class Ejercicio01 {
public static void main(String[] args) {
Scanner scan = new Scanner (System.in);
Scanner scan2 = new Scanner (System.in);
System.out.println ("Inserte el primer valor");
double valor1= scan.nextDouble();
System.out.println ("\nInserte el segundo valor");
double valor2=scan.nextDouble();
double resultado1= valor1+valor2;
double resultado2=valor1-valor2;
double resultado3=valor1*valor2;
double resultado4=valor1/valor2;
double resultado5=(valor1%valor2);
System.out.println ("La suma de " + valor1 + " y " + valor2 + " es: " + resultado1);
System.out.print ("\nLa resta es de " + valor1 + " y " + valor2 + " es: " + resultado2);
System.out.print ("\nLa multiplicacion es de " + valor1 + " y " + valor2 + " es: " + resultado3);
System.out.print ("\nLa divison es de " + valor1 + " y " + valor2 + " es: " + resultado4);
System.out.print ("\nEl resto es de " + valor1 + " y " + valor2 + " es: " + resultado5);
}
}
package ejercicio01;
import java.util.Scanner;
/**
*
* @author Lucas Maidana
*/
public class Ejercicio02 {
/**
* @param args the command line arguments
*/
public static void main(String[] args) {
// TODO code application logic here
Scanner scan = new Scanner (System.in);
Scanner scan2 = new Scanner (System.in);
System.out.println ("Inserte el primer valor");
int valor1= scan.nextInt();
System.out.println ("\nInserte el segundo valor");
int valor2=scan.nextInt();
if (valor1>valor2)
{
System.out.println ("El primer valor es mayor" );
}
if (valor1==valor2)
{
System.out.println ("Son iguales");
}
if (valor1<valor2)
{
System.out.println ("El segundo valor es mayor");
}
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio03 {
public static void main(String[] args)
{
Scanner scan = new Scanner (System.in);
System.out.println (" ");
String nom= "Lucas";
System.out.print ("Bienvenido " + nom);
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio04 {
public static void main(String[] args)
{
Scanner scan = new Scanner (System.in);
String nom= scan.nextLine();
System.out.print ("Bienvenido " + nom);
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio05 {
public static void main(String[] args)
{
Scanner scan = new Scanner (System.in);
int num= scan.nextInt();
if (num%2==0)
{
System.out.println ("Es divisible entre dos");
}
else
{
System.out.print ("No es divisible entre dos");
}
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio06 {
public static void main(String[] args)
{
double IVA = 0.1;
Scanner scan = new Scanner (System.in);
double precio = scan.nextDouble();
double preciof = precio+precio*IVA;
System.out.println ("El precio final es de " + preciof);
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio07 {
public static void main(String[] args)
{
for (int i=0; i<=100; i++)
{
if (i%2==0 && i%3==0)
{
int numero=i;
System.out.print ("\n " + numero + " es divisible entre 2 y 3");
}
}
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio08 {
public static void main(String[] args)
{
Scanner scan = new Scanner (System.in);
int a;
do {
System.out.println("Inserte un numero");
a = scan.nextInt();
System.out.println ("El numero es: " + a);
} while (a<0);
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio09 {
public static void main(String[] args)
{
int C=0;
String password="roshka";
Scanner scan = new Scanner (System.in);
String contraseña= scan.nextLine();
if (contraseña.equals(password))
{
System.out.println ("Contraseña correcta!");
}
while (!contraseña.equals(password) && C<=2)
{
C=C+1;
System.out.println("Fallaste! jajaja");
contraseña=scan.nextLine();
if (C==3)
{
System.out.println ("Ya no puedes ingresar tu contraseña");
}
}
}
}
package ejercicio01;
import java.util.Scanner;
public class Ejercicio10 {
public static void main(String[] args)
{
String a;
Scanner scan = new Scanner (System.in);
System.out.println ("Inserte que dia de la semana es");
a = scan.nextLine();
if (a.equalsIgnoreCase("sabado") | a.equalsIgnoreCase("domingo"))
{
System.out.println ("No es día laboral");
}
else{
System.out.println ("Es dia laboral");
}
}
}
1-Es la parte del navegador encargada de despegar la información o contenido.
2-Le explicaría que los navegadores no solo se trata de lo que ve, que dentro de ellos hay un "motor" que hace que funcione y sea posible mas que nada visualizar todo.
3-Google chrome: Blink
Google chromeAndroid: WebView
Google chrome IOS: Webkit
Rendering Engine Safari Mac Os: Webkit
Renndering Engine Safari Ios: Webkit
Mozilla:Gecko
Mozilla para android: Quantum Layout
Mozilla Firefox: Gecko
Internet: SVG
Opera: Opera Software
4-AccesibleTablix: indica el clima y utiliza metadatos para compartir datos en la pantalla.
DocMap: indica el clima y muestra el mapa.
5-La diferencia es que el XML es para describir informacion y el HTML es para mostrarla.
6-La diferencia es que HTML muestra la información y el otro mas bién tiene que ver con las transacciones y sigue el esquema peticion respuesta entre un cliente y servidor.
7-
-HTML 2.0: lanzado en noviembre de 1995, autores: Tim Berners Lee y Dan Conolly, primeros navegadores: Mozilla Firefox, Safari, cambios mas resaltantes: puntando hacia la socialización de la web, conceptualizada en el enfoque a flexibilidad en la gestión y difusión de contenidos, usabilidad.
HTML 3.0 y 3.2: autor: Dave Raggett,autores: , primeros navegadores/herramientas:W3C, cambios: los exploradores comenzaron a incluir etiquetas extras no contempladas en el estándard.
HTML 4.0: fecha: 19999 ,autores:John D. Burger, Steve Byrne ,cambiosmasres: se estandarizan los marcos, las hojas de estilo y los scripts.
HTML 5.0: lanzado en octubre de 2004, autores:Miembros de Apple con WHAT primeros navegadores/herramientas: XHTML, cambios: Fusion entre HTML Y XHTML.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment