Welcome | Get started | Dive into Lino | Contribute | Topics | Reference | More
Plugins¶
This section assumes that you have read the plugin reference for end user. See also About plugins.
about: Information about a siteaddresses: Multiple addresses per partnerana: Analytical accountingappypod: Generate printable documents from odt templatesb2c: BankToCustomer SEPAbeid: Belgian ID card holdersbevat: Belgian VAT declarationsbevats: Simplified Belgian VAT declarationsblogs: Blogging functionalityc2b: Export SEPA CustomerToBank statementscal: Calendar functionalitycalview: Calendar viewchanges: Keep track of changes in the databasecheckdata: High-level integrity testsclients: Manage clients and client contactscoachings: Managing coachingscomments: The comments frameworkcontacts: Managing contactscountries: Countries and citiescourses: Managing coursescv: Managing career-related data of clientsdashboard: customizable dashboarddeploy: Deployment managementeevat: Estonian VAT declarationsevents: Publishing an event calendarexcerpts: Database excerptsexport_excel: Exporting to Excelfiles: Manage external filesfinan: Financial vouchersgoogle: Synchronization with Googlegroups: user groupsgfks: Utilites for Generic Foreign Keyshealthcare: Manage healthcare providershelp: Make local help pageshouseholds: Handling households and their membershumanlinks: managing family relationshipsinvoicing: Generating invoicesjinja: Jinja printingledger: General accountinglino: Lino core functionalitylinod: The Lino daemonlists: Partner listsmemo: The memo parsernicknames: Nicknamesnotes: Notesnotify: Notification frameworkoffice: Adding an "Office" menuorders: Managing orderspages:phones: Multiple phone numbers per partner (Contact details)polls: managing questionnaires and responsesprinting: Basic printing functionalityproducts: defining the things you sell and buyproperties: configurable propertiespublisher: render database content as styled htmlsearch: Add search functionalitysummaries: Summary tablessystem: Site-wide system settingsssin: Belgian national identification numberssepa: Communicating with the bank using SEPAsheets: Balance sheet and Income statementshopping: A shopping cartsmtpd: Add an SMTP daemonsources: manage bibliographic sourcesstorage: Storage, provisions and fillerssubscriptions: Subscriptionstickets(Ticket management)tim2lino: importing legacy data from TIMtinymce: Add the TinyMCE editortopics: topics and tagstrading: Product invoicestrends: Managing trendsuploads: Managing uploaded filesusers: user managementuserstats: User statisticsvat: Adding VAT (Value-added tax) functionalityvotes: User opinionswarehouse: managing the goods you ownweasyprint: Printing documents using WeasyPrintworking: Work time trackingxl: General utilities for XL plugins
"Standard" versus "Extensions" library¶
The plugins of the Lino framework are spread over several Python packages. Some
of them are in lino.modlib and we call them core plugins, others are in lino_xl and we call them the plugins
of the Extension Library. Furthermore, individual applications can
have their own plugin library.
The Lino Extensions Library or XL is a plugin library considered part of the Lino framework and used by many Lino applications.
It is separate from the Standard Plugin Library because despite our efforts of making it very reusable, it is still just one possible view of the world and you might prefer your own view.
It is a big library, so beginners might not want to dive into all these concepts right now.
Where is the borderline between a standard plugin and an "XL" plugin? The theoretical answer is that the Standard Plugin Library contains "basic features" that remain useful also for people who don't want the XL.
The borderline is neither very clear nor definitive. For example we have two
plugins printing and excerpts. The former in the core (lino.modlib) while the
latter is in lino_xl.lib. Yes, it remains arbitrary choice.
TODO: move languages and office to the XL? Move excerpts to the
core? And what about vocbook?