I like cooktop ver2.5, but have just got VS.Net, and am trying to figure out how it can work with XML.
-
Re: what are you using for your editor?
Mon, December 8, 2003 - 1:24 PMBelieve it or not, I'm usually doing XML by hand or generating it via Perl. I don't do a lot of XML coding on the desktop. I've never worked with Cooktop or VS.Net (perhaps since I'm a Mac/Unix user). Sorry I can't help. -
-
Re: what are you using for your editor?
Tue, September 13, 2005 - 8:49 AMI do XML by hand, too. I like TextPad.
-
-
Re: what are you using for your editor?
Mon, September 12, 2005 - 6:44 AMThe only precautionary thing about this excellent free editor is that Cooktop 2.5 saves files in the editor, without asking, before running various tools such as XSLT transformations and validation. (Assume that Cooktop will overwrite your file with the current contents of the editor at any given time!) This will speed up the editing process - so you will be generating code rapidly...!
Every other editor I have suggests making a backup first. TextPad is cautious about overwriting originals and Vedit even makes a backup which it stores when you open the file.
But I, too, am looking for people's ideas on a "perfect" IDE for XSLT. So anyone know? I appreciate it!
-
-
Re: what are you using for your editor?
Mon, September 12, 2005 - 10:37 PMVi is great in a UNIX/Linux environment. But for Windows and generating really fast slick code in a proper IDE, I would have thought VI would be rather hard. CookTop actually separates all the different components of XSLT, and for freeware, I think it is brilliant.
I have seen variants of the Vi editor in Windows too. There are other flavors in Linux like Vim. What do you like about using vi to generate XSLT in UNIX, Roger? -
-
Re: what are you using for your editor?
Tue, September 13, 2005 - 6:21 PMThere are times when I do like a full blown IDE, such as XCode for Cocoa development, or Eclipse for J2EE projects.
A lot of times though, I'm just working with a few files. I don't need to worry about libraries of Java or Obj-C classes, nor deal with linking and compiling. At those times, I just want a really quick, simple, yet powerful, editor that's going to stay out of my way and let me work. For me, vi (well, VIM actually) does the job. This is usually the case working with XML and XSL. I have a few templates for boilerplate, a few macros for common tags and blocks, Saxon for XSLT processing, and that's about all it takes.
r.m.
-
-