I'm just thinking of ways to use your same thing there for more than just the contents of the current document.

If it could handle just STDIN or a path to a file, you could use it for anything anywhere. For example, almost all of my xHtml files have embedded erb style thinggies in them which will be replaced by lovely well-formed goodness, but with your plugin, all it sees is the contents of the frontmost document.

I could easily write a textmate command that could strip out my ERB junk and replace it or even parse it and then use your tool to check it. I could make the textmate command trigger on save so I could check the XML-goodness of my pages without thinking about it.

Currently, i'd have to write a command to convert my document to xml compatible (which i would have to do either way)

then output the contents of that action into a new document

save it

then click the validate button on your palette

Ideally, i'd like to

write a command to convert my document to xml compatible (which i would have to do either way)

that then outputs the contents of that action directly into your plugin and clicks validate for me

and bind this command to command-s

The second way, I would get validations automatically for any and all XML scoped documents on save automatically.

The first way, I have to go through 3-4 steps for each document I want to validate every time I want it to validate and I have to deal with temporary files and extra windows full of parsed out junk.

I must admit that your plugin is really quite hip and I will be using it.

I just think it could be more flexible.

thomas Aylott — design42 — subtleGradient — CrazyEgg

On Dec 27, 2006, at 11:40 AM, Todd Ditchendorf wrote:

Does this thing necessarily have to be a plugin to function?

It looks like you could create an iconless application instead and launch it with a tmCommand.

There's no technical barrier to just grabbing the window's current (possibly unsaved) text from a plugin. In fact, it would probably be easier. Then again, I have no idea what a tmCommand is...

I'm looking into this, but at the moment, I'm thinking a plugin is more appropriate than a separate, pseudo-app. But I welcome input from anyone who knows more.

Todd

On Dec 27, 2006, at 10:30 AM, thomas Aylott wrote:

On Dec 27, 2006, at 9:54 AM, Todd Ditchendorf wrote:

- It only seems to recognize changes in the document after I have saved it

yeah.. this could be improved. thanks for the input

Does this thing necessarily have to be a plugin to function?

It looks like you could create an iconless application instead and launch it with a tmCommand.

That would give you the ability to parse the unsaved version by simply piping the contents of the window to a temporary file using the tmCommand.

http://www.cocoadev.com/index.pl?LSUIElement

Specifies that an application is background-only but has a UI as well (usually a floating utility window). No menu bar or Dock icon, with the exception that it may have an NSStatusItem.

thomas Aylott — design42 — subtleGradient — CrazyEgg

______________________________________________________________________

For new threads USE THIS: textmate@lists.macromates.com

(threading gets destroyed and the universe will collapse if you don't)

http://lists.macromates.com/mailman/listinfo/textmate

______________________________________________________________________

For new threads USE THIS: textmate@lists.macromates.com

(threading gets destroyed and the universe will collapse if you don't)

http://lists.macromates.com/mailman/listinfo/textmate

______________________________________________________________________

For new threads USE THIS: textmate@lists.macromates.com

(threading gets destroyed and the universe will collapse if you don't)

http://lists.macromates.com/mailman/listinfo/textmate