(resending since I got a failure from xwiki's mail content filter )
---------- Forwarded message ----------
From: Vincent Massol <vincent(a)massol.net>
Date: Sun, Jul 26, 2009 at 11:33 AM
Subject: [Wiki Importer] Design questions
To: XWiki Developers <devs(a)xwiki.org>
Hi Arun,
I've just started reviewing your module. I'll send questions as they
come. Here are some to start with:
1) Why do you need the Wiki interface? Since all implementations are
wiki-specific and since it doesn't contain any useful method I don't
see why it's needed.
2) Why do you need 2 methods in WikiImporter interface? I would have
imagine only a single method:
WikiImporter.import(...)
3) Why do you pass a byte array instead of a stream? If the import is
large a byte array will result in an OOM error.
4) WikiImporterVelocityContextInitializer has invalid javadoc. In
addition instead of exposing each importer you could expose only a
single importer factory and pass an import syntax to it. This will
reduce the coupling and not expose the implementations to the client
side (very important). Something like:
WikiImporterFactory.createImporter(ImportSyntax).
5) This should never be written (in DefaultImportWikiParser &
DefaultImportWikiRenderer for ex):
//Intialize Embeddable Component Manager
EmbeddableComponentManager ecm = new EmbeddableComponentManager();
ecm.initialize(this.getClass().getClassLoader());
The component manager must alway be passed as a dependency.
6) You shouldn't use @Component("default") but instead @Component
7) You should never use new
File(System.getProperty("java.io.tmpdir"). Instead you should use the
existing API located in
Container.getApplicationContext().getTemporaryDirectory().
I have some more comments but since they are linked to the above let's
agree first on the points above before going further.
Thanks
-Vincent
Hi Devs,
Currently on a multi-xwiki installation all the xwikis can manipulate the OO
server instance shared between them. I think it makes more sense to allow
only the primary xwiki to control the oo server while rest of the xwikis
become observers / consumers.
WDYT?
Here is my +1.
Thanks.
- Asiri
+1
-----Message d'origine-----
De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Asiri Rathnayake
Envoyé : mercredi 29 juillet 2009 11:52
À : XWiki Developers
Objet : [xwiki-devs] [PROPOSAL] Restrict OO server administration to mainxwiki
Hi Devs,
Currently on a multi-xwiki installation all the xwikis can manipulate the OO
server instance shared between them. I think it makes more sense to allow
only the primary xwiki to control the oo server while rest of the xwikis
become observers / consumers.
WDYT?
Here is my +1.
Thanks.
- Asiri
_______________________________________________
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
In case nobody ran into this so far I just wanted to make sure everybody knows that 3827:
http://jira.xwiki.org/jira/browse/XWIKI-3827
is still or again broken in 1.9.2. The fix from David mentioned at the end of the comments did do the trick for me:
wiki/resources/js/xwiki/wysiwyg/xwe/stylesheets/RichTextArea.css:
change: background-image: none;
to: background-image: none !important;
I cannot change the status of this JIRA report to reopen it so please could someone do it or just apply the fix.
Thanks
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Here I go. My own public blog is now upgraded to 2.0 Syntax using the attached XAR file. The entry discusses the other changes that needed to be done in order to make it work well:
http://madplanet.com/xwiki/bin/view/Blog/
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
On Monday, July 27, 2009, at 05:13PM, "Andreas Schaefer" <schaefera(a)me.com> wrote:
>Sorry but I forgot to mention the JIRA report I attached the draft to:
>
>http://jira.xwiki.org/jira/browse/XABLOG-50
>
>Cheers - Andy
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
>
Hi
Currently our company is using Magnolia (magnolia.info) as the CMS for our website. Because our website is not very dynamic, big or complex using Magnolia is often a little bit of an overkill and keeping it up to date is not easy. So I was wondering if I could use XWiki to create a simple application that would enable the creation and maintenance of a website.
Today the Blog is a list of Blog Document building up the blog page. Breaking up the page into a header, left and right side bar (or using the panels) and columns for the content it should be possible to define a web page. The parts of a page a defined by classes and the content is provided by objects. The application just provides the code that displays the web site and additional elements to create, edit and remove parts of the document (paragraphs) when the user is in edit mode.
The application would provide a simple web site but also the framework to create a custom web site by extending the application.
What do you think?
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Hi fellow XWikiers,
While celebrating XWiki's 5th birthday last week, we spent a couple days
brainstorming with the full team about where XWiki stands today and what its
future holds. We came up with a long list of features and ideas and we'd
love to get community feedback before deciding in which direction we're
going to move forward once our 2.0 release is out.
To this aim, we've built a survey that we'd like our users and developers to
take. It's a bit long though definitely worth the pain. We're eagerly
waiting for your feedback to start working on new and existing features.
You can access and fill the survey at the following address:
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures
Thanks a lot for your time,
Guillaume on behalf of the XWiki Team
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
XWiki had always had some nice feedback about its interface. But things are
not that honey pink, we have many inconsistencies in our user interface,
some of them caused by the fact that we're developing in an open source
environment.
Our goal is to improve the user experience of XWiki and we'd like you to get
involved. We need to improve the usability of the XWiki platform and we
would be very happy if the community got involved in helping us making this
happen.
All the decisions we make directly imply and affect our community which is
why we're eager to get your feedback before we start working further on
these topics.
- We would like to know what are your main usability problems when using
XWiki - we badly want to fix them ;-)
- We would be super-happy to receive bold and creative ideas that we
might be able to incorporate into XWiki's look and feel.
Want to get involved? Yay! We’d love to have you aboard! It doesn't matter
whether you're a developer who’s interested in participating, an UX person
or someone with an eye for design as long as you come up with great ideas.
You can add your mockups and videos to our Flickr group
http://www.flickr.com/groups/xwikiux/ or to our Vimeo group
http://www.vimeo.com/groups/xwikiux . These groups can be used to show off
your ideas or just to point the problems you had using XWiki.
Let’s make XWiki amazing !!