mirror of
https://github.com/gryf/wmaker.git
synced 2025-12-29 01:42:32 +01:00
08e811aae7
This was we internally only deal with fc names and properties. It will incur a small performance hit as the font needs to be parsed/unparsed, but this is only for backward-compatibility to support old xlfd names. People are encouraged to swtich to fontconfig names. - WINGs no longer adds sans as a fallback for internal fonts. It is automatically done by fontconfig (if it can't find the requested font it will use the closest match which is the default font: sans-serif) - Added code to honor the AntialiasesText global option - Fixed style names for WMCopyFontWithStyle() - Added fonts in style files where they were missing. Also changed some fonts to better defaults.
76 lines
3.1 KiB
Plaintext
76 lines
3.1 KiB
Plaintext
To do before next release:
|
|
--------------------------
|
|
- Fix font conversion (in WINGs, with convertfonts, setstyle and getstyle)
|
|
in WINGs convert automatically for a while (remove in later versions
|
|
and give a warning if font is not converted, but let user manually convert
|
|
it with convertfonts as the process may need manual tweaking for best
|
|
results)
|
|
- check whether window states are being saved/restored properly via netwm
|
|
on restart/crash-restart (grep for XXX/TODO)
|
|
|
|
|
|
=====================================================================
|
|
|
|
remake wrlib rule to not compile with -fomit-frame-pointer and stuff
|
|
if its added to CFLAGS
|
|
|
|
Do ASAP:
|
|
========
|
|
- fix bestvisual selection code. Broken.
|
|
- fix RemakeStackList() to account for transient windows
|
|
- blink border of clients with UrgencyHint set between red and black
|
|
- finish session stuff
|
|
- remove colors_per_channel stuff from wmaker after?
|
|
+ finish the ability to browse for files/dirs in the WPrefs menu editor
|
|
|
|
Need to do:
|
|
===========
|
|
- figure out a better gnustep path for wprefs.app installation
|
|
- impelment a generic pixmap type, which receives attributes
|
|
(scaled/maxscaled/centered/tiled, smoothed, size/position, ...)
|
|
- allow user to select/restore default root menu from wprefs
|
|
- support for X11R6.4 extension for getting extra visual info in wrlib's
|
|
automatic best context guessing
|
|
- docklet to control AccessX (keyboard accessibility) functions
|
|
- rewrite all redundant stuff to use WINGs
|
|
- add function to directly make a thumbnail of an image, using the
|
|
functionality provided by the image libraries to load a minimal
|
|
amount of data.
|
|
- rewrite defaults/wdefaults stuff to use WINGs UD stuff. Search list:
|
|
~/G/D/WindowMaker /u/l/s/W/D/WindowMaker built-in-defaults
|
|
- remake internal string processing to use wchar? unicode?
|
|
- add new file for stuff like default commands and dnd commands for
|
|
docked apps, balloons for the dock etc
|
|
- check whether apps with name.class set to empty strings should be treated
|
|
like if name.class is NULL.NULL
|
|
- review the defaults handling code (not to reread after we update a
|
|
domain if possible, check WINGs apps updating WMWindowAttributes after
|
|
start making screen to flash on update)
|
|
|
|
|
|
Maybe some day:
|
|
===============
|
|
- virtual workspace
|
|
- optimize for size
|
|
|
|
|
|
Never: (so, dont even bother to ask)
|
|
======
|
|
- different themes for each workspace. Unless you give us a SGI/Power Onyx
|
|
with 2 CPUs ;).
|
|
- anything that requires the mouse pointer to be jumped by WindowMaker to
|
|
somewhere. This is *terrible* behaviour. And it's not just IMO.
|
|
- rewrite to use Gtk... I wont even bother to explain why...
|
|
|
|
|
|
- ICCCM 2.0: ICCCM 2.0 (not 1.0, which is what everybody supports so so) is
|
|
a relatively new standard and nobody, AFAIK, complies with it (not even
|
|
twm as people tend to think). It has some neat things, but many of the new
|
|
stuff is really weird and tricky to implement, not to say unworthy (read the
|
|
specs and you'll see). This is not bad, since I think it is very unlikely
|
|
that a client that requires it exists... Anyway, if we get an "official"
|
|
sample implementation (twm?) it might be supported. Maybe dtwm supports
|
|
it? I dont know...
|
|
|
|
|