{"id":32464,"date":"2019-10-31T21:47:12","date_gmt":"2019-10-31T18:47:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools\/"},"modified":"2019-10-31T21:47:12","modified_gmt":"2019-10-31T18:47:12","slug":"eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools","title":{"rendered":"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Asi <noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/\">Eclipse<\/a><\/noindex> sa u\u017e dlho nemus\u00ed \u0161peci\u00e1lne predstavova\u0165. Mnoh\u00ed poznaj\u00fa Eclipse v\u010faka n\u00e1strojom pre v\u00fdvoj v Jave Eclipse (<noindex><a rel=\"nofollow\" href=\"http:\/\/www.eclipse.org\/jdt\/\">JDT<\/a><\/noindex>). Tento popul\u00e1rny open-source Java IDE je pre v\u00e4\u010d\u0161inu developerov sp\u00e4t\u00fd so slovom \u201cEclipse\u201d. Eclipse je v\u0161ak aj roz\u0161\u00edrite\u013en\u00e1 platforma pre integr\u00e1ciu v\u00fdvojov\u00fdch n\u00e1strojov (Eclipse Platform) a cel\u00e1 rada IDE postaven\u00fdch na jej z\u00e1klade, vr\u00e1tane JDT. Eclipse je aj Eclipse Project, projekt vy\u0161\u0161ej \u00farovne, ktor\u00fd koordinuje v\u00fdvoj Eclipse Platform a JDT, a Eclipse SDK \u2013 dod\u00e1van\u00fd v\u00fdsledok tohto v\u00fdvoja. Nakoniec, Eclipse je open-source Foundation s obrovskou komunitou projektov, z ktor\u00fdch nie v\u0161etky s\u00fa nap\u00edsan\u00e9 v Jave alebo maj\u00fa s\u00favislos\u0165 s v\u00fdvojov\u00fdmi n\u00e1strojmi (napr\u00edklad projekty <noindex><a rel=\"nofollow\" href=\"https:\/\/iot.eclipse.org\/\">Eclipse IoT<\/a><\/noindex> a <noindex><a rel=\"nofollow\" href=\"https:\/\/science.eclipse.org\/\">Eclipse Science<\/a><\/noindex>). Svet Eclipse je ve\u013emi rozmanit\u00fd.<\/p>\n<p>V tomto \u010dl\u00e1nku, ktor\u00fd m\u00e1 preh\u013eadn\u00fd charakter, sa pok\u00fasime presk\u00fama\u0165 niektor\u00e9 z\u00e1klady architekt\u00fary Eclipse ako platformy na v\u00fdvoj integrovan\u00fdch n\u00e1strojov a poskytn\u00fa\u0165 \u00favod do komponentov Eclipse, ktor\u00e9 tvoria fundament technologickej platformy pre \u201enov\u00e9ho Konfigur\u00e1tora\u201c 1C: Pred podnikan\u00edm, <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/release_IDE\/\">1C:Enterprise Development Tools<\/a><\/noindex>. Samozrejme, toto presk\u00famanie bude nevyhnutne povrchn\u00e9 a dos\u0165 obmedzen\u00e9, aj preto, \u017ee sa zameriavame nielen na v\u00fdvoj\u00e1rov Eclipse ako na cie\u013eov\u00e9ho div\u00e1ka. D\u00fafame v\u0161ak, \u017ee aj sk\u00fasen\u00ed v\u00fdvoj\u00e1ri Eclipse n\u00e1jdu v \u010dl\u00e1nku zauj\u00edmav\u00e9 inform\u00e1cie. Napr\u00edklad povedzme o jednom z \u201etajomstiev Eclipse\u201c, relat\u00edvne novom a zatia\u013e m\u00e1lo zn\u00e1mom projekte <noindex><a rel=\"nofollow\" href=\"http:\/\/eclipse.org\/handly\/\">Eclipse Handly<\/a><\/noindex>, ktor\u00fd bol zalo\u017een\u00fd a podporovan\u00fd firmou 1C.<br \/>\n<img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/eb399a50bf86b6acce1df9e3d40848d4.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>\u00davod do architekt\u00fary Eclipse<\/h2>\n<p>\nNajprv sa pozrime na niektor\u00e9 spolo\u010dn\u00e9 aspekty architekt\u00fary Eclipse na pr\u00edklade <noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/jdt\/overview.php\">Eclipse Java development tools<\/a><\/noindex> (JDT). V\u00fdber pr\u00e1ve JDT ako pr\u00edkladu nie je n\u00e1hodn\u00fd. Je to prv\u00e9 integrovan\u00e9 v\u00fdvojov\u00e9 prostredie, ktor\u00e9 sa objavilo v Eclipse. Ostatn\u00e9 *DT projekty Eclipse, ako napr\u00edklad Eclipse C\/C++ Development Tooling (CDT), boli vytvoren\u00e9 nesk\u00f4r a prebrali ako z\u00e1kladn\u00e9 architektonick\u00e9 princ\u00edpy, tak aj jednotliv\u00e9 fragmenty p\u00f4vodn\u00e9ho k\u00f3du z JDT. Z\u00e1klady architekt\u00fary, ktor\u00e9 s\u00fa zakotven\u00e9 v JDT, s\u00fa aktu\u00e1lne doteraz pre prakticky ak\u00e9ko\u013evek IDE postaven\u00e9 na Eclipse Platform, vr\u00e1tane 1C:Enterprise Development Tools.<\/p>\n<p>Na prvom mieste treba poznamena\u0165, \u017ee Eclipse sa vyzna\u010duje jasn\u00fdm architektonick\u00fdm rozdelen\u00edm, s oddelen\u00edm jazykovo nez\u00e1vislej funkcionality od funkcionality ur\u010denej na podporu konkr\u00e9tnych programovac\u00edch jazykov a oddelen\u00edm UI nez\u00e1visl\u00fdch \"jadrov\u00fdch\" (core) komponentov od komponentov s\u00favisiacich so podporou pou\u017e\u00edvate\u013esk\u00e9ho rozhrania.<\/p>\n<p>Eclipse Platform preto definuje spolo\u010dn\u00fa, jazykovo nez\u00e1visl\u00fa infra\u0161trukt\u00faru, zatia\u013e \u010do n\u00e1stroje na v\u00fdvoj v Jave prid\u00e1vaj\u00fa k Eclipse plnohodnotn\u00e9 Java IDE. Ako Eclipse Platform, tak aj JDT sa skladaj\u00fa z viacer\u00fdch komponentov, z ktor\u00fdch ka\u017ed\u00e1 patr\u00ed bu\u010f k UI nez\u00e1visl\u00e9mu \"jadru\", alebo k vrstve UI (obr\u00e1zok 1).<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/230825124962e721ecca7dfb7dee9a0c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr\u00e1zok 1. Eclipse Platform a JDT<\/b><\/p>\n<p>Zoznam hlavn\u00fdch komponentov Eclipse Platform:<\/p>\n<ul>\n<li><b>Runtime<\/b> \u2014 Definuje infra\u0161trukt\u00faru pluginov. Eclipse sa vyzna\u010duje modul\u00e1rnou architekt\u00farou. V podstate je Eclipse zbierkou \"roz\u0161\u00edrovac\u00edch bodov\" a \"roz\u0161\u00edren\u00ed\".<\/li>\n<li><b>Workspace<\/b> \u2014 Spravuje jeden alebo viac projektov. Projekt sa sklad\u00e1 z prie\u010dinkov a s\u00faborov, ktor\u00e9 s\u00fa priamo zobrazen\u00e9 vo filen syst\u00e9m.<\/li>\n<li><b>Standard Widget Toolkit (SWT)<\/b> \u2014 Poskytuje z\u00e1kladn\u00e9 prvky pou\u017e\u00edvate\u013esk\u00e9ho rozhrania, integrovan\u00e9 s opera\u010dn\u00fdm syst\u00e9mom.<\/li>\n<li><b>JFace<\/b> \u2014 Poskytuje radu UI r\u00e1mcov postaven\u00fdch na vrchu SWT.<\/li>\n<li><b>Workbench<\/b> \u2014 Definuje UI paradigmu Eclipse: editory, poh\u013eady, perspekt\u00edvy.<\/li>\n<\/ul>\n<p>\nTreba poveda\u0165, \u017ee Eclipse Platform poskytuje aj mno\u017estvo \u010fal\u0161\u00edch u\u017eito\u010dn\u00fdch komponentov na vytv\u00e1ranie integrovan\u00fdch v\u00fdvojov\u00fdch n\u00e1strojov, medzi ktor\u00fdmi m\u00f4\u017eeme spomen\u00fa\u0165 Debug, Compare, Search a Team. Osobitne sa oplat\u00ed spomen\u00fa\u0165 JFace Text \u2013 z\u00e1klad pre vytv\u00e1ranie \"inteligentn\u00fdch editorov\" zdrojov\u00e9ho k\u00f3du. Bohu\u017eia\u013e, aj r\u00fdchly poh\u013ead na tieto komponenty, ako aj na komponenty UI vrstvy nie je mo\u017en\u00e9 v r\u00e1mci tohto \u010dl\u00e1nku, preto sa v zvy\u0161ku tejto \u010dasti obmedz\u00edme na preh\u013ead z\u00e1kladn\u00fdch \"jadrov\u00fdch\" komponentov Eclipse Platform a JDT.<\/p>\n<h4>Core Runtime<\/h4>\n<p>\nInfra\u0161trukt\u00fara pluginov Eclipse je zalo\u017een\u00e1 na <noindex><a rel=\"nofollow\" href=\"https:\/\/www.osgi.org\/developer\/specifications\/\">OSGi<\/a><\/noindex> a poskytuje projekt <noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/equinox\/\">Eclipse Equinox<\/a><\/noindex>. Ka\u017ed\u00fd plugin Eclipse je OSGi bundle. \u0160pecifik\u00e1cia OSGi ur\u010duje, okrem in\u00e9ho, mechanizmy verziovania a rie\u0161enia z\u00e1vislost\u00ed. Okrem t\u00fdchto \u0161tandardn\u00fdch mechanizmov, Equinox zav\u00e1dza pojem <i>roz\u0161\u00edrovac\u00ed bod<\/i>. Ka\u017ed\u00fd plugin m\u00f4\u017ee definova\u0165 svoje body roz\u0161\u00edrenia a taktie\u017e prid\u00e1va\u0165 do syst\u00e9mu dodato\u010dn\u00fa funk\u010dnos\u0165 (\u201eroz\u0161\u00edrenia\u201c) pomocou bodov roz\u0161\u00edrenia, ktor\u00e9 s\u00fa definovan\u00e9 t\u00fdmto alebo in\u00fdmi pluginmi. Podrobnej\u0161\u00ed popis mechanizmov OSGi a Equinox presahuje r\u00e1mec tohto \u010dl\u00e1nku. Zaznamenajme len, \u017ee modulariz\u00e1cia v Eclipse je tot\u00e1lna (ak\u00e1ko\u013evek podsyst\u00e9m, vr\u00e1tane Runtime, sa sklad\u00e1 z jedn\u00e9ho alebo viacer\u00fdch pluginov) a takmer v\u0161etko v Eclipse je roz\u0161\u00edren\u00edm. Tieto princ\u00edpy boli zako\u0159en\u011bn\u00e9 u\u017e v architekt\u00fare Eclipse d\u00e1vno pred zaveden\u00edm OSGi (v tom \u010dase sa pou\u017e\u00edvala vlastn\u00e1 technol\u00f3gia, ktor\u00e1 bola do zna\u010dnej miery anal\u00f3gia OSGi).<\/p>\n<h4>Hlavn\u00fd pracovn\u00fd priestor<\/h4>\n<p>\nTakmer ka\u017ed\u00e9 integrovan\u00e9 v\u00fdvojov\u00e9 prostredie postaven\u00e9 na z\u00e1klade Eclipse Platform pracuje s Eclipse workspace. Pr\u00e1ve workspace zvy\u010dajne obsahuje zdrojov\u00fd k\u00f3d vyv\u00edjan\u00e9ho v IDE aplik\u00e1cie. Workspace priamo zobrazuje na s\u00faborov\u00fa syst\u00e9m a pozost\u00e1va z projektov, ktor\u00e9 obsahuj\u00fa prie\u010dinky a s\u00fabory. Tieto projekty, prie\u010dinky a s\u00fabory sa naz\u00fdvaj\u00fa <i>zdroje<\/i> . Implement\u00e1cia workspace v Eclipse sl\u00fa\u017ei akoby cache vo\u010di s\u00faborov\u00e9mu syst\u00e9mu, \u010do v\u00fdrazne ur\u00fdch\u013euje prech\u00e1dzanie stromom zdrojov. Okrem toho, workspace poskytuje nieko\u013eko dodato\u010dn\u00fdch slu\u017eieb, vr\u00e1tane <noindex><a rel=\"nofollow\" href=\"https:\/\/eclipse.org\/articles\/Article-Resource-deltas\/resource-deltas.html\">mechanizmu notifik\u00e1cie o zmene zdrojov<\/a><\/noindex> a <noindex><a rel=\"nofollow\" href=\"https:\/\/eclipse.org\/articles\/Article-Builders\/builders.html\">infrastrukt\u00fary inkrement\u00e1lnych builderov<\/a><\/noindex>.<\/p>\n<p>Za podporu workspace a jeho zdrojov zodpoved\u00e1 komponenta Core Resources (plugin org.eclipse.core.resources). T\u00e1to komponenta poskytuje programov\u00fd pr\u00edstup k workspace vo forme <i>modelu zdrojov<\/i>. Pre efekt\u00edvnu pr\u00e1cu s t\u00fdmto modelom potrebuj\u00fa klienti jednoduch\u00fd sp\u00f4sob prezentovania odkazu na zdroj. Pri tom by bolo \u017eiad\u00face skry\u0165 objekt, ktor\u00fd priamo uchov\u00e1va stav zdroja v modeli, pred pr\u00edstupom klienta. Inak, v pr\u00edpade, napr\u00edklad, odstr\u00e1nenia s\u00faboru, by klient mohol na\u010falej uchov\u00e1va\u0165 objekt, ktor\u00fd u\u017e v modeli nie je, s vypl\u00fdvaj\u00facimi probl\u00e9mami. Eclipse rie\u0161i tento probl\u00e9m pou\u017eit\u00edm takzvan\u00e9ho <i>handle<\/i> zdroja. Handle vystupuje v \u00falohe k\u013e\u00fa\u010da (pozn\u00e1 iba cestu k zdroju v workspace) a plne kontroluje pr\u00edstup k vn\u00fatorn\u00e9mu objektu modelu, ktor\u00fd priamo uchov\u00e1va inform\u00e1cie o stave zdroja. Tento dizajn je vari\u00e1ciou vzoru <noindex><a rel=\"nofollow\" href=\"http:\/\/wiki.c2.com\/?HandleBodyPattern\">Handle\/Body<\/a><\/noindex>.<\/p>\n<p>Obr\u00e1zok 2 ilustruje idiom Handle\/Body v s\u00favislosti s modelom zdrojov. Rozhranie IResource predstavuje handle zdroja a je API, na rozdiel od triedy Resource, ktor\u00e1 toto rozhranie implementuje, a triedy ResourceInfo, ktor\u00e1 predstavuje body a nie je API. Zd\u00f4raz\u0148ujeme, \u017ee handle pozn\u00e1 iba cestu k zdroju vzh\u013eadom na kore\u0148 workspace a neobsahuje odkaz na resource info. Objekty resource info tvoria takzvan\u00e9 \u201estrom prvkov\u201c (element tree). T\u00e1to d\u00e1tov\u00e1 \u0161trukt\u00fara je \u00faplne materializovan\u00e1 v pam\u00e4ti. Na n\u00e1jdenie in\u0161tancie resource info zodpovedaj\u00facej ur\u010dit\u00e9mu handle sa element tree prech\u00e1dza pod\u013ea cesty, ktor\u00e1 je ulo\u017een\u00e1 v tomto handle.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/9d17cd95be3730ab6b5b9e6e3ed71ace.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr\u00e1zok 2. IResource a ResourceInfo<\/b><\/p>\n<p>Ako uvid\u00edme nesk\u00f4r, z\u00e1kladn\u00fd dizajn modelu zdrojov (nazvan\u00fd handle-based) sa pou\u017e\u00edva v Eclipse a aj pre in\u00e9 modely. A zatia\u013e vymenujeme niektor\u00e9 charakteristick\u00e9 vlastnosti tohto dizajnu:<\/p>\n<ul>\n<li>Handle je objektom-hodnotou (value object). Objekty-hodnoty s\u00fa nemenn\u00e9 (immutable) objekty, ktor\u00fdch rovnos\u0165 nie je zalo\u017een\u00e1 na identite. Tieto objekty m\u00f4\u017eu by\u0165 bezpe\u010dne pou\u017e\u00edvan\u00e9 ako k\u013e\u00fa\u010de v hashovan\u00fdch kontajneroch. Nieko\u013eko in\u0161tanci\u00ed handle m\u00f4\u017ee odkazova\u0165 na ten ist\u00fd zdroj. Na ich porovnanie by sa mal pou\u017ei\u0165 met\u00f3da equals(Object).<\/li>\n<li>Handle ur\u010duje spr\u00e1vanie zdroja, ale neobsahuje inform\u00e1cie o stave zdroja (jedin\u00e9 \u00fadaje, ktor\u00e9 uchov\u00e1va, s\u00fa \u201ek\u013e\u00fa\u010d\u201c, cesta k zdroju).<\/li>\n<li>Handle m\u00f4\u017ee odkazova\u0165 na neexistuj\u00faci zdroj (bu\u010f zdroj, ktor\u00fd e\u0161te nebol vytvoren\u00fd, alebo zdroj, ktor\u00fd u\u017e bol odstr\u00e1nen\u00fd). Existenciu zdroja je mo\u017en\u00e9 overi\u0165 pomocou met\u00f3dy IResource.exists().<\/li>\n<li>Niektor\u00e9 oper\u00e1cie m\u00f4\u017eu by\u0165 vykonan\u00e9 \u010disto na z\u00e1klade inform\u00e1ci\u00ed uchov\u00e1van\u00fdch v samotnom handle (takzvan\u00e9 handle-only oper\u00e1cie). Pr\u00edkladmi s\u00fa IResource.getParent(), getFullPath a podobne. Zdroje nemusia nevyhnutne existova\u0165 na \u00faspe\u0161n\u00e9 vykonanie takejto oper\u00e1cie. Oper\u00e1cie, na \u00faspe\u0161n\u00e9 vykonanie ktor\u00fdch je potrebn\u00e9, aby zdroj existoval, vyvol\u00e1vaj\u00fa v\u00fdnimku (CoreException), ak zdroj neexistuje.<\/li>\n<\/ul>\n<p>\nEclipse poskytuje efekt\u00edvny mechanizmus notifik\u00e1cie zmien zdrojov workspace (obr. 3). Zdroje sa m\u00f4\u017eu meni\u0165 ako v d\u00f4sledku akci\u00ed vykon\u00e1van\u00fdch priamo v Eclipse IDE, tak aj v d\u00f4sledku synchroniz\u00e1cie so s\u00faborov\u00fdm syst\u00e9mom. V oboch pr\u00edpadoch s\u00fa klientom, ktor\u00ed sa prihl\u00e1sili na notifik\u00e1cie, poskytnut\u00e9 podrobn\u00e9 inform\u00e1cie o zmene vo forme \"zdrojov\u00fdch delta\" (resource delta). Delta popisuje zmeny medzi dvoma stavmi (pod-)stromu zdrojov workspace a sama je stromom, pri\u010dom ka\u017ed\u00fd uzol popisuje zmenu ur\u010dit\u00e9ho zdroja a obsahuje zoznam delt nasleduj\u00facej \u00farovne, ktor\u00e9 popisuj\u00fa zmeny podriaden\u00fdch zdrojov.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/8af412412ee97d205137ab70c8444a50.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 3. IResourceChangeEvent a IResourceDelta<\/b><\/p>\n<p>Mechanizmus notifik\u00e1cie zalo\u017een\u00fd na zdrojov\u00fdch delta m\u00e1 nasleduj\u00face charakteristiky:<\/p>\n<ul>\n<li>Jedno zmenenie a viacero zmien s\u00fa popisovan\u00e9 pomocou rovnakej \u0161trukt\u00fary, preto\u017ee delta je kon\u0161truovan\u00e1 na princ\u00edpe rekurz\u00edvnej kompoz\u00edcie. Klienti-podpisova\u010di m\u00f4\u017eu spracov\u00e1va\u0165 notifik\u00e1cie o zmene zdrojov pomocou rekurz\u00edvneho zostupu po strome delt.<\/li>\n<li>Delta obsahuje \u00fapln\u00e9 inform\u00e1cie o zmene zdroja, vr\u00e1tane jeho presunutia a\/alebo zmien s\u00favisiacich s n\u00edm \"markerov\" (napr\u00edklad chyby kompil\u00e1cie s\u00fa predstavovan\u00e9 ako markery).<\/li>\n<li>Ke\u010f\u017ee odkazy na zdroj sa robia cez handle, delta m\u00f4\u017ee prirodzene odkazova\u0165 na vzdialen\u00fd zdroj.<\/li>\n<\/ul>\n<p>\nAko \u010doskoro uvid\u00edme, z\u00e1kladn\u00e9 zlo\u017eky dizajnu mechanizmu notifik\u00e1cie o zmene modelu zdrojov s\u00fa aktu\u00e1lne aj pre in\u00e9 modely zalo\u017een\u00e9 na handle.<\/p>\n<h4>JDT Core<\/h4>\n<p>\nModel zdrojov Eclipse workspace je fundament\u00e1lny jazykovo-nez\u00e1visl\u00fd model. Komponent JDT Core (plugin org.eclipse.jdt.core) poskytuje API na navig\u00e1ciu a anal\u00fdzu \u0161trukt\u00fary workspace z poh\u013eadu Javy, tzv. \"Java model\" (<i>Java model<\/i>). Toto API je definovan\u00e9 v term\u00ednoch Java prvkov, na rozdiel od spodn\u00e9ho API modelu zdrojov, ktor\u00e9 je definovan\u00e9 v term\u00ednoch prie\u010dinkov a s\u00faborov. Hlavn\u00e9 rozhrania stromu prvkov Java s\u00fa zn\u00e1zornen\u00e9 na obr. 4.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/67bfd31e93eaa66aa94b30281693a318.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 4. Prvky modelu Java<\/b><\/p>\n<p>Model Java pou\u017e\u00edva rovnak\u00fa idiom handle\/body ako model zdrojov (obr. 5). IJavaElement je handle a JavaElementInfo hr\u00e1 \u00falohu body. Rozhranie IJavaElement definuje protokol, ktor\u00fd je spolo\u010dn\u00fd pre v\u0161etky prvky Java. Niektor\u00e9 z jeho met\u00f3d s\u00fa len handle: getElementName(), getParent(), at\u010f. Objekt JavaElementInfo uchov\u00e1va stav zodpovedaj\u00faceho prvku: jeho \u0161trukt\u00faru a atrib\u00faty.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/5b473cccfc8f258d563033ce334cb94f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 5. IJavaElement a JavaElementInfo<\/b><\/p>\n<p>Model Java m\u00e1 niektor\u00e9 odli\u0161nosti vo vykon\u00e1van\u00ed z\u00e1kladn\u00e9ho dizajnu handle\/body v porovnan\u00ed s modelom zdrojov. Ako bolo uveden\u00e9 vy\u0161\u0161ie, v modely zdrojov element tree, ktor\u00e9ho uzly tvoria objekty resource info, je \u00faplne uchovan\u00e9 v pam\u00e4ti. Ale v modeli Java m\u00f4\u017ee by\u0165 v\u00fdrazne viac prvkov, ne\u017e v strome zdrojov, preto\u017ee obsahuje aj vn\u00fatorn\u00fa \u0161trukt\u00faru .java a .class s\u00faborov: typy, polia a met\u00f3dy.<\/p>\n<p>Aby sa predi\u0161lo \u00faplnej materializ\u00e1cii cel\u00e9ho stromu prvkov v pam\u00e4ti, realiz\u00e1cia modelu Java pou\u017e\u00edva obmedzen\u00fd LRU-cache element info, kde k\u013e\u00fa\u010dom je handle IJavaElement. Objekty element info sa vytv\u00e1raj\u00fa na po\u017eiadanie, ke\u010f sa vykon\u00e1va navig\u00e1cia stromom prvkov. Pri tom sa najmenej \u010dasto pou\u017e\u00edvan\u00e9 prvky vyra\u010fuj\u00fa z cache a spotreba pam\u00e4te modelom zost\u00e1va obmedzen\u00e1 stanovenou ve\u013ekos\u0165ou cache. To je \u010fal\u0161ia v\u00fdhoda dizajnu zalo\u017een\u00e9ho na handle, ktor\u00fd \u00faplne skr\u00fdva tak\u00e9to detailne implement\u00e1cie pred klientsk\u00fdm k\u00f3dom.<\/p>\n<p>Mechanizmus notifik\u00e1cie o zmene prvkov Java je v z\u00e1sade podobn\u00fd vy\u0161\u0161ie uveden\u00e9mu mechanizmu sledovania zmien zdrojov workspace. Klient, ktor\u00fd chce sledova\u0165 zmeny v modeli Java, sa prihlasuje na notifik\u00e1cie, ktor\u00e9 s\u00fa prezentovan\u00e9 vo forme objektu ElementChangedEvent, ktor\u00fd obsahuje IJavaElementDelta (obr. 6).<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/0402ec362078eaf50f47756e7f24de01.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 6. ElementChangedEvent a IJavaElementDelta<\/b><\/p>\n<p>Model Java neobsahuje inform\u00e1cie o tele met\u00f3d alebo o rozl\u00ed\u0161en\u00ed mien, a preto na podrobn\u00e9 anal\u00fdzy k\u00f3du p\u00edsan\u00e9ho v Jave, JDT Core poskytuje dodato\u010dn\u00fd model (ne-zalo\u017een\u00fd na handle): <noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/articles\/Article-JavaCodeManipulation_AST\/index.html\">abstraktn\u00fd syntaktick\u00fd strom<\/a><\/noindex> (abstraktn\u00fd syntaktick\u00fd strom, AST). AST predstavuje v\u00fdsledok syntaktickej anal\u00fdzy zdrojov\u00e9ho textu. Uzly AST zodpovedaj\u00fa prvkom \u0161trukt\u00fary zdrojov\u00e9ho modulu (vyhl\u00e1senia, oper\u00e1tory, v\u00fdrazy at\u010f.) a obsahuj\u00fa inform\u00e1cie o s\u00faradniciach zodpovedaj\u00faceho prvku v zdrojovom texte, ako aj (volite\u013ene) inform\u00e1cie o rozl\u00ed\u0161en\u00ed mien vo forme odkazov na takzvan\u00e9 <i>viazania<\/i>Bindings s\u00fa objekty, ktor\u00e9 predstavuj\u00fa pomenovan\u00e9 entity, ako s\u00fa typy, met\u00f3dy a premenn\u00e9 zn\u00e1me kompil\u00e1toru. Na rozdiel od uzlov AST, ktor\u00e9 tvoria strom, bindings podporuj\u00fa kr\u00ed\u017eov\u00e9 odkazy a vo v\u0161eobecnosti tvoria graf. Abstraktn\u00e1 trieda ASTNode je spolo\u010dn\u00e1 z\u00e1kladn\u00e1 trieda pre v\u0161etky uzly AST. Podtriedy ASTNode zodpovedaj\u00fa ur\u010dit\u00fdm syntaktick\u00fdm kon\u0161trukci\u00e1m jazyka Java.<\/p>\n<p>Ke\u010f\u017ee syntaktick\u00e9 stromy m\u00f4\u017eu spotrebova\u0165 v\u00fdznamn\u00e9 mno\u017estvo pam\u00e4te, JDT cacheuje iba jedno AST pre akt\u00edvny editor. Na rozdiel od modelu Java sa AST zvy\u010dajne pova\u017euje za \"medzilehlov\u00fa\" alebo \"do\u010dasn\u00fa\" s\u00faradnicov\u00fa model, na ktor\u00fa by si klienti nemali udr\u017eiava\u0165 odkazy mimo kontextu oper\u00e1cie, ktor\u00e1 vedie k vytvoreniu AST.<\/p>\n<p>Tento model (Java model, AST, bindings) spolo\u010dne tvoria z\u00e1klad pre v\u00fdvoj \"inteligentn\u00fdch v\u00fdvojov\u00fdch n\u00e1strojov\" v JDT, medzi ktor\u00e9 patr\u00ed mocn\u00fd Java editor s r\u00f4znymi \"asistentmi\", r\u00f4zne akcie na spracovanie zdrojov\u00e9ho k\u00f3du (vr\u00e1tane organiz\u00e1cie zoznamu importovan\u00fdch mien a form\u00e1tovania v s\u00falade s nastaven\u00fdm \u0161t\u00fdlom), n\u00e1stroje na vyh\u013ead\u00e1vanie a refaktoring. Pri tom m\u00e1 model Java osobitn\u00fa \u00falohu, preto\u017ee pr\u00e1ve on sl\u00fa\u017ei ako z\u00e1klad pre vizu\u00e1lne zobrazenie \u0161trukt\u00fary vyv\u00edjan\u00e9ho aplik\u00e1cie (napr\u00edklad v Package Explorer, Outline, Search, Call Hierarchy a Type Hierarchy).<\/p>\n<h2>Komponenty Eclipse, pou\u017e\u00edvan\u00e9 v 1C:Enterprise Developments Tools<\/h2>\n<p>\nNa obr. 7 s\u00fa zobrazen\u00e9 komponenty Eclipse, ktor\u00e9 tvoria z\u00e1klad technol\u00f3gie platformy pre 1C:Enterprise Development Tools.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/248cceea47ee507b9ad22d6964738ee7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 7. Eclipse ako platforma pre 1C:Enterprise Development Tools<\/b><\/p>\n<p><b>Eclipse Platform<\/b> poskytuje z\u00e1kladn\u00fa infra\u0161trukt\u00faru. Niektor\u00e9 aspekty tejto infra\u0161trukt\u00fary sme presk\u00famali v predch\u00e1dzaj\u00facej sekcii.<\/p>\n<p><b><noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/modeling\/emf\/\">Eclipse Modeling Framework<\/a><\/noindex><\/b> (<b>EMF<\/b>) poskytuje v\u0161eobecn\u00e9 prostriedky na modelovanie \u0161trukt\u00farovan\u00fdch d\u00e1t. EMF je integrovan\u00fd s Eclipse Platform, ale m\u00f4\u017ee sa pou\u017e\u00edva\u0165 aj samostatne, v be\u017en\u00fdch aplik\u00e1ci\u00e1ch Java. Pomerne \u010dasto s\u00fa za\u010d\u00ednaj\u00faci v\u00fdvoj\u00e1ri Eclipse u\u017e dobre obozn\u00e1men\u00ed s EMF, aj ke\u010f e\u0161te \u00faplne nerozumej\u00fa nuans\u00e1m Eclipse Platform. Jedn\u00fdm z d\u00f4vodov jeho zasl\u00fa\u017eenej popularity je univerz\u00e1lny dizajn, ktor\u00fd zah\u0155\u0148a aj unifikovan\u00e9 API meta\u00farovne, ktor\u00e9 umo\u017e\u0148uje zov\u0161eobecnen\u00e9 pr\u00e1ce s ak\u00fdmko\u013evek modelom EMF. Poskytovan\u00e9 z\u00e1kladn\u00e9 implement\u00e1cie EMF pre objekty modelu a subsyst\u00e9m generovania k\u00f3du modelu na z\u00e1klade meta-modelu z\u00e1sadne zvy\u0161uj\u00fa r\u00fdchlos\u0165 v\u00fdvoja a zni\u017euj\u00fa po\u010det ch\u00fdb. EMF tie\u017e obsahuje mechanizmy na serializ\u00e1ciu modelov, sledovanie zmien v modeli a mnoho \u010fal\u0161ieho. <\/p>\n<p>Ako ka\u017ed\u00fd skuto\u010dne univerz\u00e1lny n\u00e1stroj, EMF je vhodn\u00fd na rie\u0161enie \u0161irok\u00e9ho spektra \u00faloh spojen\u00fdch s modelovan\u00edm, ale niektor\u00e9 triedy modelov (napr\u00edklad vy\u0161\u0161ie uveden\u00e9 modely na z\u00e1klade handle) m\u00f4\u017eu potrebova\u0165 \u0161pecializovanej\u0161ie n\u00e1stroje na modelovanie. Rozpr\u00e1va\u0165 o EMF je nevd\u011b\u010dn\u00e1 \u00faloha, najm\u00e4 v obmedzen\u00fdch r\u00e1mcoch jedn\u00e9ho \u010dl\u00e1nku, preto\u017ee je to t\u00e9ma samostatnej knihy a dos\u0165 hrubej. Upozornime len na to, \u017ee kvalitn\u00fd syst\u00e9m generaliz\u00e1ci\u00ed, ktor\u00fd je z\u00e1kladom EMF, umo\u017enil vznik cel\u00e9ho spektra projektov zameran\u00fdch na modelovanie, ktor\u00e9 patria do vrchn\u00e9ho projektu. <noindex><a rel=\"nofollow\" href=\"https:\/\/eclipse.org\/modeling\/\">Eclipse Modeling<\/a><\/noindex> spolu s EMF. Jedn\u00fdm z tak\u00fdchto projektov je Eclipse Xtext.<\/p>\n<p><b><noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/Xtext\/\">Eclipse Xtext<\/a><\/noindex><\/b> poskytuje infra\u0161trukt\u00faru pre \u201etextov\u00e9 modelovanie\u201c. Xtext pou\u017e\u00edva <noindex><a rel=\"nofollow\" href=\"http:\/\/www.antlr.org\/\">ANTLR<\/a><\/noindex> na syntaktick\u00fa anal\u00fdzu zdrojov\u00e9ho textu a EMF pre prezent\u00e1ciu v\u00fdsledn\u00e9ho ASG (abstraktn\u00fd s\u00e9mantick\u00fd graf, ktor\u00fd je v podstate kombin\u00e1ciou AST a v\u00e4zieb), ktor\u00fd sa tie\u017e naz\u00fdva \u201es\u00e9mantick\u00fd model\u201c. Gramatika modelovan\u00e9ho jazyka pomocou Xtext je pop\u00edsan\u00e1 vo vlastnom jazyku Xtext. To umo\u017e\u0148uje nielen generova\u0165 popis gramatiky pre ANTLR, ale aj z\u00edska\u0165 mechanizmus serializ\u00e1cie AST (tj. Xtext poskytuje aj parser, aj unparser), kontextov\u00e9 n\u00e1povedy a mno\u017estvo \u010fal\u0161\u00edch jazykov\u00fdch komponentov. Na druhej strane, jazyk popisu gramatiky, ktor\u00fd sa pou\u017e\u00edva v Xtext, je menej flexibiln\u00fd v porovnan\u00ed, povedzme, s jazykom popisu gramatiky v ANTLR. Preto sa niekedy mus\u00ed \u201eprisp\u00f4sobova\u0165\u201c jazyk, ktor\u00fd je implementovan\u00fd pod Xtext, \u010do obvykle nie je probl\u00e9m, ak ide o jazyk vyv\u00edjan\u00fd od za\u010diatku, ale m\u00f4\u017ee by\u0165 neprijate\u013en\u00e9 pre jazyky s u\u017e existuj\u00facou syntaxou. Napriek tomu je Xtext v s\u00fa\u010dasnosti najzrel\u0161\u00edm, funk\u010dne kompletn\u00fdm a univerz\u00e1lnym n\u00e1strojom v Eclipse na budovanie programovac\u00edch jazykov a v\u00fdvojov\u00fdch n\u00e1strojov pre ne. Osobitne je to ide\u00e1lny n\u00e1stroj na r\u00fdchle prototypovanie <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%9F%D1%80%D0%B5%D0%B4%D0%BC%D0%B5%D1%82%D0%BD%D0%BE-%D0%BE%D1%80%D0%B8%D0%B5%D0%BD%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%BD%D1%8B%D0%B9_%D1%8F%D0%B7%D1%8B%D0%BA\">predmetovo orientovan\u00fdch jazykov<\/a><\/noindex> (domain-specific language, DSL). Okrem vy\u0161\u0161ie uveden\u00e9ho \u201ejazykov\u00e9ho jadra\u201c zalo\u017een\u00e9ho na ANTLR a EMF, Xtext poskytuje mno\u017estvo u\u017eito\u010dn\u00fdch komponentov vy\u0161\u0161ej \u00farovne, vr\u00e1tane mechanizmov indexovania, inkrement\u00e1lnej stavby, \u201einteligentn\u00e9ho editora\u201c a mnoho, mnoho \u010fal\u0161\u00edch, ale ponech\u00e1va bokom jazykov\u00e9 modely zalo\u017een\u00e9 na handle. Podobne ako EMF aj Xtext je predmetom hodn\u00fdm samostatnej knihy a \u0165a\u017eko m\u00f4\u017eeme aj len letmo rozpr\u00e1va\u0165 o v\u0161etk\u00fdch jeho mo\u017enostiach.<\/p>\n<p>1C:Enterprise Development Tools akt\u00edvne vyu\u017e\u00edvaj\u00fa ako EMF samostatne, tak aj rad \u010fal\u0161\u00edch projektov Eclipse Modeling. Osobitne je Xtext jedn\u00fdm z hlavn\u00fdch n\u00e1strojov pre v\u00fdvoj tak\u00fdch jazykov 1C:Pred podnikanie, ako je zabudovan\u00fd programovac\u00ed jazyk a jazyk dotazov. Druhou z\u00e1klad\u0148ou t\u00fdchto v\u00fdvojov\u00fdch n\u00e1strojov je projekt Eclipse Handly, na ktor\u00fd sa podrobnej\u0161ie zameriame (z uveden\u00fdch komponentov Eclipse je zatia\u013e najmenej zn\u00e1my).<\/p>\n<p><b><noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/handly\/\">Eclipse Handly<\/a><\/noindex><\/b>, podprojekt projektu vy\u0161\u0161ej \u00farovne Eclipse Technology vznikol z p\u00f4vodnej pr\u00edspevku k\u00f3du do Eclipse Foundation, ktor\u00fd uskuto\u010dnila firma 1C v roku 2014. Odvtedy firma 1C na\u010falej podporuje v\u00fdvoj projektu: commit\u00e9ri Handly s\u00fa zamestnancami firmy. Projekt je mal\u00fd, ale zauj\u00edma dos\u0165 unik\u00e1tnu poz\u00edciu v Eclipse: jeho hlavn\u00fdm cie\u013eom je podpora v\u00fdvoja modelov zalo\u017een\u00fdch na handle.<\/p>\n<p>Hlavn\u00e9 architektonick\u00e9 princ\u00edpy modelov zalo\u017een\u00fdch na handle, ako je idiom handle\/body, boli posudzovan\u00e9 vy\u0161\u0161ie na pr\u00edklade modelu zdrojov a Java modelu. Tam sa tie\u017e spomenulo, \u017ee model zdrojov aj Java model s\u00fa d\u00f4le\u017eit\u00fdmi z\u00e1kladmi pre Eclipse Java development tools (JDT). A ke\u010f\u017ee takmer v\u0161etky *DT projekty Eclipse maj\u00fa architekt\u00faru podobn\u00fa JDT, nebude ve\u013ek\u00fdm preh\u00e1\u0148an\u00edm poveda\u0165, \u017ee modely zalo\u017een\u00e9 na handle s\u00fa v z\u00e1klade mnoh\u00fdch, ak nie v\u0161etk\u00fdch IDE, postaven\u00fdch na Eclipse Platform. Napr\u00edklad v Eclipse C\/C++ Development Tooling (CDT) existuje model zalo\u017een\u00fd na handle pre C\/C++, ktor\u00fd zohr\u00e1va v architekt\u00fare CDT t\u00fa ist\u00fa \u00falohu, ak\u00fa zohr\u00e1va Java model v JDT.<\/p>\n<p>Pred pr\u00edchodom Handly, Eclipse nenab\u00edzal \u0161pecializovan\u00e9 kni\u017enice na budovanie jazykov\u00fdch modelov zalo\u017een\u00fdch na handle. Existuj\u00face modely sa vytv\u00e1rali preva\u017ene pomocou priamej adapt\u00e1cie k\u00f3du Java modelu (tj. copy\/paste), <i>v pr\u00edpadoch, ke\u010f to umo\u017e\u0148uje<\/i> Eclipse Public License (EPL). (Je jasn\u00e9, \u017ee pre projekty samotn\u00e9ho Eclipse to z pr\u00e1vneho h\u013eadiska zvy\u010dajne nie je probl\u00e9m, \u010do sa ned\u00e1 poveda\u0165 o produktoch s uzavret\u00fdm zdrojov\u00fdm k\u00f3dom.) Okrem typickej bezsystematickosti t\u00e1to metodika vedie k dobre zn\u00e1mym probl\u00e9mom: duplik\u00e1cii k\u00f3du, chyb\u00e1m v r\u00e1mci prisp\u00f4sobenia at\u010f. E\u0161te hor\u0161ie je, \u017ee v\u00fdsledn\u00e9 modely zost\u00e1vaj\u00fa \u201evecou v sebe\u201c a nevyu\u017e\u00edvaj\u00fa existuj\u00faci potenci\u00e1l na unifik\u00e1ciu. A predsa vy\u010dlenenie spolo\u010dn\u00fdch pojmov a protokolov pre jazykov\u00e9 modely zalo\u017een\u00e9 na handle by mohlo vies\u0165 k vytvoreniu znovu pou\u017eite\u013en\u00fdch komponentov na ich spracovanie, podobne ako sa to stalo v pr\u00edpade EMF.<\/p>\n<p>Nemo\u017eno poveda\u0165, \u017ee by v Eclipse neexistovalo pochopenie t\u00fdchto probl\u00e9mov. E\u0161te v roku 2005 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.xing.com\/profile\/Martin_Aeschlimann\">Martin Aeschlimann<\/a><\/noindex>, zhrnuj\u00fac sk\u00fasenosti z v\u00fdvoja prototypu CDT, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.eclipse.org\/org\/langsymp\/position_paper_martin_aeschlimann.html\">argumentoval<\/a><\/noindex> potreba vytvori\u0165 spolo\u010dn\u00fa infra\u0161trukt\u00faru pre jazykov\u00e9 modely, vr\u00e1tane modelov zalo\u017een\u00fdch na handle. Av\u0161ak, ako to \u010dasto b\u00fdva, kv\u00f4li prioritnej\u0161\u00edm \u00faloh\u00e1m sa tieto n\u00e1pady dodnes nerealizovali. Medzit\u00fdm zost\u00e1va faktoriz\u00e1cia k\u00f3du *DT projektov jednou z nedostato\u010dne spracovan\u00fdch t\u00e9m v Eclipse.<\/p>\n<p>V istom zmysle projekt Handly rie\u0161i pribli\u017ene tie ist\u00e9 \u00falohy ako EMF, ale pre modely zalo\u017een\u00e9 na handle, a predov\u0161etk\u00fdm jazykov\u00e9 (t.j. predstavuj\u00face prvky \u0161trukt\u00fary ur\u010dit\u00e9ho programovacieho jazyka). Ni\u017e\u0161ie s\u00fa uveden\u00e9 hlavn\u00e9 ciele, ktor\u00e9 sa stanovili pri navrhovan\u00ed Handly:<\/p>\n<ul>\n<li>Identifik\u00e1cia z\u00e1kladn\u00fdch abstrakci\u00ed predmetnej oblasti.<\/li>\n<li>Zn\u00ed\u017eenie n\u00e1mahy a zv\u00fd\u0161enie kvality realiz\u00e1cie jazykov\u00fdch modelov na b\u00e1ze handle prostredn\u00edctvom op\u00e4tovn\u00e9ho pou\u017eitia k\u00f3du.<\/li>\n<li>Poskytnutie zjednoten\u00e9ho API meta\u00farovne k v\u00fdsledn\u00fdm modelom, \u010do umo\u017e\u0148uje vytv\u00e1ra\u0165 spolo\u010dn\u00e9 komponenty IDE pracuj\u00face s jazykov\u00fdmi modelmi na b\u00e1ze handle.<\/li>\n<li>Flexibilita a \u0161k\u00e1lovate\u013enos\u0165.<\/li>\n<li>Integr\u00e1cia s Xtext (v samostatnej vrstve).<\/li>\n<\/ul>\n<p>\nNa identifik\u00e1ciu spolo\u010dn\u00fdch pojmov a protokolov boli analyzovan\u00e9 existuj\u00face realiz\u00e1cie jazykov\u00fdch modelov zalo\u017een\u00fdch na handle. Hlavn\u00e9 rozhrania a z\u00e1kladn\u00e9 implement\u00e1cie poskytovan\u00e9 Handly s\u00fa zn\u00e1zornen\u00e9 na obr. 8.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/47f4bf74093245334b8d67b149734dfc.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 8. Spolo\u010dn\u00e9 rozhrania a z\u00e1kladn\u00e9 implement\u00e1cie prvkov Handly<\/b><\/p>\n<p>Rozhranie IElement predstavuje handle prvku a je spolo\u010dn\u00e9 pre prvky v\u0161etk\u00fdch modelov zalo\u017een\u00fdch na Handly. Abstraktn\u00e1 trieda Element implementuje v\u0161eobecn\u00fd mechanizmus handle\/body (obr. 9).<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/0651c1f284b7edfa36313d4b51d72f08.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 9. IElement a v\u0161eobecn\u00e1 realiz\u00e1cia handle\/body<\/b><\/p>\n<p>Okrem toho Handly poskytuje v\u0161eobecn\u00fd mechanizmus upozornenia na zmenu prvkov modelu (obr. 10). Ako je mo\u017en\u00e9 vidie\u0165, v z\u00e1kladn\u00fdch \u010drt\u00e1ch je anal\u00f3gov\u00fd s mechanizmami upozornenia realizovan\u00fdmi v modely zdrojov a Java modelu a pou\u017e\u00edva IElementDelta na zjednoten\u00fa reprezent\u00e1ciu inform\u00e1ci\u00ed o zmene prvku.<\/p>\n<p><img decoding=\"async\" alt=\"Eclipse ako technologick\u00e1 platforma pre n\u00e1stroje na v\u00fdvoj 1C:Enterprise\" src=\"\/wp-content\/uploads\/2019\/04\/cbdec8cf874308e0fa9dd96d04f62703.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Obr. 10. Spolo\u010dn\u00e9 rozhrania a z\u00e1kladn\u00e9 implement\u00e1cie mechanizmu upozornenia Handly<\/b><\/p>\n<p>Vy\u0161\u0161ie presk\u00faman\u00e9 \u010dasti Handly (obr. 9 a 10) m\u00f4\u017eu by\u0165 pou\u017eit\u00e9 na reprezent\u00e1ciu prakticky ak\u00fdchko\u013evek modelov zalo\u017een\u00fdch na handle. Na vytvorenie <i>jazykov\u00fdch<\/i> modelov projekt pon\u00faka dodato\u010dn\u00fa funkcionalitu \u2013 konkr\u00e9tne spolo\u010dn\u00e9 rozhrania a z\u00e1kladn\u00e9 implement\u00e1cie pre prvky \u0161trukt\u00fary zdrojov\u00e9ho textu, tzv. <i>source elements<\/i> (obr. 8). Rozhranie ISourceFile predstavuje zdrojov\u00fd s\u00fabor, zatia\u013e \u010do ISourceConstruct je prvok v r\u00e1mci zdrojov\u00e9ho s\u00faboru. Abstraktn\u00e9 triedy SourceFile a SourceConstruct implementuj\u00fa generick\u00e9 mechanizmy na podporu pr\u00e1ce so zdrojov\u00fdmi s\u00fabormi a ich prvkami, ako je pr\u00e1ca s textov\u00fdmi vyrovn\u00e1vac\u00edmi pam\u00e4\u0165ami, previazan\u00edm na s\u00faradnice prvku v p\u00f4vodnom texte, zos\u00fala\u010fovan\u00edm modelu s aktu\u00e1lnym obsahom vyrovn\u00e1vacej pam\u00e4te pracovnej k\u00f3pie, a pod. Implement\u00e1cia t\u00fdchto mechanizmov je zvy\u010dajne dos\u0165 zlo\u017eit\u00e1 \u00faloha a Handly m\u00f4\u017ee v\u00fdznamne zn\u00ed\u017ei\u0165 n\u00e1roky na v\u00fdvoj jazykov\u00fdch modelov na b\u00e1ze rukov\u00e4te v\u010faka poskytovaniu kvalitn\u00fdch z\u00e1kladn\u00fdch implement\u00e1ci\u00ed.<\/p>\n<p>Okrem vy\u0161\u0161ie uveden\u00fdch z\u00e1kladn\u00fdch mechanizmov, Handly poskytuje infra\u0161trukt\u00faru textov\u00fdch vyrovn\u00e1vac\u00edch pam\u00e4t\u00ed a \u201esnapshotov\u201c, podporu integr\u00e1cie s editormi zdrojov\u00e9ho k\u00f3du (vr\u00e1tane implementovanej \u201ez krabice\u201c integr\u00e1cie s editorom Xtext), ako aj niektor\u00e9 be\u017en\u00e9 UI komponenty, ktor\u00e9 pracuj\u00fa s modelmi zalo\u017een\u00fdmi na Handly, ako je r\u00e1mec outline. Na ilustr\u00e1ciu svojich schopnost\u00ed projekt poskytuje nieko\u013eko pr\u00edkladov, vr\u00e1tane implement\u00e1cie modelu Java na Handly. (V porovnan\u00ed s \u00faplnou implement\u00e1ciou modelu Java v JDT, je tento model z\u00e1merne trochu zjednodu\u0161en\u00fd pre lep\u0161iu preh\u013eadnos\u0165.)<\/p>\n<p>Ako bolo uveden\u00e9 sk\u00f4r, ve\u013ek\u00e1 pozornos\u0165 bola pri po\u010diato\u010dnom navrhovan\u00ed Handly a n\u00edm sa riadenom rozvoji venovan\u00e1 a na\u010falej sa venuje \u0161k\u00e1lovate\u013enosti a flexibilite. <\/p>\n<p>V z\u00e1sade s\u00fa modely na b\u00e1ze rukov\u00e4te dos\u0165 dobre \u0161k\u00e1lovate\u013en\u00e9 \u201epod\u013ea dizajnu\u201c. Napr\u00edklad idiom rukov\u00e4\u0165\/telo umo\u017e\u0148uje obmedzi\u0165 mno\u017estvo pam\u00e4te, ktor\u00fa model spotrebuje. Ale s\u00fa tu aj nuansy. Tak pri testovan\u00ed Handly na \u0161k\u00e1lovate\u013enos\u0165 bola zisten\u00e1 probl\u00e9m s implement\u00e1ciou mechanizmu notifik\u00e1cie \u2013 pri zmene ve\u013ek\u00e9ho po\u010dtu prvkov bolo vytv\u00e1ranie delta pr\u00edli\u0161 \u010dasovo n\u00e1ro\u010dn\u00e9. Uk\u00e1zalo sa, \u017ee tento ist\u00fd probl\u00e9m sa vyskytuje aj v Java modeli JDT, z ktor\u00e9ho bol svojho \u010dasu adaptovan\u00fd pr\u00edslu\u0161n\u00fd k\u00f3d. Opraven\u00fa chybu v Handly sme opravili a pripravili podobn\u00fd patch pre JDT, ktor\u00fd bol s v\u010fakou prijat\u00fd. Je to len jeden z pr\u00edkladov, kedy by implement\u00e1cia Handly do existuj\u00facich realiz\u00e1ci\u00ed modelov mohla by\u0165 potenci\u00e1lne u\u017eito\u010dn\u00e1, preto\u017ee v tomto pr\u00edpade by bolo mo\u017en\u00e9 opravi\u0165 tak\u00fato chybu len na jednom mieste.<\/p>\n<p>Aby bolo mo\u017en\u00e9 technicky implementova\u0165 Handly do existuj\u00facich modelov, kni\u017enica mus\u00ed ma\u0165 zna\u010dn\u00fa flexibilitu. Hlavn\u00fdm probl\u00e9mom je zachovanie sp\u00e4tnej kompatibility API modelu. Tento probl\u00e9m bol vyrie\u0161en\u00fd <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.eclipse.org\/Handly\/NewIn05\">Handly 0.5<\/a><\/noindex> prostredn\u00edctvom jasn\u00e9ho oddelenia modelom \u0161pecifick\u00e9ho API, definovan\u00e9ho a \u00faplne kontrolovan\u00e9ho v\u00fdvoj\u00e1rom, od jednotn\u00e9ho API meta\u00farovne poskytovan\u00e9ho kni\u017enicou. To nielen\u017ee umo\u017e\u0148uje technick\u00fa implement\u00e1ciu Handly do existuj\u00facich realiz\u00e1ci\u00ed, ale tie\u017e poskytuje v\u00fdvoj\u00e1rovi novej modely zna\u010dn\u00fa slobodu pri navrhovan\u00ed API.<\/p>\n<p>Flexibilita m\u00e1 aj in\u00e9 aspekty. Napr\u00edklad, Handly skoro nekladie obmedzenia na \u0161trukt\u00faru modelu a m\u00f4\u017ee sa pou\u017e\u00edva\u0165 ako na modelovanie jazykov v\u0161eobecn\u00e9ho ur\u010denia, tak aj predmetovo orientovan\u00fdch jazykov. Pri budovan\u00ed \u0161trukt\u00fary zdrojov\u00e9ho s\u00faboru, Handly nepredpisuje konkr\u00e9tnu formu reprezent\u00e1cie AST a v z\u00e1sade ani nevy\u017eaduje samotn\u00fa pr\u00edtomnos\u0165 AST, \u010d\u00edm zabezpe\u010duje kompatibilitu s takmer ak\u00fdmiko\u013evek mechanizmami syntaktickej anal\u00fdzy. Nakoniec, Handly podporuje pln\u00fa integr\u00e1ciu s Eclipse workspace, ale m\u00f4\u017ee fungova\u0165 aj priamo s s\u00faborov\u00fdmi syst\u00e9mami, v\u010faka integr\u00e1cii s <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.eclipse.org\/EFS\">Eclipse File System<\/a><\/noindex> (EFS).<\/p>\n<p>Aktu\u00e1lna verzia <noindex><a rel=\"nofollow\" href=\"https:\/\/projects.eclipse.org\/projects\/technology.handly\/releases\/0.6\">Handly 0.6<\/a><\/noindex> bola vydan\u00e1 v decembri 2016. Napriek tomu, \u017ee projekt je moment\u00e1lne v inkuba\u010dnej f\u00e1ze a API e\u0161te nebolo definit\u00edvne stanoven\u00e9, Handly sa u\u017e pou\u017e\u00edva v dvoch ve\u013ek\u00fdch komer\u010dn\u00fdch produktoch, ktor\u00e9 sa odv\u00e1\u017eili sta\u0165 sa \"skor\u00fdmi adopcemi\", a, treba poveda\u0165, zatia\u013e toho nelutuj\u00fa.<\/p>\n<p>Ako bolo u\u017e spomenut\u00e9, jeden z t\u00fdchto produktov je 1C:Enterprise Development Tools, kde sa Handly od sam\u00e9ho za\u010diatku pou\u017e\u00edva na modelovanie prvkov vysoko\u00farov\u0148ovej \u0161trukt\u00fary jazykov 1\u0421:\u041f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0435, ako je zabudovan\u00fd programovac\u00ed jazyk a jazyk dotazov. Druh\u00fd produkt je menej zn\u00e1my \u0161irokej verejnosti. Je to <noindex><a rel=\"nofollow\" href=\"https:\/\/www.codasip.com\/custom-processor\/\">Codasip Studio<\/a><\/noindex>, integrovan\u00e9 prostredie na n\u00e1vrh procesorov so \u0161pecifickou aplik\u00e1ciou (application-specific instruction-set processor, ASIP), ktor\u00e9 sa pou\u017e\u00edva nielen v \u010deskej spolo\u010dnosti Codasip, ale aj jej klientmi, medzi ktor\u00fdmi s\u00fa <noindex>AMD<\/noindex>, <noindex><a rel=\"nofollow\" href=\"http:\/\/www.avg.com\/\">AVG<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"http:\/\/www.mobileye.com\/\">Mobileye<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"http:\/\/www.sigmadesigns.com\/\">Sigma Designs<\/a><\/noindex>Codasip vyu\u017e\u00edva Handly v produkcii od roku 2015, pri\u010dom za\u010dal s verziou Handly 0.2. Posledn\u00e9 vydanie Codasip Studio pou\u017e\u00edva verziu 0.5, ktor\u00e1 bola vydan\u00e1 v j\u00fani 2016. Ond\u0159ej Il\u010d\u00edk, ved\u00faci v\u00fdvoja IDE v Codasip, je v kontakte s projektom a poskytuje ve\u013emi d\u00f4le\u017eit\u00fa sp\u00e4tn\u00fa v\u00e4zbu z poh\u013eadu \u201eextern\u00e9ho adapt\u00e9ra\u201c. Dokonca sa mu podarilo n\u00e1js\u0165 trocha vo\u013en\u00e9ho \u010dasu, aby sa priamo zapojil do v\u00fdvoja projektu a realizoval vrstvu UI (pribli\u017ene 4000 riadkov k\u00f3du) pre jeden z pr\u00edkladov Handly, model Java. V\u0161etky podrobnosti o pou\u017e\u00edvan\u00ed Handly adapt\u00e9rmi si m\u00f4\u017eete pre\u010d\u00edta\u0165 na str\u00e1nke <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.eclipse.org\/Handly\/Adopters\">Pr\u00edpadov\u00e9 \u0161t\u00fadie<\/a><\/noindex> projektu.<\/p>\n<p>D\u00fafame, \u017ee po vydan\u00ed verzie 1.0 so z\u00e1rukou stability API a opusten\u00edm projektu z inkuba\u010dn\u00e9ho stavu sa objavia aj nov\u00ed adapt\u00e9ry pre Handly. Zatia\u013e sa projekt na\u010falej testuje a \u010falej zlep\u0161uje API, pri\u010dom vyd\u00e1va dve \"ve\u013ek\u00e9\" verzie ro\u010dne \u2013 v j\u00fani (v rovnak\u00fd de\u0148, ako aj s\u00fa\u010dasn\u00e9 vydanie Eclipse) a v decembri, \u010d\u00edm zabezpe\u010duje predv\u00eddate\u013en\u00fd harmonogram, na ktor\u00fd sa adapt\u00e9ry m\u00f4\u017eu spolieha\u0165. M\u00f4\u017eeme tie\u017e doda\u0165, \u017ee ukazovate\u013e \u201ebug rate\u201c projektu zost\u00e1va na stabilne n\u00edzkej \u00farovni a Handly spo\u013eahlivo funguje v produktoch ran\u00fdch adapt\u00e9rov u\u017e od prv\u00fdch verzi\u00ed. \u010eal\u0161ie inform\u00e1cie o Eclipse Handly si m\u00f4\u017eete pre\u010d\u00edta\u0165 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/pisv\/gethandly\/wiki\">\u00davodn\u00fd tutori\u00e1l<\/a><\/noindex> a <noindex><a rel=\"nofollow\" href=\"http:\/\/www.eclipse.org\/downloads\/download.php?file=\/handly\/docs\/handly-overview.pdf&amp;r=1\">Architektonick\u00fd preh\u013ead<\/a><\/noindex>.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1c\/blog\/323508\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, Eclipse \u0434\u0430\u0432\u043d\u043e \u0443\u0436\u0435 \u043d\u0435 \u043d\u0443\u0436\u0434\u0430\u0435\u0442\u0441\u044f \u0432 \u043e\u0441\u043e\u0431\u043e\u043c \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0438. \u041c\u043d\u043e\u0433\u0438\u0435 \u0437\u043d\u0430\u043a\u043e\u043c\u044b \u0441 Eclipse \u0431\u043b\u0430\u0433\u043e\u0434\u0430\u0440\u044f Eclipse Java development tools (JDT). \u0418\u043c\u0435\u043d\u043d\u043e \u044d\u0442\u0430 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u0430\u044f open-source Java IDE \u0430\u0441\u0441\u043e\u0446\u0438\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0443 \u0431\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u0430 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u043e\u0432 \u0441\u043e \u0441\u043b\u043e\u0432\u043e\u043c \u201cEclipse\u201d. \u041e\u0434\u043d\u0430\u043a\u043e Eclipse \u2013 \u044d\u0442\u043e \u0438 \u0440\u0430\u0441\u0448\u0438\u0440\u044f\u0435\u043c\u0430\u044f \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0434\u043b\u044f \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u0441\u0440\u0435\u0434\u0441\u0442\u0432 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 (Eclipse Platform), \u0438 \u0446\u0435\u043b\u044b\u0439 \u0440\u044f\u0434 IDE, \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u043d\u044b\u0445 \u043d\u0430 \u0435\u0435 \u043e\u0441\u043d\u043e\u0432\u0435, \u0432 \u0442\u043e\u043c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24268,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32464","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, Eclipse \u0434\u0430\u0432\u043d\u043e \u0443\u0436\u0435 \u043d\u0435 \u043d\u0443\u0436\u0434\u0430\u0435\u0442\u0441\u044f \u0432 \u043e\u0441\u043e\u0431\u043e\u043c \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0438.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47Eclipse \u043a\u0430\u043a \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0434\u043b\u044f 1C:Enterprise Development Tools | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, Eclipse \u0434\u0430\u0432\u043d\u043e \u0443\u0436\u0435 \u043d\u0435 \u043d\u0443\u0436\u0434\u0430\u0435\u0442\u0441\u044f \u0432 \u043e\u0441\u043e\u0431\u043e\u043c \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0438.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:47:12+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:47:12+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Eclipse ako technologick\u00e1 platforma pre 1C:Enterprise Development Tools | ProHoster","description":"Eclipse pravdepodobne u\u017e ani nepotrebuje osobitn\u00fa prezent\u00e1ciu.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Eclipse \u043a\u0430\u043a \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0434\u043b\u044f 1C:Enterprise Development Tools | ProHoster","og:description":"\u041d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, Eclipse \u0434\u0430\u0432\u043d\u043e \u0443\u0436\u0435 \u043d\u0435 \u043d\u0443\u0436\u0434\u0430\u0435\u0442\u0441\u044f \u0432 \u043e\u0441\u043e\u0431\u043e\u043c \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0438.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/eclipse-kak-tehnologicheskaya-platforma-dlya-1c-enterprise-development-tools","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:47:12+00:00","article:modified_time":"2019-10-31T18:47:12+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32464","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 11:00:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:58:24","updated":"2026-01-21 11:00:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/32464","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=32464"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/32464\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/24268"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=32464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=32464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=32464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}