22 Sep
2016
22 Sep
'16
2:44 p.m.
Michele Calgaro wrote:
Ok thanks so far. I also found few examples how it would work via dcop, so
now only the last question remains unanswered. In the case of this feature
that would extend the dialog on the trashbin. How do you test it. From the
Makefile.am and the .desktop file there should be a ktrashpropsdlgplugin.so
lib that should do the job.
How is the system supposed to load and exec this lib? How can this lib be
tested?
perhaps the .desktop file is just wrong and it should all go into a single
tdeio_trash.so ?
Thanks
> Yes, I thought your question was deeper in fact.
>
> tdeio system is in principle "simple". When an application needs a file
> (whether a local one or remote one), is uses a tdeio job to request it. A
> corresponding tdeio-slave will actually do the work to get the file and
> send back to the tdeio requesting application. Under the hood, there is
> much more going on, including task scheduling for asynchronous tasks.
>
> Not sure there is some documentation about it. I recently had to dwell
> into the tdeio subsystem to debug bug 2685 and I found useful info in the
> tdelibs html files related to the class involved. See tdeio/tdeio
> documentations in tdelibs
>
file:///opt/trinity/share/doc/tde/HTML/en/tdelibs-apidocs/tdeio/tdeio/html/classTDEIO_1_1Job.html
and navigate
around from there.
Cheers
Michele
Forgot to mention that protocols are special instances of tdeio-slaves
that make a speficic file available through a given protocol.
For example an ftp tdeio-slaves will make a file on an ftp server looks
like a local file to any tde application.