After fixing some old dnd related bugs, I'm now trying to make desktop
icons movable and it's already 50% finished.
If things go smoothly, movable icon might be provided in 0.9.8.
I, however, encounter an issue, again, the config file path.
PCManFM allows using different config files.
Previously this is achieved by pcmanfm --profile <name>.
This will make pcmanfm load ~/.config/pcmanfm/<name>.conf.
It works well, but if I want to extand it and add more config files,
there will be problems.
For example, if I want to store the position of icons in a separate
config file other than <name>.conf, this can create problem.
The more appropriate path for config files seems to be
~/.config/pcmanfm/<profile name>/main.conf
~/.config/pcmanfm/<profile name>/desktop-icons.conf
~/.config/pcmanfm/<profile name>/*.conf

This looks much more reasonable and logical, but changing this part
can create backward incompatibility.
Absolutely, this kind of change is not desired. But since we had no
stable release and it's still a "work in progress",
maybe we can have more room for this issue? Some design errors should
be fixed at this point I think.
"Once there is a stable release, I won't change the config file again
and will maintain backward compatibility."

So I'd like to know, if I change this, how many things/packages will
be affected or be broken?

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list

Reply via email to