SpineJ: A software tool for quantitative analysis of nanoscale spine morphology
44
Citation
35
Reference
10
Related Paper
Citation Trend
Keywords:
Plug-in
Graphical user interface
Morphology
Interface (matter)
In chapter 9 you looked at when to use plugins and furnished some useful plugins already in existence that can come in handy when running a WordPress site. This chapter will show you what to do when you can't find a plugin that already handles the functionality you're looking for: learn how to create your own. Plugin development in WordPress is a topic that can certainly take up a whole book on its own. However, based on what you've learned about WordPress development so far, you can apply it to the subject of plugin development, enabling you to create some pretty robust plugins (as you'll see as the chapter progresses).
Plug-in
Cite
Citations (0)
Most of the time, working with plugins is straightforward. The plugin developer has written a readme file with comprehensive description of the plugin's features, good installation instructions, and a FAQ. The installation goes smoothly and what you see matches the plugin's screenshots.
Plug-in
Cite
Citations (0)
A graphical user interface for the FoldX protein design program has been developed as a plugin for the YASARA molecular graphics suite. The most prominent FoldX commands such as free energy difference upon mutagenesis and interaction energy calculations can now be run entirely via a windowed menu system and the results are immediately shown on screen.The plugin is written in Python and is freely available for download at http://foldxyasara.switchlab.org/ and supported on Linux, MacOSX and MS Windows.
Plug-in
Python
Graphical user interface
Download
Interface (matter)
Cite
Citations (316)
Plug-in
Cite
Citations (2)
This chapter covers all the steps necessary to write, test, and release your own Textpattern plugins. It starts by walking you through the steps you need to take to set up a local plugin development environment. It then moves you through several plugin examples and references time-saving helper functions within the Textpattern source code that you can use as building blocks for your own plugins.
Plug-in
Code (set theory)
Cite
Citations (0)
One can extend the features of a software system by installing a set of additional components called plugins. WordPress, as a typical example of such plugin-based software ecosystems, is used by millions of websites and has a large number (i.e., 54,777) of available plugins. These plugin-based software ecosystems are different from traditional ecosystems (e.g., NPM dependencies) in the sense that there is high coupling between a platform and its plugins compared to traditional ecosystems for which components might not necessarily depend on each other (e.g., NPM libraries do not depend on a specific version of NPM or a specific version of a client software system). The high coupling between a plugin and its platform and other plugins causes incompatibility issues that occur during the co-evolution of a plugin and its platform as well as other plugins. In fact, incompatibility issues represent a major challenge when upgrading WordPress or its plugins. According to our study of the top 500 most-released WordPress plugins, we observe that incompatibility issues represent the third major cause for bad releases, which are rapidly (within the next 24 hours) fixed via urgent releases. Thirty-two percent of these incompatibilities are between a plugin and WordPress while 19% are between peer plugins. In this article, we study how plugins co-evolve with the underlying platform as well as other plugins, in an effort to understand the practices that are related support such co-evolution and reduce incompatibility issues. In particular, we investigate how plugins support the latest available versions of WordPress, as well as how plugins are related to each other, and how they co-evolve. We observe that a plugin’s support of new versions of WordPress with a large amount of code change is risky, as the releases that declare such support have a higher chance to be followed by an urgent release compared to ordinary releases. Although plugins support the latest WordPress version, plugin developers omit important changes such as deleting the use of removed WordPress APIs, which are removed a median of 873 days after the APIs have been removed from the source code of WordPress. Plugins introduce new releases that are made according to a median of five other plugins, which we refer to as peer-triggered releases. A median of 20% of the peer-triggered releases are urgent releases that fix problems in their previous releases. The most common goal of peer-triggered releases is the fixing of incompatibility issues that a plugin detects as late as after a median of 36 days since the last release of another plugin. Our work sheds light on the co-evolution of WordPress plugins with their platform as well as peer plugins in an effort to uncover the practices of plugin evolution, so WordPress can accordingly design approaches to avoid incompatibility issues.
Plug-in
Cite
Citations (4)
Optimize the Power of the Worlds Most Popular Content Management System WordPress is the worlds most popular content management system and powers over 74 million websites. Whether you are a developer or do-it-yourselfer, expert feedback is always great when making decisions. Learn about 10 Plugins to Optimize Security and Enhance the User Experience After several years of working with multiple content management systems, I have found that WordPress is easy for non-technical people to use and also often misused. I have found security flaws with many plugins and also plugins that really did not work well for users. To help and provide guidance, I decided to write a book with ten good recommendations for plugins that help in security, search engine optimization, and other vital areas in launching a successful WordPress site. This Book Provides Information for All Skill Levels This book provides guidance on how to install plugins, make sure they are up-to-date, and my top ten list of FREE WordPress plugins.
Plug-in
Content management system
Search engine optimization
Cite
Citations (0)
Plug-in
Visibility
Cite
Citations (13)
The company Ida Infront, where the thesis was performed, was interested in how plugin configuration can be made more user-friendly in their self-produced software application iipax. The program iipax is used, among other things, to streamline workflow processes and digital archives. It is largely made up of plugins listed in a configuration file, but in some cases also in the graphical user interface. Plugin configuration is done by the user who fills in the plugin name, parameter names and parameter values into a form. There is no information available in the program about which plugins exist or what parameters they have, making it difficult to configure the plugins. Based on a specification given in the beginning of the thesis work and on meetings with employees at Ida Infront, a prototype has been developed that shows how configuring plugins in a simpler way is done. The prototype is a modified iipax application in which a framework, consisting of a database with plugins and a graphic configuration component, is included. The framework uses reflection to locate plugins, which means that only plugins that exist on the server can be added to the database. In the configuration component, the user can choose a plugin from a list and plugin parameters are filled in and validated automatically. It was also examined how annotations can be used to improve the ability to collect information about plugins. The prototype does not require the prior knowledge of the user to configure the plugins in an unmodified iipax and the risk that the user make an error has been reduced. In my opinion configuring plugins has been made more user-friendly, but no research has been done to confirm this.
Plug-in
Graphical user interface
Component (thermodynamics)
Cite
Citations (0)
WordPress includes a plugin mechanism that allows user-provided code to be executed in response to specific system events and input/output requests. The large number of extension points provided by WordPress makes it challenging for new plugin developers to understand which extension points they should use, while the thousands of existing plugins make it hard to find existing extension point handler implementations for use as examples when creating a new plugin. In this paper, we present a lightweight analysis, supplemented with information mined from source comments and the Web pages hosted by WordPress for each plugin, that guides developers to the right extension points and to existing implementations of handlers for these extension points. We also present empirical information about how plugins are used in practice, providing guidance to both tool and prospective plugin developers.
Plug-in
Implementation
Code (set theory)
Cite
Citations (9)