One or more "See Also" fields of the bugzilla (top-right side) are useful points of integration. Example: link, see the screenshot below.
Unfortunately the opposite way does not work yet: Phabricator won't display bugzilla links. But if you use the "BUG:____" lines in your git commit messages they at least appear in summaries of Differential revisions (example).
Thanks to Ben who tirelessly enabled the links.
PS: These weeks mark end of my 13rd year in KDE!
Well, today I wrote 2 articles, and why not write another one?
On this week, I’m working very hard on my proposal to Google Summer of Code, and to say some things there, I needed to know better the others printers hosts open sources.
I choose 3 to start: PronterFace, MatterControl and Repetier Host.
Only opening this programms, I already get confused, cause, where are the settings? Where are the controls? Isn’t easy to find.
So I made this comparisons between this softwares:
Obviously, the actual state of the user interface of Br-Print3D isn’t finished yet. Like the loading of the gcode file that have flaws that I want to resolve in a few weeks, but I think that you can see the difference between Br-Print3D and the above printer hosts.
And I feel that whe are making easy the way that the user can use a printer host. With the experiences that I had with this others, I really enjoy use Br-Print. But i’m a suspect to talk. =D
So, just looking at the pictures above, what do you think?
We are pleased to announce availability of the Calligra Suite, and Calligra Active 2.9.11. It is recommended update for the 2.9 series of the applications and underlying development frameworks.Support Calligra! Bug fixes in This Release
You will find most of the improvements in Krita and Kexi. There are several others that may be not mentioned here.General
- A number of fixes for charts (review 122153).
Featured story: A commercially developed upgrade for MS Access (MDB) Import to Kexi has been donated by Jarosław Staniek (wish 277583). This also fixes import of primary keys (bug 336560). Large Access databases such as the Northwind sample now import better than ever.
- Main Window:
- Make Global Search list should wider to fit the names (bug 358203).
- Make the default “Smallest readable font” used by Kexi in property editor, toolbar, etc.; allow to specify size using points; no longer depend on screen resolution (bug 358662).
- Do not switch to Data View if fetching records failed, and show more clear message. This fixes crash at the attempt to create a table row when table is invalid due to use of a reserved word or failed data fetching (bugs 356888 and 357025). The same category of errors are now also fixed for queries, forms, reports, and CSV export.
- Fix alignment of table view combo boxes when rows or columns are scrolled (bug 357655).
- Make combo box popups for tabular view fit in the current screen (bug 357682).
- Switching off the visibility of query fields no longer hides data in the last field. This is a fix for SQLite, MySQL, PostreSQL, Sybase/MSSQL (bug 346839).
- Fix possible crash due to missing removal of cached field information.
- Support queries having the same field name used in multiple tables (bug 340056).
- Make "Save button" enabled when going from SQL view to Data and back to SQL (bug 278379).
- Fix: Changes in query design not retained after changes in SQL view and switching to Data view (bug 358413).
- Make <SELECT “a” + “b”> SQL queries work; also for convenience if either argument is of text type, operator “+” is now assumed to be identical to operator “||”; also fix <SELECT “a” || “b”> for MySQL using CONCAT() (bug 358636).
- Better check result of parsing SQL statements.
- Make query parameters also work in COLUMNS section, e.g. <SELECT [Param]> works now (bug 348473).
- Fix switching to Data View when using table aliases (bug 278414).
- Add sorting to Forms. Current record is unchanged but its index most likely changes, what can be observed in the record navigator (bug 150372).
- Fix retrieval of aggregate report values for queries: fix possible crash when changing data source, support tables and queries having the same names, better recognize if report was modified (reviews D764 and D765).
- Fix handling latitude property for scripting in Report Map element.
- Fix possible memory leaks (review D780).
- Allow jump to report page (bug 357217).
- Fix a memory leak when images are copied to the cliboard
- Ask the user to wait or break off a long-running operation before saving a document
- Update to G’Mic 1.6.9-pre
- Fix rendering of layer styles
- Fix a possible issue when loading files with clone layers
- Do not crash if there are monitors with negative numbers
- Make sure the crop tool always uses the correct image size
- Fix a crash on closing images while a long-running operation is still working
- Link to the right JPEG library
- Fix the application icon
- Fix switching colors with X after using V to temporarily enable the line tool
- Fix the unreadable close button on the splash screen when using a light theme
- Fix the Pencil 2B preset
- Fix the 16f grayscale colorspace to use the right channel positions
- Add shortcuts to lower/raise the current layer
- Fix calculation of WEEKSINYEAR() function, December 31 should not belong to first week of next year.
- Fix Table of Contents generation for Okular ODT generator.
The source code of the release is available for download here: calligra-2.9.11.tar.xz.
Also translations to many languages and MD5 sums.
Alternatively, you can download binaries for many Linux distributions and for Windows (users: feel free to update that page).
The next step after the 2.9 series is Calligra 3.0 which will be based on new technologies. We expect it later in 2016.
You can meet us to share your thoughts or offer your support on general Calligra forums or dedicated to Kexi or Krita. Many improvements are only possible thanks to the fact that we’re working together within the awesome community.(Some Calligra apps need new maintainers, you can become one, it’s fun!) How and Why to Support Calligra?
Calligra apps may be totally free, but their development is costly. Power, hardware, office space, internet access, travelling for meetings – everything costs. Direct donation is the easiest and fastest way to efficiently support your favourite applications. Everyone, regardless of any degree of involvement can do so. You can choose to:
Support entire Calligra indirectly by donating to KDE, the parent organization and community of Calligra: http://www.kde.org/community/donations.
Support Krita directly by donating to the Krita Foundation, to support Krita development in general or development of a specific feature: https://krita.org/support-us/donations.
Support Kexi directly by donating to its current BountySource fundraiser, supporting development of a specific feature, or the team in general: https://www.bountysource.com/teams/kexi. About the Calligra Suite
Calligra Suite is a graphic art and office suite developed by the KDE community. It is available for desktop PCs, tablet computers and smartphones. It contains applications for word processing, spreadsheets, presentation, databases, vector graphics and digital painting. For more information visit calligra.org.About KDE
KDE is an international technology team that creates free and open source software for desktop and portable computing. Among KDE’s products are a modern desktop system for Linux and UNIX platforms, comprehensive office productivity and groupware suites and hundreds of software titles in many categories including Internet, multimedia, entertainment, education, graphics and software development. KDE’s software available in more than 60 languages on Linux, BSD, Solaris, Windows and Mac OS X.
I've been asked recently why ownCloud zipps its files instead of tarring them. .tar preserves file permissions, for one, and with tar.gz or tar.bz2 you have compression too.
Good question. Let me start by noting that we actually have both: zip and tar.bz2. But why zip?
A long time ago and far, far awayIn the beginning, we used tar.bz2. As ownCloud gained Windows Server support, we added zip. Once we dropped Windows support, we could have killed the zip files. But we had reasons not to: tar is, sadly, not perfect.
Issues with TarYou see, tar isn't a single format or a 'real' standard. If you have a platform other than plain, modern Linux, think BSD or Solaris, or the weird things you can find on NAS devices, tar files can get you in trouble. Unlike zip, tar files also can have issues with character format support or deep folders. We've had situations where upgrades went wrong and during debugging we found that moving to zip solved the problem miraculously... And, as ownCloud, we're squarely focused on the practical user experience so we keep zip, alongside tar.bz2.
See also the GNU tar manual if you want to know more about the various tar formats and limitations.
Sadly, sometimes it is impossible to find one thing that works for everyone and in every situation.
Tarred turtle pic from wikimedia, Creative Commons license. Yes, that's a different tar, I know. But - save the turtles!
Most distro’s that ship Plasma Desktop as .. well, as a desktop to work in, have their own default wallpaper choice that isn’t exactly the upstream default. OpenSUSE has things with geekos (which I personally really like, for their understatedness). KDE neon goes for the upstream default, but that is the nature of that particular distro.
The FreeBSD packages of KDE4 had a nice variant of vertical blinds (here’s the OpenSUSE variant — FreeBSD is blue and with a FreeBSD logo). I think that was done by Ivan. However, we’re getting close to a release of Plasma 5 Desktop and workspaces as well as KDE Applications for FreeBSD, and it’s time to think of a new default wallpaper for the FreeBSD packages. Something lightly branded. So this here is a call for contributions for a KDE-FreeBSD wallpaper for use with the first (FreeBSD) release of the current generation of KDE software.
My Ruby Performance Optimization book is in print!
Honestly, it's old news. I was so excited to get the book out and ruby-performance-book.com up that I forgot to announce it here on my personal blog.
I'm proud to say that my Ruby Performance Optimization is the first book on Ruby and Rails performance that actually teaches performance optimization and is not a mere collection of tips and tricks.
Printed book costs $36. Make sure to check Amazon before you buy. They sometimes sell it for $30. There are also many offers for used books around $20. I don't really know where they come from. So if you buy one, please let me know how well that went.
Of course you can stil buy an ebook in epub, PDF, and Kindle (mobi) formats for just $24.Buy Now
So. I typo’ed up some template code the other day. And once again I learned the importance of using several c++ compilers.
Here is a very reduced version of my code:
template <typename T> auto foo(const T& t) -> decltype(x.first)
And let’s start with the compiler I was testing with first.
MSVC (2013 and 2015)
main.cpp(8): error C2672: ‘foo’: no matching overloaded function found
main.cpp(8): error C2893: Failed to specialize function template ‘unknown-type foo(const T &)’
It is not completely clear from that error message what’s going on, so let’s try some other compilers:
2 : error: ‘x’ was not declared in this scope
template <typename T> auto foo(const T& t) -> decltype(x.first)
That’s pretty clear. More compilers:
2 : error: use of undeclared identifier ‘x’
template <typename T> auto foo(const T& t) -> decltype(x.first)
example.cpp(2): error: identifier “x” is undefined
template <typename T> auto foo(const T& t) -> decltype(x.first)
(Yes. I mistyped the variable name used for decltype. Replacing the x with t makes it build).
Ansible does support Windows with an entire set of modules. Thus it is also possible to run Ansible playbooks targeting Windows systems right from Ansible Tower. However, since Windows does works via WinRM and not SSH, the appropriate variables must be set in the definition of the inventory of the machine:
The given screenshot shows the variables for Ansible 1.9. For 2.0 and above the variables are a bit different. Also, keep in mind that you might need to create an additional set of credentials.
Filed under: Fedora & RHEL, Linux, Microsoft, Shell, Short Tip, Technology
My name is Jóhann Örn Geirdal and I am a professional artist and a fine art gallery supervisor. I’m from Iceland and currently living in the Reykjavik city area.Do you paint professionally, as a hobby artist, or both?
I paint digital fine art professionally and it’s definitely my hobby as well.What genre(s) do you work in?
Everything that gets the job done.Whose work inspires you most — who are your role models as an artist?
The most important artists to me are Erro, Android Jones, Francis Bacon and Miro.How and when did you get to try digital painting for the first time?
Back in 2000 I went to a multimedia school to learn to make digital art. Since then I have switched completely to digital media from traditional media.What makes you choose digital over traditional painting?
Definitely the high level of experimentation and it’s a lot cleaner.How did you find out about Krita?
It was through the Blender community. The artist David Revoy introduced it.What was your first impression?
I did not fall in love with it but it was interesting enough to explore more. Now I can’t go back.What do you love about Krita?
It is simply the best digital art software on the market.What do you think needs improvement in Krita? Is there anything that really annoys you?
I think it’s on the right track. Just keep going.What sets Krita apart from the other tools that you use?
It’s the fast development and that the developers are definitely listening to the artists who use it. That is not always the case with other software.What techniques and brushes do you prefer to use?
I use a lot of custom brushes but I also use default Krita brushes and brushes from other artists.Where can people see more of your work?
My website is http://www.geirdal.is. There you can see my current work.Anything else you’d like to share?
I like to thank everyone who has made Krita possible and this amazing!
I have the pleasure to announce the releases of two new KDevelop versions:
On one hand, there is the new and shiny KDevelop 5.0 Beta 2 release, which brings us much closer to a final release. Tons of issues have been resolved, many features got polished, and even our UI cleaned up a bit here and there. And did I mention impoved OS X and Windows support? See here for more:
Besides this new beta release, which is where most of our effort went into, I am also happy to announce KDevelop 4.7.3, a new bugfix release of our latest stable KDE 4 based KDevelop. Several annoying problems are resolved now, see the announcement for more information:
Many thanks to everyone involved!
The process to submit a session proposal changed a little bit since the last summit. You have to provide more information like "What should attendees expect to learn?", "What is the problem or use case you’re addressing in this session?", "Why should this session be selected?", but also links to former presentations. And you can submit no more than 3 proposals. Personally I have to say: This is really an improvement, especially if this information also ends up in the voting process!
I myself work currently on a proposal to speak about "From Hardware to Application in a OpenStack and Ceph NFV cloud". I hope we will see many interesting proposals for Ceph related talks!
Dear digiKam fans and users,
digiKam team is proud to announce the release of digiKam Software Collection 5.0.0 beta3. This version is new stage to the long way to stabilize code of Qt5 port of next main digiKam release. See previous announcement about 5.0.0-beta2 release to know all details about code re-writing under progress.
I have been using git for years now, I think I can say I know the tool quite well, yet I do all my commits with git gui. This often surprises my coworkers because a) it looks a bit ugly and b) it's a graphical application! The horror!
This is what it looks like:
Yes, it's indeed a bit ugly, thanks to it using tcl-tk, just like its most widely known brother, gitk.
On the left side you can see two lists: the top list contains all your unstaged changes, the bottom list contains all your staged changes (ie: files which have been added with git add, or removed with git rm).
The right side, contains a large view which shows the change of the currently selected file and in the bottom a text area where you can enter your commit message as well as a few widgets to trigger different actions.
How does one uses it? Easy: to stage a file to commit click on the icon of the file in the top-left side: the file disappears from the top list and appears in the bottom one. If you click on the name of the file, it gets selected, and you can see the changes in the main area.Why use git gui instead of the command line?
For a few reasons: first it provides an easy way to review your commits before they get in. I have often caught a debug line I forgot to remove or some added trailing spaces while going through my changes this way.
Second, and most importantly, it is much easier to do partial commits with git gui. Partial commits, if you are not familiar with this, is the ability to commit only parts of a file. This (slightly controversial) feature is useful to clean up a commit or to break a set of unrelated changes in separate commits. Often necessary when I land back on Earth after a frenzy coding session. It's also useful to split commits when doing an interactive rebase.
The command-line way to do so is git add -p, but that is really tedious because it shows one hunk at a time, you don't have a global view of all the changes. With git gui you can just scroll the diff, just right-click on a change and select "Stage Hunk For Commit". If you change your mind, select the file in the Staged list, right click the staged hunk and select "Unstage Hunk From Commit".
It's even better when you want to do finer grained commits and stage only lines: with git add -p you have to edit diffs. That is really not efficient and very error prone. This is where git gui really shines: select the lines you want to commit (either additions or removals), right click and select "Stage Lines For Commit". Done.
In this little animation I create two commits from my current changes:
It works the other way as well: stage all the file or a few hunks, then right click on that debug line or that extra blank line and select "Unstage Line From Commit".
Here I remove a debug line after staging all changes:
It turns out that, at least for me, git gui is fast enough. It starts up instantly and has a set of shortcuts which makes it possible to do many operations without using the mouse. Here is the list of shortcuts I use most often:
- Ctrl+T/Ctrl+U: Stage/unstage selected file
- Ctrl+I: Stage all files (asks if you want to add new files if there are any)
- Ctrl+J: Revert changes
- Ctrl+Enter: Commit
- Ctrl+P: Push
I must confess I haven't tried a lot of other frontends. I played a bit with git cola a few years ago but I did not feel as productive as with git gui. There are probably nicer alternatives out there but one of the main advantages of git gui is that it is an official part of Git, so it is available wherever Git is available, I have used git gui on Windows and Mac OS X: it works just like on Linux.
KDE neon website is now live.
Serving the freshest packages of KDE software. Developers’ archive with packages built from KDE Git available now, stable archive with packages built from released tars coming soon.
Launch party tonight in La Paon, Grand Place, Brussels
(Under a .uk domain name until we finish the KDE incubation process.)by
When configuring saving settings for the JPEG format in the Saving Images section of the Configure digiKam window, you can choose between medium and high chroma subsampling, or disable it altogether.
But what is chroma subsampling and what does it do? As you may know, JPEG is a lossy format, which means that it trades quality for a smaller size. One of the methods for achieving a smaller size is to store color information (chroma) at a lower resolution than brightness (a.k.a intensity or luma) data. This is possible due to the fact that the human eye is less sensitive to color than brightness, so discarding color information doesn't produce a perceptible loss of quality.
since quite some time, there is a new feature in dolphin which helps to investigate the disk usage of the current directory (or mount point etc.). The feature is a bit hidden, so I decided to write this post:
Left-click on the disk space bar (located on the right side of dolphin’s status bar). The following menu opens, see screenshot:
The first two menu items open Filelight with different entry points (current folder or current mount point), the third one is KDiskFree. In a submenu, there are also other tools available.
One nice thing is that you can configure (via submenu More -> Configure…) which programs should be shown in the main menu and in which order. The others will be kept in the submenu. Even if a program is not installed you will find it in the submenu for you to discover.
Note, that in case Filelight is already installed, you can still (and could in the past) also reach it from the folders context menu -> “Open with” -> Filelight.
That’s it. If you happen to come across another program that could be useful in the disk usage context and you think it could also be useful for others, feel free to file a bug report (severity “wishlist”, topic “KMoreTools: new disk usage tool for dolphin: …”). If accepted, this program would then appear in the submenu for other users to be discovered and you could configure it to appear in the main menu.
Going to FOSDEM 2016, this weekend at ULB campus. Looking forward to the talks and meeting hackpeople.
KDE neon launches this weekend at FOSDEM.
The launch party is on Saturday in La Paon, Grand Place, still time to sign up if you want to come.
My talk is on Sunday in the desktop devroom at 12:45CET.
And I’ll be on the KDE stall in building K demoing it and talking about it to anyone who’s interested.
Holding website at http://neon.kde.org.uk/
And follow for news and updates on