I'm proposing to have another point release for XE 1.8.x called 1.8.3.
XE 1.8.2 is planned for the 20th of April and I propose to plan 1.8.3
for two weeks after, i.e. 4th of May.
As usual the goal is to include important bug fixes. The reason I
think we need a 1.8.3 is because we're starting to get feedback from
our new wysiwyg/new rendering and we need to bring bug fixes as fast
as possible to our users without forcing them to wait for 1.9 final.
Here's my +1
Thanks
-Vincent
Hi Devs,
Jodconverter 3.0-beta-2 version has been released:
http://groups.google.com/group/jodconverter/browse_thread/thread/8b73b26b70…
One of the most important fix for us is the first point mentioned there:
"OOo is now started with -nofirststartwizard by default. This avoids the
frequent problem of OOo refusing to work on a new machine because it's
expecting somebody to accept its license dialogue even in -headless mode"
Without this fix currently we have to copy an already initialized ooprofile
directory to the destination server and point to it from xwiki.properties
file. This is a pain.
Also there are several other enhancements:
http://code.google.com/p/jodconverter/issues/list?can=1&q=label%3ATarget-3.…
Unfortunately some of the public APIs of jodconverter has been changed from
beta-1 release to beta-2 release. But still, upgrading our officeimporter
module to use this new jodconverter release will not require that much of
code changes.
Note: jodconverter is not available in any public maven repository AFAIK. So
we need to release it to our externals repository as we did with the beta-1
version.
The other feature is a frequently requested one (auto-strart) and admins are
having a hard time without this feature :)
Here is my +1 for both features.
Thanks.
- Asiri
Hi devs,
We have (at least) two issues about links inside links:
http://jira.xwiki.org/jira/browse/XWIKI-3149 and
http://jira.xwiki.org/jira/browse/XWIKI-3440
Basically the issue is that XHTML does not support links inside links.
To fix this I see two possibilities:
1) valid in XDOM: this means XHTML renderer has to take care of this
and skip link inside links
2) not valid in XDOM: this means each parser has to make sure not put
link inside links in the XDOM
+1 for 1) and -0 for 2) since it's a XHTML issue only and we could
have some use cases supporting this like XWiki syntax support it.
Thanks,
--
Thomas Mortagne
Hai Ludovic.
I liked to continue the survey application project even if I not selected to
GSOC. If you give me a chance I can show my commitment to the Xwiki.
If I'm on the project. I would like to know about the following points.
1. Ideas that need to change in my application.
2. How the milestone plan should be adjusted based on the above ideas
complexity.
3. Changes that need to be done with the mockups that I had created.
Its better if I can have a mentor who can guide me to this target.
Also I would like to thank all the community members of the Xwiki. I
gathered lots of experience to my life during past month.This is my first
FOSS community involvement. If something went wrong from me please forgive
me. I don't want to loose this connections that I had build with those great
people.
So
Good luck Xwiki...
Thank you...
--
~ Chathura Prabuddha Ganegoda~
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa,
Sri Lanka.
http://gacpganegoda.blogspot.com/
Hi,
I have been looking at how to notify when an event has been finished. Here
what I have currently understood and I got some confusion.
In order to get notified when login event finished, I think I have to do the
following things.
1. Create a LoginListener class that implements EventListener
2. Create object of DefaultObservationManager class
(DefaultObservationManager implements ObservationManager)
3. Define class UserLoginEvent similar to DocumentSaveEvent
4. call addListener() of ObjectManager interface (using
DefaultObjectManager) with parameters - object of UserLoginEvent and
reference to login listener.
5. get reference to DefaultObjectManager instance
6. call notify() of DefaultObjectManager instance when user successfully
logged in, with parameters - object of UserLoginEvent, doc and context
7. Implement notify() in LoginListener class.
Q. But I have several confusions when I looked at XWiki class,
saveDocument()
1. Where does it create and add a listener to ObservationManager object??
2. And also it takes ObservationManager object from Util.getComponent()but
where does this observationManager instance is added or set ?
Please clarify me on what I currently understood and let me know if its the
right steps to go with.
Kind Regards,
-Tharindu
Hi devs,
To be clear about what a "frame" means in OOo please have a look at
following screenshots:
http://i39.tinypic.com/293aptt.pnghttp://i41.tinypic.com/259fnfq.jpg
The problem with these frames is that OOo server generates html like below:
<code>
<SPAN ID="Frame1" DIR="LTR" STYLE="float: left; width: 3.09in; height:
3.8in; border: 1px solid #000000; padding: 0.06in; background: #ffffff">
<P CLASS="frame-contents">Hello, This is a frame as it is called on
openoffice writer.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">We have a problem with importing documents
that contain this sort of frames.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">This is the last paragraph</P>
</SPAN>
<code>
Let's forget the fact that it should be a <div> instead of a <span> for the
moment. But even if we convert it to a <div>, with our style filtering
approach this kind of frames are filtered out (because the frame is made out
of a style).
So, the first question is, should these "frames" be filtered in "filter
styles" mode? I think they should not be filtered because it is same as if
we filter tables with "filter styles" mode.
If they should not be filtered completely, what should be the output under
"filter styles" mode?
I can think of two outputs:
<code>
<DIV STYLE="float: left; border: 1px solid #000000;">
<P CLASS="frame-contents">Hello, This is a frame as it is called on
openoffice writer.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">We have a problem with importing documents
that contain this sort of frames.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">This is the last paragraph</P>
</DIV>
<code>
Height & Width are removed because when styles are filtered fonts sizes
change and the size of the box might not be enough for the content to fit
in.
The other output we can have is:
<code>
<table>
<tr>
<td>
<P CLASS="frame-contents">Hello, This is a frame as it is
called on
openoffice writer.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">We have a problem with importing
documents
that contain this sort of frames.</P>
<P CLASS="frame-contents"><BR><BR>
</P>
<P CLASS="frame-contents">This is the last paragraph</P>
</td>
</tr>
</table>
<code>
So it becomes a single cell table, problem solved.
So, wdyt?
Thanks.
- Asiri