Alfred KAT

[godbout]

a little update. dropping PHP 7.1 that is not supported anymore. adding support for 7.4. refactored using my new alfred-workflow-workflow package. links in first page.

[godbout]

4.1.0 released. just a little update. inner grooming, smaller Workflow, consistent with old and new coming ones that will share the same Workflow Skeleton.

 

links in first page.

[godbout]

5.0.0 release. Apple Music in Macau lost some albums so had to use KAT. but ended up with lots of porn links. so added #tags. links in first page.

 

P.S.: tags only work at the end coz i'm lazy.

P.S.2.: wrong tags will return nothing. coz i'm lazy.

[xilopaint]

21 minutes ago, godbout said:

5.0.0 release. Apple Music in Macau lost some albums so had to use KAT. but ended up with lots of porn links. so added #tags. links in first page.

 

P.S.: tags only work at the end coz i'm lazy.

P.S.2.: wrong tags will return nothing. coz i'm lazy.

 

You are not lazy if you use your dash docset builder to make this requested docset . 😃

Edited January 26, 2021 by xilopaint

[godbout]

3 minutes ago, xilopaint said:

 

You are not lazy if you use your dash docset builder to make this requested docset . 😃

i'm lazy coz i just build exactly for my needs 😃️

 

you lucky. i built the dash docset builder for people like you! can build your own docset 😂️

 

(your pine thing is just one page?)

[xilopaint]

3 minutes ago, godbout said:

you lucky. i built the dash docset builder for people like you! can build your own docset 😂️

 

I would love to create my own docsets but I don't have a clue on PHP and can barely understand the README of the builder's repo. 😞

 

3 minutes ago, godbout said:

(your pine thing is just one page?)

 

It seems to be.

[godbout]

4 minutes ago, xilopaint said:

 

I would love to create my own docsets but I don't have a clue on PHP and can barely understand the README of the builder's repo. 😞

 

 

It seems to be.

LOL

 

alright. i'll have a look this week.

[godbout]

can you multiquote on this forum without having to copy paste stuff?

[xilopaint]

3 minutes ago, godbout said:

LOL

 

alright. i'll have a look this week.

 

Thanks!!!

 

2 minutes ago, godbout said:

can you multiquote on this forum without having to copy paste stuff?

 

I think only for different posts.

[xilopaint]

Hey, I suggest you to use OneUpdater to add auto-update capability to Alfred Kat. It's very easy to implement.

Edited January 26, 2021 by xilopaint

[deanishe]

1 hour ago, godbout said:

can you multiquote on this forum

 

Select the text you want to quote, then

 

1 hour ago, godbout said:

without having to copy paste stuff?

 

use the "Quote selection" button.

 

[godbout]

14 hours ago, xilopaint said:

Hey, I suggest you to use OneUpdater to add auto-update capability to Alfred Kat. It's very easy to implement.

oh. had never heard about this. cool. i'll have a look. thanks!

 

(although i'll have to see if it includes the possibility to give a change log. easier to post the new stuff on GitHub/here and get people to read them there/here.)

[godbout]

13 hours ago, deanishe said:

use the "Quote selection" button.

 

1 minute ago, godbout said:

oh. had never heard about this. cool. i'll have a look. thanks!

 

[vitor]

5 hours ago, godbout said:

although i'll have to see if it includes the possibility to give a change log.

Kind of. A major goal of OneUpdater is to be “set and forget” (and easy to remove). You should only have to edit its short configuration once and never again worry about it.

 

There’s two main ways updates can happen: the new version is auto-downloaded and opened, or a web page is opened (and the user manually downloads from there). The latter is specifically geared for versatility of cases (like yours). If sending users to a releases page with the change log and download link is acceptable, it will work.

[godbout]

4 hours ago, vitor said:

Kind of. A major goal of OneUpdater is to be “set and forget” (and easy to remove). You should only have to edit its short configuration once and never again worry about it.

 

There’s two main ways updates can happen: the new version is auto-downloaded and opened, or a web page is opened (and the user manually downloads from there). The latter is specifically geared for versatility of cases (like yours). If sending users to a releases page with the change log and download link is acceptable, it will work.

cool. i'll have a deeper look when i update one of my workflow. thanks!

[godbout]

On 1/26/2021 at 11:54 PM, xilopaint said:

 

You are not lazy if you use your dash docset builder to make this requested docset . 😃

ok so this Docset is shit, sorry 😂️  it's even more shit than the Stripe one. it's not a doc page itself, lots of links pointing basically to the whole site. tried to strike them one by one, but still missing a bunch of unrelated JS but that still breaks the reference. and the reference itself seems to be using a pile of JS, like Stripe. a mega nightmare.

 

i'm trying to download the WHOLE site to see if that kinda works but it's even mega slow. sorry, doesn't seem to be worth it. i'm not even gonna maintain it at the end. not using it.

 

this other page is much better, more like a doc one: https://www.tradingview.com/pine-script-docs/en/v4/index.html

 

would that be useful to you or not?

[xilopaint]

16 hours ago, godbout said:

this other page is much better, more like a doc one: https://www.tradingview.com/pine-script-docs/en/v4/index.html

 

would that be useful to you or not?

 

The User Manual is useful, but not as useful as the Language Reference Manual. I don't want to waste your time. I asked that assuming your builder could make it easy. Thanks anyway!

 

Yesterday I managed to create my first docset from a Sphinx based doc using doc2dash. It's great!

 

Btw, do you know some tool that could be used to convert this documentation in a dash docset?

[godbout]

5 hours ago, xilopaint said:

 

The User Manual is useful, but not as useful as the Language Reference Manual. I don't want to waste your time. I asked that assuming your builder could make it easy. Thanks anyway!

 

Yesterday I managed to create my first docset from a Sphinx based doc using doc2dash. It's great!

 

Btw, do you know some tool that could be used to convert this documentation in a dash docset?

 

for most of the smart docs, the builder runs smoothly. by smart docs i mean a bunch of static files, some css and js that you can grab from wget/curl. there's a few shit docs that generate some js/css dynamically. if you download the docs through wget, then you end up with a lot of things missing. this is the case with your Pine Script stuff. i get maybe twenty asset files, but there's another 200 generated by a runtime.js. i had the case with one Docset (Tiki) and luckily they had a header that i could pass to force their js to render (see here: https://github.com/godbout/tiki-dash-docset/blob/136b648c82fe0fcfcf45d9e3073b51be79eacb4a/app/Docsets/Tiki.php#L68). but that required working with them, going through the source, etc... i did it coz i'm working half a day a week at a client and need it, but it was a mega pain. another way could be to use a headless browser, but still, i stay away from those docs. coz sometimes you even need to change their js once it's downloaded. total shit. so yeah sorry, that Pine Script is definitely not gonna work out.

 

the Binance one, it took me less than ONE MINUTE to get it downloaded and packaged 🤣️ but straight, not one piece of fine tuning. i can do that later if that's kinda of what you want. have a look and let me know: https://www.dropbox.com/s/vtr58pbi69c9sey/binance.tgz?dl=0

[xilopaint]

2 hours ago, godbout said:

Binance one, it took me less than ONE MINUTE to get it downloaded and packaged 🤣️ but straight, not one piece of fine tuning. i can do that later if that's kinda of what you want. have a look and let me know: https://www.dropbox.com/s/vtr58pbi69c9sey/binance.tgz?dl=0

 

Yes, I would like! I'm working with that API at the moment. Also, I would appreciate if you could ELI5 (step by step)  how I can use the builder to generate docsets and fine tuning after that. Do I need to know PHP for it?

Edited January 28, 2021 by xilopaint

[godbout]

well, it's not complicated, but if you don't know the PHP environment, yeah forget it. from the package manager to Collections, it's gonna be a pain to explain, sorry.

 

i can do it quick, but without automated tests etc and no fine-tuning, so i'll not release it on Dash. will send you a link. you need only EN i guess, no CN? what about the 4 different pages on the top. you need only the USD-M Future stuff or all of them?

[xilopaint]

6 hours ago, godbout said:

can do it quick, but without automated tests etc and no fine-tuning, so i'll not release it on Dash. will send you a link. you need only EN i guess, no CN? what about the 4 different pages on the top. you need only the USD-M Future stuff or all of them?

 

I don't need CN and have no idea how much work it would get for all of them. USD-M Futures is what I'm working on at the moment so it would be fine.

 

Btw is the fine-tuning something I could make by myself after you create the docset? Is there a file that I could edit to improve the sections of the docs and make it better for the search on Dash?

Edited January 29, 2021 by xilopaint

[godbout]

8 hours ago, xilopaint said:

Btw is the fine-tuning something I could make by myself after you create the docset? Is there a file that I could edit to improve the sections of the docs and make it better for the search on Dash?

 well, you could edit the SQLite db that stores the entries, yes. and you could edit each HTML file to make them look like the way you want. all explained on the Dash site: https://kapeli.com/docsets#dashDocset

but that's exactly what the dash-docset-builder does for you.

 

basically with the dash-docset-builder you have only one file, where you do two things: 1) define a few constants that tells dash-docset-builder where to download the docs 2) tell the dash-docset-builder from what it should generate the Dash entries and how it should format the HTML.

 

by default the dash-docset-builder will check your constants and will check if the docs have a sitemap. if yes, it'll download the doc following the sitemap. if no, it'll download from the URL you gave as a constant. if you need to fine-tune the download yourself, you can override the `grab` method and use whatever way you're comfortable with to download the docs exactly the way you need. 

 

then the dash-docset-builder will go through all the HTML files twice, calling two methods from your one file. one method to generate the Dash entries, one to format the HTML files. why twice rather than once? because you're not going to generate the Docset many times so the extra time is not an issue, but separating the two processes is much better for maintaining the code.

 

the parts about generating the entries, and formatting the HTML, i provide a way to easily crawl the DOM, but you could use whatever you want.

 

all is in the README (but it seems, not clear enough :D): https://github.com/godbout/dash-docset-builder

Edited January 29, 2021 by godbout

[godbout]

here you go: https://github.com/godbout/binance-dash-docset

 

basic TOC and formatting, but usable. you can download the tgz. if you want to modify yourself, you can fork and play! good luck.

[xilopaint]

15 hours ago, godbout said:

here you go: https://github.com/godbout/binance-dash-docset

 

basic TOC and formatting, but usable. you can download the tgz. if you want to modify yourself, you can fork and play! good luck.

 

It looks great! Thanks a lot, man!

[godbout]

excellent.

 

time to go back to Alfred Kat now. so did you guys know that if you use the tag #xxx you can filter by pron?