Analyze ZK configuration files similar to Spring

[schauder]

This should probably done in a separate project, since ZK is somewhat obscure. But it could be a great example for a plugin like thin.

[schauder]

all *.zul files in the directory structure should get considered

<include src="x">

should be considered a dependency from the current file to the "x"

@ref Elements in the file shoud be considered dependencies
fully qualified class Names should be considered dependencies to these classes

[matthiasthieroff]

An example for included zul files

tabbox.zul (reduced to minimum necessary information)

<zk>
    <!-- Option 1 -->
    <include src="/WEB-INF/styles/default.zul" />

    <tabbox >
        <tabs>
            <tab label="1" />
            <tab label="2" />
        </tabs>
        <tabpanels>
            <tabpanel>
                <!-- Option 2 -->
                <include src="@load(xyzVW.getSrc('tabpanel1.zul'))" />
            </tabpanel>
            <tabpanel>
                <!-- Option 3 -->
                <include src="@load(xyzVW.getSrc('subdir/tabpanel2.zul'))" />
            </tabpanel>
        </tabpanels>
    </tabbox>
</zk>

Option 1: The src path is a path relative to the web apps root folder.

Option 2: The src path is composed of a root path and the filename 'tabpanel1.zul'. By convention the root path is the exact same directory where 'tabbox.zul' is located.

Option 3: The src path is composed of a root path and a subdirectory/filename 'subdir/tabpanel2.zul'. By convention the root path is the exact same directory where 'tabbox.zul' is located.

[matthiasthieroff]

An example for dependent Java classes

viewModel.zul

<zk>
    <!-- Option 1 -->
    <div apply="org.zkoss.bind.BindComposer"
        viewModel="@id('xyz') 
        @init('com.abc.def.XyzVM')">

        <!-- Option 2 -->
        <include src="other.zul"
            otherVM="@ref(xyz.other)"/>

        <!-- Option 3 -->
        <div apply="${mnoCtrl}"/>

        <!-- Option 4 -->
        <div apply="com.abc.def.pqsCtrl"/>

    </div>
</zk>

Option 1: Full qualified name to a dependent viewModel 'com.abc.def.XyzVM'.

Option 2: The variable 'otherVM' points to the return value of 'XyzVM.getOther()' and is accessible in 'other.zul'. This class could be everywhere :(

Option 3: A controller which gets injected via spring. You have to look up all spring conexts or scan all source files to resolve the dependency :(

Option 4: A controller with a full qualified name.

[schauder]

Sorry, currently I have no intention to make analysis pluggable