We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 6228
    • 249 Posts
    [rant]
    While I continue to wrap my head around Revolution’s new programming paradigms, xPDO, ExtJS, A zillion MODclasses and documentation still forthcoming, I find the words ’simple’ and ’easy’ to be nails on a chalkboard within the Revolution docs because, quite frankly, I don’t necessarily find some of the illustrations simple or easy. Don’t get me wrong, I think Ryan and Jason are freaking brilliant, borderline insane for giving away this masterpiece for free, and I’m excited for the day when I can call myself a MODx Revolution developer. But ’simple’ and ’easy’ are subjective terms and make me feel like a complete moron when I just don’t ’get it’.
    [/rant]
      lo9on.com

      MODx Evolution/Revolution | Remote Desktop Training | Development
      • 9207 ☆ A M B ☆
      • 2,475 Posts
      Yeah, Revo has a steep learning curve. The abstractions in the architecture allow for some crazy flexibility, but they aren’t intuitively grasped... unless you are a mad psychotic programming genius. Evo was much easier to be sure. I think the trick is having flexible architecture with a simplified presentation for the average user. Hopefully the forthcoming documentation will help make this thing easier to drive.... I’m planning to do a few tutorial videos... just as soon as I can figure out what’s going on heheh
        • 4080
        • 139 Posts
        I gotta be honest. I’m kind of in the same boat, clinging to Evo like a baby and its "binky". I have faith that it’s just a matter of time and all the fundamentals I’ve learned in Evo will translate to Revo as it continues to mature. It is indeed more intimidating I’ve found and the UI still seems so much faster on Evo.
          • 11155
          • 74 Posts
          Add my vote here. I’ve been following modX for several months, reading Evo tutorials for some times and understanding them quite easily. Then it was time to start really building a website; as Revo was the next big thing, I decided to do it using Revo, thinking that all the reading I had on Evo would help me and that the difference couldn’t be that big. Well, big mistake. Every little step I do, I have to learn a whole bunch of new stuff, spend days and days on it, test code line after line if not word after word, and I keep thinking that I could do if faster using Evo. But then I don’t know if I should go back to Evo as I’m not sure if this product will be continued...
            • 25663 MODX Staff
            • 12,272 Posts
            Evo will be maintained for years to come, but our energy will be directed towards Revo which has an exciting future. In fact, the things in the not-too-distant future are truly awesome with Revo. That being said if Evo fits your needs then by all means use it!

            Would love to see an example of something done in Evo that you can’t translate easily into Revo.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 10076
              • 1,024 Posts
              eh front end editor?
                • 11155
                • 74 Posts
                Simple query on custom DB ?
                Custom TVs ? (well, maybe a little bit picky here cause it’s not that easy either in Evo -> http://www.mapledesign.co.uk/projects/modx-tvs/)
                  • 5340
                  • 1,624 Posts
                  @GoustiFruit

                  1. Very easy to use a custom table in a snippet

                  <?php

                  $resultSet = array();
                  $stmt = $modx->query("SELECT * FROM `custom_regions` ORDER BY name ASC");
                  if ($stmt) {
                  $resultSet = $stmt->fetchAll(PDO::FETCH_OBJ);
                  }

                  foreach($resultSet as $r){
                  echo ’<div class="checkboxWrp"><input type="checkbox" name="r-’.$r->id.’" value="’.htmlentities($r->name).’" id="r-’.$r->id.’" /> <label for="r-’.$r->id.’">’ . htmlentities($r->name) .’</label></div>’;
                  }

                  ?>


                  2. http://modxcms.com/forums/index.php?topic=52539.0 and it does’n break the modx install in case you want to upgrade from the official release

                    • 25519
                    • 265 Posts
                    Quote from: rthrash at Oct 29, 2010, 08:18 AM

                    Evo will be maintained for years to come ...
                    That’s quite a relief as, to be honest, I don’t need to upgrade certain sites and also don’t actually want to upgrade some. Reason being that certain clients understandably aren’t be responsive to paying for upgrades which won’t fundamentally improve what they already have.

                    I presume that ongoing Evo support covers only core code, and that snippet/mod writers should update/secure independently of any ’official’ modx core team support. Would this be on or near the mark?

                    A real concern of mine has been that a vulnerability is found for Evo after support has finished, and a client’ site is hacked/broken.
                      • 4080
                      • 139 Posts
                      I personally have a lot of confidence in the MODx team that security issues will definitely be taken care of in updates to Evo as needed. On that note, I believe 1.0.5 is to come out soon. Two versions of MODx--all the more to love I say.

                      :)