Bringing Evo back to life again

• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #241, 14 years, 5 months ago

  We have improved the code so that it can provide for you.
  Would you wait to further development?
  If it advances as at now, it becomes impossible for us to offer anything.
  The pilot edition is due to translate Japanese into English and to be made.
  I want you to wait for a while.
  
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #242, 14 years, 5 months ago

  We have proposed many improvements through GitHub until now.
  However, they have continued up to now, while not being adopted by them.
  We are not necessarily making what can be used only in Japan.
  
• • 
  • 222 Posts
  Stefanie Reply #243, 14 years, 5 months ago

  Hi yama,
  
  lets see how it works and thank you for the work.
  
  Can you do a fork of the Evolution from my github account at https://github.com/sjstoelting/evolution?
  
  There is a branch called 1.1.dev, please use this branch to submit your code through a pull request. From that branch we can get it in our personal branches to go on with development. In addition I create a pre alphha download for those, who want to test.
  
  As my Japanese knowledge is near zero, I would like to have the English translation availble.
  Gone away and found a better place to stay
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #244, 14 years, 5 months ago

  Very thanks, Stefanie.
  
  A request cannot be sent to your repository.
  It is because there is too much difference.
  Much fine improvement was made. Parser, chache and other have improved.
  
  Difference increased so far because a development team did not correspond, 2 year.
  It did not look back upon our activity. While regrettable.
  
  First, I want you to see our work.
  If it can do, I will want a base to carry out this.
  
  Since it is unfamiliar English, it cannot say well...
  
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #245, 14 years, 5 months ago

  Quote from: Stefanie at Apr 10, 2012, 11:29 PM

  I would like to have the English translation availble.

  ...Now, I noticed your text. OK, I make the English edition, in several days.
  I make the picture for explanation, also.
  
• • 
  • 222 Posts
  Stefanie Reply #246, 14 years, 5 months ago

  Quote from: yama at Apr 10, 2012, 11:39 PM

  Very thanks, Stefanie.
  
  A request cannot be sent to your repository.
  It is because there is too much difference.
  Much fine improvement was made. Parser, chache and other have improved.
  
  Difference increased so far because a development team did not correspond, 2 year.
  It did not look back upon our activity. While regrettable.
  
  First, I want you to see our work.
  If it can do, I will want a base to carry out this.
  
  Since it is unfamiliar English, it cannot say well...
  

  Then fork my github Evolution and add a new branch. Afterwards make a pull on this branch. That would give us the chance to merge the code, I personally do not want to work on things, that other people already solved.
  
  The target should be to bring all of our work together and btanching and merging will help us
  Gone away and found a better place to stay
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #247, 14 years, 5 months ago

  It is very difficult.
  We have improved thousands of places.
  Isn't there any solution excellent in others?
  
• • ☆ A M B ☆
  • 1,231 Posts
  yama Reply #248, 14 years, 5 months ago

  https://github.com/modxcms-jp/evolution-jp/commits/develop
  This is us activity.
  I consider how to contribute efficiently.
  
• • 
  • 898 Posts
  chucktrukk Reply #249, 14 years, 5 months ago

  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?
  
  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.
  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
• • 
  • 222 Posts
  Stefanie Reply #250, 14 years, 5 months ago

  Quote from: yama at Apr 11, 2012, 01:54 AM

  https://github.com/modxcms-jp/evolution-jp/commits/develop
  This is us activity.
  I consider how to contribute efficiently.
  

  I took a fast look through that repository, the Japanese community has done a lot of changes on the code base. But I think with some work it should be possible, to bring the current development and the work already done be the Japanese community together again.
  
  When I'm ready with the implementation of ezSQL and the unit test on DBAPI and DocumentParser I would like to compare both sources and try to bring them together. But I think I need a lot of your help, because you know much more about the changes and that should help me to understand the ideas. I'll send you a private message, to get an appointment to work on the code together and to chat about the changes, if you would like to help that way.
  
  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?
  
  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.

  
  

  
  
  • jQuery Manager
  • New Manager design
  • New demo layout
  • ezSQL as database classes to get Evo working with more RDBMS
  • Unit test
  • PHP5
  • Cache improvement

  
  These are some of the things we are working on.
  Every help is welcome
  
  We started with a fork of the MODX Evolution sources on github, with this fork we can do pull requests to the original code base. That way we see a chance to get all the changes back into Evolution.
  
  The basis is the fork on github done by me. The development branch is 1.1.dev. Fork evo from that repository, add your code, and start pull requests.
  Gone away and found a better place to stay

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