Wikipedija

Додатак (рачунарство) – razlika između verzija

Interaktivna pretraga historije
← Starija izmjenaNovija izmjena →
Uklonjeni sadržaj Dodani sadržaj
VizualnoWikitekst
Nema sažetka izmjene
Uklanjanje svog sadržaja stranice
Red 1:
{{Prijevod}}[[File:Mozilla plugins screenshot without subpixel rendering.png|300px|thumb|''[[Mozilla Firefox]] displaying a list of installed plug-ins'']]
У [[рачунарство|рачунарству]], '''додатак''' ([http://en.wikipedia.org/wiki/Plug-in_(computing) енг.] '''plug-in''') је софтверска компонента која додаје специфично својство на већ постојећу [[Апликације|апликацију]]. Када апликација подржава додатке, онда одобрава прилагођавање према корисничким потребама. Најчешћи примери су додаци коришћени у [[претраживач веба|веб прегледачима]], да додају нова својства као што су веб претраживачи, вирус скенерс, или могућност да употребимо нови [[file type|тип датотеке]] као што је нови видео формат. Познати додаци прегледачима укључују [[Adobe Flash Player]], [[QuickTime Player]], и [[Java plug-in|Јава додатак]], који може да покрене [[Java applet|Јава аплети]] на странице које се извршавају на локалној [[Java virtual machine|Јава виртуелној машини]].
 
[[Теме]] су пакети који садрже додатне или промењене графичке детаље, које смо постигли коришћењем графичког корисничког интерфејса, које могу бити примењене на специфичан софтфер и веб странице, и тиме омогуће кориснику да промени изглед у складу са корисничким потребама и жељама.
 
==Сврха и примери==
Апликације подржавају додатке из много разлога. Неки од главних разлога укључују:
* омогућавање [[third-party developer]]s који проширују апликацију
* подржавање лаког додавања нових својства
* редуковање величина апликација
* одвајање [[изворни код|изворног кода]] од апликација због некомпатибилних [[софтверске лиценце|софтверских лиценци]]
 
Типови апликација и зашто користе додатке:
 
* [[Audio editor|Аудио едитор]] користи додатке да генерише, процесуира и/или анализира звук ([[Ardour (software)|Ardour]], [[Audacity|Audacity]])
* [[Email client|Клијенти електронске поште]] користе додатке да шифрују и дешифрују електронксу пошту([[Pretty Good Privacy]])
* [[Graphic software|Графички софтвер]] користе додатке да подрже формате дадотека и процесуира слике ([[Adobe Photoshop]], [[GIMP]])
* [[Media player (software)|Media players]] use plug-ins to support file formats and apply filters ([[foobar2000]], [[GStreamer]], [[Quintessential Media Player|Quintessential]], [[Virtual Studio Technology|VST]], [[Winamp]], [[XMMS]])
* [[Packet sniffer]]s use plug-ins to decode packet formats ([[OmniPeek]])
* [[Remote sensing application]]s use plug-ins to process data from different sensor types ([[Opticks (Software)|Opticks]])
* [[Text editors]] and [[Integrated development environment]]s use plug-ins to support [[programming languages]] ([[Eclipse (computing)|Eclipse]], [[jEdit]], [[MonoDevelop]])
* [[Web browser]]s use plug-ins (often implementing the [[NPAPI]] specification) to play video and presentation formats ([[Adobe Flash|Flash]], [[QuickTime]], [[Microsoft Silverlight]], [[3DMLW]])
<!-- Only list (in alphabetic order) items that have explicit call out of plug-in architecture in their Wikipedia article -->
 
==Mechanism==
[[File:Plug-InExample.png|thumb|right|260px|''Example Plug-In Framework'']]
 
As shown in the figure, the host application provides services which the plug-in can use, including a way for plug-ins to register themselves with the host application and a [[Protocol (computing)|protocol]] for the exchange of data with plug-ins. Plug-ins depend on the services provided by the host application and do not usually work by themselves. Conversely, the host application operates independently of the plug-ins, making it possible for end-users to add and update plug-ins dynamically without needing to make changes to the host application.<ref name="amo-def">[https://addons.mozilla.org/en-US/firefox/browse/type:7 Mozilla Firefox plugins] – Description of the difference between Mozilla Firefox plugins and extensions under the general term ''add-on''.</ref><ref name="wordpress-def">[http://codex.wordpress.org/Plugin_API Wordpress Plug-in API] – Description of the Wordpress Plug-in architecture.</ref>
 
Programmers typically implement plug-in functionality using [[Shared library|shared libraries]] installed in a place prescribed by the host application. HyperCard supported a similar facility, but more commonly included the plug-in code in the HyperCard documents (called ''stacks'') themselves. Thus the HyperCard stack became a self-contained application in its own right, distributable as a single entity that end-users could run without the need for additional installation-steps. Programs may also implement plugins by loading a directory of simple [[script (computing)|script]] files written in a [[scripting language]] like [[Python (programming language)|Python]] or [[Lua (programming language)|Lua]].
 
==Compared to extensions==
In the [[Mozilla Firefox]] [[web browser]], [[Software extension|extensions]] differ slightly from plug-ins. Firefox supports plug-ins using [[NPAPI]]. When the browser encounters references to content a plug-in specializes in, the data is handed off to be processed by that plug-in. An extension, or "addon" is a [[user interface]] enhancement that may add abilities such as a [[download manager]], toolbar buttons, or enhancements specific to a particular web site.
 
The original impetus behind the development of [[Mozilla Firefox]] was the pursuit of a small baseline application, leaving exotic or personalized functionality to be implemented by extensions to avoid [[feature creep]]. This is in contrast to the "[[wikt:everything but the kitchen sink|kitchen sink]]" approach in its predecessors, the [[Mozilla Application Suite]] and [[Netscape (browser)#Mozilla Application Suite-based releases|Netscape 6 and 7]].
 
The same distinction between plug-ins and extensions is in use by other web browsers, such as Microsoft Internet Explorer, where a typical extension might be a new [[toolbar]], and a plug-in might embed a video player on the page. Since plug-ins and extensions both increase the utility of the original application, [[Mozilla]] uses the term "add-on" as an inclusive category of augmentation modules that consists of plug-ins, extensions and themes.
 
==History==
Plug-ins appeared as early as the mid 1970s, when the [[EDT (text editor)#Univac/Fujitsu|EDT]] [[text editor]] running on the [[Unisys]] [[VS/9]] [[operating system]] using the [[UNIVAC Series 90]] [[mainframe computer]]s provided the ability to run a program from the editor and to allow such a program to access the editor buffer, thus allowing an external program to access an edit session in memory.<ref>''EDT Text Editor Reference Manual'', [[Cinnaminson, New Jersey]]: [[Unisys Corporation]], 1975</ref> The plug-in program could make calls to the editor to have it perform text-editing services upon the buffer that the editor shared with the plug-in. The [[University of Waterloo|Waterloo]] Fortran [[compiler]] used this feature to allow interactive compilation of [[Fortran]] programs edited by EDT.
 
Very early [[personal computer|PC]] software applications to incorporate plug-in functionality included [[HyperCard]] and [[QuarkXPress]] on the [[Apple Macintosh|Macintosh]], both released in 1987. In 1988, [[Silicon Beach Software]] included plug-in functionality in [[Digital Darkroom]] and [[SuperPaint]], and Ed Bomke coined the term ''plug-in''.{{fact|date=September 2014}}
 
==See also==
{{Wiktionary|plug-in}}
{{Wiktionary|add-on}}
 
* [[Applet]]
* [[Library (computing)|Shared library]]
* [[Add-ons for Firefox]]
* [[Add-on (Mozilla)]]
* [[Browser extension]]
* [[Theme (computing)]]
* [[Skin (computing)]]
 
==References==
{{reflist}}
 
{{Web browsers}}
 
{{DEFAULTSORT:Plug-In (Computing)}}
[[Category:Application programming interfaces]]
[[Category:Software add-ons]]
[[Category:Technology neologisms]]
Izvor: https://sh.wikipedia.org/wiki/Додатак_(рачунарство)