[libreoffice-users] QA on the LibreOffice project
Hi, I'm intentionally starting a new thread, as Charles's replies this morning raised a few points that are rather important for subscribers of this mailing list to know about. At least it seems that Charles reall assumed certain things about our project that are inaccurate and in turn that makes me think many peope here may make the same assumptions. I hope this post will help, and maybe we could turn this into a page in the wiki that we could point to, from time to time. 1) Most or the majority of developers are paid to work on LibreOffice Not at all, and it is quite the opposite. In rough numbers, there are about 800 people who contributed code to LibreOffice ever since the beginning, and the number is constantly increasing. On this number a very small minority are paid to work on LibreOffice, full time or only partially. They are either self employed or are paid by a company to do so. The Document Foundation does not employ anyone to code. Still talking in rough numbers, on these 800 people there are about 120 more or less regular developers (we have more accurate figures periodically published here: http://blog.documentfoundation.org ) developing LibreOffice . Among them, roughly 20 of them are paid to develop LibreOffice more or less full time. A dozen more are assumed to work on a periodic basis, with very specific focus on certain parts of the code and for a limited time only. 2) Developers should at least test their builds While this may sound counterintuitive, not all of them do that, far from it, and when they do, many of them run automated tests, which is a standard practice in development these days. These automated test do include regression tests (more info here: https://wiki.documentfoundation.org/QA/Testing/Regression_Tests ) Ultimately, the development process leads to a specific sub process called the release process. Certain criteria must be met, and they are listed here: https://wiki.documentfoundation.org/Release_Criteria . Obviously no process is ever perfect but we encourage everyone to join our Quality Assurance team. Only you, not the developers only, can improve LibreOffice. This is how Free Software works, and what sets us apart from more traditional vendors. Actually, there are several other, sometimes less technical ways to help: http://www.libreoffice.org/community/get-involved/ 3) I manage and run systems for my customers.I am just a user Congratulations, you are a system administrator. But no, you are not just a user. You are a professional and while LibreOffice may not be what generates revenue for you, you are a professional distributing, installing and configuring software to your customer. As such, you must at least read our release notes. They are always on the wiki (for instance, here : https://wiki.documentfoundation.org/ReleaseNotes/4.3 ) and in an abridged version in our download section here: http://www.libreoffice.org/download/release-notes/ 4) Patches integration have never been notified to me / We have not been warned on this list This is not a detailed answer. It is possible some developer did not warn the issue thread on the bug tracker - that is a mistake. However, and as a general remark, the users list is only meant for users support (watch me, I'm writing stuff and upsetting everyone). Information is spread all over the project, on mailing lists, twitter accounts, and the wiki. Some useful pointers have already been given in the points above, this page however is rather dense in its links and might be useful: http://www.documentfoundation.org/contribution/ 5) How can you all be volunteers? This is crazy! You'll never make it! Maybe. Or not. It depends. We strongly suggest acquiring a license of MS Office in order to remediate to the current insanity one may be experiencing and going back to the normal world. The worrying trend here is that we're not the only ones: http://www.kernel.org and http://www.debian.org are but two random examples. Maybe someone ought to call the cops. 6) Welcome to the LibreOffice project. How are you doing? Thank you for reaching the end of this mail. We hope it helped. Best, Charles. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: MySQL native connector for LibreOffice 4.2 and 4.3 (Linux versions)
Le 03/10/2014 07:27, Alan B a écrit : Hi Alan, I have a database from the US gov't, npidata freely available, with about 3.5 million rows and around 350 columns. Actually the gov't provides a csv. Imported it into a MySQL db using the MySQL command line. Never been able to read the primary table using the Java connector. With the native MySQL Yeah, the whole Java connector thing within LibreOffice and large record sets is a very bad combination, even with a mysql backend ! I'm not surprised you couldn't read it with an array of data that big, even if each field only contained 1 byte :-) Glad that the native connector at least allows you to load the records :-)) Alex -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: [Base Database] How to open a particular form at startup ?
Le 02/10/2014 22:00, Rafnews a écrit : Hi, i have a database created with Base from LibreOffice. i have a form stored in the same ODB file called FMain. Now how can i do to open automatically the form when i open the ODB file ? https://forum.openoffice.org/en/forum/viewtopic.php?f=39t=34147 read the thread all the way through to the end. Alex -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: MySQL native connector for LibreOffice 4.2 and 4.3 (Linux versions)
Alex Thurgood schrieb: Le 03/10/2014 07:27, Alan B a écrit : Hi Alan, I have a database from the US gov't, npidata freely available, with about 3.5 million rows and around 350 columns. Actually the gov't provides a csv. Imported it into a MySQL db using the MySQL command line. Never been able to read the primary table using the Java connector. With the native MySQL Yeah, the whole Java connector thing within LibreOffice and large record sets is a very bad combination, even with a mysql backend ! I'm not surprised you couldn't read it with an array of data that big, even if each field only contained 1 byte :-) Glad that the native connector at least allows you to load the records :-)) Alex Hi Alex, I do have a long-time connection with ALL 3 kinds of MySQL connectors. Only the native one REALLY works o.k... There is one problem in MY case, however: My DB-Hosting facility specifies a connection time-out value of 1 minute. With the Java connector one can specify reconnect-true (or yes?) when defining the DB under LO. This means that LO at least re-connects after a termination of the connection by the server. This is NOT a good situation, but it is kind of acceptable. The native connector does NOT allow such a specification. This makes it unusable to me unfortunately. I hope that it might be possible to change this limitation of the native connector. Regards Heinrich -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] fixing as a service ...
Hi Tanstaafl / Florian, On Thu, 2014-10-02 at 09:50 -0400, Tanstaafl wrote: You obviously haven't read this entire thread. Florian is trying to extort money from me to fix this major regression. So - just to put my oar in here since Collabora was mentioned; I notice several issues here and some bugs - let me try to address them in order from my perspective. A. I'm pleased that Florian is excited about our L3 bug fixing services (so am I) - but I'd -really- prefer people to advertise other competent / certified developers; the project benefits from a diverse corporate ecosystem; so it is wise to link this instead: http://www.documentfoundation.org/certification/developers/ B. It is true that there is a sense in which large corporate users of LibreOffice capture a lot of benefit and cost saving from that - and a great way to contribute back is to help fund someone to represent your interests in the development community - by writing regression tests for your pet features and being present in the discussions. + arriving after the fact and complaining doesn't work. C. Anything is possible, don't assume that because it is 'broken' today, it will not be fixed tomorrow. Please don't assume that because it is difficult a volunteer won't fix it I know volunteers of amazing skill and tenacity nailing horrible bugs left/right =) D. Complaining doesn't work, contribution does. IMHO LibreOffice does not exist to meet your needs, it exists to allow you to collaborate constructively with others to meet our needs :-) We are a meritocracy, and constructive contribution should give you, whomever you are, influence. E. Extortion is a pretty silly word to use to describe a mismatch of expectations around a bug or two. F. A couple of specific bugs: Apparently not a regression: around printing https://www.libreoffice.org/bugzilla/show_bug.cgi?id=65205 Input fields re-work: https://bugs.freedesktop.org/show_bug.cgi?id=79877 I'm confused wrt. this one, we re-worked text fields adding MS Office compatible rich, in-line editable fields for LibreOffice 3.x - so - perhaps this is another feature ? quite possibly we started mapping old fields to new ones in the filters more recently but ... The underlying feature un-screwed-up millions of business users documents, and hugely improved interoperability so ... A regression should be dealt with, and in your case it has, just not fast enough for you - but that is life. Yep... and the consequences, in this case, are that my biggest client is seriously considering switching to Microsoft office I like the fact that you care about that =) so do I - Free Software is important - I wish it was perfect; we should try to make the project a fun constructive one where more people feel like they want to volunteer their time to make a positive change. Tone helps there. Then again, if you really can't get your work done with LibreOffice (yet), and you prefer to pay a chunk of cash to Microsoft rather than pay for having LibreOffice tweaked to your taste, then that is entirely your choice - and the economics of course depend on how many users you have: if it is just 5x people - then, it's not enough to justify paying for any debilitating issue to be fixed - of course. Finally, I'm curious how Microsoft handles these pop-out vs. inline fields - they do have file-format support for their legacy fields of course I just wonder if they try to update them in newer versions [ if there are no macros / whatever associated with them ]. Anyhow - hope that helps, All the best, Michael. -- michael.me...@collabora.com , Pseudo Engineer, itinerant idiot -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] fixing as a service ...
On Fri, 2014-10-03 at 12:26 +0100, Tom Davies wrote: So basically LibreOffice is Is what it is (profound huh). Anything could easily fail at any time. All software is buggy. If something does fail then users are expected to fix it for themselves ? I don't know how you make that stuff up. There are a huge number of bugs filed (and fixed) each week from companies and individuals around the project. My thesis is that shouting and pointing is not a good strategy for interesting volunteers in your bug; and demanding XYZ is a particularly unhelpful approach; grow the ecosystem of people contributing to improving quality by either contributing yourself, or paying someone else to is by contrast a constructive thing to do =) ATB, Michael. -- michael.me...@collabora.com , Pseudo Engineer, itinerant idiot -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Fair enough. I guess that belief was a remnant from the Sun/Openoffice days. My apologies for a huge, incorrect assumption. Also, I just realized there is a distinction that I have been making, but that may have been missed and so may be causing a disconnect. That distinction is, code that someone writes and contributes - like, for example, this new 'Inline editing' feature for Input fields' - vs pre-existing/old legacy code and/or bugs that is/was already there, long before any new volunteers come along. In most of the projects I use and interact with, bugs are taken very seriously, and fixed as soon as they are verified (after being reported), with a 'thank you very much for reporting this!' response... It is *only* enhancements/feature requests that get the *very* valid and legitimate 'patches welcome!' and/or 'we will happily add that feature for you for $# bucks.' responses... Libreoffice, and Mozilla Thunderbird are the only projects I use and interact with on a daily basis that seem to act totally contrary to this, and constantly play the 'fix it yerself/pay someone to fix it for you' cards. With Thunderbird, it is really only because they simply don't have enough manpower (2 or 3 devs for the entire project, I believe), and they are dealing with a ton of pre-existing/old legacy code/bugs, and I totally get it. I also totally get it with respect to the same code in Libreoffice, and from what I understand, that it is a huge monster of a code base. But all of that is really orthogonal to my main point... Software developers, whether volunteer or not, should have *some* level of responsibility and obligation on their part to fix bugs they themselves introduce into code they write. I know I would if I were one, and I know I do for anything that I do build. They write it - they should own it. I simply don't understand how anyone could believe otherwise. On 10/2/2014 5:57 PM, Joel Madero jmadero@gmail.com wrote: Um - well two points: 1. None of the paid developers are paid by TDF - we have 0 paid developers on staff. 2. Most commits are still done by volunteers and many are done by paid developers on their free time (ie. when they are volunteering). -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] fixing as a service ...
Tom, I didn't read Michael's email in any way shape or form the way you did. I thought it was very on point and productive, as far as it went. It also appears that there are actually two different bugs with respect to this new inline editing, one of which deals with fields *other* than 'Input Fields' - and the one being discussed in this thread, dealing strictly with 'Input Fields'... On 10/3/2014 7:26 AM, Tom Davies tomc...@gmail.com wrote: Hi :) So basically LibreOffice is unreliable. Anything could easily fail at any time. If something does fail then users are expected to fix it for themselves? Regards from Tom :) On 3 October 2014 11:55, Michael Meeks michael.me...@collabora.com mailto:michael.me...@collabora.com wrote: Hi Tanstaafl / Florian, On Thu, 2014-10-02 at 09:50 -0400, Tanstaafl wrote: You obviously haven't read this entire thread. Florian is trying to extort money from me to fix this major regression. So - just to put my oar in here since Collabora was mentioned; I notice several issues here and some bugs - let me try to address them in order from my perspective. snip -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] fixing as a service ...
Hi :) So you are saying that posting a bug-report and co-operating with the devs politely is shouting and pointing? That is all that Tanstaafl was doing before suddenly getting attacked by Charles, Sophie, Werner, Florian and others at the beginning of this thread. All i have seen him do since then is to try to defend himself and attemtp to explain his situation to a hostile audience. A couple of us have attempted to stand by him but either been ignored or also attacked. Any chance of answering Paul's last post? Regards from Tom :) On 3 October 2014 13:08, Michael Meeks michael.me...@collabora.com wrote: On Fri, 2014-10-03 at 12:26 +0100, Tom Davies wrote: So basically LibreOffice is Is what it is (profound huh). Anything could easily fail at any time. All software is buggy. If something does fail then users are expected to fix it for themselves ? I don't know how you make that stuff up. There are a huge number of bugs filed (and fixed) each week from companies and individuals around the project. My thesis is that shouting and pointing is not a good strategy for interesting volunteers in your bug; and demanding XYZ is a particularly unhelpful approach; grow the ecosystem of people contributing to improving quality by either contributing yourself, or paying someone else to is by contrast a constructive thing to do =) ATB, Michael. -- michael.me...@collabora.com , Pseudo Engineer, itinerant idiot -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: [Base Database] How to open a particular form at startup ?
Hi, I have a macro similar to neptuneuk's that Alex pointed to, but I go one step further. I run Windows 7 64 bit. I right click on my project's .odb file, click on 'Send to' and then on 'Desktop (create shortcut)'. Then I can simply double click on the shortcut to go directly into my Main Menu form. Sometimes, usually if I have just started my PC, it's a bit slow and LibreOffice's initial menu appears for a few seconds before the Menu form is displayed. But once the machine has warmed up, double clicking on the shortcut displays the Menu almost immediately. I have found this is simpler for my users. It also keeps them away from the underlying LO menu and prevents them being confused by a screen that they don't need to be concerned about! I have several such shortcuts on my desktop and find the them faster than opening LibreOffice and going through several steps to select the .odb file I want to open. Don't know how well this would work on other operating systems, but it works well for me. Noel -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: fixing as a service ...
Hi Michael, Thanks, mostly agree with your thoughts, with two comments... On 10/3/2014 6:55 AM, Michael Meeks michael.me...@collabora.com wrote: B. It is true that there is a sense in which large corporate users of LibreOffice capture a lot of benefit and cost saving from that - and a great way to contribute back is to help fund someone to represent your interests in the development community - by writing regression tests for your pet features and being present in the discussions. + arriving after the fact and complaining doesn't work. 1. Some people (like me) are of limited skills. Setting up an entire automated build/test environment is simply way beyond my capability. The best I can do is download installable builds and simply test them by using them. I'm happy to do this, but hopefully you recognize that it is basically impossible for someone to test all or even most of the features that they use on a daily basis, and it would be very easy to miss something. C. Anything is possible, don't assume that because it is 'broken' today, it will not be fixed tomorrow. Please don't assume that because it is difficult a volunteer won't fix it I know volunteers of amazing skill and tenacity nailing horrible bugs left/right =) 2. There is a huge difference between: a) bugs that are directly introduced by a specific developer while working on a new feature or a specific bug, and b) old pre-existing/legacy code/bugs that current developers had nothing to do with. Meaning - a developer should be responsible for the code they write, including fixing bugs when they are found *without* resorting to 'patches welcome' or 'pay someone to fix it' type responses in the bug reports (or on this list) - the latter only being appropriate for: a) new feature/enhancement requests, and/or b) old pre-existing/legacy code/bugs If the vast majority of the developers don't agree with this principle, and in fact believe that they should be able to just commit code for something, then go on their merry way and/or respond with the 'patches welcome' or 'pay someone to fix it' responses, then I guess we are so far apart philosophically that I should just stfu and go away. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] fixing as a service ...
Hi :) It was points B, D and his 2nd to last paragraph. Normally those wouldn't have caused concern but they follow on from what Charles Schulz has been saying. Also the fact that Paul's post got ignored. He, Paul, obviously raises good points that none of them can deal with = so instead they pick on other posts. That seems to be a good tactic that they have adopted through the rest of the thread too. They only write to inflame, as a troll would do. Michael and Sophie are usually above that sort of thing and i usually feel a huge sense of relief when they post. This time Michael unfortunately hit a nerve that's been rubbed raw by other people. Regards form Tom :) On 3 October 2014 13:20, Tanstaafl tansta...@libertytrek.org wrote: Tom, I didn't read Michael's email in any way shape or form the way you did. I thought it was very on point and productive, as far as it went. It also appears that there are actually two different bugs with respect to this new inline editing, one of which deals with fields *other* than 'Input Fields' - and the one being discussed in this thread, dealing strictly with 'Input Fields'... On 10/3/2014 7:26 AM, Tom Davies tomc...@gmail.com wrote: Hi :) So basically LibreOffice is unreliable. Anything could easily fail at any time. If something does fail then users are expected to fix it for themselves? Regards from Tom :) On 3 October 2014 11:55, Michael Meeks michael.me...@collabora.com mailto:michael.me...@collabora.com wrote: Hi Tanstaafl / Florian, On Thu, 2014-10-02 at 09:50 -0400, Tanstaafl wrote: You obviously haven't read this entire thread. Florian is trying to extort money from me to fix this major regression. So - just to put my oar in here since Collabora was mentioned; I notice several issues here and some bugs - let me try to address them in order from my perspective. snip -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Many apologies to the devs generally and the individual one in question
On 10/2/2014 8:15 PM, Paul paulste...@afrihost.co.za wrote: I did say it was not a major thing to be guilty of, and I really mean that. These things happen, and a simple oops, my bad, I'll fix that is really all that I feel is needed here. I agree - but they didn't. Instead, users are told they need to 'pony up' with $4,000+ to get their 'pet bug' fixed, rather than cry about it. This is perfectly acceptable for pre-existing/old/legacy bugs and/or new feature/enhancement requests. The great work the devs are doing overall is far, far more important than any little slips (and even the odd major one) that may creep in from time to time. In fact I agree very much. Hey - bugs happen, and I absolutely would never accuse any developer of deliberately introducing bugs (although, I guess, in some rare cases, it can happen)... BUT... When bugs are discovered in new code added by a current/specific developer, those bugs, when reported and confirmed, should simply be fixed, by the developer that wrote the code, maybe gasp even with a 'thanks for the bug report'! I just really wish that some developers would realize that the (admittedly often valid) open-source retort of 'well, fix it yerself or hire someone to do it' simply isn't an appropriate response, especially for a bug in a 'new' feature that replaced a pre-existing feature that worked perfectly for over 10 years - not to mention the fact that paying $4,000 per bug to get them fixed simply isn't an option for some people. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: [Base Database] How to open a particular form at startup ?
On 10/03/2014 08:27 AM, Marion Noel Lodge wrote: Hi, I have a macro similar to neptuneuk's that Alex pointed to, but I go one step further. I run Windows 7 64 bit. I right click on my project's .odb file, click on 'Send to' and then on 'Desktop (create shortcut)'. Then I can simply double click on the shortcut to go directly into my Main Menu form. Sometimes, usually if I have just started my PC, it's a bit slow and LibreOffice's initial menu appears for a few seconds before the Menu form is displayed. But once the machine has warmed up, double clicking on the shortcut displays the Menu almost immediately. I have found this is simpler for my users. It also keeps them away from the underlying LO menu and prevents them being confused by a screen that they don't need to be concerned about! I have several such shortcuts on my desktop and find the them faster than opening LibreOffice and going through several steps to select the .odb file I want to open. Don't know how well this would work on other operating systems, but it works well for me. Noel What Noel has done also works with Linux by creating a soft link to the database on the Desktop. Then double clicking the link causes the database to open. Similarly, creating a soft link to a folder containing the databases that are often used can be used. Then double clicking the link and then double clicking the name of the desired database will accomplish the same thing. But I do not think this is what the OP was wanting. When the database opens, he wants the form named, FMain, to open as well as the main database window. Obviously, he would want the window containing the FMain form to be on top. Dan -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Hi :) Aww heck that'd be brilliant! If TDF could take Thunderbird under their wing instead of leaving it with Mozilla. Mozilla don't seem to appreciate just how many people rely on Thunderbird. It's the best OpenSource email client around, in the opinion of a huge percentage of people apparently. People, and articles have often said that LibreOffice could never compete with MSO because it lacks an email client. Completely missing the point that so many great email clients integrate so well with LibreOffice. Maybe if there was a kinda default one and if that was as great as Thunderbird is then it'd cut a lot of detractors off at the knees. Sorry! I do agree with your main points! Regards from Tom :) On 3 October 2014 13:16, Tanstaafl tansta...@libertytrek.org wrote: Fair enough. I guess that belief was a remnant from the Sun/Openoffice days. My apologies for a huge, incorrect assumption. Also, I just realized there is a distinction that I have been making, but that may have been missed and so may be causing a disconnect. That distinction is, code that someone writes and contributes - like, for example, this new 'Inline editing' feature for Input fields' - vs pre-existing/old legacy code and/or bugs that is/was already there, long before any new volunteers come along. In most of the projects I use and interact with, bugs are taken very seriously, and fixed as soon as they are verified (after being reported), with a 'thank you very much for reporting this!' response... It is *only* enhancements/feature requests that get the *very* valid and legitimate 'patches welcome!' and/or 'we will happily add that feature for you for $# bucks.' responses... Libreoffice, and Mozilla Thunderbird are the only projects I use and interact with on a daily basis that seem to act totally contrary to this, and constantly play the 'fix it yerself/pay someone to fix it for you' cards. With Thunderbird, it is really only because they simply don't have enough manpower (2 or 3 devs for the entire project, I believe), and they are dealing with a ton of pre-existing/old legacy code/bugs, and I totally get it. I also totally get it with respect to the same code in Libreoffice, and from what I understand, that it is a huge monster of a code base. But all of that is really orthogonal to my main point... Software developers, whether volunteer or not, should have *some* level of responsibility and obligation on their part to fix bugs they themselves introduce into code they write. I know I would if I were one, and I know I do for anything that I do build. They write it - they should own it. I simply don't understand how anyone could believe otherwise. On 10/2/2014 5:57 PM, Joel Madero jmadero@gmail.com wrote: Um - well two points: 1. None of the paid developers are paid by TDF - we have 0 paid developers on staff. 2. Most commits are still done by volunteers and many are done by paid developers on their free time (ie. when they are volunteering). -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
I really do understand but I think you underestimate the complexity of a project with more than 10,000,000 lines of code. That being said, I have no additional feedback and we're not going to be forcing anything on volunteers so . . . we can agree to disagree and know that this is how the project works-take it or leave it. Best, Joel On 10/03/2014 06:19 AM, Tom Davies wrote: Hi :) Aww heck that'd be brilliant! If TDF could take Thunderbird under their wing instead of leaving it with Mozilla. Mozilla don't seem to appreciate just how many people rely on Thunderbird. It's the best OpenSource email client around, in the opinion of a huge percentage of people apparently. People, and articles have often said that LibreOffice could never compete with MSO because it lacks an email client. Completely missing the point that so many great email clients integrate so well with LibreOffice. Maybe if there was a kinda default one and if that was as great as Thunderbird is then it'd cut a lot of detractors off at the knees. Sorry! I do agree with your main points! Regards from Tom :) On 3 October 2014 13:16, Tanstaafl tansta...@libertytrek.org wrote: Fair enough. I guess that belief was a remnant from the Sun/Openoffice days. My apologies for a huge, incorrect assumption. Also, I just realized there is a distinction that I have been making, but that may have been missed and so may be causing a disconnect. That distinction is, code that someone writes and contributes - like, for example, this new 'Inline editing' feature for Input fields' - vs pre-existing/old legacy code and/or bugs that is/was already there, long before any new volunteers come along. In most of the projects I use and interact with, bugs are taken very seriously, and fixed as soon as they are verified (after being reported), with a 'thank you very much for reporting this!' response... It is *only* enhancements/feature requests that get the *very* valid and legitimate 'patches welcome!' and/or 'we will happily add that feature for you for $# bucks.' responses... Libreoffice, and Mozilla Thunderbird are the only projects I use and interact with on a daily basis that seem to act totally contrary to this, and constantly play the 'fix it yerself/pay someone to fix it for you' cards. With Thunderbird, it is really only because they simply don't have enough manpower (2 or 3 devs for the entire project, I believe), and they are dealing with a ton of pre-existing/old legacy code/bugs, and I totally get it. I also totally get it with respect to the same code in Libreoffice, and from what I understand, that it is a huge monster of a code base. But all of that is really orthogonal to my main point... Software developers, whether volunteer or not, should have *some* level of responsibility and obligation on their part to fix bugs they themselves introduce into code they write. I know I would if I were one, and I know I do for anything that I do build. They write it - they should own it. I simply don't understand how anyone could believe otherwise. On 10/2/2014 5:57 PM, Joel Madero jmadero@gmail.com wrote: Um - well two points: 1. None of the paid developers are paid by TDF - we have 0 paid developers on staff. 2. Most commits are still done by volunteers and many are done by paid developers on their free time (ie. when they are volunteering). -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: MySQL native connector for LibreOffice 4.2 and 4.3 (Linux versions)
On 10/03/2014 06:07 AM, Heinrich Stöllinger wrote: Alex Thurgood schrieb: Le 03/10/2014 07:27, Alan B a écrit : Hi Alan, I have a database from the US gov't, npidata freely available, with about 3.5 million rows and around 350 columns. Actually the gov't provides a csv. Imported it into a MySQL db using the MySQL command line. Never been able to read the primary table using the Java connector. With the native MySQL Yeah, the whole Java connector thing within LibreOffice and large record sets is a very bad combination, even with a mysql backend ! I'm not surprised you couldn't read it with an array of data that big, even if each field only contained 1 byte :-) Glad that the native connector at least allows you to load the records :-)) Alex Hi Alex, I do have a long-time connection with ALL 3 kinds of MySQL connectors. Only the native one REALLY works o.k... There is one problem in MY case, however: My DB-Hosting facility specifies a connection time-out value of 1 minute. With the Java connector one can specify reconnect-true (or yes?) when defining the DB under LO. This means that LO at least re-connects after a termination of the connection by the server. This is NOT a good situation, but it is kind of acceptable. The native connector does NOT allow such a specification. This makes it unusable to me unfortunately. I hope that it might be possible to change this limitation of the native connector. Regards Heinrich This may not be much of a work a round. I have a database using MySQL 5.5 server that I leave open for long periods of time. So when I come back the database, I get the message: MySQL has gone away. Since the database is the only thing that I am using LibreOffice for at the time, I close the database rather than LibreOffice. This opens the Start window which contains a list of previously used files. I double click the name of the database, and I am reconnected. It even remembers the user name and password, so the database is opened and ready to use. Have you filed a bug report about this? Dan -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
On 10/2/2014 3:11 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote: Charles S. (aka Tanstaafl) was given instructions and has agreed to do what needs to be done and review the corrected function for his use case with a current build of master (4.4.0alpha0+)--and respond in the fdo#76565 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76565 BZ issue regards the UX regression. Fix confirmed (had some spare time this morning)... It was also mentioned in the bug that it would be back-ported to 4.3 (I guess not for 4.2, but thats ok)... -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Hi :) The 4.4.0 is due out fairly soon, within a month or so. It might be good to test-drive the alpha and beta release on 1 or 2 machines because they are generally stable enough for your own usage. Obviously don't roll-out until after 4.4.1 at the earliest if your users are likely to get stumped by the slightest issue. Many of us wait until much later in the cycle but tbh even the beta-releases are stable. It's a good idea to test-drive releases, in your own daily work, from as early as possible so that you can see if anything obvious is broken. Regards from Tom :) On 3 October 2014 17:25, Tanstaafl tansta...@libertytrek.org wrote: On 10/2/2014 3:11 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote: Charles S. (aka Tanstaafl) was given instructions and has agreed to do what needs to be done and review the corrected function for his use case with a current build of master (4.4.0alpha0+)--and respond in the fdo#76565 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76565 BZ issue regards the UX regression. Fix confirmed (had some spare time this morning)... It was also mentioned in the bug that it would be back-ported to 4.3 (I guess not for 4.2, but thats ok)... -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
On 10/3/2014 12:36 PM, Tom Davies tomc...@gmail.com wrote: It might be good to test-drive the alpha and beta release on 1 or 2 machines because they are generally stable enough for your own usage. I'm doing that now with this release - will change to a beta once it is available. Obviously don't roll-out until after 4.4.1 at the earliest For everyone else I always wait until at least the .3 or .4 release It's a good idea to test-drive releases, in your own daily work, from as early as possible so that you can see if anything obvious is broken. I know, but time is my biggest problem, and the fact is, this is the first time that I can remember ever having to roll back after beginning an upgrade rollout. Also, as I mentioned before, it is simply not possible to test every single feature - and reading the release notes is all fine and good - and I actually do (contrary to what someone seemed to be implying earlier), but the release notes is one big long page, and for 4.2, the note about the massively major (for those who use them) change from pop-up to inline editing of Input Fields consisted of one, single solitary line easily missed among everything else. Hence my comment that major changes like this should always be pre-announced on the users list (since, you know, it will kind of affect them). Anyway, I've got it setup now so I can easily install master builds if/when I need to test something. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
On 10/3/2014 12:35 PM, Florian Reisinger flo...@libreoffice.org wrote: Q: Why do not get bugs fixed at the moment they are reported? A: Before devs see the bug, it goes through the hands of QA. We are a small team and have a lot of backlog on reported bugs. (More bugs are reported than we are able to tackle) All well and good, but has nothing to do with what started the flamefest. 1. It took a few days in the bug to get it confirmed. 2. 3 *months* later, Joel asked a question making it very plain he did not bother to even read the bug report and subsequent comments 3. 1 month later, Jan-Marek posted a patch (thanks Jan-Marek!) 4. 1 month later the bug reporter asked (reasonably politely) if the fix would be back-ported to 4.3. 5. The same day Joel responded with a rude Feel free to submit a patch...' and more like it. So, it was confirmed very quickly. At that point, the dev who cause it should have been contacted to fix it, and that same dev should have taken ono the responsibility of pushing the fix to at least 4.3, if not also 4.2 (had it been fixed soon after being confirmed, it would have made more sense to push it to 4.2). Q: Why the hack did you tell someone to get some money in its hand to get it fixed? A: I hear such voices very often and got the same answer: Either help (so that others does not have to wait so long) or pay. Or continue hoping, that a dev will tackle your pet bug in its free time And yet again this comment totally ignores the fact that we are talking about newly contributed code (not some old/pre-existing/legacy bug), and that software developers should take ownership of their code. Q: I have a problem XYZ for months but I did not want to report a bug A: For us it is like the bug did not exist (ans answer to the next question) I have no problem reporting bugs, and have multiple times, so n/a... Q: I will argue for an hour, but won't check something gets confirmed in a few moments A: Everyone knowing how this is done will help you, if you ask... Apparently some of this is a language thing, so I'll give you some room. But I would seriously ask that you address your apparent unwillingness to differentiate between: a) new bugs that are introduced with new code from existing/current developers, and that these devs should 'own their code' - meaning be willing to fix bugs when they are confirmed *and* push the changes to the releases without resorting to responses suggesting users fix it themselves and/or pay someone else to do it, and b) and old/pre-existing/legacy bugs that were introduced by someone long gone... I ask again - are you in disagreement with the above? If so, please, by all means, attempt to explain how you can logically and rationally be in opposition to this principle. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
On 10/3/2014 12:25 PM, Tanstaafl tansta...@libertytrek.org wrote: On 10/2/2014 3:11 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote: Charles S. (aka Tanstaafl) was given instructions and has agreed to do what needs to be done and review the corrected function for his use case with a current build of master (4.4.0alpha0+)--and respond in the fdo#76565 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76565 BZ issue regards the UX regression. Fix confirmed (had some spare time this morning)... It was also mentioned in the bug that it would be back-ported to 4.3 Also, I'm confused... Jan-Marek in the bug comment on August 17th - well before the 'Hard code freeze' on September 1st for 4.3.2 (released on Sept 22nd - said that the patch would show up in the daily builds after that. So, I'm not complaining, I'm just asking - can someone who understands the dev process explain why this fix did not make it into 4.3.2? Thanks -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Hi, answer inline, Liebe Grüße, / Yours, Florian Reisinger Am 03.10.2014 um 19:08 schrieb Tanstaafl tansta...@libertytrek.org: On 10/3/2014 12:35 PM, Florian Reisinger flo...@libreoffice.org wrote: a) new bugs that are introduced with new code from existing/current developers, and that these devs should 'own their code' - meaning be willing to fix bugs when they are confirmed *and* push the changes to the releases without resorting to responses suggesting users fix it themselves and/or pay someone else to do it, and b) and old/pre-existing/legacy bugs that were introduced by someone long gone... I ask again - are you in disagreement with the above? If so, please, by all means, attempt to explain how you can logically and rationally be in opposition to this principle. Bugs are bugs. Bugs are not meant to be introduced. For developers and end users it one not matter, if the bug is in new code or not. Even if it seems to be in new code, how do you know? A bug corrected here can affect something on the other side of the codebase, which was fixed around to correct the wrong behavior. So, CORRECT might not always be the old state. It might be the new, with some crazy side effects. (Taking your example: I did not touch how to paste, how could I break it. [BTW: I thought I was too dumb to write into the new input field]) By all of this, why should dev A introduced a regression yesterday be more responsible then dev B which broke something 10 years ago? Both are basically the same, so why treat them different. Regressions are always bad, but neither dev A nor dev B wanted to break this... If you want the fix NOW (or backport, for which it is too late for 4.2 I guess) it might be wise to get in touch with someone paid (better words then you should invest into the fix or hope someone will do that for free :) [Backporting is boring and risky] Did that help? -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
I have no clue how my comment was rude, it's pretty standard in open source world to say that patches welcome or some variation. I'm unsubscribing though as I don't have the time nor energy to continue this and you seem to have more than enough of both to go around. Enjoy ranting on the thread. Best, Joel On 10/03/2014 10:14 AM, Tanstaafl wrote: On 10/3/2014 12:25 PM, Tanstaafl tansta...@libertytrek.org wrote: On 10/2/2014 3:11 PM, V Stuart Foote vstuart.fo...@utsa.edu wrote: Charles S. (aka Tanstaafl) was given instructions and has agreed to do what needs to be done and review the corrected function for his use case with a current build of master (4.4.0alpha0+)--and respond in the fdo#76565 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76565 BZ issue regards the UX regression. Fix confirmed (had some spare time this morning)... It was also mentioned in the bug that it would be back-ported to 4.3 Also, I'm confused... Jan-Marek in the bug comment on August 17th - well before the 'Hard code freeze' on September 1st for 4.3.2 (released on Sept 22nd - said that the patch would show up in the daily builds after that. So, I'm not complaining, I'm just asking - can someone who understands the dev process explain why this fix did not make it into 4.3.2? Thanks -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
On 10/3/2014 1:27 PM, Florian Reisinger flo...@libreoffice.org wrote: Bugs are bugs. Bugs are not meant to be introduced. I agree... your point? For developers and end users it one not matter, if the bug is in new code or not. True enough. Even if it seems to be in new code, how do you know? Maybe one clue is that it is a brand new feature that the developer created? A bug corrected here can affect something on the other side of the codebase, which was fixed around to correct the wrong behavior. Irrelevant. If a developer introduces a new inline editing *feature*, and it is discovered after the fact that something about this new feature is broken, it is on the developer who built it to fix it... PERIOD... regardless of if the broken code was introduced by them or is the result of some related code suffering from bit-rot somewhere else. It is the nature of software development (I happen to know enough about it to not be easily bamboozled by gobbledyspeak). Anything else would result in a finger-pointing madhouse. By all of this, why should dev A introduced a regression yesterday be more responsible then dev B which broke something 10 years ago? It is a simple matter of logic. If dev B is still around, then dev A should ping dev B to fix their code. If dev B is long gone, then dev A bears the burden of either finding and fixing dev B's code, or reverting their new code with the bug unless/until someone else comes along and fixes the bug. Both are basically the same, so why treat them different. You only treat them different if they are (ie, if one is no longer around). Regressions are always bad, but neither dev A nor dev B wanted to break this... sigh and again, no one said they did... If you want the fix NOW (or backport, for which it is too late for 4.2 I guess) it might be wise to get in touch with someone paid (better words then you should invest into the fix or hope someone will do that for free :) [Backporting is boring and risky] Did that help? Yep. You have made it plain that you don't think software developers are or should be held accountable in any way, shape or form for their code and/or for the parts of the code they choose to work on. Which means you are someone I would *never* choose to pay to fix a bug, because you would never sign the agreement that I would put in front of you requiring you to actually warrant the code you write, and fix any bugs (at no cost to me), regardless of when they are discovered (within reason - say one full release cycle). -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: How to handle regressions
Hi :) That all seems reasonable. It also seems like a good idea to regularly market the QA team in the Users List. New people with a variety of skills join this Mailing List all the time and many are looking for a way of contributing back to the project. It'd be kinda rude not to invite them in! I think more than 1/week might be tooo often and maybe even considered spam by some but 1/month might not be often enough to catch people before they wander off. The main difference with your post this time was that there wasn't even a hint of refusing to solve a person's bug unless they paid for it. Quite the opposite! Talking with people is quite an art and not one that many of us really expect from devs, especially when they have been deep into coding - nor from QA who may have been deep into fast filing - nor from documenters or translators who may have been deep into their equivalent of code. However, it's not unreasonable to expect marketeers and leaders to be able to talk to people without causing offence. Also, leaders kinda need to be able to solve conflicts, instead of creating them! At least within their own organisation and their own customers/users! Regards from Tom :) On 3 October 2014 17:35, Florian Reisinger flo...@libreoffice.org wrote: Hi, So beside of what was written I want to explain something. I do not know if I say it marketing-wise... But still... Q: Why do not get bugs fixed at the moment they are reported? A: Before devs see the bug, it goes through the hands of QA. We are a small team and have a lot of backlog on reported bugs. (More bugs are reported than we are able to tackle) Q: Why the hack did you tell someone to get some money in its hand to get it fixed? A: I hear such voices very often and got the same answer: Either help (so that others does not have to wait so long) or pay. Or continue hoping, that a dev will tackle your pet bug in its free time Q: I have a problem XYZ for months but I did not want to report a bug A: For us it is like the bug did not exist (ans answer to the next question) Q: I will argue for an hour, but won't check something gets confirmed in a few moments A: Everyone knowing how this is done will help you, if you ask... Sorry if I seemed rude... Liebe Grüße, / Yours, Florian Reisinger -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] zoom in and out bound to a key
Hello LO has a nice button down right which allows to zoom in and out using the mouse. However I would prefer to bind zoom in to a key and zoom out to another say Crt-+ and Crtl-- but when I go to Customize--View--Zoom in and bound it to say Crtl-+ nothing happens, Customize--View--what do I miss? thanks Uwe Brauer -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] zoom in and out bound to a key
Uwe Brauer wrote: Hello LO has a nice button down right which allows to zoom in and out using the mouse. However I would prefer to bind zoom in to a key and zoom out to another say Crt-+ and Crtl-- but when I go to Customize--View--Zoom in and bound it to say Crtl-+ nothing happens, Customize--View--what do I miss? thanks Uwe Brauer A couple of possibilities... 1. Your operating system might do something with those shortcut keys, and not pass them on to LibreOffice. 2. More likely - There are two levels of assigning shortcut keys in LibreOffice - those for the whole suite and those for an individual application. In the Customise Keyboard dialog, at the upper right, there is an option to flip between assignments for LibreOffice (the whole suite shortcuts) and Writer (or whichever application you're in). If the same shortcut key is defined for both, the one for an individual application takes priority when in that application. In Writer, Ctrl++ is assigned to Calculate and Ctrl+- is assigned to Optional hyphen (at least for me). If you assign those keys to zoom in and out at the LibreOffice level, they will not have that effect when in Writer; you'd need to remove the assignments from the Writer level (and likewise for Calc etc. if you want them to work there too). I hope that helps. Mark. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: MySQL native connector for LibreOffice 4.2 and 4.3 (Linux versions)
Dan Lewis schrieb: On 10/03/2014 06:07 AM, Heinrich Stöllinger wrote: Alex Thurgood schrieb: Le 03/10/2014 07:27, Alan B a écrit : Hi Alan, I have a database from the US gov't, npidata freely available, with about 3.5 million rows and around 350 columns. Actually the gov't provides a csv. Imported it into a MySQL db using the MySQL command line. Never been able to read the primary table using the Java connector. With the native MySQL Yeah, the whole Java connector thing within LibreOffice and large record sets is a very bad combination, even with a mysql backend ! I'm not surprised you couldn't read it with an array of data that big, even if each field only contained 1 byte :-) Glad that the native connector at least allows you to load the records :-)) Alex Hi Alex, I do have a long-time connection with ALL 3 kinds of MySQL connectors. Only the native one REALLY works o.k... There is one problem in MY case, however: My DB-Hosting facility specifies a connection time-out value of 1 minute. With the Java connector one can specify reconnect-true (or yes?) when defining the DB under LO. This means that LO at least re-connects after a termination of the connection by the server. This is NOT a good situation, but it is kind of acceptable. The native connector does NOT allow such a specification. This makes it unusable to me unfortunately. I hope that it might be possible to change this limitation of the native connector. Regards Heinrich This may not be much of a work a round. I have a database using MySQL 5.5 server that I leave open for long periods of time. So when I come back the database, I get the message: MySQL has gone away. Since the database is the only thing that I am using LibreOffice for at the time, I close the database rather than LibreOffice. This opens the Start window which contains a list of previously used files. I double click the name of the database, and I am reconnected. It even remembers the user name and password, so the database is opened and ready to use. Have you filed a bug report about this? Dan Hello Dan, I understand what you are telling me! However, a one-minute-timeout value (which I unfortunately cannot change since I don't have sysadmin access to the server) is simply too short. It means that it interrupts normal work far too often. Certainly one cannot go away for a coffee and excpect the server to still be connected!!! No, I haven't yet filed a bug report. Solving this issue (auto-reconnect) is probably more of an enhancement than a bug. However, I think I will follow your suggestion in any case. Regards Heinrich -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-users] Re: How to handle regressions
@Charles, *, Tanstaafl wrote Also, I'm confused... Jan-Marek in the bug comment on August 17th - well before the 'Hard code freeze' on September 1st for 4.3.2 (released on Sept 22nd - said that the patch would show up in the daily builds after that. So, I'm not complaining, I'm just asking - can someone who understands the dev process explain why this fix did not make it into 4.3.2? No worries, it can get a bit confusing about what commits are where and when. His would show up in the daily builds refereed only to master branch. To be clear, in the normal flow of things, majority of development is made by commits onto the master branch. That includes new features, or UX/UI tweaks or even patches to repair or revert regressions. The in-line field edits have been available for testing in master since the commit in August. So where it gets confusing is the master's relationship with prior releases. At present we have the 4.2 branch nearing its final bug-fix release and then EOL a month later, and the 4.3 branch with its third bug fix in the works. While commits to master can and do break things, in order to keep the code stable, patches committed to master require additional review and deliberation before being back-ported to a prior branch. As needed some work will be done directly on the older branches--but most is integrated into master first and ideally are fully tested there. Some times if dealing with an obvious regression with simple correction, the developer will put up the back-port for review immediately, but usually just one release back. At times the issue has technical dependencies and requires review and validation, and only then will the back-port be posted and again reviewed before it is committed. But occasionally the dev will simply overlook a good opportunity to resolve an issue on branches other than master--which is understandable as most developers are forward looking and framing the work to tackle the next feature or issue in queue. And that is where the user and QA community comes in, we have to stay up with the issues on the forum and in BZ and occasionally make comment regards opportunity that might otherwise be missed. For this issue--despite being on the 4.2 Most Annoying Bug list--once patched the back-port to 4.2 or to 4.3 for the in-line field editing was not pursued. In fact it was only proposed yesterday, meaning it missed 4.3.2 testing and build cycle. But when committed to the branch should make the 4.3.3 bug-fix cut. And, technically, it could still make the 4.2.7 final release, but that requires an exceptional approval by three devs or the Engineering Steering Committee. Jan-Marek G.'s proposed backport to 4.3 branch for the in-line field edits are up for code review, each of these is a separate facet of the patch needed for 4.3 (and possibly 4.2) as already implemented in master since August. https://gerrit.libreoffice.org/11779 https://gerrit.libreoffice.org/11780 https://gerrit.libreoffice.org/11781 https://gerrit.libreoffice.org/11782 If there are no technical issues, since the patch put into master in August was sound they'll likely be approved and committed in time for the next 4.3 release--but available for testing in context on nightly builds of the 4.3 branch once committed, i.e. they should be checked by users and QA for continued proper function. Hope that was clear enough for all. Stuart -- View this message in context: http://nabble.documentfoundation.org/How-to-handle-regressions-tp4124391p4124855.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-users] Re: [Base Database] How to open a particular form at startup ?
Hi Dan, Its good to know that Linux users can also use this technique. Regarding opening FMain, neptuneuk shows at the bottom of his post that this is achieved, (when the database initially opens), by clicking on Tools | Customise | Events and setting Open Document to call the macro that opens FMain. After that, when the database opens, it automatically displays FMain. Noel -- Marion Noel Lodge lodg...@gmail.com On 3 October 2014 23:13, Dan Lewis elderdanle...@gmail.com wrote: On 10/03/2014 08:27 AM, Marion Noel Lodge wrote: Hi, I have a macro similar to neptuneuk's that Alex pointed to, but I go one step further. I run Windows 7 64 bit. I right click on my project's .odb file, click on 'Send to' and then on 'Desktop (create shortcut)'. Then I can simply double click on the shortcut to go directly into my Main Menu form. Sometimes, usually if I have just started my PC, it's a bit slow and LibreOffice's initial menu appears for a few seconds before the Menu form is displayed. But once the machine has warmed up, double clicking on the shortcut displays the Menu almost immediately. I have found this is simpler for my users. It also keeps them away from the underlying LO menu and prevents them being confused by a screen that they don't need to be concerned about! I have several such shortcuts on my desktop and find the them faster than opening LibreOffice and going through several steps to select the .odb file I want to open. Don't know how well this would work on other operating systems, but it works well for me. Noel What Noel has done also works with Linux by creating a soft link to the database on the Desktop. Then double clicking the link causes the database to open. Similarly, creating a soft link to a folder containing the databases that are often used can be used. Then double clicking the link and then double clicking the name of the desired database will accomplish the same thing. But I do not think this is what the OP was wanting. When the database opens, he wants the form named, FMain, to open as well as the main database window. Obviously, he would want the window containing the FMain form to be on top. Dan -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to- unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
