<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Visnu,<br>
You can simply join the channels. See <a class="moz-txt-link-freetext" href="http://drupal.org/irc">http://drupal.org/irc</a> for an
overview of available channels and make sure to choose the most
appropriate channel for your needs.<br>
Marc<br>
<br>
PS When replying to the mailing list, please quote as little as
possible.<br>
<br>
vishnu vardhan wrote:
<blockquote
cite="mid:7e2c1d8d0912010402o3caef865wc0a9c4914b5e4e6c@mail.gmail.com"
type="cite">Hi All ,<br>
Can i join #drupal chaneel or do i need recomendation???<br>
Visnu<br>
<br>
<div class="gmail_quote">On Tue, Dec 1, 2009 at 5:10 PM, <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:development-request@drupal.org">development-request@drupal.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send
development mailing list submissions to<br>
<a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a moz-do-not-send="true"
href="http://lists.drupal.org/mailman/listinfo/development"
target="_blank">http://lists.drupal.org/mailman/listinfo/development</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a moz-do-not-send="true"
href="mailto:development-request@drupal.org">development-request@drupal.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:development-owner@drupal.org">development-owner@drupal.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of development digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Consolidating duplicate contrib modules for D7 (Brian Vuyk)<br>
2. Re: Consolidating duplicate contrib modules for D7 (Andrew Berry)<br>
3. Re: Ctools form wizard (Earl Miles)<br>
4. Re: Consolidating duplicate contrib modules for D7 (Shai Gluskin)<br>
5. alter theme registry, but only for some themes. possible?<br>
(David Cohen)<br>
6. Re: Consolidating duplicate contrib modules for D7<br>
(Martin Stadler)<br>
7. Re: Consolidating duplicate contrib modules for D7 (Zoltan Varady)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 30 Nov 2009 14:44:58 -0500<br>
From: Brian Vuyk <<a moz-do-not-send="true"
href="mailto:brian@brianvuyk.com">brian@brianvuyk.com</a>><br>
Subject: [development] Consolidating duplicate contrib modules for D7<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:4B1420BA.7010404@brianvuyk.com">4B1420BA.7010404@brianvuyk.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
I know the whole 'duplication in contrib' issue has been discussed to<br>
death on this list, so I will try to keep this short.<br>
<br>
Obviously, the duplication in contrib is something we are working hard<br>
as a community to avoid. Nevertheless, in some cases, duplication has<br>
still crept in, and this leads to a poorer user experience, and user<br>
confusion.<br>
<br>
One prime example is the node access modules, which all perform nearly<br>
identical functions with more or less polish:<br>
<br>
Node Access: <a moz-do-not-send="true"
href="http://drupal.org/project/node_access" target="_blank">http://drupal.org/project/node_access</a><br>
Nodeaccess: <a moz-do-not-send="true"
href="http://drupal.org/project/nodeaccess" target="_blank">http://drupal.org/project/nodeaccess</a><br>
Content Access: <a moz-do-not-send="true"
href="http://drupal.org/project/content_access" target="_blank">http://drupal.org/project/content_access</a><br>
<br>
Now, is there anything we as a community can do to clean up this sort of<br>
issue in contrib? I realize that in individual cases, the best policy is<br>
to post in the issue queues for the individual projects, but on a larger<br>
scale, is it worth starting something along the lines of #D7CX to<br>
consolidate the dupes in the name of a better user experience?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 30 Nov 2009 15:22:55 -0500<br>
From: Andrew Berry <<a moz-do-not-send="true"
href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a>><br>
Subject: Re: [development] Consolidating duplicate contrib modules for<br>
D7<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:53A37D3A-8063-4E4A-B679-19689DCE51E7@sentex.net">53A37D3A-8063-4E4A-B679-19689DCE51E7@sentex.net</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
On 2009-11-30, at 2:44 PM, Brian Vuyk wrote:<br>
<br>
> Node Access: <a moz-do-not-send="true"
href="http://drupal.org/project/node_access" target="_blank">http://drupal.org/project/node_access</a><br>
> Nodeaccess: <a moz-do-not-send="true"
href="http://drupal.org/project/nodeaccess" target="_blank">http://drupal.org/project/nodeaccess</a><br>
<br>
IMO there should be a CVS policy disallowing namespaces to be
differentiated with dashes, underscores, spaces, and so on. This is a
perfect example of the confusion this can cause.<br>
<br>
> is it worth starting something along the lines of #D7CX to
consolidate the dupes in the name of a better user experience?<br>
<br>
I think that if this is something you want to do, you should try and
find some of the more popular maintained modules and try to get one or
two sets of projects on board. Once there are a few big projects
starting down this path, I think it would really help to encourage the
smaller projects to work together.<br>
<br>
--Andrew<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/pkcs7-signature<br>
Size: 2676 bytes<br>
Desc: not available<br>
Url : <a moz-do-not-send="true"
href="http://lists.drupal.org/pipermail/development/attachments/20091130/4ee3aa0c/attachment-0001.bin"
target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091130/4ee3aa0c/attachment-0001.bin</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 30 Nov 2009 12:33:35 -0800<br>
From: Earl Miles <<a moz-do-not-send="true"
href="mailto:merlin@logrus.com">merlin@logrus.com</a>><br>
Subject: Re: [development] Ctools form wizard<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:4B142C1F.7040006@logrus.com">4B142C1F.7040006@logrus.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Dipen wrote:<br>
> Hi list,<br>
><br>
> Can I mix system form with a custom form in ctools form wizard, I
wish<br>
> to create a wizard containing 1 node add form and 2 custom forms.
I have<br>
> briefly looked at advanced help of form wizard and I think there
would<br>
> be problem in dealing with _submit of node add form in module
space. Has<br>
> anyone encountered this before? I am trying to create multistep
form<br>
> with 1 node add form and 2 custom forms and ctools looks like the<br>
> cleanest way but not sure how would I get around the _submit
handler<br>
> problem for node add form.<br>
><br>
> From ctools help:<br>
><br>
> " The primary difference between these forms and a normal Drupal
form is<br>
> that the submit handler should not save any data. Instead, it
should<br>
> make any changes to a cached object (usually placed on the
$form_state)<br>
> and only the _finish or _return handler should actually save any
real<br>
> data. "<br>
<br>
Run in fear!<br>
<br>
What you want to do is really really hard, especially when dealing with<br>
nodes, because the node form is a *very* difficult workflow that is not<br>
really open to being changed. I don't think the ctools wizard is going<br>
to help you here. That said, at one point Nick Lewis was doing some work<br>
trying to integrate form wizard into the node form, and he had some<br>
success, but I haven't seen any movement there for a long time.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 30 Nov 2009 15:50:12 -0500<br>
From: Shai Gluskin <<a moz-do-not-send="true"
href="mailto:shai@content2zero.com">shai@content2zero.com</a>><br>
Subject: Re: [development] Consolidating duplicate contrib modules for<br>
D7<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID:<br>
<<a moz-do-not-send="true"
href="mailto:9f68efb70911301250mb94a68fj7a4156b4bf3b712f@mail.gmail.com">9f68efb70911301250mb94a68fj7a4156b4bf3b712f@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I think the important part is giving users good information. Asking the
docs<br>
team to write module comparison pieces is a good thing too. But I'm
against<br>
any plan that tries to put controls on module creation because the
freedom<br>
to scratch an itch has led to great creativity and ingenuity. But
helping<br>
module developers know what is already out there, that's always a good<br>
thing.<br>
<br>
When the d.o. re-design launches, I think it is going to be a different<br>
world. And I think it will be a lot clearer where energies should be
spent<br>
on helping site builders and other Drupal constitutents get what they
need.<br>
<br>
Shai<br>
Content2zero Web Development <<a moz-do-not-send="true"
href="http://content2zero.com" target="_blank">http://content2zero.com</a>><br>
<br>
On Mon, Nov 30, 2009 at 3:22 PM, Andrew Berry <<a
moz-do-not-send="true" href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a>>wrote:<br>
<br>
> On 2009-11-30, at 2:44 PM, Brian Vuyk wrote:<br>
><br>
> > Node Access: <a moz-do-not-send="true"
href="http://drupal.org/project/node_access" target="_blank">http://drupal.org/project/node_access</a><br>
> > Nodeaccess: <a moz-do-not-send="true"
href="http://drupal.org/project/nodeaccess" target="_blank">http://drupal.org/project/nodeaccess</a><br>
><br>
> IMO there should be a CVS policy disallowing namespaces to be<br>
> differentiated with dashes, underscores, spaces, and so on. This
is a<br>
> perfect example of the confusion this can cause.<br>
><br>
> > is it worth starting something along the lines of #D7CX to
consolidate<br>
> the dupes in the name of a better user experience?<br>
><br>
> I think that if this is something you want to do, you should try
and find<br>
> some of the more popular maintained modules and try to get one or
two sets<br>
> of projects on board. Once there are a few big projects starting
down this<br>
> path, I think it would really help to encourage the smaller
projects to work<br>
> together.<br>
><br>
> --Andrew<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a moz-do-not-send="true"
href="http://lists.drupal.org/pipermail/development/attachments/20091130/ca4380e0/attachment-0001.html"
target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091130/ca4380e0/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 30 Nov 2009 16:08:07 -0800<br>
From: "David Cohen" <<a moz-do-not-send="true"
href="mailto:drupal@dave-cohen.com">drupal@dave-cohen.com</a>><br>
Subject: [development] alter theme registry, but only for some
themes.<br>
possible?<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:1259626087.7546.1347767341@webmail.messagingengine.com">1259626087.7546.1347767341@webmail.messagingengine.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I have some modules that alter the theme registry. In practice, I could<br>
limit these alterations to only some themes. On a site with multiple<br>
themes, my modules might need to alter only one or two. However, I<br>
can't figure a way in code to determine which themes might need these<br>
alterations.<br>
<br>
Ideally, I could allow the administrator to select one or more themes<br>
which will be used. Either by selecting the themes in a form, or<br>
possibly by adding something to the theme's .info file.<br>
<br>
Is such a thing possible. In particular, how can I ensure that the<br>
theme registry will be rebuilt after the administrator submits my form<br>
or edits the .info file? Is there a best practice along these lines?<br>
<br>
-Dave<br>
<br>
P.S. too bad drupal doesn't support post-process functions in theme...<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 1 Dec 2009 11:29:26 +0100<br>
From: Martin Stadler <<a moz-do-not-send="true"
href="mailto:martin@siarp.de">martin@siarp.de</a>><br>
Subject: Re: [development] Consolidating duplicate contrib modules for<br>
D7<br>
To: <a moz-do-not-send="true" href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:E5FF7DDF-E092-46EF-A3A7-0A06B4352FF9@siarp.de">E5FF7DDF-E092-46EF-A3A7-0A06B4352FF9@siarp.de</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br>
<br>
I think the best solution is a comparison of similar modules on the<br>
module's project page. Some maintainers do that and it saves you so<br>
much time and trouble. It's easy and non-restrictive and there's<br>
nothing that's sacrificed.<br>
<br>
Martin<br>
<br>
<br>
Am 30.11.2009 um 21:50 schrieb Shai Gluskin:<br>
<br>
> I think the important part is giving users good information. Asking<br>
> the docs team to write module comparison pieces is a good thing
too.<br>
> But I'm against any plan that tries to put controls on module<br>
> creation because the freedom to scratch an itch has led to great<br>
> creativity and ingenuity. But helping module developers know what
is<br>
> already out there, that's always a good thing.<br>
><br>
> When the d.o. re-design launches, I think it is going to be a<br>
> different world. And I think it will be a lot clearer where
energies<br>
> should be spent on helping site builders and other Drupal<br>
> constitutents get what they need.<br>
><br>
> Shai<br>
> Content2zero Web Development<br>
><br>
> On Mon, Nov 30, 2009 at 3:22 PM, Andrew Berry<br>
> <<a moz-do-not-send="true" href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a>>
wrote:<br>
> On 2009-11-30, at 2:44 PM, Brian Vuyk wrote:<br>
><br>
> > Node Access: <a moz-do-not-send="true"
href="http://drupal.org/project/node_access" target="_blank">http://drupal.org/project/node_access</a><br>
> > Nodeaccess: <a moz-do-not-send="true"
href="http://drupal.org/project/nodeaccess" target="_blank">http://drupal.org/project/nodeaccess</a><br>
><br>
> IMO there should be a CVS policy disallowing namespaces to be<br>
> differentiated with dashes, underscores, spaces, and so on. This is<br>
> a perfect example of the confusion this can cause.<br>
><br>
> > is it worth starting something along the lines of #D7CX to<br>
> consolidate the dupes in the name of a better user experience?<br>
><br>
> I think that if this is something you want to do, you should try
and<br>
> find some of the more popular maintained modules and try to get one<br>
> or two sets of projects on board. Once there are a few big projects<br>
> starting down this path, I think it would really help to encourage<br>
> the smaller projects to work together.<br>
><br>
> --Andrew<br>
><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Tue, 1 Dec 2009 12:33:58 +0100<br>
From: Zoltan Varady <<a moz-do-not-send="true"
href="mailto:zoltan@farm.co.hu">zoltan@farm.co.hu</a>><br>
Subject: Re: [development] Consolidating duplicate contrib modules for<br>
D7<br>
To: development <<a moz-do-not-send="true"
href="mailto:development@drupal.org">development@drupal.org</a>><br>
Message-ID:<br>
<<a moz-do-not-send="true"
href="mailto:70defad0912010333y66fb4766s2f299b39960a46ad@mail.gmail.com">70defad0912010333y66fb4766s2f299b39960a46ad@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
You do know about the "Similar Module Review" group, right?<br>
<br>
<a moz-do-not-send="true"
href="http://groups.drupal.org/similar-module-review" target="_blank">http://groups.drupal.org/similar-module-review</a><br>
<br>
They review similar modules.<br>
<br>
<br>
------------------------------<br>
<font color="#888888"><br>
--<br>
[ Drupal development list | <a moz-do-not-send="true"
href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a>
]<br>
<br>
End of development Digest, Vol 84, Issue 1<br>
******************************************<br>
</font></blockquote>
</div>
<br>
</blockquote>
</body>
</html>