DevLog: How It Worked(QuickPress)

This will be of no use to you. This is just a log of how QuickPress came into life.

  • Had to install the tools required- PyQt4, PyKDE4(Linux),pyuic4,python-wordpress-xmlrpc,lxml
  • Designed the user interface in QtDesigner which generated the .ui file. This could have been coded, but I hate diving into documentation for reasonably trivial thingies. The greatest advantage was by looking at the code generated, I learnt GUI Programming and learning from code is far better than any of the best books. Sort of Reverse Engineering
  • Generated the python script from ui file using pyuic4.
  • Wrote the main handler script which imports the designed GUI Object and wrote a thin wrapper to modify its properties. This is where my actual code goes.
  • Time to turn it into an executable that runs on multiple platforms. Why else could anybody choose Qt for?
  • Used PyInstaller. The process was way too smooth for windows. In Linux there were bugs, in hooks for importing modules. Worked it out by hardcoding the buggy import statement in the raw Python Script.
  • Everything else, pyinstaller and its long schezophrenic log messages took care.
  • For Gnome, KDE I had to write a QuickPress.desktop configuration file, that took care of linux specific stuff.
  • …..and Finally, It was done. I anticipated a slower performance, since it was written with a scripting language, but to my surprise, the app responded exceptionally perfect.
  • My First GUI app, a Greeting card Application, written in Java was responding a little bit faster than a turtle walk, to the GUI events! That should be so, because it had to draw its own interface using its swing or awt classes.
  • But in QuickPress, Qt was just a binding to the OS’s native GUI elements. that made it faster and better. Even, its looks gently morphed with the OS’s native looks and gives a homely touch.
  • And here comes Sunday Morn! Time to sleep.

via QuickPress