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,
Following Richard Brown ( https://twitter.com/sysrich ) made me
notice a 58 minute presentation from a recent LinuxFest Northwest
2016 conference:
openQA - Avoiding Disasters of Biblical Proportions
https://www.youtube.com/watch?v=SyBIr_l-hjU
Of course you know what OpenQA does here but you may be interested
in seeing how it is used in Fedora, and feel proud about our
technology improving the world.
--
Martin Vidner, YaST Team
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
As mentioned in a call last week, we have been encouraged to move our
blog out of lizards.opensuse.org because there are plans to shut down
that service.
For me, the most obvious substitute would be just adding a blog section
to yast.github.io (that is, Jekyll + github pages).
It looks like is possible to enable rss for github pages and the only
missing part would be comments. Not that bad, since all the really
useful feedback we have gotten from the blog posts has always come from
the mailing lists, not from direct blog comments.
If we really want to have comments, there are solutions out there using
disqus or github issues[1][2]. Just google for something like
blog github pages
or
jekyll github comments
Looks like a candidate PBI for next sprint.
Cheers.
[1] https://github.com/mpalmer/jekyll-static-comments
[2]
http://ivanzuzak.info/2011/02/18/github-hosted-comments-for-github-hosted-b…
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
as you probably know I'm working on the Travis -> Jenkins CI switch for YaST.
Currently it's enabled only for few packages [1] to find possible issues before
the global switch.
I wrote a short documentation about it, check [2].
How to continue with the switch:
- Test the current status, find possible issues with the few modules
- Enable Jenkins for all YaST modules
- Finally remove the Travis support and disable the builds
Still missing parts:
- Pull requests are not built yet
- Support for coveralls (code coverage reporting) is missing
If you want to try Jenkins also for your packages just ping me, it's quite easy
to add more packages...
Ladislav
[1] yast2-devtools, yast2-nfs-client, yast2-registration, yast2-ruby-bindings,
yast2-storage-ng, yast2
[2] http://yastgithubio.readthedocs.org/en/latest/jenkins-integration/
--
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
