complete autocomplete (like TopStyle)

[mainderay]

I really like what you're doing with WeBuilder. What would help myself and hopefully others is a more complete autocomplete functionality for CSS. In TopStyle it not only autocompletes on properties (like WeBuilder) but also on values (which is very helpful).

The other input is on the search box. The default options don't work well for me and I'd like to them to be persistent when I close the search and open it again. Failing that, the ability to configure the search defaults would probably work as well.

Thanks for listening and let me know if you have any questions!

kind regards,

-raymond

[Gatis]

I am not quite sure why do you think that auto-complete is not available for CSS values.

a{
background: |;
}

If you press Ctrl-Space now, a list would pop up. Or did you mean something else?

And also Find window should remember the last search options . Please specify what seems to be non-persistent.

[HyrumR]

I am not quite sure why do you think that auto-complete is not available for CSS values.

The list will only show up if there is a semicolon at the end of the line. So, if you type in a property name without using autocomplete and hit ctrl + space, nothing ever happens.

[Gatis]

Thank you for your cooperation.
Well, seems that there is a minor bug we would like to correct. If there is a space after the cursor (and no semicolon in the line), the list actually pops-up.
However, as this is not a sever 'bug', we can only promise to correct this within one month as the next three weeks will be quite busy for me.

[rem]

Hi.
In auto complete mode there's a semicolon inserted automatically at the end of the line.
Maybe it would be better to make this feature optional or even forget about it at all. It is easier and faster to press semicolon on the keyboard than right arrow for example (especially while inserting many selector properties one by one in css). You can also try it in Dreamweaver to see exactly what I mean.
Regards,
Rem.

[syrupcore]

thanks for searching first rem! and welcome to the forum. I'm with you - I'd prefer no semicolon.

Also, gatis, if you're around, the first post is still correct - Find options are still not sticky (for me anyway).

[Charybdis]

Hi.
In auto complete mode there's a semicolon inserted automatically at the end of the line.
Maybe it would be better to make this feature optional or even forget about it at all. It is easier and faster to press semicolon on the keyboard than right arrow for example (especially while inserting many selector properties one by one in css). You can also try it in Dreamweaver to see exactly what I mean.
Regards,
Rem.

Even better behaviour: insert semicolon at the end of the line, but also move the caret AFTER the semicolon.

[syrupcore]

Even better behaviour: insert semicolon at the end of the line, but also move the caret AFTER the semicolon.

I dream of it often. The problem is with selectors that allow multiple values - like border or background. It would be troublesome if it put the caret after the semicolon too soon on these. I'm sure there are more. I guess it would mean the team would have to build up an exclusion list. I'm not sure if the overhead would be worth it. How do other editors handle it?

I wonder if a shortcut/command would be the answer. Like a 'start next declaration' command that could be triggered from anywhere on a line. ctrl+enter maybe? I think read a post from karlis that the css new line stuff was being changed around in an upcoming release. Good time to slip it in?

Will

[rem]

Thanks for comments. I was afraid that nobody cares about it.

So, how about making this feature optional for the moment? It should be good enough for those who like it and also for those who don't. Shortcut command idea could be good solution too (starting new declaration with 'ctrl+enter' for example).
Anyway, meantime I found walk around for guys who don't like auto semicolons. Just type everything like you didn't see any 'auto semicolon' (simply insert semicolon manually). Then there is always one extra semicolon (this automatic one) running just after the caret. You can leave it at the last line or whatever. For me it's working fine.
Regards,
Rem.

[Gatis]

Actually you guys seem to speak quite reasonably
I believe there should not be too many obstacles to improve the auto-complete for css so that keeps cursor before ";" for a small number of properties, but for the rest it would place it after ";".

The question is if this list of properties can be defined and everybody more or less would agree with it.
Otherwise, we could simply remove the semicolon or maybe (Karlis will hate me for this )make this as an option.

Also, I think we could improve auto-complete if there is missing ";".
If we get more votes for improving this feature, I think Karlis will assign some resources to this. So anybody else?

[syrupcore]

not thinking about it too much, seems like just removing the ";" altogether is the simplest. Not sure if it's the best. I often end up with two ";;" anyway because it's so automatic for me to add a semicolon to the end of each line.

And Gatis, if your boss doesn't hate you every once in a while, you're not earning your money.