Thanks Dave,
this cleared up a few things.
What I wanted to do is to create as few new files as possible. There are already quite a number of files to wire up a page :wink: , so if you could achieve it with config only that would be great. I realise that this example would need more files anyway, beacuse you typically would want the preview on the right of your form.
As you said, adding as a subcomponent to edit-metadata shows preview with only config.
). So what is the default index for a component, SurfBug didn't show that (or i didn't look close enough)?
this cleared up a few things.
What I wanted to do is to create as few new files as possible. There are already quite a number of files to wire up a page :wink: , so if you could achieve it with config only that would be great. I realise that this example would need more files anyway, beacuse you typically would want the preview on the right of your form.
As you said, adding as a subcomponent to edit-metadata shows preview with only config.
<extension>
<modules>
<module>
<id>Edit Metadata with Preview</id>
<description>Adding document preview to edit metadata page</description>
<components>
<component>
<region-id>edit-metadata</region-id>
<source-id>edit-metadata</source-id>
<scope>template</scope>
<sub-components>
<sub-component id="metadatapreview" index="200">
<url>/components/preview/web-preview</url>
<properties>
<nodeRef>{nodeRef}</nodeRef>
</properties>
</sub-component>
</sub-components>
</component>
</components>
</module>
</modules>
</extension>
The index is shown in SurfBug but ONLY if it is non-default. I made this decision because although the default default is 50 (two intentional defaults there) it could be changed and I wanted SurfBug to indicate a default value by NOT displaying anything (because the default index could be manually set)… hope that makes sense - I've possibly overused the word "default" in that last sentence!
I think the Blog post does mention index briefly but doesn't go into a lot of detail… it was something of a balance trying to keep the articles concise but contain enough depth. I'll probably start writing some more in-depth articles as I get more feedback - and of course this is only a temporary substitution for the official documentation that will get released with Alfresco Enterprise.
The configuration you've included looks correct and you've indicated it's working, so I just want to check if there's anything else I can help with?
I really appreciate your feedback on the Blogs - it's good to know people are trying this stuff out !!
Regards,
Dave
I think the Blog post does mention index briefly but doesn't go into a lot of detail… it was something of a balance trying to keep the articles concise but contain enough depth. I'll probably start writing some more in-depth articles as I get more feedback - and of course this is only a temporary substitution for the official documentation that will get released with Alfresco Enterprise.
The configuration you've included looks correct and you've indicated it's working, so I just want to check if there's anything else I can help with?
I really appreciate your feedback on the Blogs - it's good to know people are trying this stuff out !!
Regards,
Dave
Thanks,
I actually tried your suggestion with sub-components, but since a component also renders a a div, it closes the yui opening div. Also tried doing
Next will be to try the customization way.
Here is another scenario:
I want to reorder the action and info panels in document-details, my preference is that document-metadata comes first.
We have in document-details.ftl
Now it isn't, so is there another way for a simple re-order?
Lots of questions here, if you dont find time to answer now, I'll bring them to Devcon.
I actually tried your suggestion with sub-components, but since a component also renders a a div, it closes the yui opening div. Also tried doing
</div><div class="yui-gc">
<div class="yui-u first><div>Next will be to try the customization way.
Here is another scenario:
I want to reorder the action and info panels in document-details, my preference is that document-metadata comes first.
We have in document-details.ftl
<div class="yui-u">
<@region id="document-actions" scope="template"/>
<@region id="document-tags" scope="template"/>
<@region id="document-links" scope="template"/>
<@region id="document-metadata" scope="template"/>
<@region id="document-permissions" scope="template"/>
<@region id="document-workflows" scope="template"/>
<@region id="document-versions" scope="template"/>
<@region id="document-publishing" scope="template"/>
</div>Now it isn't, so is there another way for a simple re-order?
Lots of questions here, if you dont find time to answer now, I'll bring them to Devcon.
Thanks for testing that out… it does sound like there might be a bug in there, I'll do some investigation when I next get a chance.
The other advantage of doing it this way is that you can use a module evaluator to only apply the change in specific circumstances (e.g. specific sites, users, etc). I have to admit this wasn't something that I'd necessarily expected anyone to do, but it's good that you've found another use for it!
The other advantage of doing it this way is that you can use a module evaluator to only apply the change in specific circumstances (e.g. specific sites, users, etc). I have to admit this wasn't something that I'd necessarily expected anyone to do, but it's good that you've found another use for it!
