12944qwertyHome • Talk • Contribs
See More →
- If I left a message on your talk page, feel free to respond there or here, but stay consistent — don't respond here then continue the discussion there.
- Unless you ask me to do otherwise, if you talk to me here I will reply to you here.
- All guidelines (Community and Scratch Wiki) still apply here — please follow them.
- If you leave me a disrespectful message, do not expect a response and expect to see your message deleted.
- If I made a mistake, of any kind whatsoever (assume good faith), please post your view calmly and collectedly.
- Think about your post before posting and preview!
- I welcome all questions — Wiki-/Scratch-related questions and personal(not too personal)/offtopic questions are equally welcome here.
- I will only ping you if I know you are a new (of less than a week old) user (if I forget, do let me know) or if you ask me to!
- Remember to write four tildes at the end of your reply/question
- When referring to me, call me 12944qwerty or qwerty
| Bot Archives | 1 | 2 | 3 | 4 | 5 |
|---|
This page contains 15,715 bytes
Discussing an Edit
Done
Hi! I reverted an edit of yours and I would like to discuss it with you. First of I think it the page Scratch Design Studio Row should stay, because it discuss the row not the SDS, If we get rid of that Projects Curated by () would go as well.
Jakel181 (talk | contribs) 17:19, 15 January 2019 (UTC)
- Ok, should I add it using Template:main? This way it still has it's own page.
12944qwerty Talk Contribs Scratch 18:12, 15 January 2019 (UTC)
That is true, but on the same note shouldn't Projects Curated by () be merged with Curator_(front_page) as well. Also we have documented the front page on scratch and that includes the SDS row, and every row on the homepage. Jakel181 (talk | contribs) 01:01, 16 January 2019 (UTC)
- Actually, I'm in favor of merging, because the entire SDS Row page's contents could fit into one section in the SDS page... also, there was overwhelming consensus on merging, so @jake why did you revert?
- FYI @qwerty we usually don't delete pages that are merged, instead we redirect them to wherever they got merged.
kenny2scratch Talk Contribs Directory 02:43, 16 January 2019 (UTC)
- The Front page is very big altogether, sure you can include some info on each of them, but it wouldn't make sense to add 7 rows in one.
- Also, instead of deleting the page after merging, we can keep it and say that the main page was on the SDS Row. Like ken is saying.
- @jakel181 Also, you used an outdent for 6 instead of 5.
- @ken should I merge and redirect it? 12944qwerty Talk Contribs Scratch 02:45, 16 January 2019 (UTC)
- Formalities are formalities, and the other side hasn't had a chance to express further views. Let's wait until Jake says something. kenny2scratch Talk Contribs Directory 02:46, 16 January 2019 (UTC)
- @qwerty whooops thanks fixed.
- @ken I reverted so the page wouldn't get deleted whilst we we discussing and wouldn't be blank if anyone came to the wiki whilst we were discussing.
- I start this argument with a question. Why should this article be merged? The response was as follows: "The page is talking about a part of the SDS. So, it should just be a section in the main page of SDS saying SDS Row." Yes the page is about a part of the SDS, though, as Scratch Design Studio Row is to Scratch Design Studio, likewise, Projects Curated by () is to Curator (front page). I never though I would ever need to use an analogy lol. If we merge the page, then by the same principle, we would merge the page about the curator row. When you said "The page is talking about a part of the SDS..." it can be assumed that you are talking about the page in a whole. With that inference, I can declare your statement false. Yes the page is about a part of the SDS, but it is also about the forth row from the top of the page. The article explains the purpose of the row, and how the row works. When I mentioned documenting the front page, which you responded with "The Front page is very big altogether, sure you can include some info on each of them, but it wouldn't make sense to add 7 rows in one." That is not my intention to merge all the row articles to that page, and I apologize for making myself unclear. What I was trying to say was that we have documented every row, with it's own article and I would not make sense if we did not have an article for the SDS row. Jakel181 (talk | contribs) 13:30, 16 January 2019 (UTC)
- My motivation for merging is purely practical: the "Projects Curated by ()" page has a modest amount of content of its own, and would not fit into a section. The SDS Row page, however, has about a section's worth of content. Rather than taking up an entire search result with a stub, it makes more sense to just redirect it to a bigger piece of content that people can then read as well, without having to click a different link.
- Keeping it consistent is a good goal, but it does not take priority on keeping articles at least modestly long, with the exception of block and FAQ pages which are not strictly articles. If there are other rows with very short pages to their name, they should be merged too, unless there is nowhere to merge them to. kenny2scratch Talk Contribs Directory 13:41, 16 January 2019 (UTC)
- Agreed, keeping a section worth of page is unnecessary. Merging them would be more practical as it wouldn't remove it entirely but still have the proper amount of information in a section on the main page.
- My mistake from when I tried to merge them was deleting the page instead of redirecting it.
- Also, should we move this discussion to the CP for more views? 12944qwerty Talk Contribs Scratch 14:12, 16 January 2019 (UTC)
- Formalities are formalities, and the other side hasn't had a chance to express further views. Let's wait until Jake says something.
That makes sense. :) I'm in favor of merging it now :) Jakel181 (talk | contribs) 12:34, 17 January 2019 (UTC)
- Merging 12944qwerty Talk Contribs Scratch 14:02, 17 January 2019 (UTC)
A commit to your website
You recently made a commit to your website on Github and credited me (since I made the edits). However, you credited me as "@jammum". I'm not on Github, so if it's possible, make a link to my Scratch Wiki profile to credit me. You don't have to do it. 
Jammum (talk | contribs) 18:26, 15 January 2019 (UTC)
- I'll see if I can.
- Also, if you are not on Github, how did you notice it? 12944qwerty Talk Contribs Scratch 18:53, 15 January 2019 (UTC)
On My Talk Page
As i am writing this i notice WikiMonitor already messaged you, but on my talk page User_Talk:JJBullet you forgot to sign your post.
JJBullet Talk Contribs Templates 14:29, 4 February 2019 (UTC)
- Yup, sorry.
- Also, what happened to your sig? Go to editing mode.
12944qwerty Talk Contribs Scratch 14:34, 4 February 2019 (UTC)
Welcome.js
Hey there,
i have a query about welcome.js
how do i install it so it automatically goes onto a new users talk page without even having to visit that said page??
many thanks
JJBullet Talk Contribs Templates 14:52, 4 February 2019 (UTC)
- I think your sig is fixed now.
- To make the welcome.js work, you can just follow ken's instructions If you still have questions, just ask. 12944qwerty Talk Contribs Scratch 14:55, 4 February 2019 (UTC)
- ok thanks
- JJBullet Talk Contribs Templates 14:59, 4 February 2019 (UTC)
What is in the box? 12944qwerty Talk Contribs Scratch 15:20, 4 February 2019 (UTC)
How do you create a sidebar?
I saw your sidebar and was wondering how to make one, please can you explain how to make one or link to somewhere which says how to create one. Thanks.
SuperWhale123 (talk | contribs) 20:07, 4 February 2019 (UTC)
- Basically you just need to have the attributes of:
position:fixed;left:0;bottom:0;
This will make it fixed on the screen like the header on the top. And the sidebars. 12944qwerty Talk Contribs Scratch 20:12, 4 February 2019 (UTC)
You don't need to reload your common.css
Hi, I saw you added something to your common.js that loads your common.css... but that's unnecessary, because your common.css is loaded for you on all pages anyway, so that only serves to slow down your page loads. If you added it because your CSS wasn't updating, remember that both common.js and common.css sometimes need a hard refresh. I recommend you remove the line loading your common.css. kenny2scratch Talk Contribs Directory 10:27, 7 February 2019 (UTC)
- Hey, I tried refreshing cache, refreshing, and restarting my computer but it still didn't work. I'll try removing the line though. 12944qwerty Talk Contribs Scratch 14:00, 7 February 2019 (UTC)
- It didn't work because your CSS was overridden. A rule in CSS is that more specific selectors take precedence. In the "navigation" and such sidebars, the more specific
h4selector (child element of "body") overrides thecolor: redof the body, setting it to#575e75instead; the more specificaselector (also child of "body") overrides thecolor: redand sets it to#4d97ff. And in the actual page, content, the#contentselector (selecting a specific element by ID) overrides thecolor: redand changes it toblack. - To fix that, it really depends on what you want to do. Do you want to:
- really make every single piece of text red?
- It didn't work because your CSS was overridden. A rule in CSS is that more specific selectors take precedence. In the "navigation" and such sidebars, the more specific
body {
color: red !important; /* !important is the ultimate override */
}
- make everything that isn't specifically non-red red?
* { /* selects all elements */
color: red; /* still overridden by more specific selectors like h1, h4, a */
}
- make every single piece of text that is part of the page content red?
#content { /* selects only the page content */
color: red !important; /* but overrides everything inside it */
}
- make everything inside the page content that isn't specifically non-red red?
#content { /* selects only the page content */
color: red; /* should turn most stuff red,
* but anything that sets its color in style= will stay that way
*/
}
- One of those should be what you meant. kenny2scratch Talk Contribs Directory 08:27, 11 February 2019 (UTC)
- Oh, ok. Thanks! 12944qwerty Talk Contribs Scratch 14:06, 11 February 2019 (UTC)
- Oh, ok. Thanks!
- One of those should be what you meant.
Hi
Cool, you speak Gujarati too?
Kritav (talk | contribs) 16:33, 11 February 2019 (UTC)
- Oh, so you are Indian cool!
- Yep, but I don't know how to write. Unfortunately. 12944qwerty Talk Contribs Scratch 17:18, 11 February 2019 (UTC)
Hey
Hey There, How Are You??
JJBullet Talk Contribs Directory 11:34, 13 February 2019 (UTC)
- I'm fine, you? 12944qwerty Talk Contribs Scratch 14:24, 13 February 2019 (UTC)
Lol
You only need to say "compressed" once and the next time my bot runs it'll ignore the file as "probably already compressed"... of course, don't abuse it by saying "compressed" when it isn't actually - just use that to mark it as compressed. kenny2scratch Talk Contribs Directory 14:22, 15 February 2019 (UTC)
- No, I compressed untill it wouldn't compress anymore.... It took 10 tries before it compressed by 0%. 12944qwerty Talk Contribs Scratch 14:31, 15 February 2019 (UTC)
