Hi,
We have the need to handle optional Transformations (for Annotations
and more generally for user-introduced annotations).
Here's what Thomas and I are proposing:
1) We remove the TransformationManager component from the Rendering
module (public API). This means that calling code must lookup
Transformations directly.
2) We modify the Converter interface in the Rendering module in 2 ways:
- add a new signature that takes a list of Transformation as parameter
- modify the implementation for the signature that take no
Transformation params so that no Transformations are executed when
it's used (API breakage)
3) We add a XWiki configuration parameter in xwiki.properties to list
the transformations that must be executed (it's a list of component
hints) when a document is rendered. If this config param is not
defined then the default value will contain the Macro Transformation.
4) We introduce a new module called xwiki-presentation which will
contain code to handle XWiki Presentation stuff. For example:
- template handling
- displayers (document displayer, object displayers, etc)
- display configuration
- more to be defined but related to presentation
The idea would be to move stuff that is currently in XWiki/
XWikiDocument related to presentation there (for example
XWikiDocument.getRenderedContent could be replaced by
DocumentDisplayer.display(DocumentName, Syntax, Writer output) - to be
defined later).
5) In order to allow modules to not depend on xwiki-core we introduce
PresentationConfiguration in the new xwiki-presentation module defined
in 4) with a getViewTransformations() method corresponding to a
"presentation.viewTransformations" configuration parameter.
6) We introduce a new TransformationContext class similar to
MacroTransformationContext and modify the Transformation API to:
void transform(XDOM, TransformationContext) (instead of XDOM dom,
Syntax syntax)).
TransformationContext would contain 2 type of data:
- the syntax
- the list of transformations being executed (this is required by some
Macros. For ex the HTML macro needs it and other may need it too)
7) We remove the getPriority() method from the Transformation interface
8) We modify calling code: WYSIWYG, XMLRPC, etc to use the new
Converter API and to lookup PresentationConfiguration to get access to
the list of view transformations to be executed.
Here's my +1
Thanks
-Vincent
PS: A long and complex mail... sorry about that...
Hi devs,
I would like to reorg a little rendering submodule on svn/maven to have:
xwiki-rendering
- xwiki-rendering-syntaxes
-- xwiki-rendering-syntax-wikimodel
-- xwiki-rendering-syntax-xml
instead of the current
xwiki-rendering
- xwiki-rendering-parsers
-- xwiki-rendering-parser-wikimodel
-- xwiki-rendering-parser-xml
- xwiki-rendering-renderers
-- xwiki-rendering-renderer-wikimodel
-- xwiki-rendering-renderer-xml
Because parsers and renderer for a same syntax usually share
informations and are synchronized.
Here is my +1
--
Thomas Mortagne
Hi devs,
I want to add two new methods to the xml-rpc api:
- String getRenderedContent(String token, String pageId, String syntaxId);
- String getRenderedContent(String token, String pageId, String content,
String syntaxId);
Currently we are only able to get xhtml/1.0 output by using getPage and
accesing page.Content from the methods output. We need this new methods
to get the output in different syntaxes(Eg: annotatedxhtml). This is
useful to parse the output for macros, images and links like we do in
the wysiwyg.
I'd like the code to go in the 2.0.4 release. The old method invocation
required different method names. Since we don't have the xml-rpc cleanup
in 2.0.4 we probably need to have different naming for the methods
above. Since starting with 2.1 we use the Apache Xml-Rpc method lookup
and invocation, we might be able to use the same name and different
signature in the future. I'll need to check this.
WDYT?
Thanks,
Florin Ciubotaru
For Hibernate.cfg.xml it is ok but when i upgrade from 1.9.3 to 2.0.3 I got a crash when I copied the entire xwiki.cfg.
Regarding my script modifications :
I change in login.vm (in colibri skin) the message regarding the forgotten message like follow :
## TODO: Replace this with an interface extension once IX are implemented
#if($xwiki.exists("XWiki.ResetPassword"))
## <div style="font-size: 70%; margin-top: 2em;">Forgot your <a href="$xwiki.getURL('XWiki.ForgotUsername')">username</a> or <a href="$xwiki.getURL('XWiki.ResetPassword')">password</a>?</div>
<div style="font-size: 70%;font-style:bold;color:#005A83; margin-top: 2em;">To connect, use your Network Id and password.</div>
#end
In a future, I hope to implement SSO...and then avoid such modification ;-)
Cyril
-----Message d'origine-----
De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Vincent Massol
Envoyé : mercredi 25 novembre 2009 12:23
À : XWiki Developers
Objet : Re: [xwiki-devs] Automatic update
On Nov 25, 2009, at 12:10 PM, MOUZELER Cyril wrote:
> Currently this is my process:
>
> 1. download the XEM war
> 2. unzip the file into my jetyt/webapps folder 3. configure
> hibernate.cfg.xml
This one is not needed. You can simply reuse your existing config file.
> 4. in the xwiki.cfg set the ldap part(server, user, group), the stat
> part, virtual part, lucene part
Again this one is not needed you can reuse your existing file.
> 5. in the xwiki.properties set OpenOffice part
Same as above.
> 6. in the xwiki itself , set the Alias for default name, the smtp
> server.
Again not needed. You just need to not import XWikiPreferences. Or are you talking about another page?
> 7. adjust some skins modifications, script modifications.
Any details on these?
> Several times I tryed to copy directly the file but I got a crash
> (some properties in hybernate file change, new properties definition
> in the xwiki.cfg...).
hmm... What you could do is a diff between your version and the new version. In general whatever new config param we add has a default value that is similar to the old behavior so it shouldn't change anything.
Personally I'd like to move all config files in a .xwiki directory in your user directory so that upgrades don't require you to remember to save your config and put it back.
> Points 4 to 7 consume time.
> I understand that the automatic process is complex (for example to
> change the script...) I will have a look on the ExtensionManager.
IMO the only real hard part is the upgrade of the XAR (ie the wiki pages). To reduce this burden you should try to not change pages packaged in the default XAR and instead create new pages. This will prevent you from overwriting changes. There's also a list of page you should not upgrade, listed in the Installation guide.
It's for the XAR upgrade that we'd like to have the Extension Manager in the future.
Thanks
-Vincent
> Thx for your answer !
>
> Cyril
>
> -----Message d'origine-----
> De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part
> de Vincent Massol Envoyé : mercredi 25 novembre 2009 11:49 À : XWiki
> Developers Objet : Re: [xwiki-devs] Automatic update
>
> Hi Cyril,
>
> On Nov 25, 2009, at 11:39 AM, MOUZELER Cyril wrote:
>
>> Hi all,
>>
>> Is it planned to develop a way to update xwiki automatically ?
>> I have installed XEM on Windows using Oracle, ActiveDirectory,
>> Exchange, Openoffice... To configure all, it takes time and it is not
>> an obvious task.
>
> Could you list the tasks that take time? (I have some idea but would
> be interested to know what you think is painful in the upgrade
> process).
>
> Note: In the future we've planned to implement an extension manager,
> see http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager
>
> Thanks
> -Vincent
>
>> That's why i am wondering if there is a way to automatically update
>> XEM without change the conf.
>>
>>
>>
>> Cyril
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
> ----------------------------------------------------------------------
> ----------
>
> This e-mail is intended only for the addressee named above. It does
> not bind the sender, except in the case of an existing written
> convention with the addressee. This e-mail may contain material that
> is confidential and privileged for the sole use of the intended
> recipient. Any review, reliance or distribution by others or
> forwarding without express permission is strictly prohibited and may
> be unlawful. If you are not the intended recipient, please contact the
> sender and delete all copies.
>
> While reasonable precautions have been taken to ensure that this e-
> mail and any attachments are free from any computer virus or similar
> defect, no liability will be accepted in that respect. Anyone
> accessing this e-mail must take their own precautions as to security
> and virus protection.
>
> KBL European Private Bankers S.A., 43 boulevard Royal L-2955
> Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
> _______________________________________________
> 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
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
Currently this is my process:
1. download the XEM war
2. unzip the file into my jetyt/webapps folder
3. configure hibernate.cfg.xml
4. in the xwiki.cfg set the ldap part(server, user, group), the stat part, virtual part, lucene part
5. in the xwiki.properties set OpenOffice part
6. in the xwiki itself , set the Alias for default name, the smtp server.
7. adjust some skins modifications, script modifications.
Several times I tryed to copy directly the file but I got a crash (some properties in hybernate file change, new properties definition in the xwiki.cfg...).
Points 4 to 7 consume time.
I understand that the automatic process is complex (for example to change the script...) I will have a look on the ExtensionManager.
Thx for your answer !
Cyril
-----Message d'origine-----
De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Vincent Massol
Envoyé : mercredi 25 novembre 2009 11:49
À : XWiki Developers
Objet : Re: [xwiki-devs] Automatic update
Hi Cyril,
On Nov 25, 2009, at 11:39 AM, MOUZELER Cyril wrote:
> Hi all,
>
> Is it planned to develop a way to update xwiki automatically ?
> I have installed XEM on Windows using Oracle, ActiveDirectory,
> Exchange, Openoffice... To configure all, it takes time and it is not
> an obvious task.
Could you list the tasks that take time? (I have some idea but would be interested to know what you think is painful in the upgrade process).
Note: In the future we've planned to implement an extension manager, see http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager
Thanks
-Vincent
> That's why i am wondering if there is a way to automatically update
> XEM without change the conf.
>
>
>
> Cyril
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
Hi all,
Is it planned to develop a way to update xwiki automatically ?
I have installed XEM on Windows using Oracle, ActiveDirectory, Exchange,
Openoffice... To configure all, it takes time and it is not an obvious
task.
That's why i am wondering if there is a way to automatically update XEM
without change the conf.
Cyril
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
Hello devs,
as a result of the cleaning of the annotations extension, I propose to move it
to the platform xwiki-plugins and the respective xwiki-applications.
The application (client) could use a little more stabilization, but I prefer to
do it when I get to the client improvements part, as presented in the last
roadmap at http://markmail.org/message/5mnfhpdf2cgqlbop (at the end of mail).
I would like to do that now since what we have now is runnable, somewhat usable,
it represents a clean, correct version of what we have in the sandbox, a "zero
point". I am starting to make improvements from here on.
WDYT?
Thanks,
Anca