jasononeil / haxelib Goto Github PK
View Code? Open in Web Editor NEWThis project forked from haxefoundation/haxelib
Provisional project for the Haxe 3 related haxelib changes.
This project forked from haxefoundation/haxelib
Provisional project for the Haxe 3 related haxelib changes.
Regarding downloads : I think that we should not count the total number of downloads which will in general favor older libraries versus "trending ones".
A suggestion to improve that: every month, run a cron that count the number of downloads this month, then update popularity with popularity = (max(downloads-this-month,popularity) + downloads-this-month) * 0.5
.
And double check that descriptions, names etc are all safe.
http://lib.haxe.org/p/tink_xml/
How much time does it take before the stats are updated?
The header does not use the same size / font / behavior / etc than on haxe.org (and the logo is the old one which has rendering issues :) )
Do we:
And then....
We just had a google bot start crawling "preview.lib.haxe.org". (Still not sure where it scraped the URL from, but oh well).
It hit the File Browser, which currently displays a source file by opening the haxelib zip, unpacking the file, rendering it, and sending it to the client. Needless to say, with the tens (hundreds?) of thousands of files, this was causing significant strain on the server.
I've turned the preview site off for now until I fix this, either by having a faster (cached?) implementation, or by using robots.txt to block google from the file browser section.
Create new issues later:
๐ the new api.haxe is already live, would be great if we can put lib.haxe also live with this 3.2 release.
Is there anything I can do to help?
This seems to be a glitch somewhere inbetween SPOD relations, our SiteDB model classes, and erazor's templating. The templates can't access the properties by a getter.
I either need to diagnose the glitch, or use a View-Model typedef similar to ProjectInfos, that has all the information relevant to the view.
The left menu on the documentation section order does not match the drop down menu
http://preview.lib.haxe.org/documentation/using-haxelib
I'm not sure we should have a "About haxelib", we don't have much more to say here than what's already on the haxelib home page. Not sure about "Tip and tricks" also (all commands should be properly documented already).
I would put these in that order:
Getting started (would mention install, upgrade, how to open commandline on Windows :) etc)
Commands (all commands documented, nicely formated)
FAQ (where are my libs stored, contributing, reporting issues, etc)
API
As for contributing, we could have a link to Github project with an github icon in the header
With the READMEs and file browsing, we currently have extract each file from the zip as required. It might cause too much load on the server if we have a sudden rush of people. Perhaps some caching is needed, at least for the READMEs?
Also for the haxelib.json file, which I think I want to start using to grab information about dependencies, extra params etc also.
This will have an effect across much of the website, and API:
I think that the haxelib command list documentation could be made much more readable
Currently we have http://preview.lib.haxe.org/documentation/using-haxelib
We could present each "command" with a description, a bit longer than it is right now and an usage example. By using a bold+color for the command it will make it more easy to find the one that you're looking for (similar to "CLI command" section on https://docs.npmjs.com/)
I saw on the forums questions about how this awesome readme embedding thing works. Maybe there should be a section created to explain this feature.
See http://preview.lib.haxe.org/p/cleversort/nosuchversion
It would be nice if the 404 page also had the version list, or at least a link to the current version.
I want to use Dox to create API documentation. A few things to consider:
It would be great to show "depends on" and "depended on by" information on the Project page.
"Depends on" we could extract from the haxelib.json.
"Depended on by" would have to be loaded from a database, with all of the dependencies added. So a bit more work, but would be useful information.
Another question: for "depended on by", do you link the dependencies with specific versions? It gets messy if you are caching version information in the DB, but it is not depending on an exact version, and then the dependency gets an update.
Maybe we could add the favicon corresponding to the website URL in front of each library ? that would add a bit of graphics/colors to an otherwise black&white pages. We could also allow people to put their own icon.png in the zip but that's maybe a bit more difficult to implement ?
https://www.npmjs.com allows big icons for instance (if I look a the featured packages)
It just shows the directory listing again:
http://preview.lib.haxe.org/p/flixel-tools/1.0.4/files/run.n
This issue is to collect a TODO list of things to fix up when viewing the site on mobile.
Do not list downloads count in http://preview.lib.haxe.org/u/ (still sort by most downloaded) this will make the page more readable
btn-primary
whiteCan we search for relative links in MD and redirect them?
See:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.