Closed (fixed)
Project:
radix
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2013 at 12:16 UTC
Updated:
2 Feb 2013 at 00:50 UTC
So I've created this sandbox:
http://drupal.org/sandbox/rerooting/1890090
Where I am going to just start pushing style plugins, submodules that provide field formatters, widgets, etc. Some of these may be theme-oriented, some not. What I think might work is if I just start pushing style plugins as I develop them, and where you feel it is appropriate, you can pull them into the radix theme, and I can drop them from radix_ui. Is that a bad idea? Should I just send all ctools style plugins your way? Do you like the idea of a Radix UI project?
Comments
Comment #1
shadcn commentedI like the idea of a radix_ui module. I think we can keep ui plugins there.
I'm following the same convention as you suggested above. I have Radix Admin module and Radix Layouts module. Both as enhancements/plugins for Radix.
I'm keeping radix theme as a bare minimum with the css and some basic tpl files. I'm hoping eventually the theme can be used outside of Panopoly as well.
Let's go with Radix UI.
Thanks for helping ^^
Comment #2
rerooting commentedNo problem!
Also a quick note, I will be submitting a roll of patches of some theme tricks borrowed from the twitter_bootstrap theme that might give us a bit more control over some core-level theme behavior. I actually went through and basically mushed in all the code I thought would be helpful, including some snazzy includes, and the results are pretty neat though some tweaking will be needed. I will introduce this all pretty much one function at a time so that we can all choose what to accept or reject!
Comment #3
shadcn commentedMarking this as fixed.