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

CommentFileSizeAuthor
#1 omega-d8.zip578.52 KBjoelpittet
#1 2226069-1-omega-d8.patch446.3 KBjoelpittet
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

joelpittet’s picture

FileSize
446.3 KB
578.52 KB

Ok here is a new one I just rolled up and some conversion notes after twiggify did it's thing.

Removed: variable_get('clean_url', 0)
No longer in d8.
.info = .info.yml
https://drupal.org/node/1935708
variable_get('js_gzip_compression', TRUE) 
\Drupal::config('system.performance')->get('js.gzip')
template.php
omega.theme
variable_get('admin_theme', $GLOBALS['theme'])
\Drupal::config('system.theme')->get('admin')
cache_set()/_get()
$cache = \Drupal::cache();
$cache->set()/->get()
Replace theme() with drupal_render().
I cheated on one and used _theme()
drupal_add_js() drupal_add_css()
#attached + drupal_render()
drupal_get_js() drupal_get_css()
new RenderWrapper('drupal_get_*') 
Seriously hate his abomination... I made it but stop gap to get rid of the process layer...
drupal_array_merge_deep_array()
NestedArray::mergeDeepArray
drupal_get_path_alias() 
$title = \Drupal::service('path.alias_manager')->getPathAlias($path);
attributes_array
attributes
classes_array
attributes.class
row_attributes
row.attributes
column_attributes
column.attributes
field_attributes
field.attributes
For these I just removed the views preprocess files.
$'s in *.twig.html removed.
$block = $variables['elements']['#block']->toArray();
$variables['block']->module
$variables['configuration']['module']
$variables['block']->delta
$variables['elements']['#plugin_id']
variable_get('drupal_js_version_query_string')
was removed from core.
Removed omega_initialize_attributes() and omega_cleanup_attributes()
More or less done in d8
No more process functions in d8
No more poll or overlay modules in d8
CSS
element-invisible
visually-hidden
element-focusable
focusable
current_path()
\Drupal::languageManager()->getDefaultLanguage()
GRDDL removed in d8
https://drupal.org/node/1052354
Added these for things I didn't know how to deal with.
// @todo Convert to d8.

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!

fubhy’s picture

I 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).

steinmb’s picture

Status: Needs review » Postponed (maintainer needs more info)

Perhaps we should close this since we now have a 8.x-5.x -branch?

sahaj’s picture

@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.

sahaj’s picture

Status: Postponed (maintainer needs more info) » Active

I mean 'We, as users, need more info'

MacMladen’s picture

The 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.