Hi John,

You're right on track. Ben and I proposed this very idea years ago, but alas it didn't go anywhere.

It's a shame too, because obviously server technologies are very set these days. It's either Java, .NET based, PHP or ColdFusion. The occasional radical comes along like Ruby or Python, but in my opinion these are just blips on the scope. And even if a new server platform could come along to supplant the kings of the hill - at this point in the game, it would have to be free to compete.

But when it comes to a good Editor to build that code (whether PHP or F-frigg'n #) - people will pay very good money for a kick-a** IDE that gets their work done fast, smart and allow them to have fun at it, to boot.

Oh well. Such is life, nobody said it would be fair.

Scott,





On Oct-24-2008, at 12:05 PM, John McGowan wrote:

Witango is Witango...

It just happens to XML as a medium for storing the programming logic. Underneath the XML is a language, just one that you would never write by hand... unless you were insane...

Which was a cool idea, and completely underutilized. You could do so many cool things with it because of the XML if you wanted to. A while back when I was starting to get really good at writing XSL Transformations, I wrote some transforms that worked with with witango xml (taf and tcf files). I prototyped, as a proof of concept, an XSLT that converted some basic witango actions (conditionals and control structures) to another language, PHP.

What's cool is that with an XSLT like this in your back pocket, you could use witango as a RAD environment for other languages. The J2EE product from witango is similar, but it's way more complicated, because it also has to be capable of parsing witango's meta tags. What I was playing with, was a system where you would abandon the use of @tags, and instead just write straight php,jsp,asp, right there in the witango editor. I'm sure i wasn't the only one to think of it. I'm positive that if someone added this (very thin) layer of functionality to the witango editor, that today there would be PHP developers using Witango as their PHP IDE. Why? Because you would be able to use the strongest part of the Witango system. That being, the dev studios approach to "visual coding". there is no other part of the witango system that sets it apart. Witango's action approach to the top level coding view is unique, and like "code folding on steroids"

Witango should have taken this piece, and exploited it, because I'm sure it won't be long until some really cool PHP IDE catches up and decides to add that extra layer of abstraction. Heck one might already do it out there, but I haven't seen it yet. I've seen good "code folding", but not something that works as well as the action system in witango.

The worst part about it all, is that I beleive that the prototype that I described above, probably violates the license agreement for Witango, because if I remember correctly, I was told that using a tool like JTransit was a violation of the license agreement.

And, for what it's worth, I've been emailing phil, sophie, and support for a couple of weeks now asking for any information that they have on running witango in a 64 bit linux environment, and have gotten NO response from them.

/John

On Fri, Oct 24, 2008 at 3:50 AM, janet <[EMAIL PROTECTED]> wrote:
So if Witango is not PHP or C+ or whatever what is it?

Is it just XML?

If so then why don't I see other products that are XML?

I ask this because when I was looking at other RAD tools they all seem to end up with PHP, VB, or C+ or something but not XML.


Wow talk about getting back to basics.


Janet




From: WebDude [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2008 12:48 AM
To: [email protected]
Subject: RE: Witango-Talk: Open Letter to Phil and Sophie



________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to