I've seen the one paragraph mentioning WISP - but that's not all that much info :)
If WISP allows web services (obviously not as easily as CF or .NET, but still) - then I'll be happy with that. From reading the one paragraph description - it might...but I'd really be interested in its implementation. -- Alex Kac, CEO/Developer Innovation in Personal and Business Information Management http://www.pocketinformant.com/ zoomzoom > From: Garth Penglase <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Fri, 02 Aug 2002 03:31:53 +1000 > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > Subject: RE: Witango-Talk: Pushing the E:nvelope ;-) > > WISP seems to be a huge step forward for the product since as Scott, in his > conference round-up, mentioned the idea of WISP being used for web services > and such. I assume you saw Scott's conference round-up, Alex? If not get > him to send it to you. > > Also, it would seem that WISP would enable us to create apps that could > communicate directly with the engine, by-passing the web server. My > thinking is that in a years time I will be focusing on creating > Mozilla-style apps communicating with the web server, and/or proprietary > non-web direct-to-server apps using WISP and the server core for specific > audiences. > > Garth > > > At 11:41 1/08/02 -0500, you wrote: >> WISP sounds really interesting to me. This is the one area I'm going to >> spend some time in with the beta if they have info then. >> >> Also, I was playing with the new Project Builder for Jaguar - I REALLY >> think Tango could learn a thing or two from this.... >> >> -- >> Alex Kac, CEO/Developer >> >> Innovation in Personal and Business Information Management. >> http://www.pocketinformant.com/ >> >> zoomzoom >> >> >> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED]] On Behalf Of Scott Cadillac >>> Sent: Thursday, August 01, 2002 11:27 PM >>> To: Multiple recipients of list witango-talk >>> Subject: Re: Witango-Talk: Pushing the E:nvelope ;-) >>> >>> >>> Well said Garth, but you're more than a lurker :-) >>> >>> A great expression comes to mind. >>> >>> "No pain, no gain." >>> >>> And don't forget, in addition to Java deployment, they are >>> planning on possible .NET deployment too and don't forget about WISP. >>> >>> Cheers... >>> >>> ----- Original Message ----- >>> From: "Garth Penglase" <[EMAIL PROTECTED]> >>> To: "Multiple recipients of list witango-talk" >>> <[EMAIL PROTECTED]> >>> Sent: Thursday, August 01, 2002 9:16 AM >>> Subject: Re: Witango-Talk: Pushing the E:nvelope ;-) >>> >>> >>>> I tend to agree with you Gauthier since I am probably more of your >>> typical >>>> WiTango (yes, the name leaves me cold too, Alex) developer. I think >>>> that most of us will be satisfied with the java deployment, tcf, >>>> customtags, external object integration, handy XML >>> manuipulation, XML >>>> Sourcecode etc. that is on offer. >>>> >>>> Can I say (Ben, Scott, Alex et al), that to me a discussion >>> like this >>>> is healthy since a product such as this can't flourish in >>> isolation, >>>> nor >>> with >>>> a internal-only view. I am sure that WI are happy for the >>> feedback as >>>> it must help them to grow the product over time. It is also >>>> enlightening, since without an overview of what is available it is >>>> easy to get stuck >>> into >>>> one product line to one's own detriment - and to become defensive >>>> about a product shows that one's eyes aren't open to progrssion and >>>> the future. I think that it is that exact attitude that WiTangoers >>>> complain about of developers and customers who are one-eyed about >>>> other products (ASP >>> etc.) - >>>> so let's not make the mistake ourselves. We can only learn by being >>>> open >>> to >>>> ideas and opportunities. >>>> >>>> I certainly have and continue to do so. What this thread >>> has confirmed >>>> to me is that WiTango has the goods for me, and hopefully, >>> the future >>>> path >>> to >>>> provide progressions to web services and other tools that >>> are quickly >>>> becoming of importance in our world. And WiTango does stack up well >>>> (in some cases extremely well) against the competition in almost all >>> respects. >>>> >>>> Garth >>>> (the lurker??!!) >>>> :-) >>>> >>>> >>>> At 01:43 2/08/02 +0200, you wrote: >>>>> I don't think Alex is uninterested about Witango, I think that >>>>> Witango didn't have any problem to be compared to other >>> application >>>>> server >>> platforms >>>>> available. >>>>> >>>>> Even if the some higher-end features (that Alex have mentionned >>>>> before) >>> are >>>>> not internaly embeded to the product, it's just a matter of >>>>> developments >>> and >>>>> there is always ways to go where you need with Witango. Just think >>>>> about >>> the >>>>> time it save you to develop with it for the majority of the >>>>> solutions, >>> even >>>>> the current product is very competitive, here is some point : >>>>> >>>>> -Outstanding databases support >>>>> -The visual action editing is STILL a feature that many others >>>>> products lacks -The variable store scope concept is really >>> powerfull >>>>> and let you >>> completely >>>>> manage your variable life cycle. >>>>> -The Metatag language is tightly integrated and you can use it just >>> anywhere >>>>> in your files (it's also extensible thanks to the customtags!) I >>>>> didn't >>> saw >>>>> a such thing anywhere. >>>>> -It's designed to be effective from the complete newbie (easy RDBMS >>> actions, >>>>> builders, visual action) as well from the diehard developper (tcf, >>>>> customtags, external object integration, handy XML >>> manuipulation, XML >>>>> Sourcecode...) >>>>> -It's multiplatform and interoperable, that's really an important >>>>> point >>> for >>>>> an application server >>>>> >>>>> We are all impatient (since the conference) to discover >>> the accurate >>>>> featureset of the new version, and I think that the java deployment >>> ability >>>>> is really a great point! >>>>> >>>>> There is also a feature of the server that wasn't elaborated on the >>> list, >>>>> this is the WISP here is the only infos I've found about it (I'm >>>>> investigating ;) -http://xml-extra.net/webpage.xmlx?node=55 >>>>> -http://www.leavens.net/witangoconf/pages/P4240319.html (really >>> enigmatic >>>>> look like a 007 stuff !!!) >>>>> >>>>> So that's the surely kind of things that can bring higher-end >>>>> features >>> for >>>>> the whole client/server application development activity! >>>>> >>>>> Please don't take me wrong that's just my developer standpoint :) >>>>> >>>>> I don't want this thread become a flamewar thread! >>>>> >>>>> Regards >>>>> >>>>> Gauthier >>>>> >>>>> ----- Original Message ----- >>>>> From: "Ben Johansen" <[EMAIL PROTECTED]> >>>>> To: "Multiple recipients of list witango-talk" >>> <[EMAIL PROTECTED]> >>>>> Sent: Friday, August 02, 2002 12:17 AM >>>>> Subject: RE: Witango-Talk: Pushing the E:nvelope ;-) >>>>> >>>>> >>>>>> I am all for Free forums for the public, >>>>>> >>>>>> But, are you really interested in Witango, or are you >>> just killing >>> time >>>>>> Jerking us around? >>>>>> >>>>>> If you want to discuss WO (what objects) or Confussion, >>> I am sure >>> there >>>>>> are list servers for that. >>>>>> >>>>>> As long as you keep thinking this is just a Service >>> Pack 2 to your >>>>>> 2 year old knowledge of the past Tango. You will probably never >>>>>> like >>> what >>>>>> the good people at With Enterprises are doing. >>>>>> >>>>>> This is Witango and it is going forward, if it is not at your >>>>>> speed, move on >>>>>> >>>>>> Ben Johansen >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: [EMAIL PROTECTED] >>>>>> [mailto:[EMAIL PROTECTED]] On Behalf Of Alex Kac >>>>>> Sent: Thursday, August 01, 2002 2:59 PM >>>>>> To: Multiple recipients of list witango-talk >>>>>> Subject: Re: Witango-Talk: Pushing the E:nvelope ;-) >>>>>> >>>>>> I am waiting patiently :) Seriously, I am very hopeful >>> as I'd love >>>>>> to rekindle my years of Tango knowledge and comfortablness with >>>>>> Tango. I truly would rather not have to start from scratch >>>>>> somewhere else (which I >>> did >>>>>> with >>>>>> .net). >>>>>> >>>>>> I'm also taking the opportunity to download WebObjects >>> through my >>>>>> ADC account since I now have a few days to spare. >>>>>> >>>>>> That'll be very interesting - esp. since WO comes with >>> both Mac OS >>>>>> X deployment and Windows deployment - easing the transition on >>>>>> servers. >>> So >>>>>> both WO and CF now have free crossgrades, while With (I >>> asked them >>>>>> directly) >>>>>> will charge the upgrade fee for that. This comment is just a >>> sidenote. >>>>>> >>>>>> -- >>>>>> Alex Kac, CEO/Developer >>>>>> >>>>>> Innovation in Personal and Business Information Management >>>>>> http://www.pocketinformant.com/ >>>>>> >>>>>> zoomzoom >>>>>> >>>>>> >>>>>>> From: "Ian Daniel" <[EMAIL PROTECTED]> >>>>>>> Reply-To: [EMAIL PROTECTED] >>>>>>> Date: Thu, 1 Aug 2002 14:31:48 -0700 >>>>>>> To: Multiple recipients of list witango-talk >>>>>> <[EMAIL PROTECTED]> >>>>>>> Subject: RE: Witango-Talk: Pushing the E:nvelope ;-) >>>>>>> >>>>>>> To Stephen and all others urgently needing Version 5 info. >>>>>>> >>>>>>> Here's what we can share, just now. >>>>>>> >>>>>>> Information, including pricing is being distributed to >>>>>>> resellers, >>> and >>>>>> they >>>>>>> have been given a few days to prepare themselves, >>> their websites >>> and >>>>>> update >>>>>>> their support systems with the new data. >>>>>>> >>>>>>> When I say a few days, I mean a few days. That's less than a >>>>>>> week. >>>>>>> >>>>>>> Next week, the public beta will be released, and there will be >>> several >>>>>>> places to go to download it. You'll be pleased to >>> know that the >>>>>> Editor is >>>>>>> being separated from the personal server, to reduce download >>>>>> requirements. >>>>>>> The personal server will be a separate item without a cost >>> attached, >>>>>> but >>>>>>> with tighter restrictions than were previously on the personal >>> server, >>>>>> to >>>>>>> ensure that it is just used for development purposes. >>>>>>> >>>>>>> With the release of the public beta, there will be a detailed >>>>>>> list >>> of >>>>>>> enhancements. >>>>>>> >>>>>>> Witango and Java will become good friends .. and very >>> well-acquainted >>>>>> .. but >>>>>>> not in version 5. >>>>>>> >>>>>>> Questions relating to functionality and release date of a >>>>>>> Witango >>>>>> editor >>>>>>> that incorporates Java capabilities must be deferred to WE. >>> However, >>>>>> I can >>>>>>> personally tell you what I know to be a fact: >>> elements of the >>>>>>> Java functionality were demonstrated at the >>> conference in April, >>>>>>> and the >>>>>> next >>>>>>> release of the Editor will not take as long as Version 5 took, >>> because >>>>>> the >>>>>>> time has been taken to re-architect everything to prepare for >>>>>>> the >>>>>> future. >>>>>>> >>>>>>> And all marketing hype aside, I will tell you something else >>>>>>> that >>>>>> everyone >>>>>>> on this list could figure out for themselves: that if you >>>>>>> combine >>> the >>>>>>> absolutely top-shelf IDE that is the Witango Editor >>> ... with the >>>>>> ability to >>>>>>> create Java in object-oriented fashion, the future is indeed >>> bright. >>>>>>> >>>>>>> And you can take that to the bank. >>>>>>> >>>>>>> Please ... no flames .. for this thread, it's all been said. >>>>>>> >>>>>>> For those who anxiously await the launch of Witango Version 5 >>> public >>>>>> beta .. >>>>>>> take a deep breath, have a good weekend, and watch your email >>>>>> carefully >>>>>>> early next week. >>>>>>> >>>>>>> Sincerely, >>>>>>> Ian >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Stephen Arnold >>>>>>> >>>>>>> <sarcasm> Gee, thanks Ben. Such a tease!</sarcasm> >>>>>>> >>>>>>> I would think after the barrage of sentiment that >>> MOST of us are >>>>>> anxious >>>>>>> to know when and how much, a few of you insiders >>> wouldn't brag >>>>>>> so >>>>>> much. >>>>>>> >>>>>>> Really, some of us are reaching critical mass on making >>>>>>> important decisions on software and hardware. Christmas is >>>>>>> coming and we know >>>>>> with >>>>>>> this year's anticipated volume and loads we can't sustain the >>> status >>>>>> quo >>>>>>> again this year. We, like some others, will be forced to seek >>>>>>> other solutions, despite our affinity for the product >>> and what >>>>>>> it may or >>> may >>>>>>> not offer during its next "life". >>>>>>> >>>>>>> Stephen >>>>>>> >>>>>>> >>>>>> >>> ______________________________________________________________ >>> __________ >>>>>>> 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 >>>>>> >>>>>> >>> ______________________________________________________________ >>> __________ >>>>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to >>> [EMAIL PROTECTED] >>>>>> with unsubscribe witango-talk in the >>> message body >>>>> >>>>> >>>> >>>> _____________________________________________________________ >>> __________ >>>> ___ >>> ____ >>>>> ifrance.com, l'email gratuit le plus complet de l'Internet ! vos >>>>> emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... >>>>> http://www.ifrance.com/_reloc/email.emailif >>>>> >>>>> >>>> >>>> _____________________________________________________________________ >>>>> ___ >>>>> 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 >>>> >>> >>> ______________________________________________________________ >>> __________ >>> 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 > > ________________________________________________________________________ > 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
