Hi all,
Yesterday I published a short blog post about recording a screencast
(a desktop session) to create a video or an animated image.
So if you want to have nice animated images in READMES [1] or in pull requests [2]
then check this post [3].
Enjoy!
[1] https://github.com/lslezak/build-rake/blob/master/README.md
[2] https://github.com/yast/yast-registration/pull/240
[3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
...I want to make sure there is a solution that I simply have not yet found.
Expected (OK) fonts results (e.g.):
sw_single @120 DPI in KDE3 on 13.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png
sw_single @132 DPI in KF5 on TW:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png
Not expected (undersized) fonts results (e.g.):
sw_single @108 DPI in TDE on 13.2:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png
sw_single @120 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p…
sw_single @168 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p…
Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using
smaller fonts than those used in the y2 control center and in the rest of DE
UI, as if both the non-KF5 DE's font settings and QT's font setting in
Trolltech.conf are being disregarded.
Is there something that can be installed or removed to bring up font sizes to
match the rest of the DE and y2cc in KDE3 and TDE without loading the
installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a
bug that's already been filed, or one that needs filing?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
It looks like we have version conflicts in skelcd-control-openSUSE project
between "master"[1] and "openSUSE-42_2"[2] branches. After some discussion in
the IRC channel, Ladislav proposed to use the following schema:
* 42.2.99.X for tumbleweed (master)
* 42.2.X for openSUSE-42_2
If nobody objects, I would like to do the change next friday. Or maybe you
have a better idea.
Anyway, I'll bring the topic in the daily call so we can discuss it.
Regards,
Imo
[1] https://github.com/yast/skelcd-control-openSUSE/blob/master/package/
skelcd-control-openSUSE.changes
[2] https://github.com/yast/skelcd-control-openSUSE/blob/openSUSE-42_2/
package/skelcd-control-openSUSE.changes
--
Imobach González Sosa
YaST team at SUSE LINUX GmbH
Hi,
in last year we play a lot with different services and various
automatic checks for yast modules. I think it make sense that we after
SP2 and 42.2 branching start looking and discussing, what is useful,
what not and what is promissing.
Ideally if something is useful, then use it everywhere, if something is
not useful, then remove POC and if something is promising, then try to
invest time in its POC.
Reason why I mention it is, that I face it in last days few times, e.g.
that some modules do not use rubocop, so when I call rubocop
--auto-correct it basically destroy my changes, some modules do not
have spellchecker, so when we update in one module CONTRIBUTING.md, it
pass, but in other modules it cause crash as osc vc do not pass
spellchecker.
So I think we can start with discussion what is useful, what not now,
even before branching, so we can make conclusion and start working on
it. I will write down all projects I am aware of together with its POC
to see how it works. Feel free to react to any project how you see it
or add project if I forget any.
projects:
travis build - https://travis-ci.org/yast/yast-yast2 - currently used
only for ruby modules and in other projects in other languages
jenkins build for pull requests -
http://ci.opensuse.org/job/yast-registration-github-push/586//console -
currently only in few yast modules
coveralls - https://coveralls.io/r/yast/yast-yast2?branch=master -
currently in few yast modules, do not support c++
codecov - https://codecov.io/gh/yast/yast-bootloader/pull/355?src=pr
and https://codecov.io/gh/jreidinger/libstorage-ng/pull/1?src=pr -
currently only POC for bootloader and libstorage-ng
codeclimate - https://codeclimate.com/github/yast/yast-yast2 -
currently for few yast modules and other ruby projects, do not support
c++
codacy - https://www.codacy.com/app/YaST_Team/yast-bootloader/dashboard
- similar to codeclimate, only POC for bootloader, can integrate test
coverage, comment pull requests
inch - http://inch-ci.org/github/yast/yast-registration - checker for
documentation coverage, currently used only in yast2-registration
pullreview -
https://www.pullreview.com/github/yast/yast-registration/reviews/master
- sends mails to lslezak, currently only used in yast2-registration
rubylint - https://github.com/yast/yast-yast2/pull/480 - checker for
errors in ruby, currently only POC
rubocop - https://github.com/yast/yast-yast2/blob/master/.rubocop.yml -
currently used in many yast modules, but not all
spellchecking -
https://github.com/yast/yast-yast2/blob/master/.travis.yml#L10 -
currently in few yast modules
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
This is a call for papers for LinuxDays in Prague, October 8th - 9th,
one of the most important conferences about Linux in Czech Republic.
SUSE/openSUSE has some tracks there, but we ideally have more. Your
presentation can be in English or Czech. Most of attendees speak English
anyway.
See https://www.linuxdays.cz/2016/en/
I was thinking about some joint presentation made by two or more Yasties
or their users or even external contributors. We have done quite some
progress in the last year:
- SCRUM that actually works (even with bugs/fixing in the process)
- Blogging about our achievements
- New storage [WIP]
- Self-update
- Continuous integration, AY CI
- Automation in general
- Code quality checking
- ...
If you are interested or if you have any better idea (or if you have
doubts), let me know!
Thanks in advance
Lukas
--
Lukas Ocilka, Systems Management (Yast) Team Leader
SLE Department, SUSE Linux
https://en.wikipedia.org/wiki/Scout_Promise#Czech_Republichttp://www.scouting.org/Visitor/WhyScouting/ServingOthers.aspx
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org