Re: Is it possible to implement Weizenbaum's original Eliza as a chatbot with LIVECODE?
Hi Ingar, Check this stack: https://forums.livecode.com/viewtopic.php?f=10=33212 based on this HyperCard stack: http://umich.edu/~archive/mac/hypercard/fun/spectresmart2.5.sit.hqx Al ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Is it possible to implement Weizenbaum's original Eliza as a chatbot with LIVECODE?
> I wrote: > You could build on https://www.masswerk.at/elizabot/ > ... > You could similarly make a LC GUI based on elizabot.js in > a browser widget. > ... Here is a basic LiveCode GUI: Browser Widget usage example #28: ELIZA_bot http://forums.livecode.com/viewtopic.php?p=184198#p184198 The jslib and the vocabulary are included in the stack. Moreover that default vocabulary is attached for editing (you can the chnaged file import to the stack, replacing the default vocabulary, using button "ImportData"). ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Give a bug a hug
agree On Fri, Oct 11, 2019 at 3:15 PM hh via use-livecode < use-livecode@lists.runrev.com> wrote: > This is a wonderful project. > > Should be limited to bugs that are NOT regressions. > And instead extended by feature requests. > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Give a bug a hug
This is a wonderful project. Should be limited to bugs that are NOT regressions. And instead extended by feature requests. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Give a bug a hug
For what its worth, I think this is the way to go. A totally community run initiative, with a bounty on bug fixes. Someone or several someones outside of the LiveCode team would need to take responsibility for setting up a structure. We'd love to see bugs being fixed, by members of the community. It's kind of the reason behind Open Source. There are plenty of bugs that would be suitable, which don't require deep dives into the engine. Pull requests arrive in the usual manner and get approved or fed back on in the normal scheme of things by our team. If this could be encouraged by a bounty on fixes, funded by the community, run by the community and entirely outside of LiveCode Ltd.'s scope, what's not to like? Our overstretched resources would be augmented by a community team, and the dual nature of the licensing would bear fruit in a new and productive manner. I like it. Over to you. Best Regards, Heather Heather Laine Customer Services Manager LiveCode Ltd www.livecode.com > On 10 Oct 2019, at 22:17, Mike Kerner via use-livecode > wrote: > > wow, i managed to mute this conversation. fail. > @paul, that's exactly why we ponied up, too, as an insurance policy. we > have been burned by numerous organizations either abandoning their software > work product or disappearing. thankfully, for most of our mission-critical > stuff, we have, own, and maintain the source. > @Sean, I'm not generally thinking of the underlying engine for the bounty > program, I'm thinking of pieces in LCS/LCB. In those cases, the PR doesn't > get submitted to the LC repo until whatever step it was further down. > There isn't any reason why private repos can't be used to manage this > process, especially with submodules. The patrons would have access to the > repo, no one else would. > As for the conversation about the unfinished projects that all of us ponied > up for on a promise, I 100% agree, which is why the funds are escrowed. > The developer proposing a solution doesn't get paid until the patch is > tested and approved by the patrons of the patch. > > On Wed, Oct 9, 2019 at 11:02 AM Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> +1 Richard. I got onboard with what user to be Runtime Revolution (I think >> it was version 2!) Where livecode is today is orders of magnitude more than >> it was when it first started. There was no datagrid. No way to display >> tabular data apart from a very simple table field. No arrays. Difficult and >> confusing database APIs. No mobile support. The list goes on. >> >> LC is like a really good girlfriend. She isn't everything I ever wanted, >> but she's good enough for me. :-) >> >> Bob S >> >> >>> On Oct 8, 2019, at 19:49 , Richard Gaskin via use-livecode < >> use-livecode@lists.runrev.com> wrote: >>> >>> Pi Digital wrote: >>> > On 8 Oct 2019, at 21:42, Richard Gaskin wrote: > > And here is a May 2016 update: > > >> https://livecode.com/trevor-devore-interviews-kevin-mark-on-infinite-livecode/ > > > A small number of people keep going round and round on this a large > number of times. > > How many times will the same conversation happen before more recent > information is absorbed? An excellent article. Which part was you pointing to in reference to Lagi’s question about older campaigns funded that have still not met the core? >>> >>> There's a section in the middle listing off the accomplishments since >> the Kickstarter, and some of the discussion goes into how much of that was >> paid for out-of-pocket. >>> >>> And which part do you refer to when asserting that absorption of info is needed to reduce the same conversations recursion rate? >>> >>> The portion of Lagi's post I had originally quoted in my reply: >>> >>> This is what I was talking about being treated like mushrooms >>> - no communication as to what the future holds.- rough timescales >>> as to when new or reassigned resources will be implemented - what >>> is the intention with sqlite, 2d physics, Audio >>> >>> He's one of about three people who keep going back to the Kickstarter >> list as some form of eternal damnation against the team, and he knows that >> I know that he's read comments here and in the forums from Kevin and other >> team members that have discussed all of that over and over and over and >> over again. >>> >>> How many times does Kevin need to post a mea culpa about being among the >> 80% of software project leaders that underestimated cost? Apparently half >> a dozen isn't enough. >>> >>> In summary: Most of the list was delivered, most of the remainder is in >> the DB as feature requests to be completed as resources permit. >>> >>> >>> Kevin, Heather, Mark and others have been very forthcoming here about >> what the company is working on, at least to the degree that this community >> allows. But there's not much allowance granted: >>> >>>
Re: Is it possible to implement Weizenbaum's original Eliza as a chatbot with LIVECODE?
You could build on https://www.masswerk.at/elizabot/ They build there in javascript on it for a "terminal" or speech i/o. You could similarly make a LC GUI based on elizabot.js in a browser widget. Or moreover translate elizabot.js to LiveCode. The js is already object oriented and has 1.7K in < 400 lines. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Is it possible to implement Weizenbaum's original Eliza as a chatbot with LIVECODE?
May be someone even has experience with similar attempts? I would be grateful for any suggestions. Ingar ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Android/Java PKCS12 Industry format Keystore
That's the same i use too. Maybe the updated java is the cause of the warning. Latest of jave jdk 8. The keys still work, so i was curious if this could have consequences. "J. Landman Gay via use-livecode" schreef op 10 oktober 2019 22:36:11 CEST: >I use the example from Google, which is identical to the example in the > >LC lesson. This is Google: > >keytool -genkey -v -keystore my-release-key.jks -keyalg RSA -keysize >2048 -validity 1 -alias my-alias > >This is the LC lesson (using Windows exe): >keytool.exe -genkey -v -keystore release.keystore -alias TicTacToe >-keyalg RSA -keysize 2048 -validity 1 > >I have never seen any warnings. > >On 10/10/19 1:55 PM, JJS via use-livecode wrote: >> Hi, >> >> >> have some people already changed their (Android/Java) keystore keys >to >> the PKCS12 format? >> >> >> When creating a keystore key i get this warning a few times: >> >> >> Warning: >> The JKS keystore uses a proprietary format. >> It is recommended to migrate to PKCS12 which is an industry standard >> format using "keytool -importkeystore -srckeystore yourapp.keystore >> -destkeystore yourapp.keystore -deststoretype pkcs12". >> >> Or still using the proprietary format? >> >> Regards. >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > >-- >Jacqueline Landman Gay | jac...@hyperactivesw.com >HyperActive Software | http://www.hyperactivesw.com > > >___ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode -- Verstuurd vanaf mijn Android apparaat met K-9 Mail. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
