Tuesday, October 12, 2004

New PyQLogger release!

Theres a new version available: 1.2.1, which was planned to be just a bugfix release, but incorporated some really nice new features and changes aswell.
Here is a quote from changelog:
+ Added new version notification
+ Added icon to the window
* Changed taborder in wizard
+ Wrote first test case for AtomBlog (see blog for link)
+ Added export feature for posts
- Cleaned up the BG module. Less code now, no notify() method.
- Minor bugs fixed
* Changed the settings format. Its incompatible with previous version.
Sorry, but it was needed, since previous format did not allow the user to store list of posts for multiple blogs.
* Changed the UI to represent the ability to control multiple blogs

The 1.3 version will be next major update, with toolbar plugins

As usual the release can be found at Savannah and PyPI


Li-Zhao 李钊 said...

wow, excellent,
this is the only tool i have seen that can edit a post's title.
and its feature of save as draft is my favorite.

how about add a feature to backup whole blog?

PS: pyqlogger.py cannot exit, it just close GUI interface. is it a bug or what should to do?

Li Zhao, LIZhao

Li-Zhao 李钊 said...

another question, is it possible to edit a post's date?

Li-Zhao 李钊 said...

oh, sorry, will you add international chars support?

Sir Reflog said...

Great to hear from a pleased user :)
Now about your requests:
1st. about exiting problem - you are absolutely right, and i will get it fixed
2nd. about date editing - it can be done, but why? i just dont really see a reason for it, but it can be done rather easily, i will add it to TODO list.
3rd. i will complete it in 1.3 version (it's rather easy in python, just need to do it carefully)

Anyway, thanks for comments, and watch out for new releases :)

Li-Zhao 李钊 said...

one of my friend want to move from her blog server to blogger and want to move some posts from old one. so, it's very important for her to modify date. :-) right?
and u know, using blogthis to post dozens posts is very boring. much easier to do it using ur client.

another reason why i like the feature of backup as local draft is bcz it provide a potential to use ur client to move from other server to blogger quickly, if pyqlogger can post multiple posts.

thanks again.

Li-Zhao 李钊 said...

i installed 1.3.2 on a debian, and when i setup in the configuration windows, it cannot fetch blog list. what can i do?

PS: on another debian, everything is OK.
thanks very much

Sir Reflog said...

Hi Li.

Sorry for not answering, I didn't realize that I couldn't mail back to blog comment notifications...

Anyway, that's what I wrote to you in mail:

Good day!

Well, since PyQLogger is very beta-quality software, there isn't much
error checking there... So ANY network problem would cause this. What
you can do to try and help me help you, is to go to
"SetupWizardForm_Impl.py" line 121, and replace it with this:
except Exception, e:
fetch list of blogs (%s)!"%(str(e)))

and run setup again. when it fails, send me the error string it
reports, and i'll try to figure it out.


Li-Zhao 李钊 said...

thank ur reply.

why i replace both line 121 and 122 with:

except Exception, e:
QMessageBox.critical(self,"Error","Couldn't fetch list of blogs!"+str(e))

there is an error when i start pyqlogger:

Traceback (most recent call last):
File "/usr/bin/pyqlogger.py", line 59, in ?
File "/usr/bin/pyqlogger.py", line 50, in main
if w.init():
File "/usr/lib/python2.3/site-packages/PyQLogger/MainForm_Impl.py", line 337, ininit
File "/usr/lib/python2.3/site-packages/PyQLogger/MainForm_Impl.py", line 188, inbtnSettings_clicked
File "/usr/lib/python2.3/site-packages/PyQLogger/SetupWizardForm_Impl.py", line 32, in initValues
if params.has_key("login") :self.editLogin.setText(params["login"])
AttributeError: PyQLoggerConfig instance has no attribute 'has_key'

thanks again

Li-Zhao 李钊 said...

i must say, this time, the error returned is not the same as last time. hehe

sorry for that i know nothing about python. :-)

Sir Reflog said...

Hi Li.
Sorry PyQlogger still doesn't play nice with you :(
Anyway, what version are u using? Judging by the stack trace u posted, it's not 1.3.3, and i really recommend upgrading to it. If not - i'll have to think of a better answer :)

Btw, it's better if u contact me at gmail. More convinitent.