Hi Daniel, you don't say what OS you use. This can make a big difference, especially if you're familiar with shell scripting. I use Ubuntu Linux, have a local apache service running which is configured out of the box for user dirs (ie. http://localhost/~mark - served from /home/mark/public_html). I have a common dir in there containing jQuery & UI - these are updated, built and copied there from the svn working-copies elsewhere in my filesystem by a short custom shell script. I use rsync to then sync all of this up to a public web-server hosted by my company. For editing I use the very understated GEdit which is part of Gnome desktop, and the snipets plugin - which insert all the boiler plate html/js I need - I did briefly try a couple of web-dev env's but just found them annoying. While on this, I'd be interested to know what editors (or even IDE's) people use for JS/jQuery work. I've not really found any that can handle a functional language such as JS all that well. Personally I can't stand bulky IDE's (such as Eclipse) that insist on managing projects for you and eat all your resources.
2009/3/13 Daniel Friesen <nadir.seen.f...@gmail.com>: > > I'm wondering what kind of tricks and setups other people have when they > are developing with jQuery. > Be it writing some improvements to jQuery itself, or writing a plugin. > I'm not really looking for those using jQuery in an application, cause > that environment is normally just taking a few jQuery files and plugins > and including that into your existing development environment. > > I'm trying to find out how people (plugin and core jQuery developers) > normally handle their development environment for working on jQuery or a > jQuery plugin. > > Every time I work on another piece for jQuery, I end up creating a new > html file, which normally consists of either copying some junk from > another project and modifying it, or constructing a new one by grabbing > a doctype and a few tags off some references on the internet. I also end > up grabbing jQuery again to shove in and include. > As for actually testing stuff, I normally might just go off the > filesystem, however sometimes that doesn't quite work right, and I end > up needing to configure a local webserver (normally I just edit the > config for my local nginx). > Things get real ugly when working on patches to jQuery core itself. > Mostly because of needing to `make jquery` all the time. Sometimes I end > up sitting there for a few minutes trying to figure out "why the hell > didn't my edit fix this bug?" then realize I forgot to rebuilt jquery > before I refreshed the page to test it. > > All in all, I don't really consider it a nice and clean, or even helpful > environment. > For that reason I've actually started experimenting with building a > Rails app to manage projects and streamline things like creating html > pages from templates, previewing a page and working on code live, as > well as nice integration for github forks of jQuery (fork/clone as in > gitspeak), jQuery svn, and different versions of jQuery. > > -- > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
