Menu
▾
▴
fvwm-themes-devel — Developing FVWM Themes
You can subscribe to this list here.
| 2000 |
Jan
(40) |
Feb
(57) |
Mar
(31) |
Apr
(62) |
May
(15) |
Jun
(38) |
Jul
(46) |
Aug
(50) |
Sep
(13) |
Oct
(41) |
Nov
(65) |
Dec
(36) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(15) |
Feb
(50) |
Mar
(57) |
Apr
(10) |
May
(24) |
Jun
(10) |
Jul
(14) |
Aug
(20) |
Sep
(9) |
Oct
(32) |
Nov
(4) |
Dec
(3) |
| 2002 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
(3) |
May
(15) |
Jun
(23) |
Jul
(11) |
Aug
|
Sep
(6) |
Oct
(7) |
Nov
|
Dec
(30) |
| 2003 |
Jan
(8) |
Feb
(5) |
Mar
(4) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(5) |
Aug
|
Sep
(22) |
Oct
(30) |
Nov
(13) |
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2008 |
Jan
(1) |
Feb
|
Mar
(12) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(10) |
Oct
|
Nov
|
Dec
(4) |
|
From: Olivier C. <oli...@fr...> - 2001-02-19 22:15:35
|
Mikhael Goikhman wrote: > > Olivier, I have some questions about how we divide our tasks. > > 1) On wm-icons I can work (as time allows) on all existing icon sets, but > maybe you had plans to work on them too? > Yes and no, I've a lot of 16x16-general and kde icons like on my machine, so if you have gap I may help. Also, I've planed to add gnome icons (16x16-gnome is almost finished). Finally, I would like to reworte fvwm-themes-menuapp (a script for (re)building programs menu and (mini)icon styles). But, this need discussion; e;g., a - where to put this script? In wm-icons, in fvwm-themes, in both? b - what kind of data base we have to use? c - do we have to start a new project: wm-db? d - can we use debian system menu? ... > 2) Do we implement gradient-like active titles for colors@redmond95 > as Lorenz Minger suggested in its patch? I attach the relevant lines, > but since there are small color conflicts, I prefer you to look at it. > Ok > 3) Do you have any guesses about com problems of Andre Goeree? > Can you add some debug code in cvs and ask Andre to run with it? > (He is on this list and uses the cvs version.) > Seems this is fixed. We may suggest in the FAQ or in the INSTALL/README that it is prudent to remove (and backup) ~/.fvwm when upgrading fvwm-themes or when another config was used under this directory? Regards, Olivier |
|
From: Olivier C. <oli...@fr...> - 2001-02-19 22:15:34
|
Andre Goeree wrote: > > > On 18 Feb 2001 00:32:32 +0100, Andre Goeree wrote: > > > This is the error log: > > > > > > config-99506: No more FvwmScript-ThemesCenter: exit! > > > fvwm-themes-config: internal error 1, killing FvwmScript-ThemesCenter > > > com: No lock Fifo .tmp-com-lock-config-99506 for config-99506 communication > > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > Hmm, all my troubles with fvwm-themes suddenly disappeared when i > started with a fresh (empty) ~/.fvwm (now, why didn't i think of > that in the first place?). > Hello, Sorry to come only now in the discussion. I am happy that now every thing work and also that you can, Andre, test fvwm-themes on a BSD machine. > The "old" config files in ~/.fvwm-orig where created by > fvwm-script-setup95.pl and i have only used the default settings > (except for changing the default background color). > Searching through the files in ~/.fvwm-orig doesn't show any > strange settings. The only thing that seems missing is .FvwmForm. > I'm not sure whether this is a problem, but the file is mentioned > in other settings. > I do not see how setup95 can interact with fvwm-themes (but I do not think a lot on this). Also, it is possible that the problem came from fvwm-themes itself: a config file from an old version may be the cause of some problems ... Regards, Olivier |
|
From: Mikhael G. <mi...@ho...> - 2001-02-19 09:36:46
|
Olivier, I have some questions about how we divide our tasks. 1) On wm-icons I can work (as time allows) on all existing icon sets, but maybe you had plans to work on them too? 2) Do we implement gradient-like active titles for colors@redmond95 as Lorenz Minger suggested in its patch? I attach the relevant lines, but since there are small color conflicts, I prefer you to look at it. 3) Do you have any guesses about com problems of Andre Goeree? Can you add some debug code in cvs and ask Andre to run with it? (He is on this list and uses the cvs version.) Regards, Mikhael. |
|
From: Andre G. <abg...@uw...> - 2001-02-19 09:29:21
|
> On 18 Feb 2001 00:32:32 +0100, Andre Goeree wrote: > > This is the error log: > > > > config-99506: No more FvwmScript-ThemesCenter: exit! > > fvwm-themes-config: internal error 1, killing FvwmScript-ThemesCenter > > com: No lock Fifo .tmp-com-lock-config-99506 for config-99506 communication > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. Hmm, all my troubles with fvwm-themes suddenly disappeared when i started with a fresh (empty) ~/.fvwm (now, why didn't i think of that in the first place?). The "old" config files in ~/.fvwm-orig where created by fvwm-script-setup95.pl and i have only used the default settings (except for changing the default background color). Searching through the files in ~/.fvwm-orig doesn't show any strange settings. The only thing that seems missing is .FvwmForm. I'm not sure whether this is a problem, but the file is mentioned in other settings. At least my fvwm-themes is now *fully* functional without any problems or core dumps :-) I will keep the ~/.fvwm-orig some time in case you have any questions. Regards, -- Andre. |
|
From: Mikhael G. <mi...@ho...> - 2001-02-18 11:29:48
|
On 18 Feb 2001 10:34:08 +0100, Andre Goeree wrote: > > What i mean is that the m4 version doesn't seem to make any difference. > I tried it first with the "system" m4, same thing except that FvwmForm > core dumped on me:( (i'm not sure if this is related to m4 but changing > m4 to the version fvwm was built with sounded like a good start). We don't really use m4, it is FvwmM4 that uses it. We only warn if m4 is not found. FvwmM4 is used in colors@cde, background@cde, colors@luthien, moduls@osx and probably nowhere else. How did you configure fvwm to use gm4? There is a hardcoded "m4" string in FvwmM4.c. If you have core dump with FvwmForm, which is themes related, tell what you did to get it. If this is not themes related post your FvwmForm config. > Hmm, i like the project very much:) and i would like it to run on > FreeBSD so what's involved? (keeping up with the source code and > reading the mailing list?). Being on the mailing list may certainly help, although not neccessary. Testing CVS sources is also preferable. See the home page how to get them. You also need one of the latest fvwm versions. How often is updated FreeBSD fvwm port? Is it still incorrectly named "fvwm2" with 2 at the end? Regards, Mikhael. |
|
From: <abg...@uw...> - 2001-02-18 11:12:43
|
[snip] > Maybe Olivier has better suggestions, but I think we need your help here. > Please add some prints into checkScript in bin/fvwm-themes-config to see > whether and why it fails. Can you use the CVS version? [snip] I have cvs'ed to the latest code now and rebuild, still same thing:( What prints and more exactly where to put them in fvwm-themes-config? Although i can read and understand the code up to a certain level, you have to understand that my knowledge of perl is *very* basic at the moment. (but i'm working on it:) Now i'm up-to-date with the latest code, any patches or tests you want me to try out are welcome:) Regards, -- Andre. |
|
From: Andre G. <abg...@uw...> - 2001-02-18 09:30:31
|
On Sat, Feb 17, 2001 at 07:04:48PM -0600, Mikhael Goikhman wrote: > On 18 Feb 2001 00:32:32 +0100, Andre Goeree wrote: > > > > Hello fvwm-workers, > > I am forwarding this to the right list, fvwm-themes-devel. > These problems are not directly related to FVWM. Oops, i accidently sent it to the wrong list, luckily you read both;) I will send following messages to the right address. > > > I'm trying your latest beta version (fvwm-themes-0.4.1). > > out on FreeBSD 4.2-STABLE. Although almost everything works as it > > should, i'm having some trouble:( > > Maybe you remember me from my previous message concerning > > GNU mknod & BSD mknod. I am happy to see that the more portable > > mkfifo is used in this newer version. However this is probably part > > of the problem i'm writing about now. > > Yes, I remember. Without your reports there would be no BSD patches. > That's nice:) > > This is the error log: > > > > config-99506: No more FvwmScript-ThemesCenter: exit! > > fvwm-themes-config: internal error 1, killing FvwmScript-ThemesCenter > > com: No lock Fifo .tmp-com-lock-config-99506 for config-99506 communication > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > > > I can switch themes, i'm using fvwm-themes right now:), but whenever > > i take one of the "Fvwm Configuration" menus the above error occurs. > > > > So far i haven't made any progress in tracking the error but i haven't > > examined the code/scripts carefully yet. > > Maybe Olivier has better suggestions, but I think we need your help here. > Please add some prints into checkScript in bin/fvwm-themes-config to see > whether and why it fails. Can you use the CVS version? > Yep, i will find out how to cvs the stuff and start right away! > > Notes: > > I changed m4 in configure.in to gm4, the GNU m4 for FreeBSD. > > gm4 is also the "m4" fvwm-2.3.28 was built with but i don't > > think this could have anything to do with the error. > > perl: version 5.005_03 built for i386-freebsd > > I think the CVS version should work with non-GNU m4 now (not tested). > Or you mean something else? What i mean is that the m4 version doesn't seem to make any difference. I tried it first with the "system" m4, same thing except that FvwmForm core dumped on me:( (i'm not sure if this is related to m4 but changing m4 to the version fvwm was built with sounded like a good start). [snip] > > Additional question: My guess is that this problem has something > > to do with portability. How many (beta-)testers do you have at the > > moment testing this project on FreeBSD-i386? > > There are no official FreeBSD testers for fvwm-themes. You are the first. > The Solaris tester position is vacant too. :-) Hmm, i like the project very much:) and i would like it to run on FreeBSD so what's involved? (keeping up with the source code and reading the mailing list?). Sorry, no Solaris. > > Regards, > Mikhael. > Let's put this subject in the fridge untill i cvs'ed to the latest code and rebuild the stuff. For the moment i'm available as an unofficial (beta-)tester for your project. Once i know more about what's involved, maybe i'll become an official tester for FreeBSD-i386. If fvwm-themes proves to run reliable and stable on FreeBSD i'll try to get it into the FreeBSD ports tree, that would probably attract a boatload of testers/developers/people interested in the project:) (in fact fvwm-themes is one of my try-out projects in becoming a FreeBSD porter). I will get back to you on this subject. Regards, -- Andre. |
|
From: Dan E. <da...@mk...> - 2001-02-18 01:32:26
|
Mikhael Goikhman <mi...@ho...> writes: > The Solaris tester position is vacant too. :-) I wish I could but I'm pretty much at my limit. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Mikhael G. <mi...@ho...> - 2001-02-18 01:05:27
|
On 18 Feb 2001 00:32:32 +0100, Andre Goeree wrote: > > Hello fvwm-workers, I am forwarding this to the right list, fvwm-themes-devel. These problems are not directly related to FVWM. > I'm trying your latest beta version (fvwm-themes-0.4.1). > out on FreeBSD 4.2-STABLE. Although almost everything works as it > should, i'm having some trouble:( > Maybe you remember me from my previous message concerning > GNU mknod & BSD mknod. I am happy to see that the more portable > mkfifo is used in this newer version. However this is probably part > of the problem i'm writing about now. Yes, I remember. Without your reports there would be no BSD patches. > This is the error log: > > config-99506: No more FvwmScript-ThemesCenter: exit! > fvwm-themes-config: internal error 1, killing FvwmScript-ThemesCenter > com: No lock Fifo .tmp-com-lock-config-99506 for config-99506 communication > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > cannot open .tmp-com-buf-config-99506 at /home/ago/sys/fvwm/bin/fvwm-themes-com line 62. > > I can switch themes, i'm using fvwm-themes right now:), but whenever > i take one of the "Fvwm Configuration" menus the above error occurs. > > So far i haven't made any progress in tracking the error but i haven't > examined the code/scripts carefully yet. Maybe Olivier has better suggestions, but I think we need your help here. Please add some prints into checkScript in bin/fvwm-themes-config to see whether and why it fails. Can you use the CVS version? > Notes: > I changed m4 in configure.in to gm4, the GNU m4 for FreeBSD. > gm4 is also the "m4" fvwm-2.3.28 was built with but i don't > think this could have anything to do with the error. > perl: version 5.005_03 built for i386-freebsd I think the CVS version should work with non-GNU m4 now (not tested). Or you mean something else? > Now i hope some(one) of you can shed some light on this. I'm willing to > provide you with any information, or do any testing/debugging/patching. > Feel free to ask:). > > Please send/reply/cc any messages directly to my address as i'm no > longer subscribed to this list (i'm cutting back on my mail volume). > > Keep up the good work. > > -- Andre. > > Additional question: My guess is that this problem has something > to do with portability. How many (beta-)testers do you have at the > moment testing this project on FreeBSD-i386? There are no official FreeBSD testers for fvwm-themes. You are the first. The Solaris tester position is vacant too. :-) Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-02-17 13:47:37
|
On 17 Feb 2001 13:05:50 +0100, Olivier Chapuis wrote: > > I think that we should be agree on the 85 names so that > we can begin to work on the icons. [icon list skipped] Ok, but since we use nouns not adjectives, graphic should be renamed to graphics. Also can you give examples when this icon will be used? > Note: > * Finally I removed x and keep battery > * Really I think that program <> utility. > * I do not know what to do with xv, renaming it to gimp? It is easier to keep it for now. > * Any idea for the 85th name, gimp, science-graph, help-man? gimp or help-man are ok, although not absolutely essential. Regards, Mikhael. |
|
From: Alex W. <aw...@do...> - 2001-02-17 13:46:59
|
Olivier Chapuis wrote: > > Alex Wallis wrote: > > > > When I do.... > > awol@awol:/opt/fvwm > FvwmCommand 'FvwmScript FvwmScript-ThemesCenter > > --lang en' > > awol@awol:/opt/fvwm > > > > > I get a GUI that still looks like the attached picture. > > > > Am I missing something? > > > > Do not know ... Do you have any message in your X stderr? > Can you try: > > fvwm-themes-script --get-msg FvwmScript-ThemesCenter > > And see if this gives some errors? If not you will see a very big > line that begin with: > > ChangeFont 00001SelFont 0031-adobe-helvetica-bold-r-*-*-12-*ShadeFont > > What is your version of perl (perl -v). > > Thanks, Olivier > I'm hoping Mikhael will have fixed it by now. :-) But just for the record..... awol@awol:~ > fvwm-themes-script --get-msg FvwmScript-ThemesCenter END 0003end awol@awol:~ > perl -v This is perl, version 5.005_03 built for i586-linux I trimmed the GNU guff. Any help? Alex |
|
From: Mikhael G. <mi...@ho...> - 2001-02-17 13:28:26
|
On 17 Feb 2001 11:46:37 +0100, Olivier Chapuis wrote: > > Alex Wallis wrote: > > > > When I do.... > > awol@awol:/opt/fvwm > FvwmCommand 'FvwmScript FvwmScript-ThemesCenter > > --lang en' > > awol@awol:/opt/fvwm > > > > > I get a GUI that still looks like the attached picture. > > > > Am I missing something? > > Do not know ... Do you have any message in your X stderr? > Can you try: > > fvwm-themes-script --get-msg FvwmScript-ThemesCenter I got the same problems as Alex and intended to fix them today. Now when you gave this line I see 2 problems, one is that @datadir@ uses the default @prefix@ (/usr/local), which is incorrect, so the locale directory is not found if installed in non-default place. The second problem is that there is no any error message when the message file is not found. :-) I will fix both now. Regards, Mikhael. |
|
From: Olivier C. <oli...@fr...> - 2001-02-17 12:09:11
|
Hello, I think that we should be agree on the 85 names so that we can begin to work on the icons. Here another try of 84 names: amusement (new) battery (new) calculator cd-player chat choice-yes choice-no clock colors (new) configuration (new) development (renaming: debugger) disk disk-cd disk-floppy display editor empty file (new) file-manager (renaming: folders) folder folder-open (new) font game game-cards game-board (renaming: game-chess) game-action (new) game-logic (new) game-strategy (new) gnome (new) gnu (new) graphic (new) ghostview help home image-processor (new) image-viewer information item keyboard kde (new) mail module (new) monitoring (renaming of monitor) mouse multimedia (new) music netscape network news (new) penguin (new) printing (new) program (new) sound science (new) system (new) terminal terminal-remote (new) terminal-special (new) themes (new) todo unknown utility video (new) viewer window windows (new) window-close window-delete window-destroy window-iconify window-identify window-lower window-maximize window-move window-raise window-resize window-shade window-stick lock (renaming wm-lock) quit (renaming wm-quit) restart (renaming wm-restart) refresh (renaming wm-refresh) word-processor www xv removed: desktop, shell, xterm Note: * Finally I removed x and keep battery * Really I think that program <> utility. * I do not know what to do with xv, renaming it to gimp? * Any idea for the 85th name, gimp, science-graph, help-man? Olivier |
|
From: Olivier C. <oli...@fr...> - 2001-02-17 12:09:11
|
Alex Wallis wrote: > > When I do.... > awol@awol:/opt/fvwm > FvwmCommand 'FvwmScript FvwmScript-ThemesCenter > --lang en' > awol@awol:/opt/fvwm > > > I get a GUI that still looks like the attached picture. > > Am I missing something? > Do not know ... Do you have any message in your X stderr? Can you try: fvwm-themes-script --get-msg FvwmScript-ThemesCenter And see if this gives some errors? If not you will see a very big line that begin with: ChangeFont 00001SelFont 0031-adobe-helvetica-bold-r-*-*-12-*ShadeFont What is your version of perl (perl -v). Thanks, Olivier |
|
From: Alex W. <aw...@do...> - 2001-02-05 07:01:44
|
Alex Wallis wrote: > > I get a GUI that still looks like the attached picture. > > Am I missing something? Oops! I forgot to attach the picture.... Alex |
|
From: Alex W. <aw...@do...> - 2001-02-05 07:01:03
|
Alex Wallis wrote: > > I get a GUI that still looks like the attached picture. > > Am I missing something? > > Alex Oops! I forgot to attach the picture.... |
|
From: Alex W. <aw...@do...> - 2001-02-05 05:19:53
|
When I do.... awol@awol:/opt/fvwm > echo $LANG en awol@awol:/opt/fvwm > ls -al /opt/fvwm/locale/en/ total 27 drwxr-xr-x 2 root root 1024 Feb 4 15:23 . drwxr-xr-x 5 root root 1024 Nov 16 21:44 .. -rw-r--r-- 1 root root 907 Feb 4 15:23 FvwmScript-ColorSelector.html -rw-r--r-- 1 root root 109 Feb 4 15:23 FvwmScript-ColorSelector.msg -rw-r--r-- 1 root root 688 Dec 4 01:17 FvwmScript-ColorSelector.txt -rw-r--r-- 1 root root 117 Feb 4 15:23 FvwmScript-ComponentProperties.msg -rw-r--r-- 1 root root 6039 Feb 4 15:23 FvwmScript-ConfigCenter.msg -rw-r--r-- 1 root root 117 Nov 29 22:09 FvwmScript-ThemeOption.msg -rw-r--r-- 1 root root 5459 Feb 4 15:23 FvwmScript-ThemesCenter.html -rw-r--r-- 1 root root 2912 Feb 4 15:23 FvwmScript-ThemesCenter.msg -rw-r--r-- 1 root root 4920 Dec 4 01:17 FvwmScript-ThemesCenter.txt awol@awol:/opt/fvwm > FvwmCommand 'FvwmScript FvwmScript-ThemesCenter --lang en' awol@awol:/opt/fvwm > I get a GUI that still looks like the attached picture. Am I missing something? Alex |
|
From: Mikhael G. <mi...@ho...> - 2001-01-27 23:41:56
|
On 26 Jan 2001 11:56:39 +0100, Olivier Chapuis wrote: > > Here a 85 names proposition: > > amusements (new) amusement > battery (new; tbd see below) Ohh. Maybe monitoring? > devel (renaming: debugger) development > display (tbd: rename this one to screen?) do you mean screensaver? :) no idea > game-chess not game-board? > gnome-gnu (new) gnome > ghostview (tbd: remove it?) Seems like the de-facto standard for ps/pdf/printing. Maybe postscript... There are many icons for ghostview. > graphic graphics (noun; graphic is adjective) > printer (new) printing? > program (new) How icons of utility and program will be different? Seems like synonyms. > x (new; the x window system) Just for menus? For applications we have unknown. > xv (tbd: remove it?) This was the standard before gimp. There are many icons for xv. :) Seems like it is not included into RH by default. Bad. > This gives 28 new names and a list of 85 names (at first I get a list > of 84 names and I surely forget at least one name that we should add > to the main list. So I add battery). Moreover, if we do not want to > have more than 85 names and you think that we need others than the > above I think we can remove: xv and ghostview (and maybe netscape). > Also, maybe I make some "mistake" in this list! No, I don't want new names other than above. > Fine, but now I think that we can go further and for me a list of 100 > names is not a bad idea: I do not take a look to wm-config yet, but > I think that a few work on it can do so that it is not more difficult > to work with 100 (and even 150) names than with 85. We just have to > replace missing icons in a set by symlink following hardcoded > rules (in wm-config). It is not difficult to add new symlinks. There are other problems: * Every symlink is 4Kb on many of filesystems. * Do user want to install 1600 (or even 300) new files just to get some icons for xterm or netscape? wm-icons is also replacement for fvwm-icons. * Having an icon set with more than 50% of symlinks is not good for me. * Drawing/searching for hundreds of icons is very hard. * Documenting and veryfying licenses for hundreds of icons is hard. * Linux has a bug that only 5 levels of symlinks are allowed. The fix is trivial (one number), but I forgot to report this. So it is possible this bug is still in 2.4! You should leave at least 1 or 2 levels for directories, so you end up with only 3-4 icon symlink levels! This is why I don't want a lot of icon names. If you solve these problems, please feel free to add more names. I think now we may move this discussion to wm-icons cvs (TODO file). Regards, Mikhael. |
|
From: Olivier C. <oli...@fr...> - 2001-01-26 11:59:37
|
Hello, Here a 85 names proposition: amusements (new) battery (new; tbd see below) calculator cd-player chat choice-yes choice-no clock colors (new) configuration (new) devel (renaming: debugger) disk disk-cd disk-floppy display (tbd: rename this one to screen?) editor empty file (new) file-manager (renaming: folders) folder folder-open (new) font game game-cards game-chess game-action (new) game-logic (new) game-strategy (new) gnome-gnu (new) gnu (new) graphic (new) ghostview (tbd: remove it?) help home image-processor (new) image-viewer information item keyboard kde (new) mail module (new) monitoring (renaming of monitor) mouse multimedia (new) music netscape network news (new) penguin (new) printer (new) program (new) sound science (new) system (new) terminal terminal-remote (new) terminal-special (new) themes (new) todo unknown utility video (new) viewer window windows (new) window-close window-delete window-destroy window-iconify window-identify window-lower window-maximize window-move window-raise window-resize window-shade window-stick lock (renaming) quit (renaming) restart (renaming) refresh (renaming) word-processor www x (new; the x window system) xv (tbd: remove it?) Removed from the old list: desktop, shell, xterm This gives 28 new names and a list of 85 names (at first I get a list of 84 names and I surely forget at least one name that we should add to the main list. So I add battery). Moreover, if we do not want to have more than 85 names and you think that we need others than the above I think we can remove: xv and ghostview (and maybe netscape). Also, maybe I make some "mistake" in this list! Fine, but now I think that we can go further and for me a list of 100 names is not a bad idea: I do not take a look to wm-config yet, but I think that a few work on it can do so that it is not more difficult to work with 100 (and even 150) names than with 85. We just have to replace missing icons in a set by symlink following hardcoded rules (in wm-config). So here 12 more icons (almost with obvious symlink): archiving (new) calendar (new) connect (new) help-man (new) office (new) panel (new) pager (new) science-graph (new) science-astronomy (new) science-nature (new) text (new) winlist (new) So to go to 100 we need to choose 3 or 5 more icons. You may ask why I want office and text (for example). The reason is that these are "meta-categories" (menu popup) as editor and word-processor are just software categories. With this menus may look better. And more name applet background cursor dialup emulator file-* where * can be hex,c,ps,pdf,image, ...etc game-? hardware icq irc images-? icons package phone scanner screensaver terminal-? theme viewer-? ...etc. Olivier |
|
From: Mikhael G. <mi...@ho...> - 2001-01-22 20:52:17
|
On 22 Jan 2001 11:29:25 +0100, Olivier Chapuis wrote: > > I think that we have to add extra colors to the .db file. > I will do as follows: > 1 - add motifHilightColor and motifShadowColor in the > fvwm-themes-images.in colors library > 2 - add a new sub option to --colorscheme, say > --colorscheme-hish x,y,methode > which take the x first colors of a .db file and then replace/create > the colors y to y + x by the hi colors computed from the colors 1 to x > useing the method "method" and do the same thing with sh and colors > 1 to x and y+x+1 to y+2x I think we should change the format of our .dp files. Every .dp file has 8 lines (by number of cde colors). There may be 3 cases: 1) one color in line - bg, just like in cde .dp 2) two colors in line - bg fg 3) four colors in line - bg fg sh hi I am not sure we really need (2) if we have (3). This way the number of colors is the same as the number of lines, so we don't need to pass this number at all. Also modifications to .dp may be done in place, i.e. without temporary directory/files. And finally the format of the .dp file, (1) or (2) or (3), may be autodetected. > 3 - then, modifying themes/cde/colors/main > > Can you send a patch for 1 and possibly to 2 and 3 but I can do 2 > (when I will have the time) and 3 is easy. > Do you want write access to fvwm-themes? Just create a user in sourceforge.net. Regards, Mikhael. |
|
From: Olivier C. <oli...@fr...> - 2001-01-22 10:51:44
|
Mikhael Goikhman wrote: > > On 18 Jan 2001 23:54:11 +0100, Olivier Chapuis wrote: > > > > Now I think that we need to add a *lot* of names. > > I think you don't know yet what is it to manage 960 icons to suggest a lot > of new names! :) Even with only one icon set it may be a problem. I begin to saw: I've almost finished a 16x16-gnome icon set ... But a symlink is an easy way to build an icon. > > Can you please prepare a full listing (including existing ones) accourding > to our comments. If you don't agree with me, you may try to argue or push > your suggestions anyway if you are sure they are needed. More existing > icons may be removed if are not useful enough. > > After we have a full listing (say 85 icons), we may start to search for > missing icons in all icon sets. And probably we will have some changes > in the list, because it is not useful to have all symlinks. > OK, Olivier |
|
From: Olivier C. <oli...@fr...> - 2001-01-22 10:51:41
|
"Riswick, J.G.A.v." wrote:
>
> Hi!
>
Hello, happy to "see" you again!
> I'd like to make another addition to the cde theme,
> which calculates the hilight and shadow colors as they
> are calculated in Motif. I have the color calculations,
> but now I need to integrate the colors in the theme.
> How do you think could this
> best be done? Should I add extra colors to the .dp files,
> or run al pl script each time another colorset is chosen?
>
I think that we have to add extra colors to the .db file.
I will do as follows:
1 - add motifHilightColor and motifShadowColor in the
fvwm-themes-images.in colors library
2 - add a new sub option to --colorscheme, say
--colorscheme-hish x,y,methode
which take the x first colors of a .db file and then replace/create
the colors y to y + x by the hi colors computed from the colors 1 to x
useing the method "method" and do the same thing with sh and colors
1 to x and y+x+1 to y+2x
3 - then, modifying themes/cde/colors/main
Can you send a patch for 1 and possibly to 2 and 3 but I can do 2
(when I will have the time) and 3 is easy.
Do you want write access to fvwm-themes?
> Also I have a question concerning the background. In cde,
> background is a gradient ranging from the shadow color
> to the hilight color belonging to the colorset of the
> current workspace. So I tried something like this:
>
> + I Exec exec fvwm-themes-images --sky --sky-colors
> $[shadow.cs2],$[hilight.cs2] --setroot
>
> however, that doesn't work..
This is a fvwm-themes-images bug (in parsing the options), will be fixed
in 0.4.2
Thanks, Olivier
|
|
From: Mikhael G. <mi...@ho...> - 2001-01-22 01:10:25
|
On 18 Jan 2001 23:54:11 +0100, Olivier Chapuis wrote: > > Now I think that we need to add a *lot* of names. I think you don't know yet what is it to manage 960 icons to suggest a lot of new names! :) Even with only one icon set it may be a problem. And 16? But I want to make wm-icons more complete, so let see. > First, if I look at the fvwm-themes root menus we needs: > > 50 programs (can be a symlink to utility) Are you sure we need both? I am not. > 60 system (can be a symlink to monitor) I myself tried to use the following criteria, can system be used only in menu/ or also in mini/, norm/, bar/? Another criteria was how many icon sets have this icon not symlinked. > 90 configuration (in your list) > 90 modules (in your lists) > 50 themes No comments. These are concepts which are hard to show. > Now I go further in the menus. First if I look to our "root" programs > menus (and one I've planed in a previous messages) as well as to the > kde "root" programs menus we need: > > 50 applications (can be a symlink to utility) Now it is programs + applications + utilities? :) > 50 office (can be a symlink to desktop but seems <> for me) Instead of word-processor? > 50 text (can be a symlink to informations or viewer) I am not sure does this mean text file or text utility (sed) or what. But is not terminal + editor + viewer + information + file enough? > 50 science (can be symlink to calculator) I though about mathematics in icons.lst, but science is probably better. > 50 multimedia (can be a symlink to sound but <>) Ok. A symlink may vary in every icon set. Probably music is better. > An interesting system is the debian menu package (used by Mandrake). > Here there are lot of sub categories but the only top category > without an obvious wm-icons (office is their to) is > > 40 session (can be a symlink to desktop or wm-restart) Not very useful to have IMHO. > 50 office (again) > 50 multimedia > > Now if I go to the debian sub categories we "need": > > Under config: > ?? hardware > ?? packaging I really don't know on these two. There are a lot of computer words. :) > 70 printer (no obvious symlink) symlink to hardware? :) or utility (printing software) > ?? boot No, restart or quit. > Under applications: > ?? development Instead of debugger? > 50 science (again) > ?? emulators 50, but how can you draw such icon? > ?? archiving (can be a symlink to file) No. > 80 monitoring (can be a symlink to monitor and a better > name is system-stat) I can't choose between monitoring, system-stats and system-report. > ?? publishing office? > 50 text (again) -20 > Under Networks: > 50 download (can be symlink to file) > 60 news (can be a symlink to chat) > 60 connection (I.e., remote access, isp, ..., need a better name, > easy symlink) I would prefer not to add these 3, since there are similar icons. > Under Games: > 40 sports game-action? > 60 some in your list (in fact I take in account your list) > ?? games-puzzles (can be a symlink games-logic) > ?? games-aventure (can be a symlink games-action or strategy) We can't add all. arcade, adult, adventure, interactive fiction (huh?), educational, puzzle, rpg, simulation, sport, and worst of all games which are in several categories. I would start with action, board, cards, logic, strategy and see if there are many games which can't be icon-ed. > Under Multimedia: > 80 video ok, but -20 :) > There are also sub sub categories under applications. These suggest to > me: > > 50 hex > 50 science-graph (can be a symlink to science) > 50 science-astronomy (ditto) > 50 science-nature (ditto) > ?? compression > ?? backup I see nothing useful, i.e. urgent. > So that's it for "programs" icons. I think that it will be go that > wm-icons have a support for the (powerful and very good) debian > system menu). What system is used with RedHat and Suse? I think > that more or less supporting Debian/RedHat et al./Suse will > be good. RedHat used/uses wmconfig that builds menus for fvwm95, fvwm2, afterstep, mwm, anotherlevel, icewm, blackbox, wmaker, kde. I didn't really use it. > Let us continue the fvwm-themes menu: > > 50 theme (different from themes) folder? > ?? component file? > 30 cursor > ?? animation (symlink to window-iconify) > ?? may be one or two configuration-* > 90 x > ?? background (symlink to colors) > 60 icons o:) > > ?? help-man (symlink to help) > > ?? pager > ?? panel/buttons > ?? winlist > ?? applet > > ?? wm (can be a symlink to windows) I fear we will loose icon themability this way. I would not add anything from these. x would be ok, but it is not really less general than existing unknown. > Others: > > 50 penguin Ok, I forgot this one, which de facto is here. > 50 start -20 > 60 ball (component can be a symlink to this) item? > ?? os (can be a symlink to penguin :o) > ?? cde (better into apps icons set) > ?? distributions -50 all, assuming they were greater than 50. > Renaming > > ?? wm-lock, wm-restart, wm-quit, wm-refresh to lock, restart, > quit, refresh (more generic) Ok. > That's all :o). Of course the 50% have not the same meanings that > for your reasonable list. 50% is bad. We should have a full agreement on icon name meanings. I tried to describe my meanings in doc/icons.lst > Moreover, I am new with wm-icons. But, > I will say that for me the icons with priority > 50 should be added. > Also, those with a priority of 50 with an obvious symlink can also > be added. For the ?? one, its depends of the future of the discussions Can you please prepare a full listing (including existing ones) accourding to our comments. If you don't agree with me, you may try to argue or push your suggestions anyway if you are sure they are needed. More existing icons may be removed if are not useful enough. After we have a full listing (say 85 icons), we may start to search for missing icons in all icon sets. And probably we will have some changes in the list, because it is not useful to have all symlinks. P.S. I am happy you interested in this. I am alone may be too subjective. Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-01-21 22:50:40
|
Here is a small introduction to the existing icon sets of wm-icons. There is more info in the doc/ directory. I have originals used for all icon sets (thousands of icons), which I may put on sourceforge.net. Feel free to comment on these icon sets, which to leave, which to remove. 01x01-template A working template for creating new icon sets. 16x16-general Basically from fvwm-icons, uses small number of colors. Included in fvwm-themes. 14x14-general I manually created this from 16x16-general. I am not sure whether this set is needed. It's good for mini icons and small TitleStyle Height. 48x48-general Mix from different icon packs. Bad that number of colors used in this set is big. At least one user asked for 8bpp support. This icon set should be improved by replacing many icons. Included in fvwm-themes. 56x46-3dpixmaps 17x14-3dpixmaps 21x18-3dpixmaps These 3 icon sets were inspired by 3dpixmaps distribution, there were rpm for SuSE. The author changed to GPL after we (Julian) asked him: http://stargate.solsys.org/cgi-bin/showlsm.cgi?/home/httpd/sol/linux/projects/3d_pixmaps.lsm I think that background used is ok, but not the best one. Two last icon sets are created automatically by convert - very bad quality. I would drop all 3 icon sets and add a plain icon set 32x32, without background. As I said in other email background patern may be added by scripts. 56x56-martys 56x56-martys2 Martys gave wm-icons permission to distribute these icons. I actually use 56x56-martys just now. :) I rarely switch to 56x56-martys2. 20x20-martys 20x20-martys2 Unfortunately, these are great icons, but there are not enough of them to complete an icon set. I am not sure whether to keep them. 44x52-penguins Very nice and complete (well almost) icon set. Everyone will like it. 16x16-kde 32x32-kde From KDE1 (some are from 16x16-general). They use only 40 colors! 32x32-kde2 48x48-kde2 Very nice if you have more than 8bpp. Totally 15+1 icon sets for now. When wm-icons was started there were no enough gnome icons to compose an icon set, now it is probably enough. Regards, Mikhael. |
|
From: Riswick, J.G.A.v. <J.G...@tu...> - 2001-01-20 22:53:45
|
Hi! I'd like to make another addition to the cde theme, which calculates the hilight and shadow colors as they are calculated in Motif. I have the color calculations, but now I need to integrate the colors in the theme. How do you think could this best be done? Should I add extra colors to the .dp files, or run al pl script each time another colorset is chosen? Also I have a question concerning the background. In cde, background is a gradient ranging from the shadow color to the hilight color belonging to the colorset of the current workspace. So I tried something like this: + I Exec exec fvwm-themes-images --sky --sky-colors $[shadow.cs2],$[hilight.cs2] --setroot however, that doesn't work.. best regards, jos |
6 messages has been excluded from this view by a project administrator.
