wish - store and reuse xml cache localy

Bug #499443 reported by Ferdinand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE OpenObject Client
New
Wishlist
Unassigned

Bug Description

on slow lines it would speed up starting koo considerably if the xml info could be stored locally and be reused
in production systems this would be the normal case.
koo - server module should be able to tell koo client if (and which) modules have changed and a reload is necessary

I am specially addressing this issue having costly and/or slow mobile internet connections in mind.

Changed in openobject-client-kde:
importance: Undecided → Wishlist
Revision history for this message
olefoxe (olaf-vocks) wrote :

Hi

I think not only the starting time is very slow, the whole Client in comparison to the gtk-client is slow. My koo runs on windows 7. Don't know why?

Ole

Revision history for this message
Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan) wrote : Re: [Bug 499443] Re: wish - store and reuse xml cache localy

A Dijous, 14 de gener de 2010, olefoxe va escriure:
> Hi
>
> I think not only the starting time is very slow, the whole Client in
> comparison to the gtk-client is slow. My koo runs on windows 7. Don't
> know why?

Koo with Pyro and properly configured is much faster than GTK client. Just to
start, you may want to install 'koo' module on the server. That will probably
solve the "very slow" issue you mention.

Then you can configure some default settings to enable client cache and
install pyro module.

>
>
> Ole
>

--
Albert Cervera i Areny
http://www.NaN-tic.com
Mòbil: +34 669 40 40 18

Revision history for this message
olefoxe (olaf-vocks) wrote :

Hi

ok i have to believe in you, because it is not posible for me to install the pyro module.

these are the modules to update:

fts-indexes : to install
pyro : to install
smart_attach : to instal

i got this message:

ImportError: No module named PyQt4.QtCore

any idee?

Thank you.

Ole

Revision history for this message
Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan) wrote :

A Dijous, 14 de gener de 2010, olefoxe va escriure:
> Hi
>
> ok i have to believe in you, because it is not posible for me to install
> the pyro module.
>
> these are the modules to update:
>
> fts-indexes : to install
> pyro : to install
> smart_attach : to instal
>
> i got this message:
>
> ImportError: No module named PyQt4.QtCore

smart_attach depends on PyQt, you need it installed on your system if you want
to use it.

But pyro does NOT depend on fts-indexes nor smart_attach...

>
> any idee?
>
> Thank you.
>
> Ole
>

--
Albert Cervera i Areny
http://www.NaN-tic.com
Mòbil: +34 669 40 40 18

Revision history for this message
olefoxe (olaf-vocks) wrote :

Hi,

this was the first thing i did yesterday after the "ImportError".
I installed PyQt like Rob http://www.oak-tree.us/blog/index.php/2009/05/12/pyqt-windows

qt-sdk-win-opensource-2009.05
python-2.5.4
sip-4.10-snapshot-20100108
PyQt-win-gpl-4.6.2

And i also put this: C:\Program Files\Koo in the Path Variable.

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Windows\Qt\mingw\bin;C:\Windows\Python25;C:\Windows\Qt\qt\bin;C:\Program Files\jEdit;C:\Program Files\Koo

Starting my Python 2.5.4 and test QT
>>> print SIP_VERSION_STR
4.10-snapshot-20100108
>>> print QT_VERSION
263680
>>> print PYQT_VERSION_STR
4.6.2

After that a installed Pyro-3.10.win32.exe, but still the same problem.

maybe i have to tell smart_attach.py where QtCore is?

so i try this now, i put "from sip import *" in the .py:

line 39 and 40 in the smart_attach.py
import ocr
from PyQt4.QtCore import *
from sip import *

Thank you

Olaf

Revision history for this message
olefoxe (olaf-vocks) wrote :

Hi,
when i try to install the moduls alone i got this message from the pyro modul:

ImportError: No module named Pyro.core

And this for smart_attach

ImportError: No module named PyQt4.QtCore

So these are different things but i think the same reason,.

Thank you

Olaf

Revision history for this message
Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan) wrote :

A Divendres, 15 de gener de 2010, olefoxe va escriure:
> Hi,
>
> this was the first thing i did yesterday after the "ImportError".
> I installed PyQt like Rob
> http://www.oak-tree.us/blog/index.php/2009/05/12/pyqt-windows

Oh. Now I understand, you're running it on Windows. I'm sorry I have zero
experience running those modules on a Windows server.

Because of the way the server may be packaged it probably can't find the
modules you installed. You may try to download (don't know if you're already
doing that) server from bazaar or use source code and install python and the
rest of the packages individually. Then I think pyro would work, but I
understand that this is a mess compared to the standard windows installer.

If you succeed, we can document it somewhere in the modules, but I'm afraid I
can't help you very much there...

>
> qt-sdk-win-opensource-2009.05
> python-2.5.4
> sip-4.10-snapshot-20100108
> PyQt-win-gpl-4.6.2
>
> And i also put this: C:\Program Files\Koo in the Path Variable.
>
> %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\
> System32\WindowsPowerShell\v1.0\;C:\Windows\Qt\mingw\bin;C:\Windows\Python2
> 5;C:\Windows\Qt\qt\bin;C:\Program Files\jEdit;C:\Program Files\Koo
>
> Starting my Python 2.5.4 and test QT
>
> >>> print SIP_VERSION_STR
>
> 4.10-snapshot-20100108
>
> >>> print QT_VERSION
>
> 263680
>
> >>> print PYQT_VERSION_STR
>
> 4.6.2
>
> After that a installed Pyro-3.10.win32.exe, but still the same problem.
>
> maybe i have to tell smart_attach.py where QtCore is?
>
> so i try this now, i put "from sip import *" in the .py:
>
> line 39 and 40 in the smart_attach.py
> import ocr
> from PyQt4.QtCore import *
> from sip import *
>
> Thank you
>
> Olaf
>

--
Albert Cervera i Areny
http://www.NaN-tic.com
Mòbil: +34 669 40 40 18

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.