Indefinido até agora….


MSN blocking googlepages.com links?
abril 1, 2008, 3:46 am
Filed under: Uncategorized

Today, I discovered something in MSN:

Try to send this message to someone:

http://www.googlepages.com

or

http://anything.else.doesnt.work.too.googlepages.com and check the result.

Yes, the connection is automatically closed in the chat :)

Check the kopete screenshot:

Msn hates googlepages.com

I know that MSN blocks some keywords, but googlepages links?  April Fools’ maybe?



KDE 4.0 lançado!
janeiro 11, 2008, 8:54 pm
Filed under: Uncategorized



Life.rotate(180)
dezembro 15, 2007, 12:40 am
Filed under: Uncategorized

Yes, that’s it!



How to make a bug report
dezembro 3, 2007, 7:44 pm
Filed under: Uncategorized

xxx to kde-multimedia show details Dec 2 (1 day ago)
subject    juk
Reply

Helo is poland “”openbsd 4.2″” is problem “””juk”””

kbuildsycoca running…
# juk: WARNING: Unable to play

help ?



Changing buffers in Vim like in emacs
outubro 25, 2007, 7:02 pm
Filed under: Uncategorized

If you want to mimic emacs’ keyboard shortcuts to change buffers, put these lines in your .vimrc

map <C-x><Right> :bnext!<CR>
map <C-x><Left> :bprevious!<CR>

and you can use Ctrl+x Left/Right arrows to change buffers.



I Love Video4Linux!
outubro 19, 2007, 2:21 pm
Filed under: Uncategorized

Fact, Video4Linux is crap not so good:

  1. It doesn’t have an userspace API like libasound, and forces everyone to rewrite everything;
  2. The API is not stable;
  3. The drivers don’t implement color conversion in kernel, so you have to do that too;
  4. V4L2 is almost 10 years old (it was created to fix some shortcomings of V4L1 and to support a wider range of devices), but a lot of drivers still use V4L1 (that is already obsolete),  then you have to implement support for both of them in your application.
  5. There isn’t a way to enumerate the supported resolutions in a video device, so you have to check that “brute forcing” the device!!

(code from Qtopia’s Camera App):

v4l2videocapturedevice.cpp
void V4L2VideoCaptureDevice::calcPhotoSizes()
{
QList<QSize> resolutions;

// standard resolutions – XGA, SVGA, VGA, CGA (roughly) and postage stamp
resolutions << QSize(1024, 768) << QSize(800, 600) << QSize(640, 480) << QSize(320, 200) << QSize(120, 120);

// test if the resolutions are supported (write back modifications)
QMutableListIterator<QSize> sizeIt(resolutions);

while (sizeIt.hasNext())
{
v4l2_format format;
QSize& currentSize = sizeIt.next();

memset(&format, 0, sizeof(format));

format.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
format.fmt.pix.width = currentSize.width();
format.fmt.pix.height = currentSize.height();
format.fmt.pix.pixelformat = V4L2_PIX_FMT_RGB32;
format.fmt.pix.field = V4L2_FIELD_NONE;

if (ioctl(m_fd, VIDIOC_TRY_FMT, &format) == 0)
{
qWarning(“V4L2: Tried resolution & format (%d, %d, RGB4) – device wants (%d, %d, %4s)”,
currentSize.width(),
currentSize.height(),
format.fmt.pix.width,
format.fmt.pix.height,
(char const*)&format.fmt.pix.pixelformat);

unsigned int& imageType = m_imageTypes[QSize(format.fmt.pix.width, format.fmt.pix.height)];

if (imageType != V4L2_PIX_FMT_RGB32) // have been here? keep RGB32 if we can
{
imageType = format.fmt.pix.pixelformat;
}
}
}
}

(In fact there’s a experimental ioctl() that enumerates the supported resolutions, but that it’s not garanteed that it’s implemented in a driver, and it’s, well, experimental).

So, why there aren’t some kind of guidelines that “force” the drivers that are part of the official kernel tree to implement the necessary functions to, at least, make it easier to application developers?

P.S.: I know that there’s an effort to implement a userspace API, but it’s just in the beginning yet.



Nokia 6070 support in Gammu
outubro 1, 2007, 6:14 pm
Filed under: Uncategorized

Today, my patch to add support for nokia 6070 in Gammu was merged in svn.

Thank you, guys!




Seguir

Obtenha todo post novo entregue na sua caixa de entrada.