Hi, everyone. I'm new to PyKE, and want to use PyKE in my project. Are there any successful projects that base on PyKE? I think it's a good idea to refer to some successful projects before using it. Any suggestion (and URL) will be appreciated. Thank you.
Hi pinot and all, I'm in the same situation and it would be really useful to see a real life example.
I also saw your other post (about the bad documentation) and I have to admit that I kinda agree with you, even if not fully. Actually the documentation is there and is also quite advanced, the only thing is that it is lacking an introduction for beginners.
So hereby I'm asking to the experts, which are the prerequisites in order to fully understand PyKE and to use it at its best?
I'm now doing a project which needs some sort of knowledge base and I think that PyKE would be the right choice to my case, if only I knew how to use it.
Probably I'm still missing something theoretical here, that's why I'm asking for some pointers. Any help is greatly appreciated.
I can not find any project to study until now. PyKE is great, I think it's the best way to study PyKE is starting using it.
Maybe I chose some wrong words in my post that you mention before, for example the word "ugly". I agree with you, it will be very helpful if there is some documentations such as "Tutorial", "*** for beginners" and so on.
But as we all know, saying is much easier that doing.
I'm trying to build a real project with PyKE. If I can make it, I really want to write some docs for beginners. Maybe I will have the sufficient knowledge to do that at that time. But my native language is not English, that's a big problem.
> Hi pinot and all, > I'm in the same situation and it would be really useful to see a real > life example.
> I also saw your other post (about the bad documentation) and I have to admit > that I kinda agree with you, even if not fully. > Actually the documentation is there and is also quite advanced, the only > thing is that it is lacking an introduction for beginners.
> So hereby I'm asking to the experts, which are the prerequisites in order to > fully understand PyKE and to use it at its best?
> I'm now doing a project which needs some sort of knowledge base and I think > that PyKE would be the right choice to my case, if only I knew how to use > it.
> Probably I'm still missing something theoretical here, that's why I'm asking > for some pointers. > Any help is greatly appreciated.
> Best Regards, > Elisiano Petrini
> -- > You received this message because you are subscribed to the Google Groups > "PyKE" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/pyke/-/0m5UIacsDGgJ. > To post to this group, send email to pyke@googlegroups.com. > To unsubscribe from this group, send email to > pyke+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pyke?hl=en.
Thank you for your offer of help! I wouldn't worry about your English skills. The hard part is figuring out what needs to be said, how it should be organized and what examples to use. If you can do this, there are many people who can help with the English. You might just write it the best you can (I would suggest not spending too long on the English to keep the flow going smoothly) and then somebody else can clean up the language; or you could prepare an outline with a bullet list of things that need to be said and prepare examples. Then somebody else could write the English.
I wrote the PyKE documentation before Sphinx <http://sphinx.pocoo.org/>was available. I am open to either moving to sphinx or to some other documentation tool. I am also willing to make you a committer to the project so that you can commit directly. Just let me know how I can help.
I am wondering if you've looked at the examples provided in the examples source code directory?
Also, PyKE uses a very different computational model than standard procedural programming languages. So the learning curve is much greater than, say, moving from Java to Python. But it is based on prolog (though with different syntax). So maybe some prolog tutorials would be useful?
The Structured Program Theorem<http://en.wikipedia.org/wiki/Structured_program_theorem>states that all programs can be decomposed into 3 control structure: sequence (do A, then do B), selection (do A or do B based on some condition), and repetition (do A many times). Perhaps simple examples of how to do each of these in PyKE would be useful? And then maybe showing how abstraction works (the counterpart to procedural programming's concept of a user-defined function)?
On Thu, Dec 1, 2011 at 5:30 AM, zhijun wu <pinot...@gmail.com> wrote: > I can not find any project to study until now. PyKE is great, I think > it's the best way to study PyKE is starting using it.
> Maybe I chose some wrong words in my post that you mention before, for > example the word "ugly". I agree with you, it will be very helpful if > there is some documentations such as "Tutorial", "*** for beginners" > and so on.
> But as we all know, saying is much easier that doing.
> I'm trying to build a real project with PyKE. If I can make it, I > really want to write some docs for beginners. Maybe I will have the > sufficient knowledge to do that at that time. But my native language > is not English, that's a big problem.
> 2011/11/25 Elisiano Petrini <elisi...@gmail.com>: > > Hi pinot and all, > > I'm in the same situation and it would be really useful to see a real > > life example.
> > I also saw your other post (about the bad documentation) and I have to > admit > > that I kinda agree with you, even if not fully. > > Actually the documentation is there and is also quite advanced, the only > > thing is that it is lacking an introduction for beginners.
> > So hereby I'm asking to the experts, which are the prerequisites in > order to > > fully understand PyKE and to use it at its best?
> > I'm now doing a project which needs some sort of knowledge base and I > think > > that PyKE would be the right choice to my case, if only I knew how to use > > it.
> > Probably I'm still missing something theoretical here, that's why I'm > asking > > for some pointers. > > Any help is greatly appreciated.
> > Best Regards, > > Elisiano Petrini
> > -- > > You received this message because you are subscribed to the Google Groups > > "PyKE" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/pyke/-/0m5UIacsDGgJ. > > To post to this group, send email to pyke@googlegroups.com. > > To unsubscribe from this group, send email to > > pyke+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/pyke?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PyKE" group. > To post to this group, send email to pyke@googlegroups.com. > To unsubscribe from this group, send email to > pyke+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pyke?hl=en.
On Thu, Dec 1, 2011 at 12:57 PM, Bruce Frederiksen <dangy...@gmail.com> wrote: > Zhijun,
> Thank you for your offer of help! I wouldn't worry about your English > skills. The hard part is figuring out what needs to be said, how it should > be organized and what examples to use. If you can do this, there are many > people who can help with the English. You might just write it the best you > can (I would suggest not spending too long on the English to keep the flow > going smoothly) and then somebody else can clean up the language; or you > could prepare an outline with a bullet list of things that need to be said > and prepare examples. Then somebody else could write the English.
> I wrote the PyKE documentation before Sphinx was available. I am open to > either moving to sphinx or to some other documentation tool. I am also > willing to make you a committer to the project so that you can commit > directly. Just let me know how I can help.
> I am wondering if you've looked at the examples provided in the examples > source code directory?
> Also, PyKE uses a very different computational model than standard > procedural programming languages. So the learning curve is much greater > than, say, moving from Java to Python. But it is based on prolog (though > with different syntax). So maybe some prolog tutorials would be useful?
> The Structured Program Theorem states that all programs can be decomposed > into 3 control structure: sequence (do A, then do B), selection (do A or do > B based on some condition), and repetition (do A many times). Perhaps > simple examples of how to do each of these in PyKE would be useful? And > then maybe showing how abstraction works (the counterpart to procedural > programming's concept of a user-defined function)?
> Anyway, welcome aboard!
> -Bruce
> On Thu, Dec 1, 2011 at 5:30 AM, zhijun wu <pinot...@gmail.com> wrote:
>> I can not find any project to study until now. PyKE is great, I think >> it's the best way to study PyKE is starting using it.
>> Maybe I chose some wrong words in my post that you mention before, for >> example the word "ugly". I agree with you, it will be very helpful if >> there is some documentations such as "Tutorial", "*** for beginners" >> and so on.
>> But as we all know, saying is much easier that doing.
>> I'm trying to build a real project with PyKE. If I can make it, I >> really want to write some docs for beginners. Maybe I will have the >> sufficient knowledge to do that at that time. But my native language >> is not English, that's a big problem.
>> 2011/11/25 Elisiano Petrini <elisi...@gmail.com>: >> > Hi pinot and all, >> > I'm in the same situation and it would be really useful to see a real >> > life example.
>> > I also saw your other post (about the bad documentation) and I have to >> > admit >> > that I kinda agree with you, even if not fully. >> > Actually the documentation is there and is also quite advanced, the only >> > thing is that it is lacking an introduction for beginners.
>> > So hereby I'm asking to the experts, which are the prerequisites in >> > order to >> > fully understand PyKE and to use it at its best?
>> > I'm now doing a project which needs some sort of knowledge base and I >> > think >> > that PyKE would be the right choice to my case, if only I knew how to >> > use >> > it.
>> > Probably I'm still missing something theoretical here, that's why I'm >> > asking >> > for some pointers. >> > Any help is greatly appreciated.
>> > Best Regards, >> > Elisiano Petrini
>> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "PyKE" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/pyke/-/0m5UIacsDGgJ. >> > To post to this group, send email to pyke@googlegroups.com. >> > To unsubscribe from this group, send email to >> > pyke+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/pyke?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "PyKE" group. >> To post to this group, send email to pyke@googlegroups.com. >> To unsubscribe from this group, send email to >> pyke+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/pyke?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PyKE" group. > To post to this group, send email to pyke@googlegroups.com. > To unsubscribe from this group, send email to > pyke+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pyke?hl=en.
Sounds like an excellent way to get more examples! I'd be eager to know what you find when you do this! Maybe you could report interesting examples back here so that others can also benefit from them?
On Thu, Dec 1, 2011 at 11:40 AM, Dante_Zaupa <dante...@gmail.com> wrote: > Hey Zhijun
> Here's my 2 cents: try searching for "import pyke" in Google, GitHub > and similar repositories. That ought to find open source projects > using Pyke.
> Best regards, > Dante
> On Thu, Dec 1, 2011 at 12:57 PM, Bruce Frederiksen <dangy...@gmail.com> > wrote: > > Zhijun,
> > Thank you for your offer of help! I wouldn't worry about your English > > skills. The hard part is figuring out what needs to be said, how it > should > > be organized and what examples to use. If you can do this, there are > many > > people who can help with the English. You might just write it the best > you > > can (I would suggest not spending too long on the English to keep the > flow > > going smoothly) and then somebody else can clean up the language; or you > > could prepare an outline with a bullet list of things that need to be > said > > and prepare examples. Then somebody else could write the English.
> > I wrote the PyKE documentation before Sphinx was available. I am open to > > either moving to sphinx or to some other documentation tool. I am also > > willing to make you a committer to the project so that you can commit > > directly. Just let me know how I can help.
> > I am wondering if you've looked at the examples provided in the examples > > source code directory?
> > Also, PyKE uses a very different computational model than standard > > procedural programming languages. So the learning curve is much greater > > than, say, moving from Java to Python. But it is based on prolog (though > > with different syntax). So maybe some prolog tutorials would be useful?
> > The Structured Program Theorem states that all programs can be decomposed > > into 3 control structure: sequence (do A, then do B), selection (do A or > do > > B based on some condition), and repetition (do A many times). Perhaps > > simple examples of how to do each of these in PyKE would be useful? And > > then maybe showing how abstraction works (the counterpart to procedural > > programming's concept of a user-defined function)?
> > Anyway, welcome aboard!
> > -Bruce
> > On Thu, Dec 1, 2011 at 5:30 AM, zhijun wu <pinot...@gmail.com> wrote:
> >> I can not find any project to study until now. PyKE is great, I think > >> it's the best way to study PyKE is starting using it.
> >> Maybe I chose some wrong words in my post that you mention before, for > >> example the word "ugly". I agree with you, it will be very helpful if > >> there is some documentations such as "Tutorial", "*** for beginners" > >> and so on.
> >> But as we all know, saying is much easier that doing.
> >> I'm trying to build a real project with PyKE. If I can make it, I > >> really want to write some docs for beginners. Maybe I will have the > >> sufficient knowledge to do that at that time. But my native language > >> is not English, that's a big problem.
> >> 2011/11/25 Elisiano Petrini <elisi...@gmail.com>: > >> > Hi pinot and all, > >> > I'm in the same situation and it would be really useful to see a > real > >> > life example.
> >> > I also saw your other post (about the bad documentation) and I have to > >> > admit > >> > that I kinda agree with you, even if not fully. > >> > Actually the documentation is there and is also quite advanced, the > only > >> > thing is that it is lacking an introduction for beginners.
> >> > So hereby I'm asking to the experts, which are the prerequisites in > >> > order to > >> > fully understand PyKE and to use it at its best?
> >> > I'm now doing a project which needs some sort of knowledge base and I > >> > think > >> > that PyKE would be the right choice to my case, if only I knew how to > >> > use > >> > it.
> >> > Probably I'm still missing something theoretical here, that's why I'm > >> > asking > >> > for some pointers. > >> > Any help is greatly appreciated.
> >> > Best Regards, > >> > Elisiano Petrini
> >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "PyKE" group. > >> > To view this discussion on the web visit > >> > https://groups.google.com/d/msg/pyke/-/0m5UIacsDGgJ. > >> > To post to this group, send email to pyke@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > pyke+unsubscribe@googlegroups.com. > >> > For more options, visit this group at > >> > http://groups.google.com/group/pyke?hl=en.
> >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "PyKE" group. > >> To post to this group, send email to pyke@googlegroups.com. > >> To unsubscribe from this group, send email to > >> pyke+unsubscribe@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/pyke?hl=en.
> > -- > > You received this message because you are subscribed to the Google Groups > > "PyKE" group. > > To post to this group, send email to pyke@googlegroups.com. > > To unsubscribe from this group, send email to > > pyke+unsubscribe@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/pyke?hl=en.
> Usuário Linux #459228 -- Linux Mint 11 ("Katya")
> -- > You received this message because you are subscribed to the Google Groups > "PyKE" group. > To post to this group, send email to pyke@googlegroups.com. > To unsubscribe from this group, send email to > pyke+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pyke?hl=en.
Dante, Thank you, it's really a good way to get more examples. I will share anything interesting I find.
Bruce, Thank you for your advise. You are right, the learning curve is much greater than some other languages, and the user should be familiar with expert system theory. Yes, I read the examples provided in the code tree, but not all of them, and I'm exploring the other parts of the code tree.
I always benifit from open source projects, so I would like to return something. Being a committer is an honor, but it requires more responsibility. I don't think I have the sufficient skills to become a committer right now (I knew PyKE just less 2 months ago), I don't want to mess up everything. I said I want to write some docs after my project, I meant it. After all these, after proving I can do something useful I will require a committer. If anyone starts the work before me I'm also grad to offer help.
> Sounds like an excellent way to get more examples! I'd be eager to know > what you find when you do this! Maybe you could report interesting examples > back here so that others can also benefit from them?
> Thanks Dante!
> -Bruce
> On Thu, Dec 1, 2011 at 11:40 AM, Dante_Zaupa <dante...@gmail.com> wrote:
>> Hey Zhijun
>> Here's my 2 cents: try searching for "import pyke" in Google, GitHub >> and similar repositories. That ought to find open source projects >> using Pyke.
>> Best regards, >> Dante
>> On Thu, Dec 1, 2011 at 12:57 PM, Bruce Frederiksen <dangy...@gmail.com> >> wrote: >> > Zhijun,
>> > Thank you for your offer of help! I wouldn't worry about your English >> > skills. The hard part is figuring out what needs to be said, how it >> > should >> > be organized and what examples to use. If you can do this, there are >> > many >> > people who can help with the English. You might just write it the best >> > you >> > can (I would suggest not spending too long on the English to keep the >> > flow >> > going smoothly) and then somebody else can clean up the language; or you >> > could prepare an outline with a bullet list of things that need to be >> > said >> > and prepare examples. Then somebody else could write the English.
>> > I wrote the PyKE documentation before Sphinx was available. I am open >> > to >> > either moving to sphinx or to some other documentation tool. I am also >> > willing to make you a committer to the project so that you can commit >> > directly. Just let me know how I can help.
>> > I am wondering if you've looked at the examples provided in the examples >> > source code directory?
>> > Also, PyKE uses a very different computational model than standard >> > procedural programming languages. So the learning curve is much greater >> > than, say, moving from Java to Python. But it is based on prolog >> > (though >> > with different syntax). So maybe some prolog tutorials would be useful?
>> > The Structured Program Theorem states that all programs can be >> > decomposed >> > into 3 control structure: sequence (do A, then do B), selection (do A or >> > do >> > B based on some condition), and repetition (do A many times). Perhaps >> > simple examples of how to do each of these in PyKE would be useful? And >> > then maybe showing how abstraction works (the counterpart to procedural >> > programming's concept of a user-defined function)?
>> > Anyway, welcome aboard!
>> > -Bruce
>> > On Thu, Dec 1, 2011 at 5:30 AM, zhijun wu <pinot...@gmail.com> wrote:
>> >> I can not find any project to study until now. PyKE is great, I think >> >> it's the best way to study PyKE is starting using it.
>> >> Maybe I chose some wrong words in my post that you mention before, for >> >> example the word "ugly". I agree with you, it will be very helpful if >> >> there is some documentations such as "Tutorial", "*** for beginners" >> >> and so on.
>> >> But as we all know, saying is much easier that doing.
>> >> I'm trying to build a real project with PyKE. If I can make it, I >> >> really want to write some docs for beginners. Maybe I will have the >> >> sufficient knowledge to do that at that time. But my native language >> >> is not English, that's a big problem.
>> >> 2011/11/25 Elisiano Petrini <elisi...@gmail.com>: >> >> > Hi pinot and all, >> >> > I'm in the same situation and it would be really useful to see a >> >> > real >> >> > life example.
>> >> > I also saw your other post (about the bad documentation) and I have >> >> > to >> >> > admit >> >> > that I kinda agree with you, even if not fully. >> >> > Actually the documentation is there and is also quite advanced, the >> >> > only >> >> > thing is that it is lacking an introduction for beginners.
>> >> > So hereby I'm asking to the experts, which are the prerequisites in >> >> > order to >> >> > fully understand PyKE and to use it at its best?
>> >> > I'm now doing a project which needs some sort of knowledge base and I >> >> > think >> >> > that PyKE would be the right choice to my case, if only I knew how to >> >> > use >> >> > it.
>> >> > Probably I'm still missing something theoretical here, that's why I'm >> >> > asking >> >> > for some pointers. >> >> > Any help is greatly appreciated.
>> >> > Best Regards, >> >> > Elisiano Petrini
>> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups >> >> > "PyKE" group. >> >> > To view this discussion on the web visit >> >> > https://groups.google.com/d/msg/pyke/-/0m5UIacsDGgJ. >> >> > To post to this group, send email to pyke@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > pyke+unsubscribe@googlegroups.com. >> >> > For more options, visit this group at >> >> > http://groups.google.com/group/pyke?hl=en.
>> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "PyKE" group. >> >> To post to this group, send email to pyke@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> pyke+unsubscribe@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/pyke?hl=en.
>> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "PyKE" group. >> > To post to this group, send email to pyke@googlegroups.com. >> > To unsubscribe from this group, send email to >> > pyke+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/pyke?hl=en.
>> Usuário Linux #459228 -- Linux Mint 11 ("Katya")
>> -- >> You received this message because you are subscribed to the Google Groups >> "PyKE" group. >> To post to this group, send email to pyke@googlegroups.com. >> To unsubscribe from this group, send email to >> pyke+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/pyke?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "PyKE" group. > To post to this group, send email to pyke@googlegroups.com. > To unsubscribe from this group, send email to > pyke+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pyke?hl=en.
