Improving LibreOffice for Windows


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Improving LibreOffice for Windows

  1. 1. Improving LibreOffice for Windows <ul><li>Jesús Corrius Llavina
  2. 2. Version 2011-10-15 (Gold) </li></ul>
  3. 3. Table of Contents <ul><li>Windows as a “vendor”
  4. 4. A new Windows installer
  5. 5. Playing nice with the StarOffice legacy ecosystem
  6. 6. Developers, developers, developers </li></ul>
  7. 7. Windows as a “vendor” I guess Microsoft will not join TDF but...
  8. 8. Windows as a “vendor” <ul><li>Major Linux distributions do: </li><ul><li>Have a team and a organization to work on LibO
  9. 9. Build customized and branded versions of LibreOffice
  10. 10. Offer support and convenient way to distribute and update it
  11. 11. Marketing about their product and that includes LibO
  12. 12. Have dedicated developers working in LibreOffice fixing bugs and add new features their customers want
  13. 13. This model works very well </li></ul></ul>
  14. 14. Windows as a “vendor” <ul><li>Windows is an important platform but things don't work the same way
  15. 15. Why not? Maybe... </li><ul><li>There are no customers, no bugs or feature requests
  16. 16. No companies are migrating Windows users to LibO
  17. 17. No one makes money </li></ul><li>Why not? Probably... </li><ul><li>Market is too fragmented
  18. 18. No real FOSS / collaboration culture
  19. 19. Lack of proper channels to canalize this support (“I am a company and I want to support the Windows build, how can I do it?”) </li></ul></ul>
  20. 20. Windows as a “vendor” <ul><li>Let's create a Windows “vendor” inside the project
  21. 21. What's that? </li><ul><li>Organized infrastructure to support the Windows build
  22. 22. An umbrella where small and big companies can feel at home
  23. 23. Bugs, feature requests
  24. 24. Marketing
  25. 25. A small company migrating Windows desktops can't afford to have a dedicated developer, but maybe 20 companies can.
  26. 26. Make it very easily for companies with no FOSS culture to join the effort </li></ul></ul>
  27. 27. Windows as a “vendor” <ul><li>Why do we have to spend our time and effort on that? </li><ul><li>Windows is still a very important platform, especially for companies, but end users also
  28. 28. We have already won the Linux/BSD market
  29. 29. The StarOffice legacy ecosystem will concentrate on Windows and (probably MacOS X too)
  30. 30. We need to clearly show the outside world that we do really care and we are serious about it
  31. 31. We also need to clearly show that the other platforms are still very important and they always be </li></ul></ul>
  32. 32. A new Windows installer... If it works why do we have to change it?
  33. 33. A new Windows Installer <ul><li>The two steps installation (NSIS/MSI) is not very friendly for Windows users
  34. 34. Why are we leaving temporal files in the desktop?
  35. 35. Not optimal for large deployments in corporations
  36. 36. On Windows the installer is the first impression you get of an application
  37. 37. UTF-8 stuff, etc.
  38. 38. But... I think there's a more compelling reason... </li></ul>
  39. 39. A new Windows Installer <ul><li>SHOCKING! Most Windows users don't perceive a difference between LibO and other products of the StarOffice legacy ecosystem
  40. 40. We need a new nice, good-looking and friendly installer to differentiate LibO from the other legacy products
  41. 41. We need to involve all the community and especially the design team
  42. 42. It will be send a hint to the outside world than we do care about the Windows users and we are working in the right way for them </li></ul>
  43. 43. Playing nice with the StarOffice legacy ecosystem Because we are not alone
  44. 44. Playing nice with the StarOffice legacy ecosystem <ul><li>None of the other projects of the StarOffice legacy ecosystems have produced installable builds yet
  45. 45. But there's a chance that they do
  46. 46. Products will not be installable side by side on Windows
  47. 47. There are many reasons: </li><ul><li>“Greedy” installers
  48. 48. Application Ids (COM+ and OLE stuff)
  49. 49. Common registry keys
  50. 50. File associations (bad clean up code, backup, etc)
  51. 51. Same file names ;) </li></ul><li>In short: it's a mess </li></ul>
  52. 52. Playing nice with the StarOffice legacy ecosystem <ul><li>Should we play nice? I think so
  53. 53. Let the others be the “bad” guys
  54. 54. Some things are trivial to fix
  55. 55. Others are not: </li><ul><li>Very bad decisions when designing the OLE support can make us incompatible with older documents or documents generated with other products based on StarOffice </li></ul><li>It's fixable, but it's a lot of work
  56. 56. Other products will have the same problems
  57. 57. But.... let's be the nice guys of the ecosystem </li></ul>
  58. 58. Developers, developers, developers (No need to comment about this one)
  59. 59. Developers, developers, developers
  60. 60. Developers, developers, developers <ul><li>What would a Windows developer ask first?
  61. 61. “Dude, where's the Visual Studio project to compile LibreOffice?”
  62. 62. Cross-compilation is good, but we have to continue to support the native Windows tools
  63. 63. Support for latest Windows compilers and environments: </li><ul><li>Visual Studio 2010
  64. 64. Newest Microsoft SDKs, etc
  65. 65. Properly detect all the tools and dependencies, etc.
  66. 66. Easy way to set up a Windows development environment (msi that installs everything in the right places?) </li></ul><li>By popular demand: 64 bits version for Windows </li></ul>
  67. 67. Developers, developers, developers <ul><li>Full support for the free Microsoft Visual Studio Express: remove ATL dependencies
  68. 68. Extensions builder for Visual Studio
  69. 69. Known languages for Windows developers to write extensions: C#, Visual Basic, etc </li></ul>
  70. 70. Thank you … for listening to me! <ul><li>See you at the LibreOffice Paris Conference
  71. 71. Find out more at </li></ul>