May 2006 - Development - lists.drupal.org

RE: 5.0 and or 4.8 (was Re: [development] Drupal x.x.0 freeze date)
by Boerland, Bert 03 May '06

03 May '06

-----Original Message----- From: development-bounces(a)drupal.org > The 4.5 to 4.6 roadmap while interesting was in my opinion a fairly > interesting boondoogle. It might have been "boondoogle", but I wouldnt have called the 4.5/4.6 a roadmap. IMHO drupal might needs some form of a roadmap written down. We tend to forget that we /do/ have a roadmap, it is just all over the place (like the real roads) in people's heads (like a mind map). Writing it down, adjusting it on the fly, will do wonders for outsiders (potential users/customers, developers etc) The reason we don't have a roadmap, is twofold. One: we don't /need/ a roadmap and two we don't /want/ a roadmap. The second reason is mostly because people are afraid it will be fixed. Roadmaps aren't fixed, roads can change, so can roadmaps, they are not rigid. The first reason is from /our/ point of view valid, however we are not alone in this world and it will create new opportunities for Drupal from an outsiders POV if we did have a roadmap.

6 5

SoC - ImageMagick integration for Drupal
by Novák Áron 03 May '06

03 May '06

Hi, I'm working on a Summer of Code application. The finished and well done projects will be the part of the 4.8 release, won't be? So what is the requirement of the code in the question of the PHP version? Is the backward compatibility ( to 4.x PHP) important in the future releases? On the other hand the Drupal don't attached to a specific platform so the ImageMagick - module would work fine with various platforms. Is it a necessity to test a new module in various environments or the developer community (this mailing list for example) will help to make the new stuff environment-independent? I hope that after my exams I'll have a chance to make something useful for Drupal! Thanks, Aron Novak

3 6

Drupal Test Suite
by Nimish Pachapurkar 03 May '06

03 May '06

Hello, Some months ago, I had inquired about the current state of the Drupal test suite in this forum. At that time there were some issues in running the simpletest module for Drupal 4.6.5. A team at SpikeSource, Inc. (http://www.spikesource.com) - where I work - has recently developed a test suite for Drupal that comprises of 5925 functional tests that exercise more than 50% of the code. This test suite runs against both MySQL and PostgreSQL back ends. The test suite is developed using following open source tools: * TestGen4Web: Used for recording user actions through browser and then translating them into SimpleTest test cases. http://developer.spikesource.com/projects/testgen4web/ * SimpleTest: PHP unit and functional testing tool. (http://www.lastcraft.com/simple_test.php) * PHPCoverage: PHP line coverage measurement tool. (http://developer.spikesource.com/projects/phpcoverage/) Currently, the test suite works against a deployed and configured instance of Drupal 4.6.6 with 99.98% tests passing. (SimpleTest counts each assertion as a test case.) The test suite covers following modules in addition to the core modules. * article * event * fckeditor * flexinode * image * img_assist We would like to contribute this test suite so that more people can add to it and improve it. Please let me know if anyone might be interested in taking a look at it and carrying this discussion forward. Thanks, Nimish -- SpikeSource, Inc.

5 7

recursive book functionality?
by Derek Wright 03 May '06

03 May '06

anyone ever heard of (or worked on) efforts to make the book module function more recursively? by this, i mean: 1) "add child page" should inherit all the node metadata of the parent page (publishing options, access control/node visibility settings, etc) 2) providing a way to do an operation on a book page and all its children recursively (like setting a publishing option, ACL, etc). is this new territory? any suggestions before i roll up my sleeves and start hacking? is book going to be completely deprecated in the short term by new-fangled "views + cck makes everything obsolete" talk? ;) i'm hopeful that i can do all this as a contributed "recursive_book.module" that just uses nodeapi and form_alter(). am i being naive to think that's all i need? any suggestions on a better name for the contrib module? (can you tell i'm a computer scientist for my day job, not a web designer?) ;) any wisdom or pointers would be greatly appreciated. anyone else care about this functionality? anyone know of anyone who'd be willing to pay for it? ;) thanks! -derek (dww)

1 0

parseJson behaves differently under PHP 5.0
by Dan Robinson 02 May '06

02 May '06

Folks, I am doing some AJAX stuff and it looks like parseJson may be handling arrays differently between PHP 4.x and 5.x. When using parseJson this is dumped under PHP 4.x { 0: { 0: "47", 1: "-122", 2: "Mr Dan Robinson" }, 1: { 0: "47.5", 1: "-122.5", 2: "dan(a)foobar.org" }, 2: { 0: "47.75", 1: "-122.6", 2: "George Robinson" } } and this in 5.x [ [ "44.4966", "-75.073", "Mr Anne C Jones Jr" ], [ "32.2153", "-98.208", "Mrs Sheila X Yadav Sr" ], [ "34.9967", "-85.2375", "Dr Michael M Patel Jr" ] ] Different data obviously - same code. Hints appreciated, Dan

4 7

RE: 5.0 and or 4.8 (was Re: [development] Drupal x.x.0 freeze date)
by Steven Peck 02 May '06

02 May '06

The 4.5 to 4.6 roadmap while interesting was in my opinion a fairly interesting boondoogle. Part was people ended up working on other things then they thought, either due to life, paying work or better/different ideas, some disappeared and some stuff just didn't get done. We got people who would look at the 'roadmap' and then chastise the dev community or rant using the roadmap as there justification. It was annoying. -sp > -----Original Message----- > From: development-bounces(a)drupal.org > [mailto:development-bounces@drupal.org] On Behalf Of Earl Miles > Sent: Monday, May 01, 2006 8:16 PM > To: development(a)drupal.org; kb(a)2bits.com > Subject: Re: 5.0 and or 4.8 (was Re: [development] Drupal > x.x.0 freeze date) > > Khalid B wrote: > >> It is fair, one can have ones own view of what they like > or dislike > >> without the concerns of others yet wishing others can help to test > >> and comment on their pet features. It is pretty sad if > this is the main > >> stream thoughts from developers - I hope this is not the > case. But of > >> course, we all like no rules and no obligations ;-). > > > > > > Jenny > > > > This is Open Source development. It does not happen because > corporate > > marketing mandates a feature, or someone up high in the hierarchy > > orders it down the command chain. > > > > It is mainly a scratch your itch thing. Someone's itch may be > > something relating to a web site they own and run, another person's > > itch is their > > non- > > profit clients, yet another would be commercial clients, > yet another > > would be scalability for a hosting provider, ...etc. > > > > We cannot force everyone to a herd mentality or a hive > mind. If others > > want a feature in, they write it, they lobby for it, they convince > > others of its value. > > I will only object if I see that this breaks something else, or is > > bloated, or whatever. > > > > In my view, the features have to be the collective sum of > pet features > > that people who chose to propose them and put the effort to > make them happen. > > > > So, it is not as pessimistic as you understood it to be, or > as you may > > sound to you. > > I do think that the one positive to the 'roadmap' argument is > to put together what people are working on. Not so much a > "This is waht will happen" but a projection of how things > look now. Even with the knowledge that this isn't a promise, > and is malleable, it can help people out by identifying areas > that could use help, should someone wish to pitch in, and it > can identify areas that are well covered so that people don't > end up butting heads trying to scratch the same itch. > >

4 4

File caching patch for Drupal 4.6 and 4.7
by Kieran Lal 02 May '06

02 May '06

Hello, we have updated the file caching patches for 4.6 and 4.7. This work was funded by http://goodstorm.com and http://ondemand- network.com. It was developed by Jeremy Andrews for CivicSpace. File caching for Drupal 4.6 http://drupal.org/node/61227 File caching for Drupal 4.7 http://drupal.org/node/45414 We will try to get this in Drupal 4.8 now that it has opened up. Please test and respond to the appropriate issues. Kieran

5 5

personal battle plans
by Dries Buytaert 02 May '06

02 May '06

In good tradition: http://drupal.org/node/61397. -- Dries Buytaert :: http://www.buytaert.net/

2 1

RE: 5.0 and or 4.8 (was Re: [development] Drupal x.x.0 freeze date)
by Boerland, Bert 02 May '06

02 May '06

-----Original Message----- From: development-bounces(a)drupal.org > (currently at Internet Identity Workshop in San Francisco trying to > figure out a good standards-based replacement for Drupal dist auth) well, this [1] feature request is 3 years old, but still valid [1] http://drupal.org/node/1575

1 0

RE: [development] Time to remove poll module from core
by Steven Peck 02 May '06

02 May '06

Why don't you start submitting patches for it and later apply to become poll module maintainer. http://cvs.drupal.org/viewcvs/drupal/drupal/MAINTAINERS.txt?view=markup In general I believe Dries would rather find module owners than list himself. :) -sp > -----Original Message----- > From: development-bounces(a)drupal.org > [mailto:development-bounces@drupal.org] On Behalf Of Derek Wright > Sent: Monday, May 01, 2006 8:20 PM > To: development(a)drupal.org; rob(a)robshouse.net > Subject: Re: [development] Time to remove poll module from core > > > On May 1, 2006, at 12:14 PM, Robert Douglass wrote: > > > http://drupal.org/node/61285 > > > > Its presence in core is holding up its own development. > > i agree with the thrust of this discussion (and the > spin-offs) about slimming down core, removing not-so-core > modules from core, etc. > > however, back to the original discussion at hand: removing > poll -- does that mean i shouldn't bother working on > http://drupal.org/node/51561 at all? i'd like to see a lot > of improvements in poll, and would be willing to help work on > them, but i don't want to waste effort if it's all going to > be re-done, etc. > > should we make a group on groups.drupal.org for "poll > developers"? i wonder how many of the DEP-related activities > (e.g. all the almost-effort going into event, event > management, etc) should be moved to a group there, too. i > just created my account on groups.drupal.org, so i haven't > checked it out yet in detail, but should this be the wave of > the future for collaborative development, co-maintainers, etc? > > thanks, > -derek (dww) > > >

1 0