Refactor and cleanup into a unified 'TYPO3 Support' plugin

I would love to see a single IntelliJ plugin that provides support for the complete range of TYPO3 products:

• CMS
• FLOW
• NEOS
• FLUID
• ...

This would mean that the current plugin will need to be refactored a bit to avoid clashes.

I have started setting up such a plugin following the plugin development cookbook because I want support for TypoScript2. Setting it up was a breeze. I just need to take a long hard look at the bnf and flex files.

Maybe we could namespace the refactored plugin to the org.typo3 namespace? What do you think?

Reassigned to @fgalinski

Milestone changed to 1.2.0

Hi Michiel,

I likes the idea of one single plugin, which provides support for all TYPO3 products. Which exact code should I refactor to avoid clashes?

Sure I will change the namespace, when I did the refactoring.

Btw. you aren't alone with the understanding of the bnf and flex stuff. :smiley_smile:

Regards, Fabi

Milestone removed

Milestone changed to 1.2.0

Milestone changed to 1.3.0

Here is a nice and verbose BNF example: http://savage.net.au/SQL/sql-2003-2.bnf.html

And one in EBNF for TypoScript: http://forge.typo3.org/projects/package-typo3-typoscript/repository/revisions/589f6741ac757b64ecf43c97a6b19b7d3d4c3a26/entry/Documentation/TypoScript_Grammar_EBNF.txt

There is also a template grammar and an eel grammar in the NEOS code:

Packages/Framework/TYPO3.Fluid/Documentation/TemplateEngine_Grammar_EBNF.txt Packages/Framework/TYPO3.Eel/Documentation/FLOW3-Eel-Grammar.txt

Robert created a TypoScript grammar, but is seems that is no longer present in the TypoScript package in the NEOS source. There is however a thread about it here: http://forum.typo3.org/index.php/t/196382/

Oh wait. The grammar file seems to be here: http://forge.typo3.org/projects/package-typo3-typoscript/repository/revisions/589f6741ac757b64ecf43c97a6b19b7d3d4c3a26/entry/Documentation/TypoScript_Grammar_EBNF.txt

Now all these files are EBNF. But conversion to BNF should be a no-brainer.

This is really cool. Thank's for your help!

It will save us a lot of time for the integration of a highlighter.

Should we split this EBNF stuff into a .flex and .bnf file? What do you think? :smiley_smile:

I have no idea what the relation between flex and bnf is. Also, the BNF syntax in IDEA seems to support EBNF (usage of * and such). Is there any more documentation about that?

BNF resources:

• http://matt.might.net/articles/grammars-bnf-ebnf/
• https://github.com/JetBrains/Grammar-Kit
• http://www.garshol.priv.no/download/text/bnf.html

What I know is, that the flex stuff assigns every single character from the editor a type and groups them together by rules. The BNF can create parent elements and assigns them the the generated types from the flex.

After this every character has an specific type, it's grouped and nested. With these informations we could implement an auto completion, auto formatting, ...

I think, that the flex stuff is possible in the BNF, but unfortunately I don't have any experience about it.

Maybe this will help: http://confluence.jetbrains.com/display/IntelliJIDEA/Lexer+and+Parser+Definition

In the Neos source we can find a PEG (Parsing Expression Grammar) definition for Eel: Packages/Framework/TYPO3.Eel/Resources/Private/Grammar/Eel.peg.inc

Here is my work so far. There is sooooo much to this grammar: TypoScript2 basic syntax + Eel expressions + Flow query . . .

Wow, really cool! How long did you need for this? If it does work, then I will add this to the next release in two weeks. I work on the plugin next week, then I could implement your code.

Keep on your great work!

I'm currently using the plain bnf and the live preview mode. Took me a while to get to grips with the syntax. I would love to get a better understanding of pinning and recovery. I'm just posting this wip because I'll not be able to work on it in the coming weeks. I don't think it's production ready yet :-)

Thanks for your help Michiel!

I will close this issue and organize them for TS2 for better structuring the open tasks.

Status changed to closed