[Yanel-dev] organization of data

[Evaldas Taroza]

simon litwan wrote:
> 
>> which lets you programmatically  access htdosc/yanel-htodcs.
>>
>> then we could introduce a kind a protocol in the rc. e.g. htdocs:// 
>> resp. yanelhtdocs://
>>
>>      <view id="tablelist" type="jelly">
>>        <xslt>/xslt/usecase.xsl</xslt>
>>        <template>htdocs://create-tablelist-shortcut.jelly</template>
>>        <mime-type>text/html</mime-type>
>>      </view>
>>
>> this would use the jelly provided by the resource via htdocs.
>> one could overwrite the jelly by omitting the protocol and point to a 
>> jelly in the realms data repository.
>>
>> BTW:
>> i think if the method public InputStream getHtdocs(String path) would 
>> access the data via package resolving we would go a step forward to 
>> provide resource-types as packages (which i consider very important.)
> i've implemented two new resourceResolver. one with the scheme 
> "resourcehtdocs:" which access files within the resource-types htdocs 
> directory and an other one with the scheme "resourceyanelhtdocs:" which 
> access files within the resource-types yanel-htdocs directory.
> 
> i'm not very happy with the naming of the schemes maybe someone has a 
> better idea.
> 
> here again the two examples for the  schemes:
> resourcehtdocs:/bar/foo.xml
> resourceyanelhtdocs:/bar/foo.xml

I think that instead of resourceyanelhtdocs scheme we should put 
yanel-htdocs inside htdocs of a resource type and use the single scheme 
called 'htdocs':
htdocs:/bar/foo.xml
htdocs:/yanel/bar/foo.xml

We talked with Simon about that, looks like there could be some 
backwards compatibility issues, but it's much nicer isn't it?

Evaldas

-- 
+41 79 616 53 76
www.linkedin.com/in/taroza

Optaros - www.optaros.com