xilopaint

10 hours ago, deanishe said:

 

https://github.com/deanishe/alfred-reddit/releases/tag/v1.7

 

Not working for me. Are you sure you committed the changes?

5 minutes ago, deanishe said:

 

I haven't! It's all gone a bit tits-up as I've massively revised the AwGo library, so no rebuild without a non-trivial rewrite.

Ok, so could you please update your Reddit workflow fixing the autocomplete issue? ?

?

On 9/3/2018 at 7:11 PM, deanishe said:

Perhaps I can make a release using the binary I'm currently using. That one seems to work…

Please, don't forget me! ?

Update (v2.15)

Added Keyword to change the value of the "suffix" environment variable.

5 minutes ago, deanishe said:

I've just had a look, and it's more or less uncompilable at the moment. The AwGo API has changed a lot since then, so it'll need a bit of a rewrite  

 

Perhaps I can make a release using the binary I'm currently using. That one seems to work…

It's ok for me. If you prefer don't making a new release you can share the binary on this thread as well.

On 8/30/2018 at 6:57 PM, deanishe said:

If you can build the workflow from the develop branch, it should work as expected.

 

Beyond that, I'll try to release a new RC at the weekend. There are a few fixes/enhancements in develop and Niki has started posting duplicates of his own issues on the Searchio! repo.

Unfortunately I can't do it without any Go knowledge. I tried to build the search.go file with go build search.go and didn't succeed because of some missing packages.I thought about installing the packages on my $GOPATH but I was afraid to screw up everything so I gave up.

Hope the new RC will not take long.

hahahaha thank you for bringing those issues to my attention. deanishe vs. nikvi discussions are on top of my geek humor ranking.

On 12/15/2017 at 3:41 PM, xilopaint said:

 

I'm having issues with Google engines and Amazon. Wikipedia and DuckDuckGo are ok.

Any news here?

I had to create a new Urban Dictionary workflow as my previous one was broken.

It's available on GitHub.

Never mind, I built myself a workflow.

It doesn't work for me anymore. Could anyone with knowledge in PHP fix this?

Update (v2.14)

Improved syntax for Slice file action to allow the user to omit the second value of a page range in order to indicate that it ends on the last page of the PDF file (eg. "8-").

On 8/6/2018 at 4:30 PM, Jasondm007 said:

@xilopaint I love this workflow! Thanks a ton for sharing it.

 

Quick Question: Is there any way to quickly view a selected PDF's info (e.g., total page numbers - or other info)? 

No, currently there's no such feature in the workflow.

On 8/6/2018 at 4:30 PM, Jasondm007 said:

For example, I love using your workflow to quickly move the first page of a PDF to the end of the document. While the Slice file action (single file) is great for this, its syntax requires knowing the total number of pages in the PDF (e.g., for a 15 page PDF, it would be 15, 1-14). Is there any way to get the page count through the workflow (kMDItemNumberOfPages - I think ...)?

The input in your example moves the last page to the beginning, not the first page to the end.

On 8/6/2018 at 4:30 PM, Jasondm007 said:

If not - and, of course, assuming that you're looking for suggestions for future updates - I was thinking that it might be cool to display the relevant file information in the file action's title. So, for example, in the slice file action for a single file, it might do something like this:

• Current Title: Enter page numbers and/or page ranges (e.g. 2, 5-8).
• New Title: Enter page numbers and/or page ranges (e.g. 2, 5-8) of X pages.

And, for the resolution or size file actions of a single file, it might also provide their respective details.

The file actions get user input by keywords objects. Such objects can't be dynamically populated. Your suggestion is a work for script filters, but I'm not yet convinced that the additional information would worth it. The page count information in particular can be handled by the syntax in a more straightforward manner.

On 8/6/2018 at 4:30 PM, Jasondm007 said:

Alternatively, adding generic reference points to the end of a document might also do the trick (e.g., last, blank for remaining pages, etc.). So, users could do the same thing without knowing the actual page count (e.g., last, 2-).

Blank as the end of the document is a well known syntax for page ranges. It will be implemented soon.

Hi @Jasondm007! Thank you for the feedback. I'm a bit busy for the next few days but I'll look into your suggestions once I have some free time.

On 5/26/2018 at 7:23 PM, RyuX51 said:

Is there an alternative?

According a comment by @Vero on Reddit there are plans for an official alternative on the road map.

Update (v1.5.1):

Fixed typo in Mark as Completed action.

Hey @tamvodopad, your issue should be fixed on the latest release.

Update (v1.5):

• Added ability to show to-dos in projects using the ⇧ modifier key.
• Fixed multiple issues for non-English locale.

On 5/2/2018 at 7:49 AM, tamvodopad said:

This action not work with Russian language ?:

 

 

Info from debug:

 

Starting debug for 'Things'

[2018-05-02 13:38:10][ERROR: action.script] 0:82: execution error: Получена ошибка от «Things3»: Не удается получить list "–Т—Е–Њ–і—П—Й–Є–µ" of application "Things3". (-1728)
[2018-05-02 13:38:10][ERROR: input.scriptfilter] Code 1: 0:61: execution error: Получена ошибка от «Things3»: Не удается получить list "–Т—Е–Њ–і—П—Й–Є–µ" of application "Things3". (-1728)
[2018-05-02 13:40:58][ERROR: input.scriptfilter] Code 1: 0:61: execution error: Получена ошибка от «Things3»: Не удается получить list "–°–µ–≥–Њ–і–љ—П" of application "Things3". (-1728)

I think problem with russian Inbox translating and russian project names.

Has it worked for you before or have you just tried the workflow for the first time?

38 minutes ago, deanishe said:

 

You mean what is the best practice?

Yes, sure. Sorry for the typo.

On 4/13/2018 at 8:37 PM, deanishe said:

 

I'm not sure it's actually critical (from my understanding, OAuth2 threw out the OAuth1 requirement that access tokens be bound to the client ID, which if true, makes the client ID a bit of a joke), but certainly Google does not like client IDs and secrets turning up in public repos.

So what is the best practice?

I have poor knowledge on OAuth but found this in an article :

Quote

If the developer is creating a “public” app (a mobile or single-page app), then you should not issue a client_secret to the app at all. This is the only way to ensure the developer won’t accidentally include it in their application.

Quote

It is critical that developers never include their client_secret in public (mobile or browser-based) apps. To help developers avoid accidentally doing this, it’s best to make the client secret visually different from the ID. This way when developers copy and paste the ID and secret, it is easy to recognize which is which. Usually using a longer string for the secret is a good way to indicate this, or prefixing the secret with “secret” or “private”.

Nothing relevant there.

The code was catching the true error, so I made some changes to find the issue:

Quote

HTTPError: HTTP Error 301: Moved Permanently

This led me to search for the API information on 17Track website:

Quote

Does 17TRACK have API?

 

Unfortunately, we currently don't offer our API for public use.

If you are in need of it, please contact our staff directly via email to discuss potential cooperation.

(Note: mark the email title as "API Inquiry")

Thank you!

Nothing we can do. The workflow is dead.

Post here the output of Alfred Debugger.