Jump to content
adrian

Batch Child Editor

Recommended Posts

I'll try to check this tomorrow. I'm currently pretty swamped between my holiday and another vacation coming up.

  • Like 2

Share this post


Link to post
Share on other sites
I'm currently pretty swamped between my holiday and another vacation coming up. 

My heart bleeds for you :)

Whenever you get the chance to look it will be greatly appreciated - turns out to be pretty painful to replicate all the checks in all scenarios - hopefully I have everything covered.

Share this post


Link to post
Share on other sites

Just added some new features and a couple of bug fixes to the dev branch.

  1. Fixes for export mode with certain complex field types
     
  2. Added support for AJAX loading of BCE - especially useful if you are using the "New Tab" position option - requires PW 2.6.11+. This will make Page -> Edit load much quicker when you have lots of child pages.
     
  3. New Lister mode - this allows you to view (and configure the default columns/filters) all children under the current page. If you have ListerPro installed you can also use the Actions on the children. This also supports inline editing which makes for a very quick and easy way to edit the key fields on each child page.

Please let me know how the new AJAX load and Lister mode features work for you - I think I need some wider testing before pushing this to the master branch.

You can define the Lister config settings sitewide, and then provide overrides for each parent page that has been enabled under "Configurable Pages"

post-985-0-61627100-1439912334_thumb.png

This screenshot shows the new Lister mode configured to show a predefined set of columns - a great way to preview the page content of child pages.

post-985-0-89453200-1439904134_thumb.png

This shows the Lister Inline Edit mode - making for very quick editing of key fields in child pages.

post-985-0-03194800-1439919612_thumb.png

  • Like 6

Share this post


Link to post
Share on other sites

seems i've to translate some strings again....you're really getting this as alternative editing interface for childpages instead of the normal pagetree....;)

Thank you very much for this nice piece of work - will testing soon.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @mr-fan!

I just put together another screenshot showing how you can use BCE as the equivalent of an inline PageTable field interface. 

Obviously these are just child pages and are not callable from a field, but it provides an excellent editing interface in a dedicated tab along with all the filtering options of lister. It also doesn't have any of the problems with a PageTable field regarding editing the content page directly and not having new pages automatically added, etc. The inline ajax editing is also a great bonus over the popup modal editing. 

Of course, this inline editing requires ListerPro, but I think it is worth it :)

post-985-0-14812200-1439922118_thumb.png

  • Like 3

Share this post


Link to post
Share on other sites

Sorry for the stream of updates, but you can now embed BCE into the flow of fields within the Content Tab. This makes for even easier access to inline ajax editing of child pages.

It probably only makes sense for Lister, Edit, and Export modes.

Just pushed this option to the dev branch.

post-985-0-90776500-1439936696_thumb.png

  • Like 4

Share this post


Link to post
Share on other sites

You are a real bad guy....with all this "stream updates" ;)

just one tick while testing...

https://github.com/adrianbj/BatchChildEditor/pull/4

(changes the labels on the field selection in the right language)

The issue with Lister view if there was images is a problem of the actuale PW dev i think?

For BCE i tested today very much and the next days german translation follows....while testing i've to say just one thing but i think i'm repeating me:

THIS IS A SUPER MEGA GREAT ADDON.... ^-^

some little testing things:

- Setting (Editor,Position, Load...) ->Position = Inline Fieldset, Insert After = title, load the fieldset open = true, ....Open Method is hidden if loading the fieldset collapsed but "Normal" or "Ajax" loading should be selectable while this setting enables the inline editing, too not only the loading?

- A "modal option" for lister mode should be a little additional option for the lister edit links, to edit childpages in modal mode...

This is really great if your wanna a easy and nice overview page on such root pages for the same kind of content like team, tags and articles or similar....i'll embed it in my current projects since it is much more flexible that a pagetable for this task!

And a additional call for others to buy Lister Pro...;)

Best regards mr-fan

  • Like 1

Share this post


Link to post
Share on other sites

@mr-fan - thanks for the great feedback, testing, and the PR for language labels. 

  1. Yep - I think the issue with the Lister view not working when there is an images field selected is a problem with PW dev / Lister
  2. I don't quite understand the Normal/Ajax load problem (I am sure I am missing something obvious so will look better later to see if I can figure out why that needs to be an available option when Open is checked.
  3. Yep - I was planning on making the Lister EDIT mode configurable to include the modal option, but there is something stopping it from working properly in modal mode - I think it's because Lister is in an iframe, but I will look again and see if I can get it to work - it would be much nicer for times when inline/ajax editing is not enough (or the user doesn't have ListerPro).

I am also thinking of making it possible to choose a different parent (or maybe even use a full PW selector) so you can make BCE grab children from somewhere else in the page tree - I think this would only work for Lister, Edit, and Export modes, but could be very cool - kinda like the ability of PageTable to specify a different parent, but even more powerful. I'll hopefully play with this in the next few days and post a new dev version then.

  • Like 1

Share this post


Link to post
Share on other sites

Ok, just pushed a new version to dev that adds support for choosing an alternate Parent. This allows you to bring in child pages from any other parent in the page tree (like I mentioned in my previous post above). It's a new option under the Content / Deletion / Protection tab - obviously only available for page specific config settings.

Also added an option to determine whether Filters/Columns/Actions are available in Lister mode - checkbox under the Lister mode settings tab.

This version might require a little extra testing regarding allowed templates for editing/adding pages.

Please let me know how it goes.

  • Like 3

Share this post


Link to post
Share on other sites

Somehow the "Own Tab" setting doesn't seem to work on a 2.6.14 installation, leaving the functionality inside of "Children" does work.

Share this post


Link to post
Share on other sites

Somehow the "Own Tab" setting doesn't seem to work on a 2.6.14 installation, leaving the functionality inside of "Children" does work.

Not sure exactly what changed just yet, but it works for me so long as the Tab / fieldset name is only one word. Not sure if it's a bug that Ryan introduced or what, but if you use a multi word name, I run it through the PageName sanitizer and now it breaks the tab. Will investigate further later, but for now, one word names should work fine. 

Share this post


Link to post
Share on other sites

Sorry for the delay - while I was out for dinner I realized exactly what the issue was - I needed the fieldName sanitizer, not pageName. Not sure why it worked before - I guess 2.6.14 enforced no dashes in fieldset names?

Anyway, it is fixed now on the dev branch. if you don't want to switch to the dev branch at the moment, here are the changes you need:
https://github.com/adrianbj/BatchChildEditor/commit/f1721794a77c1b6dfebcae692485f41ee0df75ea#diff-b79b82291600910335909ae234e40fdb

Share this post


Link to post
Share on other sites

I'm not sure if that's a Lister issue, but by default the pages should really be sorted by "sort" and not "-modified", which makes less sense in the module's context.

Edit: It would also be nice if there would be a way to exclude some fields (e.g. mode) from the new save-reminder functionality.

Share this post


Link to post
Share on other sites

I'm just started to use BCE id a project and I like it, thanks!

One question: do you plan to add a toggle checkboxes to columns, eg. mark all / unmark all?

Sometimes I need to delete tens of pages at a time and this would speed up the process a lot.

(for example 72 pages this time, this happens when my form processor goes wrong :))

Share this post


Link to post
Share on other sites

I'm just started to use BCE id a project and I like it, thanks!

One question: do you plan to add a toggle checkboxes to columns, eg. mark all / unmark all?

Sometimes I need to delete tens of pages at a time and this would speed up the process a lot.

(for example 72 pages this time, this happens when my form processor goes wrong :))

The easiest way to batch delete a huge number of pages is to enable the "Replace" mode and make sure you have the "Text/Paste" option checked under: Data entry / CSV import options > Page data options

Then simply empty the TextArea list of all the child pages and click save!

Please let me know if anything doesn't make sense - the config options in this module can take a while to get the hang of  :)

Share this post


Link to post
Share on other sites

I'm not sure if that's a Lister issue, but by default the pages should really be sorted by "sort" and not "-modified", which makes less sense in the module's context.

Edit: It would also be nice if there would be a way to exclude some fields (e.g. mode) from the new save-reminder functionality.

Sorry for the late response on this one - it is definitely on my list of things to do - unfortunately it doesn't seem to be as simple as it sounds - I am getting conflicts with the main Pages->Find Lister, but when I find some time, I'll definitely see if it can be fixed.

Share this post


Link to post
Share on other sites

Please let me know if anything doesn't make sense - the config options in this module can take a while to get the hang of  :)

Sure it helps, thanks! The module seemed surprisingly simple at first but now I can see the whole beast :)

The thing I was trying to recommend is a checkbox that would toggle all checkboxes in the column, like this:

post-3156-0-44542700-1441908361_thumb.pn

This would require only some lines of JavaScript.

Share this post


Link to post
Share on other sites

Thanks - I do see your point regarding the check all - it would be especially useful for the hidden/unpublished options and I am sure something similar could be done for the delete option in edit view also.

Would you mind adding an Issue on Github for me so I don't forget to do this at some point, or better yet, a PR ;)

Share this post


Link to post
Share on other sites

Ok, will try to squeeze out a PR :)

  • Like 1

Share this post


Link to post
Share on other sites

PR done! Feel free to review.

It doesn't check whether the items are checked or not, just toggles items on/off.

post-3156-0-95916800-1442151817_thumb.gi

  • Like 4

Share this post


Link to post
Share on other sites

I don't think the shift-click is related to this module. That was the first thing I tried before adding the header checkboxes.

The rearrange feature doesn't work here, and clicking on the the headers doesn't sort the columns - I don't know if that is normal.

Share this post


Link to post
Share on other sites

@tpr - thanks very much for the PR - the functionality looks awesome and will be a great timesaver - I'll try to review in the next couple of days. I haven't ever seen the header "order by" icons in BCE - I certainly didn't add them intentionally - have you added these?

@BernhardB - thanks for all the likes :) I just looked at your video and the only issue I can reproduce is the shift-click selecting checkbboxes both hidden and unpublished columns - not sure if I can fix this or not since it is core functionality, but I will take a look. I am not having any issues using the sort/move handles and the Add New is also working fine. I am using the dev version of BCE here, but I know it worked for me with stable before. I would be curious if you have the same issue with the dev version though. Could you also let me know if there are any console errors - looks like the javascript for BCE is not working at all for you. Is anyone else seeing these issues?

Share this post


Link to post
Share on other sites

No, I only added the thead checkboxes, the sort icons were already there. It looks if there was some js file is missing or somehow it is blocked, but no signs of that in the console. I also got all the issues Bernard has. I will try the dev version later. Isn't it some module setting that blocks some features? (eg. add new page button)

Share this post


Link to post
Share on other sites

that's strange. the issues are gone! i'm on 2.6.17 and the dev version of BCE. though i started with the master BCE and maybe the video was taken with that version. i can't remember, sorry :)

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By robert
      I often had the need for an overview of all used fields and their contents for a specific page/template while developing new websites without switching to the backend, so I made a small module which lists all the needed information in a readable manner (at least for me):
      Debug Page Fields
      https://github.com/robertweiss/ProcessDebugPageFields
      It adds two new properties to all pages:
      $page->debugFieldValues – returns an object with all (sub-)fields, their labels, fieldtypes and values $page->debugFieldTypes – returns an object with all fieldtypes and their corresponding fields // List all values of a pages $page->debugFieldValues // List a specific field $page->debugFieldValues->fieldname // List all used fieldtypes of a page $page->debugFieldTypes I recommend using it in combination with Tracy Debugger, Ray, Xdebug etc. as it returns an object and is only meant for developing/debugging uses. 
      For now, the fieldtype support includes mostly fieldtypes I use in my projects, but can easily be extended by adding a new FieldtypeFIELDNAME method to the module. I use it with five different client installations (all PW 3.0.*), but of course there might be some (or more) field configurations which are not covered correctly yet.
      Supported fieldtypes
      Button Checkbox Color Combo Datetime Email FieldsetPage * File FontIconPicker Functional Image ImageReference MapMarker Multiplier Mystique Options Page PageIDs PageTitle Radio Repeater * RepeaterMatrix * RockAwesome SeoMaestro Table Text Textarea Textareas Toggle URL * The fields with complete subfield-support also list their corresponding subfields.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. As this is my first ›public‹ module, I hope I did not miss any important things to mention here.
    • By horst
      Wire Mail SMTP

      An extension to the (new) WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.6.0
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; }  
      A MORE ADVANCED DEBUG METHOD!
      You can add some debug code into a template file and call a page with it:
      $to = array('me@example.com'); $subject = 'Wiremail-SMTP Test ' . date('H:i:s') . ' äöü ÄÖÜ ß'; $mail = wireMail(); if($mail->className != 'WireMailSmtp') { echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; } else { $mail->from = '--INSERT YOUR SENDER ADDRESS HERE --'; // <--- !!!! $mail->to($to); $mail->subject($subject); $mail->sendSingle(true); $mail->body("Titel\n\ntext text TEXT text text\n"); $mail->bodyHTML("<h1>Titel</h1><p>text text <strong>TEXT</strong> text text</p>"); $dump = $mail->debugSend(1); } So, in short, instead of using $mail->send(), use $mail->debugSend(1) to get output on a frontend testpage.
      The output is PRE formatted and contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection, like this one:
       
      Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      debugSend(1) - returns and / or outputs a (pre formatted) dump that contains the areas: SETTINGS, RESULT, ERRORS and a complete debuglog of the server connection. (See above the example code under ADVANCED DEBUG METHOD for further instructions!)


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
       
    • By Cybermano
      Food Allergens Module
      A simple List of Food Allergens
      My needs were to provide a simple list of food allergens for our clients with restaurant related activity.
      The idea was to simply output the list (to speed up the data entry) without leaving the food menu editing, eg. opening another page in new tab or window.
      This isn't a perfect solution, but it works fine for my needs and I decided to share the base idea.
      This could also be easily used to show little notes or short "vademecum", not only for the list of food allergens.
      ---
      Main features
      The basis
      All moves from a short editing of the module in this tutorial: How to create custom admin pages by @bernhard
      First of all it creates an empty admin page, with a dedicated permission to let safe-user to see it (this permission has to be created as a new ones, manually or by the module).
      Once the page is created, I have hooked its behaviour into the ready.php, to show the content (basically a list).
      A step further
      With the tips of  @bernhard, @Soma (and many others), see here , the magic happens. 
      The new page will be shown as a panel, so editors will not abandon their data entry to have a quick view to the list.
      A little further
      Why scroll to the top of the page to click a link?
      The next step was to create a sticky button only in the food menu pages.
      Again with a @bernhard tip I moved into the customization of this simple module and the related hook.
      ---
      How to use this module
      After installed, it creates the page /admin/page/allergens/ and the module is to be setted up. The first field is a CKEditor with multi-language. This is the place where to write the informations that will be shown into the page. The next field is a simply text-area where to place a bit of JS that will be appended to the markup of the text (omit the 'script' tags). I also putted a checkbox with a silly statement: this to think at least twice on the safety of the written JS. Now comes the first way to display the link to the page
      Field Note with Link. Enable and save it. The module will display a new row with 4 selects (1 standard and 3 ASM):
      View mode (to show the page as Panel or as Modal PopUp); Templates to select: select one or more and save before proceed, so the  asm-select of the pages will be populated showing all the pages of the selected templates. Pages to select: also here select at least one and save before proceed to populate the asm-select for fields only with the ones that belong to the selected pages. Select the fields where to place the note and save again. That's all: now you will find into the notes of the selected fields the link "See the List of Allergens".
      At the same way, the option for the sticky button, but with a plus
      The field select is obviously unnecessary, but you could play with the last row: the inline styles to fix your sticky button where you like. Here you could set the sticky position of the <div> and the absolute ones of the <a>.

      Video Explanation
      In these screencasts you could see a custom JS that show a "copy" button near a "hanna-code" call.
      This because I've set a specific one for each allergen to show up a tooltip in the front end.

      Registrazione #33.mp4  

      Registrazione #34.mp4 ---
      Last but not the least
      Actually it works fine for my needs, even if it's much improvable: I'm working on the permissions creation, the uninstall section, a separate configs and defaults and how to include the hook into the module leaving free the ready.php. According to a simpler uninstall. Also I would make the link text as a dynamic text field, so it will be more flexible.
      I always learn a lot here, so I would share my code for whom it could be interested.
      I removed the hanna code references, but I provide you the html list of the allergens, English and Italian too, so you can paste them into the "source" of the CKEditor field to have a ready to use module.
      Obviously you are free to modify the code as per your needs.
      Please, keep in mind that I'm not a pro coder and I beg your pardon for my verbosity (speaking and coding). 😉
      I hope be helpful or for inspiration.
      Bye
      ready.phpList-ITA.htmlList-ENG.htmlAllergens.module
      README.md
    • By Robin S
      This module is sort of an upgrade to my earlier ImageToMarkdown module, and might be useful to anyone working with Markdown in ProcessWire.
      Copy Markdown
      Adds icons to images and files that allow you to copy a Markdown string to the clipboard. When you click the icon a message at the top left of the screen notifies you that the copying has occurred.
      Screencast

      Note: in the screencast an EasyMDE inputfield is used to preview the Markdown. It's not required to use EasyMDE - an ordinary textarea field could be used.
      Usage: Images
      When you hover on an item in an Images field an asterisk icon appears on the thumbnail. Click the icon to copy an image Markdown string to clipboard. If the "Description" field is populated it is used as the alt text.
      You can also open the "Variations" modal for an image and click the asterisk icon to copy an image Markdown string for an individual variation.
      Usage: Files
      When you hover on an item in a Files field an asterisk icon appears next to the filename. Click the icon to copy a link Markdown string to the clipboard. If the "Description" field is populated it is used as the link text, otherwise the filename is used.
       
      https://github.com/Toutouwai/CopyMarkdown
      https://processwire.com/modules/copy-markdown/
    • By BitPoet
      I've realized that I've been jumping back and forth between the PW API docs and the source code for site modules far too much. The idea to hold all necessary documentation locally in one place has occurred to me before, but getting PHPDocumentor et al set up and running reliably (and producing readable output) as always been too much of a hassle. Today I was asked how I find the right hooks and their arguments, and that inspired me to finally get my backside down on the chair and whip something up, namely the
      Module Api Doc Viewer
      ProcessModuleApiDoc
      It lets you browse the inline documentation and public (optionally also protected) class/method/property information for all modules, core classes and template files in the ProcessWire instance. The documentation is generated on the fly, so you don't have to remember to update your docs whenever you update a module.
      The module is quite fresh, so expect some bugs there. Behind the scenes it uses PHP-Parser together with a custom class that extracts the information I needed, and the core TextformatterMarkdownExtra module for rendering the description part in the phpdoc style comments.
      This is not a replacement / competitor to the API Viewer included in the commercial ProDevTools package. There is quite some information included in the inline documentation that my module can't (and won't) parse, but which makes up parts of the official ProcessWire API docs.
      This, instead, is a kind of Swiss army knife to view PHPDoc style information and get a quick class or function reference.
      If you feel daring and want to give it a spin, or if you just want to read a bit more, visit the module's GitHub repository.
      This is the overview page under "Setup" -> "Module API Docs":

      And this is what the documentation for an individual class looks like:

      The core module documentation can of course be found online, but it didn't make sense not to include them.
      Let me know what you think!

×
×
  • Create New...