-
python2-senaite.core.supermodel-1.2.3-1.lbn25.noarch
:height: 128- **SENAITE.CORE.SUPERMODEL**: *A beautiful content wrapper for
SENAITE that you will love* :target:
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.health-1.2.3.2-1.lbn25.noarch
.. figure:: :width: 500px— **SENAITE.HEALTH**: *SENAITE for healthcare labs,
the evolution of Bika Health* :target:
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.impress-1.2.3-1.lbn25.noarch
Publication of HTML/PDF Reports in SENAITE
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.jsonapi-1.2.2-1.lbn25.noarch
SENAITE JSON API The JSON API provides a RESTful JSON interface to SENAITE
CORE. SENAITE JSON API v1 Running this test from the buildout directory::
bin/test test_doctests -t JSONAPIv1 Test Setup -Needed Imports:: >>> import
transaction >>> from plone.app.testing import TEST_USER_ID >>> from
plone.app.testing import TEST_USER_PASSWORD >>> from senaite import
apiFunctional Helpers:: >>> def...
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.lims-1.3.3.2-1.lbn25.noarch
Responsive User Interface for SENAITE Core
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.storage-1.0.1.1-1.lbn25.noarch
:width: 500px *Sample storage add-on for SENAITE LIMS* :target:
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-senaite.sync-1.0.1-1.lbn25.noarch
:height: 128px*Data Synchronization tool for SENAITE LIMS* SENAITE.SYNC is a
SENAITE add-on to synchronize data amongst SENAITE instances or migrate from a
BIKA instance. Installation In order to get SENAITE.SYNC running properly both
senaite.api and senaite.jsonapi are required in the source and destination
instances. However, senaite.sync is only required in the destination instance
(where...
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
collective.progressbar-0.5-1.lbn25.noarch
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
collective.taskqueue-0.8.2-1.lbn25.noarch
collective.taskqueue enables asynchronous tasks in Plone add-ons by providing a small framework for asynchronously queueing requests to ZPublisher. With this approach, asynchronous tasks are just normal calls to normally registered browser views (or other traversable callables) and they are authenticated using PAS as are all the other requests.
In addition, it’s possible to configure views so that they are visible only for asynchronous requests. Also, collective.taskqueue ships with a special PAS-plugin, which authenticates each request as the user who queued it.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
jarn.jsi18n-1.1-1.lbn25.noarch
While internationalization in Zope/Plone is very mature there is no generally accepted way of doing i18n in JavaScript. Typically packages that contain Javascript code expose i18n by having hard-coded dictionaries or templates that dynamically create these dictionaries. While this is fine for small i18n catalogs, it easily gets tedious and is hard to update.
This package provides the essentials for leveraging the i18n infrastructure in Plone inside your JavaScript code:
Allows you to load arbitrary gettext catalogs from Plone.
Provides you with Message Factories very similar to the ones used in your python code.
Makes use of the local storage available in modern browsers to avoid reloading message catalogs.
Usage
Your package should depend on jarn.jsi18n and include it in its meta-data dependencies.
In order to instantiate a MessageFactory and use it you will need to load the i18n catalog. Typically, this will be done in a way similar to:
$(document).ready(function () {
jarn.i18n.loadCatalog('plone', 'el');
_ = jarn.i18n.MessageFactory('plone')
});
The second parameter in loadCatalog specifying the language is optional, when omitted the lang attribute in the html tag is used.
Now that we have a message factory we can use it to get translated strings:
> _('Contributor');
Συντελεστής
or with keyword parameters:
> _('Groups are: ${names}', {names: 'Jarnians'})
"Οι ομάδες είναι: Jarnians "
You can if you wish load multiple catalogs (or languages for the same catalog) and instantiate their respective factories, for instance:
> jarn.i18n.loadCatalog('plone', 'es');
> _es = jarn.i18n.MessageFactory('plone', 'es');
> _es('Contributor');
"Contribuyente"
Caching
If the client browser supports local storage it will be used to store the catalogs that you load. This makes it possible to avoid making an ajax request every time in order to load the full catalog. The stored catalog is by default valid for 24 hours. You can set the time-to-live by calling jarn.i18n.setTTL(millis) passing in milliseconds for how long the local storage cache should remain valid. Note that if local storage is supported, and the cache has not expired, the browser will NOT reload a catalog even if it changes in the filesystem.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
