15 Mar
2010
15 Mar
'10
11:15 a.m.
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much more
time would you need?
Thanks
-Vincent
15 Mar
15 Mar
11:19 a.m.
On 03/15/2010 11:15 AM, Vincent Massol wrote:
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
I worked on it this weekend, fixing the remaining bugs in IE; so all
that's left is preparing the commit. Further AJAXy improvements will be
done for M2.
- captcha on comments. Caleb, let us know if
that's all done or if there's need for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
12:33 p.m.
Sergiu Dumitriu wrote:
On 03/15/2010 11:15 AM, Vincent Massol wrote:
It should be working.
Caleb
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
I worked on it this weekend, fixing the remaining bugs in IE; so all
that's left is preparing the commit. Further AJAXy improvements will be
done for M2.
> - captcha on comments. Caleb, let us know if that's all done or if there's
need for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:31 p.m.
Hi,
On Mon, Mar 15, 2010 at 12:33 PM, Caleb James DeLisle <
calebdelisle(a)lavabit.com> wrote:
Sergiu Dumitriu wrote:
It worked fine for me in FF 3.6 , I'll try to test it in IE.
Guillaume
On 03/15/2010 11:15 AM, Vincent Massol wrote:
> Hi,
>
> We've slipped badly for the 2.3M1 release (my fault for not monitoring
it
closely enough). It was planned on the 8th of March and we're the 15th
already (one week delay).
>
> The other problem is that we don't have what we had imagined would go in
2.3M1 (color theme improvement for ex). Right now there are lots of changes
but nothing really user-noticeable.
>
> So I'd suggest the following:
> * Delay by a few days in order to be able to include:
> - color theme improvement. Sergiu you need to tell us if that's doable
and
for when.
I worked on it this weekend, fixing the remaining bugs in IE; so all
that's left is preparing the commit. Further AJAXy improvements will be
done for M2.
> - captcha on comments. Caleb, let us know if that's all done or if
there's need for more testing/development.
It should be working.
Caleb
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
>
> Bonus:
> - Anca, will it be possible to have annotations released for 2.3M1 (ie
now)?
How much more time would you need?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:04 p.m.
Hi Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the server
and a .xar to install the default annotations application.
Thanks,
Anca
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
6:17 p.m.
New subject: [xwiki-devs] [VOTE]Â Annotations in the platform (was Re: XE 2.3M1 release preparation)
On Mar 15, 2010, at 4:04 PM, Anca Luca wrote:
Hi Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
I think we should:
* have platform/xwiki-annotations and release it when we release the plaform
* have applications/annotations and include it in the default XE XAR
The rationale is that annotations is a powerful feature and I believe it's good to
have it by default for now (it would be too difficult to install it separately for now).
When we have the extension manager implemented, we'll be able to trim down the size of
what the "core" platform and instead have the user be able to install extensions
when they start their wiki for the first time or when they go to the admin page for this.
But since we don't have this now I feel it's better to have annotations packaged
in the platform and in the default XAR than not have it.
Here's my +1 to both (API in the platform and annotation XAR in default XE).
Note: It would be great to have the ability to turn on/off the annotations feature for 2.3
final.
Thanks
-Vincent
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the server
and a .xar to install the default annotations application.
17 Mar
17 Mar
12:56 a.m.
New subject: [xwiki-devs] [VOTE]Â Annotations in the platform (was Re: XE 2.3M1 release preparation)
Hi Vincent,
On 03/15/2010 07:17 PM, Vincent Massol wrote:
On Mar 15, 2010, at 4:04 PM, Anca Luca wrote:
Why would it be difficult? we can maven magic a zip with a bunch of jars anytime
and make people unpack it in their WEB-INF/lib & install the xar. I think that's
reasonable complexity for such an extension.
Thanks,
Anca
Hi Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
I think we should:
* have platform/xwiki-annotations and release it when we release the plaform
* have applications/annotations and include it in the default XE XAR
The rationale is that annotations is a powerful feature and I believe it's good to
have it by default for now (it would be too difficult to install it separately for now).
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the server
and a .xar to install the default annotations application.
When we have the extension manager implemented, we'll be able to trim down the size
of what the "core" platform and instead have the user be able to install
extensions when they start their wiki for the first time or when they go to the admin page
for this. But since we don't have this now I feel it's better to have annotations
packaged in the platform and in the default XAR than not have it.
Here's my +1 to both (API in the platform and annotation XAR in default XE).
Note: It would be great to have the ability to turn on/off the annotations feature for
2.3 final.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
7:59 a.m.
New subject: [xwiki-devs] [VOTE]Â Annotations in the platform (was Re: XE 2.3M1 release preparation)
On Mar 17, 2010, at 12:56 AM, Anca Luca wrote:
Hi Vincent,
On 03/15/2010 07:17 PM, Vincent Massol wrote:
That's what I call complex. It's too complex for a large majority of our users and
it would make the annotation feature not used which is a shame. In any case I don't
see any compelling reason not to bundle it by default in the default XE we distribute.
Thanks
-Vincent
On Mar 15, 2010, at 4:04 PM, Anca Luca wrote:
Why would it be difficult? we can maven magic a zip with a bunch of jars anytime
and make people unpack it in their WEB-INF/lib & install the xar. I think that's
reasonable complexity for such an extension. Hi Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
I think we should:
* have platform/xwiki-annotations and release it when we release the plaform
* have applications/annotations and include it in the default XE XAR
The rationale is that annotations is a powerful feature and I believe it's good to
have it by default for now (it would be too difficult to install it separately for now).
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the server
and a .xar to install the default annotations application. Thanks,
Anca
When we have the extension manager implemented, we'll be able to trim down the size
of what the "core" platform and instead have the user be able to install
extensions when they start their wiki for the first time or when they go to the admin page
for this. But since we don't have this now I feel it's better to have annotations
packaged in the platform and in the default XAR than not have it.
Here's my +1 to both (API in the platform and annotation XAR in default XE).
Note: It would be great to have the ability to turn on/off the annotations feature for
2.3 final.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
15 Mar
15 Mar
8:37 p.m.
Hi Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
Annotations JS and CSS should be moved to web/standard/ as filesystem
extensions/resources (as are the other "core" UI features), not be
contained in the XAR.
Jerome.
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring
it closely enough). It was planned on the 8th of March and we're the
15th already (one week delay).
The other problem is that we don't have what we had imagined would go in
2.3M1 (color theme improvement for ex). Right now there are lots of
changes but nothing really user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable
and for when.
- captcha on comments. Caleb, let us know if that's all done or if
there's need for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie
now)? How much more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a
long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the
server
and a .xar to install the default annotations application.
Thanks,
Anca
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
17 Mar
17 Mar
12:54 a.m.
Hi Jerome,
On 03/15/2010 09:37 PM, Jerome Velociter wrote:
Actually that's a longer refactor, to actually make the Annotations part of the
UI / skin, instead of having this integration done in js, after the pages get
rendered. That's if we make it a core default feature.
Anca
Hi Vincent,
all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
Annotations JS and CSS should be moved to web/standard/ as filesystem
extensions/resources (as are the other "core" UI features), not be
contained in the XAR. Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring
it closely enough). It was planned on the 8th of March and we're the
15th already (one week delay).
The other problem is that we don't have what we had imagined would go in
2.3M1 (color theme improvement for ex). Right now there are lots of
changes but nothing really user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable
and for when.
- captcha on comments. Caleb, let us know if that's all done or if
there's need for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie
now)? How much more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a
long
time now.
I shouldn't need more than 2 days, but how would we want the annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on the
server
and a .xar to install the default annotations application.
Jerome.
Thanks,
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:30 a.m.
Hi Jerome,
On 03/15/2010 09:37 PM, Jerome Velociter wrote:
Actually that's a longer refactor, to actually make the Annotations part
of the
UI / skin, instead of having this integration done in js, after the pages
get
rendered. That's if we make it a core default feature.
But isn't that what we are discussing right now, making it a core feature?
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :)
Jerome.
Hi
Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
Annotations JS and CSS should be moved to web/standard/ as filesystem
extensions/resources (as are the other "core" UI features), not be
contained in the XAR. Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring
it closely enough). It was planned on the 8th of March and we're the
15th already (one week delay).
The other problem is that we don't have what we had imagined would go
in
2.3M1 (color theme improvement for ex). Right now there are lots of
changes but nothing really user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable
and for when.
- captcha on comments. Caleb, let us know if that's all done or if
there's need for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie
now)? How much more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a
long
time now.
I shouldn't need more than 2 days, but how would we want the
annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on
the
server
and a .xar to install the default annotations application.
Anca
Jerome.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks,
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:44 a.m.
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
For me it should be packaged in the default XE but it should stay as separate as possible
from the rest, i.e. it should be possible to have a working platform without the
annotations feature. This is true for almost everything but for technical reason we cannot
always do it.
If we can keep it separate and use skin extensions for ex rather the having to modify
existing templates, etc we should probably do that.
Thanks
-Vincent
Hi Jerome,
On 03/15/2010 09:37 PM, Jerome Velociter wrote:
Actually that's a longer refactor, to actually make the Annotations part
of the
UI / skin, instead of having this integration done in js, after the pages
get
rendered. That's if we make it a core default feature.
But isn't that what we are discussing right now, making it a core feature?
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :) Hi
Vincent, all
On 03/15/2010 12:15 PM, Vincent Massol wrote:
> Hi,
>
> We've slipped badly for the 2.3M1 release (my fault for not monitoring
> it closely enough). It was planned on the 8th of March and we're the
> 15th already (one week delay).
>
> The other problem is that we don't have what we had imagined would go
> in
> 2.3M1 (color theme improvement for ex). Right now there are lots of
> changes but nothing really user-noticeable.
>
> So I'd suggest the following:
> * Delay by a few days in order to be able to include:
> - color theme improvement. Sergiu you need to tell us if that's doable
> and for when.
> - captcha on comments. Caleb, let us know if that's all done or if
> there's need for more testing/development.
>
> Bonus:
> - Anca, will it be possible to have annotations released for 2.3M1 (ie
> now)? How much more time would you need?
I'll close the vote for XWIKI-4775 asap, and commit it since it's due a
long
time now.
I shouldn't need more than 2 days, but how would we want the
annotations
integrated in the platform?
Right now they're built as an extension, with some jars to deploy on
the
server
and a .xar to install the default annotations application.
Annotations JS and CSS should be moved to web/standard/ as filesystem
extensions/resources (as are the other "core" UI features), not be
contained in the XAR.
Jerome.
>
> Anca
>
>>
>> Jerome.
>>
>>>
>>> Thanks,
>>> Anca
>>>
>>>>
>>>> Thanks
>>>> -Vincent
11:34 a.m.
Hi Vincent,
On 03/17/2010 11:44 AM, Vincent Massol wrote:
We can keep it separate using the js and css that is currently in the
extensions, for the moment.
But as a general strategy, if we "integrate" them in the default platform /
enterprise and it gets stable enough, I don't see why they won't be properly
integrated, i.e. instead of adding the "Annotations" tab shortcut from js, put
it in the vms where the others are, same for the Annotations tab, etc.
However, we need to make sure we preserve the level of customizability:
annotations are designed to be easily customizable, from forms and UI, to js
powering functionality and all, easily *from the browser* with no filesystem
access. I prefer it stays like that.
However, for the moment (2.3M1), that's quite a bit of refactoring (the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
2/ js & css in resources, script documents with annotation forms & other
scripted UI in .xar
My vote goes for 1/ since it's less mess.
WDYT?
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
>> Hi Jerome,
>>
>> On 03/15/2010 09:37 PM, Jerome Velociter wrote:
>>>> Hi Vincent, all
>>>>
>>>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
>>>>> Hi,
>>>>>
>>>>> We've slipped badly for the 2.3M1 release (my fault for not
monitoring
>>>>> it closely enough). It was planned on the 8th of March and we're
the
>>>>> 15th already (one week delay).
>>>>>
>>>>> The other problem is that we don't have what we had imagined
would go
>>>>> in
>>>>> 2.3M1 (color theme improvement for ex). Right now there are lots of
>>>>> changes but nothing really user-noticeable.
>>>>>
>>>>> So I'd suggest the following:
>>>>> * Delay by a few days in order to be able to include:
>>>>> - color theme improvement. Sergiu you need to tell us if that's
doable
>>>>> and for when.
>>>>> - captcha on comments. Caleb, let us know if that's all done or
if
>>>>> there's need for more testing/development.
>>>>>
>>>>> Bonus:
>>>>> - Anca, will it be possible to have annotations released for 2.3M1
(ie
>>>>> now)? How much more time would you need?
>>>>
>>>> I'll close the vote for XWIKI-4775 asap, and commit it since it's
due a
>>>> long
>>>> time now.
>>>> I shouldn't need more than 2 days, but how would we want the
>>>> annotations
>>>> integrated in the platform?
>>>>
>>>> Right now they're built as an extension, with some jars to deploy on
>>>> the
>>>> server
>>>> and a .xar to install the default annotations application.
>>>
>>> Annotations JS and CSS should be moved to web/standard/ as filesystem
>>> extensions/resources (as are the other "core" UI features), not be
>>> contained in the XAR.
>>
>> Actually that's a longer refactor, to actually make the Annotations part
>> of the
>> UI / skin, instead of having this integration done in js, after the pages
>> get
>> rendered. That's if we make it a core default feature.
>
> But isn't that what we are discussing right now, making it a core feature?
yes, but I don't think it's fully decided (should send a vote asap).
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :)
For me it should be packaged in the default XE but it should stay as separate as
possible from the rest, i.e. it should be possible to have a working platform without the
annotations feature. This is true for almost everything but for technical reason we cannot
always do it.
If we can keep it separate and use skin extensions for ex rather the having to modify
existing templates, etc we should probably do that.
Thanks
-Vincent
Jerome.
>
> Anca
>
>>
>> Jerome.
>>
>>>
>>> Thanks,
>>> Anca
>>>
>>>>
>>>> Thanks
>>>> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:49 a.m.
On 03/17/2010 11:34 AM, Anca Luca wrote:
Hi Vincent,
On 03/17/2010 11:44 AM, Vincent Massol wrote:
We can keep it separate using the js and css that is currently in the
extensions, for the moment.
But as a general strategy, if we "integrate" them in the default platform /
enterprise and it gets stable enough, I don't see why they won't be properly
integrated, i.e. instead of adding the "Annotations" tab shortcut from js, put
it in the vms where the others are, same for the Annotations tab, etc.
However, we need to make sure we preserve the level of customizability:
annotations are designed to be easily customizable, from forms and UI, to js
powering functionality and all, easily *from the browser* with no filesystem
access. I prefer it stays like that.
However, for the moment (2.3M1), that's quite a bit of refactoring (the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
2/ js& css in resources, script documents with annotation forms& other
scripted UI in .xar
My vote goes for 1/ since it's less mess.
+1 for 1/
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
>> Hi Jerome,
>>
>> On 03/15/2010 09:37 PM, Jerome Velociter wrote:
>>>> Hi Vincent, all
>>>>
>>>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
>>>>> Hi,
>>>>>
>>>>> We've slipped badly for the 2.3M1 release (my fault for not
monitoring
>>>>> it closely enough). It was planned on the 8th of March and we're
the
>>>>> 15th already (one week delay).
>>>>>
>>>>> The other problem is that we don't have what we had imagined
would go
>>>>> in
>>>>> 2.3M1 (color theme improvement for ex). Right now there are lots of
>>>>> changes but nothing really user-noticeable.
>>>>>
>>>>> So I'd suggest the following:
>>>>> * Delay by a few days in order to be able to include:
>>>>> - color theme improvement. Sergiu you need to tell us if that's
doable
>>>>> and for when.
>>>>> - captcha on comments. Caleb, let us know if that's all done or
if
>>>>> there's need for more testing/development.
>>>>>
>>>>> Bonus:
>>>>> - Anca, will it be possible to have annotations released for 2.3M1
(ie
>>>>> now)? How much more time would you need?
>>>>
>>>> I'll close the vote for XWIKI-4775 asap, and commit it since it's
due a
>>>> long
>>>> time now.
>>>> I shouldn't need more than 2 days, but how would we want the
>>>> annotations
>>>> integrated in the platform?
>>>>
>>>> Right now they're built as an extension, with some jars to deploy on
>>>> the
>>>> server
>>>> and a .xar to install the default annotations application.
>>>
>>> Annotations JS and CSS should be moved to web/standard/ as filesystem
>>> extensions/resources (as are the other "core" UI features), not be
>>> contained in the XAR.
>>
>> Actually that's a longer refactor, to actually make the Annotations part
>> of the
>> UI / skin, instead of having this integration done in js, after the pages
>> get
>> rendered. That's if we make it a core default feature.
>
> But isn't that what we are discussing right now, making it a core feature?
yes, but I don't think it's fully decided (should send a vote asap).
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :)
For me it should be packaged in the default XE but it should stay as separate as
possible from the rest, i.e. it should be possible to have a working platform without the
annotations feature. This is true for almost everything but for technical reason we cannot
always do it.
If we can keep it separate and use skin extensions for ex rather the having to modify
existing templates, etc we should probably do that.
12:02 p.m.
Hi Vincent,
On 03/17/2010 11:44 AM, Vincent Massol wrote:
We can keep it separate using the js and css that is currently in the
extensions, for the moment.
But as a general strategy, if we "integrate" them in the default platform
/
enterprise and it gets stable enough, I don't see why they won't be
properly
integrated, i.e. instead of adding the "Annotations" tab shortcut from js,
put
it in the vms where the others are, same for the Annotations tab, etc.
However, we need to make sure we preserve the level of customizability:
annotations are designed to be easily customizable, from forms and UI, to
js
powering functionality and all, easily *from the browser* with no
filesystem
access. I prefer it stays like that.
The proper way of doing this is with an extension mechanism where wiki JSX
(so in the browser) come and register new features/extensions against the
generic annotation feature (a plugin system of some sort), not by letting
developers modify the core of the annotation feature script (which makes
it un-maintainable)
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
>> Hi Jerome,
>>
>> On 03/15/2010 09:37 PM, Jerome Velociter wrote:
>>>> Hi Vincent, all
>>>>
>>>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
>>>>> Hi,
>>>>>
>>>>> We've slipped badly for the 2.3M1 release (my fault for not
>>>>> monitoring
>>>>> it closely enough). It was planned on the 8th of March and we're
>>>>> the
>>>>> 15th already (one week delay).
>>>>>
>>>>> The other problem is that we don't have what we had imagined
would
>>>>> go
>>>>> in
>>>>> 2.3M1 (color theme improvement for ex). Right now there are lots of
>>>>> changes but nothing really user-noticeable.
>>>>>
>>>>> So I'd suggest the following:
>>>>> * Delay by a few days in order to be able to include:
>>>>> - color theme improvement. Sergiu you need to tell us if that's
>>>>> doable
>>>>> and for when.
>>>>> - captcha on comments. Caleb, let us know if that's all done or
if
>>>>> there's need for more testing/development.
>>>>>
>>>>> Bonus:
>>>>> - Anca, will it be possible to have annotations released for 2.3M1
>>>>> (ie
>>>>> now)? How much more time would you need?
>>>>
>>>> I'll close the vote for XWIKI-4775 asap, and commit it since
it's
>>>> due a
>>>> long
>>>> time now.
>>>> I shouldn't need more than 2 days, but how would we want the
>>>> annotations
>>>> integrated in the platform?
>>>>
>>>> Right now they're built as an extension, with some jars to deploy on
>>>> the
>>>> server
>>>> and a .xar to install the default annotations application.
>>>
>>> Annotations JS and CSS should be moved to web/standard/ as filesystem
>>> extensions/resources (as are the other "core" UI features), not be
>>> contained in the XAR.
>>
>> Actually that's a longer refactor, to actually make the Annotations
>> part
>> of the
>> UI / skin, instead of having this integration done in js, after the
>> pages
>> get
>> rendered. That's if we make it a core default feature.
>
> But isn't that what we are discussing right now, making it a core
> feature?
yes, but I don't think it's fully decided (should send a vote asap).
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more
comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :)
For me it should be packaged in the default XE but it should stay as
separate as possible from the rest, i.e. it should be possible to have a
working platform without the annotations feature. This is true for
almost everything but for technical reason we cannot always do it.
If we can keep it separate and use skin extensions for ex rather the
having to modify existing templates, etc we should probably do that.
However, for the moment (2.3M1), that's quite a bit of refactoring (the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
If it's only for M1 as a path to have the feature integrated in templates
and resources, it means you are creating yourself a challenge for the
migration path (you will need to find a way to delete or ignore the
always-loaded SX from the wiki if at some point the make their ways into
the core).
2/ js & css in resources, script documents with
annotation forms & other
scripted UI in .xar
What does form and scripted UI means ? They are scripts that generated
HTML loaded by AJAX in the pages ? (for example in the docExtra tabs ?) Or
is it something else ?
My vote goes for 1/ since it's less mess.
0
Jerome.
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Jerome.
>
> Anca
>
>>
>> Jerome.
>>
>>>
>>> Thanks,
>>> Anca
>>>
>>>>
>>>> Thanks
>>>> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:37 p.m.
Hi Jerome,
On 03/17/2010 01:02 PM, Jerome Velociter wrote:
Ideally yes, i've been thinking about this in the past days, and I still think
it's too much.
1/ because it would mean maintaining an annotations js API, which sounds a bit
too much: we need to commit to it, make it backwards compatible, etc. However if
it's part of the platform, then it follows all platform rules, among which js
API. "plugin system of some sort" it's a bit too much...
2/ because chances are it won't be enough unless very granulated, and the finer
the granulation, the bigger pain 1/ is
3/ because customizations are not only at .js level, they would be at the macros
& scripts generating the UI level too (documents now but templates in the
integration), for which building APIs is a bit harder (there is no way to
override a macro in velo iirc) and, again, "plugin system of some sort" sounds a
bit too much and chances are it won't be enough.
That's a good point. Is it an option to have good release notes from M1 to M2
and RCs and having it done nice for final?
can the migration be handled with good release notes between milestones and RCs?
(as in I agree this would be a mess for a final, but milestones have a different
status...)
Thanks,
Anca
yes, that's what it means: the docExtra tab, all the annotation forms (create,
edit, display, etc) are html fetched with ajax from generating scripts in xwiki
docs ftm, none is created from javascript, for customizability purposes.
Hi Vincent,
On 03/17/2010 11:44 AM, Vincent Massol wrote:
We can keep it separate using the js and css that is currently in the
extensions, for the moment.
But as a general strategy, if we "integrate" them in the default platform
/
enterprise and it gets stable enough, I don't see why they won't be
properly
integrated, i.e. instead of adding the "Annotations" tab shortcut from js,
put
it in the vms where the others are, same for the Annotations tab, etc.
However, we need to make sure we preserve the level of customizability:
annotations are designed to be easily customizable, from forms and UI, to
js
powering functionality and all, easily *from the browser* with no
filesystem
access. I prefer it stays like that.
The proper way of doing this is with an extension mechanism where wiki JSX
(so in the browser) come and register new features/extensions against the
generic annotation feature (a plugin system of some sort), not by letting
developers modify the core of the annotation feature script (which makes
it un-maintainable)
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
>> Hi Jerome,
>>
>> On 03/15/2010 09:37 PM, Jerome Velociter wrote:
>>>> Hi Vincent, all
>>>>
>>>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
>>>>> Hi,
>>>>>
>>>>> We've slipped badly for the 2.3M1 release (my fault for not
>>>>> monitoring
>>>>> it closely enough). It was planned on the 8th of March and we're
>>>>> the
>>>>> 15th already (one week delay).
>>>>>
>>>>> The other problem is that we don't have what we had imagined
would
>>>>> go
>>>>> in
>>>>> 2.3M1 (color theme improvement for ex). Right now there are lots of
>>>>> changes but nothing really user-noticeable.
>>>>>
>>>>> So I'd suggest the following:
>>>>> * Delay by a few days in order to be able to include:
>>>>> - color theme improvement. Sergiu you need to tell us if that's
>>>>> doable
>>>>> and for when.
>>>>> - captcha on comments. Caleb, let us know if that's all done or
if
>>>>> there's need for more testing/development.
>>>>>
>>>>> Bonus:
>>>>> - Anca, will it be possible to have annotations released for 2.3M1
>>>>> (ie
>>>>> now)? How much more time would you need?
>>>>
>>>> I'll close the vote for XWIKI-4775 asap, and commit it since
it's
>>>> due a
>>>> long
>>>> time now.
>>>> I shouldn't need more than 2 days, but how would we want the
>>>> annotations
>>>> integrated in the platform?
>>>>
>>>> Right now they're built as an extension, with some jars to deploy on
>>>> the
>>>> server
>>>> and a .xar to install the default annotations application.
>>>
>>> Annotations JS and CSS should be moved to web/standard/ as filesystem
>>> extensions/resources (as are the other "core" UI features), not be
>>> contained in the XAR.
>>
>> Actually that's a longer refactor, to actually make the Annotations
>> part
>> of the
>> UI / skin, instead of having this integration done in js, after the
>> pages
>> get
>> rendered. That's if we make it a core default feature.
>
> But isn't that what we are discussing right now, making it a core
> feature?
yes, but I don't think it's fully decided (should send a vote asap).
For me, as soon as we distribute annotations together with XE, their
should be not a single line of JavaScript in wiki documents.
(But that does not mean you need to rewrite everything so that more
comes
with the rendered DOM and less is injected/manipulated in JS - though I
agree it would be nicer if the annotations would work even when there
would be no JavaScript :)
For me it should be packaged in the default XE but it should stay as
separate as possible from the rest, i.e. it should be possible to have a
working platform without the annotations feature. This is true for
almost everything but for technical reason we cannot always do it.
If we can keep it separate and use skin extensions for ex rather the
having to modify existing templates, etc we should probably do that.
However, for the moment (2.3M1), that's quite a bit of refactoring (the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
If it's only for M1 as a path to have the feature integrated in templates
and resources, it means you are creating yourself a challenge for the
migration path (you will need to find a way to delete or ignore the
always-loaded SX from the wiki if at some point the make their ways into
the core). 2/ js& css in resources, script documents
with annotation forms& other
scripted UI in .xar
What does form and scripted UI means ? They are scripts that generated
HTML loaded by AJAX in the pages ? (for example in the docExtra tabs ?) Or
is it something else ?
My vote goes for 1/ since it's less mess.
0
Jerome.
WDYT?
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Jerome.
>
> Anca
>
>>
>> Jerome.
>>
>>>
>>> Thanks,
>>> Anca
>>>
>>>>
>>>> Thanks
>>>> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:58 p.m.
On 03/17/2010 01:37 PM, Anca Luca wrote:
That's a good point. Is it an option to have good release notes from M1 to M2
and RCs and having it done nice for final?
can the migration be handled with good release notes between milestones and RCs?
(as in I agree this would be a mess for a final, but milestones have a different
status...)
Thanks,
Anca
yes, that's what it means: the docExtra tab, all the annotation forms (create,
edit, display, etc) are html fetched with ajax from generating scripts in xwiki
docs ftm, none is created from javascript, for customizability purposes.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi Jerome,
On 03/17/2010 01:02 PM, Jerome Velociter wrote:
Ideally yes, i've been thinking about this in the past days, and I still think
it's too much.
1/ because it would mean maintaining an annotations js API, which sounds a bit
too much: we need to commit to it, make it backwards compatible, etc. However if
it's part of the platform, then it follows all platform rules, among which js
API. "plugin system of some sort" it's a bit too much...
2/ because chances are it won't be enough unless very granulated, and the finer
the granulation, the bigger pain 1/ is
3/ because customizations are not only at .js level, they would be at the macros
& scripts generating the UI level too (documents now but templates in the
integration), for which building APIs is a bit harder (there is no way to
override a macro in velo iirc) and, again, "plugin system of some sort" sounds
a
bit too much and chances are it won't be enough.
Actually .js can be handled, to some extent, using events.
And we can consider that we ignore 'the html issue' since it can all be modified
from js provided that appropriate handlers can be registered.
I don't like the second part that much though.
Thanks,
Anca
Hi
Vincent,
On 03/17/2010 11:44 AM, Vincent Massol wrote:
The proper way of doing this is with an extension mechanism where wiki JSX
(so in the browser) come and register new features/extensions against the
generic annotation feature (a plugin system of some sort), not by letting
developers modify the core of the annotation feature script (which makes
it un-maintainable)
On Mar 17, 2010, at 10:30 AM, Jerome Velociter wrote:
>> Hi Jerome,
>>
>> On 03/15/2010 09:37 PM, Jerome Velociter wrote:
>>>> Hi Vincent, all
>>>>
>>>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
>>>>> Hi,
>>>>>
>>>>> We've slipped badly for the 2.3M1 release (my fault for not
>>>>> monitoring
>>>>> it closely enough). It was planned on the 8th of March and we're
>>>>> the
>>>>> 15th already (one week delay).
>>>>>
>>>>> The other problem is that we don't have what we had imagined
would
>>>>> go
>>>>> in
>>>>> 2.3M1 (color theme improvement for ex). Right now there are lots of
>>>>> changes but nothing really user-noticeable.
>>>>>
>>>>> So I'd suggest the following:
>>>>> * Delay by a few days in order to be able to include:
>>>>> - color theme improvement. Sergiu you need to tell us if that's
>>>>> doable
>>>>> and for when.
>>>>> - captcha on comments. Caleb, let us know if that's all done or
if
>>>>> there's need for more testing/development.
>>>>>
>>>>> Bonus:
>>>>> - Anca, will it be possible to have annotations released for 2.3M1
>>>>> (ie
>>>>> now)? How much more time would you need?
>>>>
>>>> I'll close the vote for XWIKI-4775 asap, and commit it since
it's
>>>> due a
>>>> long
>>>> time now.
>>>> I shouldn't need more than 2 days, but how would we want the
>>>> annotations
>>>> integrated in the platform?
>>>>
>>>> Right now they're built as an extension, with some jars to deploy on
>>>> the
>>>> server
>>>> and a .xar to install the default annotations application.
>>>
>>> Annotations JS and CSS should be moved to web/standard/ as filesystem
>>> extensions/resources (as are the other "core" UI features), not be
>>> contained in the XAR.
>>
>> Actually that's a longer refactor, to actually make the Annotations
>> part
>> of the
>> UI / skin, instead of having this integration done in js, after the
>> pages
>> get
>> rendered. That's if we make it a core default feature.
>
> But isn't that what we are discussing right now, making it a core
> feature?
yes, but I don't think it's fully decided (should send a vote asap).
>
> For me, as soon as we distribute annotations together with XE, their
> should be not a single line of JavaScript in wiki documents.
> (But that does not mean you need to rewrite everything so that more
> comes
> with the rendered DOM and less is injected/manipulated in JS - though I
> agree it would be nicer if the annotations would work even when there
> would be no JavaScript :)
For me it should be packaged in the default XE but it should stay as
separate as possible from the rest, i.e. it should be possible to have a
working platform without the annotations feature. This is true for
almost everything but for technical reason we cannot always do it.
If we can keep it separate and use skin extensions for ex rather the
having to modify existing templates, etc we should probably do that.
We can keep it separate using the js and css that is currently in the
extensions, for the moment.
But as a general strategy, if we "integrate" them in the default platform
/
enterprise and it gets stable enough, I don't see why they won't be
properly
integrated, i.e. instead of adding the "Annotations" tab shortcut from js,
put
it in the vms where the others are, same for the Annotations tab, etc.
However, we need to make sure we preserve the level of customizability:
annotations are designed to be easily customizable, from forms and UI, to
js
powering functionality and all, easily *from the browser* with no
filesystem
access. I prefer it stays like that.
However, for the moment (2.3M1), that's quite a bit of refactoring (the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
If it's only for M1 as a path to have the feature integrated in templates
and resources, it means you are creating yourself a challenge for the
migration path (you will need to find a way to delete or ignore the
always-loaded SX from the wiki if at some point the make their ways into
the core). 2/ js& css in resources, script documents
with annotation forms& other
scripted UI in .xar
What does form and scripted UI means ? They are scripts that generated
HTML loaded by AJAX in the pages ? (for example in the docExtra tabs ?) Or
is it something else ?
My vote goes for 1/ since it's less mess.
0
Jerome.
WDYT?
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thanks
-Vincent
>
> Jerome.
>
>
>
>>
>> Anca
>>
>>>
>>> Jerome.
>>>
>>>>
>>>> Thanks,
>>>> Anca
>>>>
>>>>>
>>>>> Thanks
>>>>> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:15 p.m.
[snip]
Yes, that's what I had in mind.
Ideally yes,
i've been thinking about this in the past days, and I still
think
it's too much.
1/ because it would mean maintaining an annotations js API, which sounds
a bit
too much: we need to commit to it, make it backwards compatible, etc.
However if
it's part of the platform, then it follows all platform rules, among
which js
API. "plugin system of some sort" it's a bit too much...
2/ because chances are it won't be enough unless very granulated, and
the finer
the granulation, the bigger pain 1/ is
3/ because customizations are not only at .js level, they would be at
the macros
& scripts generating the UI level too (documents now but templates in
the
integration), for which building APIs is a bit harder (there is no way
to
override a macro in velo iirc) and, again, "plugin system of some sort"
sounds a
bit too much and chances are it won't be enough.
Actually .js can be handled, to some extent, using events. And we can consider that we ignore 'the html
issue' since it can all be
modified
from js provided that appropriate handlers can be registered.
What is the 'HTML issue' ? I don't understand what you mean by that.
Jerome.
I don't like the second part that much though.
Thanks,
Anca
That's a good point. Is it an option to have good release notes from M1
to M2
and RCs and having it done nice for final?
can the migration be handled with good release notes between milestones
and RCs?
(as in I agree this would be a mess for a final, but milestones have a
different
status...)
Thanks,
Anca
yes, that's what it means: the docExtra tab, all the annotation forms
(create,
edit, display, etc) are html fetched with ajax from generating scripts
in xwiki
docs ftm, none is created from javascript, for customizability purposes.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
However, for the moment (2.3M1), that's quite a bit of refactoring
(the
integration) which i'm not willing to do.
So for M1 it would be either:
1/ all in xar (js, css, script documents with annotation forms)
If it's only for M1 as a path to have the feature integrated in
templates
and resources, it means you are creating yourself a challenge for the
migration path (you will need to find a way to delete or ignore the
always-loaded SX from the wiki if at some point the make their ways
into
the core). 2/ js& css in resources, script documents
with annotation forms&
other
scripted UI in .xar
What does form and scripted UI means ? They are scripts that generated
HTML loaded by AJAX in the pages ? (for example in the docExtra tabs ?)
Or
is it something else ?
My vote goes for 1/ since it's less mess.
0
Jerome.
WDYT?
>
> Thanks
> -Vincent
>
>>
>> Jerome.
>>
>>
>>
>>>
>>> Anca
>>>
>>>>
>>>> Jerome.
>>>>
>>>>>
>>>>> Thanks,
>>>>> Anca
>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> -Vincent
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:24 p.m.
On 03/17/2010 03:15 PM, Jerome Velociter wrote:
[snip]
Yes, that's what I had in mind.
The fact that some extensions need to change the html of the annotations
interface. For example, the way an annotation is displayed when hovered in the
text, or the edit form (point 3/ above).
Anca
Ideally
yes, i've been thinking about this in the past days, and I still
think
it's too much.
1/ because it would mean maintaining an annotations js API, which sounds
a bit
too much: we need to commit to it, make it backwards compatible, etc.
However if
it's part of the platform, then it follows all platform rules, among
which js
API. "plugin system of some sort" it's a bit too much...
2/ because chances are it won't be enough unless very granulated, and
the finer
the granulation, the bigger pain 1/ is
3/ because customizations are not only at .js level, they would be at
the macros
& scripts generating the UI level too (documents now but templates in
the
integration), for which building APIs is a bit harder (there is no way
to
override a macro in velo iirc) and, again, "plugin system of some sort"
sounds a
bit too much and chances are it won't be enough.
Actually .js can be handled, to some extent, using events. And we can consider that we ignore 'the html
issue' since it can all be
modified
from js provided that appropriate handlers can be registered.
What is the 'HTML issue' ? I don't understand what you mean by that.
Jerome.
I don't like the second part that much though.
Thanks,
Anca
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
>
> However, for the moment (2.3M1), that's quite a bit of refactoring
> (the
> integration) which i'm not willing to do.
>
> So for M1 it would be either:
>
> 1/ all in xar (js, css, script documents with annotation forms)
If it's only for M1 as a path to have the feature integrated in
templates
and resources, it means you are creating yourself a challenge for the
migration path (you will need to find a way to delete or ignore the
always-loaded SX from the wiki if at some point the make their ways
into
the core).
That's a good point. Is it an option to have good release notes from M1
to M2
and RCs and having it done nice for final?
can the migration be handled with good release notes between milestones
and RCs?
(as in I agree this would be a mess for a final, but milestones have a
different
status...)
Thanks,
Anca
> 2/ js& css in resources, script documents with annotation forms&
> other
> scripted UI in .xar
What does form and scripted UI means ? They are scripts that generated
HTML loaded by AJAX in the pages ? (for example in the docExtra tabs ?)
Or
is it something else ?
yes, that's what it means: the docExtra tab, all the annotation forms
(create,
edit, display, etc) are html fetched with ajax from generating scripts
in xwiki
docs ftm, none is created from javascript, for customizability purposes.
>
> My vote goes for 1/ since it's less mess.
0
Jerome.
>
> WDYT?
>
>>
>> Thanks
>> -Vincent
>>
>>>
>>> Jerome.
>>>
>>>
>>>
>>>>
>>>> Anca
>>>>
>>>>>
>>>>> Jerome.
>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Anca
>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> -Vincent
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
22 Mar
22 Mar
1:44 p.m.
I see Annotations and ColorThemes improvements have been committed,
I'd like to perform the 2.3M1 release ASAP.
WDYT about tomorrow afternoon or the day after tomorrow ?
Thanks,
JV.
On Mon, Mar 15, 2010 at 11:15 AM, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
The other problem is that we don't have what we had imagined would go in 2.3M1 (color
theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
So I'd suggest the following:
* Delay by a few days in order to be able to include:
- color theme improvement. Sergiu you need to tell us if that's doable and for when.
- captcha on comments. Caleb, let us know if that's all done or if there's need
for more testing/development.
Bonus:
- Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:56 p.m.
On Mar 22, 2010, at 1:44 PM, Jean-Vincent Drean wrote:
I see Annotations and ColorThemes improvements have
been committed,
I'd like to perform the 2.3M1 release ASAP.
WDYT about tomorrow afternoon or the day after tomorrow ?
+1 from me if Anca can fix these 3 problems before then:
- Blacklist AnnotationCode space
- Fix velocity errors in console
- Fix problem in annotating headers on home page
Thanks
-Vincent
Thanks,
JV.
On Mon, Mar 15, 2010 at 11:15 AM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi,
>
> We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
>
> The other problem is that we don't have what we had imagined would go in 2.3M1
(color theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
>
> So I'd suggest the following:
> * Delay by a few days in order to be able to include:
> - color theme improvement. Sergiu you need to tell us if that's doable and for
when.
> - captcha on comments. Caleb, let us know if that's all done or if there's
need for more testing/development.
>
> Bonus:
> - Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
>
> Thanks
> -Vincent
5:31 p.m.
Hi Vincent, all
On 03/22/2010 05:56 PM, Vincent Massol wrote:
On Mar 22, 2010, at 1:44 PM, Jean-Vincent Drean wrote:
Shouldn't take too long
I see Annotations and ColorThemes improvements
have been committed,
I'd like to perform the 2.3M1 release ASAP.
WDYT about tomorrow afternoon or the day after tomorrow ?
+1 from me if Anca can fix these 3 problems before then:
- Blacklist AnnotationCode space
- Fix velocity errors in console - Fix problem in annotating headers on home page
On it now, found it, writing tests and fixing it.
I'll try to be done with all these by tonight and I'm fine with the release
anytime after this moment.
Happy hacking,
Anca
Thanks
-Vincent
Thanks,
JV.
On Mon, Mar 15, 2010 at 11:15 AM, Vincent Massol<vincent(a)massol.net> wrote:
> Hi,
>
> We've slipped badly for the 2.3M1 release (my fault for not monitoring it closely
enough). It was planned on the 8th of March and we're the 15th already (one week
delay).
>
> The other problem is that we don't have what we had imagined would go in 2.3M1
(color theme improvement for ex). Right now there are lots of changes but nothing really
user-noticeable.
>
> So I'd suggest the following:
> * Delay by a few days in order to be able to include:
> - color theme improvement. Sergiu you need to tell us if that's doable and for
when.
> - captcha on comments. Caleb, let us know if that's all done or if there's
need for more testing/development.
>
> Bonus:
> - Anca, will it be possible to have annotations released for 2.3M1 (ie now)? How much
more time would you need?
>
> Thanks
> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5295
days inactive
5302
days old
21 comments
7 participants
participants (7)
-
Anca Luca -
Caleb James DeLisle -
Guillaume Lerouge -
Jean-Vincent Drean -
Jerome Velociter -
Sergiu Dumitriu -
Vincent Massol