Quote from: sottwell at Sep 23, 2013, 09:36 AM<sigh> you don't leave me much in the way of an excuse to keep putting it off... so now I'm going to github to make a fork.</sigh>
FYI, there's a section in my book on using Git to contribute to MODX. I think it's still fairly accurate.
-
☆ A M B ☆
- 24,524 Posts
Yes, that part isn't too difficult. I just spent over an hour trying to figure out how to get PHPStorm (on OS X) to do the unit test setup. Doesn't work the way your docs in MyComponent suggest. Have to give it up for now. Maybe better luck later after some research.
I had a devil of a time getting PhpStorm to generate unit test too, but that was some time ago. Supposedly, the skeleton generator is built in to PhpStorm 7.0 but I haven't tried it yet.
-
☆ A M B ☆
- 24,524 Posts
Ah. I haven't upgraded for a while, I'm still running 6-something. This is getting rather far off-topic, so if you don't mind I'll start a new thread.
I think I'm the only staffer that doesn't use PHPStorm. It just brings back really bad memories of Eclipse based Flex (Flash Builder). I should start using it, but my PHP would probably still be crappy anyways.
jpdevries
Quote from: sottwell at Nov 15, 2013, 02:16 AMAh. I haven't upgraded for a while, I'm still running 6-something. This is getting rather far off-topic, so if you don't mind I'll start a new thread.
New thread is a good idea, but just in case I don't find it. The info at that link should be good for 6.x.
One should not compare PHPStorm to Eclipse based editors, Eclipse is slow, buggy and overall rubbish. PHPStorm is fast, feature ready, future ready, fast, not buggy, fast, emmet included, best git integration ever, fast, autocomplete great for large projects, fast and did I mention fast.
Didn't mean to knock it. I'm sure the only reason I mentioned anything is I hear so much about it I wonder myself why I haven't gotten more into it. It may be the Java-esque IDE that initially turned me away. I did finally upgrade to 7 and switch to a darker theme and it feels much improved. This is also coming from someone who has licenses to most the hip Mac text editors out there, and still predominantly uses TextMate 1 because it's just that comfortable.
Trust me I get grief for not using it all the time, but every time I open it I see a million options I don't care about and run away. Kind of reminds me of what almost happened the first time I used something else :p.
I would say I'd give PHPStorm another whirl sometime soon but my skills at bribing others who are much more qualified has recently begun to exceed that of writing it on my own.
jpdevries
I absolutely love PhpStorm, but it's not bug free. Some of the keyboard shortcuts don't work on my machine, I've had the code reformatting introduce errors into my code (haven't tried it lately), and there's a maddening bug where the input line doesn't get focus with Ctr-F (find) and you end up typing the search term in your code. That last one has been around for at least two major releases. In addition, the MySQL DB editor is so clunky that it's easier to shell out to PhpMyAdmin. In addition, PhpStorm takes forever to load, even from a solid-state drive, so unless you keep it open, it's useless for quick editing of files.
That said, there are a million reasons to use it. The biggest for me are the blindingly fast multi-file search and replace (with regex support) that lets me search all my extras plus the MODX code for anything I might want to use or consult; the on-screen regex feedback when constructing a regex (it not only shows you every section the regex is selecting, but what it will be replaced by as well); and best of all, the automatic code inspection, which blows all other editors out of the water. It flags *all* syntax errors (and highlights their location), and as a bonus, warns you about misspelled, unused, unset, and undeclared variables as well as variables that are set and then changed before they are used. It also flags unreachable code.
Another big plus when working with MODX is that it knows all the MODX classes and will auto-complete their methods (with hints about their arguments).
☆ A M B ☆