[Prototype-core] Re: Lag between click and invocation of event handler in IE
Hi Marco, This list is for discussion of the actual development *of* Prototype. Would you repost your question on the user's list: http://groups.google.com/group/prototype-scriptaculous Thanks, -- T.J. Crowder Independent Software Consultant tj / crowder software / com www.crowdersoftware.com On Apr 9, 5:26 pm, marcoow wrote: > Hi list, > > I have some JS code that listens to click events on links. In IE I see > a reasonable lag (around 1 sec.) between the actual click and the > invokation of my event handler. Is there any typical reason for that? > My JS attaches around 50 event handlers on the page in question. > > Can provide code if neccessary but I thought there might be a typical > reason for lags like this? Something that's very likely the case of my > problem? > > Thanks for help, > Marco -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Lag between click and invocation of event handler in IE
Hi list, I have some JS code that listens to click events on links. In IE I see a reasonable lag (around 1 sec.) between the actual click and the invokation of my event handler. Is there any typical reason for that? My JS attaches around 50 event handlers on the page in question. Can provide code if neccessary but I thought there might be a typical reason for lags like this? Something that's very likely the case of my problem? Thanks for help, Marco -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: API Documentation "Sections"
Done. On Apr 9, 6:33 am, gf3 wrote: > BAM. > Done:http://github.com/gf3/pdoc/commit/55f6628be7fc5f91b7602ced0fddd5617db... > > On Apr 8, 10:23 am, Tobie Langel wrote: > > > > > May I suggest someone fix this and send me a pull request? > > > Best, > > > Tobie -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
Tobie, I'm just not going to continue this, it's a pointless aggravation for both of us. Have a good one, -- T.J. On Apr 9, 1:10 pm, Tobie Langel wrote: > > Oh for cryin' out loud, Tobie. There are roughly 50 wiki engines out > > there that make contributing a darn sight easier than using flippin' > > git. But: > > Hosted, fully style-able wikis with an integrated blog engine, which > allow inclusion of static HTML pages (the generated API doc), and can > live on their own domain name for less than $7/month ? > > Yes please!! -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
> Oh for cryin' out loud, Tobie. There are roughly 50 wiki engines out > there that make contributing a darn sight easier than using flippin' > git. But: Hosted, fully style-able wikis with an integrated blog engine, which allow inclusion of static HTML pages (the generated API doc), and can live on their own domain name for less than $7/month ? Yes please!! -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
Mislav, Fair nuff. I'm not going to argue the point, though I think one could argue it from a ... no, wait, saying "from a ___ perspective" would be arguing the point, and I'm not going to, because: 1. It's not my project 2. It's not my project (I think it's worth saying twice) :-) 3. The people *actually running the project* have made their decision 4. GitHub makes life fairly easy for people who don't use git, so this whole discussion was pretty much unnecessary. You don't need git to help out. You just need a browser. Thank you again for pointing that out. -- T.J. On Apr 9, 12:29 pm, Mislav Marohnić wrote: > On Fri, Apr 9, 2010 at 09:47, T.J. Crowder wrote: > > > We'll have to disagree on that, then, and it's your project. For a > > project I was running, I would consider it a completely unacceptable > > barrier to non-code contribution. > > From my experience: I'm working on an open-source project right now for my > employer. This project has had a number of contributions over the past 3 > weeks (since I started), most of them coming from people that don't know > git. These contributions were translations, design changes, copywriting. It > was generally more difficult and time-consuming to merge in changes > submitted by people who didn't use git than from people that did. Also, > patches from people generated by git were generally more quality. > > I fully back Tobie's decision to set up some bar for contributors. -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
Re: [Prototype-core] Re: Helping with the web site once it's on github
On Fri, Apr 9, 2010 at 09:47, T.J. Crowder wrote: > > We'll have to disagree on that, then, and it's your project. For a > project I was running, I would consider it a completely unacceptable > barrier to non-code contribution. >From my experience: I'm working on an open-source project right now for my employer. This project has had a number of contributions over the past 3 weeks (since I started), most of them coming from people that don't know git. These contributions were translations, design changes, copywriting. It was generally more difficult and time-consuming to merge in changes submitted by people who didn't use git than from people that did. Also, patches from people generated by git were generally more quality. I fully back Tobie's decision to set up some bar for contributors. -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
Tobie, > I'd like the perfect solution as much as anybody, I just haven't > bumped into it yet. > > If you have, please speak up. If not, please spare me that kind of > remarks. They're just completely counter-productive Oh for cryin' out loud, Tobie. There are roughly 50 wiki engines out there that make contributing a darn sight easier than using flippin' git. But: > P.S.: For the record. Mislav's right, you can fork the project and > edit it in the browser. Excellent! So minimum requirement is a browser. -- T.J. On Apr 9, 10:55 am, Tobie Langel wrote: > > > I think I can live with that. > > > We'll have to disagree on that, then, and it's your project. For a > > project I was running, I would consider it a completely unacceptable > > barrier to non-code contribution. > > I'd like the perfect solution as much as anybody, I just haven't > bumped into it yet. > > If you have, please speak up. If not, please spare me that kind of > remarks. They're just completely counter-productive > > Thanks. > > Tobie > > P.S.: For the record. Mislav's right, you can fork the project and > edit it in the browser. -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
> > I think I can live with that. > > We'll have to disagree on that, then, and it's your project. For a > project I was running, I would consider it a completely unacceptable > barrier to non-code contribution. I'd like the perfect solution as much as anybody, I just haven't bumped into it yet. If you have, please speak up. If not, please spare me that kind of remarks. They're just completely counter-productive Thanks. Tobie P.S.: For the record. Mislav's right, you can fork the project and edit it in the browser. -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
[Prototype-core] Re: Helping with the web site once it's on github
@Tobie: > > Mind you, it seems to me even git is a barrier to casual helpers, if > > they don't already use it. > > I think I can live with that. We'll have to disagree on that, then, and it's your project. For a project I was running, I would consider it a completely unacceptable barrier to non-code contribution. @Mislav: > People can edit pages from the website and preview the result in their text > editor if it supports Textile/Markdown. That's a feature of GitHub? Browser-based editing of content? The content Tobie's talking about (as opposed to other stuff)? If so, result! -- T.J. On Apr 8, 7:46 pm, Mislav Marohnić wrote: > On Thu, Apr 8, 2010 at 18:34, T.J. Crowder wrote: > > Thanks. Purely git? Not ruby (unless you also want to install Jekyll)? > > People can edit pages from the website and preview the result in their text > editor if it supports Textile/Markdown. Jekyll is only needed if they want > to generate the complete site to see how will a reflect when put online (not > necessary in most cases). > > Speaking of Textile/Markdown, we're going to standardize on Markdown, right? > I think that we should get rid of all Textile in this process, then? I > recall we started with Textile on Mephisto but eventually started writing > mostly in Markdown. -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en To unsubscribe, reply using "remove me" as the subject.
