Development environment

By the way Jonas,

I have added a request for a CUSTOM FIELD to be added here - please up-vote if you think this will be useful..

I consider it essential, and very easy to implement, basically a custom field, with a textarea to paste pre-existing Form XML into

www.component-creator.com/en/forum/featu...m-joomla-form-fields

It will solve all those issues with having to wait for Component Creator Devs to give us the new fields more quickly..

Custom Field sounds like a very good idea! 

I've been using NetBeans. It let's me start a GIT repository right from the IDE and it is very simple to use.
I usually start by creating the component and try it out, then I go back to component creator and modify some things and reinstall it. I repeat the process several times in the beginning.
When I'm happy with my component as a good starting point, I start my GIT repository and begin modifying files.
I'm usually not shy about modifying any files in the component. There is nothing to fear since GIT is keeping backups for everything. GIT is really awesome and I consider it one of my most useful tools.

This setup has been working very good for me. I only need 1 program to work on my components. But here I haven't seen any comments on NetBeans. Is there a reason why nobody seems to be using it?

I also use this setup to learn how Joomla works and how to develop my own components. I create a component, commit to GIT, go back to CC, edit my component, reinstall and take a look at the changes. CC can be a very useful educational tool!!!

Great! I knew I couldn't be te only one! haha! Kudos to Netbeans!

Thanks to all for yours experience.
I use CC with Git, but change component version is change all php-files and it's not usable for track changes.

I have added feature request for this: www.component-creator.com/en/forum/featu...on-output-in-php#878

Hi,
there is a way to use git efficiently even though cc replaces all files:

before installing your component, check out a branch for the component. This branch will be used only for the bare component innstalled directly from cc. Do Not edit these files after innstalling:

git checkout -b com_yourcomponent

Now innstall the component the normal way. After innstalling, commit the changes, and go back to master (or whatever branch you are working on). Then merge in the changes:

git status # all changed files are listed
git add . #adding all files
git commit -m "Innstalling changes from CC"
Immediately checkout master before accidentially editing the files in the branch com_yourcomponent
git checkout master
git merge com_yourcomponent

Be sure to keep your branch com_yourcomponent after merging, you'll want to reuse it. Now you can make whatever changes you want to the component, without fear that they will be overwritten. Next time you want to innstall changes directly from the component-builder, do the dance all over again:

git checkout com_yourcomponent
Innstall from cc in /administrator
git status # all changed files are listed
git add . #adding all files
(be aware you might have to remove files manually, if you have made changes in cc so that less files are innstalled, f.eks. if you removed a table, or removed frontend editing or similar)
git commit -m "Innstalling changes from CC"
git checkout master
git merge com_yourcomponent

There might be conflicts where both you and cc has made actual changes to the same file, but this is no different than other conflicts using git.

I use this scheme all the time now, it has very few problems. Be aware to close files in your editor as you switch branches, or else you might make a little mess of things,

regards Jonas