Posted by zkrebs on May 2, 2011 at 5:42pm
Trying to keep up with the schedule here -
I talked with a local business owner in Talent about having our next meeting at his place, Picasso's Pantry, and he's thrilled! There's a big square table, $5/pasta and wireless internet! So, lets have our next meeting there, How about the 14th at 11:00AM? I'll call and let him know, and check to see if its available.
Would anyone like to present something this meeting? My ddblock stuff turned out to be lackluster - Personally I'd love if someone would illustrate the Context way vs. the Panels way for building a site.
Comments
Meeting Place Sounds Great
The Meeting Place sounds great. Maybe some of the Ashland people could carpool?
I installed context to work with the Omega Theme and Beta subtheme. The Omega tutorial which I found is very long and still confusing. However, the lecturer repeatedly said panels was confusing for clients and that Omega 960 grid was a better way to go. The address of the video is himerus dot com. I'm not far enough along to really help you but the theme topic is one of the most important parts for all of us and I am glad Jeff pointed out Omega. Your suggestion of discussing Context is a great idea. In fact, the 960 grid and context might be a great topic for the next two meetings so we can discuss what to focus on in the first meeting and and discuss what we know about context and a grid theme. The second meeting we could display some examples and talk about any nifty successes.
For Omega I choose the beta subtheme because it has a color picker in the settings. That way it is easier to flip the colors and see the results. Once the results are seen it is easy to go to the css and reverse engineer the classes and ids. The gamma theme is neat because it shows lots of the sections but then you have to clean it up to get a final site. The Libra subtheme did not match the Omega version so it had significant problems.
See ya on the 14th.
Sounds good on the time and
Sounds good on the time and place.
I do use context on a couple of sites. It does work much the same as panels without some of the fancy drag and drop interfaces.
With Omega you probably want to use the alpha version along with one of the starter themes included. The alpha version did look stable during my testing.
Sounds good!
Is that the place next to the Hardware/Liquor store? Either way, I'm in!
I don't have much to demo. I would love to see various examples of Views (front and back). Even though I'm confused about some of the major settings, I'm amazed at how much I accomplished so far!
-
She was a whiskey maker, but he loved her still.
Good plan
I will be there to share in the Drupal goodness. I was hoping to share info on Pantheon as a platform but I am still waiting for my beta invite. If anyone has a beta account I would love to see it in action.
Drupal
D7 Clarification
Omega install for D7 provides 2 subthemes - HTML5 starter kit and XHTML starter kit. Alpha is only D6, there is no alpha theme written for D7. Himerus also built 2 additional separate downloadable subthemes for D7 called Beta and Gamma.
I should always preface comments with D7 since most people that are building for clients are using D6. If I forget to remind people about D7 please remember D6 has some differences. Many recommended modules have no D7 counter part and some modules are incorporated CORE and in modules with different names. That seems to be true with media modules in particular. Drupal developers seem to be consolidating all the various media options. For example there is an HTML 5 open video player now by a group or organization called MediaFront. There is a mediafront module which does have a D6 version too. I'll start to move my website from localhost to the internet and see about building a video to show on mediafront (if it works ok).
D7 is the version I decided to learn so please remember my comments might not always apply to D6. Concepts in D7 are pretty much the same however.
I am doing
a paid project using the Omega theme (the 2.x version) - from the page - http://drupal.org/project/omega - I have learned my lesson about stability.
Status MessagesOmega 2.x is STABLE!!! Please note the following issues for a couple items that will affect users upgrading from an alpha version > current release.
We'll see how it really works compared to Zen / Fusion, my former favorites.
Additionally,
@hozt - right - also, i did a site with panels and its a huge RAM Hog, I'm experiencing - another win for Context - also open atrium, etc. use "the context context way" so its useful to learn. however, the more i get into drupal i just edit regions and tpl.php files -
@quincunx55555 - yes its next to the liquor store ;) classy, right?
@joedully - great, glad to see you ! don't have a pantheon account, but I'd also be interested
@bill hatch - sounds good, thanks for keeping an eye on the media module options
Which Subtheme?
Which subtheme are you using. Beta is based on the HTML 5 starter kit. This next meeting should be interesting. Like I mentioned Libra is not compatible with 2x so that was a quickly disabled theme. Question about themes... is there an uninstall or do you just delete the directory. Does a theme installation add anything to the database?
Could someone say a little more about the Pantheon Platform? I see is is free for developers which is my favorite price. Since I can't currently use Drush (no command line ssh) that will be a real opportunity to learn Drush too. Just want to know a little about Pantheon from people that might be familiar with the platform.
I copied the HTML5 starter
I copied the HTML5 starter kit and made my own sub-theme of Omega.
You can read more about
You can read more about Pantheon on their website. If you want to test the platform now there is an ami image for Amazon EC2 and Linode has a stack script that will install everything for you.
Omega D7 Questions
I know there is lots written about the Omega Theme. I have been reading some of the documentation but still not understanding how things work.
Question 1. Omega has a .info file and the html5 subtheme has a .info file. The subtheme .info has a line showing the "base theme = Omega". So how do these two .info files relate? Both theme and subtheme have .info files which are pretty much the same even though I haven't compared line by line. Of course, Omega .info doesn't define a base theme.
Question 2. Omega has many css files (18 to be exact). The html5 subtheme just has subtheme.css which is required as explained in the README.txt. It is also empty. Lets say I want to change the omega_theme_settings.css. I want to change the "color:" value in the class named .region_title.
Do I copy the lines from .region_title in Omega and paste them in the html5 subtheme.css with the identical name?
Question 3. (depends on question 2. but hopefully you can understand the meaning of both questions).
This another way of asking question 2. There may only be one answer for both questions.
What about coping the entire css file from Omega and adding a line to the subtheme .info "stylesheets[all][] = whateverfilename.css" Would that over-ride the same css file in the Omega css directory? If so, that would mean Drupal will stop searching for the class name as soon as it finds the first definition in both questions.
Assumptions:
My first assumption is that I don't delete or modify any Omega Theme css files.
Second assumption is that Drupal uses the first definition of a class name that it finds. Meaning duplicate definitions are OK and in fact are the proper way to re-define the Base Theme values.
Part of why I am confused is that Omega .info only defines the css/960.css. However, it appears to be using some or all of the other 18 css files. Why doesn't the .info file have 18 lines defining "stylesheets[all][] = xxx" for each of the 18 stylesheet in the /css directory? What is the relationship to those files that are not defined in the .info file and those that are defined in the .info files?
This has been long question but one more thing. Has anyone installed the Omega UI module?
Pro Drupal 7 Development
This book explains the theme building process and points out the the core modules involved as well. Learning Drupal is complicated and "Pro Drupal 7 Development" ties together concepts. The individual Drupal Node documentation focuses on pieces which is sometimes confusing. This book is worth the price.