New Front End Contributor Requirements for 2.3

Quote from: sottwell at Sep 08, 2013, 12:57 PM

Indeed. Lots to do. Controllers to connect. Styling to correct. But it's going to be pretty awesome.

Media Browsers to finish and the list goes on. I think one of the biggest improvements is the uberbar. It will be so much easier to quickly edit Elements or really find anything.

I'm hoping for some improvements to Form Customization. I'm hoping to be able to hide TVs by resource ID. It's a nuisance to have to have multiple otherwise identical templates just to organize TVs. Or have to go through some kind of convoluted process to move them out of the TV tab and hide the TV tab, which may well be wanted for other purposes.

Quote from: sottwell at Sep 08, 2013, 03:56 PM

I'm hoping for some improvements to Form Customization. I'm hoping to be able to hide TVs by resource ID. It's a nuisance to have to have multiple otherwise identical templates just to organize TVs. Or have to go through some kind of convoluted process to move them out of the TV tab and hide the TV tab, which may well be wanted for other purposes.

I'll second that Susan. Very counter productive.

Quote from: easylancer at Sep 07, 2013, 08:06 AM

[s]I am not sure of the relevance of the Asciify stuff, but if its purely for adding that do not edit at the top of files which increases the filesize, it kinda defeats the purpose. I would propose removing it, if its purely only for that.

Removed the asciify header in favor of keeping the 'contributor guestbook' at the top.
https://raw.github.com/jpdevries/revolution/grunt/manager/templates/default/css/index.css

Remember to sign if you contribute!
https://github.com/jpdevries/revolution/blob/grunt/_build/templates/default/sass/index.scss

Quote from: jonleverrier at Sep 08, 2013, 08:03 PM

Quote from: sottwell at Sep 08, 2013, 03:56 PM

I'm hoping for some improvements to Form Customization. I'm hoping to be able to hide TVs by resource ID. It's a nuisance to have to have multiple otherwise identical templates just to organize TVs. Or have to go through some kind of convoluted process to move them out of the TV tab and hide the TV tab, which may well be wanted for other purposes.

I'll second that Susan. Very counter productive.

Thanks for the feedback, but this is a bit off-topic. It would be better to open up a thread about features you would like to see in future versions of MODX for this kind of stuff.

Back to the topic at hand, I've started working on an automator for creating custom (non-default) Manager themes. Nothing much more than playing around at this point, and will be much more useful when the Sass has been abstracted to separate layout from style. Idea is, you runs this command, answer 11 questions for things like theme name, author info and a few settings like whether you will be using Sass or Less, and it creates a scaffold of all the files you need to stub out your theme.

Installation
If you haven't already done so, install grunt-init.
More on grunt-init at http://gruntjs.com/project-scaffolding


Clone Theme Automator
Linux/Mac Users


Windows Users


Usage
cd to an empty directory then

Quote from: dinocorn at Sep 08, 2013, 08:44 PM

Quote from: easylancer at Sep 07, 2013, 08:06 AM

[s]I am not sure of the relevance of the Asciify stuff, but if its purely for adding that do not edit at the top of files which increases the filesize, it kinda defeats the purpose. I would propose removing it, if its purely only for that.

Removed the asciify header in favor of keeping the 'contributor guestbook' at the top.
https://raw.github.com/jpdevries/revolution/grunt/manager/templates/default/css/index.css

Remember to sign if you contribute!
https://github.com/jpdevries/revolution/blob/grunt/_build/templates/default/sass/index.scss

Sorry for being a pest JP, but I think this is as bad as the ASCII stuff, anything that increases filesize that isn't relevant to CSS shouldn't be included in any CSS files. I think a copyright notice for MODX alone should be in any css file. We should move the contributors to a README file in the root of the MODX project. That way all users can add their name to it without worrying about increase of filesize of anything loaded by the browser.

Quote from: dinocorn at Sep 09, 2013, 01:45 AM

Back to the topic at hand, I've started working on an automator for creating custom (non-default) Manager themes. Nothing much more than playing around at this point, and will be much more useful when the Sass has been abstracted to separate layout from style. Idea is, you runs this command, answer 11 questions for things like theme name, author info and a few settings like whether you will be using Sass or Less, and it creates a scaffold of all the files you need to stub out your theme.

Installation
If you haven't already done so, install grunt-init.
More on grunt-init at http://gruntjs.com/project-scaffolding

npm install -g grunt-init

Clone Theme Automator
Linux/Mac Users

git clone [email protected]:jpdevries/grunt-modx-manager-theme.git ~/.grunt-init/modx-manager-theme

Windows Users

git clone [email protected]:jpdevries/grunt-modx-manager-theme.git %USERPROFILE%/.grunt-init/modx-manager-theme

Usage
cd to an empty directory then

grunt-init modx-manager-theme

This is beautiful (my geekyness kicking in), I shall give it a test run later on today and let you know how it goes. I will try and catch up with you later on Skype to talk about the dependencies issue and the Vagrant setup I am working on.

Quote from: easylancer at Sep 09, 2013, 01:56 AM

Quote from: dinocorn at Sep 08, 2013, 08:44 PM

Quote from: easylancer at Sep 07, 2013, 08:06 AM

[s]I am not sure of the relevance of the Asciify stuff, but if its purely for adding that do not edit at the top of files which increases the filesize, it kinda defeats the purpose. I would propose removing it, if its purely only for that.

Removed the asciify header in favor of keeping the 'contributor guestbook' at the top.
https://raw.github.com/jpdevries/revolution/grunt/manager/templates/default/css/index.css

Remember to sign if you contribute!
https://github.com/jpdevries/revolution/blob/grunt/_build/templates/default/sass/index.scss

Sorry for being a pest JP, but I think this is as bad as the ASCII stuff, anything that increases filesize that isn't relevant to CSS shouldn't be included in any CSS files. I think a copyright notice for MODX alone should be in any css file. We should move the contributors to a README file in the root of the MODX project. That way all users can add their name to it without worrying about increase of filesize of anything loaded by the browser.

It'll ultimately just be a copy right notice once I figured out the one to use. I honestly don't know a thing about them. cssmin is configured to only include the first 'special comment' so as long as it is the first one in index.scss it will be all that gets printed.

Hi. Really nice initiative !
Is there a list of todos/ideas/guidelines/placetodiscuss for this default manager ?
My local setup is running now and i started to tweak _scss files a bit.. it works well and i see a lot to clean there.. but i don't know how to contribute with github... I think a short list of commands you use for pull/commit the theme save me a lot of time..