[FIXED] The menu to disambiguate bundle items should now work correctly with multi monitor setups.
Works fine here.
[NEW] Tab triggers are now rendered right-aligned in the menus and with some visual ornaments that are supposed to make them distinctive. It is no longer necessary to put the tab trigger in the items title, to get it rendered -- in fact this is now deprecated. I am aware that the items with tab triggers are shown in the normal menu font size when using the gear menu from the status bar.
Love it! Any chance the tree view in the bundle editor could similarly show shortcuts and tab triggers?
Gerd
[NEW] Tab triggers are now rendered right-aligned in the menus and with some visual ornaments that are supposed to make them distinctive. It is no longer necessary to put the tab trigger in the items title, to get it rendered -- in fact this is now deprecated. I am aware that the items with tab triggers are shown in the normal menu font size when using the gear menu from the status bar.
Love it! Any chance the tree view in the bundle editor could similarly show shortcuts and tab triggers?
Agreed! Absolutely lovely. The new way bundles are treated now is just superb.
Andreas
Love it! Any chance the tree view in the bundle editor could similarly show shortcuts and tab triggers?
And for that matter reuse the new dir/sub-dir format. Some of the bundles (Rails/Ruby/etc) are getting mighty hard to navigate in there.
Couple notes also:
When a bundle is selected above the tables you see "No Item Selected", "Edit Menu Structure: Ruby on Rails" might be better.
Your allowed to edit the names of items in the menu structure editor, but not of the excluded items, annoying.
On 7/6/2006, at 0:59, Gerd Knops wrote:
[ tab triggers ] Love it! Any chance the tree view in the bundle editor could similarly show shortcuts and tab triggers?
Thanks! I do plan to put them in the menu structure outline.
I am a little undecided on the faith of the bundle editor -- initially I wanted to scrap it in favor of using the 2.0 file manager, but I also do see some value in a dedicated editor. If I do continue with the bundle editor, I am likely going to change the current bundle outline to just a bundle source list, and let the menu structure outline be the view of the bundle contents (as the old outline doesn’t work for large bundles, and having two lists of bundle contents is redundant) -- though there then needs to be a place for items not in the menus (likely just a list below the excluded items.)
(if I do continue with the bundle editor, there likely will be (the oft requested) searching (both on title and key equiv.), back/forward buttons, and the filtering will be more like seen in iTunes (the All Artist Album … emblems going across the top of the window))
On Jun 7, 2006, at 4:04 AM, Allan Odgaard wrote:
On 7/6/2006, at 0:59, Gerd Knops wrote:
[ tab triggers ] Love it! Any chance the tree view in the bundle editor could similarly show shortcuts and tab triggers?
Thanks! I do plan to put them in the menu structure outline.
I am a little undecided on the faith of the bundle editor -- initially I wanted to scrap it in favor of using the 2.0 file manager, but I also do see some value in a dedicated editor.
Hmm... it does seem odd that to edit snippets, commands or syntaxes inside one of the premier text editors one has to rely on the limited features of a text field. It would be great to have TextMate's abilities available when editing (syntax highlight, easy version control, snippets etc). But I can see how the BundleEditor's requirements would make it difficult to convert it into a special built in project of sorts.
Gerd
Try "Edit in Textmate" when editing a bundle item. There is even a language grammar for it!
Dan
On Jun 7, 2006, at 2:41 PM, Daniel Käsmayr wrote:
Try "Edit in Textmate" when editing a bundle item. There is even a language grammar for it!
That helps somewhat, but version control is still a pain. Or sometimes an easy diff to a previous version of a syntax could really help to find the errors of one''s ways...