Re: [dev] developing extension
Rajveer Sangha schrieb: Dear Open Office, I am an amateur programmer, knowing primarily c++ and c. i want to develop a certain extension for open office which will enable a 'tagging mode' in open office, for easier formatting, much like TEX. Is it workable, where should i begin? Could you explain in closer detail what that tagging mode should be? What should become tagged and what are these tags going to contain? Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] contribution
Lawrence Quinn schrieb: hi, I would like to help this (these) project(s). I have skills as both a programmer and a technical writer. If you have needs in either area, let me know. Lawrence Quinn thanks for your interest in our project. The best place to get informed about OOo development is http://wiki.services.openoffice.org/wiki/Main_Page You should also have a look on our projects at http://projects.openoffice.org/index.html Many projects have a to do list on their project pages so please visit the project(s) you find interesting. If you want to know more about a project please write a mail to the dev mailing list of this project. Best regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] may i know how to access UNO using javascript in firefox?
hunter schrieb: may i know how to access UNO using javascript in firefox? it can be done easily in IE, due to the support of Auntomation. but can it be done in firefox, especially under Linux? if can, how can i get this done? Firefox uses a technology called XPCOM to make calls to the application code from JavaScript so you would need an XPCOM bridge to UNO to access UNO from within Firefox. Some time ago we did some experimental development in this area but the project was abandoned. In case you are interested in a UNO-XPCOM binding please get in touch with the UNO developers on the dev@udk.openoffice.org mailing list. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] File | Open default file type
Allen Pulsifer schrieb: Yes, that sounds good. I would change it a little bit and offer showing the filter dialog (that also needs a redesign BTW). Only offering to open as text is not enough. Especially text files are detected quite reliably. But as in most cases where OOo fails to detect the file it *is* an unknown type showing the filter dialog immediately isn't a good idea. So a message box asking how to proceed as you suggested will help. Hello Mathias, I did a preliminary spec at http://wiki.services.openoffice.org/wiki/File_Chooser_Type_Handling_Specific ation I think you may have more insights than me though. Could you comment further how the filter dialog should work, vis a vis the draft spec? Thanks for your effort, Allen. However I'm afraid that your proposal to default to an application specific filter will not be accepted. The issue list you have presented in your initial mail already contained some issues that have been closed for that reason. We see OpenOffice.org as an integrated package and don't see why the fact that somebody is writing a text makes it more probable that the next file to be opened will be a text file also. This is something that perhaps should be taken up by the new user experience project. I will study the other points in your spec in the next days and give you a feedback on this list. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OOo w/o URE
Rüdiger Timm schrieb: Caolan McNamara wrote: On Tue, 2007-02-13 at 09:54 +0100, Stephan Bergmann wrote: FYI: http://odftoolkit.openoffice.org/servlets/ReadMsg?list=devmsgNo=32 Yeah, I'm very much in favour of this myself. Split the build into two parts the API stable ure stuff, and the rest. I'm trying to home-brew some hackery to fake this up. The current practical problems are of course as listed above and [...] So it's certainly kludgy to try and do it right now, but is a very attractive goal for me to be able to just rebuild the portion of OOo affected by whatever bug I've just fixed. And a nice thin edge of a wedge to make OOo more modular at build-time as well as at runtime. C. I also like the idea to modularize products and packages. But I am no friend of splitting it at build time, at least now. For one I still remember times when we here at Sun Hamburg practized such a split between SDK and rest of office. It was quite some effort to reach that split (f.e. separating idl files into two separate modules, 'udkapi' and 'offapi') and some effort to mainatain it. It was unhandy to work with. And we gained nearly nothing. So in the end we again merged both workspaces into one. We gained nothing as there was no demand for a split. This may change in the future (I hope it will). The maintenance effort mainly exists in the heads of the developers: they must make themselves aware of it and act accordingly. IIRC people never tried to understand why we had two idl modules and so they often feeled annouyed. But maybe my memories fool me. Second reason is that (curently) this does not fit our development stile. We do childworkspaces feature wise. With the current degree of code mudularity this quite often means to work on base (URE) modules ^^^ I hope that this is a typo and not a Freudian slip! :-) providing some new functionality and applications where you want to use that in one childworkspace. So, yes, it may be an attractive goal. But we should start with package restructuring and more code modularity. Stick with building on one workspace for now. I agree that it is fortunate to be able to work on a CWS that contains all necessary modules even if they are part of 2 or 3 products. OTOH I think it is essential that we make it easy to build SDK and URE from scratch independently from OOo. This is the kind of split we need. That does not exclude that active development work (CWS) still happens in the integrated environment. As long as all products share the same cvs repository I don't think that this is endangered. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Releasing 2.3 earlier - to capture part Back to school season?
Kirill S. Palagin schrieb: Hello everybody. Version 2.3 is scheduled to be released on September 4th, 2007 (http://wiki.services.openoffice.org/wiki/OOoRelease23). In my opinion we may gain substantial number of users if we release earlier. The idea behind this - people generally buy more computers in August and for their new computers they need an office suit. If we manage to release by, say 25th of August we will capture users by giving them new shiny tempting version 2.3 (which is promising to be very good feature-wise) for their new computers. I don't think that this makes sense (BTW: I think that most computers are ordered around Christmas, so releasing a new feature release in September isn't a bad timing). What do developers think of this? I can speak for myself only. I think we should stick to our release cycle. We extended it for a reason. This reason hasn't gone. Besides that, OOo 2.2 isn't bad either. :-) Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] developing extension
Mathias Bauer, 15-02-2007 10:47:
Rajveer Sangha schrieb:
Dear Open Office,
I am an amateur programmer, knowing primarily c++ and c. i want to develop a
certain extension for open office which will enable a 'tagging mode' in open
office, for easier formatting, much like TEX.
Is it workable, where should i begin?
Could you explain in closer detail what that tagging mode should be?
What should become tagged and what are these tags going to contain?
Since he cited TEX, tags probably means meta-edition of the text. For
instance:
{{HEADER| page_numbering start=3 align=left}}
Some text here
{{LIST| style=numbering}}
{ITEM} a item
{ITEM} another item
{{END_LIST}}
I believe it will be an easy task to use ODF with this kind of thing
after moving to the toolkit.
A goal would be to use a plain text editor to edit the files and to
generate ODF files with the extension running on ODF toolkit.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OOo w/o URE
Mathias Bauer wrote: Rüdiger Timm schrieb: Caolan McNamara wrote: On Tue, 2007-02-13 at 09:54 +0100, Stephan Bergmann wrote: FYI: http://odftoolkit.openoffice.org/servlets/ReadMsg?list=devmsgNo=32 [...] Second reason is that (curently) this does not fit our development stile. We do childworkspaces feature wise. With the current degree of code mudularity this quite often means to work on base (URE) modules ^^^ I hope that this is a typo and not a Freudian slip! :-) Typo :-) BTW, what's 'mudularity'? Sounds interesting, but I don't know such word . providing some new functionality and applications where you want to use that in one childworkspace. So, yes, it may be an attractive goal. But we should start with package restructuring and more code modularity. Stick with building on one workspace for now. I agree that it is fortunate to be able to work on a CWS that contains all necessary modules even if they are part of 2 or 3 products. OTOH I think it is essential that we make it easy to build SDK and URE from scratch independently from OOo. This is the kind of split we need. That does not exclude that active development work (CWS) still happens in the integrated environment. As long as all products share the same cvs repository I don't think that this is endangered. OK. If that's all, 'make it easy to build SDK and URE from scratch independently from OOo', than I am fully with you. It should be possible to check out just a needed subset of modules and build them. Without the need to go through the whole tree just because you need 'instsetoo_native'. But, that's only the first of four paragraphs Stephan wrote concerning 'at build time'. Rüdiger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [dev] File | Open default file type
Thanks for your effort, Allen. However I'm afraid that your proposal to default to an application specific filter will not be accepted. The issue list you have presented in your initial mail already contained some issues that have been closed for that reason. We see OpenOffice.org as an integrated package and don't see why the fact that somebody is writing a text makes it more probable that the next file to be opened will be a text file also. Hello Mathias, Thank you. Believe me, I don't take it personally. That is just one of several proposals in the draft spec and I'm glad to see it get discussion and consideration. To me, that part of the proposal is all about work flow and new user expectation, not about marketing. I put that in there because it matches the way I work, and also because this had been requested by others. When I use the File | Open dialog in an application, I am generally going to open the same type of document, and having this preselected makes it easy for me. I think most new users expect the same thing, and get confused to see so many files list. I can certainly see how other people might view it differently, and I would be happy to have the UX team look at it. Allen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OOo w/o URE
Rüdiger Timm schrieb: Mathias Bauer wrote: Rüdiger Timm schrieb: Caolan McNamara wrote: On Tue, 2007-02-13 at 09:54 +0100, Stephan Bergmann wrote: FYI: http://odftoolkit.openoffice.org/servlets/ReadMsg?list=devmsgNo=32 [...] Second reason is that (curently) this does not fit our development stile. We do childworkspaces feature wise. With the current degree of code mudularity this quite often means to work on base (URE) modules ^^^ I hope that this is a typo and not a Freudian slip! :-) Typo :-) BTW, what's 'mudularity'? Sounds interesting, but I don't know such word Doesn't exist, but I hoped that it wasn't the word mud that was going around in your head and slipped into your fingers when you wanted to write modularity. :-) OK. If that's all, 'make it easy to build SDK and URE from scratch independently from OOo', than I am fully with you. It should be possible to check out just a needed subset of modules and build them. Without the need to go through the whole tree just because you need 'instsetoo_native'. But, that's only the first of four paragraphs Stephan wrote concerning 'at build time'. Yes, I only presented my personal POV. For users and developers of OOo there wouldn't be much they could get from separated builds. That's clearly something for people that don't want to build OOo. So for me the ability to build and work on URE and ODK separately while still keeping the OOo build environment would be sufficient. Stephan's mileage may vary of course. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] developing extension
Hi, Thanks for replying. I try to explain my point. This is something like an interpreted markup document. Instead of writing the text and then applying various levels of formatting to it, for example: headlines, sub-headlines, body text etc. we can write our document like: headingthis is heading/heading subthis is sub heading/sub bodyText formatiing is so easier this way in a large document/body User would be able to define these tags, like heading means BookMan Old 20 pt Red Color etc. . Say I can make a toggle button for Interpreter mode. Press the button and start writing your document in this interpreted fashion. Once you're done, toggle the button and the whole document is interpreted and displayed in formatted manner and you able to write in that WYSIWYG manner too, ie without interpreting. what i am talking about is very similar to TEX. But its integrated in Open Office, like bringing the power of TEX to ordinary users which I find has a learning curve of its own. Do reply. Reagrds Rajveer On 2/15/07, Mathias Bauer [EMAIL PROTECTED] wrote: Rajveer Sangha schrieb: Dear Open Office, I am an amateur programmer, knowing primarily c++ and c. i want to develop a certain extension for open office which will enable a 'tagging mode' in open office, for easier formatting, much like TEX. Is it workable, where should i begin? Could you explain in closer detail what that tagging mode should be? What should become tagged and what are these tags going to contain? Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. -- Rajveer Sangha Room # F-46 Ravindra Bhavan IIT Roorkee Roorkee-247667 Uttaranchal Ph: +91-9358354995
Re: [dev] developing extension
Hi Thanks for replying. I try to explain my point. This is something like an interpreted markup document. Instead of writing the text and then applying various levels of formatting to it, for example: headlines, sub-headlines, body text etc. we can write our document like: headingthis is heading/heading subthis is sub heading/sub bodyText formatiing is so easier this way in a large document/body User would be able to define these tags, like heading means BookMan Old 20 pt Red Color etc. . Say I can make a toggle button for Interpreter mode. Press the button and you may have a look at reveal code from Ian Laurenson http://homepages.paradise.net.nz/hillview/OOo/ http://www.oooforum.org/forum/viewtopic.phtml?p=36201 Laurent -- Laurent Godard [EMAIL PROTECTED] - Ingénierie OpenOffice.org - http://www.indesko.com Nuxeo Enterprise Content Management http://www.nuxeo.com - http://www.nuxeo.org Livre Programmation OpenOffice.org, Eyrolles 2004-2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] developing extension
Rajveer Sangha schrieb: Hi, Thanks for replying. I try to explain my point. This is something like an interpreted markup document. Instead of writing the text and then applying various levels of formatting to it, for example: headlines, sub-headlines, body text etc. we can write our document like: headingthis is heading/heading subthis is sub heading/sub bodyText formatiing is so easier this way in a large document/body User would be able to define these tags, like heading means BookMan Old 20 pt Red Color etc. . Say I can make a toggle button for Interpreter mode. Press the button and start writing your document in this interpreted fashion. Once you're done, toggle the button and the whole document is interpreted and displayed in formatted manner and you able to write in that WYSIWYG manner too, ie without interpreting. what i am talking about is very similar to TEX. But its integrated in Open Office, like bringing the power of TEX to ordinary users which I find has a learning curve of its own. Do reply. I see now. I think Laurents tip about the reveal codes macro is one way to tackle this. Perhaps it gives you a start. But I'm not sure if this really is what you want. What you are describing looks more like kind of directly editing the XML code of the document to me. While I think that this is doable it's definitely not an easy task. What looks simple if you only see text or character attributes can become quite complicated if you consider everything possible in a document e.g. graphics, OLE objects, tables, foot notes, change tracking etc. You will end up with programming a complete new view and GUI for the application - something that the core developers have done in months and years. A *possible* approach could be what we are doing in the HTML editor (Writer/Web). You can toggle the document view between the HTML view and the source code view, both are editable. When you switch between them the document gets saved and reimported. This is not the most elegant way but an easy one. In result you will implement your own XML editor then. Given the enormous enhancements or feature requests we already have I would recommend to contribute to these things before starting a new editing mode. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] File | Open default file type
Hi Allen, Allen Pulsifer schrieb: I can certainly see how other people might view it differently, and I would be happy to have the UX team look at it. As I could see on the discuss list of the ux project they are already involved. Great! So I will redirect further discussions to the ux-list. Thanks for your dedication to the project. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OOo w/o URE
Stephan Bergmann schrieb: Mathias Bauer wrote: Rüdiger Timm schrieb: OK. If that's all, 'make it easy to build SDK and URE from scratch independently from OOo', than I am fully with you. It should be possible to check out just a needed subset of modules and build them. Without the need to go through the whole tree just because you need 'instsetoo_native'. But, that's only the first of four paragraphs Stephan wrote concerning 'at build time'. Yes, I only presented my personal POV. For users and developers of OOo there wouldn't be much they could get from separated builds. That's clearly something for people that don't want to build OOo. So for me the ability to build and work on URE and ODK separately while still keeping the OOo build environment would be sufficient. Stephan's mileage may vary of course. One idea behind the separation of URE and OOo is that you have one URE installed on your machine and potentially many other applications that use it (OOo, an ODF toolkit in whatever form, etc.). Sine URE and OOo are potentially deployed into different locations (e.g., /opt/openoffice/ure vs. /opt/openoffice2.2), this means that the OOo-specific code will no longer find the general URE code right next to it. And that would also probably have implications on the build environment, as I detailed in my original post. Making URE more easily buildable inside the current OOo build environment is one possible (first) step. The complete picture would go further, however, and that is where Rüdiger's concerns would kick in. Understood, but I think we should start with the first step as it seems to be uncontroversal and it already helps a lot. When we start to implement the complete picture it should be possible to address any concerns that still might exist then. So if people could build the URE and the SDK easily they would be able to use it as we wanted them to use it. Wether we deployed OOo in a way that allowed to share a common URE installation later on shouldn't be important currently, though it surely should be the final goal if we take the idea of the ODF toolkit seriously. I think if Rüdigers' concerns were still valid they would be a clear sign that the separation between the URE and OOo is not really done and that there are still too much dependencies. OTOH if both indeed are separated enough the necessary changes in the build environment shouldn't make problems. Why should anybody have one CWS that contains sources from OOO *and* URE then? Or do I overlook something? Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Please join (and spread the word): Community member's photos for poster
Hi all, sorry for cross-posting, but I'd like to reach as many community members as possible. Follow-up at [EMAIL PROTECTED] if possible. In a few days (Feb. 21th) there will be the UNESCO International Mother Language Day [1] and John McCreesh asked the Native-Lang Confederation if we would be able to do anything for that date [2]. Discussion started on creating a website with images of as many community members as possible, but I think we might create a poster with lots of photos showing that OOo is created and supported by people on all over the world. It would be something like Frappr [3], but usable offline, reusable for marketing means like other posters and licensed under LGPL. If you want to join, please attach a small photo (60x80 to 90x120 px) to issue http://qa.openoffice.org/issues/show_bug.cgi?id=74585 (after logging in in the right upper corner of the page, you're shown a link Create new attachments below the present attachments). If you want to tell us your location we'd try to position the photos according their location on a world map. Please inform your project about that work. The more people join, the better the result will be. Best regards Bernhard [1]: http://portal.unesco.org/education/en/ev.php-URL_ID=12871URL_DO=DO_TOPICURL_SECTION=201.html [2]: http://native-lang.openoffice.org/servlets/ReadMsg?list=devmsgNo=7368 [3]: http://www.frappr.com/ooodev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
