Skip to main content

Home/ drupal-docs/ Contents contributed and discussions participated by Hans Henderson

Contents contributed and discussions participated by Hans Henderson

3More

Specifying Components and Settings (Drupal 6) | drupal.org - 0 views

shared by Hans Henderson on 24 Nov 08 - Cached
    • Hans Henderson
       
      dvessel wrote in the sidebar: Actually, the "Clearing the theme cache" should be in this main page. The cache is always a hinderance for those that don't know how it behaves. It should be very visible. --- me - absolutely - I have the menu item from Devel module on every site's custom nav that shows up for any user role=admin, this (or an equivalently easy method) should be part of any "introduction to customizing a theme". Not with the background details about the registry etc, perhaps a "here's why" link to that information.
    • Hans Henderson
       
      dvessel - I've proposed a convention for our using Diigo's many different types of "spoor" - Discussion threads in sticky notes, text-specific comments in highlights, as these show on the page without having to browse with the sidebar open. Bookmarks for tagging (because that's the only way to get tags; currently just tagging for D5/6 applicability), don't use Page Comments at all. What do you think of this idea?
2More

Architectural overview of theming | drupal.org - 0 views

shared by Hans Henderson on 24 Nov 08 - Cached
    • Hans Henderson
       
      The content here should allow me to at least have a chance of understanding the node that follows, or maybe intervening nodes need to be inserted, huge jump from this to the coding stuff that follows.
1More

Add $classes to hook templates | drupal.org - 0 views

shared by Hans Henderson on 23 Nov 08 - Cached
  •  
    deep background on preprocess
2More

HowTo: Emulate "preprocess" theme functions in Drupal 5 | drupal.org - 0 views

shared by Hans Henderson on 23 Nov 08 - Cached
    • Hans Henderson
       
      to D5-specific preprocess section
2More

Theming guide | drupal.org - 0 views

shared by Hans Henderson on 23 Nov 08 - Cached
    • Hans Henderson
       
      Great example of a "walk-through" with appropriate tone/level. The wizardly stuff could be below here (NOT buried), and the noob isn't scared away.
13More

Preprocess functions | drupal.org - 0 views

    • Hans Henderson
       
      OK, summarizing - first impression from many was this is way-deep module-developer's stuff and it should be moved to the developer's guide, perhaps http://drupal.org/node/165706. dvessel and addi strongly differed, so we're leaving it here. However IMO the idea of preprocess functions needs to be introduced from a more-noob POV with relevant mainstream examples, with the more-advanced stuff moved to a clearly labeled section or sub-page. Plus the whole idea is D6-specific, except for Zen, right?
    • Hans Henderson
       
      Past comments: Hans Move (most of this?) to the Developer's guide, relevant to creating modules, not end-user theming. Although there should be docs here on how to override using preprocess - applies to D5 using Zen and some others, otherwise just D6. Lee Yes, most of this, maybe all, should be moved. If we're leaving some of this here, there should be a clearer introductory sentence. Something like "If you are developing your own module, you can make it easy for others to theme your content." (I don't know if that's what this page is about, but something like that would allow someone like me to say "Ok this page is something I don't need to read") Shai +1. As evidence that this is the right move, there is a comment on that developer page asking, "Where is the documentation on preprocess functions?" -- and then another comment referring to this page. heather I think also the inclusion of Lee's suggested Intro sentence and help divert anyone off this page to save them some time- no matter where this page ends up. "If you are developing your own module, you can make it easy for others to theme your content." dvessel This is very specific to *theming* so it should stay in the theming handbook. Let's not dumb this down. It's a very important topic to grasp for themers. Addi Whoa, I agree with dvessel here. This is *theming* info that a themer needs to know if they want to implement in their template.php. The devs have their own guide from the module side already. Removing this from the theme guide would be a *horrible* decision. Yes, we can change the text to orient people more, but srsly, this *is* for themes, not modules.
    • Hans Henderson
       
      dvessel - re dumbing it down - agree, but IMO the main "spine" needs to be accessible to people that are brand new users of Drupal, otherwise they won't even try to climb that steep learning curve and bail out of Drupal. We need to make the docs complete, but anyone who's capable of understanding this page as it stands now ain't finding his way by clicking through the nav hierarchy, she already knows google's site:drupal.org :)
    • Hans Henderson
       
      From dvessel 's page-level comment (only visible from the sidebar - I reckon it's easier to see things all together in a sticky) Re: searching through google.. I don't buy it. It can be changed so it's more accessible but all the information should be there in full. I've seen many situations where someone has no clue as to where a piece of information comes from. It's the theming layer and they should be aware of the underlying function to solve their problems. Common question.. How do I change $primary_links? If they knew that "template_preprocess_page" pulls all the page template data then it would be easier to track down. So yeah, change the text so it's easier to understand but let's not remove it preventing others from learning.
    • Hans Henderson
       
      Can we please standardize on floating sticky's except when commenting on specific text? If I have time, I'll summarize and start a new one when a threads gotten too long, but I can't actually delete it until everyone deleted their old posts (after they've been summarized)
    • Hans Henderson
       
      @dvessel - sorry if I'm not being clear, no one's saying move it out anywhere, in fact we're bringing *everything* relating to a topic together as it hasn't been before. It's just that there should be intro/overview pages that are "parents" to the more advanced ones (eg talk about coding), which should help frame the topic for the non-coders, rather than them being thrown right into the deep end without a clue. The complex content will be right there e.g. intro "about pre-process functions", containing info as to how a noob could use them e.g. Zen theme's template.php. This would be a parent of: "details on pre-process functions" and "example pre-process snippets" and "module development and pre-process functions" and a series of step-by-step HowTos on pre-process functions and links to API docs, etc etc. Bringing it all together so it's easy to find via the navigation for everyone, setting the tone of the intro/overview nodes so they are accessible, give the noob a chance to get up to speed.
    • Hans Henderson
       
    • Hans Henderson
       
      http://drupal.org/node/201587 D5 specific to come here
    • Hans Henderson
       
      NP devessel, we're all Diigo noobs, that's why we'll need to define practices as we go. I think these stickies work well, basically a topic thread, start a new one for a different topic or when the old one's got too long, summarizing the old one at the top of the new, along with decisions. D* versioning group tags coming soon.
    • Hans Henderson
       
      Looked at it again, and still can't get my head around it. Needs re-working for different skill/experience level: 1 extract what's relevant for Joe noob tweaking Zen, without him having to learn how it actually works. 2 extract what's only relevant to developers. 3 teach Joe how to understand what's left, and sequence, insert flow/connecting transitions and references to other relevant nodes. e.g. what is a hook? how do you "implement a hook as a template", and what are the other ways to do it, differences?
1More

Dilgo Question - 39 views

started by Shai Gluskin on 21 Nov 08 no follow-up yet
  • Hans Henderson
     
    > Have any of you figured out how to turn off that elaborate toolbar
    > If I can't figure out a way to make that toolbar go away, I'll have to turn Dilgo completely off

    Don't have to turn it off, the whole point is you see the stickies and highlights when you visit a page without having to do anything! And you definitely want to be able to quickly open/close the sidebar.

    Just hide the toolbar - native FF View>Toolbars

    I use a Hide Toolbars icon in my single nav/menu/bookmarks toolbar (you use Tiny Menu don't you?) that has a quick dropdown to turn on and off any of the dozen or so extension-specific toolbars I've got.

    I'm not sure, but I think it's part of "Toolbar Buttons" extension (I had to get an extension to manage my "customize toolbars" window, it's a full five scroll pages tall!)
1More

Redesign- recent iterations and implications for handbook re-write - 29 views

started by heather james on 20 Nov 08 no follow-up yet
  • Hans Henderson
     
    Heather,

    don't want to be a wet dishrag but IMO this should be posted to d.o.

    1 I don't want people to be able to point to Diigo splintering/diluting discussion
    2 you'll get better feedback there
    3 the record of the discussion will be useful to people later on, all this will go away
    4 this is higher-level topic than theming anyway

    Basically I'd like to keep discussion on Diigo to specific categorization/placement of existing d.o. pages, and even those should be summarized and posted back as issues periodically if we can.

    Substantive discussion about handbook pages (i.e. about the content itself) should also take place on d.o.

    I like the topic and will respond over on the issues queue if you repost it there.


    OK?
1More

Welcome Richard - 25 views

started by Hans Henderson on 20 Nov 08 no follow-up yet
  • Hans Henderson
     
    Looks like you're the Diigo veteran here, please have a look at the "getting started for Newbies" bits that Heather and I have written and see if they make sense.

    Look forward you your help with docs in general - do you have a specific interest in helping reorganize the Theming handbook(s).

    And hope you can make it to the IRC meeting tonight. . .
1More

HowTos - Basic HowTo add comments to pages - 34 views

started by Hans Henderson on 20 Nov 08 no follow-up yet
  • Hans Henderson
     
    You can also add sticky notes in specific places on the page, and highlight specific text and then comment on it.

    Both these alternatives have more visibility than the basic whole-page Bookmarks with comments, as you don't need to have the Diigo sidebar open, they appear in situ right on the page.

    I would suggest a convention of all page comments to be posted via a floating sticky near the Title.

    Instructions (thanks Heather!)

    - I have my diigo toolbar installed and opened

    - I browse to the theming handbook, and I will see pink highlighted words, where you've made comments

    - I right click and I can add sticky notes. If I select text then right click, I can add a highlight and sticky note

    - I can also bookmark

    - I must make sure to select which group I am publishing to.

    Anyone please feel free to create new Diigo HowTos here, copy-paste from here to make a new version. . .
2More

Welcome Heather - 30 views

  • Hans Henderson
     
    Excellent, did you go to the D6 theming guide and check out the "Sticky notes?"

    My idea is to come up with a set of standard tags for the group to use on shared Diigo spoor, so that we can work our way through the various nodes related to theming, get them classified and then use that to ensure a good single navigation hierarchy for Book to use.

    I'm proceeding on the assumption we won't see robust use of tagging, or maybe even full consolidation of all the theming stuff into one Book anytime soon.

    IMO this would allows a group to work without depending on d.o. leadership time and attention - a most limited resource it seems. . .

    And the voluminous discussion won't clog up the issue queue or mailing list for those that aren't involved in the project.

    Obviously, periodic summary updates would keep the larger team informed as to our direction so as to be able to give feedback or join in the effort if they become interested.

    What do you think?

    heather james wrote:
    > it works!
    >
    > all looks good!
    >
    >
    > Hans Henderson wrote:
    > > Just for testing, reply to this let's see how it works
  • Hans Henderson
     
    > a similar system we used in the late 90's. We could write sticky notes on any page and share it with our team. We were gutted when they shut it down.

    ThirdVoice?

    > Yes - I think it's brilliant. I'll have a look at your current sticky notes and see what's going on now.

    Nothing going on much yet, we've got an IRC in a few hours hopefully we can get Addy on board with the idea.

    Let's keep the actual group's bookmarks limited to D.O., referencing from those page comments with any external URLs.

    > Could we start with the top level tag of drupal-docs or something like that? And then we free tag after that until we find other repetitive tags?

    Just share the comments to the group, no need for that as a tag.

    Obviously our own bookmarking system as individuals can have anything we like, e.g. I use Evernote.

    But I hate to think about cleaning up freetagging on group comments once we get going on hundreds of pages, I think better to define a few standard vocabularies based on what we think is critical. But maybe I'm not getting how Diigo works, does each member's posting to the group show up as a separate bookmark? In which case we could come up with our own and then discuss merging them later. . .

    Now that I think about it, we need to look for an online collaboration tool to help define the hierarchy, then use tags that point to locations within that. Just tagging by topic,

    To give you an idea of some of the classification ideas discussed:

    I know someone who's going to want "Conceptual vs Procedural vs Mixed-OK vs Mixed-split out" but he's not here yet. Target audience/user role, importance of topic, accuracy of version applicability, accuracy of content.
2More

Introduction to theming | drupal.org - 0 views

    • Hans Henderson
       
      "Changing the labels and the ordering of fields in content types created with the Content Creation Kit. For more information, see the CCK documentation." I would say that this is part of theming, maybe using color module too, but they're not to be included because they are topics specific to contrib-modules, which belong with the module's docs. We can of course link to them when appropriate, and I think CCK is so widely used these kinds of issues need to be at least mentioned as part of template.php/page/node template-specific pages. Also re Views, a lot of what people use Views for can be done through theming, so again, links when appropriate, enough information to inform them in making the choice.
1More

Documentation Team | groups.drupal.org - 0 views

  •  
    read-only, Addy posts announcements here
1More

Welcome drupal-docs team - 18 views

started by Hans Henderson on 14 Nov 08 no follow-up yet
  • Hans Henderson
     
    email me to let me know you've joined:

    hans@pobox.com

    Guideline - let's use this forum to only talk specifically about Diigo-related meta issues.

    Otherwise let's talk in the issues queue or the mail list so everyone can see and comment.

Basic theme help | drupal.org - 0 views

shared by Lee Hunter on 14 Nov 08 - Cached
1 - 17 of 17
Showing 20 items per page