[Yanel-dev] resource-creator and creation of resource-configuration

[Guillaume Déflache]

Hi!

Michael Wechner wrote:
> simon wrote:
>> Michael Wechner schrieb:
>>> simon wrote:
>>>> hi all
>>>>
>>>> i'm developing a svg resource-type. have a look at 
>>>> http://trac.yanel-contribution.3k3.org/wiki/svg
>>>> the resource configuration is done with configurable views within a 
>>>> custom-config (like the BasicXMLResource).
>>>
>>> very cool :-)
>> BTW i also integrated svg-edit which is a cool browser based svg 
>> editor: http://trac.yanel-contribution.3k3.org/wiki/svg-edit
>> soon i will have a online demo page.

Cool, please ping us again when the demo is online!


>>> I would like to add a third-party resource type page to the yanel 
>>> website where we can link such resource types as yours.
>>>
>>> Makes sense?
>> would be nice.

+1 too.


>>>> i implemented CreatableV2 to allow creation of an svg via 
>>>> resource-creator. but the resource-creator is not able to create 
>>>> custom-config. i think this is ok for now. but what i would like is 
>>>> to disable creation of resource configuration at all.
>>>> e.g if CreatableV2.createRTIProperties(Request) returns null no 
>>>> resource-configuration is created. this would be useful for resource 
>>>> which are configured via rc-map.
>>>
>>> very much aggreed and I have the same itch ;-)
>>>
>>> The question is where would you expect this to be configured? Or just 
>>> as you suggest above if null is returned?
>> the problem is null  is check and  just adds a RC without any 
>> properties. i think is not really proper to change the null behavior.
>>>>
>>>> an other solution would be to delegate the creation of the 
>>>> resource-configuration to the resource. e.g. within CreatableV2 
>>>> introduce a methode createRC(HttpServletRequest request).
>>>
>>> that would probably be the most elegant. I think the CreatableV2 is 
>>> not released yet
>> after thinking some more time i really would prefer a methode 
>> createRC(HttpServletRequest request).
>>>
>>> http://www.yanel.org/javadoc/org/wyona/yanel/core/api/attributes/CreatableV2.html 

[Cannot really comment on that as I dunno much in that area.]


>>> but on the other hand it exists for quite some time now without any 
>>> changes and hence I am afraid
>>> that people consider it realeased ...
>> i'm afraid as well. i would suggest to release CreatableV2 now as it 

Agreed, let's acknowledge reality and release CreatableV2! ;)


>> is. and introduce a new Creatable with the new method. unfortunately 
>> there is already this CreatableV3. i guess it's not possible to 
>> introduce a CreatableV2.1 right?
> 
> sure, that should work.
> 
> Before we get going we should check where the interface is used and what 
> would be the consequences.

Maybe CreatableV3 is not relied upon too much yet and we can still break it?


>> wouldn't it make sense to release the interfaces early and often?
> 
> I think we rather need to think about checkpoints which need to be 
> fulfilled that an interface should be released

Is the standard "life-cycle" of versioned interfaces documented somewhere?
Also I suggest we use Java 5 annotations to document the state of the 
interfaces (e.g. @Frozen, @Draft) instead of copy-pasted docs: we could 
then add extensive documentation on the annotations themselves, and they 
could then be used for Yarep as well as Yanel.


Cheers,
    Guillaume