Ioa Petra-ka
Full Member
Offline
Posts: 103
Portland, Oregon, USA
|
In my opinion, the ability to couple Tinderbox event processing with the underlying UNIX shell offers an amazing level of interaction with the rest of the world. With a little knowledge of PHP, Ruby, or some other easily web aware scripting language, you can integrate Tinderbox with your own website---even other web sites that offer external APIs, such as Basecamp, Google Maps, and so on. That's not even counting the extant Tb features already brought up, such as mail integration, and URL fetching.
I have yet to fully explore script coupling myself, but getting my own to-do list roughly synchronised with my company's Basecamp collaboration hub would be fantastic, and it is on my long-term list of things to sort out.
One Tb application that I already have developed facilitates the composition of our monthly newsletter. I get copy from the writers and dump their rich text right into Tinderbox, which it exports to HTML precisely as I configure it to. Tb uses several private APIs I've developed for our web site to pull various bits of data straight out of the site's database, and then I use a series of exporters to produce an email's HTML part, Plain-text part, and web-site archive all from the same source. Revisions can be produced instantly and published directly for collaborative proofing.
I'd say Tb4 is already a web app. Sure, it doesn't have a bunch of stuff out-of-the-box, but Tb out of the box is just an outliner (to be brazenly understated, ha). We have to "program" it to do everything we want it to do with a file. Same goes for integration.
|