File: TODO

package info (click to toggle)
fvwm-crystal 3.4.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: buster, stretch
  • size: 21,700 kB
  • ctags: 1,494
  • sloc: sh: 3,265; cs: 1,335; python: 875; makefile: 214
file content (128 lines) | stat: -rw-r--r-- 5,379 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
FVWM-Crystal TODO / Roadmap
===========================

The content of this file is a relic. Anyway, I done so much bug fixes and
improvements that the next release number will certainly divert from what
is described here. My priority was first to fix existing functions like
Fullscreen. This was not only wanted, but also needed, because to have
good working functions is the only way to go in order to exploit them
to their full potential.

I will keep the rest of this file like it is for historical raison,
and also because it is some good ideas. 

- The colorset implementation sucks. Need standardisation, extension and more
  colorsets.

- As mentionned by harnir, pixmaps implementation sucks too. This is not
  limited to colorsets but seam mostly related with flaky Xorg drivers
  and maybe also transparency support.
  
- The FvwmScripts are not internationalized.

- Investigate how it is possible to make a FvwmScript Font Selector. It must be
  possible to show not only the font name, but also how it look.

- More recipes, especialy for wide-screen (16/9, ...) screens. Maybe put
  all the decorations and the title bars on the left or the right.

- One directory per recipe? I am not sure. It would be nice to find a way
  to create wrappers for the decorations. That would simplify the code in
  the recipes, but presnet the risk of standardisation.
  Also, study the configuration of Fvwm-Nightshade. It have very nice decorations,
  is simple and is well commented.

- More players, especialy the multimedia ones like xine or VLC.

- MPlayer sucks. MPlayer2 sucks too. This seam to be related with flaky X graphic
  drivers. Not much to do here. Ctrl-Alt-F<n> and kill(all) are our friends.

- The Expose clone sucks. It is very flaky. Find a way to swallow display but
  with transparency, or find another application than display which will 
  support transparency.

The Relic
=========
* Version 3.0.5 (devel)

I'm thinking about releasing this one as a "development" release, since last
version was released many months ago... It would be good to show that project
is not dead. Preferred date of the release - end of April 2007.

- remove all non-free icons from the source tree; that would be the Firefox
  icon, commercial application and game icons, and other with unknown license
  terms. For now applications can go without replacement icons, but if you
  have some on the free license, bring 'em on;

- add support for stalonetray/trayer in all current recipes;

- synchronize application and menu icons with the Tango Project. Good source
  of icons is on the http://tango.freedesktop.org/Tango_Fridays site;

- add support for gnome-session proposed by Dominique Michel;


* Version 3.0.6 (stable)

This version should be focused on polishing current code, removing bugs and
adding missing translations and documentation. Proposed release date: summer
2007 (July or August probably).

- create a downloadable package or repository with all non-free application
  icons, so users can easily download them and use on their desktops if they
  wish. I know that not all apps will have free icon alternatives and some
  people prefer Mozilla Firefox logo instead of IceWeasel;

- find a way to better handling of 'fvwm-crystal-minimal' vs main version.
  I just don't feel that it's very useful at the moment, maybe there's
  a better way to do this? Possible way is to split the package into:
  
  'fvwm-crystal' - main "core", 1 or 2 window decorations (preferably Crystal
  and Clearlooks), some application icons (xterm.png, default.png,
  directory.png, something else?), 1 wallpaper (fvwm-crystal-dark1)

  'fvwm-crystal-artwork' - rest of the wallpapers/window decorations/icons,
  optional

  That way Crystal will be either small but functional (good for LiveCD) or
  big and colorful ("normal" distributions);

- add new translations, update the current ones with the missing strings;

- debug all recipes;

- add the documentation sources in DocBook format, create a Makefile entry to
  easily generate the different documentation formats from DocBook;

- write a doc about Crystal's configuration structure and initialization
  process - it's somewhere on the list, but the better place would be to
  include it in the doc/ directory;

- finish writing FAQ and Application database documentation;

- update all window decorations to support UTF-8 strings (similar way as the
  menu supports it, although this way is a dirty hack, maybe in the newest
  FVWM release it's already fixed?);

- clean up the application database - support for xfg menu structure is nice,
  but for me still some applications are in different sections than they
  should be. Add icons for as many applications as we can;


* After 3.0.7

New ideas, scripts and configurations... Any thoughts?

- add gettext support for FvwmApplet-MpdPlEd

- do something with colorsets, they suck... I just don't know if
  implementation in Crystal sucks or how FVWM handles colorsets suck ;)
  Anyway, pixmapped panels would be cool, but how to make good
  horizontal/vertical themes?

  Integrate colorsets with recipes. Put recipes in subdirectories, so they can
  use their own pixmaps for shaped panels, etc. Colorset numbers need to be
  changed: #1-#4 for window decorations (that's max they can use anyway), the
  rest for panels/menus/forms, depending on the recipe.