I fed it the livecode reference manual ... i had a pdf of it, not sure
where to find that now. Also the builder documentation from here
https://livecode.com/apidocs/docs/guide.html#livecode-builder-language-reference
I think I might have missed the top section of builder related guides.
and the
what did you send to chatgpt to generate the LC expert model?
On Wed, Jul 24, 2024 at 11:46 AM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Mike,
>
> I also asked it to check over each answer before i accepted it.
> so it is essentially 2-shot instead of the usual 1.
> T
Hi Mike,
I also asked it to check over each answer before i accepted it.
so it is essentially 2-shot instead of the usual 1.
The reason I added the script for httpd is so that it would not need to
figure out correct syntax for socket connections, by having examples of the
correct syntax.
Yes, I su
so, for you, the trick was:
* claude (opus)
* supply some lc source code in a similar universe (curious why you did
that)
* supply the rfc, not just referencing the rfc
anything else?
On Tue, Jul 23, 2024 at 7:31 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hey Mike,
>
>
Hey Mike,
I describe how I did it on the GitHub page. I find all llms work better
when they have a starting point if you ask them just to start from nothing
the performance will be significantly worse.
Examples of correct responses are key so in this case I provided the source
code for the httpd
i'd like to learn more about how you did this.
i have had terrible luck getting any of the LLM's to generate reasonable LC
code (including multiple attempts on this very topic).
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this
t;
> >> Testing will start soon enough.
> >> I started this early so that when inevitably I really need web sockets,
> >> there is some kind of hope.
> >> My main need for this is the ability to stream data like for example
> >> streaming responses
;>
>> Testing will start soon enough.
>> I started this early so that when inevitably I really need web sockets,
>> there is some kind of hope.
>> My main need for this is the ability to stream data like for example
>> streaming responses from openAI voice /
e for example
> streaming responses from openAI voice / chat completions.
>
> https://github.com/MakeShyftRDA/Websockets-for-Livecode
>
> Enjoy.
>
> Tom
> .
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.co
ind of hope.
My main need for this is the ability to stream data like for example
streaming responses from openAI voice / chat completions.
https://github.com/MakeShyftRDA/Websockets-for-Livecode
Enjoy.
Tom
.
___
use-livecode mailing list
use-livecode@l
If you are going to roll your own security with raw sockets, what I had to do
was encrypt the data then base64encode it, then reverse the process on the
other side.
Sent from my iPhone
> On Apr 27, 2024, at 17:56, Richard Gaskin via use-livecode
> wrote:
>
> Bernard Devlin wrote:
>
>> One
Bernard Devlin wrote:
> One thing to bear in mind is that Livecode does not support secure sockets
> (despite what the Dictionary might say).
This is based on the Dictionary example for the "open socket" command. It runs
without error, and the callback works.
on mouseup
open secure sock
LC just provides raw sockets. You can implement a TLS equivalent with a bit of
elbow grease. Writing your own protocol gives a lot of control.
TLS is something you may have to use to check boxes. Out of curiosity is there
a market for something like this within the community?
Sent from my iPho
really? discuss.
On Sat, Apr 27, 2024 at 5:06 PM Bernard Devlin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> One thing to bear in mind is that Livecode does not support secure sockets
> (despite what the Dictionary might say).
>
> On Sat, Apr 27, 2024 at 12:31 AM Richard Gaskin via
One thing to bear in mind is that Livecode does not support secure sockets
(despite what the Dictionary might say).
On Sat, Apr 27, 2024 at 12:31 AM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> - How hard would it be to script it using LC's good socket support?
>
>
it in livecode.
> 2. dunno
> 3. interesting thought, I will look into testing this.
> 4. many blockchains are websockets only, and most API with data "streams".
>
> Mike, I hear you on all that.
>
>> On Fri, Apr 26, 2024 at 7:31 PM Richard Gaskin via use-livecod
Richard, thanks for chiming in.
1. dunno, it can't be that hard, i would take an existing implementation in
another language and rewrite it in livecode.
2. dunno
3. interesting thought, I will look into testing this.
4. many blockchains are websockets only, and most API with data "strea
be to script it using LC's good socket support?
- Is there a curl option available that might allow Charles to handle
this more quickly in tsNet?
- Would it be feasible to use WebSockets through an embedded browser widget?
- What are the use cases requiring WebSockets excluisively?
i'm interested in client side, especially on mobile. we have an app that is
in the wild that would be much better if we could stop pinging the server
every five seconds.
On Fri, Apr 26, 2024 at 4:10 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Folks,
>
> Can we get a
Hi Folks,
Can we get a measure again as to the interest in web sockets implementation
in livecode?
As far as I know we still do not have one that is available or able to be
contributed to,
I'd be willing to put in some engineering time if there was help from
others available.
Here are the full spe
ng for
> > > > someone else to do it?
> > > > Or is there a reason why it hasn't been done in all the years that web
> > > > sockets have been around?
> > > > Shrug.
> > > >
> > > > On Sat, May 20, 2023 at 9:24 AM Mike Ker
ithout waiting for
> > > someone else to do it?
> > > Or is there a reason why it hasn't been done in all the years that web
> > > sockets have been around?
> > > Shrug.
> > >
> > > On Sat, May 20, 2023 at 9:24 AM Mike Kerner via use-livecode <
r
> > someone else to do it?
> > Or is there a reason why it hasn't been done in all the years that web
> > sockets have been around?
> > Shrug.
> >
> > On Sat, May 20, 2023 at 9:24 AM Mike Kerner via use-livecode <
> > use-livecode@lists.runrev.c
e without waiting for
> someone else to do it?
> Or is there a reason why it hasn't been done in all the years that web
> sockets have been around?
> Shrug.
>
> On Sat, May 20, 2023 at 9:24 AM Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
y 20, 2023 at 9:24 AM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> any news from anyone on lc+websockets?
>
> --
> 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 t
any news from anyone on lc+websockets?
--
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
Greetings!
I've been looking around the boards and whatnot and see there has been some
discussion about implementing web sockets in LiveCode. Has anyone come up with
a library or a way to do this effectively for the Big 4 (Windows, Mac, iOS and
Android)?
Thanks in advance,
Dan
__
thing yet.
Thanks for your thoughts.
On Wed, Oct 21, 2020 at 1:01 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 10/21/20 7:09 AM, Tom Glod via use-livecode wrote:
> > Hi Livecoders,
> >
> > Does anyone know if there are any pla
On 10/21/20 7:09 AM, Tom Glod via use-livecode wrote:
Hi Livecoders,
Does anyone know if there are any plans for introducing websockets to
livecode?
Or if there are any working 3rd party implementations that are available?
its been a lot of years.
Thanks,
Charles Warwick has something in
Tom Glod wrote:
> Does anyone know if there are any plans for introducing websockets
> to livecode?
I've not seen any indication of a commitment to add websockets to LC.
Websockets were added to browsers to provide a constrained way to allow
persistent connections without exposin
Hi Livecoders,
Does anyone know if there are any plans for introducing websockets to
livecode?
Or if there are any working 3rd party implementations that are available?
its been a lot of years.
Thanks,
--
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Mobile:647.562.
>
> Hey Todd, did you get this figured out?
>
>
___
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
> Todd wrote:
> I assume that it is a memory leaking error. Has anyone had this problem of
> calling LiveCode function from a JavaScript function in the browser?? This
> is a HUGE problem for us as the app cannot be shipped.
Libbrowser eats on desktop up to 5 MByte of memory per second. Bug #20012
,
Charles
> On 27 Dec 2018, at 3:47 pm, Todd Fabacher via use-livecode
> wrote:
>
> This is a 911 call for HELP from anyone.
>
> We are using a Socket IO server. We tried using the web browser to
> send websockets messages...no problems.
>
> but when we listen and receive
This is a 911 call for HELP from anyone.
We are using a Socket IO server. We tried using the web browser to
send websockets messages...no problems.
but when we listen and receive the websocket message, that is where the
problem is created. If we don't call LiveCode from the web browser, we
Charles,
A WebSockets external would be very beneficial for everyone doing web
stuff from LC. I am looking forward to checking it out when it is
released. :-) Thanks a lot for working on this.
Cheers
andre
On 11/26/2018 6:24 AM, Charles Warwick via use-livecode wrote:
Hi Bob,
The
at 12:44 am, "b...@bobhall.net" wrote:
>
> Charles,
>
> I would like to find out more about your socket external specifically for
> websockets. Can you point me to where I can find out about the socket
> external?
>
> Thanks,
> Bob Hall
>
>> On
Thanks Charles for the reply. Hope all is going well with you. Where can I
test the WebSocket external? I will need it for iOS, Android, Mac, and
Windows. Can you email me directly as we are time sensitive on this please.
We have the server up and running. Socket.io is the BEST in the market and
c
Charles,
I would like to find out more about your socket external specifically for
websockets. Can you point me to where I can find out about the socket external?
Thanks,
Bob Hall
> On Nov 23, 2018, at 1:10 AM, Charles Warwick via use-livecode
> wrote:
>
> Hi Todd,
>
>
ps > requires websocketd to go along with it.
On Fri, Nov 23, 2018 at 1:46 AM Tom Glod wrote:
> Todd, this was posted here a little while ago..haven't tested it, but
> apparently its websockets for livecode. Let us know how it goes.
>
> https://github.com/samansjukur/wsl
Todd, this was posted here a little while ago..haven't tested it, but
apparently its websockets for livecode. Let us know how it goes.
https://github.com/samansjukur/wslc
On Fri, Nov 23, 2018 at 1:10 AM Charles Warwick via use-livecode <
use-livecode@lists.runrev.com> wrote:
Hi Todd,
Depending on what platforms you need to support, I have a socket external for
LiveCode that includes the ability to use websockets.
Cheers,
Charles
> On 23 Nov 2018, at 4:09 pm, Todd Fabacher via use-livecode
> wrote:
>
> We have hot a wall because we have an API
We have hot a wall because we have an API that is ONLY accessible via a
call to Socket.io server using Websockets.
Richard Gaskin, I remember you were looking into this last year, any
success from your research.
It seems the best way would be to open a web browser and code the
communications
Many thanks for this useful reference link Andrew
Le 9 juil. 2013 à 02:32, Andrew Kluthe a écrit :
> I had read that, and found some other useful info here as well.
> https://github.com/LearnBoost/socket.io-spec
>
> Andrew
--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.com
>> Would you care to discuss the difference between websockets and the
>>socketswe work with in livecode or point me to some basic information on the
websocket implementation you think we could implement in pure livecode?
What things would keep it from working very efficiently?
Pierre Sahores
To: How to use LiveCode
Sent: Tuesday, 9 July 2013, 0:56
Subject: Re: LiveCode and WebSockets
Mark ,
Should work (untested) :
Node.js on the server side + revBrowser (desktop) or mobileBrowser
(iOS/android) + some js + client-side pseudo urls to get catched
by :
on brows
ile.html…) in your client app sandboxed cache or document
> directory to be catchable on the Android platform at least. To maintain a
> common codebase with the iOS app, i have the habit to create the on this
> platform too.
>
> Pierre
>
> Le 8 juil. 2013 à 20:35, Mark Wi
now, I'm interested in websockets for realtime comms between apps. Right
> now I think it'd be possible to implement one or more of the supported
> transports for socket.io in pure LiveCode but maybe not very efficiently. An
> alternative would be to wrap existing native implem
n the next few years if we were to see
sockets and UI (resolution independence, etc) improvements on mobile.
and websockets are very definitely not the same thing as standard sockets.
I am having a hard time just finding straight forward info on the lower
level websocket information. As of right no
are
> doing most of our mobile apps as mobile web apps.
>
> However, this will change likely in the next few years if we were to see
> sockets and UI (resolution independence, etc) improvements on mobile.
>
>
> >>and websockets are very definitely not the same thin
sockets and UI (resolution independence, etc) improvements on mobile.
>>and websockets are very definitely not the same thing as standard sockets.
I am having a hard time just finding straight forward info on the lower
level websocket information. As of right now all the information I am
We know, I'm interested in websockets for realtime comms between apps. Right
now I think it'd be possible to implement one or more of the supported
transports for socket.io in pure LiveCode but maybe not very efficiently. An
alternative would be to wrap existing native implemen
in using something like socket.io as part of a backend for
> mobile (and maybe also desktop) apps. However, we don't have proper sockets
> support on mobile (without externals at least) and websockets are very
> definitely not the same thing as standard sockets.
>
> Wh
I'm interested in using something like socket.io as part of a backend for
mobile (and maybe also desktop) apps. However, we don't have proper sockets
support on mobile (without externals at least) and websockets are very
definitely not the same thing as standard sockets.
What do y
I have been learning a little bit about websockets lately for a project and
I have never really played around with livecode's socket communication
methods. This makes me curious.
Is there anyone else on the list that might be more familiar with both that
would be interested in discussing
55 matches
Mail list logo
