I'm testing the new Skinr dev modules. So far everything looks fantastic, and I've run into very few problems.

I decided to try integrating the Fusion Theme base with the new Skinr Dev. Fusion's editing divs show up behind the Ajax editing div, which isn't a large problem because you can usually still click on the ajax div.

I decided I want to keep testing with dev Skinr and Fusion so I made the following quick changes to Fusion's style.css in the core module located at ./fusion/fusion_core/css/style.css

Change lines the Blocks region, lines 1004-1062 to read:

/* Blocks
/-------------------------------------------------------------- */
.block {
  float: left; /* LTR */
  margin-bottom: 1.5em;
  overflow: hidden;
  width: 100%;
}

/* no gutters for blocks in content region */
#content-content .inner {
  margin-left: 0;
  margin-right: 0;
}

/* administrator block edit links */
.block .inner {
  position: relative;
}

.block .fusion-edit {
  display: none;
  padding: 0px 25px;
  position: absolute;
  right: 0;
  text-align: left; /* LTR */
  top: 0;
  z-index: 10;
}

.block:hover > .inner > .fusion-edit {
  display: block;
}

.block .fusion-edit a {
  background-color: #fff;
  border: 0px solid #333;
  display: block;
  float: left;
  outline: 0;
  padding: 2px 2px 2px 6px;
  text-indent: -9999px;
  width: 16px;
}

.block .fusion-edit a:hover {
  background-color: #eee;
  text-decoration: none;
}

.block .fusion-block-config,
.block .fusion-block-edit {
  visibility:hidden;
  background: url(../images/emblem-system.png) center center no-repeat;
}

.block .fusion-edit-menu {
  background: url(../images/text-x-generic-menu.png) center center no-repeat;
}

There are only a few changes in the code above to the div css, but I included the whole block to make it easier to find and replace. The change only hides and moves Fusion's editing divs.

I hope this helps someone else test out all the changes in Skinr-dev version and Fusion! The Skinr-dev has made some significant changes. All seems to be working well other than this minor CSS conflict.

I'm new to Drupal, so I hope you'll forgive me if I committed a faux pas by posting a an issue on an as yet unsupported Skinr dev module. Please move or delete this info if it's in the wrong place. Thanks for understanding!

Comments

stephthegeek’s picture

Thanks very much! It's great to have people checking out the latest version as long as there is an understanding that it's not officially supported yet :)

There are still a few major things shaking out in Skinr 2.x but we will be testing with it very soon and making sure we sort things out for Fusion 1.0.

brassington’s picture

Yes, not supported now, but I figured that at some point we'd need to push toward Skinr's 2.x dev requirements. Hope this helps down the road somewhere - though it's a very insignificant change.

Overall, I'm very impressed. In my sandbox, Fusion is performing remarkably with Skinr's unstable dev module. Truly, this is a testiment to quality of the code coming from both Fusion and Skinr. I'm sure there are bugs, but I've been running them together for several hours and have not noticed any significant problems. From where I am, it's looking like when Skinr's 2.x is finished, Fusion may have little difficulty adapting. At least, here's hoping!

Thanks to all the fusion contributors for your solid and amazingly flexible code!

stephthegeek’s picture

Status: Active » Postponed

Skinr 2.x is indeed working pretty well with Fusion. It has changed a bit since this issue was initially opened :)

One problem is that I'm not sure when 2.x will be the clearly recommended release. Also, its installation is much more involved than 1.x, so it's difficult to require not only a theme and a module to use Fusion themes, but now that module's dependencies and manually installing jquery ui on your server.

Image previews are a tricky one since those are going into Skinr itself but we'll need to check for one version or another so we know if the image previews from Fusion should display or not.

Acquia Slate for Fusion was just released and it has some overriding done of the 2.x styling since the dark background doesn't work great in the popup window.

So all of this is by way of saying that yep, things are working pretty well but we won't be gearing much specifically towards Skinr 2.x for a little while yet.

stephthegeek’s picture

Status: Postponed » Closed (works as designed)