Re: pengines extension to html_requires
Anne Ogborn <[email protected]>
| Newsgroups | gmane.comp.ai.prolog.swi |
|---|---|
| Message-ID | <[email protected]> |
Suggestion - write a set of REAL demos - that is, something like a chat room, or other bare bones version of something someone would actually use, that uses all the API's. Any that you feel strained to come up with a use for should probably be private. API's are just that - interfaces to let application programmers use your code. They need to 'talk' in terms the application programmer understands and make common use cases simple. I'm swimming in a see of 'how would I?' questions with pengine. How would I write a chat room? How would I write an online tool that taught prolog concepts in a sandbox? How would I write an online collaborative programming tool that let validated user prolog programmers work on the same file, submitting it to the make process? How would I make a LAN of systems that monitor sensors and collate the data in a central place for processing, then send messages back to effectors? How would I use pengines to make a home rolled mapreduce on data in a cloud? How would I use pengines with a prolog based semantic web? What applications am I not seeing because I don't understand the system? I really can't answer any of these, beyond using pengine as a rather useless wrapper around ajax. I'm sure there's a lot more there. But if you don't make the bulb go on in the API programmers head, internal brilliance is useless. Oo 8cD <-- Annie with lightbulb on