26 Oct
2009
26 Oct
'09
5:38 p.m.
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
I need it for the WYSIWYG sync plug-in service. I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
Thanks,
Marius
26 Oct
26 Oct
6:02 p.m.
On 10/26/2009 05:38 PM, Marius Dumitru Florea wrote:
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
+0.75
I need it for the WYSIWYG sync plug-in service. I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
28 Oct
28 Oct
8:28 a.m.
Sergiu Dumitriu wrote:
On 10/26/2009 05:38 PM, Marius Dumitru Florea wrote:
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
+0.75
Or, I could add a DocumentVersion class in the bridge and instead have:
/**
* @return the document version
*/
DocumentVersion getVersion();
In this case we have to decide how to create a DocumentVersion instance
and how to serialize it. The easiest way is:
1) new DocumentVersion(String) + DocumentVersion#toString()
and the elaborate way is:
2) DocumentVersionFactory + DocumentVersionSerializer
WDYT? Is it worth to add the DocumentVersion class now when we don't
have a real need?
Thanks,
Marius
I need it for the WYSIWYG sync plug-in service.
I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
10:02 a.m.
On Wed, Oct 28, 2009 at 08:28, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Sergiu Dumitriu wrote:
I would say adding something we don't need in a temporary bridge is
not very usefull, let put this for new model.
On 10/26/2009 05:38 PM, Marius Dumitru Florea
wrote:
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
+0.75
Or, I could add a DocumentVersion class in the bridge and instead have:
/**
* @return the document version
*/
DocumentVersion getVersion();
In this case we have to decide how to create a DocumentVersion instance
and how to serialize it. The easiest way is:
1) new DocumentVersion(String) + DocumentVersion#toString()
and the elaborate way is:
2) DocumentVersionFactory + DocumentVersionSerializer
WDYT? Is it worth to add the DocumentVersion class now when we don't
have a real need?
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
I need it for the WYSIWYG sync plug-in service.
I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
2 Nov
2 Nov
10:44 a.m.
On Oct 28, 2009, at 8:28 AM, Marius Dumitru Florea wrote:
I think I prefer the String for the reason Thomas mentioned (ie that
this is just a bridge and not meant to be our model - I'll restart the
discussion about the Model API).
Thanks
-Vincent
Sergiu Dumitriu wrote:
> On 10/26/2009 05:38 PM, Marius Dumitru Florea wrote:
>> Hi devs,
>>
>> I propose we add the following method to DocumentModelBridge:
>>
>> /**
>> * @return a string identifying the current version of this
>> document
>> */
>> String getVersion();
+0
+0.75
Or, I could add a DocumentVersion class in the bridge and instead
have:
/**
* @return the document version
*/
DocumentVersion getVersion();
In this case we have to decide how to create a DocumentVersion
instance
and how to serialize it. The easiest way is:
1) new DocumentVersion(String) + DocumentVersion#toString()
and the elaborate way is:
2) DocumentVersionFactory + DocumentVersionSerializer
WDYT? Is it worth to add the DocumentVersion class now when we don't
have a real need?
Thanks,
Marius
>
>> I need it for the WYSIWYG sync plug-in service. I'm refactoring
>> the code
>> to use components and I want to drop the dependency on xwiki-core.
>> Getting the document version is the last thing that stops me.
>>
>> Here my +1.
26 Oct
26 Oct
6:12 p.m.
+1
On Mon, Oct 26, 2009 at 17:38, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
I need it for the WYSIWYG sync plug-in service. I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
6:15 p.m.
+1
- Asiri
On Mon, Oct 26, 2009 at 10:08 PM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
I need it for the WYSIWYG sync plug-in service. I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5432
days inactive
5439
days old
6 comments
5 participants
participants (5)
-
Asiri Rathnayake -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol