We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 21838
    • 284 Posts
    Okay, I’ve just released MODX-Boilerplate v1.5 today.
    This release features some minor fixes and improvements to the Revolution version: https://github.com/smooth-graphics/modx-boilerplate/issues?milestone=1&sort=created&direction=desc&_pjax=true&state=closed

    This features also the first commit of a MODX Evolution version: https://github.com/smooth-graphics/modx-boilerplate/tree/evo-master
    I just want to note that I’m not actively developing on MODX Evolution any more but it has been (quickly) tested by hunterhig (thank you again!) so I hope it works fine. If not or if you have improvements, please file a bug with label "evo" or "revo".
      MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)
      • 14822
      • 61 Posts
      Tnx men!!!!!!!
        • 12147
        • 182 Posts
        Novolo, Thanks again very much for Evolutionizing your project! I hope you continue to develop Revo and Evo both. I think they are each for different purposes and environments. Many of the websites I build are perfectly suited to Evo, while Revo might be overkill.

        I am noisy about continuing support for and attention to Evo, and appreciate anyone who notices it’s still a major part of MODx. grin

        From now, I think to release it as free with commercial support available and with commercial themes to buy for the framework. This means, I can get revenue from users who won’t do much work but means anybody can use the framework for free and profits from paying users. Hope this is okay?
        This is terrific! laugh
          • 21838
          • 284 Posts
          Quote from: wlhh at May 19, 2011, 05:29 PM

          Novolo, Thanks again very much for Evolutionizing your project! I hope you continue to develop Revo and Evo both. I think they are each for different purposes and environments. Many of the websites I build are perfectly suited to Evo, while Revo might be overkill.
          I Hope i find the Time to do that. It’s still some more work for me As i have to Port it all the Time from revo Version to evo Version. But i already mentioned in the issue tracker that i will continue support of evo..
            MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)
            • 21838
            • 284 Posts
            Sorry for duplicate post but some announcement you should know:

            I most probably won’t create a package for my MODX-Boilerplate.

            Providing a package would need much more delay for changes in code as it has to packed by me, approved by MODX-team and then updated by user.
            I’ve seen this at HTML5Boilerplate. There you have version 1.0 as download which currently is totally out of state. If you look at the github repo you’ll see that it’s better to read what they change and get your code from there.
            It also would be very problematic with updates on an existing customized setup as it would overwrite all custom settings.
            Another reason is that currently there are changes about every 1-3weeks and they’re major. So I’d have to provide updates every 2 weeks. This would be annoying for users and me and the MODX-team.

            So please be gentle but I don’t see a reason why and how this could go into a package.
              MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)
              • 1169
              • 312 Posts
              @novolo I have recently ported a template to MODX and used less.js to change the color scheme from a site variable.
              I was wondering about package management. You seem to suggest it will be more trouble than it is worth. I am using github at present with a simple README file for explanation of installation procedures. Do you feel this is the best place to keep code.

              I do not see that I will be updating this package as often as you, as once completed will only update errors wink
                DEVELOPMENT ENV:- Ubuntu 12.04 | MODx Revolution 2.2.8 | LAMP 2i Apache 2.2.22 | Php 5.3.10 | Mysql 5.5.31 MySQL client version: 5.5.31
                • 21838
                • 284 Posts
                Quote from: allanb at May 20, 2011, 07:31 AM

                @novolo I have recently ported a template to MODX and used less.js to change the color scheme from a site variable.
                I was wondering about package management. You seem to suggest it will be more trouble than it is worth. I am using github at present with a simple README file for explanation of installation procedures. Do you feel this is the best place to keep code.

                I do not see that I will be updating this package as often as you, as once completed will only update errors wink

                Hi,
                so you see it’s a huge difference between a template framework (I’m offering) and a ready-to-use template.
                So the only thing where it makes sense to offer a package for me is when version2 is available with themes (=full templates, ready-to-use).
                  MODX Free Template Base: MODX-Boilerplate | my blog (lots of MODX stuff) | my gitHub (translations) | MODX User Groups Germany (Facebook)
                  • 25663 MODX Staff
                  • 12,272 Posts
                  If you’ve submitted packages previously that have been approved, there is no approval delay ... it’s published automatically. There may be a threshold but that shouldn’t be a reason to keep you from creating Packages. Packman makes it incredibly straightforward.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 1169
                    • 312 Posts
                    @novolo
                    Thanks for your reply I see I am not in the same position as you but thanks for your prompt reply.

                    @rthrash
                    I will look into packman. My only concern was that when installing for eg demo site this wipes out existing site content as I am only adding a template element, chunks, snippets and a few files to the system.
                      DEVELOPMENT ENV:- Ubuntu 12.04 | MODx Revolution 2.2.8 | LAMP 2i Apache 2.2.22 | Php 5.3.10 | Mysql 5.5.31 MySQL client version: 5.5.31
                      • 29597 ☆ A M B ☆
                      • 350 Posts
                      A question about JS loading via yepnope..

                      I am using the nice Slides jQuery slider http://slidesjs.com/ on a theme based on the MODx Boilerplate.
                      If I load the JS via the yepnope in the footer (using the plugins.js and scripts.js) the images in the slider are all displayed for a short time before the slider becomes "active".

                      If I place the JS code (jquery.min.js, jquery.easing.1.3.js and slides.min.jquery.js) in the header all works fine.

                      - How can I keep using yepnope in the footer and bypass this problem?

                      - Is placing JS in the footer really that mutch better?

                      This works,
                      Code in header:
                      <script src="[[++site_url]]assets/templates/main/js/libs/modernizr.min.js"></script>
                      <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js"></script>
                      <script src="http://gsgd.co.uk/sandbox/jquery/easing/jquery.easing.1.3.js"></script>
                      <script src="[[++site_url]]assets/templates/main/js/libs/slides.min.jquery.js"></script>
                      <script>
                      	$(function(){
                      		$("#slides").slides({
                      			preload: true,
                      			preloadImage: '/images/site/loading.gif',
                      			play: 5000,
                      			pause: 2500,
                      			hoverPause: true
                      		});
                      	});
                      </script>
                      


                      This doen not work nicely
                      Code in footer:
                      <script>
                      yepnope([{
                      	load: '//code.jquery.com/jquery-1.6.min.js',
                      	complete: function () {
                      		if (!window.jQuery) {
                      			yepnope('[[++base_url]]assets/templates/main/js/libs/jquery-1.6.min.js');
                      		}
                      	}
                      }, {
                      	load: ['[[++base_url]]assets/templates/main/js/plugins.js', '[[++base_url]]assets/templates/main/js/scripts.js'  ]
                      }]);
                      </script>
                      

                      With in plugins.js the jquery.easing.1.3.js and slides.min.jquery.js code.
                      In scripts.js:
                      $(function(){
                      	$("#slides").slides({
                      		preload: true,
                      		preloadImage: '../images/site/loading.gif',
                      		play: 5000,
                      		pause: 2500,
                      		hoverPause: true
                      	});
                      });
                      


                      EDIT:
                      It is not the position of the code... placing the yepnope in the header does not fix this problem, Plaing this:
                      <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js"></script>
                      <script src="http://gsgd.co.uk/sandbox/jquery/easing/jquery.easing.1.3.js"></script>
                      <script src="[[++site_url]]assets/templates/main/js/libs/slides.min.jquery.js"></script>
                      <script>
                      	$(function(){
                      		$("#slides").slides({
                      			preload: true,
                      			preloadImage: '/images/site/loading.gif',
                      			play: 5000,
                      			pause: 2500,
                      			hoverPause: true
                      		});
                      	});
                      </script>
                      


                      Does work...
                        MODX Ambassador (NL) | Responsive web design specialist, developer & speaker
                        DESIGNfromWITHIN, MPThemes and Any Screen Size
                        Follow me on Twitter | Read my blog | My code on GitHub