Re: [dev] Get list of top votes on QA site?
Hi Niklas, Niklas Nebel schrieb: On 03/25/09 11:47, Niklas Nebel wrote: Oh, that's quite bad. Thanks for noticing it. As soon as Issue Tracker works again, I will submit an issue and try to get it into 3.1. http://qa.openoffice.org/issues/show_bug.cgi?id=100538 Thanks! I did not have the time to submit the issue this morning. André - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Get list of top votes on QA site?
André Schnabel wrote: The link that is used by the spreadsheet is (very long:) http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&votes=50&cmdtype=doit&order=issues.votes%20desc%2C%20issues.priority Also, thank you for the link. That is very useful! Regards -- Bill Stewart - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Get list of top votes on QA site?
André Schnabel wrote: If an issue is going to be fixed does not only depend on votes. So .. no matter if you put more votes on it unless you have very good arguments, this will not raise the chances for a fix. Hi André, Understood and I agree. Naturally, I think the arguments are quite sound, and I think we are going to discuss on the UX list rather than here. Regards -- Bill Stewart - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] XML and XSL into ODT transformation
Hi there! David Tardon wrote: On Wed, Mar 25, 2009 at 02:24:54AM +0100, Pasqualino Imbemba wrote: Hello, I am writing a Java application which at a certain point needs to generate an OO word processor file (ODT), based on a XSL stylesheet and XML data file. Is there a library that provides such functionality? Hello, any XSLT processor will do. Saxon is a good choice, regarding the fact you work in Java. OpenDocument Files consist not of just one XML Stream but several XML Streams packaged together with binary content like graphics for example into a ZIP Format file. ODFDOM contains a java library handling this basic ODF Package Format plus providing Helper functions on applying XSL stylesheets on subcontent of such ODF Packages or storing results from XSL Transformations into such ODF Packages. Besides that ODFDOM provides a Document Object Model for ODF. ODFDOM can be downloaded from http://odftoolkit.org/projects/odftoolkit/downloads More information on ODFDOM is availalbe at http://odftoolkit.org/projects/odftoolkit/pages/ODFDOM Kind regards, Bernd Eilers David - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Info: potential SDK changes for OO.org 3.2
Hi, the SDK contains many examples showing the usage of the API etc. The examples got not really maintained and the workload for testing them is high. Some time in the past i have already mentioned that the idea is to remove some of the examples from the SDK. Mainly examples written in Java that are now available as NetBeans projects and that can be used instead. The advantage of the NetBeans projects is that you can easier browse the code and debug the examples directly from NetBeans. The removed examples (in the original structure) can be stored for potential use. Well the idea still is to provide the examples as Eclipse projects as well, or as MSDEV projects converted to C++, or Python? Volunteers are welcome! A further advantage of having the examples standalone and documented in the wiki is that the community can easier help to improve the examples. you can comment them on the related discussion page, can improve the code or the documentation etc. We now have enough experienced API users that can help in this area ;-) Anyway nothing is decided yet and the SDK build system will remain in the SDK independent of the examples. That means your own solutions based on the SDK build env will still work. The main reason for this email is that i would like to ask if somebody has concerns about this planned change. If so please let me know and let us continue further discussion on d...@api.openoffice.org. By the way QA volunteers for the SDK examples or the SDK in general are welcome. If you are interested to help in this area please let me know. Regards Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] MediaWiki *import* function ?
Hi, There is an underdevelopment extension that converts MediaWiki markup to OpenDocument Text format (.odt) Extension:OpenDocument Export (Release status: beta) http://www.mediawiki.org/wiki/Extension:OpenDocument_Export T. J. Frazier wrote: Do you think it might be useful, to consider a two-step conversion process, using XML as the intermediate step? That is, instead of "ODF <==> Wiki", we could have "ODF <==> XML", and "Wiki <==> XML". @TJ: That is a beautiful implementation. But, I am afraid, it might not be useful, I think. The advantage I see is the division of labor. Both groups (MW and OO.o) would likely see those transformations as, "not very efficient, but relatively simple". Neither group would have to deal with each other's oddities, only their own. I can agree with lesser amount of labor. But its complexity and less reproductivity might make it less interesting, though. Possible user scenario which I probably want to have for the interoperability between OpenOffice.org and MediaWiki: (Writer to MediaWiki) 1. On writer, select a portion of or entire document and copy it. 2. Ctrl-N to start an empty Writer document. 3. Ctrl-Shift-V to paste special with a choice of MediaWiki format. 4. Ctrl-A to select all and copy it. 5. In a text field of MediaWiki, paste it. (MediaWiki to Writer) 1. Click on a special link next to 'Edit.' 2. OpenOffice.org automatically starts and draws the target page or section in a web browser. 3. Select it and copy it. 4. On Writer, paste it. Regards, Tora - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Get list of top votes on QA site?
On 03/25/09 11:47, Niklas Nebel wrote: Oh, that's quite bad. Thanks for noticing it. As soon as Issue Tracker works again, I will submit an issue and try to get it into 3.1. http://qa.openoffice.org/issues/show_bug.cgi?id=100538 Niklas - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Get list of top votes on QA site?
On 03/25/09 08:02, André Schnabel wrote: I am looking for a way to list the issues with the largest number of votes on the QA site (qa.openoffice.org). I tried going to: qa.openoffice.org -> Miscellaneous link -> Issue Votes link The list at this location (http://qa.openoffice.org/iz_votes.html) has not been updated since 2006-02-19, and the spreadsheet template it mentions (issuevotes.ots) doesn't seem to have a way to let me list the issues with the largest number of votes. The link that is used by the spreadsheet is (very long:) http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&votes=50&cmdtype=doit&order=issues.votes%20desc%2C%20issues.priority interestinng - the spreadsheet crashes with OOo 3.1 :( Oh, that's quite bad. Thanks for noticing it. As soon as Issue Tracker works again, I will submit an issue and try to get it into 3.1. Niklas - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Sections and appending documents
Hey,
I was thinking about first writing the original document to disk and later
if an unmerge is needed to just use "loadFromURL" with the path of the
original document to reload it. However it doesn't get past the loading of
the XComponent. The application freezes as a result and I need to kill the
soffice.bin process manually.
This is the code:
> public void loadFromURL(final String aURL, final
> com.sun.star.beans.PropertyValue aArguments[],String target) {
> if(target == null){
> target = "_self";
> }
> try {
> XMultiComponentFactory serviceFactory =
> getOOoConnection().getComponentContext().getServiceManager();
> xServiceFactory = (com.sun.star.lang.XMultiServiceFactory)
> UnoRuntime.queryInterface(
> com.sun.star.lang.XMultiServiceFactory.class,
> serviceFactory);
>
> if (xFrameWindow == null) {
> serviceFactory =
> getOOoConnection().getComponentContext().getServiceManager();
> removeAll();
> xFrameWindow =
> iConnection.createOfficeWindow(MyOOoBean.this);
> add(xFrameWindow.getAWTComponent());
> }
> if (aFrame == null) {
> com.sun.star.awt.XWindow xWindow =
> (com.sun.star.awt.XWindow)
> UnoRuntime.queryInterface(
> com.sun.star.awt.XWindow.class,
> xFrameWindow.getUNOWindowPeer());
> xFrame =
> xServiceFactory.createInstance("com.sun.star.frame.Frame");
> aFrame = new Frame((com.sun.star.frame.XFrame)
> UnoRuntime.queryInterface(
> com.sun.star.frame.XFrame.class, xFrame));
> aFrame.initialize(xWindow);
> aFrame.setName(aFrame.toString());
>
> // register the frame at the desktop
> com.sun.star.frame.XFrames xFrames =
> ((com.sun.star.frame.XFramesSupplier)
> UnoRuntime.queryInterface(
> com.sun.star.frame.XFramesSupplier.class,
> getOOoDesktop())).getFrames();
> xFrames.append(aFrame);
> }
> xURLTransformer = (com.sun.star.util.XURLTransformer)
> UnoRuntime.queryInterface(
> com.sun.star.util.XURLTransformer.class,
>
> xServiceFactory.createInstance("com.sun.star.util.URLTransformer"));
>
> // get XComponentLoader from frame
> com.sun.star.frame.XComponentLoader xLoader =
> (com.sun.star.frame.XComponentLoader)
>
> UnoRuntime.queryInterface(com.sun.star.frame.XComponentLoader.class,
> aFrame);
>
> if (xLoader == null) {
> throw new java.lang.RuntimeException(
> "com.sun.star.frame.Frame(" + aFrame +
> ") without
> com.sun.star.frame.XComponentLoader");
> }
>
> com.sun.star.beans.PropertyValue aArgs[] =
> addArgument(aArguments, new
> com.sun.star.beans.PropertyValue(
> "MacroExecutionMode", -1,
> new
> Short(com.sun.star.document.MacroExecMode.USE_CONFIG),
>
> com.sun.star.beans.PropertyState.DIRECT_VALUE));
>
> com.sun.star.lang.XComponent xComponent =
> xLoader.loadComponentFromURL(
> aURL, target, 0, aArgs); //2nd load doesn't get past
> this point resulting in a crash
>
> // nothing loaded?
> if (xComponent == null && aDocument != null) {
> // reactivate old document
> if (aFrame != null && aFrame.getController() != null)
> aFrame.getController().suspend(false);
> aDocument.setModified(true);
>
> // throw exception
> throw new java.io.IOException(
> "Can not load a document: \"" + aURL + "\"");
> }
>
> // Get document's XModifiable interface if any.
> xModel = (com.sun.star.frame.XModel)
> UnoRuntime.queryInterface(
> com.sun.star.frame.XModel.class, xComponent);
> aTxtDocument = (XTextDocument)
> UnoRuntime.queryInterface(XTextDocument.class,xComponent);
> XComponentContext xRemoteContext =
> com.sun.star.comp.helper.Bootstrap.bootstrap();
>
> aDocument = new OfficeDocument(xModel);
>
> //adding additional listeners to the frame
> createBroadCaster();
>
>
> } catch (NoConnectionException e) {
>
> }
> catch (IllegalArgumentException e) {
> e.printStackTrace(); //To change body of catch statement use
> File | Settings | File Templates.
> } catch (IOException e) {
> e.printStackTrace(); //To change body of catch statement use
> File | Setti
Re: [dev] XML and XSL into ODT transformation
On Wed, Mar 25, 2009 at 02:24:54AM +0100, Pasqualino Imbemba wrote: > Hello, > > I am writing a Java application which at a certain point needs to > generate an OO word processor file (ODT), based on a XSL stylesheet and > XML data file. > > Is there a library that provides such functionality? > Hello, any XSLT processor will do. Saxon is a good choice, regarding the fact you work in Java. David - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] MediaWiki *import* function ?
Hi, tora - Takamichi Akiyama wrote: Hi, Rich wrote: I immensily enjoy the MediaWiki export function, but in order to make it the perfect WYSIWIG MediaWiki editor, it would also need a MediaWiki *import* function. Is anything like that currently planned ? If I tried to realize such a function that converts MediaWiki's format into OpenOffice.org format, there were some ideas: Idea 1: Implement it in the MediaWiki as its extension. Idea 2: Realize it as an offline tool. Idea 3: Incorporate it in the OpenOffice.org as an import filter or in a copy-and-paste function of OpenOffice.org. IMHO, idea 1 would be the easiest, reliable, robust way. With an extension of the MediaWiki, a link labeled "download this page as an OpenOffice.org file" might be one of the possible user interface implementations. The reason is that MediaWiki itself knows how to interpret MediaWiki format and how to produce its corresponding HTML format. So, what we might need to work to realize it would be just to write a code producing ODF format instead of HTML format. If we had implemented it in our OpenOffice.org, we would forever have to follow up MediaWiki's versions. Its history shows that its format has been being revised version by version and consequently it is easy to infer that its format would be continuously revised in the future. So, it is a MidiaWiki extension exporting its Wiki page into ODF format. I don't know if it is already available or not. :-> Regards, Tora @Tora: thank you for the fine insight, as to where most of the problems lie. Do you think it might be useful, to consider a two-step conversion process, using XML as the intermediate step? That is, instead of "ODF <==> Wiki", we could have "ODF <==> XML", and "Wiki <==> XML". The advantage I see is the division of labor. Both groups (MW and OO.o) would likely see those transformations as, "not very efficient, but relatively simple". Neither group would have to deal with each other's oddities, only their own. Just a thought. /tj/ -- T. J. Frazier Melbourne, FL (TJFrazier on OO.o) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Get list of top votes on QA site?
HI, Bill Stewart schrieb: Hello all, I am looking for a way to list the issues with the largest number of votes on the QA site (qa.openoffice.org). I tried going to: qa.openoffice.org -> Miscellaneous link -> Issue Votes link The list at this location (http://qa.openoffice.org/iz_votes.html) has not been updated since 2006-02-19, and the spreadsheet template it mentions (issuevotes.ots) doesn't seem to have a way to let me list the issues with the largest number of votes. The link that is used by the spreadsheet is (very long:) http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&votes=50&cmdtype=doit&order=issues.votes%20desc%2C%20issues.priority interestinng - the spreadsheet crashes with OOo 3.1 :( Background: I, along with many others, are trying to get issue 96594 implemented ASAP (i.e., undo the bad decision made in issue 91086). As I write this, we have gathered 71 votes so far, and I want to know whether 96594 has a good chance of getting fixed in the next release. If an issue is going to be fixed does not only depend on votes. So .. no matter if you put more votes on it unless you have very good arguments, this will not raise the chances for a fix. André - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
