Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
6136
Off-topic / Re: Another WIP
« on March 14th, 2012, 08:27 AM »
Just when I thought I was out of overstyling, you pull me back in! :P
Gradients, shadows and rounded borders are things I can't use freely in the default skin, which is what I'm focusing right now... Thanks for reminding me that styling is fun and wecss is a powerful tool :)
Gradients, shadows and rounded borders are things I can't use freely in the default skin, which is what I'm focusing right now... Thanks for reminding me that styling is fun and wecss is a powerful tool :)
6138
Features / Re: New revs
« on March 14th, 2012, 12:52 AM »
rev 1461
(7 files +3, 14kb)
+ Added <mobile> option for skins. What it does right now is modify the post layout to show the userbox above the post, rather than next to it. Also, the userbox in mobile mode is simplified to: avatar, user name, user rank, post date, and action buttons. More importantly, the Quote and Modify buttons get moved to the Action menu to save some space. (Display.php, and most of the other files.)
+ Added support for 'like', 'unlike', 'quote' and 'modify' to the Action menu. (Display.php, index.language.php)
+ Added a new skin, Wireless (see the pattern in official Wedge skin names, eh?), which simply enables mobile mode and provides userbox styling, so that we don't have to style it in Weaving under a specificity of '.mobile'... Yeah, whatever. (skins/Wireless/*)
! In some rare situations, Wedge would not close the opening UL tag for action buttons. Not that it would break anything else than validation, though... (Display.template.php)
! Post classes would break in all situations (except for topic messages), because of a padding reset. I'm pretty sure I reset it for a reason, so it's likely that something else will break... If it does, well, I'll fix it again. Differently. (sections.css)
- Replaced $txt['reply_quote'] with just $txt['quote']. We're adding so many new strings to the index language files, might as well remove anything that doesn't really serve a point... (PersonalMessage.template.php, Profile.template.php, index.language.php)
(7 files +3, 14kb)
+ Added <mobile> option for skins. What it does right now is modify the post layout to show the userbox above the post, rather than next to it. Also, the userbox in mobile mode is simplified to: avatar, user name, user rank, post date, and action buttons. More importantly, the Quote and Modify buttons get moved to the Action menu to save some space. (Display.php, and most of the other files.)
+ Added support for 'like', 'unlike', 'quote' and 'modify' to the Action menu. (Display.php, index.language.php)
+ Added a new skin, Wireless (see the pattern in official Wedge skin names, eh?), which simply enables mobile mode and provides userbox styling, so that we don't have to style it in Weaving under a specificity of '.mobile'... Yeah, whatever. (skins/Wireless/*)
! In some rare situations, Wedge would not close the opening UL tag for action buttons. Not that it would break anything else than validation, though... (Display.template.php)
! Post classes would break in all situations (except for topic messages), because of a padding reset. I'm pretty sure I reset it for a reason, so it's likely that something else will break... If it does, well, I'll fix it again. Differently. (sections.css)
- Replaced $txt['reply_quote'] with just $txt['quote']. We're adding so many new strings to the index language files, might as well remove anything that doesn't really serve a point... (PersonalMessage.template.php, Profile.template.php, index.language.php)
6139
Features / Re: New revs
« on March 14th, 2012, 12:41 AM »
rev 1460
(4 files, 12kb)
* Re-optimized quickbuttons.png, saved about 200 bytes. Increased gamma correction on like/unlike because the contrast was too high on bright backgrounds. (images/theme/quickbuttons.png, other/images/quickbuttons-32bit.png)
! Fixed skin option retrieval code, that's what happens to you when you focus on documenting a feature instead of testing it thoroughly... ;) (Subs-Cache.php)
! The theme selector is too restrictive when searching for skins. It should allow for skins that don't have an index.css file to begin with. (Themes.php)
(4 files, 12kb)
* Re-optimized quickbuttons.png, saved about 200 bytes. Increased gamma correction on like/unlike because the contrast was too high on bright backgrounds. (images/theme/quickbuttons.png, other/images/quickbuttons-32bit.png)
! Fixed skin option retrieval code, that's what happens to you when you focus on documenting a feature instead of testing it thoroughly... ;) (Subs-Cache.php)
! The theme selector is too restrictive when searching for skins. It should allow for skins that don't have an index.css file to begin with. (Themes.php)
6140
A social stream is probably not too hard to implement... Probably the only difficulty is to make it translatable, which means we have to store an action ID, as well as IDs or strings for whatever is done. Has to be done either in a table with multiple fields, or a single field with serialized arrays of whatever we want to translate... I'd go for the multiple fields because it would allow to easily filter out some message types (such as likes.)
6143
The Pub / Re: Logo Madness
« on March 13th, 2012, 08:42 PM »
Good.
Ain't committed my changes yet... Having problems testing my local install on my iPod (dunno why but it no longer recognizes my direct IP, even though I haven't changed anything to the firewall setup and it's a static IP...). Still, I'll be done before tomorrow I think.
Ain't committed my changes yet... Having problems testing my local install on my iPod (dunno why but it no longer recognizes my direct IP, even though I haven't changed anything to the firewall setup and it's a static IP...). Still, I'll be done before tomorrow I think.
6144
The Pub / Re: Logo Madness
« on March 13th, 2012, 07:14 PM »
I think we're talking about both, I'm not sure myself... ;)
I'm doing other tests with a similar font that has more... 'peculiarities' of its own. I still like the current one best, though...
As for the logo (the 'two coloured things on the left'), it represents whatever you want it to be -- a rainbow, water/dust in the trail of a text string moving very quickly in your imagination, feathers, wings, a mountain, a random object split in two by a wedge... Whatever suits you best :P
Pete -- looking at your latest commits... Can you confirm that you added no extra strings to the English version? I've checked them all and it looks like it's only about splitting strings into a string + subtext, and you did it all for the French version... (Thankfully :lol:)
(Oh, and the <options> thing is broken... I've fixed it locally. Sorry.)
I'm doing other tests with a similar font that has more... 'peculiarities' of its own. I still like the current one best, though...
As for the logo (the 'two coloured things on the left'), it represents whatever you want it to be -- a rainbow, water/dust in the trail of a text string moving very quickly in your imagination, feathers, wings, a mountain, a random object split in two by a wedge... Whatever suits you best :P
Pete -- looking at your latest commits... Can you confirm that you added no extra strings to the English version? I've checked them all and it looks like it's only about splitting strings into a string + subtext, and you did it all for the French version... (Thankfully :lol:)
Posted: March 13th, 2012, 06:42 PM
(Oh, and the <options> thing is broken... I've fixed it locally. Sorry.)
6145
Features / Re: New revs
« on March 13th, 2012, 06:59 PM »
rev 1458
(12 files, 5kb)
+ Added support for skin options. This is, basically, what the <sidebar> option was about: a setting that's only used at templating time, so it should naturally belong in a wider structure, which is now $context['skin_options']... You can add any options you like, as long as you test for them in your templates. Remember that you'll have to test for empty() as well, because Wedge won't fill in the option for you if it isn't set. (Load.php, Aeva-Gallery.php, Subs-Cache.php, Display.template.php, Wine/skin.xml, Wine/Warm/skin.xml)
* Note: I also documented the upcoming <mobile> option. (Wine/Warm/skin.xml)
* Spacinazi (leftover tabs.) (Class-Editor.php, Class-WebGet.php, ManageModeration.php, ManageServer.php, ManageBoards.template.php, ManagePaid.template.php)
(12 files, 5kb)
+ Added support for skin options. This is, basically, what the <sidebar> option was about: a setting that's only used at templating time, so it should naturally belong in a wider structure, which is now $context['skin_options']... You can add any options you like, as long as you test for them in your templates. Remember that you'll have to test for empty() as well, because Wedge won't fill in the option for you if it isn't set. (Load.php, Aeva-Gallery.php, Subs-Cache.php, Display.template.php, Wine/skin.xml, Wine/Warm/skin.xml)
* Note: I also documented the upcoming <mobile> option. (Wine/Warm/skin.xml)
* Spacinazi (leftover tabs.) (Class-Editor.php, Class-WebGet.php, ManageModeration.php, ManageServer.php, ManageBoards.template.php, ManagePaid.template.php)
6146
Off-topic / Re: Introduction
« on March 13th, 2012, 01:10 AM »
Okay then.
We shall have the demo online by March 15. On the 16th anniversary of my very first website ;)
We shall have the demo online by March 15. On the 16th anniversary of my very first website ;)
6147
Off-topic / Re: Introduction
« on March 13th, 2012, 01:05 AM »
And a demo using imported data or not?
6148
Off-topic / Re: Introduction
« on March 13th, 2012, 12:59 AM »
Pete, what are your thoughts on where I should install Wedge?
6149
Off-topic / Re: Another WIP
« on March 13th, 2012, 12:00 AM »
- Yes, IIRC I tried to ensure it was easier to center-align the main menu in Wedge than in SMF :P
- A couple of suggestions based on the screenshot... (1) use a rgba(255,255,255,.3) or something as the background for the sidebar, rather than a solid color. It would benefit from the gradient below it ;) (2) remove the black line below the main menu. This area needs some breathing space.
Oh, and I really should upload my Welcome.template.php update... :P
- A couple of suggestions based on the screenshot... (1) use a rgba(255,255,255,.3) or something as the background for the sidebar, rather than a solid color. It would benefit from the gradient below it ;) (2) remove the black line below the main menu. This area needs some breathing space.
Oh, and I really should upload my Welcome.template.php update... :P
6150
Off-topic / Re: Introduction
« on March 12th, 2012, 11:55 PM »Here, here. Give them their dues, they're the only SMF fork that's still active (correct me if I'm wrong, anyone?)
and they always had the biggest goal in mind; going *far* beyond the code they started with, not just some little incremental change. That's why they started earliest, and why they're still working towards the goal of a public demo/release.
Right now is simply not the right time for releasing an alpha version of Wedge. As I said earlier, a demo is very much doable. (If we decide to do it on a separate demo site, it'll be online in a matter of days. Otherwise, might take another few weeks... Not sure about it.)
Posted: March 12th, 2012, 11:52 PM
install a wedge with disabled functional thoughts?Quote from Nao on March 12th, 2012, 01:12 PM Wedge is not ready for use yet -- which it isn't the case, but I still need to at least implement proper thought privacy and such.