FLOSS Project Planets

Gunnar Wolf: LIDSOL: teaching privacy and anonymity concepts and tools to social scientists

Planet Debian - Sun, 2019-06-23 23:46

I have been working on several privacy/anonymity topics in the past couple of years. And I am very happy, as we just achieved one of our most important stated goals.

I am coordinating LIDSOL, Laboratorio de Investigación y Desarrollo de Software Libre, at the Engineering Faculty, UNAM. LIDSOL is a very interesting and very open lab regularly inhabited by ≈7 bright students, most of them from Computer Engineering (but some from other careers in the faculty), and with over twenty years of history. And I have worked with several of them in my PAPIME project for privacy and anonymity. This time, the task was –after working a year on the broad topic– for the students to plan and present a course titled Privacidad y anonimato para un manejo seguro de mi información en redes» — Privacy and anonymity for safely handling my online information, as part of the Political and Social Sciences Faculty's intersemestral courses on technological updating.

The covered program was quite ambitious; I'm not translating it, you can look at it in Spanish in the course's information. The LIDSOL instructors (please, a round of applause for them!) were:

  • Diego Barriga
  • Emilio Cabrera
  • Marco Ruano

My friend Lourdes Reséndiz, who works at FCPyS and got us the space to present the course, also gave a module.

Lourdes, during the famous three envelopes dynamic for explaining onion routing

I felt the course to be a great success, and we were asked to repeat it in the future. As any course presenting anonymization technologies, it was of course not without its controversy and discussion — which was great! I think we got many concepts clarified for the attendees. I will later report on any measurable accounts we got, of course!

AttachmentSize grupo_priv.1500.jpg835.55 KB 2019-II Cedula - Privacidad y anonimato para un manejo seguro de mi información en redes.pdf96.53 KB introd.1500.jpg365.73 KB tres-sobres.1500.jpg382.81 KB
Categories: FLOSS Project Planets

Podcast.__init__: Behind The Scenes At The Python Software Foundation

Planet Python - Sun, 2019-06-23 22:32
One of the secrets of the success of Python the language is the tireless efforts of the people who work with and for the Python Software Foundation. They have made it their mission to ensure the continued growth and success of the language and its community. In this episode Ewa Jodlowska, the executive director of the PSF, discusses the history of the foundation, the services and support that they provide to the community and language, and how you can help them succeed in their mission.Summary

One of the secrets of the success of Python the language is the tireless efforts of the people who work with and for the Python Software Foundation. They have made it their mission to ensure the continued growth and success of the language and its community. In this episode Ewa Jodlowska, the executive director of the PSF, discusses the history of the foundation, the services and support that they provide to the community and language, and how you can help them succeed in their mission.

  • Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
  • When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With 200 Gbit/s private networking, scalable shared block storage, node balancers, and a 40 Gbit/s public network, all controlled by a brand new API you’ve got everything you need to scale up. And for your tasks that need fast computation, such as training machine learning models, they just launched dedicated CPU instances. Go to pythonpodcast.com/linode to get a $20 credit and launch a new server in under a minute. And don’t forget to thank them for their continued support of this show!
  • And to keep track of how your team is progressing on building new features and squashing bugs, you need a project management system designed by software engineers, for software engineers. Clubhouse lets you craft a workflow that fits your style, including per-team tasks, cross-project epics, a large suite of pre-built integrations, and a simple API for crafting your own. With such an intuitive tool it’s easy to make sure that everyone in the business is on the same page. Podcast.init listeners get 2 months free on any plan by going to pythonpodcast.com/clubhouse today and signing up for a trial.
  • Bots and automation are taking over whole categories of online interaction. Discover.bot is an online community designed to serve as a platform-agnostic digital space for bot developers and enthusiasts of all skill levels to learn from one another, share their stories, and move the conversation forward together. They regularly publish guides and resources to help you learn about topics such as bot development, using them for business, and the latest in chatbot news. For newcomers to the space they have the Beginners Guide To Bots that will teach you the basics of how bots work, what they can do, and where they are developed and published. To help you choose the right framework and avoid the confusion about which NLU features and platform APIs you will need they have compiled a list of the major options and how they compare. Go to pythonpodcast.com/discoverbot today to get started and thank them for their support of the show.
  • You listen to this show to learn and stay up to date with the ways that Python is being used, including the latest in machine learning and data analysis. For even more opportunities to meet, listen, and learn from your peers you don’t want to miss out on this year’s conference season. We have partnered with organizations such as O’Reilly Media, Dataversity, and the Open Data Science Conference. Coming up this fall is the combined events of Graphorum and the Data Architecture Summit. The agendas have been announced and super early bird registration for up to $300 off is available until July 26th, with early bird pricing for up to $200 off through August 30th. Use the code BNLLC to get an additional 10% off any pass when you register. Go to pythonpodcast.com/conferences to learn more and take advantage of our partner discounts when you register.
  • Visit the site to subscribe to the show, sign up for the newsletter, and read the show notes. And if you have any questions, comments, or suggestions I would love to hear them. You can reach me on Twitter at @Podcast__init__ or email hosts@podcastinit.com)
  • To help other people find the show please leave a review on iTunes and tell your friends and co-workers
  • Join the community in the new Zulip chat workspace at pythonpodcast.com/chat
  • Your host as usual is Tobias Macey and today I’m interviewing Ewa Jodlowska about the Python Software Foundation and the role that it serves in the language and community
  • Introductions
  • How did you get introduced to Python?
  • Can you start by explaining what the PSF is for anyone who isn’t familiar with it?
    • How did you get involved with the PSF and what is your current role?
  • What was the motivation for creating the PSF?
  • What are the primary responsibilities of the PSF?
    • How has the scope and scale of the responsibilities for the PSF shifted in the years since its foundation?
  • What is the relationship between the PSF and the language core developers?
  • What are some reasons that someone would want to become a member of the PSF and what is involved in gaining membership?
  • What are the challenges confronted by you and the PSF, currently and in the recent past?
  • What are you most worried about and most proud of in the PSF, the core language, or the community?
  • What challenges or changes do you foresee for the PSF in the near to medium future?
  • What are some of the most interesting/unexpected/challenging lessons that you have learned while working with the PSF?
  • How are the PSF and the PSU (Python Secret Underground) related?
  • Outside of the PSF, how can the community contribute to the health and longevity of the language, its ecosystem, and its community?
Keep In Touch Picks Links

The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA

Categories: FLOSS Project Planets

Israel Fruchter: Introducing pytest-elk-reporter

Planet Python - Sun, 2019-06-23 20:00

tl;td: https://github.com/fruch/pytest-elk-reporter


Few years back I’ve wrote a post about how I’ve connected python based test to ELK setup - “ELK is fun”, it was using an xunit xml, parsing it and sending it via Logstash.

Over time I’ve learn a lot about ElasticSearch and it’s friend Kibana, using them as a tool to handle logs. and also as a backend for a search component on my previous job.

So now I know logstash isn’t needed for reporting test result, posting straight into elasticsearch is easier and gives you better control, ES is doing anything “automagiclly” anyhow nowadays.

What can it do ?
  • collect as much information as you can about one test results and running environment and send it to elasticsearch.
    • data like git commit/sha from current directory
    • jenkins environment variables, like job id and username triggered the job.
    • cool tracebacks which pytest excels at.
  • extend - let user configure (like target address and credentials) it from code, and add data of their own to each session or test.
Tricks I’ve picked on the way

Every time I start a new package, I learn a few new things, here’s a few I’m happy about this time:

  • Created the package with cookiecutter-pytest-plugin

  • I’m using pre-commit

    • black - instead of the old friend autopep8.

    • pylint in both python27 and python36 to keep the code clean of silly mistakes.

  • Travis

    build and test with Tox on all possible python versions.

    also uploading wheels to pypi based on tags.

    thanks to setuptools_scm version no need to edit files for setting version number.

  • Appveyor

    I also cover windows own little issue (non found so far).

  • Codecov

    really like that it can collect from multiple run, for example both linux and windows tests run, which helps to show the total coverage.

    got me to 93% line coverage (and going down as I add more code).

The bad stuff - a.k.a things I need to improve
  • Documentation - I’ve mostly wrote test, zero docs.

  • Name - it’s a bit boring, and might conflict with other plugins.

  • Kibana Dashboards examples

    I should really include some sample kibana dashboard to show the strength of it, it’s own test data is a bit boring.

  • auto generating and upload of docs

    I’ve tried using Travis Deploy to github Pages, didn’t exactly nailed, or got it working as I expect, maybe I should try readthedocs.

  • pytest-xdist

    I still need to test it with xdist, it’s going to make thing a more tricker, as usual.

What you should next

Go grab it, git it a star, fork it.

I’m waiting for your PRs, and your stories on how it’s help you tame a whole bunch of tests.

# forgot to show how to install :\ pip install pytest-elk-reporter
Categories: FLOSS Project Planets

Dirk Eddelbuettel: binb 0.0.4: Several nice improvements

Planet Debian - Sun, 2019-06-23 11:49

The fourth release of the binb package just arrived on CRAN. binb regroups four rather nice themes for writing LaTeX Beamer presentations much more easily in in (R)Markdown. As a teaser, a quick demo combining all four themes follows; documentation and examples are in the package.

This release brings a few nice pull requests. Rob Hyndman, improved the Monash theme. Johan Larsson added support for slide notes, pgfpages and beamer options. Joseph Stachelek corrected the date setting in the Presento theme to reflect the date from the YAML header.

Changes in binb version 0.0.4 (2018-06-23)
  • The Monash theme now has improved color theme handling (Rob Hyndman in #15)

  • The Monash them has a demo, a new tighttoc option and other small improvements (Rob Hyndman in #16).

  • A slide notes example was added to Metropolis, pgfpages can be used if present, beameroption was added to three templates (Johan Larsson in #17).

  • The Presento them now use the date from the yaml header (Joseph Stachelek in #18)

CRANberries provides the usual summary of changes to the previous version.

For questions or comments, please use the issue tracker off the GitHub repo.

This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.

Categories: FLOSS Project Planets

Srijan Technologies: #DCD19: A True Summer Delight!

Planet Drupal - Sun, 2019-06-23 09:56

The summer of 2019 gave a reason for the Delhiites to rejoice. This time as one of the most conspicuous open source technology events of India, DrupalCamp was back after a sabbatical of two years, in Delhi.

Categories: FLOSS Project Planets

Drupixels: First 5 Drupal 8 modules to install to make your life easy

Planet Drupal - Sun, 2019-06-23 09:04
Starting a new Drupal 8 project? And the first thing you might do is to install a module, but which one first. There are a few obvious ones to install and sometimes these have no relation with the functionality of your project but they always help you in the background.
Categories: FLOSS Project Planets

apl @ Savannah: GNU APL 1.8 Released

GNU Planet! - Sun, 2019-06-23 09:03

I am happy to announce that GNU APL 1.8 has been released.

GNU APL is a free implementation of the ISO standard 13751 aka.
"Programming Language APL, Extended",

This release contains:

  • bug fixes,
  • ⎕DLX (Donald Knuth's Dancing Links Algorithm),
  • ⎕FFT (fast fourier transforms; real, complex, and windows),
  • ⎕GTK (create GUI windows from APL),
  • ⎕RE (regular expressions), and
  • user-defined APL commands.

Also, you can now call GNU APL from Python.

Categories: FLOSS Project Planets

Skrooge 2.20.0 released

Planet KDE - Sun, 2019-06-23 05:49

The Skrooge Team announces the release 2.20.0 version of its popular Personal Finances Manager based on KDE Frameworks

  • Correction bug 406903: no message when Skrooge can't open .skg file given on command line
  • Correction bug 406904: skrooge command-line help "--+[URL]" doesn't match its behavior
  • Correction bug 406741: QFX Date Import
  • Correction bug 407280: Skrooge flatpak unintentionally builds unused tests
  • Correction bug 407279: Skrooge flatpak needs later libofx
  • Correction bug 407257: Importing GNUcash (Account name instead of AccountID)
  • Correction bug 409026: skrooge appdata.xml fails validation on flathub, needs release and content_rating tags
  • Correction: aqbanking corrections:
    • Added auto repair for certain banks (Sprada, Netbank, Comdirect).
    • Added --disable-auto-repair command line option
    • Added --prefer-valutadate command line option
    • Removed --balance command line option
  • Correction: getNetWorth (used to compute PFS) is now computed by using all accounts
  • Correction: Remove color of hyperlinks in dashboard for a better rendering in dark theme
  • Correction: Remove broken quotes sources (BitcoinAverage, BitcoinCharts)
  • Correction: Better handling of the mode and comment field using the aqbanking import backend.
  • Feature: New REGEXPCAPTURE operator in "Search & Process" to capture a value by regular expression
  • Feature: Import backend aqbanking allows to import accounts without an IBAN. (See https://phabricator.kde.org/D20875)
Get it, Try it, Love it...

Grab Skrooge from your distro's packaging system. If it is not yet included in repositories, go get it from our website, and bug your favorite distro for inclusion.

Now, you can try the appimage or the flatpak too !

If you want to help me to industrialise the windows version, you can get it from here: https://binary-factory.kde.org/job/Skrooge_Nightly_mingw64/

Get Involved

To enhance Skrooge, we need you ! There are many ways you can help us:

  • Submit bug reports
  • Discuss on the KDE forum
  • Contact us, give us your ideas, explain us where we can improve...
  • Can you design good interfaces ? Can you code ? Have webmaster skills ? Are you a billionaire looking for a worthy investment ? We will be very pleased in welcoming you in the skrooge team, contact us !
Categories: FLOSS Project Planets

New website for Konsole

Planet KDE - Sun, 2019-06-23 05:00

Yesterday, konsole.kde.org got a new website.

Doesn’t it look nice? As a reminder the old website looked like this.

The design is very similar to the kontact.kde.org and kde.org websites.

The content could probably still need some improvements, so if you find typos or want to improve the wording of a sentence, please get in touch with KDE Promo. The good news is that you don’t need to be a programmer for this.

Community goal

With Jonathan Riddell, we proposed a new community goal: KDE is All About the Apps.

One part of this goal is to provide a better infrastructure and promotional material for the KDE applications (notice the lowercase a). I think websites are important to let people know about our amazing applications.

So if you are maintaining a KDE applications and want a new shinning website, please contact me. And I will try to setup for you a new websites, following the general design.

Technical details

The new website uses Jekyll to render static html. Because the layout and the design aren’t unique to konsole.kde.org, I created a special Jekyll located at invent.kde.org/websites/jekyll-kde-theme, so that only the content and some configuration files are located in the websites/konsole-kde-org repository. This make it easier to maintain and will make it easier to change others website in the future without repeating ourself.

This was a bit harder to deploy than I first though, I had problem with installing my Jekyll theme in the docker image, but after the third or fourth try, it worked and then I had an encoding issue, that wasn’t present on my development machine.

How can I help?

Help is always welcome, the KDE community develops more than 200 different applications, and even though not all applications need or want a new modern website, there is tons of work to do.

If you are a web developer, you can help in the development of new website or in improving the Jekyll theme. Internalization, localization and accessibility still need to be implemented.

If you are not a web developer, but a web designer, I’m sure there is room for improvement in our theme. And it can be interesting to have small variations across the different websites.

And if you are neither a designer nor a developer, there is still tons of work with writing content and taking good looking screenshots. For the screenshots, you don’t even need to have a good English.

If you have question, you can as always contact me in Mastodon at @carl@linuxrocks.online or with matrix at @carl:kde.org.

You can discuss this post in reddit or mastodon.

Categories: FLOSS Project Planets

Srijan Technologies: Should You Migrate Your Developer Portal To Drupal 8?

Planet Drupal - Sun, 2019-06-23 04:23

APIGEE recently announced - from May 31, 2020, Apigee-sponsored hosting for Drupal-based portals will end. The existing customers who wish to remain on Drupal 7 need to assume hosting responsibility, they can either migrate to Drupal 8 or move to Apigee's integrated portal.

Categories: FLOSS Project Planets

KDE Usability & Productivity: Week 76

Planet KDE - Sun, 2019-06-23 03:19

Week 76 in KDE’s Usability & Productivity initiative is here! This week’s progress report includes the first several days of the Usability & Productivity sprint, and as such, it’s absolutely overflowing with cool stuff!

New Features Bugfixes & Performance Improvements User Interface Improvements

Next week, your name could be in this list! Not sure how? Just ask! I’ve helped mentor a number of new contributors recently and I’d love to help you, too! You can also check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

If you find KDE software useful, consider making a donation to the KDE e.V. foundation.

Categories: FLOSS Project Planets

KStars v3.3.1 is released

Planet KDE - Sun, 2019-06-23 01:37
KStars v3.3.1 is released for Windows, MacOS, and Linux on all platforms (Intel/AMD and ARM). This is yet another maintenance release with a few new experimental features and addons.

MacOS Updates
Robert Lancaster cleared all the issues reported on astrometry.net problems on MacOS. After gathering the feedback of users with experimental releases on this dedicated INDI thread.

Astrometry on MacOS
Furthermore, DBus is now working again in this release which would make the Ekos Scheduler operational again under Mac.

New Observatory Module
Wolfgang Reissenberger developed a new Ekos Observatory module to manage the dome and weather-triggered shutdown procedure. This is the first iteration of the module with more expected in the upcoming months but it provides a compact and friendly interface to observatory management. Feedback is welcome.

Meridian Flip is gone!
Well, sorta of. Wolfgang Reissenberger removed Meridian Flip from the Capture Module and moved it to the Mount Module. This way the meridian flip can be controlled even if there is no active capture session going on.

So just set when you want the meridian flip to occur at the mount module. Remember that the setting is in Hour Angle (HA). 1 HA = 15 degrees, therefore 0.1 HA = 1.5 degrees West of the Meridian. 
Always use a positive value to ensure proper meridian flip takes place. Using zero could theoretically work but it is at the very edge where the decision to flip or not is made by the mount, so it's safer to use a slightly higher value like 0.1 HA.
Stream Window

Due to popular demand, the FPS control in the Stream window is replaced Frame Duration in seconds control. So a setting of 0.1 seconds would yield a frame rate of 10 FPS (1/0.1 = 10) if the hardware can support that. The duration can be set as low as 1 microsecond but only if supported by the driver and camera!

Other highlights:

  • Reset focus frame when mount slews.
  • Do not abort PHD2 guiding while suspended.
  • Switching to homebrew, python3, and astroy for plate solving on OS X.
  • Check if dust cap is detected before checking whether the camera is shutterful or shutterless.
  • Fix translation issue with Sun, Moon, and Earth designations.
Categories: FLOSS Project Planets

Support for Jupyter notebooks has evolved in Cantor

Planet KDE - Sat, 2019-06-22 16:19

Hello everyone, it's been almost a month since my last post and there are a lot of changes that have been done since then.

First, what I called the "minimal plan" is arleady done! Cantor can now load Jupyter notebooks and save the currently opened document in Jupyter format.

Below you can see how one of the Jypiter notebooks I'm using for test purposes (I have mentioned them in previous post) looks in Jupyter and in Cantor.

As you can see, there aren't many differences in the representation of the content except of some minor differences in the rendering of the markdown code.

For the comparison, I also prepared some previews of the same fragments of the notebooks, opened in Jupyter and in Cantor.
This is a fragment from Understanding evolutionary strategies and covariance matrix adaptation notebook.

As the next example, we show a screenshot of A Reaction-Diffusion Equation Solver in Python with Numpy notebook.

As the final example, we show a screenshot of Rigid-body transformations in a plane (2D) notebook.

To be more detailed and concrete on what is currently supported in Cantor, below is the list of objects that can be imported:
  • Markdown cells
    • With mathematical expressions
    • With attachments
  • Code cells
    • With text (including error messages) and image results)
  •  Raw NBConvert cells
Cantor is able to handle almost all content specified by Jupyter notebook format, except of some metadata information about the notebook in general and about its cells, information about the used "kernel" (support for this will be added soon) and results of another types (for example latex or html outputs), which are more difficult to implement because of the lack of good and complete documentation of them.

When saving the project in Jupyter's format, Cantor handles almost all of its native entry types like markdown entries, text entries, code entries and image entries. For the remaining "page break entry" in Cantor it is still to be worked out how to map this element to Jupyter's structures.

Despite quite a good progress made, there is still a lot place and potential for improvements. Besides some technical issues arising when dealing with the import of another format and mapping its sturcture to the native structures of your application, which is very natural actually for all applications I guess, there is currently also currently problem with perfromance of the renderer used for mathematical expressions in Cantor. Openning of large documents (either in Cantor's native format or Jupyter notebooks) having a lot of formulas takes considerable amount of time because of the bad renderer implementation in Cantor. This heavily influence the user experience and I plan to start working on this soon.

So, there are some work for done before Cantor will support what I call the "maximum plan". With this I understand the ability to garantee the conversion between two formats when openning or saving projects to happen without any substantial loss of information relevant and critical for the consumption of the project file.

To achieve this, I want now to invest more into testing with more notebooks and closing the remaining gaps but also into writing automatic tests for Cantor covering this new functionality in Cantor. The latter are important to also prevent any kind of regressions introduce during bug fixing activities in the next weeks. This is something for the next week.

In the next post I plan to show a working test system and how Cantor are passing its tests.
Categories: FLOSS Project Planets

AArch64 support for ELF Dissector

Planet KDE - Sat, 2019-06-22 06:00

After having been limited to maintenance for a while I finally got around to some feature work on ELF Dissector again this week, another side-project of mine I haven’t written about here yet. ELF Dissector is an inspection tool for the internals of ELF files, the file format used for executables and shared libraries on Linux and a few other operating systems.

Use Cases

As a quick introduction, let’s focus on what ELF Dissector is most useful for.

  • Inspecting forward and backward dependencies, on library and symbol level. Say you want to remove the dependency on a legacy library like KDELibs4Support from your application, the inverse dependency viewer helps you to identify what exactly pulls in this library, and which symbols are used from it.
  • Identifying load-time performance bottlenecks such as expensive static constructors or excessive relocations. An example for this is David Edmundson’s current research into KInit.
  • Size profiling of ELF files. That’s easiest shown in the picture below.
ELF Dissector size tree map view. AArch64 Support

Last week I had to analyze 64bit ARM binaries with ELF Dissector for the first time, which made me run into an old limitation of ELF Dissector’s disassembler. Until now ELF Dissector used Binutils for this (via some semi-public API), which works very well but unfortunately only on the host platform (that is, usually for x86 code). So this limitation finally needed to go.

We now have support for using the cross-platform disassembler framework Capstone. So far only AArch64 and x86 support are actually implemented, but adding further architectures is now quite straightforward. Together with a few other fixes and improvements, such as support for relocations in the .init_array section, ELF Dissector is now actually useful for inspecting loading performance of Aarch64 binaries too.

ELF Dissector showing AArch64 assembler. Outlook

ELF Dissector had its first commit more than six years ago, but it is still lingering around in a playground repository, which doesn’t really do it justice. One major blocker for making it painlessly distributable however are its dependencies on private Binutils/GCC API. Using the Capstone disassembler is therefore also a big step towards addressing that, now only the use of the demangler API remains.

Categories: FLOSS Project Planets

denemo @ Savannah: Release 2.3 is imminent - please test.

GNU Planet! - Sat, 2019-06-22 05:29

New Features
    Seek Locations in Scores
        Specify type of object sought
        Or valid note range
        Or any custom condition
        Creates a clickable list of locations
        Each location is removed from list once visited
    Syntax highlighting in LilyPond view
    Playback Start/End markers draggable
    Source window navigation by page number
        Page number always visible
    Rapid marking of passages
    Two-chord Tremolos
    Allowing breaks at half-measure for whole movement
        Also breaks at every beat
        Mark Passages of music
        Perform tasks on the marked passages
        Swapping musical material with staff below implemented
    Search for lost scores
        Searches whole directory hierarchy
        Works for transposed scores
    Compare Scores
    Index Collection of Scores
        All scores below a start directory indexed
        Index includes typeset incipit for music
        Title, Composer, Instrumentation, Score Comment fields
        Sort by composer surname
        Filter by any Scheme condition
        Open files by clicking on them in Index
    Intelligent File Opening
        Re-interprets file paths for moved file systems
    Improved Score etc editor appearance
    Print History
        History records what part of the score was printed
        Date and printer included
    Improvements to Scheme Editor
        Title bar shows open file
        Save dialog gives help
    Colors now differentiate palettes, titles etc. in main display
    Swapping Display and Source positions
        for switching between entering music and editing
        a single keypress or MIDI command
    Activate object from keyboard
        Fn2 key equivalent to mouse-right click
        Shift and Control right-click via Shift-Fn2 and Control-Fn2
    Help via Email
    Auto-translation to Spanish

Bug Fixes

    Adding buttons to palettes no longer brings hidden buttons back

    MIDI playback of empty measures containing non-notes

    Instrument name with Ambitus clash in staff properties menu fixed

    Visibility of emmentaler glyphs fixed

    Update of layout on staff to voice change

    Open Recent anomalies fixed

    Failures to translate menu titles and palettes fixed

Categories: FLOSS Project Planets

Crazy Last Weeks

Planet KDE - Fri, 2019-06-21 20:00

Last weeks have been crazy for me. Since the GSoC began, I have been rushing everything related to university and my life to dedicate exclusively to the development. Besides the two classes I was taking, Static Code Analysis and Approximation Algorithms, I had my obligatory teaching internship in Project and Analysis of Algorithms for the postgraduate program, where I was responsible for creating and evaluating assignments for 50+ students and answering general questions.

Besides that, I was in the organization of the Latin & American Algorithms, Graphs and Optimization Symposium during June 2nd to 7th, where I was responsible for a plethora of things before and during the event (Although it was a lot of fun, a lot of researchers from all around the globe and incredible research). And, just as I got back, I had to delve back to tests, assignments, seminars…

One of the problems for brazilians in taking the GSoC is that the beginning of the program does not match exactly with the end of our classes. But now, as everything is (finally!) ending, I can focus entirely in the GSoC and my project. Just before the GSoC (and before even creating my project), I had compiled to KDE Framework 5 and the ROCS software, so most of the development environment was already set.

I am using as my environment the Qt Creator, and I am focusing in the algorithm for creation of specific graph classes inside the generategraphwidget. I have already implemented algorithms for Paths, Complete and Complete Bipartite graphs, besides fixing some details here and there. These modifications are still only in my local machine, as I am having some problems pushing the commits (I must be doing something wrong in my configuration).

I noticed that the calculation of the position of the graphs generated is strange, as it put the graphs almost ouside the view (and we can’t push the view there), so probably the positioning must be corrected. There is a function for calculating the center there, I will compare that function to the point where the view always come back and adjust accordingly. Another detail is the symbols of the view tools, that are not showing correctly.

Categories: FLOSS Project Planets

Latte and "Flexible" settings...

Planet KDE - Fri, 2019-06-21 17:57

Following Latte and a "Shared Layouts" dream,  today I am going to present you all the new settings pages for upcoming v0.9 and the approach used for them. In following screenshots you can find Basic and Advanced pages for docks and panels.

Basic Settings
Advanced Settings

Flexible Settings

Latte v0.9 changed the approach between Basic/Advanced settings. Following the  Deepin paradigm our advanced mode is now using all the available screen height by taking into account surrounding latte dock/panels in order to not overlap. At the same time advanced settings window is moved at a screen edge in order to free up main screen area for the user. All settings windows now follow a more flexible design in order to provide different width/height scales at per screen basis.
  • Above free areas in settings window you can use Meta+Scroll wheel to alter window width scale
  • Above free areas in settings window you can use Ctrl+Scroll wheel to alter window height scale (only in Basic mode)
  • If you click Latte trademark you can access Latte Global Preferences window

Advanced Settings in 64% width scale

Edit Mode is Split at "Live Editing" and "Configure Applets"

From earlier Latte versions it was obvious that users wanted to be able to alter settings and check runtime how things behave and look afterwards (including the parabolic effect). This is why Latte Editing mode was split in "Live Editing" and "Configure Applets"

"Live Editing" mode
In this mode users can check settings in runtime. This state is active when "Rearrange and configure your widgets" button is not pressed. At the same time users can adjust the edit background opacity when  scrolling above empty areas.
"Live Editing" with fully transparent edit background
"Live Editing" with 50% transparency for edit background
"Configure Applets" mode

In this mode users can delete/configure and move applets around. This state is active when the "Rearrange and configure your widgets" button is pressed. In this mode edit background is solid at all times. Applet tooltips that appear on hovering provide you the following options:"Configure Applets" mode and Application Launcher applet edit mode tooltip
Popup improvements

In order to improve the settings experience a little more, some of the ComboBoxes popups have gained icons/tooltips and enhanced their behavior

Dock Actions popupIndicators popup

Global Preferences

Layouts page has also been improved a lot and its comboboxes should behave a lot better now. Most notable addition is Shared Layouts support for Multiple Layouts mode.

"TopPanel" layout shared to "My Profile" and "Unity Dream"

Global Preferences page provides new options for Meta key behavior and global outline width for panel backgrounds
Global Preferences options

Command Line
New options have been added in command line in order to enhance interaction with Latte, import layouts or settings/clear qml cache etc.
command line options

Latte v0.9 Release Schedule

  • End June 2019: last stable release for v0.8 [0.8.9]
  • Mid July 2019: v0.9 Beta release
  • End July 2019: bugs / translation strings fixes  and improvements
  • Start August 2019:  v0.9 will be released officially as the new Latte stable version

How Can You Help

  1. As you may noticed plenty new settings are added and bugs in their combinations may exist that have not been reported yet
  2. For complicated settings I use tooltips in order to describe them better. If you find such option that has not any tooltip OR its tooltip text can be explained more or be simplified feel free to report it (I am not a native english speaker)


You can find Latte at Liberapay if you want to support,    

or you can split your donation between my active projects in kde store.
Categories: FLOSS Project Planets

Codementor: Creating a new Flask project with pipenv

Planet Python - Fri, 2019-06-21 17:14
Creating a new Flask project with pipenv
Categories: FLOSS Project Planets

Yasoob Khalid: Setting up dev environment for SciPy

Planet Python - Fri, 2019-06-21 17:03

Hi everyone!

I got an email from someone pretty recently who wanted to setup a dev environment for SciPy. He had made changes to the source code of SciPy and now wanted to test if his changes were working or not. He had gotten so far without actually testing the code. In this post I will share details on how to setup a dev environment the right way. I will focus mainly on Mac OS.

Firstly, go to the GitHub repo and try to figure out the dependencies for the project. Normally they are listed in the readme file. If they are not listed there then you just try installing the package/libary and the errors in the terminal will give you a clue as to what you are missing. I did that and figured out that I needed Fortran compiler, Cython and NumPy.

Installing dependencies:

Let’s start with Fortran:

brew install gcc

Now create a new folder and setup a virtualenv there:

mkdir ~/dev cd ~/dev python -m venv env

Activate the virtualenv:

source env/bin/activate

Now install Cython and NumPy:

pip install cython pip install numpy

Now clone SciPy:

git clone git@github.com:scipy/scipy.git

And finally install SciPy in development mode:

cd scipy python setup.py develop

Normally if you are installing a Python package using the setup.py file, you use python setup.py install. This copies the code into the site-packages directory. After that if you make any changes to the source code of the package, you need to run python setup.py install each time.

The difference between that and python setup.py develop is that in the later case Python does not copy the code to site-packages. It uses the code from that development folder directly whenever you import the package. This way if you make any changes to the package you don’t need to run python setup.py install or python setup.py develop.

After you are done with the development you can safely type deactivate and this will turn off the virtualenv.

You can read more about virtualenv on Real Python. I hope someone out there in the same boat as one of my other readers finds this helpful.

Have a good day!


Categories: FLOSS Project Planets