Updated: Comment #N
Problem/Motivation
So this is just a kickstart for Drupal 8 version of Omega 4. I used Twigify
https://drupal.org/sandbox/forest/1974984
This should help in some regard or another to get the ball rolling. This seems to work on the latest dev of drupal 8 and get around to the pages without any glaring mistakes.
Proposed resolution
Depending on how you would like to play this, my thought would be start from scratch and compare with this twiggify patch as a nice diff to spot missing things and maybe also improve twigify's conversions.
Remaining tasks
Review Patch
Open new D8 Branch with a fresh version or the Twiggified version and move this issue to that branch.
Commit a initialized d8 branch.
User interface changes
n/a
API changes
All the D8 ones:P
Comment | File | Size | Author |
---|---|---|---|
#1 | omega-d8.zip | 578.52 KB | joelpittet |
#1 | 2226069-1-omega-d8.patch | 446.3 KB | joelpittet |
Comments
Comment #1
joelpittetOk here is a new one I just rolled up and some conversion notes after twiggify did it's thing.
What I would recommend as it seems a perfectionist's dream base theme (That's why I like it!). Take this, start from scratch though and in each file from a brand new theme. Then use your favourite merge tool to move over chunks at a time to save some time. That way every file and line will get an eyeball to two on them and less old crap to remove later on... 2¢
I'll look at adding some of these annoying details into Twiggify, like the $'s and *_array variables to attributes.
Oh and for shits and giggles, I've uploaded an diff:P
I maybe moved a few things over form core's templates like block.html.twig innards and some of html and page. But a good follow-up for anybody so inclined could be to compare and port more of core's templates into omega replacing what was generated.
Cheers!
Comment #2
fubhy CreditAttribution: fubhy commentedI am going to start working on a Drupal 8 based Project soon and therefor plan to do an initial Omega 8.x-4.x conversion some time in the upcoming 1-2 weeks. Thanks for starting the issue and digging through it. Will get back to you when I start with the conversion (which will be in the near future).
Comment #3
steinmb CreditAttribution: steinmb as a volunteer commentedPerhaps we should close this since we now have a 8.x-5.x -branch?
Comment #4
sahaj CreditAttribution: sahaj commented@steinmb is 8.x-5.x the successor of Omega 4? I should admit that I did not try it yet, but I have some doubt from what I have read. Even if that thread are getting a bit old, I think that it is not clear for many people what are the plan about the D8 version of Omega 4. Does it will change project name? When it will be ready? Will it ever happen? I really think that such information should be visible on the project page. Thanks.
Comment #5
sahaj CreditAttribution: sahaj commentedI mean 'We, as users, need more info'
Comment #6
MacMladen CreditAttribution: MacMladen as a volunteer commentedThe Omega theme was started by Jake Strawn (himerus) - @himerus and the most recent versions (7.x-5.x, 8.x-5.x) are his work.
At some time after huge success of 7.x-3.x version, the next generation of Omega (7.x-4.x) was conceived and coded by Sebastian Siemssen (fubhy) - @thefubhy and Matt Smith (splatio) - @splatio_
After some dispute Jake took back over Omega development so both new Omega versions (7.x-5.x, 8.x-5.x) probably have nothing in common with (7.x-4.x) and are not the successor of Omega 4.
The successor to (7.x-4.x) is new project Khan so all the questions about that should be posted there. Truth to be told, there is not much activity there, since.
So if you wish to make some sort of continuation of current 4.4 code base to D8, probably you will have to do it yourself. Personally, I do not think it will make much sense as the differences between D7 and D8 would not leave much in common.