Re: Draft Blog Post: Use the Source, Luke
On 25/09/2012 Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke It's good, as usual, but it would feel more complete with some specific call to action, like giving potential code contributors (core, extensions) pointers to get involved. The web server is called Apache HTTP Server and I've seen its modules called just modules most of the time. There are some other possible typos around, like an product, but you can surely spot them better than me in the final proofreading. Regards, Andrea.
Re: Draft Blog Post: Use the Source, Luke
On 09/25/2012 07:57 PM, Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke Good blog. Could use the usual proof reading. Also, specific requests: 1) Anyone have a recent KLOC estimate for the source code? I just ran cloc-1.56.pl on a freshly updated copy of trunk but am not convinced that the numbers are correct. For example the number of c/c++ headers (730) seems to be too small in comparison with the number of c++ files (11014). Can anybody provide better numbers? 50196 text files. 48795 unique files. 31380 files ignored. http://cloc.sourceforge.net v 1.56 T=235.0 s (96.7 files/s, 35983.4 lines/s) Language files blank comment code C++ 11014 837029 8160004690902 Java 3709 101925 206181 440363 IDL4401 86334 1 310547 XML1042 9507 23860 188177 XSLT143 3751 11465 114043 Pascal 224 16178180 99695 Teamcenter def 19 27 0 70644 Perl265 18281 18814 69461 C/C++ Header730 15605 33301 56638 C 157 10218 10393 47304 Visual Basic323 6219 11193 25379 HTML148 899 3031 16823 yacc 3 594665 7966 CSS 121 2381 3217 6785 C# 28 1030 1463 6632 Bourne Shell100 849 2894 6303 Objective C++36 1072 1256 6132 make 85 1533 2147 5700 Python 43 1183 1366 4899 Objective C 15 712903 2702 Assembly 17 230293 2294 DTD 27 662 1035 2173 lex 4 223201 1208 Javascript6 124258 1063 awk 12 62397755 XSD 4 32 88546 PHP 5 95 57520 OpenCL2 99332444 Korn Shell2 93 96385 m41 45 0350 ASP 6 39 9284 DOS Batch11 76216234 Lisp 1 11 0115 C Shell 5 12 83 43 Bourne Again Shell1 2 25 16 ASP.Net 1 0 0 10 sed 3 0 0 7 Expect2 0 0 2 SUM: 227161117132 11514206187544 -Andre 2) Any other recent non-end-user product uses that we should highlight? -Rob
Re: Draft Blog Post: Use the Source, Luke
On 09/26/2012 10:34 AM, Andre wrote: I just ran cloc-1.56.pl on a freshly updated copy of trunk Correction: I looked at the source code of cloc-1.56.pl (which, by the way, can be found at [1]) and saw that the extension hxx was not bound to c++ header files. After fixing this I get a result that better correlates with manually counting all files with extensions cxx (10908) and hxx (11359) : 50196 text files. 48795 unique files. 20023 files ignored. http://cloc.sourceforge.net v 1.56 T=183.0 s (186.0 files/s, 55412.8 lines/s) Language files blank comment code C++ 11014 837029 8160004690902 C/C++ Header 12059 324056 491409 974528 Java 3709 101925 206181 440363 IDL4401 86334 1 310547 XML1042 9507 23860 188177 XSLT143 3751 11465 114043 Pascal 224 16178180 99695 Teamcenter def 19 27 0 70644 Perl265 18281 18814 69461 C 157 10218 10393 47304 Visual Basic323 6219 11193 25379 HTML148 899 3031 16823 yacc 3 594665 7966 CSS 121 2381 3217 6785 C# 28 1030 1463 6632 Bourne Shell100 849 2894 6303 Objective C++36 1072 1256 6132 make 85 1533 2147 5700 Python 43 1183 1366 4899 Objective C 15 712903 2702 Assembly 17 230293 2294 DTD 27 662 1035 2173 lex 4 223201 1208 Javascript6 124258 1063 awk 12 62397755 XSD 4 32 88546 PHP 5 95 57520 OpenCL2 99332444 Korn Shell2 93 96385 m41 45 0350 ASP 6 39 9284 DOS Batch11 76216234 Lisp 1 11 0115 C Shell 5 12 83 43 Bourne Again Shell1 2 25 16 ASP.Net 1 0 0 10 sed 3 0 0 7 Expect2 0 0 2 SUM: 340451425583 16095287105434 -Andre [1] http://sourceforge.net/projects/cloc/
Re: Draft Blog Post: Use the Source, Luke
On Wed, Sep 26, 2012 at 3:02 AM, Andrea Pescetti pesce...@apache.org wrote: On 25/09/2012 Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke It's good, as usual, but it would feel more complete with some specific call to action, like giving potential code contributors (core, extensions) pointers to get involved. OK. What links would you recommend for someone who wanted to take their first look at the source code? Building guide, for certain. Any other good introductory information? The web server is called Apache HTTP Server and I've seen its modules called just modules most of the time. There are some other possible typos around, like an product, but you can surely spot them better than me in the final proofreading. Regards, Andrea.
Re: Draft Blog Post: Use the Source, Luke
Syntax-weenie: has and continues to grow - has grown and continues to grow but also helping users use it - but also by helping users use it natural for an product - natural for a product (or natural for any product?) optimized for a specific install scenarios - optimized for specific install scenarios Our Extensions websites -- there's more than one? Don On Wed, Sep 26, 2012 at 6:59 AM, Rob Weir robw...@apache.org wrote: On Wed, Sep 26, 2012 at 3:02 AM, Andrea Pescetti pesce...@apache.org wrote: On 25/09/2012 Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke It's good, as usual, but it would feel more complete with some specific call to action, like giving potential code contributors (core, extensions) pointers to get involved. OK. What links would you recommend for someone who wanted to take their first look at the source code? Building guide, for certain. Any other good introductory information? The web server is called Apache HTTP Server and I've seen its modules called just modules most of the time. There are some other possible typos around, like an product, but you can surely spot them better than me in the final proofreading. Regards, Andrea.
Re: Draft Blog Post: Use the Source, Luke
On Wed, Sep 26, 2012 at 3:16 PM, Donald Whytock dwhyt...@gmail.com wrote: Syntax-weenie: Thanks, I've made those corrections, as well as the typo noted by Andrea and the information and getting more info on the source code. I also added the lines of code stat from Andre. I'll let the earth turn and if no more comments then I'll go ahead and publish. I then have one more blog post that I had already started in draft form. This is about Apache OpenOffice and ODF. I'll finish what I started there and then I'll be pleased to yield to the other volunteers who are rumored to be eager to blog, if only I wasn't doing it so much. Regards. -Rob has and continues to grow - has grown and continues to grow but also helping users use it - but also by helping users use it natural for an product - natural for a product (or natural for any product?) optimized for a specific install scenarios - optimized for specific install scenarios Our Extensions websites -- there's more than one? Don On Wed, Sep 26, 2012 at 6:59 AM, Rob Weir robw...@apache.org wrote: On Wed, Sep 26, 2012 at 3:02 AM, Andrea Pescetti pesce...@apache.org wrote: On 25/09/2012 Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke It's good, as usual, but it would feel more complete with some specific call to action, like giving potential code contributors (core, extensions) pointers to get involved. OK. What links would you recommend for someone who wanted to take their first look at the source code? Building guide, for certain. Any other good introductory information? The web server is called Apache HTTP Server and I've seen its modules called just modules most of the time. There are some other possible typos around, like an product, but you can surely spot them better than me in the final proofreading. Regards, Andrea.
Re: Draft Blog Post: Use the Source, Luke
Rob Weir wrote: https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke What links would you recommend for someone who wanted to take their first look at the source code? Building guide, for certain. Any other good introductory information? Maybe OpenGrok http://opengrok.adfinis-sygroup.org/source/ and the guide for Extensions developers http://wiki.openoffice.org/wiki/Extensions_development unless someone believes it's too outdated. And, in general, volunteers who need guidance to work with the OpenOffice source code can ask on ooo-dev (which we are using to discuss everything, but is surely the mailing list to use for discussing code too!). Regards, Andrea.
Draft Blog Post: Use the Source, Luke
https://blogs.apache.org/preview/OOo/?previewEntry=use_the_source_luke Could use the usual proof reading. Also, specific requests: 1) Anyone have a recent KLOC estimate for the source code? 2) Any other recent non-end-user product uses that we should highlight? -Rob
