- xwiki-devs@xwiki.org - lists.xwiki.org

Re: [xwiki-devs] [xwiki-notifications] r19131 - in xoffice/trunk/xword: XWikiLib/XWiki XWord

by Sergiu Dumitriu

fciubotaru (SVN) wrote: > Author: fciubotaru > Date: 2009-04-27 15:00:12 +0200 (Mon, 27 Apr 2009) > New Revision: 19131 > > + Space exstngWithUnpubPagesSpace = wiki[sp.name]; I prefer to keep away from such shorted names, as they don't provide any real benefits, but reduce readability. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
1
0 0

[xwiki-devs] [VOTE] getCurrentDocumentName method to DocumentAccessBridge

by Thomas Mortagne

Hi dev, My use case is http://jira.xwiki.org/jira/browse/XWIKI-3418 WDYT ? Here is my +1 -- Thomas Mortagne

16 years, 4 months

4
8
0 0

[xwiki-devs] Implementing pseudoversions

by Sergiu Dumitriu

Hello devs, Auto-saving the content during long edit sessions, to prevent the complete loss of data in case of browser or OS crashes, (http://jira.xwiki.org/jira/browse/XWIKI-1581) is a pretty useful feature that people have been asking for. For 1.9 there will be the possibility to enable autosave. However, the implementation is pretty basic, more of a hack on top of the current architecture: an asynchronous JavaScript calls periodically save & continue, marking the saved versions as minor and setting the version comment to "(Autosaved)". This approach has some obvious disadvantages: - A lot of minor versions are created during the editing - Cancel does not undo the changes (a revert could be done to the version at the beginning of the editing session, which creates yet another document version) ... but at least it's a start. For properly implementing this in the future, some important changes are needed. In particular, the support for pseudoversions (http://jira.xwiki.org/jira/browse/XWIKI-500). Pseudoversions are temporary versions of a document being edited, and can be seen as short-lived versioning branches, resulting in a one official version when the user finishes editing the document. These pseudoversions will be memorized in a new table, similar to the document table or the recycle bin. Along with introducing pseudoversions, several behaviors should be changed, improving the user experience. For instance: - In all editors, "Save & Continue" should become "Save draft" and should create pseudoversions that can be canceled, and "Save and View" should become simply "Save" (these texts are also much easier to understand by the user). - In class editing, properties are added in the pseudoversion, and these changes can be canceled when the user presses the "Cancel" button. (canceling property addition is not possible ATM, unless the document is reverted). - In the object editor, objects can be added in the pseudoversion, and all changes can be saved at once. These changes are pretty substantial, from the data management and user experience point of view, but I believe it is worth making the step. Please tell me what you think. Should we try to get this done before 2.0? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

3
3
0 0

[xwiki-devs] Welcoming our GSoC students

by Sergiu Dumitriu

Hello Google Summer of Code students, First of all, congratulations on your applications and your activity during the selection period, and welcome in the XWiki development team. Before guiding the accepted students to their next steps, we'd like to thank again all those who showed interest in XWiki for this Summer of Code. We had an impressive number of good applications this year, with professional approaches and interesting ideas, and it was very difficult to choose only 6. Unfortunately, some very good students, with great potential, were not accepted. So, to those interested in getting involved anyway, without Google's implication, I renew the invitation to put your ideas in practice under the guidance of the community. Even though the money will be missing, you can still take advantage of the other GSoC benefits: learning new things, gaining experience, earning recognition, etc [http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/]. If you would like to do that, please let us know by replying to this mail. For the accepted students, here are some getting started hints: Community bonding period According to the program timeline [http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding. The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you. Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/ Mentorship We prefer open mentorship. While your assigned mentor is the one officially in charge with your guidance, almost all interaction should be done 'in the open' as much as possible, on the IRC channel or on the mailing list. You should choose the communication medium according to the importance of the matters to be discussed: naturally, the less important issues are to be discussed on IRC, while the design decisions, important progress announcements and testing/feedback requests go on the list. This way, the community is informed on the evolution of your project, and other developers can come up anytime with useful ideas and suggestions. Moreover, if your mentor is hit by a bus (the bus factor [http://en.wikipedia.org/wiki/Bus_factor]), another developer can take his place with little effort. Communication Sitting alone in your room, working secretly on your project is definitely a bad approach. However, please keep in mind that too much communication can also be harmful, as it distracts the others from their own work. You need to be able to communicate just right: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced developer (or a student that fought the same problem) could quickly provide you an answer; however, do try to find the answer yourself at first. Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when building my project, and googling for a solution doesn't seem to help. Looking at the error, I think that there's a wrong setting for the assembly plugin, but nothing I tried works. Can someone please take a look?" Subscribe to the devs list (if you didn't do this already), and start monitoring the discussions. It is also recommended to subscribe to the users list, but not mandatory. The notifications list is a little too high volume and technical for the moment, but it is a great knowledge source. We have set up a wiki on the community farm for you to organize your ideas and log your progress: http://gsoc.myxwiki.org/ . Each student must register on this wiki, create and organize a space for the project, with a blog where the evolution will be described. Currently the wiki is pretty empty, but it will grow. Development process The project's lifecycle is NOT design -> implementation -> testing -> documentation. [http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/] We invite you to adopt a test driven development [http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com…] approach and to experience agile development [http://www.amazon.com/dp/0596527675/]. After the first coding week, you must have some code that works. It won't do much, of course, but it will be the seed of your project. Every functionality will be validated by tests. The code must be properly tested and commented at the time of the writing (don't think you'll do that afterwards, because in most cases you won't). We will create the proper projects in the xwiki sandbox, and we encourage you to do __at least__ weekly commits (ideally, if you are well organized, you should be able to commit code that works daily, so try to aim at daily commits). This way, the code can be properly reviewed, and any problems can be detected before they grow into something too difficult to fix. One big code blob committed at the end, no matter how good it may seem, is a failure at several levels. A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class. Next steps, in a nutshell - Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project. At the end of the community bonding period, you should have a clear vision of the project, well documented on the wiki, you should have the build infrastructure ready, and you should be pretty familiar with the existing code you will need to interact with. And, of course, you should be familiar with the community and the way we communicate. Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

13
22
0 0

Re: [xwiki-devs] [xwiki-notifications] r19122 - platform

by Sergiu Dumitriu

jvdrean (SVN) wrote: > Author: jvdrean > Date: 2009-04-27 09:25:39 +0200 (Mon, 27 Apr 2009) > New Revision: 19122 > > Added: > platform/xwiki-core/ > Log: What's this? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
1
0 0

Re: [xwiki-devs] Welcoming our GSoC students

by Anthony Rosequist

While I wasn't selected for GSoC this year, I am still interested in developing the Calendar application for XWiki. I'll have a maximum of 10 hours a week to work on it, so I might not finish it in the GSoC timeline, but hopefully I will complete it someday. :)

16 years, 4 months

3
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r19116 - platform/web/trunk/standard/src/main/webapp/templates

by Vincent Massol

On Apr 26, 2009, at 8:30 PM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-26 20:30:08 +0200 (Sun, 26 Apr 2009) > New Revision: 19116 > > Modified: > platform/web/trunk/standard/src/main/webapp/templates/exception.vm > Log: > XWIKI-3677: The "XWiki has a default limit of around 10Mb for > attached files." error message is not enclosed in a > #startmessagebox() macro > Done. Patch submitted by Chathura Prabuddha Ganegoda applied without > changes. > > > Modified: platform/web/trunk/standard/src/main/webapp/templates/ > exception.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/ > exception.vm 2009-04-26 15:27:14 UTC (rev 19115) > +++ platform/web/trunk/standard/src/main/webapp/templates/ > exception.vm 2009-04-26 18:30:08 UTC (rev 19116) > @@ -2,12 +2,11 @@ > <div class="main layoutsubsection"> > #set($message = $xwiki.parseMessage()) > #if($message) > - <center> > - <h2>$message</h2> > - <br/><br/> > - </center> > + #xwikimessageboxstart($msg.get('notice') $message) > + #xwikimessageboxend() > #else > - $msg.get("problemoccured") > + #xwikimessageboxstart($msg.get('notice') > $msg.get('problemoccured')) > + #xwikimessageboxend() [snip] btw, it's "occurred" and not "occured"... For whoever wants to fix this (always tricky to ensure all places are modified)... ;) -Vincent

16 years, 4 months

2
1
0 0

[xwiki-devs] app: browse/listen to 60+ National Public Radio Podcasts in Pre2.4 Simile Timeline

by Niels Mayer

http://nielsmayer.com/xwiki/bin/view/Timeline/NprTimeline xwiki (html+wikitext+velocity+javascript) code: http://nielsmayer.com/xwiki/bin/view/Timeline/NprTimeline?viewer=code see also http://nielsmayer.com/xwiki/bin/view/Timeline/MP3Feed2TL?viewer=code http://nielsmayer.com/xwiki/bin/view/Macros/JW-Player?viewer=code http://nielsmayer.com/xwiki/bin/view/Macros/Foobar?viewer=code Niels http://nielsmayer.com PS: I'd love to get feedback if this app doesn't work for you; or if it fails to load or display... and if so, what platform/browser/etc. Also, if you don't have Flash to play podcast audio (or its not available on your iphone) do you have java applets available, or http://silverlight.net ?

16 years, 5 months

4
5
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.8.2 and XWiki Enterprise Manager 1.6.2 Released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.8.2 and XWiki Enterprise Manager 1.6.2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This release contains 76 bugfixes and enhancements. Most of the modifications are targeting the general replacement of old 1.0 code and content by 2.0 syntax and architecture and the stabilization of XWiki. Summary of changes since XWiki Enterprise 1.8.1 : * Many WYSIWYG bugs fixed and improvements * Many 2.0 syntax bugs fixed * Many 1.0 to 2.0 conversion bugs fixed * Several XMLRPC and REST, LDAP, Blog, PDF export bugs fixed and improvements * Many bug fixes in many other places For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise182 and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM162 Thanks -The XWiki dev team

16 years, 5 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r19003 - in platform/web/trunk/standard/src/main/webapp: resources/js/xwiki resources/js/xwiki/widgets templates

by Jerome Velociter

Hi Sergiu, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-23 22:06:46 +0200 (Thu, 23 Apr 2009) > New Revision: 19003 > > Added: > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/widgets/ > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/widgets/jumpToPage.css > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/widgets/jumpToPage.js > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/widgets/modalPopup.css > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/widgets/modalPopup.js > Modified: > platform/web/trunk/standard/src/main/webapp/templates/javascript.vm > Log: > XWIKI-3694: Add a reusable ModalPopup javascript widget > Done. For a project I started to work out an integration of modalbox (http://www.wildbit.com/labs/modalbox/), also based on prototype and Scriptaculous's Effects. You can see it in action in XWiki here http://incubator.myxwiki.org/xwiki/bin/view/XWiki/ModalBox While it doesn't have the needed shortcut binding feature, the DOM part of it is pretty powerful (but still pretty lightweight) and it has rock solid browser support. It also has nice options like callbacks on after/before content loading and after/before hiding, the possibility to initialize with content already in the DOM (copying over the elements), automatic height resize based on content, etc. I propose we merge both: we still need our own options here like the keyboard shortcuts and probably more in the future, but for the box display part of it it's IMHO better we take advantage of this library: mature and from which evolution we will be able to benefit. If we agree I'll be willing to do that merge. One comment below: > > > Modified: platform/web/trunk/standard/src/main/webapp/templates/javascript.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/javascript.vm 2009-04-23 19:39:22 UTC (rev 19002) > +++ platform/web/trunk/standard/src/main/webapp/templates/javascript.vm 2009-04-23 20:06:46 UTC (rev 19003) > @@ -10,6 +10,11 @@ > ## > ## JS Libraries. > ## > +$xwiki.jsfx.use('js/scriptaculous/effects.js', true) > +$xwiki.jsfx.use('js/xwiki/widgets/modalPopup.js', true) > +$xwiki.ssfx.use('js/xwiki/widgets/modalPopup.css', true) > +$xwiki.jsfx.use('js/xwiki/widgets/jumpToPage.js', true) > +$xwiki.ssfx.use('js/xwiki/widgets/jumpToPage.css', true) > <script type="text/javascript" src="$xwiki.getSkinFile("js/prototype/prototype.js")"></script> > <script type="text/javascript" src="$xwiki.getSkinFile("js/xwiki/xwiki.js", true)"></script> > <script type="text/javascript" src="$xwiki.getSkinFile("js/xwiki/compatibility.js", true)"></script> > We should decide on which way we want to include our JS/CSS in templates. I'd say only with (js|ss)fx plugin is ok. Jerome. > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

16 years, 5 months

2
4
0 0

[xwiki-devs] XWiki Jabber, Google Talk, Skype Integration

by Tharindu Madushanka

Hi, I would like to work on this idea for my experience, I would like to come up with a GWT application and then integrate it with XWiki. As I have already planned I use these days to get familiar with GWT and XWiki more and this would be great experience for my future career as I have been mostly doing mobile application development nearly about an year now. There fore, I thought contributing to this would help me to learn a lot. And it would be a great opportunity for a student like me to contribute to such big opensource work. I would love to stay with the community and use my all available time towards this work, while doing other work. Thanks, *H.T.M. Gamage ** *Student,* * Faculty of Information Technology, University of Moratuwa, SriLanka. Mobile: +94 (71) 5518852 Blog : tharindufit.wordpress.com

16 years, 5 months

3
3
0 0

[xwiki-devs] [VOTE] Release XE 1.8.2

by Thomas Mortagne

Hi devs, I would like to release XE 1.8.2 and XEM 1.6.2. Like 1.8.1 and 1.8.3 it's a bugfixes release mainly targeting new WYSIWYG and rendering. Here is my +1 -- Thomas Mortagne

16 years, 5 months

6
6
0 0

[xwiki-devs] [GSoC] Introduction and XEclipse Navigator

by Venkatesh Nandakumar

Hi Everyone, I'd like to first thank the xwiki team for selecting my proposal. I am Venkatesh, pursuing my 4th year Undergraduate and Master's integrated computer science engineering degree at IIT Roorkee [ http://en.wikipedia.org/wiki/IIT_Roorkee], India. My main mentor would be Fabio Mancinelli. I would be working on the XEclipse Navigator, and would be concentrating on improving it. I was an intern at XWiki last year, and had worked on XEclipse then itself, and hence am quite familiar with its exisiting code. In the past 2 weeks, I've also familiarised myself with the xwiki-xmlrpc implementation. The basic features that I've decided, for now, that shall be implemented are:- 1) Drag and Drop (with possibly editor integration too) 2) State persistence of the Navigator 3) Display of attachments and translations within the navigator 4) Better integration with the workbench and editor After this is done, I would like to work on improving XEclipse as such, like a better Preferences Editor, software update bundle and more editor features ( intergrate source editors from eclipse project. Thanks, Venkatesh Nandakumar Department of Electronics & Computer Engineering Indian Institute of Technology Roorkee

16 years, 5 months

3
2
0 0

[xwiki-devs] Passing value from a select to a macro

by bruno.amaro

Hi I`m trying to figure how to do this, i`m using the excel plugin and i want to have a select box to select the sheet to display: <form id="form1" name="form1" method="post" action=""> <label> <select name="sheet" id="sheet"> <option value="03-20-2009">03-20-2009</option> <option value="03-27-09">03-27-09</option> <option value="04-03-2009">04-03-2009</option> <option value="4-10-2009" selected="selected">4-10-2009</option> </select> </label> </form> </label> <p> <label> <input type="submit" name="button" id="button" value="Submit" /> </label> </p> $xwiki.ExcelPlugin.getTable("Status.xls", "4-10-2009", "A3-H20") The "4-10-2009" should be the value from the select... Any ideas? -- View this message in context: http://n2.nabble.com/Passing-value-from-a-select-to-a-macro-tp2679860p26798… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 5 months

4
4
0 0

Re: [xwiki-devs] [xwiki-notifications] r18997 - platform/web/trunk/standard/src/main/webapp/resources/js/xwiki

by Jerome Velociter

sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-23 19:35:18 +0200 (Thu, 23 Apr 2009) > New Revision: 18997 > > Modified: > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js > Log: > [misc] Fix scripting error in IE > Thanks Sergiu ... I tend to forget about that and take DOM extensions for granted everywhere :) > > Modified: platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js 2009-04-23 17:03:21 UTC (rev 18996) > +++ platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js 2009-04-23 17:35:18 UTC (rev 18997) > @@ -255,7 +255,7 @@ > if (typeof content == "undefined") { > content = document.body; > } > - content.select(".xwikirenderingerror").each(function(error) { > + $(content).select(".xwikirenderingerror").each(function(error) { > if(error.nextSibling.innerHTML !== "" && error.nextSibling.hasClassName("xwikirenderingerrordescription")) { > error.style.cursor="pointer"; > error.title = "$msg.get('platform.core.rendering.error.readTechnicalInformation')"; > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

16 years, 5 months

1
0
0 0

Re: [xwiki-devs] Welcoming our GSoC students

by raluca.morosan＠xwiki.com

Hi Anthony, I also liked your proposal and I would be happy to help you with the HTML, CSS, Javascript and Velocity part for the Calendar application. Welcome! for all the GSoC students ;) Raluca.

16 years, 5 months

1
0
0 0

[xwiki-devs] Mail Auth patch for 1.8

by Lilianne E. Blaze

Hello, Here's the newest version. Basically it bridges XWiki.sendMessage to MailSenderPlugin. It uses Reflection, so no circulars, but it's not exactly pretty. Why it's needed - registration / validation / activation e-mails are still sent via obsolete Apache Commons SmtpClient, so they _do not_ support SMTP AUTH. This is a _major_ problem because due to spam and other abuse less and less hosting providers / network admins allow SMTP without authorization, and those who do are likely to have very insecure infrastructure. I honestly believe this is a MUST HAVE for a secure, spam-free configuration. Greetings, Lilianne Index: main/resources/XWiki/AdminGeneralSheet.xml =================================================================== --- main/resources/XWiki/AdminGeneralSheet.xml (revision 18064) +++ main/resources/XWiki/AdminGeneralSheet.xml (working copy) @@ -61,6 +61,6 @@ #set($params.language = ['multilingual', 'languages' , 'default_language', 'dateformat']) #set($params.editor = ['editor']) #set($params.admin = ['admin_email']) -#set($params.server = ['smtp_server']) +#set($params.server = ['smtp_server', 'smtp_server_username', 'smtp_server_password', 'javamail_extra_props']) #includeForm('XWiki.AdminFieldsDisplaySheet')</content> </xwikidoc> Index: main/java/com/xpn/xwiki/XWiki.java =================================================================== --- main/java/com/xpn/xwiki/XWiki.java (revision 17953) +++ main/java/com/xpn/xwiki/XWiki.java (working copy) @@ -161,6 +161,8 @@ import com.xpn.xwiki.web.XWikiURLFactoryService; import com.xpn.xwiki.web.XWikiURLFactoryServiceImpl; import com.xpn.xwiki.web.includeservletasstring.IncludeServletAsString; +import java.io.BufferedReader; +import java.io.StringReader; public class XWiki implements XWikiDocChangeNotificationInterface { @@ -2838,9 +2840,13 @@ needsUpdate |= bclass.addTextAreaField("meta", "HTTP Meta Info", 60, 8); needsUpdate |= bclass.addTextField("dateformat", "Date Format", 30); + // mail needsUpdate |= bclass.addBooleanField("use_email_verification", "Use eMail Verification", "yesno"); + needsUpdate |= bclass.addTextField("admin_email", "Admin eMail", 30); needsUpdate |= bclass.addTextField("smtp_server", "SMTP Server", 30); - needsUpdate |= bclass.addTextField("admin_email", "Admin eMail", 30); + needsUpdate |= bclass.addTextField("smtp_server_username", "SMTP Server username (optional)", 30); + needsUpdate |= bclass.addTextField("smtp_server_password", "SMTP Server password (optional)", 30); + needsUpdate |= bclass.addTextAreaField("javamail_extra_props", "Additional JavaMail properties", 60, 6); needsUpdate |= bclass.addTextAreaField("validation_email_content", "Validation eMail Content", 72, 10); needsUpdate |= bclass.addTextAreaField("confirmation_email_content", "Confirmation eMail Content", 72, 10); needsUpdate |= bclass.addTextAreaField("invitation_email_content", "Invitation eMail Content", 72, 10); @@ -3311,9 +3317,139 @@ * Plugin</a> */ @Deprecated - public void sendMessage(String sender, String[] recipient, String message, XWikiContext context) + public void sendMessage(String sender, String[] recipients, String message, XWikiContext context) throws XWikiException { + LOG.info("Entering sendMessage(...)..."); + + Object mailSender; + Class mailSenderClass; + Method mailSenderSendText; + + try + { + mailSender = getPluginApi("mailsender", context); + mailSenderClass = Class.forName("com.xpn.xwiki.plugin.mailsender.MailSenderPluginApi"); + + // public int sendTextMessage(String from, String to, String subject, String message) + mailSenderSendText = mailSenderClass.getMethod("sendTextMessage", + new Class[]{String.class, String.class, String.class, String.class}); + } + catch(Exception e) + { + String eMsg = "Problem getting MailSender via Reflection: " + e; + LOG.error(eMsg); + throw new XWikiException(XWikiException.MODULE_XWIKI_EMAIL, + XWikiException.ERROR_XWIKI_EMAIL_ERROR_SENDING_EMAIL, eMsg); + } + + LOG.trace("Message = \"" + message + "\""); + + String messageParsed[] = parseRawMessage(message); + String messageSubject = messageParsed[0]; + String messageBody = messageParsed[1]; + String messageRecipients = recipients[0]; + for( int i = 1; i < recipients.length; i++) + { + messageRecipients = messageRecipients + "," + recipients[i]; + } + + if( messageSubject == null ) + { + // TODO: provide some sensible default + messageSubject = "Message from XWiki"; + } + + LOG.trace("Subject = \"" + messageParsed[0] + "\""); + LOG.trace("Text = \"" + messageParsed[1] + "\""); + + try + { + mailSenderSendText.invoke(mailSender, sender, messageRecipients, messageSubject, messageBody); + } + catch(InvocationTargetException ite) + { + Throwable cause = ite.getCause(); + if( cause instanceof XWikiException ) + { + throw (XWikiException)cause; + } + else + { + throw new RuntimeException(cause); + } + } + catch(Exception e) + { + // probably either IllegalAccessException or IllegalArgumentException + // shouldn't happen unless there were an incompatible code change + throw new RuntimeException(e); + } + + LOG.info("Exiting sendMessage(...). It seems everything went ok."); + } + + /** + * + * @return [subject (can be null), text (never null)] + */ + public String[] parseRawMessage(String rawMessage) + { + String SUBJECT = "Subject: "; + + String messageSubject = null; + String messageText = ""; + + // sanity check + if( rawMessage == null ) + { + throw new IllegalArgumentException("rawMessage can't be null"); + } + else if( rawMessage.trim().equals("") ) + { + throw new IllegalArgumentException("rawMessage can't be empty"); + } + + try + { + StringReader sr = new StringReader(rawMessage); + BufferedReader br = new BufferedReader(sr); + String line; + + StringWriter sw = new StringWriter(); + PrintWriter pw = new PrintWriter(sw); + + line = br.readLine(); + if( line.startsWith(SUBJECT) ) + { + messageSubject = line.substring(SUBJECT.length()); + line = br.readLine(); + if( !line.trim().equals("") ) + { + pw.println(line); + } + } + + while( (line = br.readLine()) != null ) + { + pw.println(line); + } + + messageText = sw.toString(); + } + catch(IOException ioe) + { + // can't happen here + } + + return new String[]{messageSubject, messageText}; + } + + + @Deprecated + public void sendMessageOld(String sender, String[] recipient, String message, XWikiContext context) + throws XWikiException + { SMTPClient smtpc = null; try { String server = getXWikiPreference("smtp_server", context); Index: main/resources/ApplicationResources.properties =================================================================== --- main/resources/ApplicationResources.properties (revision 17953) +++ main/resources/ApplicationResources.properties (working copy) @@ -181,6 +181,9 @@ use_email_verification=Use email verification admin_email=Admin email smtp_server=Outgoing SMTP Server +smtp_server_username=SMTP Server Username (optional) +smtp_server_password=SMTP Server Password (optional) +javamail_extra_props=Additional JavaMail properties validation_email_content=Validation e-Mail Content confirmation_email_content=Confirmation e-Mail Content preferences=Preferences

16 years, 5 months

5
11
0 0

[xwiki-devs] Passing value from a select to a macro

by Bruno Amaro Almeida - cubiX

Hi I`m trying to figure how to do this, i`m using the excel plugin and i want to have a select box to select the sheet to display: <form id="form1" name="form1" method="post" action=""> <label> <select name="sheet" id="sheet"> <option value="03-20-2009">03-20-2009</option> <option value="03-27-09">03-27-09</option> <option value="04-03-2009">04-03-2009</option> <option value="4-10-2009" selected="selected">4-10-2009</option> </select> </label> </form> </label> <p> <label> <input type="submit" name="button" id="button" value="Submit" /> </label> </p> $xwiki.ExcelPlugin.getTable("Status.xls", "4-10-2009", "A3-H20") The "4-10-2009" should be the value from the select... Any ideas?

16 years, 5 months

1
0
0 0

[xwiki-devs] Passing value from a select to a macro

by Bruno Amaro Almeida - cubiX

Hi I`m trying to figure how to do this, i`m using the excel plugin and i want to have a select box to select the sheet to display: <form id="form1" name="form1" method="post" action=""> <label> <select name="sheet" id="sheet"> <option value="03-20-2009">03-20-2009</option> <option value="03-27-09">03-27-09</option> <option value="04-03-2009">04-03-2009</option> <option value="4-10-2009" selected="selected">4-10-2009</option> </select> </label> </form> </label> <p> <label> <input type="submit" name="button" id="button" value="Submit" /> </label> </p> $xwiki.ExcelPlugin.getTable("Status.xls", "4-10-2009", "A3-H20") The "4-10-2009" should be the value from the select... Any ideas?

16 years, 5 months

1
0
0 0

Re: [xwiki-devs] Welcoming our GSoC students

by Cristina Scheau

Hello everybody! My name is Cristina Scheau (cristinaS from IRC). I will work on "XWiki Integration with OpenOffice", mentored by Sergiu Dumitriu. My actual design page is : <http://dev.xwiki.org/xwiki/bin/view/Design/XWikiIntegrationWithOpenOffice> http://dev.xwiki.org/xwiki/bin/view/Design/XWikiIntegrationWithOpenOffice It will be improved. If someone has suggestions about it, please let me know. The project will be an Open Office extension. In a nutshell, my action plan is: 1. Doing some research about the OpenOffice SDK API 2. Discussing with the community about the software archtecture 3. Developing a GUI for XOO extension 4. Implementing a wizard for connecting to a XWiki server and a xwiki navigational panel 5. Implementing the core classes that will be used in the future development 6. Implementing the functionalities: edit existing XWiki pages and add new XWiki pages from OpenOffice 7. Implementing the functionalities: download and upload attachments 8. Implementing : editing attachments supported by Open Office 9. Refining the GUI and adding new small functionalities 10. Improving the project using the feedback from the users. Thank you very much for accepting me! Have a great day, Cristina On Wed, Apr 22, 2009 at 1:40 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > Hello Google Summer of Code students, > > First of all, congratulations on your applications and your activity during > the selection period, and welcome in the XWiki development team. > > Before guiding the accepted students to their next steps, we'd like to > thank again all those who showed interest in XWiki for this Summer of Code. > We had an impressive number of good applications this year, with > professional approaches and interesting ideas, and it was very difficult to > choose only 6. Unfortunately, some very good students, with great potential, > were not accepted. So, to those interested in getting involved anyway, > without Google's implication, I renew the invitation to put your ideas in > practice under the guidance of the community. Even though the money will be > missing, you can still take advantage of the other GSoC benefits: learning > new things, gaining experience, earning recognition, etc [ > http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/]. > If you would like to do that, please let us know by replying to this mail. > > For the accepted students, here are some getting started hints: > > > Community bonding period > > According to the program timeline [ > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], > the next month (April 20th - May 23rd) is to be used for community bonding. > > The first thing to do, sometime this week, is to present yourself and your > project on the dev list, so that everyone knows who you are and what to > expect from you. > > Also, you should continue getting acquainted with the code, the practices > and the developers. Please make sure you all read and understand the > following - very useful - documents: > - http://purl.org/xwiki/community/ > - http://purl.org/xwiki/dev/ > - http://platform.xwiki.org/xwiki/bin/view/Features/ > > > Mentorship > > We prefer open mentorship. While your assigned mentor is the one officially > in charge with your guidance, almost all interaction should be done 'in the > open' as much as possible, on the IRC channel or on the mailing list. You > should choose the communication medium according to the importance of the > matters to be discussed: naturally, the less important issues are to be > discussed on IRC, while the design decisions, important progress > announcements and testing/feedback requests go on the list. This way, the > community is informed on the evolution of your project, and other developers > can come up anytime with useful ideas and suggestions. Moreover, if your > mentor is hit by a bus (the bus factor [ > http://en.wikipedia.org/wiki/Bus_factor]<http://en.wikipedia.org/wiki/Bus_factor%5D>), > another developer can take his place with little effort. > > > Communication > > Sitting alone in your room, working secretly on your project is definitely > a bad approach. However, please keep in mind that too much communication can > also be harmful, as it distracts the others from their own work. You need to > be able to communicate just right: > - provide meaningful information about your progress, > - ask the community's opinion on non-trivial design or implementation > decisions > - avoid waisting a lot of time on a problem, when a more experienced > developer (or a student that fought the same problem) could quickly provide > you an answer; however, do try to find the answer yourself at first. > > Wrong: "Where do I start? What do I do now? And how do I do that? Is this > good? It doesn't work, help me!" > Right: "Since a couple of hours ago I get a strange exception when building > my project, and googling for a solution doesn't seem to help. Looking at the > error, I think that there's a wrong setting for the assembly plugin, but > nothing I tried works. Can someone please take a look?" > > Subscribe to the devs list (if you didn't do this already), and start > monitoring the discussions. It is also recommended to subscribe to the users > list, but not mandatory. The notifications list is a little too high volume > and technical for the moment, but it is a great knowledge source. > > We have set up a wiki on the community farm for you to organize your ideas > and log your progress: http://gsoc.myxwiki.org/ . Each student must > register on this wiki, create and organize a space for the project, with a > blog where the evolution will be described. Currently the wiki is pretty > empty, but it will grow. > > > Development process > > The project's lifecycle is NOT design -> implementation -> testing -> > documentation. [ > http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/] > > We invite you to adopt a test driven development [ > http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com…<http://en.wikipedia.org/wiki/Test-driven_development%5D%5Bhttp://www.amazon…>] > approach and to experience agile development [ > http://www.amazon.com/dp/0596527675/]. After the first coding week, you > must have some code that works. It won't do much, of course, but it will be > the seed of your project. Every functionality will be validated by tests. > The code must be properly tested and commented at the time of the writing > (don't think you'll do that afterwards, because in most cases you won't). > > We will create the proper projects in the xwiki sandbox, and we encourage > you to do __at least__ weekly commits (ideally, if you are well organized, > you should be able to commit code that works daily, so try to aim at daily > commits). This way, the code can be properly reviewed, and any problems can > be detected before they grow into something too difficult to fix. One big > code blob committed at the end, no matter how good it may seem, is a failure > at several levels. > > A simple way of having something functional in the first week is to prepare > the maven build, which will give you the first unit test for the first > class. > > > Next steps, in a nutshell > > - Get more familiar with the code and development process and try to master > Maven, JUnit, Selenium, component driven development, ... > - Continue fixing a few small issues, chosen so that they are __related to > your project__ -- This will help you get more familiar with the code your > project needs to interact with. > - Refine and organize the ideas concerning your project (use the wiki), and > write several use case scenarios. > - Start writing the first piece of code for your project. > > At the end of the community bonding period, you should have a clear vision > of the project, well documented on the wiki, you should have the build > infrastructure ready, and you should be pretty familiar with the existing > code you will need to interact with. And, of course, you should be familiar > with the community and the way we communicate. > > Good luck, and may we all have a great Summer of Code! > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ >

16 years, 5 months

2
2
0 0

[xwiki-devs] How to handle XHTML output for semantic properties?

by Vincent Massol

Hi, I'm implementing semantic properties in XWiki Syntax 2.0 http://jira.xwiki.org/jira/browse/XWIKI-3320 I've done the wikimodel part and I'm now wondering how what XHTML we should generate in the XHTML renderer (and thus what XHTML should the wysiwyg handle). Here's an example input: %%property1 ((( %%property2 **value2** %%property3 value3 ))) Right now one solution I've found is to serialize the property content in xwiki syntax 2.0 and output it as a comment in the XHTML renderer:  (note: we could have  instead of start/stopproperty, that's a detail) Then the XHTML parser would use the xwiki syntax 2.0 parser on the content of the comment to generate events. Since it's not very trivial to serialize to xwiki syntax in the XHTML renderer I'd like to know what you think or if you have a better idea. I guess we could also do something like: <div class="'xwiki-semantic property1"> <div class="xwiki-semantic property2> <p> <strong>value2</strong> </p> </div> <div class="xwiki-semantic property3"> <p> value3 </p> </div> </div> Note: we would use span for inline semantic properties instead of divs. And then have a CSS with display:none for ".xwiki-semantic" The advantage of this latter solution are: * Easier to implement for the XHTML renderer and XHTML parser * Is in line with HCARD if we want to support it (and we probably do), see http://jira.xwiki.org/jira/browse/XWIKI-3320?focusedCommentId=39554&page=co… WDYT? Thanks -Vincent

16 years, 5 months

5
6
0 0

[xwiki-devs] Does DB2 support virtual wiki?

by Norbert Xie

Hi, I am new to XWiki. I was trying to set up virtual wiki using DB2 v9.1 or v9.5. First I installed XWiki Enterprise Manager on Tomcat and set up DB2 following the "Installation DB2" guide. After that I tried to create virtual wikis using XEM. But when I clicked "Create new wiki" link in the XWiki Enterprise Manager and enter "wikitest" as wiki identifier, it kept prompting that "A database with this identifier already exists". But the fact is that I don't have a database named "wikitest" on my DB2. Then I found out that no matter what I typed in the wiki identifier text box, it all prompted "A database with this identifier already exists". This prevents me from creating a virtual wiki. Can anyone help me out? Thanks very much in advance! BTW, I can successfully create virtual wikis on MySQL and access them.

16 years, 5 months

2
2
0 0

[xwiki-devs] [Proposal] - Behavior of the enter key in the new WYSIWYG editor

by Guillaume Lerouge

Hi devs, right now we need to hit enter twice in a row to create a new paragraph. Although I strongly pushed this implementation back in the day, it is proving to be counter-intuitive for almost all users. After a review of a number of other tools (including OpenOffice & online text editors) & reading of posts on the topic, I came to the conclusion that we'd better come back to the previous behavior for the enter key: - Hitting enter once creates a new paragraph - Hitting caps + enter creates a new line in the same paragraph When writing, users tend to write a number of sentences (most of the time between 3 and 7 of them) and then hit enter to create a new paragraph. The issue sometimes encountered is that an user writes a single line, then hits enter to find out that a lot of spacing is entered between both lines. This issue can easily be fixed through CSS in the default XWiki Enterprise distribution (we could use OOo as a source of inspiration for the respective line heights between 2 lines & 2 paragraphs - right now I'd say the height between 2 paragraphs is a bit too big). Additionally, this would "fix" the "issue" currently encountered by users when they input 2 lines and try to make one of them a title: - User inputs line of text, hits enter, inputs 2nd line - User puts caret at the end of first line and selects "Title 1" - Both lines are turned into a title -> weird This behavior is unexpected from an end-user point of view and would be fixed by coming back to the previousbehavior for the enter key. WDYT? Guillaume PS: I'm really sorry about the additional work incurred by my initial lack of understanding of the role of paragraphs -- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://guillaumelerouge.com/

16 years, 5 months

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r18914 - platform/web/trunk/xwiki-gwt-dom/src/main/java/org/xwiki/gwt/dom/client

by Sergiu Dumitriu

mflorea (SVN) wrote: > Author: mflorea > Date: 2009-04-21 18:38:10 +0200 (Tue, 21 Apr 2009) > New Revision: 18914 > > Modified: > platform/web/trunk/xwiki-gwt-dom/src/main/java/org/xwiki/gwt/dom/client/Style.java > Log: > XWIKI-3442: Review the font plugin > * Added the font-size property > > > Modified: platform/web/trunk/xwiki-gwt-dom/src/main/java/org/xwiki/gwt/dom/client/Style.java > =================================================================== > --- platform/web/trunk/xwiki-gwt-dom/src/main/java/org/xwiki/gwt/dom/client/Style.java 2009-04-21 16:35:19 UTC (rev 18913) > +++ platform/web/trunk/xwiki-gwt-dom/src/main/java/org/xwiki/gwt/dom/client/Style.java 2009-04-21 16:38:10 UTC (rev 18914) > @@ -86,6 +86,11 @@ > /** > + * The font-size property sets the size of a font. > + */ > + public static final class FontSize > + { > + /** > + * Default value. > + */ > + public static final String MEDIUM = "medium"; Can GWT code use java5 enums? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 5 months

2
1
0 0

[xwiki-devs] [Proposal] Introduce new Raw event/block in rendering to replace the current XML events/blocks

by Vincent Massol

Hi, We've had an interesting discussion with Thomas about the need to introduce a new onRawText() event in the rendering module to replace the current begin/endXML() events. Here's the need (discovered by Ludovic): * In some cases we want to inject rendered content directly in the renderer's output. For example there are some cases where we want to inject HTML directly (in order to bypass parsing) What we propose: * Remove the current XML events * Add a onRawText(Syntax syntax) event and a corresponding RawBlock block. A raw text is text injected directly in the rendered output without any parsing/modification. Note that the content depends completely on the rendered used hence the Syntax parameter. * Add a new {{raw syntax="syntaxId"}} macro so that users can inject content in the few cases where it's needed * Modify the HTML Macro to use RawBlock blocks instead of XMLBlock. Also add a new "clean=true|false" parameter (defaut is to clean). When clean = true, we pass the content to the HTML cleaner. <Implementation note>We still need to parse the content when wiki=true. We generate RawBlock blocks when we have startElement/ endElement/CDATA/Comment xml parser events.</Implementation note> This solves a number of issues: * We have a generic way to inject rendered content directly for the special cases when it's needed (ex: the user really wants to inject invalid HTML such as META tags in the body content) * We remove the XML events which were a bit weird to have in the first place. Note that we'll probably need to add some new events in the future such as one for demarcating a set of blocks (which would translate in DIV or SPAN in the XHTML renderer for example). This is needed for example for the Box Macro which is currently using XMLBlock but that's not completely correct. WDYT? Thanks -Vincent

16 years, 5 months

3
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs