Hi there,
On 28 Apr 2003 at 08:23:32 +0200, Uwe Pross wrote:
I have not made a decision yet. My current concept (in
mind) is partinioning the functions as the are now in
layout_default.inc in files and add some dependencies to
this functions ...
This concept was not that good. I had set
Hi there,
On 26 Apr 2003 at 01:35:17 +, Mikhael Goikhman wrote:
On 25 Apr 2003 20:56:23 -0400, Dan Espen wrote:
I notice that for the screenshots, the ability to move from full
size image to full size image has been removed.
Is there a plan to bring that back?
I may enhance
On Sat, 26 Apr 2003 00:37:55 +
Mikhael Goikhman [EMAIL PROTECTED] wrote:
Why do you set decoration windows to be 800 pixels tall - to always
force a side scrollbar? An empty window taller than the page looks
very bad.
This was a quick 'n dirty hack several weeks ago when the few
Hi there,
On 26 Apr 2003 at 00:37:55 +, Mikhael Goikhman wrote:
This is good. Can I suggest to move all layout classes to the
separate directory? I.e. layout/default.inc instead of
layout_default.inc.
Yes, it is good to have the files more structured.
I think the navigation methods
On 26 Apr 2003 14:43:35 +0200, Uwe Pross wrote:
On 26 Apr 2003 at 00:37:55 +, Mikhael Goikhman wrote:
BTW, I think layout is not the best term for what it does. Maybe
skin, view or look (other names: theme, design,
looknfeel).
Okay, I am not a native english speaker so some terms
Hi there,
I have finished the layout description using php classes. The current
two layouts have been ported to php class descriptions.
Currently the new layout files are not used since I have not tested
them very carefully :-|
The new layouts are accessable via
On 25 Apr 2003 23:11:00 +0200, Uwe Pross wrote:
I have finished the layout description using php classes. The current
two layouts have been ported to php class descriptions.
Currently the new layout files are not used since I have not tested
them very carefully :-|
The new layouts are
I notice that for the screenshots, the ability to move from full size
image to full size image has been removed.
Is there a plan to bring that back?
--
Dan Espen E-mail: [EMAIL PROTECTED]
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe
in message [EMAIL PROTECTED],
wrote Dan Espen thusly...
I notice that for the screenshots, the ability to move from full
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
size image to full size image has been removed.
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
Say what?
Is there a plan to
On 25 Apr 2003 20:56:23 -0400, Dan Espen wrote:
I notice that for the screenshots, the ability to move from full size
image to full size image has been removed.
Is there a plan to bring that back?
I may enhance the script to automatically add Next/Prev links, but I
think Uwe wants to
parv [EMAIL PROTECTED] writes:
in message [EMAIL PROTECTED],
wrote Dan Espen thusly...
I notice that for the screenshots, the ability to move from full
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
size image to full size image has been removed.
^ ^ ^ ^ ^ ^ ^ ^ ^ ^
I was going to send Matt Chapman a message about the WM comparison
chart on his Window Managers for X site and remove the dumb
Developers' note I left on our Links page, but a couple of questions
occurred to me.
1) He has a link to an FVWM2 THEMES page
Hi there,
On 23 Apr 2003 at 22:40:04 -0400, Bob Woodside wrote:
The standard way to prevent this is to specify the exact width
height of each icon image, so the browser knows how much space to layout
for it before loading it. I think most of the current browsers will pick
up the title
Hi there,
On 23 Apr 2003 at 15:10:17 +, Mikhael Goikhman wrote:
In the alternative css the visited links are not different
from the non-visited one, they should be clearly
distinguishable. In the alternative css the active pager
page is not marked.
The existence of an alternate style
On Thu, 24 Apr 2003 07:28:27 -0400
Dan Espen [EMAIL PROTECTED] wrote:
Bob Woodside [EMAIL PROTECTED] writes:
2) My original intent was to tell him that in the comparison
chart he should check FVWM as having pinnable
(or tear-off) menus (which, ahem, would make
FVWM the only WM
Bob Woodside wrote:
The ALT property of mini icons in the pager should be , otherwise
some browsers (at least Opera) use this name initially before the
icons are loaded making the pager too wide initially.
The standard way to prevent this is to specify the exact width
height of each
On 24 Apr 2003 08:35:29 +0200, Grzegorz Nieweglowski wrote:
Bob Woodside wrote:
The ALT property of mini icons in the pager should be , otherwise
some browsers (at least Opera) use this name initially before the
icons are loaded making the pager too wide initially.
The standard
that
never had any connection to the official one? In any case, I think Matt
should be told about the officlal one.
I think I already tried to contact Mutt in the past, but it seems that he
does not update his web pages (at least some of them) in the last 4 years.
bluesmani themes is not connected
On Thu, 24 Apr 2003 08:35:29 +0200
Grzegorz Nieweglowski [EMAIL PROTECTED] wrote:
The W3C standards are:
* alt is used by text-mode browsers to display a description of
what
you would see if your browser could display images
* alt is also displayed by graphical browsers if image
I am starting the new thread, because the thread depth of 25 is getting
ridiculous. Problems:
The ALT property of mini icons in the pager should be , otherwise some
browsers (at least Opera) use this name initially before the icons are
loaded making the pager too wide initially.
Konqueror first
On Wed, 23 Apr 2003 15:10:17 +
Mikhael Goikhman [EMAIL PROTECTED] wrote:
I am starting the new thread, because the thread depth of 25 is
getting ridiculous. Problems:
The ALT property of mini icons in the pager should be , otherwise
some browsers (at least Opera) use this name initially
On Wed, 23 Apr 2003 22:40:04 -0400
Bob Woodside [EMAIL PROTECTED] wrote:
On Wed, 23 Apr 2003 15:10:17 +
Mikhael Goikhman [EMAIL PROTECTED] wrote:
The ALT property of mini icons in the pager should be , otherwise
some browsers (at least Opera) use this name initially before the
icons
Hi Mikhael,
On 15 Apr 2003 at 01:49:54 +, Mikhael Goikhman wrote:
By meta information I mean the multiline header in all php files.
For example the line: //- Last modified : 15.04.2003 08:36:53 uwp
This belongs to the revision control system, it manages it
automatically without a need to
On 15 Apr 2003 08:37:37 +0200, Uwe Pross wrote:
Are you doing the man page conversion for the new web site?
Yes, today or most probably tomorrow.
Regards,
Mikhael.
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in
Hi Mikhael,
On 15 Apr 2003 at 09:10:13 +, Mikhael Goikhman wrote:
Are you doing the man page conversion for the new web site?
Yes, today or most probably tomorrow.
That's good.
To support passing of different layouts between fvwm-sites relative
links should be done like:
a
On 15 Apr 2003 11:31:52 +0200, Uwe Pross wrote:
On 15 Apr 2003 at 09:10:13 +, Mikhael Goikhman wrote:
Are you doing the man page conversion for the new web site?
Yes, today or most probably tomorrow.
That's good.
To support passing of different layouts between fvwm-sites
Hi Mikhael,
On 15 Apr 2003 at 10:24:45 +, Mikhael Goikhman wrote:
I think it will be much more simple for us and more convenient/consistent
for a user if we don't use/pass GET parameters to define all kinds of
layouts, themes, css-s. Yes, I really mean this. Only use session values
that
On 15 Apr 2003 15:46:55 +0200, Uwe Pross wrote:
On 15 Apr 2003 at 12:34:48 +, Mikhael Goikhman wrote:
Suppose someone wants to post (or include in his site) a link to the
FvwmButtons man page. If he copies it and it has ?layout=something, all
users are forced to read it using this
MG == Mikhael Goikhman [EMAIL PROTECTED] writes:
MG It returns the result of whatever is configured in ErrorDocument
MG 404. It may be configured to use a redirection or a local
MG substitution (this differs in which url of the missing page a user
MG gets). I prefer a substitution, i.e.
On 10 Apr 2003 08:43:09 +0200, Uwe Pross wrote:
On 09 Apr 2003 at 21:09:23 +, Mikhael Goikhman wrote:
No, I didn't mean files that are fully generated, only
files that are mostly written by hand but contain lines
(meta information) that should be updated on every file
change.
should be outside of the
file contents, but of course there may be exceptions, for
example some web pages may contain text This page was
last updated on XXX as part of the content.
In the actual version the last update time is placed on the
bottom of the page. This time is obtained from
Hi Mikhael,
On 09 Apr 2003 at 02:55:10 +, Mikhael Goikhman wrote:
Autogenerated lines in cvs files is not a good idea.
What do you mean by auto? In the new version there is not
and it was not planed to autogenerate anything.
In the new version some file for example author information
or
information) that should
be updated on every file change.
Ideally, all meta information should be outside of the file contents,
but of course there may be exceptions, for example some web pages may
contain text This page was last updated on XXX as part of the content.
But this text at least serves some
MG == Mikhael Goikhman [EMAIL PROTECTED] writes:
MG The problem with this is that you should first commit and only
MG after some time (it is updated once in several hours) check out
MG fvwm.org or fvwm.sf.net, because links like file://... or
MG http://localhost/; can't be checked.
The fvwm.org
Several notes about web pages.
Autogenerated lines in cvs files is not a good idea.
For example autogenerated Last-Modified-Date or Author or History only
lead to unnecessary cvs conflicts (if 2 people work on different parts of
the same file). This belongs to ChangeLog and/or cvs web interface
35 matches
Mail list logo
