pouet 2.0 bugs me beautifull
category: general [glöplog]
Much better this way.
...and while you can't argue taste, you certainly can argue design principles and (cognitive) ergonomics. And stuff like css/plugin bubbles for everyone on websites remains a horrible solution. So, thanks Kenet for being reasonable. :) [no fuel to the fire intended, no need to continue this one, etc.]
Thanks Luis for the idea. But to me, the star, it doest link the user name to the prod. It make it more like he is an admin or so.
I'm always reasonable Tomaes. But i still think changing the background color is the best way to do it as it sounds to me like a common language on forums and groups.
Maybe, as i said, the colors are to contrasted. I'll fix it, don't worry ;)
I'm always reasonable Tomaes. But i still think changing the background color is the best way to do it as it sounds to me like a common language on forums and groups.
Maybe, as i said, the colors are to contrasted. I'll fix it, don't worry ;)
Kenet: May I suggest something like this, using these CSS rules:
Code:
#pouetbox_prodcomments .comment.author:target .content {
border: 3px solid #224466;
}
#pouetbox_prodcomments .comment.author .content {
background: #224466;
padding: 5px;
}
#pouetbox_prodcomments .comment.author .foot {
background: #68a;
}
#pouetbox_prodcomments .comment.author a {
color: #9FCFFF;
}
#pouetbox_prodcomments .comment.author .bbs_quote blockquote,
#pouetbox_prodcomments .comment.author .bbs_code code
{
background-color: #775599;
border: 1px solid #AA88CC;
}
Sorry about the messed up indentation: live editing + reload from cache and all.
Either way, kudos for the feature. Doesn't seem like much but it's really a nice addition to Pouet.
ps: Hope all is well at home ;)
Either way, kudos for the feature. Doesn't seem like much but it's really a nice addition to Pouet.
ps: Hope all is well at home ;)
Quote:
by p01:
Kenet: May I suggest something like this, using these CSS rules:
Holy tabs, Batman! ;)
I didn't mind the purple, it does make it quite obvious. However your image above while it fits more with the existing theme doesn't do anything about the post footer (or so it seems) which I think it should.
I'm not a fan of purples, but I like the current purple - can we leave it as it is?
I also don't think the current purple is too bright or anything, but it probably can look that way on a badly (not) calibrated monitor.
AMcBain: Correct, the CSS tweaks I did there revert the changes on the .author footer. I don't have strong feeling about this: I think it's enough to change the background color of the author's .comment, but the .foot also looks cool with a darker blue using:
Code:
#pouetbox_prodcomments .comment.author .foot {
background: #335577;
}
Actualy, it's too dark... :)
I don't have Photoshop right here, i will fix it tomorrow.
Poï: Everything is fine, thx mate!
The youngs are growing fast :)
I don't have Photoshop right here, i will fix it tomorrow.
Poï: Everything is fine, thx mate!
The youngs are growing fast :)
I do know you try to provide [code] as is, but it´s totally leaving the borders if you post long lines of code...as to be seen in my post here, page 45:
http://www.pouet.net/topic.php?which=3637
Any Ideas how to solve this? Especially when zooming the page in (Ctrl+"+", i am at 200%+ zoom when browsing pouet) this doesnt work as should!
Sure, a workaround is previewing and changing the code-segment until it fits, but...
1.) you never know what level of zoom others use.
2.) changing code until it fits involves work in an external textEditor, as you cant use TAB etc. in the message-posting-window.
I myself have no idea how to fix it, as every added linebreak, based on ScreenSize/ZoomLevel or alike would fuck with the format of the code, while that is what [code] was implemented for, so...any ideas anyone?
P.S.: stupid me, after having previewed it, i realized the linkage was pretty unneeded :/
P.P.S: after having previewed this, i got the correct behaviour back, the thread-window-size enwidened as in prePouet2.0!
So any idea what went wrong in the linkage?
Could it be i had a linebreak myself in the [code]-segment, having caused this?
[/dejavu]
http://www.pouet.net/topic.php?which=3637
Any Ideas how to solve this? Especially when zooming the page in (Ctrl+"+", i am at 200%+ zoom when browsing pouet) this doesnt work as should!
Sure, a workaround is previewing and changing the code-segment until it fits, but...
1.) you never know what level of zoom others use.
2.) changing code until it fits involves work in an external textEditor, as you cant use TAB etc. in the message-posting-window.
I myself have no idea how to fix it, as every added linebreak, based on ScreenSize/ZoomLevel or alike would fuck with the format of the code, while that is what [code] was implemented for, so...any ideas anyone?
P.S.: stupid me, after having previewed it, i realized the linkage was pretty unneeded :/
Code:
model.transform.localRotation = Quaternion.Euler(new Vector3( 0.0f, Time.time, 0.0f)) * model.transform.localRotation;P.P.S: after having previewed this, i got the correct behaviour back, the thread-window-size enwidened as in prePouet2.0!
So any idea what went wrong in the linkage?
Could it be i had a linebreak myself in the [code]-segment, having caused this?
[/dejavu]
in the preview the [code]-segment was ok, after having posted it, it leaves the border again!
and doesnt enwide the threads complete layout as was and still is in the preview.
If you think everything looks ok to you, just zoom in please to get what i am talking about! (Ctrl+"NumPad+" should work in any browser, shouldn´t it?!)
If you think everything looks ok to you, just zoom in please to get what i am talking about! (Ctrl+"NumPad+" should work in any browser, shouldn´t it?!)
hardy: that's not zooming, that's changing the size of everything on the page (small difference, but it's like making all the objects in your demo bigger instead of moving the camera closer, not the same thing ;)
Try actual zooming instead? Works fine for me here (I can zoom right in, layout doesn't change, i just have to scroll horizontally if i zoom in too far). No idea what the shortcut would be, i use a trackpad so it's just the standard pinch/spread fingers.
Try actual zooming instead? Works fine for me here (I can zoom right in, layout doesn't change, i just have to scroll horizontally if i zoom in too far). No idea what the shortcut would be, i use a trackpad so it's just the standard pinch/spread fingers.
Wrt code blocks, it would be better to have overflow: auto; so that they don't screw up the rest of the layout and gain a their own scrollbar if needed.
kenet: Did you tweak the colors ? Yesterday evening the purple fell less saturated than the first time I saw it.... could be just the brightness and color temperature ( I use f.lux at home ) of my screen.
kenet: Did you tweak the colors ? Yesterday evening the purple fell less saturated than the first time I saw it.... could be just the brightness and color temperature ( I use f.lux at home ) of my screen.
ps:
sure, since pouet2.0 i can use the Ctrl+Numpad+ for zooming as it should have been forever, keeping the layout intact! good job on that!
Just still not in the preview, which makes the preview useless in that case! ;)
(pouetV1 used to enwiden threads once sth didnt fit the layout, making the user have to zoom/scroll himself a lot, but you know that!)
I do wonder by now, if i am the only one having this issue, tho...using Firefox 27.0. should be the newest stable!
sure, since pouet2.0 i can use the Ctrl+Numpad+ for zooming as it should have been forever, keeping the layout intact! good job on that!
Just still not in the preview, which makes the preview useless in that case! ;)
(pouetV1 used to enwiden threads once sth didnt fit the layout, making the user have to zoom/scroll himself a lot, but you know that!)
I do wonder by now, if i am the only one having this issue, tho...using Firefox 27.0. should be the newest stable!
oops, psonice* i meant! :/
hardy: if i 'resize' the page with cmd + it messes with the layout (your [code] block gets truncated, and I have to scroll it separately) but if I zoom with the pinch gesture the layout doesn't change. So I always use the proper zoom, it never causes any issues :D
pinch gesture -> i guess thats Opera then? Safari maybe?
to make it more clear what i get here on FF 27: the layout keeps intact at all times, just the text leaves the borders when zooming via Ctrl+Numpad+, which seems to be the wrong way to resize! (too bad, i have the resizing on two of my 40 mousebuttons, but coding a new macro for those shouldnt get too bad...coding a better resize for FF for the world could!)
In Preview-Mode it behaves as in prePouet2.0 tho...thats the point of my halfTroll here ;)
to make it more clear what i get here on FF 27: the layout keeps intact at all times, just the text leaves the borders when zooming via Ctrl+Numpad+, which seems to be the wrong way to resize! (too bad, i have the resizing on two of my 40 mousebuttons, but coding a new macro for those shouldnt get too bad...coding a better resize for FF for the world could!)
In Preview-Mode it behaves as in prePouet2.0 tho...thats the point of my halfTroll here ;)
CMD-key -> AppleOS -> Safari! but who said you cant choose your browser on Apple? ;)
Sorry, never experienced working with one of em on a daily base, would have had installed Firefox via Safari most likely as first step anyway! :/ (while not knowing if thats a good decision at all, just used to workaround IE as first step after installing new Win, or starting up some PC with preInstalled OS (Win in most cases, when not explicitly having asked for Linux Distro x.x))
Sorry, never experienced working with one of em on a daily base, would have had installed Firefox via Safari most likely as first step anyway! :/ (while not knowing if thats a good decision at all, just used to workaround IE as first step after installing new Win, or starting up some PC with preInstalled OS (Win in most cases, when not explicitly having asked for Linux Distro x.x))
poi: They changed it a bit, after some guys (ahem) were bitching about it. ;)
weren´t even coderColors, just a bit overSaturated, as had used the same saturation as the pouet-blue! ;)
hardy: yeah, safari/osx. It's a pretty good browser. Good privacy controls, fast, light on the CPU. If you have other apple devices (i'm an iOS dev so I have piles of them) there are really good sync features too (like sharing tabs between devices).
On PC, I'd first install something to replace IE too. But not safari, the PC version.. well, I'd prefer IE, put it that way ;) I think apple took it to the vets and had it put to sleep. I have firefox, but stopped using it years back, it was too slow (software rendering, urgh.. but i guess that's fixed by now). I use chrome usually as a backup browser (with webgl it's hard to edit text with a heavy shader running in safari, chrome runs a bit better, and web audio support seems a bit better too).
On PC, I'd first install something to replace IE too. But not safari, the PC version.. well, I'd prefer IE, put it that way ;) I think apple took it to the vets and had it put to sleep. I have firefox, but stopped using it years back, it was too slow (software rendering, urgh.. but i guess that's fixed by now). I use chrome usually as a backup browser (with webgl it's hard to edit text with a heavy shader running in safari, chrome runs a bit better, and web audio support seems a bit better too).
Well, mine is not a bug, but a proposition.
I have found a lot of releases of the groups, which does not exist in the DB here. The issue is that these groups, at least in may packages, have not included ANY intro in to it. But did left a sign by the NFO or ADD or FileID file.
Is it a good idea in adding a feature like "group info" attached to the group?
I have found a lot of releases of the groups, which does not exist in the DB here. The issue is that these groups, at least in may packages, have not included ANY intro in to it. But did left a sign by the NFO or ADD or FileID file.
Is it a good idea in adding a feature like "group info" attached to the group?
