vbatts/llama.cpp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

SimpleChat: Update title, usage and readme a bit

Browse source 
Keep the title simple so that print file name doesnt have chars
that need to be removed.

Update readme wrt some of the new helpers and options.

Change Usage list to a list of lists, add few items and style it
to reduce the margin wrt lists.
This commit is contained in:
HanishKVC 2024-05-23 15:43:41 +05:30
parent 073eae6778
commit 59f74c7de9
4 changed files with 40 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
examples/server/public_simplechat/index.html
View file

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>SimpleChat (LlamaCPP, ...) </title>
<title>SimpleChat LlamaCppEtal </title>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="message" content="Save Nature Save Earth" />

20
examples/server/public_simplechat/readme.md
View file

@ -68,6 +68,8 @@ Once inside
can use it just for normal completion related/based query.
* If you want to provide a system prompt, then ideally enter it first, before entering any user query.
Normally Completion mode doesnt need system prompt, while Chat mode can generate better/interesting
responses with a suitable system prompt.
* if chat.add_system_begin is used
* you cant change the system prompt, after it is has been submitted once along with user query.
* you cant set a system prompt, after you have submitted any user query
@ -91,6 +93,13 @@ Once inside
## Devel note
gChatRequestOptions maintains the list of options/fields to send along with chat request,
irrespective of whether /chat/completions or /completions endpoint.
If you want to add additional options/fields to send to the server/ai-model, and or
modify the existing options value, for now you can update this global var using
browser's development-tools/console.
Sometimes the browser may be stuborn with caching of the file, so your updates to html/css/js
may not be visible. Also remember that just refreshing/reloading page in browser or for that
matter clearing site data, dont directly override site caching in all cases. Worst case you may
@ -103,3 +112,14 @@ not been added, for now.
By switching between chat.add_system_begin/anytime, one can control whether one can change
the system prompt, anytime during the conversation or only at the beginning.
read_json_early, is to experiment with reading json response data early on, if available,
so that user can be shown generated data, as and when it is being generated, rather than
at the end when full data is available.
the server flow doesnt seem to be sending back data early, atleast for request (inc options)
that is currently sent.
if able to read json data early on in future, as and when ai model is generating data, then
this helper needs to indirectly update the chat div with the recieved data, without waiting
for the overall data to be available.

7
examples/server/public_simplechat/simplechat.css
View file

@ -48,6 +48,13 @@ button {
flex-direction: column;
}
.ul1 {
padding-inline-start: 2vw;
}
.ul2 {
padding-inline-start: 2vw;
}
* {
margin: 0.6vmin;
}

16
examples/server/public_simplechat/simplechat.js
View file

@ -14,13 +14,21 @@ class ApiEP {
}
let gUsageMsg = `
<ul>
<ul class="ul1">
<li> Set system prompt above, to try control ai response charactersitic, if model supports same.</li>
<li> + Completion mode normally wont have a system prompt.</li>
<ul class="ul2">
<li> Completion mode normally wont have a system prompt.</li>
</ul>
<li> Enter your query to ai assistant below.</li>
<li> + Completion mode doesnt insert user/role: prefix implicitly.</li>
<li> + Use shift+enter for inserting enter/newline.</li>
<ul class="ul2">
<li> Completion mode doesnt insert user/role: prefix implicitly.</li>
<li> Use shift+enter for inserting enter/newline.</li>
</ul>
<li> Refresh the page to start over fresh.</li>
<ul class="ul2">
<li> old chat is not culled when sending to server/ai-model.</li>
<li> either use New CHAT, or refresh if chat getting long.</li>
</ul>
</ul>
`;