tripwires attached to dispensers, shooting out stacks of dirt onto more tripwires attached to more dispensers, shooting out more stacks of dirt etc etc. Until you got to your destination... there are no other opportunities for wireless redstone without using commands.

Make an arrow shoot out of a dispenser and land on a WOODEN pressure plate.

I don't want to use commands.

If you are looking for wireless redstone, as in a button that is out in the open and you don't want a funky trail of redstone going off of it or an ugly command block sitting there, then use the /testfor command to search for a button being pressed. Here is what it should look like: /testforblock `x` `y` `z` 77 2 Now the x y z simple, button placement. The 77 means it's looking for a button and the 2 means it's pressed in. Now all you have to do is put the command in to a command block wherever you need the output of the redstone, enter the coordinates of the button, and add a constant clock to the command block. Then place a comparator by the command block and "vwala" you have your output. Hope this helped.

You can use command blocks to /setblock a redstone block, torch, etc. You can also have a command block on a clock that is constantly on a clock with /testfor for something like a scoreboard objective having been raised. A comparator coming out of that block will send out a redstone signal if it can /testfor succesfully.

If you do not want to use command blocks, the methods are a bit less easy. You could try an extra-long tripwire chain.