Se siete dei fan di KDevelop, allora dovete sapere che i sorgenti non sono più in trunk/KDE, ma in trunk/extragear/sdk: stessa cosa vale per KDevPlatform e Quanta. Con questa mossa, gli sviluppatori non avranno più l’acqua alla gola riguardo scadenze ufficiali e quant’altro.

Questi annunciano inoltre che, il possibile rilascio di KDevelop 4.0, avverrà probabilmente verso la fine di marzo 2010.

Un altro spostamento di minore importanza riguarda il mitico plugin katepart denominato autobrace, che è stato incluso addirittura in kdelibs

Ammetto che questo post interesserà al massimo a 5-6 persone su 6G totali… :D

I have used C++ for about 5 years now, and it is really a very powerful programming language. But I found one big disadvantage; it is too hard to make a C++ GUI. I used to do that by Windows API, but it is difficult to learn and I can’t learn my students all Windows API concepts for just making some forms and buttons!

Recently I heard about Qt and decided to learn it. As usual I stuck at the beginning; how could I build a Qt Application? and as usual too I do it my way

Building Qt Applications using Notepad

If your favorite text editor is still Notepad!, you must build your Qt Applications using command line.

To let it easy to you, I made a batch file depends on what compiler you want to use to build Qt Applications.

Building Qt Opensource Version using MingW

If you are using Qt Opensource Version you can use this batch file to build and run Qt Applications:

::::::::::::::::::::::: This is Qt building batch by Madhat Alsoos :::::::::::::::::::::::
:: First argument is the directory of the project
:: Second argument is the name of the cpp file without .cpp

@echo off
cd %1
set QTDIR=%1
set PATH=C:\Qt\2009.04\qt\bin;C:\Qt\2009.04\bin;C:\Qt\2009.04\mingw\bin;C:\WINDOWS\System32;%PATH%
set QMAKESPEC=win32-g++
qmake -project
qmake
mingw32-make.exe
IF not ERRORLEVEL 1 start debug\%2.exe

You can use this batch by passing the directory of the .cpp file and its name like this:

build.bat c:\qt\test\helloworld helloworld

It is so easy! First set Qt base directory to directory of file which we want to build (which will be passed as an argument to this batch file), then add Qt installation directory to the PATH system variable (just in case) and set QMAKESPEC to win32-g++ which tells Qt that it should make the project for g++ compiler. After that we make the .pro file (Qt project file) and compile it using mingw32 (which came by default with your Qt open source verison).

Note that you must change Qt path in this batch to where you installed Qt, or simply add your Qt bin folders to PATH system variable.

Building Qt Commercial Version using Visual Studio

If you are using Qt Commercial Version you can use this batch file to build and run Qt Applications:

::::::::::::::::::::::: This is Qt building batch by Madhat Alsoos :::::::::::::::::::::::
:: First argument is the directory of the project
:: Second argument is the name of the cpp file without .cpp

@echo off
cd %1
set QTDIR=%1
set PATH=C:\Qt\4.4.3\bin;C:\Program Files\Microsoft Visual Studio 9.0\VC\bin;%PATH%
set QMAKESPEC=win32-msvc2008
call "C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat"
qmake -project
qmake
nmake
IF not ERRORLEVEL 1 start debug\%2.exe

You can use this batch by passing the directory of the .cpp file and its name like this:

build.bat c:\qt\test\helloworld helloworld

As you see, I used nmake to build and link the Qt Application which means that you must have Visual Studio installed on your computer to use this batch file. If your using Commercial Version and you don’t have Visual Studio on your computer you can install MingW and use the first batch file which should work in this case too.

Note that you must change Qt path and Visual Studio path in this batch to where you installed them, or simply add you Qt bin folder and Visual Studio bin folder to PATH system variable.

Building Qt Applications using EmEditor

If your favorite text editor is EmEditor, you can make a small button at EmEditor Tools Toolbar and call any of the above batches in it.

Just open EmEditor and go to Tools > External Tools > Customize Tools and click New button, and fill in fields like this:

Then you will find a small button in EmEditor Tools Toolbar which will do all things for you:

Building Qt Applications using Notepad++

If your favorite text editor is Notepad++ then you are my man, so I made a Notepad++ plugin named QtNpp just for you

You can download it (and even change the way it build your Qt Applications) from my post “QtNpp: Notepad++ Plugin to build Qt Applications”.

I really love Qt and began to learn it recently, but I didn’t find a way to build Qt files from inside Notepad++ so as usual I made mine

QtNpp is my Notepad++ plugin to build and run Qt applications.

The idea

The idea of QtNpp is simple; just build the file by using these lines:

@echo off
set QTDIR=%1
set PATH=C:\Qt\2009.04\qt\bin;C:\Qt\2009.04\bin;C:\Qt\2009.04\mingw\bin;C:\WINDOWS\System32;%PATH%
set QMAKESPEC=win32-g++
qmake -project
qmake
mingw32-make.exe

but the implementation of QtNpp is not that simple!

By default QtNpp try to build Qt files by using the above script which works in one of these cases:

1. You have Qt opensource edition installed at the default path: C:\Qt\2009.04
2. You have Qt opensource edition installed at another path and this installation path was added to PATH system variables.
3. You have Qt Commercial edition and you manually installed MingW and both installation paths was added to PATH system variables.

What if that is not the case? If my QtNpp doesn’t work by default, don’t worry you can change the building script yourself!

Just create QtNpp.ini in <Notepad++ installation folder>/plugins/Config and QtNpp will execute QtNpp.ini file as a batch and passing the folder of Qt file and the filename to it.

Yes, that is you can put the above script in QtNpp.ini and change whatever you want to change in it, and QtNpp will execute your new script instead of its one!

Looking inside

I used this template as a start of my QtNpp, also I read the source of some free Notepad++ plugins to learn from.

The build and run function of QtNpp is:

void buildAndRun()
{
	//Save current opened file first
	::SendMessage(nppData._nppHandle, NPPM_SAVECURRENTFILE, NULL,NULL);
	//Get directory and filename of the opened file
	String directory = getCurrentFilePath();
	String filename = getCurrentFileName();
	String command = getBuildCommand(filename,directory,true);
	//Build and run opened file
	RunCommand(filename,directory,command);
}

Here I get the build commands by getBuildCommand and then run these commands with RunCommand function, which replace %1 with directory path and %2 with filename and save them in bat file and execute it by calling ExecuteBatch function:

String ExecuteBatch (String filename,String directory,const char* path)
{
	CreateRedirectedProcess((LPTSTR)TEXT(path),(LPTSTR)TEXT(directory.c_str()));
	String s=ReadFromPipe(showText);
	return s;
}

You can see that I run the batch file in a new process and then read its output from the redirected pipe and send it to NppExec console to print it (which is a Notepad++ plugin comes by default with Notepad++).

int CreateRedirectedProcess(LPTSTR szCmdline,LPTSTR directory)
{
   SECURITY_ATTRIBUTES saAttr; 

   saAttr.nLength = sizeof(SECURITY_ATTRIBUTES);
   saAttr.bInheritHandle = TRUE;
   saAttr.lpSecurityDescriptor = NULL; 

   if ( ! CreatePipe(&g_hChildStd_OUT_Rd, &g_hChildStd_OUT_Wr, &saAttr, 0) )
      ErrorExit(TEXT("StdoutRd CreatePipe")); 

   if ( ! SetHandleInformation(g_hChildStd_OUT_Rd, HANDLE_FLAG_INHERIT, 0) )
      ErrorExit(TEXT("Stdout SetHandleInformation")); 

   if (! CreatePipe(&g_hChildStd_IN_Rd, &g_hChildStd_IN_Wr, &saAttr, 0))
      ErrorExit(TEXT("Stdin CreatePipe")); 

   if ( ! SetHandleInformation(g_hChildStd_IN_Wr, HANDLE_FLAG_INHERIT, 0) )
      ErrorExit(TEXT("Stdin SetHandleInformation")); 

   CreateChildProcess(szCmdline,directory);

   return 0;
} 

void CreateChildProcess(LPTSTR szCmdline,LPTSTR directory)
{ 

   STARTUPINFO siStartInfo;
   BOOL bSuccess = FALSE;
   ZeroMemory( &piProcInfo, sizeof(PROCESS_INFORMATION) );
   ZeroMemory( &siStartInfo, sizeof(STARTUPINFO) );
   siStartInfo.cb = sizeof(STARTUPINFO);
   siStartInfo.hStdError = g_hChildStd_OUT_Wr;
   siStartInfo.hStdOutput = g_hChildStd_OUT_Wr;
   siStartInfo.hStdInput = g_hChildStd_IN_Rd;
   siStartInfo.dwFlags |= STARTF_USESTDHANDLES;
   siStartInfo.wShowWindow=SW_HIDE;

   // Create the child process.
   bSuccess = CreateProcess(NULL,
      szCmdline,     // command line
      NULL,          // process security attributes
      NULL,          // primary thread security attributes
      TRUE,          // handles are inherited
      CREATE_NO_WINDOW,             // creation flags
      NULL,          // use parent's environment
      directory,          // use parent's current directory
      &siStartInfo,  // STARTUPINFO pointer
      &piProcInfo);  // receives PROCESS_INFORMATION 

   if ( ! bSuccess )
      ErrorExit(TEXT("CreateProcess"));
   else
   {
      CloseHandle(piProcInfo.hProcess);
      CloseHandle(piProcInfo.hThread);
   }
}

Here I redirect the output by creating a pipe and pass it to process using siStartInfo.hStdOutput. Also I hide the console window by using CREATE_NO_WINDOW flag in CreateProcess.

Configure QtNpp

As I said above if QtNpp doesn’t work by default with you, just create QtNpp.ini and put all commands you need to build Qt on your PC in it.

I suggest to take these QtNpp.ini as a start:

QtNpp.ini for MingW

@echo off
set QTDIR=%1
set PATH=C:\Qt\2009.04\qt\bin;C:\Qt\2009.04\bin;C:\Qt\2009.04\mingw\bin;C:\WINDOWS\System32;%PATH%
set QMAKESPEC=win32-g++
qmake -project
qmake
mingw32-make.exe

QtNpp.ini for Visual Studio

@echo off
set QTDIR=%1
set PATH=C:\Qt\4.4.3\bin;C:\Program Files\Microsoft Visual Studio 9.0\VC\bin;%PATH%
set QMAKESPEC=win32-msvc2008
call "C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat"
qmake -project
qmake
nmake

Just replace fixed paths in QtNpp.ini with paths on your computer or add them to PATH system variable.

You may notice that you can build any kind of files with this plugin (not only Qt) because when you make QtNpp.ini, my plugin turns into executer for it only!

Download

You can download QtNpp dll and sourcecode under GNU License:

QtNpp dll	QtNppPlugin.zip
QtNpp source	QtNpp.zip
QtNpp.ini for MingW	QtNpp_MingW.zip
QtNpp.ini for VS	QtNpp_VS.zip
License	GNU General Public License

Buy Cheap Pink Stanley Thermos, 1/2 Qt

Buy Low Price From Here Now
Thermos is 100% stainless steel construction. Durable rust proof finish. Exclusive Char-Vac technology for superior insulation and durability. Features and easy pour stopper and wide mouth opening that is big enough for ice cubes. Easy to clean……..
Readmore

Technical Details

See more technical details

Images Product

Buy Pink Stanley Thermos, 1/2 Qt Now

Hello people, long time no blog.

I have a lot of interesting news for you, I will write a couple of posts in the next days about them. Today I just wanted to give out a small quick update on Power Management, following the drill of Sebastian

So, for the next 2 weeks (and given the freeze time) I happily try to declare and organize the Power Management bug weeks! 2 weeks in which I will dedicate to clear out the list of bugs in Powerdevil and Solid::PowerManagement. Of course I will need your help. It would be nice to have a “central” day, like a small powermanagement bug day in the middle of that. Since I never did such a thing, it would be nice to have some info/help from our bugsquad.

In the meanwhile, if you feel like closing some duplicates, reproducing and providing more information on existing bugs, it would be an extremely valuable help.

More news on completely different stuff coming up soon, stay tuned

E’  apparso in rete un video che illustra un trailer della release di Qt 4.6 e ne annuncia l’arrivo per la prima settimana di dicembre compresa una versione anche per Symbian

Qt rappresenterà una ventata d’aria fresca per i nostri Symbian? Speriamo!

Nueva propuesta de promoción del mejor desktop del mundo,KDE, y además no tiene excusa ya que es multiplataforma, Windows incluido.

Aquí una muestra:

1st Corinthians 13:7d.

“… endures all things …”

This is the hardest call to be made for a believer being challenged to love.  There are a few things about this verse that really strike me, but even before getting to that, I fear there is a great misconception about this particular call we have, as Paul writes to the church in Corinth.  At face value, much like the call to bear, believe, and hope, the object that is described here is “all things,” and I think all things as I have been studying the last few days, is a matter of proper perspective.  Clearly we are not meant to believe everything, bear everything, hope in everything, since there is plenty in this world that would cause us great harm, should we blindly take that interpretation of the passage.  Instead, the object of our endurance, is instead the motive and reasoning behind that endurance.  I argue that enduring all things is a matter of understanding our place before God.  Knowing for whom, and by whom, and through whom we are living, is literally the only thing we as humans need to endure anything.  For example, why endure through a long line at best buy to check out, the reason is because you know that by enduring, you’ll eventually be able to pay and get what you want.  Why endure through work every day from 8 to 5?  Because you know you’ll eventually get paid for it.  Our motivations drive us. 

Now, in the case of enduring things, we are very selective about our endurance.  It goes to show that our interpretation of ‘endures all things,’ can more readily be translated to ‘endures selective things.’  There’s a reason why Paul, begins this list with bears all things, then ends it with endures all things.  The meaning is similar, but different as well.  To bear something is a matter of having the brunt of life’s reality and the truth of gospel together, as something we bear, and take on.  The endurance aspect is one that is set to last a while.  To bear is to live through the initial hits of life’s difficulties and struggles as a believer, while the endurance aspect is one that is long suffering and persevering.  Now both are necessary since the initial hit of difficult circumstances in our lives can simply crush us under their weight and pressure, so we are called to love in such a way that gives us remedy to brace against those hits.  At the same time, we are meant to endure through those things, should they persist.  Almost everything in life maintains its difficulty, and is mitigated over a long period of time.  With that said, Paul is admonishing us to be believers who bear the brunt of the initial hits, and endure through the inevitable persistence of those circumstances. 

It is important to be reminded that enduring all things, doesn’t mean that believers are to become punching bags for everyone around them.  But I think in the context of living with patience and love for people, it does mean believers are called to endure through things in such a way that the gospel wins, that the message and love of Christ is exuded to others, and the kingdom wins.  That may seem like a very general mindset to have, and hard to apply in the moment, but if life was simply about rule following, God would have made it so.  The ability to have motivation for doing things negates the mere rule following mentality, since it is our heart that dictates whether or not it has any substance to the kingdom of not.  More of Christ… means more of Him in my life, means more of the natural understanding of what ‘all things’ means to me, as I am called to bear, believe, hope, and endure all things so that the gospel can win.

1st Corinthians 13:7c.

“… hopes all things …”

There is a matter of many different aspects of our lives giving us reason to doubt, and giving us reason not to explore the truth that is our God.  There are also many reasons why in our lives, we can very readily lose hope, and lose proper perspective on life in such a way that our belief in the one and only powerful God is enough for us.  Paul admonishing the church at Corinth again speaks with conviction.  After declaring that truth is what love is all about, and noting how love bears all things, believes all things are under Christ, Paul now denotes the need for love to hope in all things.

As mentioned in yesterday’s QT, the object of our hope is not merely all things, but in the character of God, in the object that is the unconditional love of our Father.  In the realm of everything that we come into contact with in our lives, to hope in all of those things seems like a very unfit and unproductive way to live your life.  And indeed, this passage is not calling us to do that at all.  But in the things that are going on in our life, our hope is to remain in the steadfast love of God, who watches over us, protects us, and guides us through the most difficult of life’s circumstances. 

Hope is not merely a function of what is believable to us, which is why Paul preceded this statement with how love believes all things.  But hope is instead a measure of what truth is.  And the truth of our lives, and of the life of every non-Christian, atheist, muslim, etc. is that we serve a God that is higher and bigger than anything.  And even if those people refuse to see it, they are living in a world that is governed by the will of God, and as Christians, our visibility is fixed on hoping on the facts, that our God is present, working, and moving in us to make us more like Him.   If that doesn’t enable you to hope, perhaps there’s a too much vested in this world.

El RVCT es el compilador de ARM que toma ventaja de las instrucciones vectoriales de los ARM es decir las intrucciones SSE, esto significa que el código será reducido al máximo, que el procesador hará más con menos “vueltas”, y al final el usuario tendrá una mejor experiencia, y de hecho si el producto final va a llevar al máximo las características del Nokia, está DEBE ser la opción elegida, por ejemplo un juego en 3d. ó un programa que maneje procesamiento de datos.

Está es una gráfica que demuestra que el código final en Dhrystone, es reducido a un 50% aproximadamente, y según la fuente, el Hello World, es reducido en un 97%.

El caso es que al instalar Qt, Carbide, y todo el SET en el Computador, uno está entusiasmado, hasta leer que el RVCT tiene costo, y que en el IDE Carbide, no existe la opción de compilar Qt con GCCE.

Pero por linea de comandos hay una alternativa.

Lo primero es llegar a la carpeta del proyecto, en mi caso es:

> cd \Symbian\Carbide\workspace\HelloWorld

Luego se ejecuta Qmake que generará los archivos necesarios para compilar.

>qmake

Esto puede tardar algunos segundo y una vez finalice estará listo para compilar, como se va a compilar con GCCE, debe darse la instrucción indicada a make.

>make release-gcce

esto si deberá tardar un poco mas, e indicará paso a paso los procesos que lleva a cabo, de tal manera que si hay un error en el código será fácil encontrar.

>patch_capabilities.pl HelloWorld_template.pkg release-gcce

>createpackage HelloWorld_template.pkg release-gcce

esté, sis se instala en el teléfono sin ningún problema.

1st Corinthians 13:7b.

“… believes all things …”

It goes to show that in the circumstances and truths of our present lives, we come to a place where doubt can very readily enter the realm of thought.  Many times, through my difficult times, I find myself wondering about what God’s will is when seemingly there is no purpose other than for it to be difficult. Still, our call to love in Spirit and in truth is the belief of all things.  This seems interesting in that believing all things is a matter of proper perspective.  Clearly we are not called to believe everything, in that ‘all’ refers to literally everything.  Meaning, if someone tells us that Jesus Christ never died on the cross, we are not called to love in believing such things.  BUT, there is a very fine granulation here, that needs to be investigated.

We are not called to believe everything we hear and experience for instance, since that is neither wisdom, nor anything close to wisdom.  But I think believing ‘all’ things is a matter of understanding that everything is under our God.  That the belief in all things is the realization that in the midst of such bad times, sin, and struggle, we are to see God and believe all things that are of Him.  Belief in His character, belief in His good and faithful heart towards us.  It’s really easy to dismiss this one, since belief in all things can be interpreted to mean belief in just things that we think are Godly, and not believing other things.  I think more accurately this passage is admonishing us to really see everything in our lives, the sin, the dirt, the difficulties, and the unholy aspects of life and know that the belief in all things is not the belief or truth of everything we experience, but is instead the belief that the character of God holds true in life.  Yes, there are definitely things not of Christ, nor of the character of God in our lives, but our belief is not in the truth or validity of those single things, but is instead in the belief that are God is above those things, stronger, and bigger than those things and able to use those things to make His children more like Him.

Belief is never a matter of circumstances making themselves believable.  Belief is a matter of faith, and really understanding, in this context, the character of God, so we can always rely on that when going through tough times.

Ithanks to LORD

FAITH

Jesus is everything!

1st Corinthians 13:7a.

“… Love bears all things …”

This morning I firmly believe the truth behind this statement.  It’s interesting because the natural instinct that we have is not to bear all things.  In fact it’s exactly to not bear anything.  It’s also interesting that in the midst of talking about love rejoicing in the truth, that Paul should follow with this statement, that love bears all things.  I think the truth is what hurts the most, the truth is what is illuminates, and gives proper perspective to situations, but ultimately is something that bears all things.  Truth in it of itself is the embodiment of everything the Word is.  The irrefutable Word of God.  Now bearing all things, a lot of times I can think of this statement as being a reflection on living up to the difficulties of being sinned against.  But what is more accurate here?

I think in light of the context, Paul is saying that bearing all things is a showing of what Christ’s love is in our lives.  Yes this is true.  But in the context of what he said prior to this statement, I also see how bearing all things is more or less the bearing of what the truth is.  Rejoicing in the truth is one thing we can do, but having to bear the truth is something entirely different, yet corollary to that as well.  When I think of bearing the truth, I think of how the truth of the Word impacts my heart, convicts, lovingly warns and admonishes.  Now since truth is in fact everything that is happening in our lives now, since those are truthful statements, that we are going through this or that, we are also called to take our life circumstances and bear them with love, as they pertain to being the truth and present of our lives.

I am compelled this morning to take my life circumstances and run with it.  Not simply as a means of JUST living for the fullest of everyday for me, but instead for the means of living for the fullest of everyday because that is how I will bear all things in my life.  Good and bad.  Time to get to work.

1st Corinthians 13:6a.

“… it does not rejoice at wrongdoing, but rejoices with the truth …”

I think because this is a contrast statement, my interpretation of it is that rejoicing in truth is to not rejoice in wrongdoing, but since rejoicing in truth is there, the wrongdoings must refer to dishonesty.  I think in the realm of loving people as Christ does, there is nothing more damaging then dishonesty.  I have seen it destroy my own life, and destroy the lives of friends.  Still it is innately a part of each of us to seek the welfare of him/herself first, even if it means bending truths, or giving half truths which are in some way, our justification for doing things.  Now this statement really sets itself apart in that we establish that rejoicing is a part of loving.  Sometimes we do not equate the two, but here it says that love rejoices, and does not rejoice as well.  There is a level of joy that I think is required for someone to rejoice in general.  I think we forget that loving someone is something that brings fulfillment and completeness to our lives.  By doing it only sparingly we are really hurting our exposure to the joy that God wishes to place in our lives. 

Let me tell you, I’m feeling pretty rejoice’y lately.  Praise God =).

It’s funny the turns Life takes.

I started programming in the eartly 1980s, on Timex Sinclair, Commodore 64 and TRS-80 computers in short order.  In those wild days when high-level languages were really coming into their own, free and open source software seemed more readily available than retail equivalents.  Hobbyist magazines, online bulletin boards and even the fledgling internet (pre WWW) were stuffed with code just waiting for eager learners like to me to take and tweak.  There wasn’t much in the way of formal free and open source protocol at the time– that evolved soon enough though.

But as I evolved myself, from hobbyist to ad hoc developer for various employers, I found myself drawn in deeper and deeper to the closed source world.  I discovered I had a liking and knack for Visual Basic and thus fell into the Microsoft development vortex.

It’s a seductive and powerful sucker, too.  It was all too easy to be “bought off” by events with (ironically) free training, free food and even giveaways of free software.  I ultimately joined a Microsoft program that dumped thousands of dollars of tools in my lap for an embarrassingly small outlay.  Resistance was futile.

Yep, I was assimilated.

Flash forward to 2005 when Nokia hired me to do data mining/management for factory quality assurance.  At first it was the usual: Microsoft SQL Server, the Office suite, VB.NET and even Oracle.  The only real challenge I faced at the time was ramping up SQL skills to an enterprise level.

Then, as I’ve mentioned in previous articles, the Nokia 770 internet tablet burst into my life.

At first it was an utterly alien object, this Linux-driven refugee from an old Star Trek show.  I only knew it mobilized the Internet like nothing else at the time… and I wanted to put it to work.

I eventually took on a new role as quality engineer for certain Nokia products and that included the 770 and then the N800, which I helped launch.  Supporting the tablets meant getting acquainted with something I had marvelled at from afar but never touched until then:

Linux.

At first I had to perform all device flashing from a Linux command line.  A helpful colleague introduced me to Ubuntu and after acquiring a laptop for the work I dug in.  Just not too deeply– I was still using Windows tools for the bulk of my labors so I didn’t really have time to invest in becoming a Linux guru… although the desire was certainly there.

And now a few years and turns later, I find myself in another role where the old trusted tools need not apply.  I haven’t even coded in VB for over a year!  Couple that with my current employer’s strong desire to save money and wham!  I’m back in the open source world.

Which is fine because I’m embarrassed that after a few years embedded in the Maemo culture I’ve barely picked up anything.  I want to do more application testing and even some development but I still lack the foundation.

So I’m excited by the opportunity I have in my employment to investigate a process workflow solution (more on that in another article) that’s completely open source and takes full advantage of the open source ecosystem (MySQL, Apache, OpenBravo, Knowledgetree, Zimbra).  This is my chance to pull free of the Microsoft vortex, at least a little bit, and gain some proficiency in what I think will ultimately become the status quo.

I’m ready now to get into Qt… Python… and whatever else looks useful.  How-To posts like those at talk.maemo.org showing how to get Windows developers onto Maemo devices are just adding irresistable fuel to the fire.

Hello (open source) World, here I (finally) come!

Salux !

Comme vous le savez peut-être, DbMaster est un projet d’étude. Malheureusement, il n’est pas le seul, et étant donné qu’il attendra bientôt ses objectifs pour le BTS, je le mettrai en pause jusqu’au mois de juillet. Je reste ouvert à toute suggestion en attendant, et il y aura peut-être des mises à jour de maintenance.

Pour autant, cela ne satisfait pas à passer DbMaster en version 1.0. Je trouve le nombre de fonctionnalités encore trop faible et il y a bien trop de bogues à résoudre. Une version 0.5 sera publiée bientôt, afin de clore temporairement le développement (comme expliqué plus haut).

Côté nouveautés pour la 0.5 :

• Nettoyage du code : DbMaster est plus léger, plus rapide et plus stable (heureusement).
• Auto-complétion SQL
• Analyse de contexte (coloration des noms de tables/champs)
• Exécution de sous-requêtes

1st Corinthians 13:5b.

“… it is not irritable or resentful…”

In the greek translation of the Word, the passage actually says it is not irritable and does not count up wrong doing.  I think at its core there’s a very strong sentiment for all of us to do this.  If there’s one thing I think God has gifted me with, it’s a heart that is not one that counts up wrong doing.  I think much more than a typical person, God gave me the means to just forgive, and forget, even if the circumstances are terrible.  At the end of the day my sentiment is that I know people have been wronged by me, and hurt by me, and more importantly, God has been wounded, hurt, Jesus died for me because of the ways that sin has taken over my life at times, and because of all of those circumstances, I am pressed and compelled to simply forgive and forget the past. 

It’s scary the way that people can be people who store up rocks.  It’s scary the way that believers are usually the ones that store up the most rocks to throw.  I think it’s true that in ways, believers are the ones who are the most judgmental, believers are the ones who hold the grudges, and take wrongdoings done to them, hold on to them, and use them for ammunition later on, or use them as leverage later on to get their own way.  I say and say again, that this practice cannot be a part of how we live our lives as believers.  The moment we take loving people, and equate it with some form of ‘pharisaical discernment’ we lose on the true purpose of the Word, and the intent that is being depicted here by Paul. 

I think about the ways that I store up rocks, I store up people’s discrediting factors and use them to pass a presumptuous assumption about them, essentially judging.  Though the ability to forgive and forget is something that comes very naturally to me, I think in other ways, I do store up rocks to throw, I do keep a record in a sense.  And as much as I do that, I must strive to completely forgive.  Where I do not hold people to the stake of their past, I do hold people to the stake of their present.  That much is true.  Where I think that is a biblical stance, it is incomplete since we cannot merely look at people’s present, and see not the potential that they can be.  Most people look at someone’s past, and don’t look at their present or future, some people look at someone’s past and present, and don’t look at their future.  Some people look at the present, but forget the past and future.  Some people look at the future and forget the present and past. 

Where I do not think any of these things are really optimal in the sense that God calls us to be one way or the other, I do see biblical backing in being able to see the past in a way such that it is not judgmental or being used against someone, seeing the present as a marker to see how someone is doing and growing, but as Christ looks at us, we must have mainly a heart for the future, seeing the potential and growth that is to come.  If we are people who do not rely on faith, and the reliance of God truly working in the lives of people around us, then we are bound to the limiting factors of what is readily discernable instead of living totally in faith.  I do this all the time unfortunately, and where I am readily able not to judge about the past, I do have limited visibility of someone’s potential, and concentrate a lot on the present.  Where there may be validity to that at times, to be losing sight of all three factors is not what the Word says. 

I am pressed this morning to live this out in how I minister to people in my care.  Being indiscriminate  is a crucial tool in ministry, and that is exactly what I must strive and grow to be.  Some people are hard to love, tough, I gotta get over it, and simply love as Christ does.  Where do I get off thinking that God’s love is applicable to me always, and selectively applicable to others.  Gotta pluck that out now, and turn my eyes to Jesus so that when I look on others, I can be in a state of Godly blindness to judgment on them, and simply love as Christ does.

1st Corinthians 13:5.

“… It does not insist on its own way …”

Welcome to rebuke!  Truly loving as Christ loves means not to insist on its own way.  This is the plague I think of every single person in this world.  If it goes unchecked, you get… the world, exactly the issues that the world presents, you get those things.  Unfortunately, because the whole world operates with the premise that insisting on your own way is the way to live, it makes it extremely difficult to live in the world.  Therein lies the exact rebuke I am experiencing as I read this about how to love people.  Since the love of Christ does not insist on its own way it means to put the kingdom’s good above the good of self.  We have to be careful because this verse is not saying that our lives must be lived not following the direction that we firmly believe we should be living.  It also doesn’t say that we have to simply do what people around us want to do instead of standing our ground.  Instead, the way I see it is that we must be people who do not insist on our own way, but instead insist that in the end, the gospel wins, the kingdom wins.

The initial thoughts about this passage bring to mind the latter thought which is to not insist on your own way immediately means to die to yourself and simply allow things to happen instead of proactively moving with conviction and purpose.  The differences have to be pretty stark.  I think it might be easy for us to think that dying to ourselves is the call that is being made in this passage.  But thinking deeper is the love of Christ that is not simply robot checklist love, but it is a specialized, person by person understanding of circumstance and experience.  We cannot be people held simply to a standard checklist of what love should be, but should be specific, and relevant in each moment, and exemplify the character of God in every way that we deal with people.  Insisting not on our own way, but insisting instead on the character of God being shown, Christ being shown.

It’s interesting because that would seem to be the case with being a believer that people readily forget about.  People suddenly realize how hard it is to simply love people where they are at.  Exude Christ to other people given their circumstances, their interpretation of the situation, their emotions, instead of thinking what you think and forcing it on them.  Now, at times, there are appropriate measures that should be taken to that effect, but with the heart that is really loving and insisting what the Word says, and not what is coming from merely the mouth as lip service.  It said before in this passage that if we have not love, then even our words, and the words of angels are like clanging cymbals and gongs.  Totally ineffectual.  Being relevant and loving in the context of fighting hard to contextualize being Christ is always the hard thing to do, but I see that is the call that is made here.