<freemangordon>
sicelo: while I agree to some extend, how useful would be to display a link that cannot be clicked?
<sicelo>
yes, i didn't finish writing another sentence to the effect that an unclickable link is somewhat confusing too. However, user intuition can help in that case, while it's totally absent when tag+text are gone
<freemangordon>
yeah, but specs say we shall remove it :(
<sicelo>
i have just read that link. if i understand it correctly, it's saying to strip the tag (not the text)
<sicelo>
"The tags specified above mark up the content in a way that allows them to be stripped out on some implementations without impacting the actual content. "
<sicelo>
what it's saying sounds exactly like in the example i gave above
<freemangordon>
ok, unless someone objects I will implement it as you say
<sicelo>
and yes, this means no parsing, unless i misunderstand. basically you find '<' ... skip everything until you reach '>'. done
<freemangordon>
no, I must parse
<freemangordon>
as I want to support <b> <i> etc
<freemangordon>
but not <a> and <img>
<sicelo>
ah, ok :-)
<freemangordon>
it is not a biggie
<freemangordon>
I am using GMarkupParser, which is said to be lightweight parser
<sicelo>
back to that sentence a bit: text is 'content', so the sentence indicates that content shall not be touched
<freemangordon>
ok
<freemangordon>
I will display links as blue underlined text
<freemangordon>
someday we may even want to support click on that as well
Pali has joined #maemo-leste
Twig has quit [Ping timeout: 256 seconds]
<Wizzup>
let's hope this doesn't introduce exploits throught notification :D
Pali has quit [Ping timeout: 256 seconds]
<freemangordon>
it shouldn't :)
<freemangordon>
hmm, it seems libnotify assumes that timeout 0 means persistent notification
<freemangordon>
but h-h looks for 'persistent' hint
<freemangordon>
I wonder what 'persistent' with non-zero timeout would be
uvos has joined #maemo-leste
<uvos>
"<freemangordon> I wonder what 'persistent' with non-zero timeout would be"
<uvos>
most notification servers have a global que
<uvos>
probubly this means to show the notification for timeout and then put it into the (usually hidden untill the user clicks) que
<uvos>
but ill test that theory on kde and lxqt in a sec
<freemangordon>
uvos: could be, but still, if this is persistent across reboots, I wonder how actions shall be implemented then
<freemangordon>
as those are dbus callbacks
<uvos>
none of the notifications are presistant across reboots
<uvos>
or restarts of the server
<freemangordon>
hmm
<uvos>
as far as i can tell
<freemangordon>
well, we support that :)
<uvos>
well as you note
<uvos>
it cant really work
<freemangordon>
i can, as soon as there are no actions involved
<uvos>
sure you can have grayed out notifications
<uvos>
or something
<freemangordon>
also, for example conversations or call-ui can listen to dbus and activate themselves
<uvos>
clearly a uninteneded hack
<freemangordon>
TBH I cannot find a single user in fremantle that sets "persistent" property
<freemangordon>
ok, so it seems we do not support persistence then (in terms of specs)
<Wizzup>
doesn't seem like a big deal atm?
<freemangordon>
sure no
<freemangordon>
I am just trying to figure out what we support and what not
<freemangordon>
to properly report to clients
<uvos>
probubly usefull for pressistance to exist
<uvos>
for instance for a mute button
<Wizzup>
I think for that we might want some notifications window or status applet
<Wizzup>
but it doesn't seem quite essential now in any case ;)
<uvos>
as a global que yeah eventually
<freemangordon>
yeah, some status bar applet
<uvos>
i dont see how my gf could survive if every notification has its own window :P
<freemangordon>
no, it is not like that
<freemangordon>
h-h supports threadung and category
<freemangordon>
so notifications gets grouped
<freemangordon>
don;t ask me how, but the code is tehre
<uvos>
the dekstop notification spec if seams to create a new window for every call
<freemangordon>
no
<uvos>
hmm it dosent work then
<freemangordon>
well, it depends on how you use that
<freemangordon>
you should set the hints correctly
<uvos>
what hints?
<uvos>
are thes mameo specific
* freemangordon
checks
<uvos>
the dekstop apps that do work with the if atm
<uvos>
spamm lots of windows
<uvos>
like if i download 10 podcasts via gpodder
<uvos>
ill get 10 windows with the compleate notification
<mighty17[m]>
it seems like its present, but the logs say `(phoc:18590): phoc-wlroots-CRITICAL **: 19:28:39.915: [render/gles2/renderer.c:445] Cannot read pixels: missing GL_EXT_read_format_bgra extension`
<freemangordon>
hmm, seems like a bug
<freemangordon>
which mesa is that?
<mighty17[m]>
from maemo-leste-upstream-forks
<freemangordon>
ok
* freemangordon
boots d4
<freemangordon>
mighty17[m]: hmm, this is DRM or WL or X11?
<freemangordon>
I guess X11
<freemangordon>
but you want DRM
<mighty17[m]>
WL
<mighty17[m]>
as in the error is from wl....
<freemangordon>
yes, but renderer is drm, afaik
<mighty17[m]>
right
<freemangordon>
sec (phone call)
<freemangordon>
hmm, is it?
<freemangordon>
DISPLAY=:0 does not look like DRM
<mighty17[m]>
thats just me doing it from ssh
<freemangordon>
still, you ask for x11 platform capabilities
<freemangordon>
not for GBM platform
<mighty17[m]>
hm? im a bit lost
<freemangordon>
there are 3 platforms that have different extensions: GBM (or drm), X11 and WL
<freemangordon>
which renderer does wlroots use?
<freemangordon>
DRM or X11?
<mighty17[m]>
wayland
<freemangordon>
no, there is no such renderer, unless I am missing something
<mighty17[m]>
I'll look into it later this week then
<uvos>
is it not a bit wierd that it makes sutch a difference in fullscreen animations, did you improve something besides using buffer age? @freemangordon
<uvos>
i would have expected that to not matter if the entire display is changed
<Wizzup>
well that depends on if it's also reloading the bg no?
<uvos>
the bg also moves
<uvos>
was it redrawing the window pixmaps too?
<uvos>
ie updateing the textures
<uvos>
btw maybe we could fix the tasknav animation in portrait
<uvos>
its a bit of a pet peeve of mine (i can also try some time)
dev has joined #maemo-leste
<freemangordon>
uvos: the big difference is that it does not re-upload the whole buffer every frame
<freemangordon>
that's what enunes' hack was doing
<freemangordon>
umm, what is wrong with tasknav animation?
<uvos>
freemangordon: in landscape it zooms out to the center of the display, in portrait it skews to one side, im pretty sure its just a missing coordinate swap
<freemangordon>
is that visible in the ^^^ video?
<uvos>
yeah
<uvos>
2:45
<uvos>
it looks like the center point of the animation dosent change for protrait
<uvos>
while the center of the display obv dose
<uvos>
just a minor visual glitch
<freemangordon>
hmm, I guess I can change transitions.ini to make that animation last few seconds
* freemangordon
boots PP
<uvos>
its visible on all devices btw
<uvos>
not pp specific
<freemangordon>
ok
<freemangordon>
tasknav is my pet for the last couple of years :)
<freemangordon>
so I will fix that when I find some spare time
<uvos>
then you probubly know where to look
<freemangordon>
shoudl be an easy fix
<freemangordon>
yeah
<freemangordon>
though I see nothing @ 2:45
<freemangordon>
oh, right
<freemangordon>
now I see
noidea_ has quit [Remote host closed the connection]
noidea_ has joined #maemo-leste
Twig has joined #maemo-leste
vagag has joined #maemo-leste
<sicelo>
lovely 'woosh' sounds. have we had them all along, or they're new to Leste?
<freemangordon>
sicelo: audio was not working :)
<freemangordon>
or, if you mean "do we have it in fremantle?", yes, we have them
Pali has joined #maemo-leste
parazyd has quit [Ping timeout: 252 seconds]
<sicelo>
i meant in Leste. i recall a day or two ago Wizzup said something about importing certain sounds. or those were ringtones only
parazyd has joined #maemo-leste
<Wizzup>
it wasn't added to any meta pkg yet
<uvos>
the woosh sounds have been there all alonge
<uvos>
thats maemo-input-sounds
<uvos>
thats worked for quite some time
<sicelo>
i guess it's because my d4 acts up so much, so i hardly use Leste
<uvos>
it also depends on your profile
<uvos>
you may have them disabled
<uvos>
the woosh is tied to the click, wich i find really annoying
<sicelo>
actually it isn't tied to the click (i've always had clicks disabled)
mardy has quit [Quit: WeeChat 2.8]
<uvos>
it is if you just swich profiles
<uvos>
(as opposed to creating a custom one)
<sicelo>
it's in "System Sounds". just rechecked with my Fremantle N900. unless something's changed in Leste
<uvos>
yes thats correct
<uvos>
but theres just 2 default profiles 1 has both enabeled 1 both disabled