Hmmm.... very interesting post by Shaun
This is good in a couple ways - one, it allows me to do development straight from my SVN checkout of Quip (or whatever 3PC), as the files are outside the MODx webroot and are ’checked out’ by SVN. So I can work on Quip, and then immediately commit.
Yes. I wanted to setup my local Git and soon realised that I would have to bring the whole lot of MODx sources under Git which is not ideal. I just want the two directories that make up my component.
I find it easiest to build it outside the file path of MODx, and add 2 System Settings to tell MODx where the files are.
I understand the principle but will these settings be removed once the component is package ready? Are they "development time" settings? I inspected Quip and only found one setting, namely the one provided with the namespace. The other setting wasn’t there and if I remember correctly it is reconstructed using the name space of the component.
i’ve put my 3PCs in a ’workspace’ directory, which is web accessible in my localhost via http://localhost/workspace/
How do I do that? Sorry if I’m ignorant but configuring Apache is at the very bottom of my skill set...
Then my component uses those settings to tell itself where its files are. All the snippets have this as their first line...
I assume that a "snippet" is a piece of PHP code that belongs to the component/CMP. I checked the code for Quip and did not find these lines of code.
Is this post still the proposed way of working?
I work with MAMP, so my MODx install is at : /Applications/MAMP/htdocs/modx
My component is now at: Applications/MAMP/htdocs/modx/ core/components/Tariff and Applications/MAMP/htdocs/modx/assets/components/Tariff
Ideally I want the component under: /Users/MyName/Development/Tariff/server (for all server related sources) and /Users/MyName/Development/Tariff/client (for the client side stuff)
Is that possible? (Sorry for the really long post)