> Hi Michele,
> you misunderstood. It compiles and installs OK, but I do not see
> the "extension" when I rightclick the trash bin and go for properties.
> My question is how the tdeio system works and how those protocol/desktop
> files fit together - where can I read about it?
> How can I test this after compiling (without installing)?
> I have the so and la files that go into /opt/trinity/lib/trinity
> thanks in advance
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
and navigate around from there.