More improvements

[GoogleCodeExporter]

'Preferences' window, page 'General', 'Default syntax highlight:' drop-down
menu item names:

asp --> ASP
c --> C/C++
css --> CSS
html --> HTML
java --> Java
js --> JavaScript
lua --> Lua
perl --> Perl
php --> PHP
python --> Python
rst --> reStructuredText
ruby --> Ruby
slice --> Slice
text --> Plain Text
xml --> XML

=================================

main menu 'File', menu item 'New...', submenu item names:

- 'Cascaded Style Sheets' --> 'CSS'

Other text editors don't use the full name for this type. They have 'CSS',
which is well known and most used. Please fix this. It will save on space, too.

- 'Active Server Pages' --> 'ASP'

Please don't forget to fix the wildcards of the 'Open' dialog as well:

- 'Cascaded Style Sheet (*.css)' --> 'CSS (*.css)'
- 'Active Server Pages (*.asp)' --> 'ASP (*.asp)'

Thank you.

Original issue reported on code.google.com by wxPytho...@gmail.com on 7 Jun 2008 at 2:10

[GoogleCodeExporter]

These are all good suggestions.

Dick

Original comment by rdmoo...@gmail.com on 7 Jun 2008 at 2:17

[GoogleCodeExporter]

If want to know if I also need to change pop up menu of new tool button also 
likes above?

Original comment by limo...@gmail.com on 7 Jun 2008 at 2:24

[GoogleCodeExporter]

Yes, please do that as well.

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 2:26

[GoogleCodeExporter]

Where is the "new tool button"?

dick

Original comment by rdmoo...@gmail.com on 7 Jun 2008 at 2:34

[GoogleCodeExporter]

The first tool button of toolbar, and when you click the down-triangle button, 
you'll
see the pop up menu.

Original comment by limo...@gmail.com on 7 Jun 2008 at 2:36

[GoogleCodeExporter]

Dick, this button is located in the toolbar which rolls down the same pop-up 
menu as
the 'New...' menu item of the main menu 'File' does. This pop-up menu of the 
toolbar
button should be fixed exactly as the 'New...' pop-up menu is.

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 2:38

[GoogleCodeExporter]

Limodou, is it fixed? After fixing this, there are no other bugs that I can 
find. I
think it is safe to publish the new version after fixing this.

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 2:40

[GoogleCodeExporter]

Got it. Thanks.

Original comment by rdmoo...@gmail.com on 7 Jun 2008 at 2:42

[GoogleCodeExporter]

No, wait, there is one little typo in the 'About' dialog:

1) UliPad Version 4.0 --> UliPad version 4.0

2) If you have any question please contact me ! --> If you have any questions,
contact me.

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 2:53

[GoogleCodeExporter]

Before publishing a new version, how about improving the vertical alignment of 
key 
bindings on menus? See the attached image for an example.

Original comment by rdmoo...@gmail.com on 7 Jun 2008 at 2:59

Attachments:

• Ulipad_Search_Menu.png

[GoogleCodeExporter]

Yes, I have once proposed this. I also find it ackward myself.

Limodou, please fix the things proposed in this issue and also fix the 'About' 
dialog
and make the menu shortcuts aligned as Dick proposed. Then we can publish the 
next
version. What do you think?

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 3:05

[GoogleCodeExporter]

Fox menu align I have a big problem. First, in my version it's good. And when I
create menu item caption, for example, the normal menu caption should be: 
Open\tF2,
and I convert \t with spaces, in order to make the width of menu items should 
be the
same, I format all menu items to the same width filling with spaces. Why I need 
do
so, just because some local accelerator process. For example, in context menu of
Directory Browser Window, I want to use F5 to refresh the window. But I also 
define
it in Python menu. So I should define F5 not an accelerator. But I still want 
to show
the F5 in the main menu. But if I put menu caption like Run\tF5, and remove F5 
from
accelerator of mainframe, the accederator of menu item dispear also. So I don't 
know
if there is a way that can show accelerator in menu but it's disabled indeed. 

Original comment by limo...@gmail.com on 7 Jun 2008 at 3:14

[GoogleCodeExporter]

If it is possible, make every key binding be ended at the edge in all main 
menus. You
can do  Run\t\tF5 or Run\t\t\tF5. Make as many tabs as you need for the menu 
items
with short names so that they'll end at the edge of the menu.

Do this... Look which menu item name in a main menu is the longest and have 
that menu
item and the key binding _one_ tab space between them. Then give other menu 
items as
many tabs as they need in order to end at the edge of the menu. Do that for 
every
main menu. I hope that'll do the job. Thanks.

Original comment by wxPytho...@gmail.com on 7 Jun 2008 at 3:40

[GoogleCodeExporter]

I tried to use Run\t\tF5, but it does not work at all.

Original comment by limo...@gmail.com on 8 Jun 2008 at 3:26

[GoogleCodeExporter]

Limodou, have you tried this yet?

(1) Run(\t*2)F5

or maybe

(2) Run((\t)*2)F5

I think the first is similar to
- Run\ttF5
and the second to
- Run\t\tF5

Maybe try even
Run(\tt)F5

I don't know if any of these will work. Just a thing for you to test. So does 
it work?

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 11:47

[GoogleCodeExporter]

Or just without the parenthesis:

Run\ttF5

Does any of this work at all?

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 11:48

[GoogleCodeExporter]

As Google results explained, the best bet would be this:

Run\t*2F5

And if that would not work or if it would produce an error, then this should 
work:

Run(\t*2)F5
Run(\t*3)F5
and so on...

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 11:58

[GoogleCodeExporter]

How to write like above?

'Run' + '\t'*2 + 'F5'?

Original comment by limodou....@gmail.com on 8 Jun 2008 at 12:01

[GoogleCodeExporter]

Please try every possibility.

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 12:05

[GoogleCodeExporter]

Yes, try your version, too. I hope one of them would work.

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 12:05

[GoogleCodeExporter]

Does it work?

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 12:09

[GoogleCodeExporter]

I've tried \t\t but failed. And tried \t\t\t buf failed.

Original comment by limodou....@gmail.com on 8 Jun 2008 at 12:31

[GoogleCodeExporter]

Please try
Run\t*2F5

and also try
Run(\t*2)F5

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 12:48

[GoogleCodeExporter]

Please try it in python command line, for 'Run\t*2F5' and 'Run(\t*2)F5' what 
you want
to get?

Original comment by limodou....@gmail.com on 8 Jun 2008 at 12:59

[GoogleCodeExporter]

This works:

print 'Run\tF5'

print 'Run\t\tF5'

print 'Run\t\t\tF5'

and so on...

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 1:12

[GoogleCodeExporter]

All format display right. Only the first can be used. But the first format, 
just as I
said before, it'll override the local shortcuts, because it'll be global scope. 
You
can try yourself:

modules/makemenu.py: 201

caption = label + '\t' + accel[idname][0]

For last two formats, it'll not work at all.

Original comment by limodou....@gmail.com on 8 Jun 2008 at 1:17

[GoogleCodeExporter]

What about this?

modules/makemenu.py: 201

caption = label + '\t' + '\t' + accel[idname][0]

Does this work?

Original comment by wxPytho...@gmail.com on 8 Jun 2008 at 3:14

[GoogleCodeExporter]

No, you can try it yourself

Original comment by limodou....@gmail.com on 9 Jun 2008 at 12:53

[GoogleCodeExporter]

Original comment by limo...@gmail.com on 24 Oct 2008 at 4:31

• Changed state: Fixed