New revs - Public comments

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: New revs - Public comments
« Reply #405, on July 4th, 2012, 10:50 PM »
Quote from Arantor on July 4th, 2012, 05:44 PM
Loving the new popup in r1627 by the way. I like it even more than the lower-right-corner alignment (which is something I never thought would happen)
Same here actually :)
But the alignment was probably something I cooked up because at the time it couldn't be dragged away.. I don't know. I think it was because of that. I think I implemented dragslide() after writing the initial code. Then I just forgot to consider centering it...
Quote
What I will do then, now we have the newer shinier version of it, is migrate the PM popup to use that - that was really what stopped me from changing the PM popup to use reqWin before was that the alignment of it seemed strange given the context, but putting it like that will work well.
Definitely.
One of my goals (which I'm unlikely to achieve though) is to ensure that as many UI elements as possible are harmonized. That would mean trying to use the same code (or at least identical CSS) for: the select box, the main menu, the mini-menu, Zoomedia, and the popups. I actually wrote all 5 of these separately, i.e. I didn't reuse any code inside another component, but right now I'm simply trying to determine whether it can be done and whether it would add to Wedge, or detract from it. The most likely candidates for merging are the main and mini menus, of course. But the mini-menus looks awfully like the popups right now. And Zoomedia is pretty much the same concept as the popup... And the select box uses a scrollbar which I could make use of in the popup. Maybe the first thing I'll try to do is split the scrollbar code from the SelectBox object into its own object (it's already done, actually, but it's an object that's internal to SB...!)
Ideally I would release the select box, zoomedia and popup code as separate components on github and offer people to help improve them (along with WeCSS). I just don't know whether it'll stick with them.
Quote
One thing that does occur is that depending on what else is going on it might not be obvious enough. XenForo, for example, does their popups similarly, but adding something like a 10px border plus a massive shadow - personally I find that a bit much, but it definitely shows some contrast to the background.
I haven't seen it in a while, but I've made the shadow a bit more obvious, and added boldness to the titles. Is that better now...?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: New revs - Public comments
« Reply #406, on July 4th, 2012, 11:04 PM »
Quote
But the alignment was probably something I cooked up because at the time it couldn't be dragged away.. I don't know. I think it was because of that. I think I implemented dragslide() after writing the initial code. Then I just forgot to consider centering it...
Heh, I know that feeling.
Quote
One of my goals (which I'm unlikely to achieve though) is to ensure that as many UI elements as possible are harmonized.
A fine goal :) Though I wouldn't worry about trying to reuse styles - I think it might be better to keep them separate but well documented, so that a theme which wanted to change everything could do so and require a shade more work than a theme that doesn't. As long as they're consistent, they don't have to reuse code - I can see it would likely make things worse to forcibly try to reuse code like that.
Quote
Ideally I would release the select box, zoomedia and popup code as separate components on github and offer people to help improve them (along with WeCSS). I just don't know whether it'll stick with them.
I'd probably be inclined not to, not because of my usual fears etc. related to such but simply the maintenance aspect about how much work it would take to de-integrate then re-integrate it later with updates etc.
Quote
I haven't seen it in a while, but I've made the shadow a bit more obvious, and added boldness to the titles. Is that better now...?
Works for me :) It is much more clearly contrasted now :)
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: New revs - Public comments
« Reply #407, on July 5th, 2012, 12:28 AM »
I can make reintegrating easier by simply splitting the stuff so that I only need to reimport the separate files... e.g. like sbox.js can be stand-alone if so desired, without any rewrites.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: New revs - Public comments
« Reply #409, on July 5th, 2012, 08:22 AM »
Well, question is, do you have any issues with me going open source with these?
Because it'd be a way for me to test github or bitbucket or whatever... If anything, I want to release WeCSS because I think it's better than LESS or SASS (not in EVERY way but in most), and it pains me to read .Net every month and see them recommend them heartily :P

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: New revs - Public comments
« Reply #410, on July 5th, 2012, 03:00 PM »
I have no issues with them being open source, provided that you're happy to keep on top of what comes in and make sure that any changes don't conflict with what Wedge is doing, really.

I still think it's likely to eat time trying to keep everything in step if we're not careful, but other than my usual cynicism about workloads, no objections :)

I find WeCSS better than LESS to deal with.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: New revs - Public comments
« Reply #411, on July 6th, 2012, 04:36 PM »
Quote from Arantor on July 5th, 2012, 03:00 PM
I have no issues with them being open source, provided that you're happy to keep on top of what comes in and make sure that any changes don't conflict with what Wedge is doing, really.
I'm trying to find a structure that would 'work' at github... I'm sure it can be done. (An organization account for Wedge, where we'll put Wedge itself, and then I need to determine whether my own little projects will be in this account or mine.)
I probably won't post everything in a single go though -- I'm thinking of going with WeCSS or SelectBox first, and then working from there...
Quote
I still think it's likely to eat time trying to keep everything in step if we're not careful, but other than my usual cynicism about workloads, no objections :)
Yeah, it's one of my main concerns about this. But it can bring benefits. Plus, I wouldn't like someone else to fork some of these components into jQuery plugins on github, even if respecting our license terms... I'd rather host the whole thing myself :P
Quote
I find WeCSS better than LESS to deal with.
Yep :) I just don't know about the name, ah ah... I think "Wess" is probably simpler and people are going to understand it better than "Wecess", because it looks more like "Less".
I ponder for a long time over many silly things!
Posted: July 5th, 2012, 06:58 PM

Also, re: PM popup...
I just looked into it, and noticed that it calls ?action=pm, rather than a popup saying "you've got mail, suckah!"
So basically what it would do if using reqWin, would open an Ajax popup with a page that's built for fullscreen, while it should instead show a special version with, for instance, an extract of the latest PMs in it, etc...
Maybe we'll get rid of it in favor of the notification system (+ popup) later, but for now all I can suggest is adding a ";sa=popup" param to the URL and build a special version for it... Or simply link to "?action=help;in=you_ve_got_mail_suckah_no_dont_bother_looking_for_that_string"
Re: New revs - Public comments
« Reply #412, on July 6th, 2012, 11:14 PM »
Btw do you have an idea whether or not I should make dimming the default?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: New revs - Public comments
« Reply #413, on July 6th, 2012, 11:19 PM »
Quote from Nao on July 6th, 2012, 11:14 PM
Btw do you have an idea whether or not I should make dimming the default?
Do it. It works very well for me.

I haven't looked at 2.1's source much (literally last looked ages ago), would rather not do so, ironically out of a weird sense of respect. I figure we branched off when we did and I've only re-incorporated stuff back in from the patches after we branched, I see it that we went our separate ways and that was that, you know?

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

Nao

  • Dadman with a boy
  • Posts: 16,082

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670

Nao

  • Dadman with a boy
  • Posts: 16,082

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
Re: New revs - Public comments
« Reply #418, on July 14th, 2012, 01:25 AM »
Quote
* Changed default windowbg colors for Weaving. I like change from time to time... (index.css)
Liked the older colors better, seemed richer to me. Now they seem pale and bland[1].
 1. Could it be that I'm just really picky about color choice? Or maybe it''s my monitor...

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: New revs - Public comments
« Reply #419, on July 14th, 2012, 07:45 AM »
Or maybe I have a tendency to either do Babylon ripoffs using Noisen-inspired color sets :P (Which are basically a series of color sets I build in a few minutes for fun and then offered as choices to blog creators on the site...)

I have a Samsung 971P monitor, it's a high-quality 5/4 monitor (like, one of the very last before this annoying 16/9 & 16/10 wave took over everything... Gosh where can I find 4/3 or 5/4 monitors now?!), it's pretty well known for the quality of its colors too.
I think that my IPS screen actually shows 'blander' but 'more accurate' colors than a TN screen. What's yours?
Posted: July 14th, 2012, 07:42 AM

(Also, these colors are closer to the postbg ones, I'd say.)