Re: My Elkarte2 Repo
Reply #2 –
Feel free to submit issues. It will help me remember things like that. A lot of the directories will have their own README.md files so I can explain what they do.
As for the commits, it's not really that much. It's just moving files, fixing namespaces, and removing static stuff. It takes a lot of work, but it's not really technical and a lot of it is done with search and replace.
Re: My Elkarte2 Repo
Reply #4 –
ehh...
yeah, merge stuff in would be a pain. In a case like that, I think the best way is to track down all the relevant commits done and port them one by one (or maybe in batches with some scripting trickery).
Re: My Elkarte2 Repo
Reply #5 –
Yeah, I don't think it would work. I am okay with porting changes forward. I will start writing tests for classes soon so you might actually start seeing things that need to be backwards ported.
Re: My Elkarte2 Repo
Reply #8 –
I didn't realize Symfony worked like that. Using Silex it would be more like {add services}, $app->run(), {find route, dispatch to controller}, in the controller find the template to render, return $twig->render($template, [vars]); and then it will return a Response. That's what I was thinking.
Your way makes sense too. Instead of the front controller just pretty much passing through it gets a TemplateResponse (or something) and then render() would be called outside of the controller.