In several ongoing issues the idea of a roadmap has been brought up. Can we discuss that and make it here?

I think the goals of Skinr are understood, but how do we get there from where we are?

Comments

coltrane’s picture

coltrane
he/him
commented

Part of my difficulty in jumping into existing issues and the code is that I don't feel I confidently understand where Skinr has come from in the 2.x branch, and what the current state of the code is at compared to Skinr 2.x's goals.

Perhaps it would be useful to list out some of the current issues and goals, to start?

jacine’s picture

jacine
she/her
Location New York
commented

Here is a summary of the issues we discussed on the phone:

Functionality issues

  • Status of skins per theme

    Issue: #1050472: Override skin status per theme
    Summary: We need to figure out whether being able to control the status of skins per theme is a feature that we need. This also affects the work we need to do here #984402: Add "details" link that shows preview of rendered skin widget and additional info.

  • Third party forms

    Issue: #1044222: Remove skin configuration functionality from third-party forms
    Summary: We need to remove all the third party forms and special handling. This will have an impact on how Skinr settings can be applied. It means that the skinr settings form will no longer be available when configuring a block or a node type. Instead we'll use a single form that will be accessible via contextual links. Since contextual links are not fully accessible, and can also be disabled we need a fallback. We need to discuss using the Rules UI for everything, and obviously stop using "Rules" to refer to it.

  • Fix performance problems

    Issue:#1029058: [META ISSUE] Change skin configuration:
    Summary: Bullet points #2 and #3 of this comment go into some detail about what needs to be done: . Using the Context module was also brought up here. The consensus is that it will add unnecessary complexities, dependencies and could cause UI problems, even if it's just users wanting to be able to use Context UI for Skinr. More research is needed here.

  • Visibility options needs a proper D7 import

    Issue: #943068: Skinr rule visibility implementation needs to be updated properly
    Summary: This was never properly ported. There is code in the issue that @ericduran wrote that does the conversion to vertical tabs and adds the necessary jQuery, but the functionality itself was horrible broken last time I checked. The summary of what I found is here.

UI and other issues that should be done for a point release:

ogi’s picture

ogi commented

subscribe

R.J. Steinert’s picture

R.J. Steinert commented

subscribe

bennyzen’s picture

bennyzen commented

subscribe

Vc Developer’s picture

Vc Developer commented

subscribe

bryancasler’s picture

bryancasler commented

subscribe

bryancasler’s picture

bryancasler commented

subscribe

g76’s picture

g76 commented

subscribe

generalconsensus’s picture

generalconsensus commented

subscribe

rickmanelius’s picture

rickmanelius commented

Subscribe

jurriaanroelofs’s picture

jurriaanroelofs commented

subscribe

rickmanelius’s picture

rickmanelius commented

More importantly @Jacine
Has anything changed in the roadmap since DrupalCon?
I'm growing to love skinr in drupal6 and can't wait to get my hands on it for Drupal 7. Part of our skill building time in my company is being spent learning this... so if there are areas where you need feedback and/or assistance, I can provide what my skill level allows!

deggertsen’s picture

deggertsen commented

subscribe

drupalicious’s picture

drupalicious commented

subscribe

g76’s picture

g76 commented

Hi,
I just wanted to assure you that although the roadmap has not been updated it's definitely no indicator that things are coming along. I am not a coder, so I have not been able to get involved with development, but there is so much being done by those involved, it's just behind the scenes.

You can take a look at the issue queue: http://drupal.org/project/issues/skinr?text=&status=Open&priorities=All&...

This will give you more of a feel of the status of things. I am very excited as well, so I share your anticipation!

shwx’s picture

shwx commented

subscribe

pitxels’s picture

pitxels commented

I don't know what is the priority here, but I would love to have skinr showing the blocks UI options, instead of having to insert classes manually.

You guys should consider fixing the bugs for making the module work with the basics, and then working on improvements.

hadi farnoud’s picture

hadi farnoud commented

we definitely need to plan better. I halted my project for skinr for now, so I do whatever I can to push this forward as Skinr is very important module for D7 upgrade (at least for most of us)

Jackinloadup’s picture

Jackinloadup commented

subscribe

BenK’s picture

BenK commented

Subscribing

joomlerrostov’s picture

joomlerrostov commented

Subscribing. So, what is the module status for D7 for now? Can we use it?

Nordtof’s picture

Nordtof commented

nope. I just tried today.

it has only "css file support" on my favorite theme.

I still cant use the dropmenus for change the theme details.

I belive D7 is still too primitive to use, without theese modules, it is simply useless for detailed web sites.

moonray’s picture

moonray commented

If you're a developer familiar with low-level Drupal 7 APIs, Skinr could use your help. Anyone else, DO NOT USE IT.

There are a lot of patches that need reviews or tweaks that would get it ready to use (and there are still *major* performance problems).

The issues to check:

jaiiali’s picture

jaiiali commented

Subscribing

bmx269’s picture

bmx269 commented

Which GIT version is the current HEAD?

coltrane’s picture

coltrane
he/him
commented

@bmx269 master is the D7 2.x compatible HEAD version in Git

jeffwidman’s picture

jeffwidman commented

subscribe

MaienM’s picture

MaienM commented

Subscribe

CSCharabaruk’s picture

CSCharabaruk commented

subscribe

hadi farnoud’s picture

hadi farnoud commented

cant wait for a beta release!
subscribe

neurojavi’s picture

neurojavi commented

subscribe

matroos’s picture

matroos commented

subscribe

mgregoire83’s picture

mgregoire83 commented

subscribe

aquariumtap’s picture

aquariumtap commented

With the four issues in comment #24 marked as fixed, here are some issues that might be of interest to subscribers. @moonray, is this a fair list to bring us to an alpha release?

Performance issues
#1147936: Decouple having to load skin info when we only need to apply skins
#1174818: Rules engine should be optimized

UI
#1172454: Allow skinr groups to be collapsible

Panels compatibility
#1160924: Undefined property: stdClass::$did in skinr_panels_skinr_elements()
#866184: Skinr forces Panels 3.7 into legacy mode
#1160980: Undefined property: stdClass::$did in panels_panels_pane_content_alter()

Misc bugs
#1163618: Clearing cache on Skin settings page causes errors default groups from skinr_skinr_group_info() to not get loaded

moonray’s picture

moonray commented

@aquariumtap: This is the list as I see it.

Alpha

Core

#1007482: Make use of Context API instead of custom rules

UI

#984402: Add "details" link that shows preview of rendered skin widget and additional info
#1149726: Create an 'add skin configuration' form to edit any element on the site (needs to be discussed; might be moved down to a future phase)
#952610: Vertical tabs integration

Misc issues/bugs

#1163618: Clearing cache on Skin settings page causes errors default groups from skinr_skinr_group_info() to not get loaded
#1160924: Undefined property: stdClass::$did in skinr_panels_skinr_elements()
#1124262: Can't attach files from sites/all/libraries to a skin

#866184: Skinr forces Panels 3.7 into legacy mode is irrelevant for D7.
The rest should be handled after the first alpha release.

rickmanelius’s picture

rickmanelius commented

It's great to see an active discussion on creating a roadmap. Thanks so much for all your hard work, and looking forward to helping as a tester when I move a few more clients over to fusion.

MaienM’s picture

MaienM commented

subscribe

rickvug’s picture

rickvug commented

sub

raysworld3’s picture

raysworld3 commented

subscribe

RikiB’s picture

RikiB commented

subscribing :)

Anonymous’s picture

Anonymous (not verified) commented

subscribing

modstore’s picture

modstore commented

subscribe

pancrilio’s picture

pancrilio commented

subscribe

StayingEnPointe.com’s picture

StayingEnPointe.com commented

Subscribing! :)

Looking forward to helping out with testing!

Keep up the good work!

Refineo’s picture

Refineo commented

subscribe

tchopshop’s picture

tchopshop commented

subscribe

lsolesen’s picture

lsolesen commented

+1

crispinbailey’s picture

crispinbailey commented

+1

niccolox’s picture

niccolox commented

Is skinr going forward or has it reach eol?

moonray’s picture

moonray commented

I have repeatedly asked for co-maintainers. So anyone willing to apply for the job is welcome.
Right now I don't have the bandwidth to do a lot of work on Skinr. It's at a reasonable spot: usable.

moonray’s picture

moonray commented
Issue summary: View changes
Status: Active » Fixed

Closing this ticket. All goals have been met. We're in beta, and dealing with mostly bug fixes at this point.
Thanks everyone who chimed in.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.