This is quite a can of worms you guys just opened. I think the issue for
everybody boils down to: what long-term chances does Witango has in the
marketplace. If we look at Apple as an example of a company with great
products and a stagnant (declining) market share, the Witango team should
ready themselves for quite a fight. The JSP compiler "inovation" is a good
one, but I am afraid that it does not go far enough to increase the chances
of business success. Hopefully, there are enough Witango-license-buying
bodies out there to fuel development of the next versions of the product
because I don't see many converts to Witango at this point in the evolution
of market for web-site building solutions, given that it is filled with
products (often much inferior) from companies with recognizable brand names.
Let's offer some ideas to the Witango team that might improve chances of our
beloved product:
1) market (and give or sell) Witango (maybe a LE version of) to schools for
next-to-nothing as the fastest environment for developing and deploying web
apps.
2) re-code the Editor in Java:
consolidate the code base
save Editor development cost (dow nthe road)
make it behave and look the same on all platforms
relase it simultaneously on all platforms
3) make it as easy to deploy in JSP as it is using the Witango server - at
least on one JSP server (say Tomcat/Jboss). This should help the
"uninitiated" to get into the world of JSP as painlessly as possible.
speculations, speculations...
> -----Original Message-----
> From: John McGowan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 10, 2003 9:25 AM
> To: Multiple recipients of list witango-talk
> Subject: Re: Witango-Talk: What to call it
>
>
> Dude,
>
> I believe the term they're all throwing around is "XML
> Execution Engine"
>
> Personally I think the term sucks. "ASCII Execution Engine" would be
> just as descriptive. These types of deceptive tactics will only slow
> the growth and popularity of Witango. People need to know what we're
> using, *and why* so they tell all their friends about it.
>
> I would never use that term, because I'd feel silly if it
> made it's way
> to someone who knows what they're talking about, someone who
> understands
> how proprietary Witango really is. The usage of XML in the
> saved file
> format is no more usefull than the fact that it's in ASCII.
> Especially
> when you consider the changes that With made to the license
> agreement.
> I can't find a copy of the agreement right now, but I'm
> pretty sure it
> states that you aren't allowed to use the XML generated by the dev
> studio for anything but running on the app server, or editing
> with the
> dev studio. Which makes using things like JT a violation of
> the license
> agreement. So, ASCII, Binary, XML, Hindu, It really doesn't matter
> what format the taf and tcf files are saved in.
>
> The only good thing about the file format is that you can
> open it up in
> notepad to fix a problem when the dev studio decides to
> corrupt it for
> you... I'd better check the license agreement about using that third
> party tool with the source code though. ;)
>
> /John
>
> P.S. I'm not trying to start any kind of flame war here...
> Those of you
> that met me at the developers conference already know how I
> feel about
> this issue. I already know I'm alone on this, and don't need to be
> reminded...
>
>
> Web Dude wrote:
>
> > I saw this somewhere on the list before but can't seem to
> find it now.
> >
> > I have a perspective client I have been trying to land for the last
> > month. It is looking good, but they are asking for a list of
> > development tools that will be used in the project. I am
> worried that
> > stating I use Witango, will give me the blank stare I have
> seen from
> > other perpective clients I have tried to woo.
> >
> > Someone on the list in the past came up with an excellent short
> > explanation of what Witango is or does using the word XML which is
> > definitely a buzzword these days.
> >
> > I need some good examples of what to tell this client so I
> can have a
> > good shot at the deal. Any ideas????
> >
> > Thanks!
>
>
> ______________________________________________________________
> __________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to
> [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
