6 Replies to “Wagn”

  1. Glad you like it! Not sure if i get what you mean by “embedded update language”. We’re working on basic notifications for the next release…

    1. Nice work, John. This kind of outside-the-box thinking is so rare and valuable. By embedded update language, I mean scripting triggers so that a full application could be built without resort to Ruby code. Think HyperCard.

      1. HyperCard – fond memories :-).

        I’m often surprised by how much we can do with WQL (Wagn’s query language), but yes, we do want users to be able to trigger scripts that do something (such scripts will, of course, be cards). We almost thought we’d have to do this to implement notifications, but we found a way around it. First use might be to allow changing from one cardtype to another by clicking a button. Seems like Wagn is well-suited for applications in which something moves through a series of stages, so easing the interface around that would be nice.

        1. Upon my first look at WAGN, my initial reaction was “Well! HyperCard re-surfaces; I wonder what Bill Atkinson (and for that matter, Paul Heckel) would think of this?”

          I mean this as high praise.

          TileStack seems to have followed a similar path, but arrived at a different place.

  2. I tried this out, and I simply don’t get what is cool about it?

    I find it hard to use, to the point where I don’t understand how to use it.

    @Cross between a Wiki and a database. And a semantic database at that, where all fields/attributes are binary associations.

    Why does this matter?

    1. Nevermind. I get it.

      It is too much for the average user. For programmers, it makes some sense, but needs much more hiding of the programmatic aspects of the system.

      Also, the interface is a long way away from being usable.

Comments are closed.