Management screen in 2.3.0

One thing I've always thought of is to have a separate clear cache button. The rationale is that in my normal development cycle, I'm using a bunch of static elements and resources, and my real work is in the code editor, then uploading to the server, and then going into the manager and clicking "Clear Cache".

If nothing were done about this, my complaints would win a "First World Problems" award (i.e. it wouldn't really be an issue), but I'm wondering if anyone else shares the same thoughts.

Personally I build all the templates outside of MODX ( I don't even install it until I have everything built ), Then I move all the templates over to MODX creating all the chunks / TV's etc so I have very little use for a clear cache button, however that said, thats just the way I choose to build and others may have a need for this so yeh a good idea.

Quote from: stalemate at Nov 16, 2013, 10:52 AM

@everyone:
One thing I've always thought of is to have a separate clear cache button. The rationale is that in my normal development cycle, I'm using a bunch of static elements and resources, and my real work is in the code editor, then uploading to the server, and then going into the manager and clicking "Clear Cache".

Tom, when you are developing, it isn't justifiable to turn off the cache? So you turn it on when in production, I think it would improve your development cycle. (mainly if you develop using localhost)

Quote from: stalemate at Nov 16, 2013, 10:52 AM

@pdincubus:
@everyone:
One thing I've always thought of is to have a separate clear cache button. The rationale is that in my normal development cycle, I'm using a bunch of static elements and resources, and my real work is in the code editor, then uploading to the server, and then going into the manager and clicking "Clear Cache".

FYI - It's *really* easy to create a Top Menu button that would clear the Revolution cache with a single click. It's even easier to move that existing menu option to the main Top Menu -- just drag it there in the right-hand tree in Manager -> Actions.

Quote from: danielmiguel at Nov 21, 2013, 07:45 PM

Tom, when you are developing, it isn't justifiable to turn off the cache? So you turn it on when in production, I think it would improve your development cycle. (mainly if you develop using localhost)

Hi Daniel,

I guess it does make sense. I'm just worried that at some point in time I would worry about remembering to turn on caching again. In my current project I have 114 resources, and I see that 4 of them are uncached. You do raise a really good point.

Quote from: BobRay at Nov 21, 2013, 09:38 PM

FYI - It's *really* easy to create a Top Menu button that would clear the Revolution cache with a single click. It's even easier to move that existing menu option to the main Top Menu -- just drag it there in the right-hand tree in Manager -> Actions.

Thanks Bob! I took the second option, and I sat there and started laughing: wow that was easy! Thanks for the tip!

Regards,
Tom

I'm glad I could help.

Back to the subject at hand. If anyone is interested in using a tool that bootstraps creating a custom manager there, this may be helpful:
http://devries.jp/yomonger

Yomonger is a Yeoman Generator that automates the build of a custom MODX Manager theme. You'll be asked things like what to call it, if you'd like to use a CSS preprocessor such as Sass, if you'd like to start off with the default layout .tpl files and images, if you'd like to include the source Sass styles of the default theme, and some author related information.
You'll then have a custom them scaffolded to be much like the default theme. That means it will be set up as a grunt project and able to use the various Grunt Commands.
https://github.com/modxcms/revolution/tree/develop/_build/templates/default#grunt-commands

You should first be fairly familiar with the tools mentioned in the Contribution Guide of for the MODX core themes.
https://github.com/modxcms/revolution/tree/develop/_build/templates/default

You'll need to have Node.js and it may be worth following the Installation instructions mentioned above.