Global ETD Search

161	Efeito da associação da triancinolona à viscossuplementação do joelho / Effect of the addition of corticosteroid to viscosupplementation of the knee Gustavo Constantino de Campos 19 March 2014 (has links) O presente estudo destinou-se a avaliar se os resultados clínicos iniciais da viscossuplementação poderiam ser melhorados com a adição de corticosteróide. As injeções intra-articulares são usadas há muitos anos no tratamento da osteoartrite dos joelhos, principalmente com suspensões cristalinas de corticosteróides. A viscossuplementação é uma intervenção relativamente nova, atualmente recomendada no tratamento da osteoartrite. Trata-se da injeção de ácido hialurônico exógeno em articulações diartrodiais, visando, além de restaurar as propriedades reológicas do líquido sinovial, efeitos modificadores da doença osteoartrite. Revisões sistemáticas mostram que a melhora clínica ocorre em duas a cinco semanas após a viscossuplementação. Comparando-se a viscossuplementação com a injeção intraarticular com corticosteróides, dados recentes sugerem maior eficiência no alívio da dor nas quatro primeiras semanas após a infiltração com corticosteróides, similaridade dos procedimentos ao redor da quarta semana e melhores resultados com a viscossuplementação após a oitava semana. Este inicio de ação mais tardio, associado a relatos de sinovite reacional após a viscossuplementação podem desencorajar médicos e pacientes ao uso desta modalidade de tratamento. No presente estudo foram avaliados 104 pacientes em tratamento para osteoartrite do joelho no grupo de doenças osteometabólicas do Instituto de Ortopedia do Hospital das Clínicas da FMUSP. Os pacientes foram randomizados em dois grupos. Um dos grupos foi denominado VS e recebeu uma única injeção intra-articular de 6ml de Hylan GF-20 (Synvisc One®-Genzyme) no joelho estudado. O segundo grupo foi denominado VS+T e recebeu uma injeção intra-articular de 6ml de Hylan GF-20 (Synvisc One®-Genzyme) mais 1ml (20mg) de Hexacetonido de Triancinolona (Triancil®-Apsen). Foram aplicados a escala visual analógica de dor (EVA) e os questionários de WOMAC e Lequesne uma semana antes da injeção e após uma, quatro, 12 e 24 semanas. Os dois grupos com 52 pacientes cada eram homogêneos. Na primeira semana, o WOMAC e a EVA apresentaram melhores resultados no Grupo VS+T (p < 0,01) em relação ao Grupo VS. Na quarta semana não houve diferença entre os grupos. Ambos apresentaram resultados similares nas semanas 12 e 24. Concluiu-se que a adição de hexacetonido de triancinolona melhorou os resultados clínicos da viscossuplementação no curto prazo, sem interferir nos resultados a longo prazo ou na incidência de efeitos adversos / The present study aims to assess if the initial results of viscosupplementation can be improved by the addition of corticosteroid. Intraarticular injections have been used for many years to treat arthritis and other painful articular disorders, mainly using long-lasting crystalline corticosteroid suspensions. Viscosupplementation is a relatively new intervention that is now widely used and recommended for the treatment of knee osteoarthritis. It is comprised of the injection of exogenous hyaluronic acid in diarthrodial joints, in order to restore the rheological properties of synovial fluid and also to promote osteoarthritis disease-modifying effects. Several placebo-controlled studies reported that clinical improvement began only within two to five weeks after viscosupplementation. When comparing viscosupplementation versus intraarticular injection of corticosteroid, recent data suggest that from baseline to week four, intraarticular steroid were more effective for pain relief. By the fourth week, however, both provided similar relief, but beyond the eighth week, hyaluronic acid provided greater pain reduction. The mechanism of action of hyaluronic acid, with delayed onset of pain/functional improvement, combined with reports of reactional sinovitis may discourage physicians and patients regarding this treatment modality. The present study evaluated 104 patients receiving usual care for knee osteoarthritis at the University of São Paulo Medical Center. Patients were randomized to receive either a single intra-articular injection of 6ml of Hylan GF-20 (Synvisc One®-Genzyme) (Group VS) or a single intra-articular injection of 6ml of Hylan GF-20 (Synvisc One®-Genzyme) plus 1ml (20mg) of Triamcinolone Hexacetonide (Triancil®-Apsen) (Group VS+T). VAS, WOMAC and Lequesne questionnaires were applied one week prior the injection, and after one, four, 12 and 24 weeks. The two groups with 52 patients each were homogeneous. At week one, WOMAC and VAS showed better results for Group VS+T compared to Group VS (p < 0,05). At week four the scores did not show statistically significant differences. The groups showed similar results at weeks 12 and 24. In conclusion, the addition of triamcinolone improved first-week symptom and functional scores of viscosupplementation, but not beyond. It did not seem to alter the likelihood of adverse effects Ácido hialurônico Corticosteróides Ensaio clínico Ensaio clínico controlado aleatório Injeções intra-articulares Medição da dor Método duplo-cego Osteoartrite do joelho Resultado de tratamento Viscossuplementação Adrenal cortex hormones Clinical trial Double-blind method Hyaluronic acid Injections intra-articular Knee osteoarthritis Pain measurement Randomized controlled trial Treatment outcome Viscosupplementation
162	Web applications using the Google Web Toolkit / Webanwendungen unter Verwendung des Google Web Toolkits von 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. GWT Google Web Toolkit Entwicklung des World Wide Web Hypertext Markup Language Cascading Style Sheets JavaScript Asynchrones JavaScript und XML GWT Entwicklungswerkzeug und Compiler GWT im Einsatz JSNI JavaScript Native Interface Java Runtime Environment Emulation GWT Widgets Übersicht der GWT Widgets Ereignisbehandlung in GWT Widgets Remote Procedure Calls Browserverlauf verwalten Client Bundle Model-View-Presenter Architektur Vergleich von MVP und MVC e.g. Newsaktualisierung Umfrage in beiden Technologien Eine Webanwendung schreiben Ein Geschwindigkeitsspiel schreiben Tomcat herunterladen HTTPS Verbindung in Tomcat erstellen Pem Zertifikat erstellen Datenbankverbindung in Tomcat erstellen MySQL-Tabellen erstellen Anmeldemechanismus in Tomcat SafeHtml SFB799 Datenbank Webanwendung GWT Google Web Toolkit Development of the World Wide Web Hypertext Markup Language Cascading Style Sheets JavaScript Asynchronous JavaScript and XML GWT toolbox and compiler GWT in action JSNI JavaScript Native Interface GWT compiler steps and optimizations Java Runtime Environment Emulation GWT Widgets Overview of GWT Widgets Event handlers in GWT Widgets Remote Procedure Calls History Management Client Bundle Model-View-Presenter Architecture Comparison of MVP and MVC e.g. news update Doing a survey in both technologies Creating a forum to show data Writing a chat application Writing the speed game Snake Download Tomcat Establish HTTPS connections in Tomcat Create a pem certificate Create TomcatGWT user and schema and add the table countries Login mechanism in Tomcat SafeHtml SFB799 Database Web Client AJAX AST Abstract Syntax Tree CM Communicating Module CSS DOM Document Object Model HTML HTML DOM JREE JSF JavaServer Faces MVC Model-View-Controller MVP Model-View-Presenter RIA Rich Internet Application RMI Remote Method Invocation RPC Remote Procedure Call SQL UML Unified Modeling Language ECMAScript GXT ddc:004 World Wide Web Anwendungssystem Programmierung Google Web Toolkit Java Server Faces Java <Programmiersprache> JavaScript HTML Ajax <Informatik> Sicherheit Tomcat <Programm> Digitales Zertifikat MySQL
163	Web applications using the Google Web Toolkit von 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 info:eu-repo/classification/ddc/004 ddc:004

Page generated in 0.0741 seconds