WebBrowser Interface to Pyke

[slyfox]

Has anyone came up already with a web interface for pyke, especially
the question base? I would love to see one, and if there is none, any
inputs on how to get started?


BR,

Neil Ablang

[Paul Haesler]

I did some work on calling the Pyke question base from the Django web framework in late 2010.

It required some changes to the ask interface to allow for asynchronous calling of the question base -
those changes have been committed to the mercurial repository, but are not in the most recent
official release (1.1.1).

I'm about to revisit this work after a long absence, so watch this space if you are still interested.

Paul.

[Paul Haesler]

See the discussion thread here:  http://sourceforge.net/p/pyke/discussion/744446/thread/fbd5dd19/?limit=50#6304

[Andrew Ernest]

I'm very interested in a web-interface for the ask_module for PyKE. I can't find the mercurial repo nor can I connect to the pad.dialog.com.ua resource mentioned in the thread. I'm more than happy to help move this forward.

[Chris Gough]

I was "the client" Paul mentioned in that thread, and still have access to his original code. I probably need to redact some peripheral stuff before it could be published/shared, and could do that next week if you like. The SVN repo where it is now is not appropriate to share unfortunately.

Pyke_test was probably last run on django version1.2 and may need a bit of maintenance to work with a modern django project. I doubt that's much work and would be able to assist. It's also fairly bereft of documentation, which it would need to be a really useful example. It was designed as a proof of concept not a generic application, and it would take some work to make it one. 

Bruce/Paul, should I put it up on github in it's own repository or would it be better in an example folder on the pyke repository?

Chris Gough

--
You received this message because you are subscribed to the Google Groups "PyKE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyke+uns...@googlegroups.com.
To post to this group, send email to py...@googlegroups.com.
Visit this group at http://groups.google.com/group/pyke.
For more options, visit https://groups.google.com/d/optout.

[Andrew Ernest]

It would be great if you could make it available in some form. I've also got a start on a kludgy ask_kivy interface that I've been reworking from the ask_wx module. To work well with the Kivy UI, the app back-end should really function in an async mode (I overcome this right now by starting and killing new Kivy apps for each user question - works, but sub-optimal), so any mods that move an async browser interface forward, would likely also apply to other app front-ends like Kivy. Both the Kivy and the Django UIs are mission critical to an ongoing project of mine, so I have a vested interest in moving them forward.

[Chris Gough]

Andrew,

FWIW here is that django_ask module I promised:

https://github.com/monkeypants/pyke_django_ask

It's under MIT license for compatibility with pyke. The ask_django.py module is probably the most useful bit. The bulk of the code is a django app demonstrating it's use. I had to rip out a lot of code/config from the code-base where it was gathering dust, so it's almost certainly broken.

I feel bad about releasing it in it's current broken form but the alternative is making you wait for me to fix it up, and I don't know when I'd get the chance to do that. By the way Linkjuggler (Paul) is the original author, he left it in a working stage and it was a nice demonstration/proof of concept. The problems created by extraction/redaction are all my fault. Pull requests welcome :)

Chris Gough

On Sun, Jul 20, 2014 at 10:56 AM, Andrew Ernest <anse...@gmail.com> wrote:

It would be great if you could make it available in some form. I've also got a start on a kludgy ask_kivy interface that I've been reworking from the ask_wx module. To work well with the Kivy UI, the app back-end should really function in an async mode (I overcome this right now by starting and killing new Kivy apps for each user question - works, but sub-optimal), so any mods that move an async browser interface forward, would likely also apply to other app front-ends like Kivy. Both the Kivy and the Django UIs are mission critical to  an ongoing project of mine, so I have a vested interest in moving them forward.

--
You received this message because you are subscribed to the Google Groups "PyKE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyke+uns...@googlegroups.com.
To post to this group, send email to py...@googlegroups.com.
Visit this group at http://groups.google.com/group/pyke.
For more options, visit https://groups.google.com/d/optout.

--
.

[Andrew Ernest]

Chris: Thanks. My apologies for the delay in responding. I've been traveling and likewise slammed with work. I did pull your/Bruce's code and have been gradually coming up to speed on the logic. I'll post back here anything I come up with.

[Andrew Ernest]

I've had a chance to dig through the ask _django.py code a bit. It looks like the key to the Django implementation is a user question response caching algorithm that's been added to the engine. This is probably embedded in a beta version or fork of the PyKE code base that I don't have, access to. Would it be possible to get my hands on that code?

[Chris Gough]

DjangoAskModule takes request.session (from django) in it's constructor. That's where the interrogation state is kept. See foo/views.py for example of it's use.

I think requsite changes to pike were merged over a year ago, you shouldn't need anything else. Sorry the code isn't a working example, I had to extract it from a non-sharable codebase. I'll try to stay on top of any github tickets you raise.

Chris Gough

On 12/08/2014, at 5:22 AM, Andrew Ernest <anse...@gmail.com> wrote:

> I've had a chance to dig through the ask _django.py code a bit. It looks like the key to the Django implementation is a user question response caching algorithm that's been added to the engine. This is probably embedded in a beta version or fork of the PyKE code base that I don't have, access to. Would it be possible to get my hands on that code?
>