I generated the JavaScript libraries (both uncompressed and compressed versions) for 18 services. They're right now checked into the kbapi_common git repo (that's also temporarily where I maintain the script that builds the libraries from the virtual machine). The directory is 'javascript/lib/kbase{,.min}.js'. There are, however, a few caveats, recorded on the KBase Services spreadsheet (Client Libraries sheet): * 5 services did not yet get deployed into production (aux_store, cdd_service, invocation, microbes_model_builder, probabilistic_annotation). Are those expected to be deployed or are they deployed and not marked as such? * 4 deployed services did not create JavaScript API libraries (assembly, auth, jnomics, and matR). None of these actually have type docs. I guess these can be ignored, but I'm not sure. Please advise. * Some services write their JS libraries into non-standard locations (most write a 'lib/[% MODULE_NAME %]/Client.js'). Not a big deal but should standardize in the future. Barring those caveats, the libraries are good to go. 232K uncompressed, 98K compressed. :) As for Python, I still want to hear from the Python devs about the best way to package the client libraries. Shiran On Feb 21, 2013, at 11:32 PM, Thomas Brettin <[email protected]> wrote:
hey shiran,
the preamble looks good, thanks.
t
On Feb 21, 2013, at 10:22 PM, Shiran Pasternak <[email protected]> wrote:
By the way, I created yet another sheet in the KBase Services spreadsheet. It actually uses formulas to remove human (Shiran) error by tapping into both the Master sheet (for modules that are services and not internal) and the Feb 4 build for their pass status. The list I included in my last email to kbase-devel is straight out of there. Anything I missed (or should not include)?
Shiran
On Feb 21, 2013, at 9:46 PM, Shiran Pasternak <[email protected]> wrote:
Yes, I have a process that does that compression/uglification/minification (I use UglifyJS).
I think that folks that want to use their own custom one can build it themselves using their desired set of services. Usually, JS libraries are distributed in both forms, so that the unminified version can be used for debugging. We'd call it kbase.js and kbase.min.js. What do you think?
For both, I include a preamble at the top that looks like this:
/** * The KBase API * http://kbase.us * * API documentation: http://kbase.us/developer-zone/api-documentation/ * @license Copyright (c) 2013, The DOE Systems Biology Knowledgebase Project */
Shiran
On Feb 21, 2013, at 9:36 PM, Thomas Brettin <[email protected]> wrote:
Not sure. I thought I saw some talk that looked like concatenating all kbase js libs into a single one, then folks saying that they custom select what they use.
I think in any case, you could run the js libs through one of those js compressors, I forget what they are called, but you know, they take out whitespace, make the libs significantly smaller.
Really though, I;m worse than a js000nb. What makes sense to you?
We can always change our mind in the future, and make old libs available in the archives area of downloads.
t
On Feb 21, 2013, at 8:31 PM, Shiran Pasternak <[email protected]> wrote:
I handle the JS client APIs, but can also distribute the python libraries as a package, which are being deployed alongside the JavaScript libraries. But isn't it misleading to only release the CDMI API as a standalone?
Thoughts? Shiran
On Feb 21, 2013, at 8:35 PM, Thomas Brettin <[email protected]> wrote:
shiran maybe?
On Feb 21, 2013, at 7:34 PM, Nomi Harris <[email protected]> wrote:
Is someone planning to update these today or tomorrow? <Screen Shot 2013-02-21 at 5.33.08 PM.png>
Thanks, Nomi
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
Thomas Brettin 865-603-7760 (cell) [email protected]
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
Thomas Brettin 865-603-7760 (cell) [email protected]
Thomas Brettin 865-603-7760 (cell) [email protected]