xfce design and impl. ideas

[Sridhar R]

hi,

Increase in features will decrease the speed.  This is
wrong and one should code apps in a way that makes
such statements false!

I propose some techniques mostly on xfce4-panel.

1. First xfce4-panel should be memory efficient 
   in its algorithms and semantics so that loading
   of many more plugins won't consume much memory.

2. Just consider the notes plugin.  It is not often
   needed.  So it can be stored in disk.  When it is
   needed it can be loaded (dlopen()?).

3. But not the others, like clock plugin.

4. Don't store configuration data-structures in 
   memory.  For example, in notes plugin text may
   not be stored in memory (except in gtkentry)
   Store/read from disk.

5. xfrun4 need not be a seperate executable.  Pressing
   Alt+F2 to load xfrun4 takes some time, since
   it has to read the code from disk and load it
   into memory.  Instead if it is built in into one
   of the xfce components code, it will open faster.
   
6. In general, there should be a architecture, that
   supports caching up executables on disk!
   xfcache4??
   
bye,


=====
-----------------------
| Sridhar R
| Best advice: http://catb.org/~esr/faqs/hacker-howto.html
-----------------------

__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/