November 2007 - Development - lists.drupal.org

Re: [development] Taxonomy usability improvement: Hierarchy -> Term structure
by Liza Sabater 20 Nov '07

20 Nov '07

HUGE +1 from me too. -- Liza Sabater, Publisher culturekitchen.com dailygotham.com AIM cultkitdiva MOB 646.552.7365 --------- Original Message -------- From: development(a)drupal.org To: development(a)drupal.org <development(a)drupal.org> Subject: Re: [development] Taxonomy usability improvement: Hierarchy -> Term structure Date: 14/11/07 11:50 > I was going to say "'Multiple parent' is confusing because it doesn't > describe what it currently does". But I decided to give it a try and > be hold ... "single" actually does mean "single parent" and > "multiple" "multiple parent". > > I had always wondered why Taxonomy supported multiple parents > internally, but never exposed that to the UI. But it did. (I > interpreted "single" as a two-layered vocabulary, where you couldn't > have a third layer.) > > So you get a big +1 from me :) > > Wim Leers ~ http://wimleers.com/work > > > On Nov 14, 2007, at 22:05 , Robert Douglass wrote: > > > For those of you who now have a thirst for re-wording things to > > improve the usability of taxonomy, here's an issue that has been > > frustrating to me for a while (and I just now got motivated to > > write a patch): http://drupal.org/node/192242 > > > > It re-words the Hierarchy field from this: > > > > Hierarchy: > > Disabled > > Single > > Multiple > > > > to this: > > > > Term structure: > > List > > Single parent > > Multiple parent > > > > There is also a patch to work on the whole help text for taxonomy: > > http://drupal.org/node/190497 > > > > And a wiki page on g.d.o. where we can discuss the text (since we > > sure as hell don't want to do that on this list): > > http://groups.drupal.org/node/7132 > > > > -Robert > > > ________________________________________________ Message sent using UebiMiau 2.7.10

3 2

AHAH widgets
by Karoly Negyesi 20 Nov '07

20 Nov '07

Hi, Until now, adding AHAH to something defined in hook_elements was not possible which was really, really sad as it made AHAH reusable elements impossible. This is now fixed, Dmitri fixed AHAH and I refactored/added some small FAPI parts. I hope that an example will be committed tomorrow, I need to finish first, but it's coming along very nicely. The example wll be an iTunes-styles drilldown selector for menu/book in http://drupal.org/node/191360 . Regards, NK

2 2

Views 2: Call for help
by Dmitri G 20 Nov '07

20 Nov '07

Views 2 is currently being updated for Drupal 6 compatibility, but it needs major help in order to be ready for the Drupal 6's approximate release date! We're short on people and short on time, so here's the bottom line. Without your assistance and contributions, there will be no Views for Drupal 6 within any useful timeframe. If we don't have Views 2 ready for the D6 release date, the vast majority of casual users will not even bother to download and try Drupal 6. That would be bad, so you need to get involved in helping to complete Views 2 so this scenario doesn't happen! What can I do to assist? There are still four major areas that need to be completed: User Interface, Handlers, Documentation, and the Upgrade Path. Here's how you can get involved: Views 2 Priorities * User Interface [managed by dmitrig01] There are several key features in the User Interface that need some help, but they're too detailed to explain here. If you would like to help code it, or if you're themer who likes intelligible design, we want your skill. * Handlers Small chunks of code that tell Views about other modules that may exist. Handlers provide the 'core integration' functionality. * Comment * Book * Comment * Forum * Profile * Search * Statistics * Taxonomy * Upload * Upgrade path * Documentation * In-module documentation for end users (tooltips, help pages) [managed by dmitrig01] * Drupal.org End-user Handbook documentation [managed by Senpai] * Drupal.org Handbook Developer documentation * Drupal.org Handbook Themer documentation Who we need * Able coders who are willing to donate some hours to the effort * Documentation writers who are willing to write a paragraph or three. * People who can over-see other people and are able to do either of the above (we're still looking for over-seers for some areas). How you can help Please leave a reply about your availability, what you capabilities are, and what you'd be willing to work on. We'll handle it from there. We really need help under these four categories but if you can think of anything else you'd like to help with, then go ahead and make a comment about that too.

6 7

Drupal 6 release status
by Dries Buytaert 20 Nov '07

20 Nov '07

Hello world, I talked to Gabor this morning and we decided we're going to release a third Drupal 6 beta on Wednesday. We also decided that this should probably be the last beta release. Hence, it is extremely likely (but not guaranteed) that we're going to have a first release candidate (RC) after Drupal 6 beta 3. I figured I'd share this information ahead of time, so we can slowly get into "RC mode" and become more strict about what pending issues we flag as "critical". It also means that there isn't a whole lot of time left for usability improvements. Thanks, -- Dries Buytaert :: http://www.buytaert.net/

11 21

This is usability too: be friendly when the user can't login
by Karoly Negyesi 18 Nov '07

18 Nov '07

It was brought to my attention that http://drupal.org/node/2946 still lingers.

1 0

hi
by Sanari Software Solutions Pvt Ltd., 18 Nov '07

18 Nov '07

-- Regards Yarramsetty Samba Siva Rao Sanari Software Solutions Pvt. Ltd., (Software Training, Development, Placements & NCFM Coaching) SRT-44, S.R.Nagar, Near Nagarjuna Jr. College, Hyderabad-500 038. Tel: 91-40-6457 3042 Mobile: 9949104388 email: sanari9(a)gmail.com

1 0

Re: [development] Early Drupal 6 review from Chris Messina
by Karen Stevenson 18 Nov '07

18 Nov '07

I think one simple change would make a world of difference without 'dumbing' anything down. As was mentioned before, the most confusing thing is the word 'vocabulary' since it's not obvious, even if you know figure out that taxonomy is way of categorizing things, what exactly a vocabulary is. So just change vocabulary to either 'category type' or 'category group', then we have a much more clear breakdown of: taxonomy -> categories vocabulary -> category type (or category group) term -> category (or term) Karen

31 47

Maintainers and co-maintainers wanted for Javascript Tools and other modules
by Nedjo Rogers 17 Nov '07

17 Nov '07

The Javascript Tools package will be separated into distinct modules for D6. If you're interested in any of these modules, please consider co-maintaining them or becoming the new maintainer. I also maintain a number of other modules that I'm looking for co-maintainers or maintainers for. Some of these are small and simple (just a few lines of code) and could be a good place to start digging into Drupal module maintaining. Please contact me, http://drupal.org/user/4481/contact, to discuss any of these modules. Thanks! Nedjo Rogers Javascript Tools, http://drupal.org/project/jstools Active Edit - In place editing. Active Menu - Makes the standard Drupal navigation menu expandable through AJAX. Active Search - Makes the search form submit through AJAX. Ajax Submit - Enables form submitting through AJAX. Collapsiblock - Makes all Drupal blocks collapsible. Tabs - Provides developer tools to produce client-side tabbed pages using the jQuery tabs plugin by Klaus Hartl, stilbuero.de/tabs. Dynamicload - Provides methods for dynamically loading selected page content without page refreshes. Includes dynamic loading of blocks. Rough edges, not currently stable. Small and relatively simple helper modules: CCK Fieldgroup Tabs, http://drupal.org/project/cck_fieldgroup_tabs - Display groups of fields on tabs, in both node edit and display. Views Tabs, http://drupal.org/project/views_tabs - Display the items in a view on tabs. CiviCRM Localize, http://drupal.org/project/civicrm_localize - Enable localization of CiviCRM profile fields. Form Block, http://drupal.org/project/formblock - Display node add forms on blocks. Node Info, http://drupal.org/project/node_info - Include info like updated time with node display. Contact Link, http://drupal.org/project/contactlink - Provide a link on nodes to users' contact forms. Search Type, http://drupal.org/project/search_type - Enable selection of type of search on search forms (user, node type). Term Display, http://drupal.org/project/term_display - Control the way terms are displayed with nodes. Text Field Tags, http://drupal.org/project/text_field_tags - Provide a basic set of HTML tag wrappers for CCK textfield display. CCK Teaser Field, http://drupal.org/project/cck_teaser_field - Select a field to serve as a teaser. Cookie Check, http://drupal.org/project/cookie_check - Display a message if cookies aren't available. Mediafield Display, http://drupal.org/project/mediafield_display - Output audio fields in Flash players. Larger or more complex modules: Content Blocker, http://drupal.org/project/contentblocker - Users can block content by specific other users (extensible API, could be used for other blocking). Formfilter, http://drupal.org/project/formfilter - Apply filters to forms to remove cluttering elements Organic Groups Sites, http://drupal.org/project/og_sites - Multisites through OG. Page Array, http://drupal.org/project/pagearray - Fetch the output of a page in array format rather than final rendered form. Taxonomy context, http://drupal.org/project/taxonomy_context - Provides display options for taxonomy terms at taxonomy/term/x, vocabularies at taxonomy/vocabulary and taxonomy/vocabulary/x, and a context-sensitive taxonomy block.

1 0

drupal_execute
by domas 17 Nov '07

17 Nov '07

Hi, I was experimenting with drupal_execute, but this set of functions does not seem to work the way I expect it to. I change the function the node creation form submits to and then try to call drupal_execute to pass the values. function splitter_form_alter($form_id, &$form) { if ($form_id == 'page_node_form') { $form['#submit'] = array( 'splitter_submit' => array() ); } } function splitter_submit($form_id, $form_values) { drupal_execute('page_node_form', $form_values); } However, this does not seem to work. After I submit, I get a blank page and no node is created. What am I missing? Thanks, Domas

3 3

RFC: Solution for avoiding duplicate issues
by Derek Wright 16 Nov '07

16 Nov '07

Earlier tonight I had a serious "eureka!" moment on how to avoid duplicate issues: http://drupal.org/node/192714 Reply-To: http://drupal.org/node/192714#comment-form Thanks, -Derek (dww)

1 0