[X] My Assistant

Had some time to actually write (big word, just used one from auctioneer) parser and some ui. Button in top right corner acts as trigger for dropdown dialog with queued items list and buttons 'send' and 'clear'. Any changes need?

(Screenshot with disabled item existence check - otherwise only black "not found" will appear)

I think i also could do automatic limits checking and share data between different PCs using some post in shop thread. How much characters allowed in one message in thread?

around 45000 character, but i don't know the exact amount.

just wondering, why that ''don't send'' thing? item exists, still in FS possession and requested... have i missed something? (IMG:[invalid] style_emoticons/default/huh.gif)

Am I right, you need to have repaired version of that script which was broken by 0.80 version (as minimum requirement)?

around 45000 character, but i don't know the exact amount.

just wondering, why that ''don't send'' thing? item exists, still in FS possession and requested... have i missed something? (IMG:[invalid] style_emoticons/default/huh.gif)

It's a button, and text on it represents action that would be taken on click. Green background for items that could be sent, orange for items that already queued for another user, blue for items that would be sent to user when you choose so and, finally, black for items that didn't found in inventory.

Today i try to complete ui and sending function, if i have time i also run mock test and send something to FreeSHop using script.

This post has been edited by Razor320: Sep 16 2014, 14:47

Am I right, you need to have repaired version of that script which was broken by 0.80 version (as minimum requirement)?

yep. the bare minimum (IMG:[invalid] style_emoticons/default/rolleyes.gif)

It's a button, and text on it represents action that would be taken on click. Green background for items that could be sent, orange for items that already queued for another user, blue for items that would be sent to user when you choose so and, finally, black for items that didn't found in inventory.

Today i try to complete ui and sending function, if i have time i also run mock test and send something to FreeSHop using script.

oh, it was only a graphical display then. i knew i didn't catch something, thanks (IMG:[invalid] style_emoticons/default/biggrin.gif)

I'm back and have some code to quickly recycle into this challenge.
I don't plan on addressing all of the requirements and won't be competing for the reward.

Would it be safe to assume that recent versions of Chrome/Firefox will be used to manage the free shop?

window.postMessage (as used in the script attached to the first post) is fairly well-supported in the latest versions of modern browsers.
It also breaks spectacularly in older versions (e.g. Chrome 23), which some users may be clinging onto for performance reasons.

your support is gladly appreciated nonetheless (IMG:[invalid] style_emoticons/default/smile.gif)

Would it be safe to assume that recent versions of Chrome/Firefox will be used to manage the free shop?

i guess so. personally i use firefox 30/32 (don't really remember which one) and pretty sure ai does so too. don't know as for piyin and the girl though

ctxl, modern Chrome and Firefox also supports cross-domain XMLHttpRequests in userscripts through one of GM_api - GM_xmlhttpRequest. It is far more convenient than message way. Firefox requires one of user scripting extensions, Scriptish or GreaseMonkey, and Chrome provides this api natively (though don't know from which version it is available, but users of old versions could install Tampermonkey, which also provides this api).

I implemented requests history in script. Size optimized, so single post in forum thread could contain around 4000 records (1 item - 1 record). Ban-list also could be stored in forum message to provide a simple way to exchange lists between different PCs. And notify users (IMG:[invalid] style_emoticons/default/smile.gif)

[a.pomf.se] The approach I cobbled together uses postMessage for two-way communication.

I gave globally-scoped XHR a try and it went kaboom if you had multiple instances running.

[a.pomf.se] The approach I cobbled together uses postMessage for two-way communication.
I gave globally-scoped XHR a try and it went kaboom if you had multiple instances running.

Don't use GM_xmlhttpRequest in this situation, keep using window.postMessage instead.
For GM_xmlhttpRequest, every time a message is sent, there is a network communication.
For window.postMessage, all messages are passed using [javascript.info] internal browser API, i.e. no network communication at all.
So basically, keep using window.postMessage whenever you can, or the browser might go kaboom like you said.

This post has been edited by djackallstar: Sep 18 2014, 12:48

[a.pomf.se] The approach I cobbled together uses postMessage for two-way communication.

I gave globally-scoped XHR a try and it went kaboom if you had multiple instances running.

And why are you trying to use same stateful object in several concurrent threads?

Don't use GM_xmlhttpRequest in this situation, keep using window.postMessage instead.
For GM_xmlhttpRequest, every time a message is sent, there is a network communication.
For window.postMessage, all messages are passed using [javascript.info] internal browser API, i.e. no network communication at all.
So basically, keep using window.postMessage whenever you can, or the browser might go kaboom like you said.

XMLHttpRequest has no relation to what goes in browser window.

And why are you trying to use same stateful object in several concurrent threads?

Web workers.

Ended?

I have written new script since last weekend, and I hope to finish within a day.

Ended?

I have written new script since last weekend, and I hope to finish within a day.

worry not, we'll update the topic whenever we will be done. until now, there's still time to submit a script

100 hath added to script fund

yep. quest is still open (IMG:[invalid] style_emoticons/default/cool.gif)

I'll bump this.
Hate to see Freeshop suffer. (IMG:[invalid] style_emoticons/default/sad.gif)

many thanks. and i confirm we're still in need of a script

Sent a little incentive to help with the fix

This post has been edited by jacksonville: Oct 24 2014, 06:36

recieved and introduction post updated consequently, many thanks (IMG:[invalid] style_emoticons/default/smile.gif)

we're still here and in need for it (IMG:[invalid] style_emoticons/default/unsure.gif)