The arctica project page says the theme depends on the skinr module. Is that correct? Or is it just the demo site that depends on skinr? I was able to enable the arctica and set it to default without enabling skinr.

Comments

dddave’s picture

dddave commented
Title: Project page says theme depends on skinr, but I'm not sure that's true » Project page says theme depends on skinr and arctica nitro, but I'm not sure that's true

Same goes for arctica nitro which I just downloaded because I revisited the module page. I don't think this can be called a dependency if the theme itself doesn't complain when the module is missing. ;)

jurriaanroelofs’s picture

jurriaanroelofs commented
Assigned: Unassigned » jurriaanroelofs
Status: Active » Needs work

Ok, I'll add a complainer function in the theme (configurator) :)

dddave’s picture

dddave commented

Related: If it would be clearer what Nitro is used for the need for it would be obvious. I am currently playing around with this whole stuff and exploring but when you simply download the theme the lack of Nitro doesn't seem problematic.

jurriaanroelofs’s picture

jurriaanroelofs commented

Currently Nitro takes care of enabling the theme on the theme settings form, for easier configuration. Later this activation will become more of a requirement when the theme configurator supports "live preview" i.e. theme settings effectuating immediately when you're working on the form or changing colors.

Nitro is also used to add the "export theme settings" and "reset to defaults" buttons to the configurator.

Part of the reason for having it as a requirement is so that people will get the benefits from Nitro when I update it with more features in the future. I have some ideas of putting part of the framework into modules because it gives me more power over Drupal.
Examples would be exposing theme settings to users for individual usability/style preferences, or advanced commerce integration. Maybe adding special features to Skinr etc.