Bespin is relatively new, and quite frankly there are a number of bugs that kind of need to be ironed out. It doesn't have enough flexibility yet to be integrated in a nice way to be able to work on a project in the way I'd like to. ;) that doesn't mean I counted it out though. jDevCloud (the ruby app I'm working on) is going to be using one or two different editors for syntax highlighting or whatnot while editing. What one you want to use can be picked by your own preference, and in the future I intend to have bespin as one of those options when it's setup so that you can integrate it's editor into other systems.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] -Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com) -MonkeyScript (http://monkeyscript.org) -Animepedia (http://anime.wikia.com) -Narutopedia (http://naruto.wikia.com) -Soul Eater Wiki (http://souleater.wikia.com) Klaus Hartl wrote: > What about Bespin ;) > > > > On 13 Mrz., 23:01, Daniel Friesen <nadir.seen.f...@gmail.com> wrote: > >> Ubuntu Linux as well. My system actually broke last Friday so I actually >> reformatted and I upgraded to Intrepid and started experimenting with >> the 64bit version. >> >> I've been using gedit to, though I haven't been using the snippets >> plugin, I honestly can't get used to snippets in any editor. >> I have tried a number of editors; Komodo Edit was nice, but is far to >> heavy and commonly slows down. jEdit does not integrate at all with >> Gnome so it's more trouble than worth since I use the built in GVFS >> (FUSE) and bookmarking fairly extensively. I could never even get any of >> the big IDEs (Eclipse, Aptana, NetBeans) to even run on my machine. I've >> tried Geany, Scribes, and Bluefish, and none of them seam to cut it. >> >> Another option for web stuff has actually been >> heel:http://copiousfreetime.rubyforge.org/heel/ >> >> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] >> -Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com) >> -MonkeyScript (http://monkeyscript.org) >> -Animepedia (http://anime.wikia.com) >> -Narutopedia (http://naruto.wikia.com) >> -Soul Eater Wiki (http://souleater.wikia.com) >> >> Mark Gibson wrote: >> >>> 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 -~----------~----~----~----~------~----~------~--~---
