> From that experience I can definitely say make sure you automate as > I have quite some experience with continuous development. > Although I am only a starting developer with joomla-extensions (no jed > Thanks for the info, I'll definately be going over: !_develo. Hand but by means of either phing or ant (or something similar) One for the administrator-Īnd then have another checkout for the root folder in order to manageĪs for as creating an install-package I will definitely not do that by Just checkout the files into a local installation of joomla.
![phpstorm ubuntu 16.10 add to menu phpstorm ubuntu 16.10 add to menu](https://i.ytimg.com/vi/-wamR3WJt8I/maxresdefault.jpg)
There is however a change I will probably make to my setup. Website for which I am developing my extension An other ant-script with which I upload the made changes to the An ant-script in place which copies the files to my local joomla Multiple repositories, which sounds weird). Just one repository per component (you might want to change the db-ĭesign at some point which results in having to make changes to I have quite some experience with continuous development.įrom that experience I can definitely say make sure you automate as
![phpstorm ubuntu 16.10 add to menu phpstorm ubuntu 16.10 add to menu](http://vignette4.wikia.nocookie.net/en.linux/images/7/74/Ubuntu_15.10.png)
New package, its just two exports away (overwriting existing files).Īlthough I am only a starting developer with joomla-extensions (no jed It's not perfect, but works pretty good, and means if I need to make a Have to move the xml file to the MyInstallFolder root, and have the MyInstallFolder so it is MyInstallFolder/com_mycomponent, then I just The svn files are correct and updated, I export the admin componentįolder to MyInstallFolder/admin so there is MyInstallFolder/admin/Ĭom_mycomponent, and export the frontend component folder to
![phpstorm ubuntu 16.10 add to menu phpstorm ubuntu 16.10 add to menu](https://linuxhint.com/wp-content/uploads/2017/06/word-image-30.png)
Install.php are put in the correct place for the install).
#Phpstorm ubuntu 16.10 add to menu install
The install package (doesn't really matter if some files like language/ I just set up the files in administrator/components/com_mycomponentįolder and components/com_mycomponent folder exactly as they are in It's too much to try and set up eclipse now,īut the exporting methods works ok in the short term. Thanks for the info, I'll definately be going over: Want all that svn stuff in the installer folder. Installer files is different than the localhost files, and I don't Tortoise svn will keep the files up to date, but it will also keep theįile/folder relationship, and the file/folder relationship in the If you copy the svn files to a different place on the computer, Synch all the files in my localhost folders into the installer. Human, and it's only a matter of time before I do something dumb lateĭo thers have any automatic way to hit a button and automatically I export them in the right place, this is a job for a computer, not a
#Phpstorm ubuntu 16.10 add to menu update
The manual part is what I don't like, did I update all the files? did
![phpstorm ubuntu 16.10 add to menu phpstorm ubuntu 16.10 add to menu](https://i.stack.imgur.com/s2hgV.png)
(during the beta phase IĬonstantly bugfix and update, untill there are no complaints, then I Into the installer folder, then rezip it. Now if I fix a bug, I need to update the files on my localhost (thatĪre part of the svn), then manually export the files I have updated Them into the appropriate place, and zipped the files. Manually made a seperate folder, exported all the files, and arranged The component is in beta at present, so I have The problem I'm having at the moment is with bundling the component Testing without worring about the data/content itself being in synch (it's a gallery extension) are kept seperate, we can do our own We find this works quite good, as we can both edit all the php files,Īnd if we update regularly, we don't get many conflcits (we don't goĪs far a locking branches). I have set up one repository for the administrator/components/Ĭom_mycomponent folder, and one for the components/com_mycomponentįolder (using subversion at and tortoise svn Currently I'm doing (jed listed) extension development with 2