Multiple instances of Firedrop2Manager causing path problems

0 views
Skip to first unread message

Adalbert Prokop

unread,
Apr 30, 2006, 11:00:10 AM4/30/06
to fire...@googlegroups.com
Since now I have slightly more time than in the last three months, I
finally decided to upgrade Firedrop from V.0.1 to V.0.2.1.

I use Fedora Core 4 Linux and installed Firedrop globally. There are some
changes one has to make, to get it to work. Mostly the problems origin in
hardcoded paths - in a global installation ordinary users do NOT have
write access to the firedrop2 directory. But these are minor problems I
can report later.

My problem is the entry.ini. Firedrop opens and saves it in the firedrop2
directory (firedrop2manager.py: self.whereami). I thought it might be
better to read this file from the site directory, so I changed the path to
self.dir. But when I create a new entry, self.dir is not the path to the
site directory but points to "None".

That's because in mainframe.py the function CreateNewEntryDialog calls
dlg = createnewentrydialog.CreateNewEntryDialog(self, "Create new entry")
and this function creates a *new* firedrop2manager-object. And this new
object does not know anything about the current site. Is there a
possibility to pass the current manager-object to CreateNewEntryDialog in
createnewentrydialog? I do not understand enough of Wax to make those
changes myself.

Bye,
Adalbert.
--
Government's Law: There is an exception to all laws.

Stewart Midwinter

unread,
Apr 30, 2006, 11:54:45 AM4/30/06
to fire...@googlegroups.com
hi Adalbert:

Good idea to upgrade - there have been many changes to Firedrop since v0.1 !!

we're about to relase v.0.2.2, which hopefully addresses these
problems. I included a feature that creates a settings directory
inside the user's home directory, specifically to address the issue of
permissions. It will be good to have you test that feature.

also, the issue you mention about the new entry dialog has also been raised.

The release should be in the next day or two.

If you find more bugs, you're encouraged to file reports here, or
preferably on the Trac site (http://firedrop2.python-hosting.com/) as
a ticket.

cheers
S

Adalbert Prokop

unread,
Apr 30, 2006, 5:51:24 PM4/30/06
to fire...@googlegroups.com
Stewart Midwinter schrieb am Sonntag, 30. April 2006 17:54:

Hi Stewart!

> we're about to relase v.0.2.2, which hopefully addresses these
> problems. I included a feature that creates a settings directory
> inside the user's home directory, specifically to address the issue of
> permissions. It will be good to have you test that feature.

All right then... I'm really curious about it. :)

Bye,
Adalbert
--
Old mail has arrived.

Adalbert Prokop

unread,
May 20, 2006, 6:31:19 PM5/20/06
to fire...@googlegroups.com
Stewart Midwinter wrote on April 30th, 2006 17:54:

> we're about to relase v.0.2.2,

Any luck with it?

Bye
Adalbert
--
Jones' Second Law: The man who smiles when things go wrong has thought of
someone to blame it on.

Michael Foord

unread,
May 20, 2006, 6:37:43 PM5/20/06
to fire...@googlegroups.com
Adalbert Prokop wrote:
> Stewart Midwinter wrote on April 30th, 2006 17:54:
>
>
>> we're about to relase v.0.2.2,
>>
>
> Any luck with it?
>
>

The new version includes the Themes plugin and various other fixes.

Having *finally* got two documents out of the way Firedrop2 is my top
priority.

There is a bit of work to do (commenting out a feature that isn't quite
ready, and sorting the docs).

Hopefully it will be done within the week, which is what I said a few
weeks ago...

Fuzzyman
http://www.voidspace.org.uk/python/shareware.shtml

> Bye
> Adalbert
>

Reply all
Reply to author
Forward
0 new messages