SynWrite (Syn2)

Alextp · Post by *Alextp » 2010-07-01, 15:16 UTC

'background-attachment' css entering crash- Fix
upload later.

Matthias030 · Post by *Matthias030 » 2010-07-01, 16:00 UTC

Good job again.

CSS crash: fixed
closing tags not possible: fixed
select autocomplete by mouse click: FIXED!

Matthias030 · Post by *Matthias030 » 2010-07-01, 16:40 UTC

3 ideas for tuning autocomplete a bit more:

1) HTML: Press "<" and choose tag <body>. Syn2 writes "<body ". That's correct. But if you open autocomplete by CTRL+SPACE and select tag <body> it is only written "body " without "<"

2) PHP: For every entry in autocomplete list there is a small description shown. By scrolling by mouse through the list, the description is changing. But if you scroll with Keyboard through list the description is not changed to current selected entry.

3) Example: Use autocomplete for "<table" then "bgcolor='". Finally you can select only "color #000000". On the screen is now "<table bgcolor='#000000" but autocomplete window is still open. It should be closed.
For the similar example "<table align='left" autocomplete is closed correctly after "left"

Alextp · Post by *Alextp » 2010-07-02, 12:28 UTC

well it is hard ti fix these autocomp. issues..
Anyway pls send me a .php file (for 2)

Alextp · Post by *Alextp » 2010-07-02, 12:33 UTC

On the screen is now "<table bgcolor='#000000" but autocomplete window is still open. It should be closed

i can partially fix, by closing autocompl. window on typing '.
So you put closing ' and window is closed.

Matthias030 · Post by *Matthias030 » 2010-07-02, 13:52 UTC

I have sent you mail.

i can partially fix, by closing autocompl. window on typing '.
So you put closing ' and window is closed.

I have thinked it over and the best solution is not to change it. It is only a minor bug and it only affects some autocomplete entries. It must not be fixed. I can help me this way:

On the screen is "<table bgcolor='". Now I select color #00000 by typing ' and not use "ENTER". On the screen is now <table bgcolor='#000000'
By typing ' I can select an autocomplete value and the closing ' is written behind automatically. For these values it is better to use it with ' and not by "ENTER"

I hope that my description is easy to understand

Alextp · Post by *Alextp » 2010-07-02, 14:00 UTC

fixed Php issue with keybd / hint.

For these values it is better to use it with ' and not by "ENTER"

I think fix for ' typing is useful- left it.
(Enter 's easier to press than ' )

Alextp · Post by *Alextp » 2010-07-03, 04:48 UTC

b300 release.

Matthias030 · Post by *Matthias030 » 2010-07-03, 06:51 UTC

fixed Php issue with keybd / hint.

It's fixed. But after using mouse to scroll through list the keys UP/DOWN are no longer working in list.

Alextp · Post by *Alextp » 2010-07-03, 06:59 UTC

they're working- just put mouse out of autocomp. window.
)

Matthias030 · Post by *Matthias030 » 2010-07-03, 07:39 UTC

Oh yes, you're right. They're working

Matthias030 · Post by *Matthias030 » 2010-07-03, 08:46 UTC

found another syn2 crash: in php autocomplete choose any function name (eg. array_map). Now press STRG+SPACE again and choose any other autocomplete value. Syn2 crashes now.
It seems it has to do with these function hints that apears on the screen. Every time such an function hint is shown, no further autocomplete value can be choosen.

This crash is only for your record. It has no high priority for me.

Matthias030 · Post by *Matthias030 » 2010-07-03, 12:17 UTC

I've thought about optimizing/fixing html autocomplete. Currently html autocomplete only works for start tags like <body>, but not for end tags like </body>. Autocomplete could be changed this way:

for start tags: "<" and CTRL+SPACE opens autocomplete window. select "body" writes to screen: "<body ". Now autocomplete window remains open so that you can use following sub values to complete your input: <body alink='#000000 (currently "<" works exactly this way. CTRL+SPACE is buggy. It doesn't work properly and gives false tags.)
for end tags: "</" opens autocomplete window. select "body" writes to screen: "</body>". Additional sub values (alink=...) could be supressed. They are not needed for end tags as far as I know.

I now it is hard work. But this would significant raise usability of autocomplete for those who use it regularly. For me it would be a completion of that feature, but I don't use it regularly.

Alextp · Post by *Alextp » 2010-07-05, 09:14 UTC

i 've almost done it. I have popup with </tags> for </ beginning. one prob is that I insert double >> when closing that popup.

Matthias030 · Post by *Matthias030 » 2010-07-05, 16:14 UTC

1. Option "New File" is really good. A way better would be return of MDI. But it's alot of work, I think.

2. "Selection Commands": I like old menu more than new one. The old one was better with this small triangle to open submenu. I would leave "sort ascent" and "sort descent" directly in menubar, not into submenu.
3. pale icon "not RO": this is a good solution. so everyone knows where to click to enable RO. Is a new 16x16 icon too big? Do you need a smaller size?
4. autocomplete for </tags>: works really good. maybe you can add the missing ">" to the tag. But you have done a lot of work for autocomplete feature. It has already greatly improved in the last betas.
5. new toolbar themes: I like them. For me "aluminium" is better than "stripes", but both are nice. Now everyone can find his own style for his personal taste.