Spelling suggestions: "subject:"hypertext markup anguage"" "subject:"hypertext markup 1anguage""
1 |
OPERATOR INTERFACES FOR CONTROLLING THE SERIAL STREAMING TELEMETRY CHANNEL VIA A COMMAND AND CONTROL LINKLaird, Daniel T. 10 1900 (has links)
ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, Nevada / The Central Test and Evaluation Incentive Program, (CTEIP) is developing Integrated Network Enhanced Telemetry (iNET) to extend serial streaming telemetry (SST) with a command and control link. Command link interfaces link remote Advanced Range Telemetry (ARTM) transmitters (Tx) and receivers (Rx), developed under the ARTM CTEIP project, via graphical user interfaces (GUI). The communication channel links the iNET Tx on a vehicle network (vNET) and the iNET Rx on a ground station network (gNET) via a single GUI. The command link is an essential part of the pending iNET Technology Demonstration.
|
2 |
A representation of Network Elements within the Operation Support SystemsCeinos, Yannick January 2005 (has links)
<p>Currently, our world is getting more and more connected: information flows are everywhere at anytime. We are only at the beginning of the communication era. However, few want to know how those data are delivered as long as they are well delivered. Which paths they take, using optical fibres or regular copper cables, such questions do not matter for end-customers.</p><p>As a part of a telecommunication company, these questions do really matter. As networks become increasingly complex, it is significant to keep them under control and make them reliable to deliver high-quality services to users.</p><p>One of our main problems is how to get a representation of this network. More precisely how to get a relevant image of elements that compose this huge web and what points are significant in order to increase the quality of offered services. This thesis will try to answer these questions.</p>
|
3 |
A representation of Network Elements within the Operation Support SystemsCeinos, Yannick January 2005 (has links)
Currently, our world is getting more and more connected: information flows are everywhere at anytime. We are only at the beginning of the communication era. However, few want to know how those data are delivered as long as they are well delivered. Which paths they take, using optical fibres or regular copper cables, such questions do not matter for end-customers. As a part of a telecommunication company, these questions do really matter. As networks become increasingly complex, it is significant to keep them under control and make them reliable to deliver high-quality services to users. One of our main problems is how to get a representation of this network. More precisely how to get a relevant image of elements that compose this huge web and what points are significant in order to increase the quality of offered services. This thesis will try to answer these questions.
|
4 |
A Mobile Deaf-to-hearing communication aid for medical diagnosisMutemwa, Muyowa January 2011 (has links)
>Magister Scientiae - MSc / Many South African Deaf people use their mobile phones for communication with SMSs yet they would prefer to converse in South African Sign Language. Deaf people with a capital `D' are different from deaf or hard of hearing as they primarily use sign language to communicate. This study explores how to design and evaluate a prototype that will allow a Deaf person using SASL to tell a hearing doctor how s/he is feeling and provide a way for the doctor to respond. A computer{based prototype was designed and evaluated with the Deaf people in a previous study. Results from the user trial of the computer{based mock{up indicated that Deaf users would like to see the prototype on a cell phone. Those user trial results, combined with our own user survey results conducted with Deaf people, are used as requirements. We built a prototype for a mobile phone browser by embedding SASL videos inside XHTML pages using Adobe Flash. The prototype asks medical questions using SASL videos. These questions are arranged in an organized way that helps in identifying a medical problem. The answers to the questions are then displayed in English and shown to the doctor on the phone. A content authoring tool was also designed and implemented. The content authoring tool is used for populating the prototype in a context free manner allowing for plug and play scenarios such as a doctor's office, Department of Home A airs or police station. A focus group consisting of Deaf people was conducted to help in the design and pilot trial of the system. A final user trial was conducted with more than thirty Deaf people and the results are presented and analyzed. Data is collected with questionnaires, semi-structured interviews and video recordings. The results indicate that most of the Deaf people found the system easy to learn, easy to navigate through, did not get lost and understood the sign language in the videos on the mobile phone. The hand gestures and facial expressions on the sign language videos were clear. Most of them indicated they would like to use the system for free, and that the system did not ask too many questions. Most of them were happy with the quality of the sign language videos on the mobile phone and would consider using the system in real life. Finally they felt their private information was safe while using the system. Many South African Deaf people use their mobile phones for communication with SMSs yet they would prefer to converse in South African Sign Language. Deaf people with a capital `D' are different from deaf or hard of hearing as they primarily use sign language to communicate. This study explores how to design and evaluate a prototype that will allow a Deaf person using SASL to tell a hearing doctor how s/he is feeling and provide a way for the doctor to respond. A computer{based prototype was designed and evaluated with the Deaf people in a previous study. Results from the user trial of the computer{based mock{up indicated that Deaf users would like to see the prototype on a cell phone. Those user trial results, combined with our own user survey results conducted with Deaf people, are used as requirements. We built a prototype for a mobile phone browser by embedding SASL videos inside XHTML pages using Adobe Flash. The prototype asks medical questions using SASL videos. These questions are arranged in an organized way that helps in identifying a medical problem. The answers to the questions are then
displayed in English and shown to the doctor on the phone. A content authoring tool was also designed and implemented. The content authoring tool is used for populating the prototype in a context free manner allowing for plug and play scenarios such as a doctor's office, Department of Home A airs or police station. A focus group consisting of Deaf people was conducted to help in the design and pilot trial of the system. A final user trial was conducted with more than thirty Deaf people and the results are presented and analyzed. Data is collected with questionnaires, semi-structured interviews and video recordings. The results indicate that most of the Deaf people found the system easy to learn, easy to navigate through, did not get lost and understood the sign language in the videos on the mobile phone. The hand gestures and facial expressions on the sign language videos were clear. Most of them indicated they would like to use the system for free, and that the system did not ask too many questions. Most of them were happy with the quality of the sign language videos on the mobile phone and would consider using the system in real life. Finally they felt their private information was safe while using the system. / South Africa
|
5 |
Metodika výuky značkovacích jazyků / Markup languages educational methodologyMatějka, Vojtěch January 2017 (has links)
The aim of this thesis is to develop an educational methodology for the following languages: Markdown, HyperText Markup Language (HTML), eXtensible Markup Language (XML) and Scalable Vector Graphics (SVG); and to verify the methodology at Czech elementary schools on the lower secondary level. An integral part of the methodology is also an introduction to the history and development, as well as the theory of syntax of the mentioned markup languages, necessary for teaching according to this methodology. The methodology uses specific examples, on which the students can verify their newly acquired knowledge in practice. The verification of the methodology took place in the form of teaching at two Czech elementary schools. The teaching took place in the seventh grade within the compulsory elective subject of informatics, in the ninth grade within a compulsory subject. The expected differences in understanding the markup languages education in favor of the ninth year have not been confirmed. The motivation of the students proved to play much greater role than their age. The verification of the methodology has shown that it is necessary to pay careful attention to the precise formulation of the task assignments and guidelines to the students, to avoid confusion and substitution of the source code of the...
|
6 |
Informační systém revizní firmy / Information System of the Service CompanyPinkava, Radek Unknown Date (has links)
This diploma thesis covers a solution of designing the information system for HNS mechanix ltd. This company provides auditorial services of optical products. During the desining not only the requirements of functionality and attributes of the system itself but also implementation and developing tools are necessary to be followed. The system is required to be available as WWW service with multilevel user access.
|
7 |
Web applications using the Google Web Toolkit / Webanwendungen unter Verwendung des Google Web Toolkitsvon Wenckstern, Michael 04 June 2013 (has links) (PDF)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit.
The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript.
Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced.
The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit.
The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project. / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese.
Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt.
Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten.
Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert.
Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.
|
8 |
Web applications using the Google Web Toolkitvon Wenckstern, Michael 05 June 2013 (has links)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit.
The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript.
Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced.
The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit.
The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project.:I Abstract
II Contents
III Acronyms and Glossary
III.I Acronyms
III.II Glossary
IV Credits
1 Introduction
2 Basics
2.1 Development of the World Wide Web
2.2 Hypertext Markup Language
2.3 Cascading Style Sheets
2.4 JavaScript
2.5 Hypertext Markup Language Document Object Model
2.6 Asynchronous JavaScript and XML
3 GWT toolbox and compiler
3.1 GWT in action
3.2 A short overview of the toolkit
3.3 GWT compiler and JSNI
3.3.1 Overview of GWT compiler and JSNI
3.3.2 Deferred binding and bootstrapping process
3.3.3 GWT compiler steps and optimizations
3.4 Java Runtime Environment Emulation
3.5 Widgets and Panels
3.5.1 Overview of GWT Widgets
3.5.2 Event handlers in GWT Widgets
3.5.3 Manipulating browser’s DOM with GWT DOM class
3.5.4 GWT Designer and view optimization using UiBinder
3.6 Remote Procedure Calls
3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations
3.6.2 GWT’s RPC service and serializable whitelist
3.7 History Management
3.8 Client Bundle
3.8.1 Using ImageResources in the ClientBundle interface
3.8.2 Using CssResources in the ClientBundle interface
4 Model-View-Presenter Architecture
4.1 Comparison of MVP and MVC
4.2 GWT Model-View-Presenter pattern example: Agricola board game
4.3 Extending the Agricola web application with mobile views
4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history
5 Comparison of the two web frameworks: GWT and JSF
5.1 Definitions of comparison fields
5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update
5.3 Comparison in category 2: Doing a survey in both technologies
5.4 Comparison in category 3: Creating a forum to show data
5.5 Comparison in category 4: Writing a chat application
5.6 Comparison in category 5: Writing the speed game Snake
5.7 Summary
6 Security
6.1 Download Tomcat
6.2 Dynamic Web Application Project with GWT and Tomcat
6.3 Establish HTTPS connections in Tomcat
6.3.1 Create a pem certificate
6.3.2 Convert pem certificate into a key store object
6.3.3 Configure Tomcat’s XML files to enable HTPPS
6.4 Establish a database connection in Tomcat
6.4.1 Create TomcatGWT user and schema, and add the table countries
6.4.2 Configure Tomcat’s XML files to get access to the database connection
6.4.3 PreparedStatements avoid MySQL injections
6.5 Login mechanism in Tomcat
6.6 SafeHtml
7 Presenting a complex software application written in GWT
8 Conclusions
8.1 Summary
8.2 Future work
A Appendix
A 1 Configure the Google Web Toolkit framework in Eclipse
A 1.1 Install the Java Developer Kit
A 1.2 Download Eclipse
A 1.3 Install the GWT plugin in Eclipse
A 1.4 Create first GWT Java Project
A 2 Figures
A 3 Listings
A 3.1 Source code of the Agricola board game
A 3.2 Source code of GWT and JSF comparison
A 4 Tables
R Lists and References
R 1 Lists
R 1.1 List of Tables
R 1.2 List of Figures
R 1.3 List of Listings
R 2 References
R 2.1 Books
R 2.2 Online resources / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese.
Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt.
Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten.
Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert.
Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.:I Abstract
II Contents
III Acronyms and Glossary
III.I Acronyms
III.II Glossary
IV Credits
1 Introduction
2 Basics
2.1 Development of the World Wide Web
2.2 Hypertext Markup Language
2.3 Cascading Style Sheets
2.4 JavaScript
2.5 Hypertext Markup Language Document Object Model
2.6 Asynchronous JavaScript and XML
3 GWT toolbox and compiler
3.1 GWT in action
3.2 A short overview of the toolkit
3.3 GWT compiler and JSNI
3.3.1 Overview of GWT compiler and JSNI
3.3.2 Deferred binding and bootstrapping process
3.3.3 GWT compiler steps and optimizations
3.4 Java Runtime Environment Emulation
3.5 Widgets and Panels
3.5.1 Overview of GWT Widgets
3.5.2 Event handlers in GWT Widgets
3.5.3 Manipulating browser’s DOM with GWT DOM class
3.5.4 GWT Designer and view optimization using UiBinder
3.6 Remote Procedure Calls
3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations
3.6.2 GWT’s RPC service and serializable whitelist
3.7 History Management
3.8 Client Bundle
3.8.1 Using ImageResources in the ClientBundle interface
3.8.2 Using CssResources in the ClientBundle interface
4 Model-View-Presenter Architecture
4.1 Comparison of MVP and MVC
4.2 GWT Model-View-Presenter pattern example: Agricola board game
4.3 Extending the Agricola web application with mobile views
4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history
5 Comparison of the two web frameworks: GWT and JSF
5.1 Definitions of comparison fields
5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update
5.3 Comparison in category 2: Doing a survey in both technologies
5.4 Comparison in category 3: Creating a forum to show data
5.5 Comparison in category 4: Writing a chat application
5.6 Comparison in category 5: Writing the speed game Snake
5.7 Summary
6 Security
6.1 Download Tomcat
6.2 Dynamic Web Application Project with GWT and Tomcat
6.3 Establish HTTPS connections in Tomcat
6.3.1 Create a pem certificate
6.3.2 Convert pem certificate into a key store object
6.3.3 Configure Tomcat’s XML files to enable HTPPS
6.4 Establish a database connection in Tomcat
6.4.1 Create TomcatGWT user and schema, and add the table countries
6.4.2 Configure Tomcat’s XML files to get access to the database connection
6.4.3 PreparedStatements avoid MySQL injections
6.5 Login mechanism in Tomcat
6.6 SafeHtml
7 Presenting a complex software application written in GWT
8 Conclusions
8.1 Summary
8.2 Future work
A Appendix
A 1 Configure the Google Web Toolkit framework in Eclipse
A 1.1 Install the Java Developer Kit
A 1.2 Download Eclipse
A 1.3 Install the GWT plugin in Eclipse
A 1.4 Create first GWT Java Project
A 2 Figures
A 3 Listings
A 3.1 Source code of the Agricola board game
A 3.2 Source code of GWT and JSF comparison
A 4 Tables
R Lists and References
R 1 Lists
R 1.1 List of Tables
R 1.2 List of Figures
R 1.3 List of Listings
R 2 References
R 2.1 Books
R 2.2 Online resources
|
Page generated in 0.0676 seconds