The popularity of XML has motivated the development of novel XML processing tools many of which embed the XPath language for XML querying, transformation, constraint specification, etc. XPath developers (as well as less technical users) have access to commercial tools to help them use the language effectively. Example tools include debuggers that return the result of XPath subexpressions visualized in the context of the input XML document.This paper provides a glimpse of the functionality of XPlainer-Eclipse, a novel kind of query understanding and debugging tool that provides visual explanations of why XPath expressions return a specific answer. XPlainer-Eclipse combines editors for visualizing both XML documents and XPath expressions as trees together with the explanation of the answers.
{"title":"XPlainer-Eclipse: explaining XPath within Eclipse™","authors":"John W. S. Liu, M. Consens, Flavio Rizzolo","doi":"10.1145/1188835.1188852","DOIUrl":"https://doi.org/10.1145/1188835.1188852","url":null,"abstract":"The popularity of XML has motivated the development of novel XML processing tools many of which embed the XPath language for XML querying, transformation, constraint specification, etc. XPath developers (as well as less technical users) have access to commercial tools to help them use the language effectively. Example tools include debuggers that return the result of XPath subexpressions visualized in the context of the input XML document.This paper provides a glimpse of the functionality of XPlainer-Eclipse, a novel kind of query understanding and debugging tool that provides visual explanations of why XPath expressions return a specific answer. XPlainer-Eclipse combines editors for visualizing both XML documents and XPath expressions as trees together with the explanation of the answers.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131895577","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Recent research has shown that developers spend significant amounts of time navigating around code. Much of this time is spent on redundant navigations to code that the developer previously found. This is necessary today because existing development environments do not enable users to easily collect relevant information, such as web pages, textual notes, and code fragments. JASPER is a new system that allows users to collect relevant artifacts into a working set for easy reference. These artifacts are visible in a single view that represents the user's current task and allows users to easily make each artifact visible within its context. We predict that JASPER will significantly reduce time spent on redundant navigations. In addition, JASPER will facilitate multitasking, interruption management, and sharing task information with other developers.
{"title":"JASPER: an Eclipse plug-in to facilitate software maintenance tasks","authors":"Michael J. Coblenz, Amy J. Ko, B. Myers","doi":"10.1145/1188835.1188849","DOIUrl":"https://doi.org/10.1145/1188835.1188849","url":null,"abstract":"Recent research has shown that developers spend significant amounts of time navigating around code. Much of this time is spent on redundant navigations to code that the developer previously found. This is necessary today because existing development environments do not enable users to easily collect relevant information, such as web pages, textual notes, and code fragments. JASPER is a new system that allows users to collect relevant artifacts into a working set for easy reference. These artifacts are visible in a single view that represents the user's current task and allows users to easily make each artifact visible within its context. We predict that JASPER will significantly reduce time spent on redundant navigations. In addition, JASPER will facilitate multitasking, interruption management, and sharing task information with other developers.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114781771","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The support available in Eclipse to help software developers learn complex APIs and development tools is inadequate; the support is largely passive and the support typically operates alongside the resources associated with normal software development tasks, thereby overloading the environment with additional complexity. In this paper, we describe an approach that enables a dynamic learning process within the context of a developer's Eclipse work environment. Our approach integrates a mechanism for explicit support of a learning process flow (cheat sheets) with a mechanism for explicit representation of different work contexts (Mylar). We have implemented a working prototype of our approach. We found it relatively easy to integrate cheat sheets with Mylar through available extension points. We describe our architecture and report on some limitations and missing features in the existing plug-ins we discovered as we developed our prototype.
{"title":"A focused learning environment for Eclipse","authors":"Izzet Safer, G. Murphy, Julie Waterhouse, Jin Li","doi":"10.1145/1188835.1188851","DOIUrl":"https://doi.org/10.1145/1188835.1188851","url":null,"abstract":"The support available in Eclipse to help software developers learn complex APIs and development tools is inadequate; the support is largely passive and the support typically operates alongside the resources associated with normal software development tasks, thereby overloading the environment with additional complexity. In this paper, we describe an approach that enables a dynamic learning process within the context of a developer's Eclipse work environment. Our approach integrates a mechanism for explicit support of a learning process flow (cheat sheets) with a mechanism for explicit representation of different work contexts (Mylar). We have implemented a working prototype of our approach. We found it relatively easy to integrate cheat sheets with Mylar through available extension points. We describe our architecture and report on some limitations and missing features in the existing plug-ins we discovered as we developed our prototype.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114375185","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
David Aspinall, D. Winterstein, Christoph Lüth, Ahsan Fayyaz
Interactive theorem proving is the art of constructing electronic proofs. Proof development, based around a proof script, has much in common with program development, based around a program text. Proof developers use rather primitive tools for developing and manipulating proof scripts at present. The Proof General project aims at to change this, by providing powerful generic tools and interfaces. The flagship tool is our Eclipse plugin, which brings the features of a industrial-strength IDE to theorem proving for the first time. In this paper we give an overview of the Eclipse plugin and its underlying architecture.
{"title":"Proof general in Eclipse: system and architecture overview","authors":"David Aspinall, D. Winterstein, Christoph Lüth, Ahsan Fayyaz","doi":"10.1145/1188835.1188845","DOIUrl":"https://doi.org/10.1145/1188835.1188845","url":null,"abstract":"Interactive theorem proving is the art of constructing electronic proofs. Proof development, based around a proof script, has much in common with program development, based around a program text. Proof developers use rather primitive tools for developing and manipulating proof scripts at present. The Proof General project aims at to change this, by providing powerful generic tools and interfaces. The flagship tool is our Eclipse plugin, which brings the features of a industrial-strength IDE to theorem proving for the first time. In this paper we give an overview of the Eclipse plugin and its underlying architecture.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127492105","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The goal of a clone detection tool is to identify sections of code that are duplicated in a program. The result of the detection is presented in some manner for the user to view, which is usually in the form of a list of clones that are grouped together. Previous research has shown how scatter plots can be used to render a graphical representation of the results. This paper describes the integration of a stand-alone clone detection tool into Eclipse and a corresponding alternative visualization of clone detection results. An Eclipse plugin is described that displays the results of a clone detection tool called CloneDR™. The visualization of the results is implemented as an extension to the AspectJ Development Tool (AJDT) Visualiser plugin, which is primarily used to view crosscutting concerns in aspect-oriented programs.
克隆检测工具的目标是识别程序中重复的代码段。检测结果以某种方式呈现给用户查看，通常以分组在一起的克隆列表的形式呈现。先前的研究已经展示了如何使用散点图来呈现结果的图形表示。本文描述了将一个独立的克隆检测工具集成到Eclipse中，以及相应的克隆检测结果可视化。描述了一个Eclipse插件，它显示名为CloneDR™的克隆检测工具的结果。结果的可视化是作为AspectJ Development Tool (AJDT) Visualiser插件的扩展实现的，该插件主要用于在面向方面的程序中查看横切关注点。
{"title":"Visualization of clone detection results","authors":"Robert Tairas, J. Gray, I. Baxter","doi":"10.1145/1188835.1188846","DOIUrl":"https://doi.org/10.1145/1188835.1188846","url":null,"abstract":"The goal of a clone detection tool is to identify sections of code that are duplicated in a program. The result of the detection is presented in some manner for the user to view, which is usually in the form of a list of clones that are grouped together. Previous research has shown how scatter plots can be used to render a graphical representation of the results. This paper describes the integration of a stand-alone clone detection tool into Eclipse and a corresponding alternative visualization of clone detection results. An Eclipse plugin is described that displays the results of a clone detection tool called CloneDR™. The visualization of the results is implemented as an extension to the AspectJ Development Tool (AJDT) Visualiser plugin, which is primarily used to view crosscutting concerns in aspect-oriented programs.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"128 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132598187","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The effectiveness of life cycle management of an embedded device solution is crucial to its value proposition. This paper shows that Eclipse technology can be used for both tooling and runtime support of device solutions using a visual flow language. We introduce a prototype implementation based on Eclipse 3.2 and Equinox and demonstrate that it helps a user in each stage of a solution life cycle.
{"title":"Embedded device solution life cycle support with Eclipse","authors":"C. Jung, Han Chen","doi":"10.1145/1188835.1188836","DOIUrl":"https://doi.org/10.1145/1188835.1188836","url":null,"abstract":"The effectiveness of life cycle management of an embedded device solution is crucial to its value proposition. This paper shows that Eclipse technology can be used for both tooling and runtime support of device solutions using a visual flow language. We introduce a prototype implementation based on Eclipse 3.2 and Equinox and demonstrate that it helps a user in each stage of a solution life cycle.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"62 4","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120907930","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Eclipse plug-ins have access to a rich collection of GUI components. One such component is the progress bar, which allows a long-running task to provide Eclipse users with feedback about its progress. This paper considers the problem of providing precise progress bar reports for plug-ins that perform static code analysis. Since static analyses often take a long time to execute, progress indicators can inform the user whether the analysis is actually making progress, and how long it will take to complete. This type of responsiveness is essential for providing positive user experience.In this paper we consider points-to analysis, which is a popular static analysis for object-oriented software. Reporting the run-time progress of a points-to analysis requires heuristics for a priori estimates of the total running time of the analysis. We define several such heuristics for a whole-program subset-based points-to analysis for Java, implemented as part of the Soot Eclipse plug-in. We also present an experimental evaluation of the heuristics on a large set of Java programs. These results provide useful insights for the creators of points-to analyses and other static analyses that will be built and distributed in Eclipse.
{"title":"Generating run-time progress reports for a points-to analysis in Eclipse","authors":"Jason Sawin, M. Sharp, A. Rountev","doi":"10.1145/1188835.1188844","DOIUrl":"https://doi.org/10.1145/1188835.1188844","url":null,"abstract":"Eclipse plug-ins have access to a rich collection of GUI components. One such component is the progress bar, which allows a long-running task to provide Eclipse users with feedback about its progress. This paper considers the problem of providing precise progress bar reports for plug-ins that perform static code analysis. Since static analyses often take a long time to execute, progress indicators can inform the user whether the analysis is actually making progress, and how long it will take to complete. This type of responsiveness is essential for providing positive user experience.In this paper we consider points-to analysis, which is a popular static analysis for object-oriented software. Reporting the run-time progress of a points-to analysis requires heuristics for a priori estimates of the total running time of the analysis. We define several such heuristics for a whole-program subset-based points-to analysis for Java, implemented as part of the Soot Eclipse plug-in. We also present an experimental evaluation of the heuristics on a large set of Java programs. These results provide useful insights for the creators of points-to analyses and other static analyses that will be built and distributed in Eclipse.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125471118","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
I. D. Silva, Ping Chen, C. V. D. Westhuizen, R. Ripley, A. Hoek
Despite the fact that software development is an inherently collaborative activity, a great deal of software development is spent with developers in isolation, working on their own parts of the system. In these situations developers are unaware of parallel changes being made by others, often resulting in conflicts. One common approach to deal with this issue is called conflict resolution, which means that changes have already been checked-in and developers must use merge tools to resolve conflicts and then retest the code to ensure its correctness. Unfortunately, this process becomes more difficult the longer the conflicts go undetected. In order to address these issues, have been proposed conflict avoidance approaches that detect conflicts as soon as they occur. In this paper, we present Lighthouse, an Eclipse plug-in that takes the conflict avoidance approach to coordinate developers. Lighthouse distinguishes itself by utilizing a concept called emerging design, an up to date design representation of the code, to alert developers of potentially conflicting implementation changes as they occur, indicating where the changes have been made and by whom.
{"title":"Lighthouse: coordination through emerging design","authors":"I. D. Silva, Ping Chen, C. V. D. Westhuizen, R. Ripley, A. Hoek","doi":"10.1145/1188835.1188838","DOIUrl":"https://doi.org/10.1145/1188835.1188838","url":null,"abstract":"Despite the fact that software development is an inherently collaborative activity, a great deal of software development is spent with developers in isolation, working on their own parts of the system. In these situations developers are unaware of parallel changes being made by others, often resulting in conflicts. One common approach to deal with this issue is called conflict resolution, which means that changes have already been checked-in and developers must use merge tools to resolve conflicts and then retest the code to ensure its correctness. Unfortunately, this process becomes more difficult the longer the conflicts go undetected. In order to address these issues, have been proposed conflict avoidance approaches that detect conflicts as soon as they occur. In this paper, we present Lighthouse, an Eclipse plug-in that takes the conflict avoidance approach to coordinate developers. Lighthouse distinguishes itself by utilizing a concept called emerging design, an up to date design representation of the code, to alert developers of potentially conflicting implementation changes as they occur, indicating where the changes have been made and by whom.","PeriodicalId":297590,"journal":{"name":"Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-10-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126786178","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：