Skip to main content
  1. Planet
  2. Global
  3. Page 871

the avatar of Frédéric Crozat

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

Recortando imagens com o Apache OpenOffice

Quem já precisou recortar uma imagem no OpenOffice sabe que não é tão simples como no micro$oft office. Por exemplo, se você está usando o Impress (editor de apresentação), é necessário clicar no Menu >> Formato >> recortar imagem e, então, na janela que abrirá, você deve ir clicando ou digitando os valores para que o corte da imagem possa ir sendo feito. Não é coisa de outro mundo, mas para um iniciante no OpenOffice isso pode ser uma dor de cabeça, já que no concorrente é muito simples (não preciso descrever aqui ….)..rs

Para facilitar esta tarefa, existe uma extensão para o OpenOffice que é a CropOOo, que nos permite trabalhar como no concorrente… ela instala uma barra de ferramentas que te permite clicar na imagem e ir selecionando com o mouse a área a ser cortada. Uma vez que selecionou a área basta apertar a tecla ENTER que a imagem é cortada.

Abaixo uma imagem da ferramenta na minha barra de tarefas. Espero ter ajudado. um abraço!

recorte de imagens

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

Instalando o OpenOffice 3.4.1 no Linux Mint 13 Maya (Ubuntu/Kubuntu)

Oi pessoALL! tudo bem? estou “meio sumido” devido estar trabalhando em muito projetos e, por isso, acabei tendo pouco tempo para escrever no blog.

Devido alguns problemas de compatibilidade com a suíte de escritório LibreOffice om alguns documento do Micro$oft Office, resolvi experimentar o OpenOffice. Pesquisei um pouco sobre comentários de outras pessoas e resolvi tirar o LibreOffice que é padrão no Linux Mint 13 e instalei o OpenOffice na versão 3.4.1.

A suíte de escritório Apache Openoffice é uma boa opção para uso no lugar da suite office da Microsoft. ela conta com muitos recursos para texto, planilhas, apresentações, desenhos e apossui até um editor de fórmulas matemáticas.

Através do Synaptic (gerenciador de pacotes) a versão disponível é a 3.3.0, mas, como eu gosto muito de ter as versòes mais atuais, eu resolvi baixar direto da página do desenvolvedor: http://www.openoffice.org/download/

Neste link você baixa a versão em português-brasil e abaixo descrevo como proceder para instalar esta versão que é muito simples.

Antes de tudo recomendo que remova o LibreOffice, pois quando tentei instalar o Open junto com o Libre tive alguns problemas e somente o Libre abria. Então com o libre removido….

  1. Reveja os Requisitos de Sistema
  2. Baixe a sua versão favorita de Linux Apache OpenOffice
  3. Comente informações úteis e opções de instalação no Guia de instalação. (este não é um passo obrigatório, pode pular e fazer depois..)
  4. Descompacte a imagem baixada para preparar a instalação.
    O seguinte comando deve funcionar: tar -xvzf "linux package name".tar.gz
    onde “linux nome do pacote” é a parte inicial do arquivo que você acabou de baixar.Isso irá criar um diretório de instalação (pt-BR).
    O nome do diretório de instalação será provavelmente a abreviação do idioma para o conjunto de instalação, por exemplo, en-US.
  5. su para root, se necessário, e navegar para Apache diretório de instalação do OpenOffice (o arquivo descompactado).
    Você provavelmente vai precisar ser root para executar o comando rpm para instalar o software.
  6. cd para os RPMS subdiretório do diretório de instalação.
    Você deverá ver um monte de rpms aqui e um sub-diretório chamado “desktop-integração”.
  7. Instalar esta nova versão, digitando rpm -Uvih *rpm .
    Por padrão, isso irá instalar / atualizar Apache OpenOffice em sua /opt diretório.Alternativamente, você pode usar um pacote de instalação GUI, referência ao diretório de instalação e instalar todos os rpms no nível superior. Isso também pode ajudá-lo na determinação quaisquer problemas de dependência, se existirem.
  8. Instale os recursos de integração de desktop para sua configuração.
    cd para desktop-integration no diretório de instalação,
    e, dependendo do seu gerenciador de pacotes / sistema, instale a interface do desktop apropriado usando RPM.
  9. Finalmente, inicie o Apache OpenOffice 3.4.x para garantir que ele está funcionando.

Com poucos minutos de uso, percebi que o OpenOffice tem um desempenho melhor e abriu as planilhas melo do que o LibreOffice, pelo menos em meu notebook.

OpenOffice 3.4.1

Fica a dica… teste e use por sua conta e faça seu comentário.

Uma abraço!!

the avatar of Medwinz's Notes
the avatar of Medwinz's Notes

Mengenang Bapak

Mohammad Ali Zakaria, bapak saya, guru dan sahabat. Seorang yang sangat sederhana, perhatian dengan keluarga, dan selalu mengajarkan kepada kami anak-anaknya untuk belajar dan menuntut ilmu. Bapak lahir di Makale, Tana Toraja, sebuah kota kecil 310 km dari Makassar ibu kota propinsi Sulawesi Selatan, pada 14 September 1937. Beliau lulus SD dan SMP di Makale dan menamatkan SMA nya di Makassar. Bapak menyelesaikan kuliahnya di UI Jakarta. Beliau kemudian bekerja sebagai pegawai negeri di Departemen Kesehatan. Bagi saya bapak adalah seorang pegawai negeri yang pejuang.

Ketika kecil kami beternak ayam petelur, sedikit demi sedikit sampai jumlahnya sekitar 500 ekor. Setiap pagi sebelum ia berangkat kerja dan kami belum berangkat sekolah ia mengajari kami memberi makan ayam-ayam itu. Dan siangnya sepulang kerja ia mengajari kami mengambil telurnya. Di awal-awal kami mengantarkan telur-telur ayam itu ke warung-warung dekat rumah setiap pulang sekolah, belakangan orang-orang dari warung itu yg mengambilnya. Uang hasil penjualan telur ini untuk biaya kami sekolah dan membeli buku selama kami SD.

Ketika saya kelas 6 SD, bapak menghentikan kegiatan ini karena saya asthma dan gak sembuh-sembuh. Kata dokter, debu dari merang alas lantai kandang ayam itu yang memicu asthma saya tidak sembuh. Saya tanya bapak kalau bapak menghentikan beternak ayam petelur ini nanti bagaimana kami anak-anaknya bisa beli buku. Dia bilang ibu masih menjahit dan bapak sudah mulai ada uang lebih yg penting saya sehat. Sejak itu asthma saya sembuh.

Bapak mengajarkan saya bermain catur ketika ada pertandingan catur dunia Karpov vs Korchnoi, dia bilang dengan bermain catur kita dilatih untuk berpikir 5-10 langkah ke depan, itu akan berguna untuk saya nanti. Dia juga mengajarkan kami berkebun menanam pisang, kelapa, cabai, dan memelihara anggrek di pekarangan rumah kami. Dia bilang semasa kecilnya berkebun dan bertani adalah pekerjaan anak laki-laki di Toraja ditambah membawa kerbau mandi di sungai Sa'dang dan menunggang kuda.

Bapak seorang altruistik, ia sangat memperhatikan saudara-saudaranya, keponakan-keponakannya, teman-temannya di kantor, bahkan kadang saya bingung karena, ketika kecil kami bukan orang berada walaupun tidak miskin, dia selalu membantu orang yang kesusahan. Tidak terhitung jumlahnya baik saudara atau bukan yang tinggal di rumah kami yang kamarnya hanya 3. Dia bahkan pelan-pelan menambah kamar di rumah kami bukan hanya untuk kami tapi untuk siapa saja yang datang dan tinggal di rumah kami.

Bapak orang yang sangat sederhana, pakaiannya berumur tahunan dan kalau sobek dia meminta ibu saya untuk memperbaikinya. Mobil kantornya Land Rover th 69 yang dia pakai 25 tahun tidak mau diganti. Bapak orang yang sangat tidak perduli dengan hal-hal yang material, dia tidak punya buku tabungan sampai dia pensiun, itupun karena uang pensiun harus ditransfer ke rekening bank. Jangan tanya kartu kredit atau deposito karena dia tidak mengerti. Dia bingung kalau orang bicara ekonomi, dia bilang semuanya akan lebih baik kalau orang hanya belanja sesuai dengan apa yang ada di kantongnya.

Bapak seorang yang sangat percaya kekuasaan Allah dan taat walaupun dia bukan tipe orang yang pintar memberi nasehat agama. Jika tidak sakit bapak selalu berusaha shalat berjamaah ke Masjid terutama shubuh, maghrib dan isya. Bapak seorang yang hangat, orang akan merasa kehilangan jika ia tidak datang ke masjid, ke warung korannya Mughni di dekat rumah atau jalan pagi di sekitar taman komplek.















Di akhir-akhir hidupnya dari 5 bersaudara sayalah anaknya yang paling dekat. Pekerjaan kakak saya mengharuskan dia keliling dunia dan Indonesia. Adik saya sejak 2001 bekerja untuk Airbus di Augsburg Jerman. Adik saya yang lain seorang dokter yang sedang pendidikan spesialis di RSCM dan kerjanya menuntut dia untuk selalu di RS. Adik saya yang paling kecil seorang dokter juga dan bertugas di Makassar.

Saya adalah teman ngobrol bapak, dia selalu menceritakan apa yang ada dalam pikirannya ke saya setiap pagi dan malam. Dia sangat terbuka kepada saya dan saya tahu dia bahagia dengan kondisi itu. Dia bangga dengan kakak saya seorang insinyur elektro yang kerjanya keliling dunia dan Indonesia. Dia sangat bangga dengan adik saya seorang engineer desainer pesawat di Airbus, dia juga sangat bangga dengan adik saya yang akan jadi dokter spesialis anak dan dokter spesialis penyakit dalam. Tapi walaupun dia tidak pernah bilang bahwa dia bangga dengan saya, saya tahu dia menganggap saya adalah anak yang paling bisa diandalkan. Perasaan yang tidak bisa diungkapkan dengan kata-kata. 

Bapak mengajarkan saya untuk menjadi orang yang siap membantu siapa saja tanpa pamrih, mengajarkan saya menjadi orang yang sederhana dan menyayangi keluarga.

Bapak pernah bilang, kalau dia bisa meminta cara untuk mati, maka dia ingin dipanggil oleh Allah dengan cara yang mulia dan tidak merepotkan orang lain. Allah mengabulkan doanya. Jum'at 16 November 2012 / 2 Muharram 1434H di Jakarta Allah memanggilnya dan dengan wajah tersenyum Bapak menyambutnya. Bahkan pohon-pohon dan tanaman kesayangannya di samping rumah malam ini rebah untuk menghormatinya. Selamat jalan pak, saya tahu Bapak bahagia di tempat yang terbaik. Innalillaahii wa inna ilaihi rojiun.

the avatar of Raymond Wooninck
the avatar of Raymond Wooninck

Running for the openSUSE Board

Maybe some people already expected this to happen, but for me it is still a surprise that I actually did it. I put myself up as a candidate for the openSUSE Board. 

I started working with Linux since the early days (Kernel v0.12) and have been using openSUSE since 2003.  I joined the openSUSE project about 4 years ago when I submitted my first KDE package. From that moment things went very fast and I am currently the main maintainer for the KDE repositories and maintaining Chromium and the Plymouth bootsplash. One of the next things I want to tackle (package wise) is Dracut 
as an alternative initrd builder. 
My current “day job” is Application Portfolio Manager for a well-known bottling company that focus on the Central and Eastern Europe market. If you look closely at my IRC nick, then you could guess which company it is  In this job I am responsible for setting out the strategy of all Applications used within the company. This ranges from our main Enterprise System (SAP) to desktop tools like collaboration, email, etc. The strategy should e.g. enable Business opportunities to exploit the main Enterprise system further.
If I am elected to the board, then my day job and past IT experience would be a good use. I would like to see the board to set out a new strategy for the openSUSE distribution which makes it possible to enhance our strengths and values. In the past SuSE has established a name for itself and it created some 
great tools, which even now are unmatched. 
Nowadays everything is about Usability and Accessibility. How usable is the software, how accessible is the information, how can I use this program, etc. I would like to extend this principles to the openSUSE project,  
On one hand we need to strengthen the relationship and the communication between the openSUSE community, including people working for SUSE. Only together we can accomplish great things. 
On the other hand we should value our end-users. These users are giving valuable feedback about how they see openSUSE with regards to Usability and Accessibility and their feedback should be incorporate into the final product. This drives the success of a distribution. Too many things out there are already being decided by a handful of people without listening to others. 
It is my opinion that the board should play a big role in both areas and to enable openSUSE to grow. 
My promise to you is that I will do my best to establish the above, If I would be elected. 

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

XWT

I started the XWT project almost one year ago and athough I talked about it at FOSDEM, I never found the time to formally present it. Those are busy days at Xamarin! Anyway, let’s go ahead.

XWT is an open-source cross-platform UI toolkit for Mono and .NET. What’s special about XWT is that it is built on top of the native widget toolkit of each supported platform. So rather than a new widget toolkit implemented from scratch it is an abstraction that wraps the native toolkits using a common API. The end goal of XWT is to allow building applications which look and feel native in each platform. Here are some screenshots of a sample application running with the GTK and Cocoa backends:

GTK backend
Cocoa backend


I initially created XWT with the idea of building MonoDevelop on top of it. Around this time last year we had a discussion about how we could improve the look & feel of MonoDevelop in Mac and Windows. MonoDevelop is built with GTK# 2, which worked very well on Linux, but which had (and still has) some issues on other platforms. Although GTK is a cross platform toolkit, not all backends have the same quality, and not all features are completely implemented. So XWT would allow us to have a native look and still reuse most of the code. However, rebuilding MonoDevelop with XWT is a lot of work and we needed to fix the Mac and Windows issues as soon as possible, so we decided to invest our efforts in fixing the most annoying GTK bugs instead of going the XWT route.

Even though we are not going to immediately migrate all of MonoDevelop to XWT, at Xamarin we have started using it for some UI code that needs run in MonoDevelop and Visual Studio. An example of this is the Android designer. The designer is implemented in XWT, and we use the GTK backend when running MonoDevelop and a WPF backend when running on Visual Studio:
The designer running on GTK in MonoDevelop

The designer running on WPF in Visual Studio

XWT vs Native Toolkits

At Xamarin we have always advocated for using the native toolkit of each platform in order to take advantage of all features offered by the platform and be able to build the most visually rich and performant applications. How does XWT fit on this idea?

XWT has three important design features:
  • User interfaces implemented using XWT can be embedded inside a native UI. It means you can build your application using the native toolkit when you need advanced platform features, and you can use XWT for more simple UI that can be shared.
  • XWT backends are built on top of native toolkits, so XWT widgets really look and behave like native widgets.
  • XWT is a UI toolkit abstraction, so it’s about abstracting common UI idioms as widgets. XWT will have support for the most common widgets such as entries or buttons, but it will also provide higher level widgets which are more “semantic”. It means that XWT applications will be constrained to use those higher level UI idioms, but each of those idioms can have a platform-specific implementation which takes full advantage of the native toolkit features, and which can abide for the platform UI guidelines. 
There is a tradeoff between portability and functionality. XWT is not for everybody. It wont have the richness and the low level features of a native toolkit, so it will not be suitable for applications which require advanced UI features.

Design Principles

XWT looks like GTK#. It uses a similar layout model and class names. That’s basically to make it easier to migrate GTK# code to XWT, not because GTK# is superior to everything else (although maybe it is). However, there are notable differences. The API design has an important focus on simplicity and usability. Here are some important differences with respect to GTK:
  • The widget hierarchy is mostly flat. There is a Widget class and most of other classes directly subclass it. There are no unnecessary infrastructure classes. For example, there is no Container class, any widget can have children if they need to.
  • Widgets are visible by default (I still haven’t figured out the reason why they are hidden by default in GTK).
  • No concept of GdkWindow. You have a widget, that’s all.
I’m a firm believer of usability-oriented API design. Many libraries are designed using complex class hierarchies and abstractions whose purpose is to make the library code easier to reuse and maintain. That is, the code is designed to facilitate the work of the library developer, not the work of the library consumer. That’s a bad approach since the library will be implemented by only few developers, but potentially consumed by thousands of developers.

Features

Here are some details about what’s currently supported by XWT:
  • XWT currently supports 3 backends with different level of development: GTK, Cocoa (Mac) and WPF (Windows).
  • XWT can instantiate more than one backend at a time, and run those side by side (with some limitations). For example, you can have XWT use Gtk and Cocoa in the same application, depending on what is hosting your code.
  • The basic widget library is mostly complete.
  • It has a drawing API, very similar to Cairo.
  • There is no visual designer yet, nor any markup language for representing windows. My plan is to use XAML or a simplified version of it.
  • XWT can be extended in different ways.
  • Applications can create subclasses of XWT widgets, or create new widgets.
  • New backends can be plugged into XWT
  • Existing backends can be extended
  • The API is not yet stable and can change at any time.

Future

The work on XWT will continue, there is still a lot to do. XWT is already already included in the MonoDevelop core. Although we don’t plan to do a big migration effort, we plan to gradually use XWT in the implementation of new features.

If you are interested in XWT, you can get the source code from here:
https://github.com/mono/xwt

There is also a mailing list:
http://groups.google.com/group/xwt-list

And an IRC channel:
irc://irc.gimp.org/xwt

Contributions are welcome!

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

openSUSE KDE Bug Squashing Days

Like everything, openSUSE is not perfect. Bugs crop here and there, or there is missing / quirky functionality that users may run into. Being a distribution of heterogeneous software, this means that bugs fall into these categories:

  • Upstream bugs in the software shipped by openSUSE

  • Bugs in the packaging

  • Bugs in distribution-specific setups or that derive from interactions with these setups (e.g. kernel, low level software stack, etc.)

To improve the distribution and to act like good FOSS citizens, distribution bugs need to be divided from upstream bugs: the former need to be properly fixed by openSUSE, the latter need to be communicated upstream so that everyone would benefit when they are fixed, including our favorite green distro.

Also, when dealing with bugs, one also runs into bugs that are invalid (local errors, for example), duplicated reports, or already fixed in newer versions.

So, how do we start improving openSUSE, and in particular the KDE part of openSUSE (since that’s what we’re talking about), from the current situation? An effective method is to triage open bug reports, verifying if they can be reproduced, reporting upstream bugs in the appropriate place, and closing off duplicate reports.

And to this aim, we will have a bug squashing session on 15th and 16th November, where you can help with reducing the number of KDE bugreports reported for openSUSE (and we for sure have more than enough of those). If you would like to help KDE in openSUSE, feel free to join.

There are no special technical knowledge requirements except for basics like being able to use the Bugzilla interface at http://bugzilla.novell.com. Having a recent KDE version installed is recommended (use either KDE:Release:49, KDE:Distro:Factory or KDE:Unstable:SC).

On the wiki page at http://en.opensuse.org/openSUSE:Bug_Squashing_KDE we tried to sum up everything relevant (comment and corrections welcome). Please make sure you read the bug screening guidelines at http://en.opensuse.org/openSUSE:Bug_Screening_KDE too.

If you want to help, hop during those days on the #opensuse-kde IRC channel on the Freenode network.

Happy bug hunting!

a silhouette of a person's head and shoulders, used as a default avatar
a silhouette of a person's head and shoulders, used as a default avatar

Are we few and small?

The truth is that this blog is a bit left alone, the main reasons are that there is no time but most of all I am not feeling in writing. I wrote so many things the last few months that I ended up actually hate writing... And here I am chattering...



A few nights before I was with a friend of mine that I hadn't seen for quite some time. While catching up the past year and so of news and going around to bars we had some quite interesting talks. The one that stuck in my head started as a conversation about the quality of the source of information and how that affects the quality of the Greek internet. My friend at a certain point ended up saying that although Greek internet is mostly full of crap there are actually people that seek quallity in their sources before they write something, also people who care on make things different by writting truths exist. Now here come the really interesting part of all this. She said that those people feel to be a minority and feel 'small' but the reality is that those people are actualy neither few nor small. The base for that conclution was that in Greek reallity most of the people who have access on the internet, and we were not talking about having a Facebook acount but actually read blogs, read news etc. and writting about all that are usually better educated and seek more stuff than 2 M friends on some social network. That stands on it's own under my opinion but it is my opinion (and my friends) and pay attention to the word usually.

Now thinking about all that got me in the loop of remembering conversations I had from time to time with people around the openSUSE community and generally FOSS people and the frustration I got from those people because they thought the same thing. We are few and small many of those people said to me when there was an idea of organizing something or make something relevant. When I first started mixing with the community and I was inexperienced I must admit that my original thought was that all those were excuses people were saying to me in order to avoid working. After a while I felt the same thing and I understood that those were not excuses but a reality all of those people were living and me because of my excitement was refusing to see. Thank to people that were more experienced than and because those people had the patience to mentor me even when I though I knew everything, I realized that this was a reality. If I ever critisiced you like that I now deeply apologise about this. I know that all of the above still don't make much of a sense and some of you might still wondering what I am trying to say through all that. A fact that goes me to the resume of that conversation I had with my friend.

The resume of that conversation was that people who have a purpose that is not something mainstream usually feel that they are few and small but if you search thoroughly into the internet you will find out that they are more than you think so. All people have to do is search for other people that have common routes or have routes that intersect and move from few to many and from small to big. Widening the way we look ourselves and thinking more out of the box can make the change, you see if you want to change something in the world and make it better requires to often look inside ourselves and changing things to us. 

a silhouette of a person's head and shoulders, used as a default avatar

the avatar of KDE at openSUSE
the avatar of KDE at openSUSE

KDE SC 4.9.3 packages for openSUSE

As announced on the opensuse-kde mailinglist, KDE SC 4.9.3 packages are available from the KR49 repo.

With those packages comes akonadi 1.8.1 which includes a lot of fixes from the recent KDEPIM coding sprint. It should improve performance and more importantly, KDE SC 4.9.3 and akonadi 1.8.1 should solve all known data loss bugs. A special thanks to all the PIM developers putting a lot of effort into improving KDE’s PIM stack!

You can find instructions on how to update on the openSUSE wiki.