Re: [cssed-devel] cssed: Added subitems to help menu

[Iago R. <iag...@hi...>]

On Sat, 2004-09-18 at 20:05, Mich=C3=A8le Garoche wrote:
> Le 17 sept. 2004, =C3=A0 12:29, Mich=C3=A8le Garoche a =C3=A9crit :
> > Le 17 sept. 2004, =C3=A0 10:31, Iago Rubio a =C3=A9crit :
> >> On Thu, 2004-09-16 at 23:50, Mich=C3=A8le Garoche wrote:
> >>> I've added two items in the Help menu: web site and online doc.
> >> The problem is to know the default browser in all platforms, that's=20
> >> why
> >> I did not use external viewers yet, I was waiting to add an entry in=20
> >> the
> >> config dialog to let the user to choose his/her preferred browser.
> > Yes, of course, it's better.
> Thinking about that, it's not a good option, because the user may wish=20
> to view either the preview (future addition), or the web site, or the=20
> docs in another browser than the default. He should have the choice at=20
> any time, as cssed is aimed at web site designers, who may want to test=20
> if the style sheets work correctly in any available browser.

Yes, you're right. I will do one entry for the default browser, other
for the help browser, and one "external commads" window to let users to
use whatever command they want.

> >>> If it's ok, just tell me, I'll commit the changes.
> >> If you could add it between ifdefs it would be great.
> > OK, I'll do that.
> I've added ifdefs, so normally it is compiled without help additions.=20
> To compile with it, just add --with-help-menus to configure and=20
> -DWITH_HELP_MENUS to preprocessor compile flags.

Ok.

> By the way I've discovered that the #ifdef DARWIN is not taken into=20
> account, if it is compiled with -DDARWIN. So that I need to know where=20
> you use that, in all packages. It could have been dramatical with ipc=20
> queues.

It should work with -DDARWIN in the gcc command line.

ITOH, #ifdef DARWIN is not used in cssed's code, only in the plugins
code. As example in find in files plugin, #if defined(DARWIN).

Just adding -DDARWIN to CFLAGS if $OSTYPE =3D "DARWIN".

> >> This way I can test it, and disable it if I find problems anywhere :)
> > Basically it is the same command as for plugindoc. So based on what=20
> > you said apropos plugindoc, I'll add  a static field to give the=20
> > strings for most popular browsers, then an entry to change it.
> I did not adventure in this, since it's too difficult for me at the=20
> time being, but there are mozilla, dillo, galeon, gnome as proposed=20
> browser.
>=20
> I'd really like to have it in the release.

Well, I prefer to do it in next release.=20

What I'm sure is I will not wait three months again for a new release :)
--=20
Iago Rubio  =20
- Home page    * http://www.iagorubio.com=20
- Last project * http://cssed.sourceforge.net        =20
- GPG Keyserv  * pgp.rediris.es id=3D0x909BD4DD