Presentation is about the sewer system of Zagreb at the beginning of the 21st century - presentation was shown at the conference on the city of Zagreb development in 2008.
This document discusses the adoption of Composer for dependency management in Magento 1.x and 2.x. It describes how Composer was customized for Magento through plugins to handle file placement and deployment. It also outlines changes made to Magento core like granular packages, semantic versioning, and declaring dependencies to fully support Composer. Composer brings benefits of resolving, downloading and updating dependencies automatically in Magento projects.
Magento 2 Composer for Extensions DistributionSergii Shymko
The document discusses the evolution of dependency management in Magento from early releases which had no formal dependency management, through PEAR and modman, to the adoption of Composer. It outlines key dates like the first Magento release, introduction of modman and first use of Composer. It describes Composer's capabilities and how it addressed issues in Magento 1.x. It also covers changes made in Magento 2 to fully support Composer like granular packages, semantic versioning and declaring dependencies.
This document summarizes the key changes and new features in Magento 2, including:
- Increased system requirements for both server-side (PHP 5.3.3, MySQL 5.1) and client-side (IE8, Firefox 11, Chrome 18, Safari 5).
- Removal of configuration like class prefixes, code pools, and compilation to improve convention over configuration.
- Introduction of dependency injection, formal application areas, and modular view files.
- Simplified customization through declarative grids/forms and validation configuration.
- Emphasis on quality control through automated testing and continuous integration.
The document summarizes an internship presentation analyzing farmers' perceptions of "Fast Mix" herbicide in Rudrapur, India. The presentation covered: industry and company profiles; research objectives to analyze awareness of Fast Mix and promotional activities; methodology using surveys; results showing low Fast Mix awareness but openness to herbicides; suggestions to increase promotion and awareness; and a conclusion that Rudrapur has potential for increased herbicide sales with better promotion.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and JavaScript for toggling div elements. The code handles logging users in and out, and checking for remember me cookies.
Black Magic of Code Generation in Magento 2Sergii Shymko
This document discusses code generation in Magento 2. It generates code for dependency injection such as factories and proxies. It also generates code for interceptors to implement plugins. Code is generated for the service layer including repositories, persistors, search results, and extension attributes. Loggers are also generated to log method calls. Code generation allows writing code at a higher level of abstraction and avoids boilerplate code.
Presentation is about the sewer system of Zagreb at the beginning of the 21st century - presentation was shown at the conference on the city of Zagreb development in 2008.
This document discusses the adoption of Composer for dependency management in Magento 1.x and 2.x. It describes how Composer was customized for Magento through plugins to handle file placement and deployment. It also outlines changes made to Magento core like granular packages, semantic versioning, and declaring dependencies to fully support Composer. Composer brings benefits of resolving, downloading and updating dependencies automatically in Magento projects.
Magento 2 Composer for Extensions DistributionSergii Shymko
The document discusses the evolution of dependency management in Magento from early releases which had no formal dependency management, through PEAR and modman, to the adoption of Composer. It outlines key dates like the first Magento release, introduction of modman and first use of Composer. It describes Composer's capabilities and how it addressed issues in Magento 1.x. It also covers changes made in Magento 2 to fully support Composer like granular packages, semantic versioning and declaring dependencies.
This document summarizes the key changes and new features in Magento 2, including:
- Increased system requirements for both server-side (PHP 5.3.3, MySQL 5.1) and client-side (IE8, Firefox 11, Chrome 18, Safari 5).
- Removal of configuration like class prefixes, code pools, and compilation to improve convention over configuration.
- Introduction of dependency injection, formal application areas, and modular view files.
- Simplified customization through declarative grids/forms and validation configuration.
- Emphasis on quality control through automated testing and continuous integration.
The document summarizes an internship presentation analyzing farmers' perceptions of "Fast Mix" herbicide in Rudrapur, India. The presentation covered: industry and company profiles; research objectives to analyze awareness of Fast Mix and promotional activities; methodology using surveys; results showing low Fast Mix awareness but openness to herbicides; suggestions to increase promotion and awareness; and a conclusion that Rudrapur has potential for increased herbicide sales with better promotion.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and JavaScript for toggling div elements. The code handles logging users in and out, and checking for remember me cookies.
Black Magic of Code Generation in Magento 2Sergii Shymko
This document discusses code generation in Magento 2. It generates code for dependency injection such as factories and proxies. It also generates code for interceptors to implement plugins. Code is generated for the service layer including repositories, persistors, search results, and extension attributes. Loggers are also generated to log method calls. Code generation allows writing code at a higher level of abstraction and avoids boilerplate code.
Composer is a dependency manager for PHP that resolves, downloads, and assembles dependencies for a project. Magento 1.x adopted Composer through a plugin that puts module files in the correct directories and supports different deployment strategies. Magento 2 fully embraced Composer by implementing granular packages for modules, themes, and locales, adopting semantic versioning, and declaring versioned dependencies. This improved management of components and their dependencies. Core changes for Composer included module and dependency versioning and validation of the environment.
The document discusses Magento's Performance Toolkit which is available on GitHub. It provides features for generating sample data, imitating user activity, and comparing performance before and after changes. The toolkit uses fixtures to define sample data, profiles to set fixture parameters, and scenarios to imitate user activity. It also discusses how to customize the toolkit by creating custom fixtures, profiles, and scenarios.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and PHP code to handle the login form submission and session handling.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and JavaScript for toggling div elements. The code handles logging users in and out, and checking for remember me cookies.
The document discusses Magento's code migration tool which helps automate the process of upgrading a custom Magento 1 codebase to Magento 2. The tool analyzes code to migrate the directory structure, layout, configuration, and PHP code between the two versions. It provides commands to generate class mappings, migrate specific code components, and offers guidance on tailoring the tool and testing migrated modules.
Magento 2 improves upon design localization and holiday scheduling compared to Magento 1.x. It uses a single package/theme/skin configuration instead of separate locale-specific skins. Themes can provide localized slogan and logo files, eliminating the need to duplicate static files. Themes also inherit from each other through unlimited levels, avoiding copy/paste of files. This allows simple localization of slogans as well as scheduling different designs for holidays while maintaining a single configuration across locales.
Magento 1.x to Magento 2 Code Migration ToolsSergii Shymko
This document discusses Magento's code migration tool which helps automate the process of upgrading a custom Magento 1.x codebase to Magento 2. It provides an overview of the tool, outlines the key components that need to be migrated (e.g. codebase, database), and describes the basic steps and commands for running the migration including generating mappings, migrating directory structure, layouts, configurations, and PHP code. It emphasizes that while the tool automates much of the routine work, manual testing and fixes are still required to complete the upgrade.
Composer is a dependency manager for PHP that resolves, downloads, and assembles dependencies for a project. Magento 1.x adopted Composer through a plugin that puts module files in the correct directories and supports different deployment strategies. Magento 2 fully embraced Composer by implementing granular packages for modules, themes, and locales, adopting semantic versioning, and declaring versioned dependencies. This improved management of components and their dependencies. Core changes for Composer included module and dependency versioning and validation of the environment.
The document discusses Magento's Performance Toolkit which is available on GitHub. It provides features for generating sample data, imitating user activity, and comparing performance before and after changes. The toolkit uses fixtures to define sample data, profiles to set fixture parameters, and scenarios to imitate user activity. It also discusses how to customize the toolkit by creating custom fixtures, profiles, and scenarios.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and PHP code to handle the login form submission and session handling.
The document appears to be configuration code for a PHP login shell called EgY_SpIdEr ShElL. It sets variables like the username and password, page title, and other configuration options. It also includes CSS for styling the login page and JavaScript for toggling div elements. The code handles logging users in and out, and checking for remember me cookies.
The document discusses Magento's code migration tool which helps automate the process of upgrading a custom Magento 1 codebase to Magento 2. The tool analyzes code to migrate the directory structure, layout, configuration, and PHP code between the two versions. It provides commands to generate class mappings, migrate specific code components, and offers guidance on tailoring the tool and testing migrated modules.
Magento 2 improves upon design localization and holiday scheduling compared to Magento 1.x. It uses a single package/theme/skin configuration instead of separate locale-specific skins. Themes can provide localized slogan and logo files, eliminating the need to duplicate static files. Themes also inherit from each other through unlimited levels, avoiding copy/paste of files. This allows simple localization of slogans as well as scheduling different designs for holidays while maintaining a single configuration across locales.
Magento 1.x to Magento 2 Code Migration ToolsSergii Shymko
This document discusses Magento's code migration tool which helps automate the process of upgrading a custom Magento 1.x codebase to Magento 2. It provides an overview of the tool, outlines the key components that need to be migrated (e.g. codebase, database), and describes the basic steps and commands for running the migration including generating mappings, migrating directory structure, layouts, configurations, and PHP code. It emphasizes that while the tool automates much of the routine work, manual testing and fixes are still required to complete the upgrade.
1. Konferencija Razvitak
Zagreba 2008. - ZAKLJUČCI
• ISPRAVNO FUNKCIONIRANJE SUSTAVA
ODVODNJE I PROČIŠČAVANJA OTPADNIH
VODA GRADA ZAGREBA JEDNO JE OD
KLJUČNIH PREDUVJETA ŽIVOTA I RADA
GRAĐANA GRADA ZAGREBA I KAO TAKVO
PREDSTAVLJA NEIZMJERNO MATERIJALNO
BOGATSTVO GRADA U KOJE SU TIJEKOM
VIŠE OD STOLJEĆA FUNKCIONIRANJA
JAVNE GRADSKE ODVODNJE ULOŽENA
OGROMNA MATERIJALNA SREDSTVA U
VLASNIŠTVU GRAĐANA.
2. • Usprkos značajnim ulaganjima u KAPITALNE
OBJEKTE odvodnje i pročišćavanja otpadnih
voda, djelovi KANALIZACIJSKOG SUSTAVA
GRADA ZAGREBA TRPE NEBRIGU u smislu
nedovoljnog provođenja mjera sanacije,
rehabilitacije i zamjene amortiziranih,
strukturalno i funkcionalno neadekvatnih
objekata odvodnje kao i neadekvatnog tretmana
prilikom planiranja gradskih radova;
3. • BRZIM I NEKONTROLIRANIM ŠIRENJEM
GRADA, čestim promjenama GUP-a kojim
ZELENE POVRŠINE postaju GRAĐEVINSKE
pogotovo u sjevernom dijelu, A BEZ
MOGUĆNOSTI ADEKVATNE REAKCIJE U
SMISLU PRILAGODBE SUSTAVA ODVODNJE
UČINCIMA URBANIZACIJE, NEPOVRATNO SE
UBRZAVA PROCES DEGRADACIJE
ZAGREBAČKE KANALIZACIJE KAKO U
FUNKCIONALNOM TAKO I U
STRUKTURALNOM SMISLU, DIJELOVI
SUSTAVA PODLOŽNI SU POVEĆANOM
RIZIKU OD ŠTETA PO MATERIJALNU
IMOVINU I LJUDSKO ZDRAVLJE TE
POVEČAVAJU TROŠKOVI PROČIŠĆAVANJA
na gradskom uređaju CUPOV GZ.
4. Iz gore navedenih ključnih činjenica, nepohodno je
potrebno provesti sljedeće aktivnosti i mjere:
• URBANISTIČKO PLANIRANJE čvrsto
TEMELJITI NA RAZVOJNIM PROJEKTIMA
SUSTAVA ODVODNJE, bez čega se koće
investicijski projekti i strana ulaganja
• INTEGRALNO PLANIRANJE UPRAVLJANJE
VODNIM RESURSIMA GRADA OGRANIČENO
JE UVJETIMA RAZVOJA SUSTAVA
ODVODNJE otpadnih voda grada Zagreba
(Sava i vodne stepenice)
• RAZVOJNI PLAN SUSTAVA ODVODNJE I
PROČIŠĆAVANJA („POKS 2009.“) najhitnije
obnoviti a GRAD TREBA INZISTIRATI NA
STRIKTNOJ PRIMJENI RJEŠENJA
5. • NAJUGROŽENIJI JE POJAS CENTRA GRADA (lijeva
obala Save) koji se proteže od zapada prema istoku i to
na prijelazu iz tipično brdskog sliva (donji obronci
Medvednice) u ravničarsko područje (od Ilice prema
Savi) sa naglim promjenom pada dna kanala.
• REKONSTRUKCIJE POJEDINIH GRADSKIH
PROMETNICA i prateće infrastrukture na području lijeve
obale Save tijekom ljetnih mjeseci nisu dovoljno
opsežni i brzi u odnosu na degradaciju sustava
odvodnje te potrebe sanacije i rekonstrukcije centralnog
dijela sustava.
• RADOVE SANACIJE POTREBNO JE PROVODITI
KONTINUIRANO – ne kampanjski i ne po političkoj
odluci . POSEBNU PAŽNJU POSVETITI CENTRU
GRADA.
6. • Na području desne obale Save – NOVI ZAGREB
NAJHITNIJE JE POTREBNO ZAPOČETI
SUSTAVNU IZGRADNJU GLAVNIH SABIRNIH
KOLEKTORA PO NOVOJ KONCEPCIJI
ODVODNJE koja je u izradi (Novelacija POKS-a iz
1998.).
• Na području desne obale Save riješiti odvodnju i
pročiščavanje dijelova sustava koji ne pripadaju u
obuhvat zagrebačkog GUP-a a koji se prirodno
„cijede“ prema kanalizaciji Novog Zagreba.
7. • Proanalizirati tehničko - ekonomsku opravdanost
i definirati elemente ev. mogućeg rješenja za
DOVOĐENJE OTPADNIH VODA PODRUČJA
GRADA VELIKE GORICE NA ZAGREBAČKI
UREĐAJ za pročišćavanje otpadnih voda (u
tijeku je izrada analize mogučnosti priključenja
Sesveta na CUPOV GZ).
• OBZIROM NA STANJE IZVORA
FINANCIRANJA I OPĆU FINANCIJSKU I
GOSPODARSKU RECESIJU – ZG HOLDING
mora realno sagledati mogućnosti iznalaženja
sredstava za kontinuiranu obnovu sustava
odvodnje grada za period nakon 2010.- 2015.g.
8. U smislu svega gore navedenog treba poticati i sljedeće opće
mjere za smanjenje potrošnje pitke vode i smanjenje dotoka u
sustav odvodnje:
• POTICATI ZAHVAĆANJE I KORIŠTENJE
KIŠNICE za individualno i kolektivno stanovanje:
• KORIŠTENJE “SIVE VODE” i KIŠNICE u
domaćinstvima
• KOD NOVOGRADNJI - izgradnja dvostrukog
sustava vodovodnih instalacija za KORIŠTENJE
KIŠNICE I “SIVE VODE”
• PRANJE ULICA I ZELENIH POVRŠINA
KIŠNICOM
9. • POTICANJE KORIŠTENJA UREĐAJA KOJI
ŠTEDE (PITKU) VODU
• POTICATI ZAPOŠLJAVANJE NOVIH
STRUČNJAKA I SPRIJEČITI ODLIV
KADROVA IZ ViO TE IZRADITI PROGRAM
ODRŽAVANJA ZNANJA
• Formirati CENTAR ZA UPRAVLJANJE
SUSTAVOM ODVODNJE pri ZGH – podružnica
ViO, uključivo SUSTAV PREDVIĐANJA
TEČENJA U SUSTAVU I PREDVIĐANJE
DOTOKA NA CUPOV GZ
10. • FORMIRATI CENTAR ZA KRIZNA STANJA
prouzrokovana neadekvatnim funkcioniranjem
sustava odvodnje i pročišćavanja otpadnih voda
bilo iz razloga prouzročenih prirodnim
katastrofama ili ljudskom aktivnošću, sve u
smislu zaštite materijalne imovine i ljudskog
zdravlja;
• IZGRADITI SUSTAV JAVNOG
IZVJEŠČIVANJA JAVNOSTI U REALNOM
VREMENU (INTERNET) O SVIM KLJUČNIM
DOGAĐAJIMA VEZANIM UZ RAD,
ODRŽAVANJE I RAZVOJ SUSTAVA
ODVODNJE I PROČIŠĆAVANJA