[Prototype-core] Re: Kudos to the documentation team
If you're on a PC you can adjust your wheel-scroll settings in Control Panel - Mouse - Wheel. I think the default is 3 and I usually adjust mine up as well. On Apr 6, 7:15 am, joe t. thooke...@gmail.com wrote: +1 for the scrolling. The navigation between documentation links has much improved, but the navigation panel still has issues. The wheel- scroll is painfully slow. Even clicking in the scroll bar doesn't work as expected. When you click a position in the scroll bar, usually it jumps to where you clicked. Otherwise, the documentation itself is phenomenal, and thanks to all! -joe t. On Apr 5, 5:19 pm, Joost joost.van.do...@gmail.com wrote: I have the same problem, because I like to use google to search for stuff in the documentation but I end up on the old one. Also I think the mouse wheel scrolling in the menu onhttp://api.prototypejs.orgis way too slow and should be fixed (it takes 10 seconds for me to scroll down with the mouse wheel..). Good work on the improved docs though. -- 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: Kudos to the documentation team
A HTTP 301 seems a better solution as it stands for Permanently redirected to a given URL... the header should look like : HTTP/1.1 301 Moved Permanently Location: http://www.newurl.com/ 2010/4/6 Tobie Langel tobie.lan...@gmail.com A practical solution would be a well designed 404. We could get pdoc to generate it with a search field, etc. We could also try JS redirection. Anyone wants to give it a shot? Best, Tobie On Apr 6, 8:42 am, T.J. Crowder t...@crowdersoftware.com wrote: My coworkers still find old docs (http://prototypejs.org/api) by googling. I had to point them to new doc site. I think it's crucial to set up 301 redirects. *ONLY* if all of the old information has now been ported over. Looking at the documentation Lighthouse project[1], it looks like all of the old merge/update tickets have been closed (yay!), which may mean exactly that, someone from the docs team can presumably confirm that. Once we're ready, 301s that live in those locations for a long, long time are indeed appropriate. Or if 301s are hard in Mephisto, replacing each of the API documentation articles with a link to the new one. [1] https://prototype.lighthouseapp.com/projects/42103-prototype-document... -- T.J. On Apr 5, 3:30 pm, Mislav Marohnić mislav.maroh...@gmail.com wrote: On Mon, Apr 5, 2010 at 11:48, Johan Arensman johanm...@gmail.com wrote: Wow! I didn't even realise they were updated until I read this message. Very nice work indeed! My coworkers still find old docs (http://prototypejs.org/api) by googling. I had to point them to new doc site. I think it's crucial to set up 301 redirects. -- 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. -- 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
Re: [Prototype-core] Re: Kudos to the documentation team
BTW, if the .htaccess file is not accessible or cannot be updated, it is still possible to redirect from the server-side language used (header() for instance with php)... 2010/4/6 Robert Kieffer bro...@gmail.com Urm... really? You can do 404's but not 301's? Not saying I don't believe you, I'm just surprised that a project as mature as prototype is hosted in an environment that doesn't support basic .htaccess-style configuration. On Tue, Apr 6, 2010 at 6:12 AM, Tobie Langel tobie.lan...@gmail.comwrote: Robert, that would be great. We unfortunately don't have this level of access to the server. -- 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. -- 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 -- 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
[Prototype-core] Re: Kudos to the documentation team
Tobie, Can we use JavaScript on Mephisto pages? -- T.J. On Apr 6, 6:49 pm, Tobie Langel tobie.lan...@gmail.com wrote: Urm... really? You can do 404's but not 301's? I was suggesting crating a good 404 page. Not modifying the http response code. Not saying I don't believe you, I'm just surprised that a project as mature as prototype is hosted in an environment that doesn't support basic .htaccess-style configuration. There's historical reasons to this. We're in the process of migrating, though (not that this will change much in terms of low-level access). 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: Kudos to the documentation team
Agreed, and it appears to be specific to Firefox. However, i can't recall any other circumstances (iframe, CSS overflow, etc) where the scroll bar behaves differently. The new API page is the only time i've seen this behavior. Peculiar. Oh well, it's hardly the end of the world. :) -joe t. On Apr 6, 8:31 am, Mislav Marohnić mislav.maroh...@gmail.com wrote: The scroll bar is native to the browser, meaning it's the same as in a regular window, iframe or frameset. The navigation panel should scroll with same methods and speed as every window in your browser.On Tue, Apr 6, 2010 at 14:15, joe t. thooke...@gmail.com wrote: +1 for the scrolling. The navigation between documentation links has much improved, but the navigation panel still has issues. The wheel- scroll is painfully slow. Even clicking in the scroll bar doesn't work as expected. When you click a position in the scroll bar, usually it jumps to where you clicked. -- 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: Kudos to the documentation team
Can we use JavaScript on Mephisto pages? -- T.J. Yes, but we're moving away from it. -- 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] Roadmap
This is a continuation of the discussion started here: http://github.com/sstephenson/prototype/commit/2f9bde3ad5a2e3dd104c812b6c81f4077fe0aa1e#all_commit_comments It would be very helpful to see some sort of Prototype roadmap or at least be able to see internal discussion about the development of the library. Not only from a personal interest standpoint but I also receive a lot of questions on IRC regarding what Prototype is doing, what's happening with development, c. Unfortunately, right now, I don't really have an information that I can pass on. Tobie mentioned a public read-only interface to internal discussions – this would satisfy my needs. Although a formal roadmap may be beneficial to core devs as well. -- 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] Roadmap
I agree that a road map would be helpful. In addition to the reasons gf3 mentioned, I think it would make it easier to contribute. Allen Madsen http://www.allenmadsen.com On Wed, Apr 7, 2010 at 4:53 PM, gf3 giannichiappe...@gmail.com wrote: This is a continuation of the discussion started here: http://github.com/sstephenson/prototype/commit/2f9bde3ad5a2e3dd104c812b6c81f4077fe0aa1e#all_commit_comments It would be very helpful to see some sort of Prototype roadmap or at least be able to see internal discussion about the development of the library. Not only from a personal interest standpoint but I also receive a lot of questions on IRC regarding what Prototype is doing, what's happening with development, c. Unfortunately, right now, I don't really have an information that I can pass on. Tobie mentioned a public read-only interface to internal discussions – this would satisfy my needs. Although a formal roadmap may be beneficial to core devs as well. -- 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. -- 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
