[skn3Participant]

nerobot, you the bomb!

[skn3Participant]

feature creep, always feature creep

[skn3Participant]

Been working with ted2go more today. A suggestion:

Can auto complete lists be sorted by a combination of casing, length and distance/popularity?

casing
If I type Item then the list should prioritise ItemBlah over itemBlah

length
If i type appl then the list should prioritise apple over AppleColor

distance/usage (not as important as casing and length)
The list should try and sort by number popularity of keyword and also the closest recent usage of keyword. So for example if i define a Local variable, then autocomplete should favour this over variables further away in the file.

[skn3Participant]

Given a quick test, seems like it doesn’t redraw properly on startup when the flag is set. I have just a black screen. I have to manually find a gadget in the dark (mojox) that will trigger the redraw. It looks like if you set a smaller window size then the actual maximised sized, then this is where it does not redraw properly.

Also noticed there is no way to capture when the maximised state in the Window class. Would be nice to get a .Maximized and .Minimized Property on Window.

This works:

Monkey

[crayon-5cba820e5c1a0647449740 inline="true" ] Cast<SDL_WindowFlags>(SDL_GetWindowFlags(window.SDLWindow)) & SDL_WINDOW_MAXIMIZED

1 2 3

[crayon-5cba820e5c1a0647449740 inline="true" ] Cast<SDL_WindowFlags>(SDL_GetWindowFlags(window.SDLWindow)) & SDL_WINDOW_MAXIMIZED

[/crayon]

Could we have new events to wrap the SDL ones too:

Monkey

[crayon-5cba820e5c1b6145748505 inline="true" ] SDL_WINDOWEVENT_MAXIMIZED SDL_WINDOWEVENT_MINIMIZED SDL_WINDOWEVENT_RESTORED

1 2 3 4 5

[crayon-5cba820e5c1b6145748505 inline="true" ] SDL_WINDOWEVENT_MAXIMIZED SDL_WINDOWEVENT_MINIMIZED SDL_WINDOWEVENT_RESTORED

[/crayon]

There doesn’t seem to be a way to capture these without modifying mojo. Would it be possible to add a RawEvent:Void() callback to the app class? So we can hook into all SDL events, even ones not captured into mojo?

[skn3Participant]

winner thanks

[skn3Participant]

Liking ted2go so far, good work!

Can I suggest switching the icons to something a bit more monochrome (and modern looking) to fit with the solid color theme of ted2?
http://fontawesome.io/icons/

Handy tool here for converting to png:
http://fa2png.io/r/font-awesome/

[skn3Participant]

winner! so let me tell you some more about promises!

lol

Monkey

[crayon-5cba820e66937888952707 inline="true" ]function ItemPromise(id) { return new Promise(function(resolve, reject) { let item = {}; //get the item or do something //finished resolve(item); }); } let jobs = []; for(let index = 0; index < 20;index++) { jobs.push(ItemPromise(index)); } Promise.all(jobs).then(function(items) { //we now have 20 items that have been fetched async, all 20 items are being fetched at the same time, with little setup! }).catch(function(err) { console.log('something went wrong'); });

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

[crayon-5cba820e66937888952707 inline="true" ]function ItemPromise(id) { return new Promise(function(resolve, reject) { let item = {}; //get the item or do something //finished resolve(item); }); }   let jobs = []; for(let index = 0; index < 20;index++) { jobs.push(ItemPromise(index)); }   Promise.all(jobs).then(function(items) { //we now have 20 items that have been fetched async, all 20 items are being fetched at the same time, with little setup! }).catch(function(err) { console.log('something went wrong'); });

[/crayon]

I dunno, but this just pleases me.

[skn3Participant]

I think the benefit of promises cant really be shown in just one small snippet. For promises to be useful, everything has to be promises. So fetching from database, a promise. Creating an object, promise. Everything a promise. Then you can just encapsulate all your routines as promises. You can flow them together without really thinking. You can have one catch to rule them all as well. Regardless of which library the promise lives.

But pretty much your correct. Promises are are to *fix* javascript lack of async/fiber. They were also introduced to solve the problem of a nested nightmare of callbacks.

However javascript does have async/await on the horizon https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function it’s just not fully mainstream yet. I get the impression they are implementing this to *fix* the issues that promises brought with it.

But yeah going off topic a little. I agree with tyou, mx2 should not go the promise route. The async/await using fibers/futures is much nicer!

[skn3Participant]

Well how about something like this:

Monkey

[crayon-5cba820e6d427332138306 inline="true" ]function loadUser() { return fetchUserData("skn3") .then(function(user) { return downloadImage(user); }); } function fetchUserData(id) { return new Promise(resolve, reject) { return database.users.query.where('username',id) .then(function(user) { if (user.banned) { reject(new Error('access denied')); } else { resolve(user); } }); } } function downloadImage(user) { return new Promise(function(resolve, reject) { if (!network.isConnected) { reject(new Error('not connected foo)); } else { let localPath = '/localFiles/users/'+user.username+'.png'; return network.get('http://www.images.com/users/'+user.username+'.png', localPath) .then(function(image) { user.image = localPath; resolve(user); }); } }) } class userWidget() { constructor(id) { this.id = id; this.user = null; this.div = document.append this.div = document.createElement('div'); this.div.style.width = '100px'; this.div.style.height = '100px'; let that = this; this.div.addEventListener('click',function(event) { if (that.user == null) { that.load(); } }); document.body.appendChild(this.div); } load() { let that = this; loadUser(this.id) .then(function(user) { that.user = user; that.div.style.backgroundImage = 'url('+user.localPath+')'; }) .catch(function(err) { console.log('failed'); }) } }

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69

[crayon-5cba820e6d427332138306 inline="true" ]function loadUser() { return fetchUserData("skn3") .then(function(user) { return downloadImage(user); }); }   function fetchUserData(id) { return new Promise(resolve, reject) { return database.users.query.where('username',id) .then(function(user) { if (user.banned) { reject(new Error('access denied')); } else { resolve(user); } }); } }   function downloadImage(user) { return new Promise(function(resolve, reject) { if (!network.isConnected) { reject(new Error('not connected foo)); } else { let localPath = '/localFiles/users/'+user.username+'.png'; return network.get('http://www.images.com/users/'+user.username+'.png', localPath) .then(function(image) { user.image = localPath; resolve(user); }); } }) }   class userWidget() { constructor(id) { this.id = id; this.user = null; this.div = document.append this.div = document.createElement('div'); this.div.style.width = '100px'; this.div.style.height = '100px'; let that = this; this.div.addEventListener('click',function(event) { if (that.user == null) { that.load(); } }); document.body.appendChild(this.div); } load() { let that = this; loadUser(this.id) .then(function(user) { that.user = user; that.div.style.backgroundImage = 'url('+user.localPath+')'; }) .catch(function(err) { console.log('failed'); }) } }

[/crayon]

I can create modular promises that can perform async operations, and then have one final destination for catching exceptions.

async and await are nice, but at the same time promises do have their merits. They fall down when you need to pass around more information then just one thing. You either have to contain the data in the parent closure, or build objects by passing it down the .then() chain. Its also possible to use Promise.all([]) and then build your object at the end. The .then() of Promise.all([]) receives an array with each promises result.

[skn3Participant]

Well clearly myn is a fugly LOL! I was trying to make it a self contained pattern, also similar to javascript with the commands passed to the callback/promise.

Anyway, I just tried your version and this works a charm. My example modified to yours:

Monkey

[crayon-5cba820e72e3b649935654 inline="true" ]Namespace myapp #Import "<std>" #Import "<mojo>" Using std.. Using mojo.. 'await code Function Await<T>:T(future:Future<T>) Return future.Get() End Function Async:Future<Int>(callback:Int()) Local future:=New Future<Int> New Fiber(Lambda() Local result:=callback() future.Set(result) End) Return future End Function Main:Void() New AppInstance New MyWindow App.Run() End Class MyWindow Extends Window Method OnRender( canvas:Canvas ) Override App.RequestRender() canvas.DrawText( "Hello World! "+Rnd(0,1),Width/2,Height/2,.5,.5 ) End Method OnKeyEvent( event:KeyEvent ) Override If event.Type = EventType.KeyUp Select event.Key Case Key.Space 'create wrapper fiber so we are not executing on main fiber New Fiber(Lambda() 'await value Print Await<Int>(Async(Lambda:Int() Local start := App.Millisecs While App.Millisecs - start < 3000 Fiber.Sleep(0) Wend Return 555 End)) Print Await<Int>(Async(Lambda:Int() Local start := App.Millisecs While App.Millisecs - start < 3000 Fiber.Sleep(0) Wend Return 123 End)) End) End Endif End End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65

[crayon-5cba820e72e3b649935654 inline="true" ]Namespace myapp   #Import "<std>" #Import "<mojo>"   Using std.. Using mojo..   'await code Function Await<T>:T(future:Future<T>)     Return future.Get() End Function Async:Future<Int>(callback:Int())     Local future:=New Future<Int>     New Fiber(Lambda()          Local result:=callback()          future.Set(result)     End)     Return future End   Function Main:Void() New AppInstance New MyWindow App.Run() End   Class MyWindow Extends Window Method OnRender( canvas:Canvas ) Override App.RequestRender() canvas.DrawText( "Hello World! "+Rnd(0,1),Width/2,Height/2,.5,.5 ) End Method OnKeyEvent( event:KeyEvent ) Override If event.Type = EventType.KeyUp Select event.Key Case Key.Space 'create wrapper fiber so we are not executing on main fiber New Fiber(Lambda() 'await value Print Await<Int>(Async(Lambda:Int() Local start := App.Millisecs While App.Millisecs - start < 3000 Fiber.Sleep(0) Wend Return 555 End)) Print Await<Int>(Async(Lambda:Int() Local start := App.Millisecs While App.Millisecs - start < 3000 Fiber.Sleep(0) Wend Return 123 End)) End) End Endif End End

[/crayon]

So your correct about the theory. Once you start pushing around those async operations you have to keep doing so.

I have had most experience using Promises in Javascript. With those you fire off a ton of operations which signal to the promise when they are complete. Like so:

Monkey

[crayon-5cba820e72e41952246975 inline="true" ]New Promise(function(resolve,reject) { 'do something blocking let success = blocking(); if (success) { resolve(123); } else { reject(new Error('uh oh)); } }).then(result) console.log(result);'123 .catch(function(err){ 'errortime })

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

[crayon-5cba820e72e41952246975 inline="true" ]New Promise(function(resolve,reject) { 'do something blocking let success = blocking(); if (success) { resolve(123); } else { reject(new Error('uh oh)); } }).then(result) console.log(result);'123 .catch(function(err){ 'errortime })

[/crayon]

The awesomeness is you can keep returning new promises from your promise, or your .then() to chain together functionality into you callbacks. So you can break your code up into say, fetchUser(), generateImage(), updateCounters(), etc and have each return a promise. You can then piece together complex tasks and receive your result back in a chain of .then()’s.

There is also Promise.All([]) which fires off a list of promises at once, and then() is called once all have finished.

But anyway…

[skn3Participant]

I removed my code above as was getting it to work. And here is the finished result

Monkey

[crayon-5cba820e78d13995836044 inline="true" ]Namespace myapp #Import "<std>" #Import "<mojo>" Using std.. Using mojo.. 'await code Function Await<T>:T(callback:Void(Resolve:Void(value:T),Yield:Void())) Local future := New Future<T> 'create fiber to handle our await Local fiber := New Fiber(Lambda() 'sleep the fiber so we get a chance to start the future Fiber.Sleep(0) 'execute callback callback(Lambda(value:T) 'Resolve() future.Set(value) End, Lambda() 'Yield() Fiber.Sleep(0) End) End) Return future.Get() End Function Main:Void() New AppInstance New MyWindow App.Run() End Class MyWindow Extends Window Method OnRender( canvas:Canvas ) Override App.RequestRender() canvas.DrawText( "Hello World! "+Rnd(0,1),Width/2,Height/2,.5,.5 ) End Method OnKeyEvent( event:KeyEvent ) Override If event.Type = EventType.KeyUp Select event.Key Case Key.Space 'create wrapper fiber so we are not executing on main fiber New Fiber(Lambda() 'await value Print Await<Int>(Lambda(Resolve:Void(value:Int), Yield:Void()) Local start := App.Millisecs While App.Millisecs - start < 3000 Yield() Wend Resolve(123) End) 'await value Print Await<Int>(Lambda(Resolve:Void(value:Int), Yield:Void()) Local start := App.Millisecs While App.Millisecs - start < 2000 Yield() Wend Resolve(555) End) End) End Endif End End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74

[crayon-5cba820e78d13995836044 inline="true" ]Namespace myapp   #Import "<std>" #Import "<mojo>"   Using std.. Using mojo..   'await code Function Await<T>:T(callback:Void(Resolve:Void(value:T),Yield:Void())) Local future := New Future<T> 'create fiber to handle our await Local fiber := New Fiber(Lambda() 'sleep the fiber so we get a chance to start the future Fiber.Sleep(0) 'execute callback callback(Lambda(value:T) 'Resolve() future.Set(value) End, Lambda() 'Yield() Fiber.Sleep(0) End) End) Return future.Get() End   Function Main:Void() New AppInstance New MyWindow App.Run() End   Class MyWindow Extends Window Method OnRender( canvas:Canvas ) Override App.RequestRender() canvas.DrawText( "Hello World! "+Rnd(0,1),Width/2,Height/2,.5,.5 ) End Method OnKeyEvent( event:KeyEvent ) Override If event.Type = EventType.KeyUp Select event.Key Case Key.Space 'create wrapper fiber so we are not executing on main fiber New Fiber(Lambda() 'await value Print Await<Int>(Lambda(Resolve:Void(value:Int), Yield:Void()) Local start := App.Millisecs While App.Millisecs - start < 3000 Yield() Wend Resolve(123) End) 'await value Print Await<Int>(Lambda(Resolve:Void(value:Int), Yield:Void()) Local start := App.Millisecs While App.Millisecs - start < 2000 Yield() Wend Resolve(555) End) End) End Endif End End

[/crayon]

[skn3Participant]

.

[skn3Participant]

When I was writing the previous reply, trying to ponder the ramifications of the Async suggestion, I did burn a few thousand braincells in the process! So yeah thats gonna be a long trip down the rabbit hole if you go that route!

The mojox thing does sound like a decent stop gap, as your not gonna break anything core in monkey2.

.

[skn3Participant]

Yeah the JS editor is a pain in the ass when adding code! Is there a markdown plugin for wordpress? Would be nice to use that instead! (https://en.support.wordpress.com/markdown/)

Well I guess everything would have to be on a fiber. Anything else and you are always going to find a scenario where this may happen?

Could we potentially tag our functions/lambdas as async, which indicates their calling mechanism? So it could be used like so:

Monkey

[crayon-5cba820e81f50726555112 inline="true" ]Function DoFiberThing:Void() Async Local value := TextDialog.Run("blah blah",text,New String[]("ok")) End list.Clicked += DoFiberThing

1 2 3 4

[crayon-5cba820e81f50726555112 inline="true" ]Function DoFiberThing:Void() Async Local value := TextDialog.Run("blah blah",text,New String[]("ok")) End list.Clicked += DoFiberThing

[/crayon]

or

Monkey

[crayon-5cba820e81f56177301264 inline="true" ]list.Clicked += Async() 'this is a lambda, but async version End

1 2 3

[crayon-5cba820e81f56177301264 inline="true" ]list.Clicked += Async() 'this is a lambda, but async version End

[/crayon]

I am surprised that emscripten doesn’t support fibers. future versions of JS will have generators, which are similar… https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*

[skn3Participant]

I created a small util function:

Monkey

[crayon-5cba820e85b32742638168 inline="true" ]Function CallFunction:Void(func:Void()) #if __TARGET__ <> "emscripten" New Fiber(func) #Else func() #endif End

1 2 3 4 5 6 7

[crayon-5cba820e85b32742638168 inline="true" ]Function CallFunction:Void(func:Void()) #if __TARGET__ <> "emscripten" New Fiber(func) #Else func() #endif End

[/crayon]

Which is used like:

Monkey

[crayon-5cba820e85b37757301478 inline="true" ]list.ItemClicked = Lambda(item:ListView.Item) CallFunction(Lambda() DoFiberThing(item.Text) End) End

1 2 3 4 5

[crayon-5cba820e85b37757301478 inline="true" ]list.ItemClicked = Lambda(item:ListView.Item) CallFunction(Lambda() DoFiberThing(item.Text) End) End

[/crayon]

It doesn’t work. Now it fails to build with

C:/dev/projects/monkey1/conveyor/tools/itemMaker/itemMaker.buildv1.0.91/windows_debug/src/itemMaker_classes_2utils.cpp:192:27: error: declaration of ‘t_std_fiber_Fiber l_func’ shadows a parameter

t_std_fiber_Fiber(l_func);

If I change it to the follow, then it works:

Monkey

[crayon-5cba820e85b3d146097767 inline="true" ]Function CallFunction:Void(func:Void()) #if __TARGET__ <> "emscripten" New Fiber(Lambda() func() End) #Else func() #endif End

1 2 3 4 5 6 7 8 9

[crayon-5cba820e85b3d146097767 inline="true" ]Function CallFunction:Void(func:Void()) #if __TARGET__ <> "emscripten" New Fiber(Lambda() func() End) #Else func() #endif End

[/crayon]

But this does seem a bit cludge!

[Author]

Posts