Bringing Evo back to life again

• • 
  • 1,098 Posts
  microcipcip Reply #251, 14 years, 5 months ago

  Quote from: chucktrukk at Apr 11, 2012, 01:25 PM

  I just found this thread. I think this 25 page thread says: let's work together to make Evo up to date. Is that right?.

  
  That's right!
  
  Quote from: chucktrukk at Apr 11, 2012, 01:25 PM

  
  I've been working on Evo on a private branch for the last 2 years (and created the current custom TV functionality). And am really interested in seeing Evo grow.
  
  Can someone post a tldr summary.

  
  I am a Web Designer so I can't go much into details, but from my understanding, this is what has been done so far:
  
  - @Stefanie is working on making Evolution support other databases
  
  - @Sottwell is working on moving the manager template plus login in one single folder, making all manager pages work with placeholders, and probably much more.
  
  - @Yama and the Japanese community have a working solution for the limit of 5000 resources, and hundred of improvements.
  
  - @Breezer is working on implementing jQuery
  
  - There are a lot of improvements in the russian community too
  
  - I have been working on the design, see the details on this thread: https://forums.modx.com/thread/?thread=75556&page=1 [ed. note: microcipcip last edited this post 14 years, 5 months ago.]
  Jertix.org -> Web Design & Development, Motion Graphics | Follow me on Twitter | MODx Tutorials (in Italiano) | MODx Snippets (English)
• • 
  • 898 Posts
  chucktrukk Reply #252, 14 years, 5 months ago

  Wow, that is awesome.
  
  The 5000 doc limit on cacheing is huge. Can't wait to see how they did it.
  
  Also, wow the Japanese community has been making updates for 2 years. That's amazing.
  
  Calendar TV: use jquery datetime. Works great. http://trentrichardson.com/examples/timepicker/
  
  I also prefer ezSQL. Great choice
  
  Yama is a hero. He's amazing. Always working.
  Also, sharkbait is a great dev. He's written some great addons and posts
  
  Stefanie
  How did you do this?
  You've got a rocket with that, I did it for example with some shop pages (round about 250,000 pages answering time less than a second included price calculation for B2B).
  
  https://forums.modx.com/thread/74766/bringing-evo-back-to-life-again?page=22#dis-post-419296
  Properties for TVs, particularly for custom TVs, is a priority for me.
  Very huge
  Chuck the Trukk
  ProWebscape.com :: Nashville-WebDesign.com
  - - - - - - - -
  What are TV's? Here's some info below.
  http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
  http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008
• • ☆ A M B ☆
  • 24,524 Posts
  sottwell Reply #253, 14 years, 5 months ago

  Ok. I need to start over with the GitHub thing. I've made a number of relatively minor improvements (in my opionion) but I have no idea how to offer them to the main source (i. e. Stefanie's repository).
  
  This looks helpful http://www.eqqon.com/index.php/Collaborative_Github_Workflow
  
  
  Studying MODX in the desert - http://sottwell.com
  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
  Join the Slack Community - http://modx.org
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #254, 14 years, 5 months ago

  How to use GitHub understands...
  
  Can't a project be advanced after taking in the improvement of a Japanese edition and the Russia edition?
  If it is possible, I will try the pull request each functions.
  
  Since order is reverse, we need to do very big restart...
  (For example, PHP5 and ezSQL)
  
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #255, 14 years, 5 months ago

  I want you to wait for PHP5 and ezSQL. However, I certainly tackle later.
• • 
  • 2,314 Posts
  anonymized-26931 Reply #256, 14 years, 5 months ago

  Also, sharkbait is a great dev. He's written some great addons

  oh, thanks, but i wouldn't say I'm a dev, more like a Hunter & Gatherer
• • 
  • 898 Posts
  chucktrukk Reply #257, 14 years, 5 months ago

  Susan,
  
  This online book is where I learned git: http://progit.org/book/
  
  Yama had a good idea. Could we apply Stefanie's changes on top of their japanese 1.6 branch.
  - The caching alone could be worth it.
  Chuck the Trukk
  ProWebscape.com :: Nashville-WebDesign.com
  - - - - - - - -
  What are TV's? Here's some info below.
  http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
  http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008
• • ☆ A M B ☆
  • 24,524 Posts
  sottwell Reply #258, 14 years, 5 months ago

  Thank you!
  Studying MODX in the desert - http://sottwell.com
  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
  Join the Slack Community - http://modx.org
• • 
  • 222 Posts
  Stefanie Reply #259, 14 years, 5 months ago

  The github thing is easy, in the end.
  
  Susan, after you pushed your changes to github
  

  git push

  
  Open the github site with your branch https://github.com/sottwell/evolution/tree/sottwell-dev
  There is a button on the right called "Pull Request". On the following site you just have to send the pull request, the message box is for information, when you send an unrequested change of code.
  
  That's it.
  
  I take the pull request and merge it into the 1.1.dev branch, that is all I have to do.
  
  The other way that the description said, is for developing in a team as organisation. I didn't start a new organisation for the Evo changes, because in this way, we can send the changes directly via a pull request back to the MODX repositories and all commits with the commit information stay intact.
  
  

  ---

  
  The merger with the Japanese community should also go in this way, that is, why I asked yama to do all those changes together. We create a new branch on my sources and start to merge the changes of the Japanese community into this branch. This way we can test this changes, without touching the ongoing development.
  After we got all that changes ready to go, we merge that 1.1.dev.japanese branch into the main 1.1.dev branch.
  
  For those, who worked with Subversion: Branching and merging does work that easy with git. It is not such a PITA as in Subversion.
  
  Then we should think about creating a community 1.1 Alpha version and pack it all together. At that point we should create pull request to the original sources.
  
  

  ---

  
  @chucktrukk:
  The shop was a job, I don't have any right to code. But it was database and application design. The articles where created in one MODX document by a snippet call, that called some classes, and so on.
  
  For your interest, I've rewritten ezSQL to make PHP5 compatible, done unit tests, and created the class documentation with PHPDocument. I've send a pull request to the original repository, but haven't got an answer by today. You find that changes in a branch at https://github.com/sjstoelting/ezSQL/tree/ezSQL-3.0.
  Gone away and found a better place to stay
• • 
  • 368 Posts
  polrbear Reply #260, 14 years, 5 months ago

  Quote from: whistlemaker at Apr 06, 2012, 02:25 PM

  as I watch the 'ftp queued files' list count down from over 4000 and wait for rather large upload to finish...

  
  Just a thought as I'm reading here... don't you zip before uploading? Trying to upload Revo (or any CMS) without zipping it first is a nightmare.
  Jason

This discussion is closed to further replies. Keep calm and carry on.