- Development - lists.drupal.org

Severity levels
by Karoly Negyesi 16 Jan '06

16 Jan '06

extreme critical: when a bug breaks all core , sessions, bootstrap one of the form elements or something like that. These are to be fixed immediately because Drupal HEAD is not usable at all. critical bugs render a whole (or most of a) module unusable. Example: you can't post a forum topic. major bugs: a smaller part of a module. You can't add a menu with menu module. -- below these are bugs that do not hold a release -- Normal bugs just bugs, we could even release with these. Just one functionality, like the category filter not working on node admin screen. And minor bugs are cosmetical stuff, notices etc I know we will not be able to agree on anything, yet I have at least tried. For once, think twice before answering. Thanks Karoly Negyesi

2 1

Re: [development] [lazyweb] Drupal Configurator
by Greg Knaddison 16 Jan '06

16 Jan '06

On 1/15/06, Arnab Nandi <arnabdotorg(a)gmail.com> wrote: > I'd post a feature request if this was a drupal feature. What I want > is an application _separate_ from drupal, that generates configs > offline. You included a variety of problems that would be solved by your new application/feature. I don't see a really strong use case for the "offline edits" part of it, but improving admin UI would certainly help everyone. > > > > Why not just improve the UI to reduce page views/iterations and/or use > > AJAX techniques to reduce the amount sent back/forth to do this work? > > Well, this is a good method and should be introduced(so should "power > edit forms"); but I'd prefer to have a native(read: disconnected) app > that can create a pre-validated, complete site structure; which can > then set up the website with one button. So what you really want is the disconnected part. The difficulty of editing the admin pages is not as high of a priority as is the offline part. > > To give you an analogy: Flickr has such great AJAX, but it still has > Uploadr and Organizr. Just because they did, doesn't make it right for others. Greg

1 0

Re: [drupal:dries] /modules contact.module
by Stefan 16 Jan '06

16 Jan '06

IMO this patch introduced even more inconsistencies in core than we already had.. Look at the way this patch dealed with HTML-tags inside the _help(). We never did that this way.. %category is IMO user submitted data, which is NOT translatable through drupal! It isn't now, and should never be wrapped through t(). I heared someone complain lately about bad reviewing of patches, but this isn't an excellent example either! C'mon Dries, why in Gods name did you applied this patch??? Steef Op 14-jan-2006, om 11:33 heeft drupal-devel(a)drupal.org het volgende geschreven: > User: dries Branch: HEAD Date: Sat, 14 Jan 2006 10:33:22 +0000 > > Modified files: > /modules contact.module > > Log message: > - Patch #39135 by Zen: various contact form improvements/fixes. > > + Conversion to _validate + _submit model.. > + Split replaced by explode - faster > + Fixed typos: Recipient > + Fixed weight defaulting to -10 > + Popped mail subject formatting into a t() > + Popped '--' formatting into a t() > + Does a lot of documentation fixing/rewriting. > + Renamed contact_user_mail form functions to contact_mail_user > for consistency. > + ... > > Links: > http://cvs.drupal.org/diff.php?path=drupal/modules/ > contact.module&old=1.39&new=1.40 > > -- > [ Drupal cvs list | http://list.drupal.org/ ] > > --- Stefan Nagtegaal Drupal-Devel(a)iStyledThis.nl Drupal Development Mailinglist

3 5

Re: [development] Re: Why Drupal 4.7 is late? (long)
by Kobus Myburgh 16 Jan '06

16 Jan '06

Can we go ahead and arrange such a party for later this week? Anyone with experience in leading such a "party"? I could volunteer to do the next one if I can just see how this is done at first. Regards, Kobus >>> karoly(a)negyesi.net 1/16/2006 9:55:33 AM >>> > How about we shift our focus instead. Instead of having "bug fixing > parties" let's have a "patch reviewing party". Or let's have both? Both for sure!

1 0

Re: [development] Re: Why Drupal 4.7 is late? (long)
by Kobus Myburgh 16 Jan '06

16 Jan '06

I agree. So, perhaps we should get some more people interested in reviewing patches more. I am new to all this, but I have tested some patches already, and given feedback. How about we shift our focus instead. Instead of having "bug fixing parties" let's have a "patch reviewing party". Or let's have both? Regards, Kobus >>> karoly(a)negyesi.net 1/16/2006 9:39:08 AM >>> > Most of my patches have been submitted for over a week, with status > "code needs review" but nobody has even looked at it. I also told numerous times (even posted to drupal.org frontpage) that we are short on reviewers. It's also part of the "can't cope with the load" stuff :(

2 1

Re: [development] Re: Why Drupal 4.7 is late? (long)
by Kobus Myburgh 16 Jan '06

16 Jan '06

Hi Karoly (and other senior Drupal developers), I have submitted my first patches for Drupal over the last few weeks (think: baby steps - I am only starting developing now and have relatively low PHP/Drupal knowledge compared to you guys). While I am not oblivious to your statements, Karoly, I will nevertheless be the Devil's advocate here. Most of my patches have been submitted for over a week, with status "code needs review" but nobody has even looked at it. Yes, one of them were committed (Capitalized 'D' for Drupal), but the bulk of them weren't even looked at. One such bug that I submitted a patch for was for form.inc (http://drupal.org/node/43131) which is the main topic of the foregoing discussion, which still didn't even get a single reaction since it was posted on the 3rd of January. I think the fact that people's patches don't get attention discourage them to submit more patches and to get involved. If you look at http://www.drupal.org/user/74/track/ (the only way I could get other people to see my patches - alternatively you can try http://drupal.org/project/issues/search and search for "bug reports" assigned to "Kobus"), you will see that I have 4 patches with "code needs review" status. I am helping where I can, where my skill level allows, but I feel that the patches don't get attention. I have respect to the fact that everyone else is busy, and have their lives, but think the following scenario: 1. You are a builder 2. You have 20 people working under you If you are only capable to supervise 15 people at any given time, would it really help to increase the people under you to 30? Basically, what I am saying, is we need more people involved with tackling patches that are *already* in the system first. That way people will feel more willing to help out. If anyone feel that I am *completely* wrong here, I am open for some more discussion. Regards, Kobus >>> karoly(a)negyesi.net 1/15/2006 7:05:38 PM >>> Folks sorry to be rude, but this is off topic. So far, only Drumm has seeked me out in private and offered a helping hand in fixing bugs. There are enough bugs for a roman legion. All hands on board! >> webchick did an example of how a .install file should look like: >> http://drupal.org/node/43492

2 1

[Fwd: LinuxTag with "Information Web" Track (3 more days to CfP!)]
by Gabor Hojtsy 15 Jan '06

15 Jan '06

Hi guys, Someone preparing a session for LinuxTag? A lot of other CMS players are there. Only three days to go until the CfP deadline. Goba

5 6

Forms API #id questions
by Robert Douglass 15 Jan '06

15 Jan '06

I'm in the habit of giving nearly every form element an #id because I've been doing lots of AJAX stuff and always have the need to grab things in the DOM. Can someone comment on this bit of instruction: http://drupaldocs.org/api/head/file/contributions/docs/developer/topics/for… Is the use of #id discouraged? Why is there no #id property allowed on hidden form elements? Thanks Robert

3 2

Forms API Documentation . . .
by Jason Flatt 15 Jan '06

15 Jan '06

Last Monday I started working on an internal site that will consist primarily of web forms. There is a great potential of literally a hundred or more forms (some of them are quite complex), but I am really just setting my sites on a core of 10-20 forms for now. For this project, I chose to just start with the 4.7 beta and the new Forms API, as I thought it would be very counter-productive to learn the 4.6 API and then upgrade in a month or two to the 4.7 API. I am not new to using and administering Drupal, but I am new to coding to it and am trying to go through the documentation for the Forms API, but I feel like either there is not enough, or I am not finding it. What I have found and gone through so far is 1) Forms API Outline [0], which doesn't have any real meat, AFAICT. 2) Forms API Quickstart Guide [1], which is a great starter guide, thanks webchick. (BTW, where is this document: "For more detailed information, also see the developer documentation [link coming soon]"? It may be the next document I'm looking for.) 3) Most of what is in Upgrading to forms API [2], except the actual upgrading parts, since I am starting from scratch in 4.7. 4) And then there is Form generation [3] and Forms API Reference [4], which are really only useful if I already have a clue and I'm looking for the details about a specific function or attribute. So, the question is, is there anymore that I have not located that will help me move to the next level? Also, I am not yet at the point where I need it, but I will be soon looking for database integration, both reading and writing, possibly with a different database that the main site will be using. Is that something that is part of the Forms API, or is it a separate API? Thanks. [0] http://drupal.org/node/37775 [1] http://drupaldocs.org/api/head/file/contributions/docs/developer/topics/for… [2] http://drupal.org/node/33338 [3] http://drupaldocs.org/api/head/group/form [4] http://drupaldocs.org/api/head/file/contributions/docs/developer/topics/for… -- Jason Flatt http://www.oadae.net/ jason(a)oadae.net

1 0

create a star rater using css
by Adrian Rossouw 14 Jan '06

14 Jan '06

http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star- rater-using-css/ http://komodomedia.com/blog/index.php/2006/01/09/css-star-rating-part- deux/ I found this tutorial via digg. I thought it might be useful to the people working on the voting API etc. Also, found this interesting point in the comments : "The 4-star system is superior to the 5-star system in every way. Discuss!" According to my economics teacher, 4 star (or any even number) is better than 5 star because people will often decide upon the median grade if they aren't shure if they like something or not. using even numbers forces a person to think about if they like or dislike something in the slightest -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

9 19