| Currently in the synced directory we only provide hierarchy in the XFF. This is to create a directory for each language. By example in java directory we will have all code related to java (so groovy and velocity scripts). For javascript it will be the same. Here are an example of what I think we can do:
├── css
│ └── example
│ └── WebHome
│ └── StyleSheetExtension_0.css
├── java
│ ├── pom.xml
│ └── src
│ └── main
│ ├── java
│ │ └── org
│ │ └── example
│ │ └── WebHome
│ │ ├── ContentMacroGroovy_0.groovy
│ │ └── ScriptComponent_0.groovy
│ └── resources
│ └── example
│ └── WebHome
│ ├── ContentMacroVelocity_0.vm
│ └── SkinFileOverride_0.vm
├── js
│ └── example
│ └── WebHome
│ └── JavaScriptExtension_0.js
└── xff
└── spaces
└── example
└── pages
└── WebHome
├── content
└── objects
├── XWiki.JavaScriptExtension
│ └── 0
│ └── properties
│ ├── cache
│ ├── code
│ ├── code.js
│ ├── name
│ ├── parse
│ └── use
├── XWiki.ScriptComponentClass
│ └── 0
│ └── properties
│ ├── scope
│ ├── script_content
│ ├── script_content.groovy
│ └── script_language
├── XWiki.StyleSheetExtension
│ └── 0
│ └── properties
│ ├── cache
│ ├── code
│ ├── code.less
│ ├── contentType
│ ├── name
│ ├── parse
│ └── use
└── XWiki.XWikiSkinFileOverrideClass
├── content
├── content.vm
└── path
So each script which are in page (in macro) or in object are provided in specific par language directory. This have several advantages:
- We can have a specific hierarchy for each specific project language, so the IDE can have the autocompletion by default.
- The hierarchy is less complex and so we can access more quickly to each file.
Note for javascript and css code the hierarchy can be improved, I don't really know what is the recommended hierarchy now. |
