So the way that the menus are currently built is pretty whacky. I want to rewrite the menu handling part of u_main.tk to change a few things. I want to know if this is going to conflict with anything that anyone else is working on.
First, each platform's menus would be clearly laid out in one place. This would make it very easy to tailor the menu structure to guidelines for each OS.
The menus would be built only at launch, except where then need to be built dynamically (i.e. the Windows menu, which is broken on Mac OS X anyway). For example, the Help menu is rebuilt after each use. AFAIK, this is unneeded and makes the menus respond sluggishly.
On a related topic, I just created a patch against 0.38-3/0.38-4 that fixes the "Browser..." and nested menu troubles on Mac OS X. Its in CVS: packages/darwin_app/patches/extended_help_menu.patch
I will start working on 0.38-4, then port the changes to 0.39.
.hc
________________________________________________________________________ ____
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
Hey,
Working on the searching patch meta data stuff as well?
thoughts about organization of abstractions?
Mathieu is convinced that the best method is to generate the external tree based on the meta keywords themselves.
b.
Hans-Christoph Steiner wrote:
So the way that the menus are currently built is pretty whacky. I want to rewrite the menu handling part of u_main.tk to change a few things. I want to know if this is going to conflict with anything that anyone else is working on.
First, each platform's menus would be clearly laid out in one place. This would make it very easy to tailor the menu structure to guidelines for each OS.
The menus would be built only at launch, except where then need to be built dynamically (i.e. the Windows menu, which is broken on Mac OS X anyway). For example, the Help menu is rebuilt after each use. AFAIK, this is unneeded and makes the menus respond sluggishly.
On a related topic, I just created a patch against 0.38-3/0.38-4 that fixes the "Browser..." and nested menu troubles on Mac OS X. Its in CVS: packages/darwin_app/patches/extended_help_menu.patch
I will start working on 0.38-4, then port the changes to 0.39.
.hc
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
What I was proposing here is a reorg of how all of the menus are built in pd.tk/u_main.tk. Right now, they are kind of scattered and have been built up over time, so they are stretched into an old framework. If the entire menu structure is laid out in one place, with one section per platform, its much easier to tailor the menus to each platforms guidelines, making Pd act like a native app. For example:
if { $tcl_platform(platform) == "windows" } { menu .mbar.edit.preferences menu .mbar.help.aboutpd } elseif { $tcl_platform(os) == "Darwin" } { menu .mbar.apple.aboutpd menu .mbar.apple.preferences } else { menu .mbar.edit.preferences menu .mbar.help.aboutpd }
I still think that meta stuff is still a great idea. The recursive function that I wrote to build the Help menu could easily be extended to look for that meta info, so in that sense, there is some progress along those lines. I think the first thing that needs to happen with the meta project is to define what meta data we are tracking in the help files.
I think its time for a wiki on this, then we can add the info from previous discussions and move forward. I am currently immersed in the build system stuff, so I'd appreciate it if someone else took the lead on that. It sounds like you two (Ben and Matju) are on it.
.hc
On Nov 15, 2005, at 11:18 AM, B. Bogart wrote:
Hey,
Working on the searching patch meta data stuff as well?
thoughts about organization of abstractions?
Mathieu is convinced that the best method is to generate the external tree based on the meta keywords themselves.
b.
Hans-Christoph Steiner wrote:
So the way that the menus are currently built is pretty whacky. I want to rewrite the menu handling part of u_main.tk to change a few things. I want to know if this is going to conflict with anything that anyone else is working on.
First, each platform's menus would be clearly laid out in one place. This would make it very easy to tailor the menu structure to guidelines for each OS.
The menus would be built only at launch, except where then need to be built dynamically (i.e. the Windows menu, which is broken on Mac OS X anyway). For example, the Help menu is rebuilt after each use. AFAIK, this is unneeded and makes the menus respond sluggishly.
On a related topic, I just created a patch against 0.38-3/0.38-4 that fixes the "Browser..." and nested menu troubles on Mac OS X. Its in CVS: packages/darwin_app/patches/extended_help_menu.patch
I will start working on 0.38-4, then port the changes to 0.39.
.hc
__ ____
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
¡El pueblo unido jamás será vencido!
-
B. Bogart -
Hans-Christoph Steiner