On 7/19/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:
Sorry for the reply-all, anyone not interested in this thread (aside from the rails-spinoffs list people), please let us know and we will exclude you from further responses (at least I will, heh)
As for the IDE, just downloaded the Windows version, all I have to say is... (nothing to say, speechless).
It's breathtaking, and for all intents and purposes (not having put it to any real tests yet, but just in reading the docs and toying with the interface)... it's just about perfect.
A couple of things that may exist, but if not, would make it perfect are... cross-browser debugging services (IE, FF, etc..), like breakpoints, step-through, watches, the whole 9 yards (I get all this via MS VWD or VS.NET script debugger, but I'm like the only .NET guy on this entire list)... and support for defining or dropping in additional abstraction/widgeting libraries besides mochikit, like prototype or dojo or jquery (at least I think that's what mochikit is synonymous with, haven't had a chance yet to play with it).
Now, I'll play with it some more and report back. But if I can do all that on top of the niceties you've already piled in there, this would easily become my companies standard js IDE.
Very nice job.
On 7/18/06, Todd Ross < [EMAIL PROTECTED]> wrote:Paul Colton wrote:
> Sorry to email all of you, but I am trying to get in touch with someone
> (Sam?) about getting Prototype documentation into the source tree.
While I can't fault your logic of scraping the Changelog for e-mail
addresses of people who have had patches submitted "recently," I doubt
that you'll have any luck getting a hold of Sam through us. He isn't
active in the community (rails-spinoffs) and I haven't seen any major
SVN activity for months so he's obviously not doing much with the bug
reports. He's largely absent and no one's handing out commit rights to
spinoffs/prototype (or maybe I'm just flirting with the wrong people, heh).
> We¹ve build an IDE for JS development (Aptana, slowly going public at
> www.aptana.com). We¹ve defined a documentation format, ScriptDoc (based on
> JSDoc), that allows us to either inline the docs or keep them in an external
> file (one or more). These docs then provide rich code assist during
> development. We¹ve already documented all of prototype and would love to get
> it in.
Your best bet is to submit a patch via http://dev.rubyonrails.org/ for
Prototype and hope that some day it catches his attention. I'll be the
first to admit though that it's not a very effective approach.
If you want more exposure for your project, publish HTML versions on
line and invite rails-spinoffs to take a look. There's a bunch of sharp
people on that list.
Todd Ross
P.S. I've CC'd rails-spinoffs.
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
