Development environment for Windows

Permalink 1 user found helpful
Hi all,

A while back I wrote a kind of a log about the setup of my development environment.

Since many developers found it quite useful, I'm writing here to say that I've just updated it...

You can find this *log* here:http://mlocati.github.io/MyDevelopmentEnvironment/...

You can track its changes here:https://github.com/mlocati/MyDevelopmentEnvironment/commits/master...

mlocati
View Replies:
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi mlocati,

I am a big fan of this guide and really like the new additions. Especially the new command line information section. Are you open to adding it to the concrete5.org documentation?
https://github.com/mlocati/MyDevelopmentEnvironment/blob/bb2e7544c3a...
mlocati replied on at Permalink Reply
mlocati
Yes, I think that an appendix to the developers docs could be helpful.
I just added it to my spare time todolist (but it's quite long ;) )
MrKDilkington replied on at Permalink Reply
MrKDilkington
@mlocati

That is great news, thank you.
MrKDilkington replied on at Permalink Reply
MrKDilkington
@mlocati

Very nice job on the documentation. It is thorough, lots of examples, and goes into detail.

The PRB reviewers will really like this. Being able to make batch files to reset, install, and copy over basic config settings is a huge timesaver.

"Command line interface (CLI) commands"
http://documentation.concrete5.org/developers/appendix/cli-commands...
mlocati replied on at Permalink Reply
mlocati
@MrKDilkington

Thank you Karl!

I wrote that page non only for PRB reviewers. I wanted to share those info also for package developers: I find really useful the c5:package-update command (to force updating packages without changing package version), the c5:package-translate to automatically build translation files and the c5:package-pack command to do a lot of magic stuff;)
And another great thing is that these last 2 commands also work on 5.6 packages: they are really time-saving for every developer.
MrKDilkington replied on at Permalink Reply
MrKDilkington
@mlocati

I just experimented with the c5:package-translate command and it works very well.

It can be used to check if a package is not using the t() function. This will also be another huge timesaver for PRB reviewers and everyone else.
mlocati replied on at Permalink Reply
mlocati
I just moved this doc tohttp://mlocati.github.io/