The 8.x-1.x branch is completely outdated and needs a real port now that the D8 API is done.
Ideally, this should start with the minimal effort to get the module to run in a test site - no switch to the Entity API (which might be an idea for later).
In order from least to most complex:
- xbbcode.info.yml
- PSR-{0->4}
- hook_menu()
- Forms
- Filter API
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | xbbcode-d8-2470805-remove-filter-object.patch | 1.65 KB | cburschka |
| #13 | xbbcode-d8-2470805-process-result.patch | 1.67 KB | cburschka |
| #4 | xbbcode-d8-oo.patch | 8.68 KB | cburschka |
Comments
Comment #1
cburschkaThe work is experimental, and will be tracked in the non-release branch "d8-port" until it's somewhat ready for testing.
(Note that this branch is temporary and may disappear or change its history without warning.)
Edit: d8-port is gone; development now happens in 8.x-2.x.
Comment #2
cburschkaDone with the easiest part.
Comment #3
cburschkaThe Routing switch is basically done.
Comment #4
cburschkaHere are a few updates to functions that used to be in the global scope (user_*, module_*, cache(), l(), url(), etc.)
Comment #5
eric_a commentedWonderfull to see this D8 activity! I'm planning to convert the chessboard-8.x-2.x filter module to xbbcode.
Seems to me that plugins would be perfect for tags. For user defined tags you'd use plugin derivers. Also, would be great to switch "markup" to use the D8 Twig inline templates system. Existing markup templates would simply move from
{and}to{{and}}. Perhaps rename markup to template or just add the template key; then this could even be ported to 7.x-1.x.Comment #6
cburschkaThat's certainly an interesting idea! Tags would be basically be like small filter plugins.
Comment #10
cburschkaThe global settings part is done. The filter-specific settings might still need a bit of work, and then of course the filter has to actually process text.
Comment #13
cburschkaThis patch uses FilterProcessResult() to return the processed text.
(Also, some stuff is now marked as private.)
Comment #14
cburschkaThe filter object should not be passed to the tag processor. There are very few reasons why you might use it, and even less of them are a good idea.
In line with the filter API itself hiding the format from the filter plugin instance, this patch now hides the filter from the tag processor.
Comment #17
pgn4web commentedIs a port of XBBCode to Drupal 8 still being developed or planned?
Or should I look for alternatives?
Kind of amazing that the ability to create custom BBCodes has not built-in directly in the Drupal platform.
Comment #18
cburschkaI'm still planning to finish the port; I just haven't had a lot of time lately. :)
I should be able to get some work done next month. If I remember correctly, the port itself doesn't take much more, as long as some of the major architectural changes are left for a later version.
Comment #19
cburschka(dev work is happening in 8.x-2.x)
Comment #22
cburschkaThe new port (8.x-3.x, plugin/entity-based) seems functional and isn't missing anything major (aside from cleanup and refactoring, as well as some more features that would be nice). An alpha may be ready within a few days.
Comment #23
cburschkaWell, aside from the whole default tag package.
Comment #24
cburschka8.x-3.0-alpha1 is up.