Re: [api-dev] Re: Examining a directory with OpenOffice.org Basic
On 12/01/2010 02:38 PM, Johnny Rosenberg wrote: 2010/12/1 Johnny Rosenberg: If I know the name of a directory, let's say ~/MyImages, how can I easily read the names of all the files in that directory? Let's say that we will fill an array with all the file names. I have searched a bit online, but so far I didn't find anything that I understand… I'll continue searching, though. He he he… I tried again to search for the answer and this time I found it almost immediately… At least I think I did: http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/Files_and_Directories_(Runtime_Library) Seems to be what I am looking for. Other thoughts about this are still welcome, though. I'm interested in how useful you find the Basic Guide Wiki page you dug up. Is it missing info? Anything unclear etc? What can be or needs to be improved? C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Progress on exporting the Dev Guide to ODT and PDF
Maybe one suggestion (very nice to have): would it be possible to apply syntax coloring/highlighting to the example code? It would make it so much easier for readers to orientate themselves in the code examples. Something like applying the [g]vim syntax highlighting? Would you be able/contemplate of adding it? Hmmm... I'm not sure how easy this will be. The code blocks are given a Preformatted paragraph style which applies the grey background, and the monospaced character styles. Short of manually editing and applying custom character styles through all code blocks, I'm not sure how it could be done. Exporting the existing syntax highlighting from the Wiki is beyond the current capabilities of the Book (Collection) extension. If anyone has any ideas on how this might be done... I'm definitely open to them :-) I have macros that do something similar in OOo. I apply character styles to different portions of the text to colorize them. The primary macro works based on a cursor selection. I have code that wades through an entire document and color codes what it finds based on paragraph styles. Because I am not aware of your process, I do not know how adaptable this is for your export process. I have code that can colorize starbasic, Java, C++, Perl, Python, and XML. I use simplistic parsers, but the only error of which I am currently aware (that I have not yet fixed) is that in Basic, I failed to list \ as an operator (integer division). Oops! That might work. The ODFs use a paragraph style for all of the code blocks in the main text. It can't hurt to give it a try - the ODFs are all available on the Wiki Books page. The export process uses the Collection/Book export to ODT, and from there I simply import a template to it, tidy up a few places where the template doesn't yet work quite right and publish. The macro, if it works, could be rolled into the template for future publish runs. C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] Update on the ODF/PDF of the Dev Guide.
Just a quick update for you guys. I've finally updated the DevGuide ODF and PDF on: http://wiki.services.openoffice.org/wiki/Documentation/Wiki_Books All chapters are in reasonable shape. The full book as one file has been uploaded in both ODT and PDF. This is as far as I plan to take these documents for this release. Next step for the Doc Project will be to streamline the export process, clean up the template we use, and improve the document layout etc. It took about 4.5 days work to take the guide from Wiki, export to ODT and clean up the output. The result is a document that is about 1670 pages long. A cleaner template and some tweaking to the Wiki pages to clean up the source so it exports cleaner will make the next export cycle go a lot faster. If there are any questions, just ask... or if you spot any big problems with the exported documents, let me know! C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] Progress on exporting the Dev Guide to ODT and PDF
I've finally been able to make some progress with exporting the Developer's Guide out of the Wiki and into ODT and PDF. Updating the Wiki was a big help in getting this working smoothly. You can find the latest documents here: http://wiki.services.openoffice.org/wiki/Documentation/Wiki_Books - ODT chapters marked as First Draft are raw exports from the Wiki that are imported to the Book template - no cleanup has been done. They are not in a final condition, do if you download/read one of those chapters, expect there to be formatting and layout problems that will affect readability - especially with tables. - ODT chapters that do NOT have First Draft have had a pass at formatting and layout cleanup. There are still a few minor issues here adn there that I will work on for teh next big export. For now, unless someone sports a really major issue, this is as far as I will take the export. I am also combining the chapters into one single document. So far, Chapters 1 to 6 are in one doc, and can also be downloaded from the page linked above. C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Progress on exporting the Dev Guide to ODT and PDF
I am also combining the chapters into one single document. So far, Chapters 1 to 6 are in one doc, and can also be downloaded from the page linked above. Maybe one suggestion (very nice to have): would it be possible to apply syntax coloring/highlighting to the example code? It would make it so much easier for readers to orientate themselves in the code examples. Something like applying the [g]vim syntax highlighting? Would you be able/contemplate of adding it? Hmmm... I'm not sure how easy this will be. The code blocks are given a Preformatted paragraph style which applies the grey background, and the monospaced character styles. Short of manually editing and applying custom character styles through all code blocks, I'm not sure how it could be done. Exporting the existing syntax highlighting from the Wiki is beyond the current capabilities of the Book (Collection) extension. If anyone has any ideas on how this might be done... I'm definitely open to them :-) C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Help please...
David Tardon wrote: On Thu, Jul 02, 2009 at 12:28:55PM -0400, Michael Custer wrote: I need to know how to download the complete developers guide to my flash drive. I hope there is a pdf version somewhere. Look at http://wiki.services.openoffice.org/wiki/Documentation/Wiki_Books . Unfortunately this page doesn't yet have the entire DevGuide for 3.1. You can build the PDF yourself though. At the top of the first page of each chapter is a link Download as PDF or ODT. 1. Click that link in each chapter you want to download 2. Click Load collection (link on the left side of the Wiki page) 3. On the right in the Download box, select the format and click the Download button. 4. Repeat for each chapter you want to save/download. The goal is to have an ODT and PDF as a snapshot for each major release. The process is still being worked on and is currently on hold, waiting on the Wiki engine upgrade. After the engine upgrade, we will be able to use the latest Collection (Book) tools and take another step towards a more automatic process. For now, it does take a small amount of work to build the PDF - the up side being that it is current as of the day you create the PDF (with all edits and corrections up to that point). C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] Rich Text editor added to the OOoWiki
NOTE: Cross-posted to website, user, api, and documentation mailing lists. =-=-=-=-=-=-= I finally figured out how to add the FCKeditor (a WYSIWYG rich text editor) to the OpenOffice.org wiki (it was held up by a long standing error in the pHp backend that I fixed this morning). The FCKeditor is *OFF* by default for all users (including new users). I set this by request from discussions we've had on this topic in the past. We can enable it by default for newly registered users if we want by changing an option in the Wiki preferences file... but for now it's disabled for everyone, and must be explicitly switched on if you want to use it. To enable the FCKeditor: 1. Log into the Wiki using your normal user ID. 2. Click the my preferences link at the top of the Wiki page. 3. Go to Misc. 4. Remove the check marks in the boxes next to the option Disable rich editor. 5. You can toggle other options related to the rich text editor depending on your preferences. 6. Click Save. This editor has many nice features beyond the basics for editing... for example adding Templates of Categories - you can pick them from a drop down list. So... test it out. Let me know if there are any issues (please discuss on the d...@website.openoffice.org mailing list). Note: You can always toggle the editor off with the Disable rich editor link at the top of the page you're editing if there is something on the page that is causing problems in the editor. C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
mmh, i think that is partly done with dynamic page lists. We can add a new category for DevGuide examples if necessary. And of course we can link it from the DevGuide but that should be done from every single code snippet The Dynamic Page lists are great.. reduces maintenance in a big way. You only need to add a code example page to the right Category, and the page with the DPL will automatically add it to the list of links. No maintenance necessary. We can and should use a specific category (or groups of categories) for the example code. I hope I didn't write too much. I am looking forward to any comments. no, i think it's good to see that people think about improvements. The more ideas the better :-) C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Update on the status of the ODT/PDF version of the DevGuide
rony wrote: Hi Clayton, Clayton wrote: Hi. Just a quick update on how things are coming along on the ODT and PDF of the entire DevGuide. I have posted an ALPHA version of the doc here: http://wiki.services.openoffice.org/wiki/Documentation/Wiki_Books (it's 1750+ pages now, and currently about 1.55MB in size) Unfortunately the URL on that page, http://wiki.services.openoffice.org/w/index.php?title=Special:UploadwpDestFile=DevelopersGuide_OOo3.0.0.pdf, causes the Wiki to think that one would like to upload something, which is not the case, I would like to download. Here, the resulting page: Yes that's because you are clicking the link for the PDF... the PDF does not yet exist... only the ODT. A red link with an edit icon to the right means that page or object does not yet exist, and the Edit or Upload page is what you are supposed to get when you click the red link. Try downloading the ODT... the one with the blue link :-) C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] Update on the stauus of the ODT/PDF version of the DevGuide
Hi. Just a quick update on how things are coming along on the ODT and PDF of the entire DevGuide. I have posted an ALPHA version of the doc here: http://wiki.services.openoffice.org/wiki/Documentation/Wiki_Books (it's 1750+ pages now, and currently about 1.55MB in size) NOTE: This is an early draft of the doc, not its final form. There are issues I am working on... - code blocks did not all export nicely from the Wiki - illustrations see to have fallen off somewhere - heading levels are not right - copyright information is not yet included (PDL) What is looking OK though is the content and general layout. So have a poke around in it if you like. I'll be updating it with new uploads as I clean up the doc and make it a little more presentable. The PDF will follow once the ODT is in better shape. C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Offline copy of Developers Guide
I am in a country with rather poor internet access, and ever since the developer's guide moved to the wiki : http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide I have had serious accessibility issues - earlier releases of the SDK used to include a PDF copy of the developers guide, unfortunately this PDF copy is still on OOo v2.3. Is it possible to have a offline dump of the developer's guide wiki so i can set it up locally / or an updated pdf version so i can use it locally ? i don't know how good it is but you can try the following. You can create a PDF based on collections. The DevGuide provides predefined collections for all top level chapters. For example - click on First Steps - move to the bottom - click on download as PDF collection - on the left side you will find Create a book - click on Load Collection - override existing collections if necessary or append - play with it - on the next page you will find on the right side a download button and before you click the download button select the PDF format - this way you should be able to create PDF for each chapter as i mentioned i don't know how good the quality is but as far as i know the documentation project is working on that. Yes, we are working on it. The steps Juergen outlined will work for now. The plan is to provide easy links for people to download individual chapters as PDF and ODT, and possibly as an entire book (which would be a huge single download). The limitation is, the Collection is static. This means that a Collection that is valid today, is not going to be valid tomorrow (people are adding and removing content all the time). We need to find a way to dynamically generate or respin the Collection once per week (or some other schedule) so that the Collection picks up the changes in the document structure. So... immediate plan. I have to finish up with the recent Wiki engine update (some issues with the upgrade need to be taken care of first). I will then start working on adding a Download as a Collection link to the bottom of the FIRST PAGE in EACH chapter of the Developer's Guide. You will be able to click this link and generate a PDF or ODT document for the current chapter you are viewing. Mid term - I will try to find a way (with some help from the community here) to script things (using a cron job and the MediaWiki API?) to auto-rebuild the Collections on some schedule to keep the Collections up to date. Manually maintaining the Collections for this large document is not practical. C. -- Clayton Cornell ccorn...@openoffice.org StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Offline copy of Developers Guide
Jason Cooper wrote: I'm glad to hear that this is being worked on. I also have a need for an offline version, since my workplace doesn't have internet access. Don't forget that the tools are already in place on the Wiki for you to make your own Collections of the chapters you need,. You don't have to wait on me to make the generic chapter versions. You can already build your own PDFs or ODT documents from the existing Wiki documents. C. -- Clayton Cornell ccorn...@openoffice.org StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] ad Wiki: possible to get whole chapters?
Today, I followed a few Wiki links given in various postings, and stumbled again over the desire/need to create a collection from a topic, including all sub-topics (as depicted in the overview box on the upper right-hand side). It seems that it is still not possible to add a Wiki page to the collection, indicating that all sub-pages (links in the upper right hand box) should be included (recursively, if sub-pages would have sub-pages themselves). That is correct. The Collection extension only allows you to add one page at a time from the clickable links, and is not smart enough to travel down all sub pages. I doubt this will ever be possible since functionality like this could easily run away with itself and effectively PDF the entire Wiki depending on where you started an action like that. To create a PDF of an entire chapter, you currently have two options. 1. Step through each Wiki page in that chapter adding each page to your personal Collection 2. Manually create the Collection (it is just a list of Wiki articles in standard Wiki syntax). This step requires that you know the Wiki article names and paths for all the articles you want to add. This information is available in the TOC template, but it's not simple to work with if you are not familiar with it. Option 1 is the most reasonable option at this point for most. I hope to simplify this a bit in the future. I have been working on an idea to auto-generate the Collections for each chapter. The Wiki syntax for a Collection and the Wiki syntax we use to generate the TOC box are similar. We should be able to run a WikiBot over the TOC pages extract the chapter information and generate a Collection. When things are ready to go on with this step, I will write up an outline of what is needed, and will call on the community here to help with the scripting. So I am wondering whether I overlook the obvious and would be greatful for any further hints/comments... No you haven't overlooked the obvious :-) Collections are not a 100% solution... it still needs some work. C. -- Clayton Cornell [EMAIL PROTECTED] StarOffice - Sun Microsystems, Inc. - Hamburg, Germany - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[api-dev] Unanswered API and OOo development related questions on the OOoForum
Can some of the experts here please take a look at (and answer) some of the unanswered questions we have over on the OOo User Forum. These questions are piling up on the forum, and the community members that monitor and answer questions on the forum are not able to help. We REALLY need some API experts to come support the OOo community on the OOo User Forum. Some of the unanswered topics with links to the forum postings are: (Note: This is NOT a complete list.. it is only some of the API and OOo Development related questions that have gone unanswered.) BUGS in event listeners and handlers: http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=10546 Protected sections http://user.services.openoffice.org/en/forum/viewtopic.php?f=25t=10400 APIs http://user.services.openoffice.org/en/forum/viewtopic.php?f=44t=10532 Getting the Name Of a SpreadSheet Document http://user.services.openoffice.org/en/forum/viewtopic.php?f=45t=10728 Example of OOoBeanViewer? http://user.services.openoffice.org/en/forum/viewtopic.php?f=45t=10763 Print Tab if cell value is X http://user.services.openoffice.org/en/forum/viewtopic.php?f=45t=10765 Issue with SID vs ServiceName for jdbc connection to Oracle http://user.services.openoffice.org/en/forum/viewtopic.php?f=40t=10791 J-UNO: efficient way to iterate over JumpEdit fields? http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=10160 Generating Calc Spreadsheet using C# .net 2005 http://user.services.openoffice.org/en/forum/viewtopic.php?f=44t=10146 Event-Listeners Handlers. Calc-OOoBasic http://user.services.openoffice.org/en/forum/viewtopic.php?f=21t=10123 [Java] Merging documents http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=10109 Inserting an absolute page number http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=10095 Printing different selections http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=10022 Setting listeners on a treeControl with Java macros http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=9863 Howto store a password for jdbc-connection? http://user.services.openoffice.org/en/forum/viewtopic.php?f=40t=9839 ooCalc-EVENT trouble, still 1 problem, how start them again? http://user.services.openoffice.org/en/forum/viewtopic.php?f=25t=9822 Insert new Row using Java http://user.services.openoffice.org/en/forum/viewtopic.php?f=44t=9797 Zoom effect for chart graph http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=9757 EVENT LISTENERS troubles stop working, CALC-OOBasic http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=9748 Example of a functional, java coded, TreeControl ? http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=9655 Page format in OOWriter via API http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=9218 No Need to Bootstrap with UNO? Better for threading? http://user.services.openoffice.org/en/forum/viewtopic.php?f=25t=9079 How to get screen size? http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=8976 Convert Excel macro to OO Basic macro http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=8928 Why LoadLibrary failed http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=8926 Bulleted List in Java? http://user.services.openoffice.org/en/forum/viewtopic.php?f=20t=8914 C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] Moving CoceSnippets into the Wiki?
I am not quite sure, which is easier: a) Download, install, execute Snippet Creator b) Learn and study to become a wiki editor I quess for those, who have no experience with the wiki, a) is much easier. MediaWiki is not all that hard to learn - at least not for the basics. There is also a MediaWiki export filter you can use in OpenOffice.org which works quite well (I'm using it to convert the API Guide to Wiki format). http://wiki.services.openoffice.org/wiki/Odt2Wiki So... with this export filter, you don't even really need to learn MediaWiki syntax in detail just use OpenOffice.org or StarOffice, export your document to a text file and paste the contents of that text file into the Wiki editor box. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
