Je 1999/07/02(5)/19:07, Steve Greenland montris sian geniecon skribante:
> [talking about Apps/Editors/Emacsen/..., and continuing about
> the collapsing trees:]
>
> Now consider the GIMP: its menu entry might be
> "Apps/Graphics/Editors/bitmaps". But even if the only installed package
> with a men
On 30-Jun-99, 05:05 (CDT), joost witteveen <[EMAIL PROTECTED]> wrote:
> The real difference is that when a program P happens to be in
> a/b/c/d/P, then with the hints, that location may be relocated
> to a/b/d/c/P (with c and d exchanged). Many probably again really
> dislike that, but think about
Let me reply once more to this email, as either I don't
understand what is meant with `collapsing trees', or a lot
of other people don't.
Fearing about stuff originally placed in Apps/Vieuwers and Apps/Sound
suddenly being placed in Apps/MultiMedia, Steve wrote:
> I still don't think that I like
Je 1999/06/27(0)/15:06, Steve Greenland montris sian geniecon skribante:
> Consider that things like xdvi and tkman should be under "Apps/Viewers".
> It would never occur to me that they could be under "Apps/Multimedia";
> If I found them there, I would submit a bug to the package maintainers
> (w
On 19-Jun-99, 16:16 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote:
> Well the alternative that has been brought up before is to make everything
> use a deeper tree (like Apps/Editors/Big/Emacsen), and have menu
> automatically collapse the tree to Apps/Editors on your system with 2 editors
> and kee
Je 1999/06/21(1)/12:06, Chris Waters montris sian geniecon skribante:
> Joey Hess <[EMAIL PROTECTED]> writes:
>
> > Wow! You've utterly bypassed the whole policy issue with a brilliant idea!
>
> Well, no (though that was my first reaction too). We still should
> have a policy regarding the *defa
Joey Hess <[EMAIL PROTECTED]> writes:
> Wow! You've utterly bypassed the whole policy issue with a brilliant idea!
Well, no (though that was my first reaction too). We still should
have a policy regarding the *default* menu layout, and it still makes
sense to have it separate from the menu packa
Je 1999/06/20(0)/13:06, Edward Betts montris sian geniecon skribante:
> On debian-policy, joost witteveen <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I've just released menu-2.0. It has many new features, one of
> > wich is the automatic optimization of the menu tree, using
> > something I'v
Je 1999/06/19(6)/23:06, Richard Braakman montris sian geniecon skribante:
> joost witteveen wrote:
> > forcetree
> > Apps/Sound
> > endforcetree
>
> Is it also possible to specify that a menu (such as Apps) must have only
> submenus? Mixed menus seem cluttered and I find them hard to use.
At t
Je 1999/06/20(0)/12:06, Joseph Carter montris sian geniecon skribante:
> On Sun, Jun 20, 1999 at 02:50:51PM -0300, Nicolás Lichtmaier wrote:
> > > Would it be possible to group menu items that would be together, just do
> > > not
> > > put them in the menu? So my menu would become:
> > >
> > > Ap
On Sun, Jun 20, 1999 at 02:50:51PM -0300, Nicolás Lichtmaier wrote:
> > Would it be possible to group menu items that would be together, just do not
> > put them in the menu? So my menu would become:
> >
> > Apps>
> > Games >
> > Screen >
> > System >
> > Wi
> Would it be possible to group menu items that would be together, just do not
> put them in the menu? So my menu would become:
>
> Apps>
> Games >
> Screen >
> System >
> Window Managers >
> Command Tool
> Shell Tool
> Xterm
But you would loose the alpha
Richard Braakman wrote:
> Is it also possible to specify that a menu (such as Apps) must have only
> submenus? Mixed menus seem cluttered and I find them hard to use.
I'd like to see that too.
--
see shy jo
On debian-policy, joost witteveen <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've just released menu-2.0. It has many new features, one of
> wich is the automatic optimization of the menu tree, using
> something I've called "hints". This is what I want to start
> discussion about with this messa
joost witteveen wrote:
> forcetree
> Apps/Sound
> endforcetree
Is it also possible to specify that a menu (such as Apps) must have only
submenus? Mixed menus seem cluttered and I find them hard to use.
Richard Braakman
Je 1999/06/19(6)/14:06, Joey Hess montris sian geniecon skribante:
[..]
> Well the alternative that has been brought up before is to make everything
> use a deeper tree (like Apps/Editors/Big/Emacsen), and have menu
> automatically collapse the tree to Apps/Editors on your system with 2 editors
Joey Hess wrote:
> Well the alternative that has been brought up before is to make everything
> use a deeper tree (like Apps/Editors/Big/Emacsen), and have menu
> automatically collapse the tree to Apps/Editors on your system with 2 editors
> and keep the big tree on mine (that has every editor in
Je 1999/06/19(6)/14:06, Chris Waters montris sian geniecon skribante:
> I'm also a little concerned about possible confusion for the
> individual users. As it is now, when I install a new package, and I
> can't find the menu entry in the first place I look, I just go check
> the /usr/lib/menu/pkg
joost witteveen wrote:
> > It sounds like this can generate
> > many possible trees that, while optimal, are very different depending on
> > what's installed. Which means that a user who is familiar with the menus on
> > one system might be completly lost on another.
>
> Well, the trees generated
Joey Hess <[EMAIL PROTECTED]> writes:
> joost witteveen wrote:
> > Although this procedure ignores the real debian tree (so much
> > discussed about), it does eventually come up that look surprisingly
> > like just that tree.
> Can you post an example? The thing I'm concerned about is consistency
Je 1999/06/19(6)/13:06, Joey Hess montris sian geniecon skribante:
> joost witteveen wrote:
> > I've just released menu-2.0. It has many new features, one of
> > wich is the automatic optimization of the menu tree, using
> > something I've called "hints". This is what I want to start
> > discussi
joost witteveen wrote:
> I've just released menu-2.0. It has many new features, one of
> wich is the automatic optimization of the menu tree, using
> something I've called "hints". This is what I want to start
> discussion about with this message.
Wow! You've utterly bypassed the whole policy is
Hi there,
I've just released menu-2.0. It has many new features, one of
wich is the automatic optimization of the menu tree, using
something I've called "hints". This is what I want to start
discussion about with this message.
First, why:
On my system, there are only two
23 matches
Mail list logo