August 2007 - Development - lists.drupal.org

jQuery animation help?
by Morbus Iff 02 Aug '07

02 Aug '07

G'day. I'm using the wrong list. Woohoo! I have a DIV full of lots of items. Images, more DIVs, more images, words, sentences, whee, fun, fun. It is a large DIV. I'd like: * on page load, for the DIV to show at (smaller) px x px. * on mouseover/hover, the DIV to enlarge to (full) px x px. * on mouseout, the DIV goes back to its onload size. * everything in the DIV should resize - the images should get bigger, the fonts should get larger and smaller, blah blah. What is /really/ close is the Grow/Shrink/Puff of Interface: http://interface.eyecon.ro/demos/ifx.html However, I can't make it NOT disappear, and the interface.js can only be found in a packed state, not one I can look into the source about how to stop it from disappearing. (Note, also, that the Interface demo is onclick, but I'd be looking for over and out). 'elp? Morbus Iff morbus(a)disobey.com Not my normal computer

4 5

channels
by Karoly Negyesi 01 Aug '07

01 Aug '07

Hi, Derek nicely summed up: Either: 1) #drupal-support should be closed and #drupal repurposed to be the support room. 2) #drupal should be a level of indirection (as per my original email in this thread 3) #drupal can remain in whatever weird, intermediary state it's in now. 3) is undesireable. 1) is also undesireable I believe because people will have harder time finding the dev channel, the theme channel, the whatever. The announcement should actually encourage them to lurk in #drupal-dev and ask devel questions there. I always found it baffling that support deals with coding as well. This leaves 2) Unless I get *very* convincing arguments against it, I will act on that. Given the activity of the room and my time to code just a bot based on bot module, let's call the day next Monday. Kind regards, NK

14 26

CK-ERP (Open Source ERP / CRM / MRP) v.0.23.1 released (with Drupal 5.2 connector)
by C K Wu 01 Aug '07

01 Aug '07

Hi, folks, I have posted a new release, v.0.23.1, of CK-ERP, at SourceForge.Net, http://sourceforge.net/projects/ck-erp . This release features connectors for MirrorMed, ClearHealth, OpenEMR, and osCMax. XOOPS connector has been enhanced to provide group-module ACL control. Locale-aware monetary figure printing has been added. Sample cheque format has been improved. [For locale-aware monetary figure printing to operate correctly, the server machine must have the relevant locales correctly implemented.] CK-ERP is an open source accounting/MRP/ERP/CRM system that runs on top of multiple middlewares. It comprises 22 modules - Administration, i18n, Contact Management, Customer Relationship, Customer Self Service, Vendor Relationship, Ledger, Bank Reconciliation, MRP, Warehouse, Inventory, Service, AP, AR, PO, SO, Quotation, POS for Cashier, POS for Manager, HR, Staff Self Service and Payroll. Operating platform can either be LAMP or LAPP. It provides accounting and back office functionalities to SMEs and utilizes the underlying middleware to administer accounts/groups. Please report error and suggestion to the discussion group / mailing list, CK-ERP-en(at)googlegroups.com or CK-ERP-zh_CN(at)googlegroups.com . General history and expected development is available at the discussion group's Archive. Supported MiddleWares: MirrorMed, ClearHealth, OpenEMR, eGroupWare, Horde-GroupWare; Zencart, CRELoaded, osCMax, osCommerce; Drupal, Joomla, Mambo, e107, XOOPS, Xaraya; Moodle, Atutor; vTiger, XRMS; WordPress, b2evolution; TikiWiki; phpBB. Information/Demo Websites: http://ck-erp.org http://ck-erp.net http://ck-erp.com Download is available from, http://sourceforge.net/projects/ck-erp http://gforge.oss.org.cn/projects/ck-erp http://gf.cs.hit.edu.cn/projects/ck-erp http://www.cnforge.org/modules/xfmod/project/?ck-erp http://gro.clinux.org/projects/ck-ledger Cheers, Wu Chiu Kay, aka CK Wu, aka CK (CK is the preferred alias) Hong Kong

1 0

channels, continued
by Karoly Negyesi 01 Aug '07

01 Aug '07

Hi, Let me write a bit about motives... If there would be a healthy discussion on this topic which would further us, it'd be great. There is none. Noone has written anything that caused someone else to change her/his view. What's the point in continuing then sending emails around? This is not a discussion. So someone needs to make the decision which will piss some people off. I tried to count the people who will be pissed off by going this way, and the mental list is, I believe, one people long. So, I would like to apologize in public to Gerhard. Sorry. Regards, Karoly Negyesi

1 0

Re: [development] #drupal / #drupal-dev split considered harmful
by Chad Phillips -- Apartment Lines 01 Aug '07

01 Aug '07

On Jul 31, 2007, at 6:19 PM, Angela wrote: > Since the people who founded #drupal-dev are the ones who rocked > the boat, I believe it is their responsibility to steer us to our > final destination. So what's it going to be? Are you guys going to > hang out in #drupal and answer support questions all day? Or are > you going to come back to the fold? i don't see how this follows. i'm guessing most left precisely because they didn't want to answer support questions, and #drupal spends a fair portion of it's time fending them off. the response seems logical to me, given their objective.

1 0

Re: [development] #drupal / #drupal-dev split considered harmful
by Larry Garfield 01 Aug '07

01 Aug '07

#drupal-support already has a fair share of friendly helping people. If they migrated to #drupal and #drupal-support shut down, problem solved. As I said, having both #drupal-support and #drupal-dev is a problem. #drupal should be definitively one or the other. Freenode standard would be that it's the support channel, but as long as it's one or the other I don't have a strong preference. --Larry Garfield On Wed, 1 Aug 2007 03:01:04 +0300, "Ashraf Amayreh" <mistknight(a)gmail.com> wrote: > I agree with Mark, why the fuss? #drupal should actually be the place where > newbies go to. While the more specific and oriented channels should be the > less obvious ones because they're for the seasoned developers who most > likely have come to know the channels by heart. > > Anyone who goes off to search for drupal help will most certainly guess > that > #drupal is the place for that. If it's for the sake of preventing people > from entering and leaving the room immediately after seeing the message, > that seems like a good enough reason. Also, what harm could possibly > result > in that? I mean what're the -ves? The only thing I could worry about is > causing a starvation in the support channel, leaving the newbie's high and > dry, so to speak. Otherwise this seems perfectly logical. #drupal for > support, #drupal-dev for development, now the question of how to prevent > knowledge starvation in the support channel is a different thing, the best > support people are obviously the developers themselves, suggestions? > > On 8/1/07, mark burdett <mfburdett(a)gmail.com> wrote: >> >> On freenode, the big unhyphenated channels like #ubuntu, #gentoo, >> #debian, #rubyonrails are open to support questions. Then you have >> more specialized channels for developer discussion like #mysql-dev, >> #kde4-devel etc. >> >> You can find a similar pattern on lists for many FOSS projects, e.g. a >> "project" list and "project-dev" list. >> >> --mark >> >> On 7/31/07, Khalid Baheyeldin <kb(a)2bits.com> wrote: >> > >> > >> > > As I understood it was: >> > > >> > > #drupal - development focused >> > > #drupal-support - support focused - for newbies >> > > >> > >> > The problem is that #drupal is the first place newbies will think >> > of to get support. Once they are there, they are greeted with the >> > "support?" reply telling them to go to #drupal-support. >> > >> > This can be offputting and make people feel unwelcome. They >> > ask the first question and get a reply that amounts to : "we don't >> > serve your type here, buzz off!" (plagiarised from Esmerel) >> > >> > So, I don't see why charters can change, with development >> > in #drupal-dev (and only development), then #drupal become >> > community focused, has support, infra discussions, and everything >> > else that is not development. >> > >> > >

1 0