Page 2 of 6

Re: [Request]: Official Library & Wrapper

Posted: 14 Sep 2018, 11:11
by nnnik
a is not an option.

Re: [Request]: Official Library & Wrapper

Posted: 14 Sep 2018, 13:05
by kczx3
Anyone know how you actually login or create an account for JoeDF's site? Can't really submit anything to it for testing.

Re: [Request]: Official Library & Wrapper

Posted: 14 Sep 2018, 16:25
by tank
OK so this burns my ass as well.
Some ground rules
Library scripts should be hosted on GitHub
Library script should have a support thread on the forum and a general instruction readme on GitHub.
Library scripts should have links to the support thread and GitHub in header comments.

Do at least this and i will set a cron job to use a page just like https://github.com/ahkscript/awesome-AutoHotkey except as a JSON page with GITHUB ZIP file download links with a server cron job to pull these packages to the server daily and set a download from the forum next to the download link above

Code: Select all

[
 {
   "Author": "Author",
   "Thread URL": "Thread URL",
   "GitHub Zip": " GitHub Zip"
 },
 {
   "Author": "Author",
   "Thread URL": "Thread URL",
   "GitHub Zip": " GitHub Zip"
 }
]
https://github.com/ahkscript/Library/bl ... brary.json

Re: [Request]: Official Library & Wrapper

Posted: 14 Sep 2018, 17:23
by kczx3
Just for clarification, is your first sentence just agreeing that we need a solution? Can’t tell if it’s that or you’re just tired of listening to people talk/complain about not having it lol

Re: [Request]: Official Library & Wrapper

Posted: 14 Sep 2018, 21:21
by tank
Agreeing

Re: [Request]: Official Library & Wrapper

Posted: 15 Sep 2018, 02:28
by tomoe_uehara
guest3456 wrote:that's exactly what the awesome-authotkey list is:
https://github.com/ahkscript/awesome-AutoHotkey
Yes, but I prefer actual code collection rather than just a 'bookmark'.

guest3456 wrote:unless of course youre expecting all the actual CODE of the libraries to all be in one place. but that is just absurd. each library should be in its own repo so that issues and bugs can be contained and maintained by the individual authors.
What will happen if the author is not active anymore, the Pull Requests won't get reviewed or even merged.
Yes, anyone else can still take over the development of that code by Forking from the original repo.

But if the author accidentally deleted the repository, we will have another missing resource(s) just like autohotkey(dot)net.
Nowadays in the cryptocurrency craze, everyone talks about 'decentralization is much better', but in this case what we actually need is 'centralization' indeed.

elmo wrote:@tomoe_uehara seems to be talking about (b) and, in the examples from other major platforms cited by @iseahound, they return code.
Yes elmo is correct, what I'm talking about is the actual code itself, not just a link to webpage or somewhere else.

tank wrote:Do at least this and i will set a cron job ... to pull these packages to the server daily
Unfortunately I think blindly uploading codes to the repository will make it bloated and the filesize will be very large to download, thus it will defeat the purpose of making a compact library itself.
We need a categorization in form of Git Branch, so anyone don't have to download whole repository just to parse JSON for example.
Git can utilize something like "selective download" by using Git Checkout.

Imagine a git repo that has multiple branches like https://crates.io/categories, those categories will be the branches.
Inside of the branch (for example 'Parser' branch), there will be another folder: JSON, YAML, etc.
Inside that JSON folder, there will be actual code itself, along with working example inside another subfolder.

Code: Select all

AHK LIB root folder/
|-- Algorithms/
|   |-- algo_code.ahk
|   +-- Example/
|       |-- algo_example.ahk
|       |-- another.file
|       +-- image.jpg
|
|-- Parser/
|   |-- JSON/
|   |   |-- json_parser.ahk
|   |   +-- Example/
|   |       +-- json_example.ahk
|   +-- YAML/
|       |-- yaml_parser.ahk
|       +-- Example/
|           +-- yaml_example.ahk
|
+-- ETC/
We don't need a sophisticated system like yum, dpkg, apt, pacman, etc. What we need is a system that works, even a simple github repository is fine too.
To make it work, we need a collaboration from the Autohotkey Community users :xmas:
More feedback is welcomed :)

Re: [Request]: Official Library & Wrapper

Posted: 15 Sep 2018, 02:48
by nnnik
If you really just want something that works for now then multiple repositories is still better - as long as they are inside a single Organization.

Re: [Request]: Official Library & Wrapper

Posted: 16 Sep 2018, 23:44
by hoppfrosch
Just want to say: I once reserved the Autohotkey V2 organization on github - and I will hand it over to anybody, who is willing to take responsibility for a github based AHK2 library server. ;)

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 10:45
by tank
As i see it Tomoe and I want 2 different solutions. Her suggestion i believe looks exactly like Awesome-AutoHotkey. I want to provide a centralized download no matter which repository it is in. And you seem to be suggesting a single repo for just ahkv2 scripts which might be a good idea if we can get adoption

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 12:43
by tomoe_uehara
Let's hear your idea, Tank.
What kind of 'centralized download' do you have in mind?
Would it has some kind of code reviewing before it got merged/uploaded, or something else perhaps?

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 13:13
by tank
Right, As i said this repo would be nothing more than a JSON file referring to approved and documented libraries. a server application would download and pack each approved library to a zip file. I would add a download button for it next to the ahk download. In this way we get a single download for all approved library files and a single JSON file to maintain for it

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 13:40
by kczx3
I don't think I'd want to be forced to download everything each time I want to get something new or update an existing library dependency.

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 13:41
by nnnik
true

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 14:08
by Helgef
If it is official, it should come with the installer, and be optional to install to the lib folder. Ahk_h comes with libs if I'm not mistaken.

Cheers.

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 16:49
by tank
@lexikos i think has expressed not wanting to package a lib with the installer before. Official to me means as a community we agree to have a hosted offering of something

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 20:27
by kczx3
I recall the same

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 21:00
by elmo
kczx3 wrote:I don't think I'd want to be forced to download everything each time I want to get something new or update an existing library dependency.
Agreed.

Re: [Request]: Official Library & Wrapper

Posted: 17 Sep 2018, 22:07
by lexikos
If the download or update of the "standard Lib" can be easily automated and "the community" wants it included with the installer, that is fine with me. I just want no part in maintaining it.

Re: [Request]: Official Library & Wrapper

Posted: 18 Sep 2018, 01:45
by nnnik
lexikos wrote:If the download or update of the "standard Lib" can be easily automated and "the community" wants it included with the installer, that is fine with me. I just want no part in maintaining it.
Thats great to hear - I always thought the same as the others. Seems we misunderstood you.
That means that we can create an entire library manager similar to pip or other related ones.

Re: [Request]: Official Library & Wrapper

Posted: 21 Sep 2018, 06:44
by tomoe_uehara
Before jumping into a conclusion, let's do some brainstorm first about how it will looks like.
  • Where the code will be hosted? (Git based / Cloud Storage / other)
  • Do we need a redundant mirror / backup storage?
  • How can people contribute to the lib? (Add new code / modify / bugfix / delete obsolete code)
  • Who will do the code review?
  • Do we need some sort of Version Control? (ie. be able to download old codes)
  • Which AHK version/flavour will we use for the lib?
  • How will we name each file on the lib, will we use standardized file naming convention?
  • How will we present the lib to the user? (Git client / AHK GUI / Web based / other)
  • How do we categorize the lib? (By name / function / author / other)
  • How about file searching capability, will it slows down if lots of libs has been added in the future?
  • Do we need to include example code(s) on each libs?
  • What about license, lots of codes were written by users whom don't exist anymore, can we add their codes into the lib?
Any ideas are welcome ;)