-
nodejs-iso8601-1.1.1-5.lbn25.noarch
Node.js module to parse and print ISO8601 dates
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
nodejs-isobject-3.0.1-1.lbn25.noarch
Returns true if the value is an object and not an array or null.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
nodejs-isstream-0.1.2-3.lbn25.noarch
Determine if an object is a Stream.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
nodejs-istanbul-0.4.5-2.lbn25.noarch
Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
nodejs-items-2.1.0-1.lbn25.noarch
Bare minimum async methods
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
nodejs-jade-1.11.0-4.lbn25.noarch
Jade is a high performance template engine heavily influenced by Haml and implemented with
JavaScript for node and browsers.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
Products.DataGridField-1.8.4-1.lbn13.noarch
A table input component for Plone. Uses Javascript to make entering tabular data more user friendly process - there are no round trip HTTP requests to the server when inserting or deleting rows.
Features
o Any number of columns set by a developer
o Any number of rows filled by a user
o Insert and deleting rows without submitting a form
o Many different column types
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
Products.DateRecurringIndex-2.1-1.lbn13.noarch
A Zope 2 catalog index with support for indexing of recurring events, following the icalendar standard. It is a drop-in replacement for the Zope2 DateIndex and will produce the same results for non-recurring dates.
The DateRecurringIndex accepts following parameters:
id
Required. The name of the field or object attribute to be indexed.
recurdef
Required. The name of the object attribute, which returns the icalendar rrule (recurrence rule) string.
until
Optional. The name of the objects attribute, which returns the date, until the recurrence should happen. The recurrence definition can also contain an UNTIL component. If both are defined, the recurrence calculation stops whenever the first until-date is met. If not given at all, there is a MAXCOUNT ceiling constant, defined in plone.event.recurrence, which defines the maximum number of occurences.
Datetime.DateTime vs. datetime.datetime
Inside Zope2 everybody uses DateTime.DateTime or iow the Zope-DateTime. At time of writing Zope-DateTime (around 1998) there was no good date/time implementation in python. But these days we have a better implementation. Even if the pythons datetime implementation has its problems, together with pytz for timezone handling it is very mature.
So, why is it covered here? Just because dst-handling over recurring events works only if the start and until values are non-naive python datetimes. Just keep it in mind when using this index: If you use recurring dates and you want dst-adjust make sure your implementation returns a python datetime. And also keep in mind: If youre i.e. in Austria with CET timezone, add a recurring date: it will look fine to you, every day at 11:00am, doesnt matter if DST or not, your event happens. If you go international and your event is shown in a different timezone - or in the same in a country without DST at all - it might differ and is not always at the the time.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
Products.DeadlockDebugger-1.0-2.lbn13.noarch
This product adds a hook so that a deadlocked Zope process can be debugged, by
dumping a traceback of all running python processes. The dump is sent to the
event log (at the DEBUG level) and returned to the browser (even though the
Zope is deadlocked and doesn't answer any other requests!).
DeadlockDebugger can of course also be used to debug Zope in non-deadlock
situations, when a Zope process is taking a long time and you wish to know what
code is being executed.
The standard way to call it is to go to the URL::
http://yourzopesite:8080/manage_debug_threads?sesame
This will return a dump, and also send this dump to the event log.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
Products.EasyNewsletter-2.6.12-1.lbn13.noarch
EasyNewsletter is a simple but powerful newsletter/mailing product for Plone.
Features
Support Text and HTML Newsletter (including images)
Support manual written Newsletters/Mailings
Plonish (can use Plone's Collections to collect content)
Variable templates to generate newsletter content
Subscribing / Unsubscribing and can use Plone Members/Groups as receivers (works also with Membrane)
support for external subscriber sources (configured through a Zope utility)
support for external delivery services (other than Plone MailHost)
TTW customizeable output Template to generate nice HTML Newsletter
Support personalized mails
Support for sending daily issues automatically, based on collections (by cron or clock-server)
mass import/export subscribers via csv
support external filtering/manipulation (filter out or add more subscribers) plugins
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
