3 ms·

It's in open public beta at the moment. We are a consultancy that work on large iOS application within large teams, with ever aging code-bases, and we built thi

It's in open public beta at the moment. We are a consultancy that work on large iOS application within large teams, with ever aging code-bases, and we built this to make our lives much much easier when it comes to debugging complex view hierarchies.

jawngee 13y ago
Looks beautiful. I've been using Spark Inspector but am not too comfortable with it modifying my Xcode projects. What's pricing going to look like?
- seanwoodhouse 13y ago
  You still need to link your app against our library for Reveal to be able to inspect it, but the instructions guide you through it so you know exactly what's being modified in your project. Pricing will be announced when we come out of beta.
  - jawngee 13y ago
    The one thing I do really like about spark is the NSNotificationCenter monitoring. Will you be supporting that?
    - theraven 13y ago
      We are currently trying to be as least invasive to the running application as we can be at the moment. We don't perform any swizzling, or URL proxying.
- bengotow 13y ago
  Hey! Author of the Spark Inspector here - what would make you more comfortable with the setup assistant? I'd love to get you to use it ;-) You can modify your project yourself, but it's important that the framework is added to the debug build configuration only, and the Spark Inspector's setup assistant makes sure you do this right. If you drag and drop the framework into your project the way Reveal tells you to, that framework will be linked into Release builds (because of the '-ObjC' flag) - so you could accidentally allow people to inspect your published app!
  - seanwoodhouse 13y ago
    Our integration guide is pretty explicit about how to link with the library so that it doesn't get linked in to Release builds. Everyone's environment is different, and we think it's a good thing that developers understand what changes are required to link with any third party framework.
    - bengotow 13y ago
      Ahh cool - I just followed the graphic on the "Getting Started" panel (the pic with the framework being dragged into the left sidebar) I already had the Spark Inspector framework linked in so I guess I was able to skip the instructions!

jawngee 13y ago

Looks beautiful. I've been using Spark Inspector but am not too comfortable with it modifying my Xcode projects. What's pricing going to look like?

seanwoodhouse 13y ago
You still need to link your app against our library for Reveal to be able to inspect it, but the instructions guide you through it so you know exactly what's being modified in your project. Pricing will be announced when we come out of beta.
- jawngee 13y ago
  The one thing I do really like about spark is the NSNotificationCenter monitoring. Will you be supporting that?
  - theraven 13y ago
    We are currently trying to be as least invasive to the running application as we can be at the moment. We don't perform any swizzling, or URL proxying.
bengotow 13y ago
Hey! Author of the Spark Inspector here - what would make you more comfortable with the setup assistant? I'd love to get you to use it ;-) You can modify your project yourself, but it's important that the framework is added to the debug build configuration only, and the Spark Inspector's setup assistant makes sure you do this right. If you drag and drop the framework into your project the way Reveal tells you to, that framework will be linked into Release builds (because of the '-ObjC' flag) - so you could accidentally allow people to inspect your published app!
- seanwoodhouse 13y ago
  Our integration guide is pretty explicit about how to link with the library so that it doesn't get linked in to Release builds. Everyone's environment is different, and we think it's a good thing that developers understand what changes are required to link with any third party framework.
  - bengotow 13y ago
    Ahh cool - I just followed the graphic on the "Getting Started" panel (the pic with the framework being dragged into the left sidebar) I already had the Spark Inspector framework linked in so I guess I was able to skip the instructions!