Add a setting to not open grssam.com after an update

[Drugoy]

I hate when I update a ton of extensions and then have a bunch of new tabs opened, this makes me feel like the opened tabs are some new kind of a spam. I know you would like to advertise your blog, but that's a quite an unpleasant way to do that, at least when there is no option to turn that off.

[grssam]

Actually, Right now I have no incentive of opening that blog, other than telling people and spreading word (No ads, no anything else).

I will disable that in future when the user base is a little higher. or atleast provide an option. Anyways, its not an everyday thing, and since this addon is in early development stages, people might want ot know what new features have been added to it. Like people would totally not know that they can easily import styles from Stylish, or they can now Sync their styles.

[Drugoy]

Well, you may attach the release notes to the updates. They will be accessible in the add-ons manager then. As for the problem of making your blog more popular I suggest you to do a few things:

1. you may set your blog's address as "homepageURL" in the install.rdf file of your extensions.
2. this is the page that most users visit when the want to know something about you. And I don't see there a link to your blog, so if I was not familiar with you earlier - I wouldn't even know that you have a blog.
3. this page says you have created 6 awesome add-ons, and your blog says you have created only 2 add-ons. You should add the rest ones to your blog at least with a reviewing article per add-on.
4. I'm not reading fast (but I'm not reading slowly either), thus I don't have enough time to read what was written in the .slide-container on your site, before the slide gets switched to the next one. I'd suggest you to remove that slider completely, as it is causing laggs even on my, pretty modern and fast computer. To notice the laggs - just try to scroll when the slides get switched.

[grssam]

Thanks for the feedback. And I already did the 4th point you mentioned. Its slow now, and will slide lesser :)

I am not popularizing my blog. I want to popularize my addons. For instance, USM has s o much potential, still so less users. The blog gives a very good platform to promote my addons from among my other addons (for ex. from LBE)

I will change the links and update the pages very soon.

[Drugoy]

You are welcome and thanks for what you do :)

To popularize your add-ons - all you have to do is keep adding newly requested features and fixing the reported bugs. That is the hardest, but the most correct way. Users are not stupid and they judge of things by their quality. High quality things become popular pretty fast. As for USM - it still loses to Stylish in some aspects, but since you finally got back to the development - there is not so much left to make USM finally beat Stylish, so just keep up the good work :)

[grssam]

But IMO, the editor is already better than what Stylish offers, even with all the parsing issues remaining ;)

[Drugoy]

Well, since you have finally fixed the issue with the AGENT_SHEET flag - I think I would agree, but I haven't yet written any styles since the today's USM update (yeah, I've noticed the USM's update just today...), so I can't yet completely agree with that. I remember last time there were some issues that made me create new styles in Stylish instead of USM.

What I personally don't like in USM is it's code formatting:

#something {

gets transformed into

#something {
}

with the caret staying on the 1st line, so if you continue typing - it will be added to the 1st line. I'd prefer if the caret would move to the 2nd line, automatically paste a "tab", then put the caret, then put one "space" and then a closing "}". But that is something Stylish doesn't even have yet.

I also don't like that if you type "!" - you will have to hit ctrl+z TWICE (instead of hitting it once) to undo that.

[grssam]

Simple things like these can be solved easily :)

Lets make it granular and create issue for each of the small things like this one :)

Many thanks that you are once again on board. I really missed your feedback.

[Drugoy]

Okay ;) As for code formatting - some issues can be of some personal preferences, so let's first talk this over.

What we have is:

1. People may have different code formatting style preferences. Example is:

.thisis{extremely:economic!important;but:unpleasant;for:reading!imporant}

.thisis { way: more !important; readable: but; not: completely !important}

.thisis {
    beautiful: yes !important;
    economic: nope !important; }

This leads to a problem: Then how should USM behave?

Possible ways out are:

1. Only hardcore and propaganda: "like it the way it is, or cope with it!", i.e. have only 1 style of code formatting <I>- this is easy, but not actually a very correct way.
2. Give users the power of choice: a. make a few predefined code formatting styles, to allow users switch between them - this is a harder, but more correct way out. However, it's not as correct as the next option. b. add some kind of "rules" support, so users could create (and also export/import to share_them_with/get_from others) rules of how the USM should format the code - this is the hardest and most expensive, but it also is the most correct way, since it brings the highest level of user customization, which is truly "̶L̶i̶n̶u̶x̶ ̶w̶a̶y̶" "Mozilla way" What do you think about it?