At this moment, is clippercms the same as evo 1.0.7 
I totally agree on continuing coding but not only for clippercms but also for Evo. Or will plugins work for both of them ?
Clipper has its own site and its own forum at
http://www.clippercms.com/forum/, where all your questions will be answered and all your wishes will come true (maybe).
The current release is designed to be compatible with existing MODX Evo sites. It's expected the key standard extras such as Ditto and eForm will continue development under new names (e.g. Ditto is now List), but with internal translation so you don't have to immediately edit all the calls. I've tested a local Clipper install with a copy of my pogwatch.com site, which uses PHx, Jot, loads of Ditto calls with a wide range of parameters, and custom snippets and plugins, without headaches.
Some core code has been redeveloped already: cacheing of nested elements makes more sense, PHP 5.4 won't cause grief, and a large proportion of the work to centralize database functions using mysql_ in place of mysqli_ has been done. This is future-proofing, it's a lot of work. Probably the point at which Evo becomes unusable is when newer versions of PHP become standard on people's hosts. As far as I know, nobody is planning to do this kind of work on MODX Evo itself.
Looking forward to your company at the above address!
;) KP
☆ A M B ☆
)