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
2941
The Pub / Re: Not using version numbers as such
« on May 28th, 2013, 03:04 PM »https://www.phpbb.com/about/history/Quote from Nao on May 28th, 2013, 02:02 PM If they're showing their mythology names somewhere, I'm too bad at finding them then...
3.0 = Olympus, 3.1 = Ascraeus, 3.2 = Arsia, 4.0 = Rhea
AFAIK they're all Greek in origin.
Plenty of choice, certainly. We could keep it simpler and just use names mentioned in Hitchhiker's Guide, there's fewer in there. ;) Not the complete alphabet if memory serves but I'm not entirely big on the 'rotating through the alphabet' thing.
Nothing wrong with that. My own cultural references are surprisingly poor these days, it's been years since I've seen or read anything with a decent cast of characters and places, barring H2G2 of course.
Apart from the 5th book which I hate with a passion (I never got around to reading the recent 6th one), I loved them all, especially the first and fourth...
My other favorite books aren't exactly filled with easy-to-remember names, though... La Horde du Contrevent, Gloriana, What Mad Universe!, maybe Riverworld though..? It has many historical characters in it...
Anyway.
Yeah, agree with you on LOTR type naming. Norse mythology is cool, but off hand I don't know many names beyond the obvious (Asgard, Thor, Odin, Valhalla, Loki and for the few Dirk Gently fans, Mr Toerag.)
Baldr/Baldur/Balder
C...Crap, Can't Conceive of one starting with C... :^^;:
Okay, let's just forget this one, I guess... ;)
2942
Plugins / [Plugin] Re: Notifications system (1.0)
« on May 28th, 2013, 02:07 PM »
So, as I mentioned in my thoughts, I've been working on an alternative way of showing notif previews, which would work on mobile...
I'm pretty much finished with it, and it works great on mobile. It's also about 100 bytes smaller in the js.gz, and also does without the extra #notprev styling I added recently.
I'm planning to upload it here to have you guys review it and tell me what you prefer.
The main issue is, I like the current one better... :-/
The difference is, the new one doesn't work on hover but on click, meaning it's less taxing on the server, but also requires more attention to get the preview. Probably needs a visual hint that you have to click, etc...
I also modified the popup to ensure it can extend to the full window height, so I can easily add previews BELOW the notifications without making it too hard to navigate.
So... Please everyone try the current version a bit, then tell me you're ready for the new version, or something... I'll upload it, and you can start comparing ;)
I'm pretty much finished with it, and it works great on mobile. It's also about 100 bytes smaller in the js.gz, and also does without the extra #notprev styling I added recently.
I'm planning to upload it here to have you guys review it and tell me what you prefer.
The main issue is, I like the current one better... :-/
The difference is, the new one doesn't work on hover but on click, meaning it's less taxing on the server, but also requires more attention to get the preview. Probably needs a visual hint that you have to click, etc...
I also modified the popup to ensure it can extend to the full window height, so I can easily add previews BELOW the notifications without making it too hard to navigate.
So... Please everyone try the current version a bit, then tell me you're ready for the new version, or something... I'll upload it, and you can start comparing ;)
2943
The Pub / Re: Not using version numbers as such
« on May 28th, 2013, 02:02 PM »
If they're showing their mythology names somewhere, I'm too bad at finding them then...
Anyway, I've had a look at these...
http://en.wikipedia.org/wiki/List_of_proper_names_of_stars
http://en.wikipedia.org/wiki/List_of_proper_names_of_stars_in_alphabetical_order
Only the letter Q is missing, and could be substituted with something else. (Look for "Qanturis" for instance.)
There's only one star that has a name (alternative name, actually) starting with an "i".
We have a large choice of names, other than that... ;)
Could even have an "A" public alpha series starting with "Alphard", where we change the star name every time we release a new alpha... Alcor[1], Altair, Antares, etc... And a B series starting with Betelgeuse (Beta), then Benetnasch, etc...
I don't have any other ideas, though. But I'm putting a veto on anything even remotely related to fantasy stuff like Tolkien, sorry... :P I like LOTR, but I'm sick of all those Legolas people in RPGs... :lol:
I could be convinced into choosing names from sci-fi books, though...
Or maybe Norse mythology? Starting with Asgard, of course..!
Anyway, I've had a look at these...
http://en.wikipedia.org/wiki/List_of_proper_names_of_stars
http://en.wikipedia.org/wiki/List_of_proper_names_of_stars_in_alphabetical_order
Only the letter Q is missing, and could be substituted with something else. (Look for "Qanturis" for instance.)
There's only one star that has a name (alternative name, actually) starting with an "i".
We have a large choice of names, other than that... ;)
Could even have an "A" public alpha series starting with "Alphard", where we change the star name every time we release a new alpha... Alcor[1], Altair, Antares, etc... And a B series starting with Betelgeuse (Beta), then Benetnasch, etc...
I don't have any other ideas, though. But I'm putting a veto on anything even remotely related to fantasy stuff like Tolkien, sorry... :P I like LOTR, but I'm sick of all those Legolas people in RPGs... :lol:
I could be convinced into choosing names from sci-fi books, though...
Or maybe Norse mythology? Starting with Asgard, of course..!
| 1. | Okay, I won't hide the fact that my #1 cultural reference is, and always be, a TV show named Saint Seiya, which emanuele is familiar with -- it was popular in France, Italy and Spain mostly -- and my favorite part of the show was set in Asgard, with the main characters fighting a set of antagonists named after the main stars in Ursa Major, so, yeah, you get the idea... And my favorite of those, is named Alcor Bud. Then you have Mizar Syd, Benetnasch Mime, Phecda Thor, and so on. |
2944
The Pub / Re: Not using version numbers as such
« on May 27th, 2013, 09:31 PM »
Constellations? Star names? Mizar, Dubhe, Alkaid... gotta love these Ursa Major stars.
Or something else entirely...
Or something else entirely...
2945
Features / Re: New revs
« on May 27th, 2013, 10:53 AM »
rev 2135
(7 files, 8kb)
+ Added a hover preview of posts that triggered a notification. A good start! Still needs work, but it works for now. Also added a get_single_post() helper function which might need some love from Pete (security-wise maybe?) if we use it elsewhere... (Class-Notification.php, Notifications.php, notifiers/Likes.php, Subs.php, script.js, index.css)
* Renamed Class-NotifierLikes.php to just Likes.php (Notifications.php, notifiers/*)
* French tweaks. (ManagePermissions.french.php)
(7 files, 8kb)
+ Added a hover preview of posts that triggered a notification. A good start! Still needs work, but it works for now. Also added a get_single_post() helper function which might need some love from Pete (security-wise maybe?) if we use it elsewhere... (Class-Notification.php, Notifications.php, notifiers/Likes.php, Subs.php, script.js, index.css)
* Renamed Class-NotifierLikes.php to just Likes.php (Notifications.php, notifiers/*)
* French tweaks. (ManagePermissions.french.php)
2946
Features / Re: Silly menu experiment...
« on May 26th, 2013, 03:42 PM »
I don't see a problem with these...
Facebook has its logout link in a dropdown menu, too, AFAIK.
As for the register link, I don't remember, but there's always a possibility to add the login box to the sidebar, which makes the argument moot.
Really, if this is a problem, these options can be moved elsewhere... I just wanted to see how good it could look if you didn't have to cope with the multiple lines of text that the main menu would use up in a smaller width context. I'd say it's pretty nice. Of course you're free to feel otherwise...
Facebook has its logout link in a dropdown menu, too, AFAIK.
As for the register link, I don't remember, but there's always a possibility to add the login box to the sidebar, which makes the argument moot.
Really, if this is a problem, these options can be moved elsewhere... I just wanted to see how good it could look if you didn't have to cope with the multiple lines of text that the main menu would use up in a smaller width context. I'd say it's pretty nice. Of course you're free to feel otherwise...
2947
Archived fixes / Re: Multiple Same-Name Selection Box When Notifying
« on May 26th, 2013, 03:41 PM »
My opinion of a non-toxic license is that it should:
- allow for re-use in any kind of program,
- not allow for re-licensing of the entire file that is under said license. Yes, you can still do closed source changes to the file, but they need to be put in another file... Which should be enough to encourage users to share their changes if they're not too complex.
That's my, err... Idea of freedom, I guess.
And yes, about the GPL code in Wedge, as you know I'm working these days on evaluating alternatives.... Which is probably why I'm reluctant to share any code right now, even though I posted my menu changes in another topic today... :lol:
- allow for re-use in any kind of program,
- not allow for re-licensing of the entire file that is under said license. Yes, you can still do closed source changes to the file, but they need to be put in another file... Which should be enough to encourage users to share their changes if they're not too complex.
That's my, err... Idea of freedom, I guess.
And yes, about the GPL code in Wedge, as you know I'm working these days on evaluating alternatives.... Which is probably why I'm reluctant to share any code right now, even though I posted my menu changes in another topic today... :lol:
2948
Archived fixes / Re: Multiple Same-Name Selection Box When Notifying
« on May 26th, 2013, 03:23 PM »
- Nowhere... I haven't SVN'ed them at all...
- Considering that your repo is BSD, and Wedge isn't, as long as Wedge isn't MPL'ed (which it might be in the future, of course), re-using my changes isn't automatically approved... Not that I don't want you to re-use my changes anywhere; it's just that to me, BSD is nearly as toxic as GPL is: if someone wants to improve on the code and re-license it, they can... Ideally, maybe you should relicense it to something that can't be relicensed (to GPL or commercial), in which case I'll update the license in the Wedge version and automatically give you my changes.
I know it stinks, and I don't like the idea of doing this, but the code itself is the only thing that gives Wedge its edge. I've seen over at Elk that they're re-using my ideas here and there, which I'm fine with, but if we go commercial, I'll be quite happy we kept our code closed-license.
So, err... The official answer is: I'm not done yet with the changes :P The code is a WIP, it's awfully complicated right now. Also, some of the bugs I fixed, may very well be absent from your own code. I may have added the bugs myself... The unofficial answer is, please be patient, while Pete and I work out the various licensing issues we still have.
- Considering that your repo is BSD, and Wedge isn't, as long as Wedge isn't MPL'ed (which it might be in the future, of course), re-using my changes isn't automatically approved... Not that I don't want you to re-use my changes anywhere; it's just that to me, BSD is nearly as toxic as GPL is: if someone wants to improve on the code and re-license it, they can... Ideally, maybe you should relicense it to something that can't be relicensed (to GPL or commercial), in which case I'll update the license in the Wedge version and automatically give you my changes.
I know it stinks, and I don't like the idea of doing this, but the code itself is the only thing that gives Wedge its edge. I've seen over at Elk that they're re-using my ideas here and there, which I'm fine with, but if we go commercial, I'll be quite happy we kept our code closed-license.
So, err... The official answer is: I'm not done yet with the changes :P The code is a WIP, it's awfully complicated right now. Also, some of the bugs I fixed, may very well be absent from your own code. I may have added the bugs myself... The unofficial answer is, please be patient, while Pete and I work out the various licensing issues we still have.
2949
Features / Silly menu experiment...
« on May 26th, 2013, 01:03 PM »
Set #main_menu to display: inline-block
Then, add this in the DOMContentReady portion of Wedge's script.js file:
Code: [Select]
This has the amusing effect of ensuring that the main menu only takes one line, and each entry beyond that will be moved to a dynamic menu entry at the end. Basically, it behaves like phpMyAdmin and a couple other scripts. I wrote the code myself though, dunno how they 'do it', but since their CSS is probably very different, it doesn't matter...
Anyway, I thought it was cool that I managed to do it in only 4 lines (2 of which compressing as one...), and of course it executes pretty quickly, but I'm not super-happy with the 'more' menu though...
- Main menu doesn't support icons in its entries; well, it does, but it doesn't look pretty... So I removed the icons for consistency, but it could be fixed by CSS.
- Need to add a 'subsection' class to all child LI's, so that we get a horizontal arrow...
- I've set the maximum width to 75% of the window size, so that we can see the sub-menus entirely. Ideally, thought, I should rewrite my main menu code to show the drop-down on the left of its parent, rather than its right, when its width extends beyond the window bounds... I already did that a few weeks ago for the select box rewrite, didn't I..?
- Probably should wrap this into a resize event, so it gets updated when the window is resized, but that also means adding more code to move the submenus to the top, and... MEH.
What do you think of this?
Here's what it looks like:
Then, add this in the DOMContentReady portion of Wedge's script.js file:
if ($('#main_menu').height() > 50 || $('#main_menu').width() > $(window).width() * 0.75)
$('#main_menu').append('<li><span id="m_more"></span><h4>' + $txt['more'] + '</h4><ul></ul></li>');
while ($('#main_menu').height() > 50 || $('#main_menu').width() > $(window).width() * 0.75)
$('#main_menu > li:last').prev().prependTo($('#main_menu > li:last > ul')).find('h4').contents().unwrap().parent().find('>span').remove();This has the amusing effect of ensuring that the main menu only takes one line, and each entry beyond that will be moved to a dynamic menu entry at the end. Basically, it behaves like phpMyAdmin and a couple other scripts. I wrote the code myself though, dunno how they 'do it', but since their CSS is probably very different, it doesn't matter...
Anyway, I thought it was cool that I managed to do it in only 4 lines (2 of which compressing as one...), and of course it executes pretty quickly, but I'm not super-happy with the 'more' menu though...
- Main menu doesn't support icons in its entries; well, it does, but it doesn't look pretty... So I removed the icons for consistency, but it could be fixed by CSS.
- Need to add a 'subsection' class to all child LI's, so that we get a horizontal arrow...
- I've set the maximum width to 75% of the window size, so that we can see the sub-menus entirely. Ideally, thought, I should rewrite my main menu code to show the drop-down on the left of its parent, rather than its right, when its width extends beyond the window bounds... I already did that a few weeks ago for the select box rewrite, didn't I..?
- Probably should wrap this into a resize event, so it gets updated when the window is resized, but that also means adding more code to move the submenus to the top, and... MEH.
What do you think of this?
Here's what it looks like:
2950
Bug reports / Re: Raw HTML in Custom Profile Fields
« on May 25th, 2013, 02:48 PM »Most (if not all) people using images in the options will treat them as icons. That said, I think the height should be elastic, jut like the width.Quote There is a separate side bug related to the selectbox. I have a piece of text with an image that's substantially bigger than a single line of text. It was the first image at hand, and was 40x40. When the selectbox is expanded, it is displayed normally. But when closed and it is the selected item, something else happens entirely. See attached. The picture shows both the expanded behaviour and the unexpanded behaviour (i.e. it doesn't change height, and the text is base-line aligned, so the text is actually out of sight)
I spent weeks, perhaps months on this select box rewrite... I'm proud of it, but I'm perfectly aware it has a few shortcomings.
Yet, I'm not ready to... Delve into that again..! :^^;:
2951
Features / Re: Plugin revs
« on May 25th, 2013, 02:36 PM »
rev 86
(3 files, 3kb)
+ Adding old_urls plugin to the repo. I thought it was already done..?! (old_urls/*)
(3 files, 3kb)
+ Adding old_urls plugin to the repo. I thought it was already done..?! (old_urls/*)
2952
Features / Re: Plugin revs
« on May 25th, 2013, 02:21 PM »
rev 85
(32 files, 15kb)
* Updated to new parse_bbc format. (edit_history/EditHistory.php, max_smileys/MaxSmileys.php, word_limits/WordLimits.php, wedgedesk/src/Subs-WedgeDesk.php, Subs-WedgeDeskPost.php, WedgeDesk-AdminCustomField.php, WedgeDesk-Display.php, WedgeDesk-Post.php, WedgeDesk-TicketGrids.php)
* Updated auto-suggests. (wedgedesk/tpl/WedgeDesk-AdminMaint.template.php, WedgeDesk-Post.template.php, WedgeDesk-Search.template.php)
- Unused $db_prefix. (calendar/CalendarSSI.php)
- Removed simple permissions from a few plugins. I did it semi-automatically by searching for _simple_, so it's likely there are some remnants in the files..? (Language files)
* French translation. (Topic Solved language files)
* French grammar. (calendar/lang/Calendar.french.php, calendar/lang/ManageCalendar.french.php, skin_selector/SkinSelector.french.php, users_online_today/OnlineToday-Admin.french.php)
* Vade retro, Array.prototype... ;) (wedgedesk/js/helpdesk.js)
* Vade retro, ending tags... Only updated a few language files, from Topic Solved and WedgeDesk.
(32 files, 15kb)
* Updated to new parse_bbc format. (edit_history/EditHistory.php, max_smileys/MaxSmileys.php, word_limits/WordLimits.php, wedgedesk/src/Subs-WedgeDesk.php, Subs-WedgeDeskPost.php, WedgeDesk-AdminCustomField.php, WedgeDesk-Display.php, WedgeDesk-Post.php, WedgeDesk-TicketGrids.php)
* Updated auto-suggests. (wedgedesk/tpl/WedgeDesk-AdminMaint.template.php, WedgeDesk-Post.template.php, WedgeDesk-Search.template.php)
- Unused $db_prefix. (calendar/CalendarSSI.php)
- Removed simple permissions from a few plugins. I did it semi-automatically by searching for _simple_, so it's likely there are some remnants in the files..? (Language files)
* French translation. (Topic Solved language files)
* French grammar. (calendar/lang/Calendar.french.php, calendar/lang/ManageCalendar.french.php, skin_selector/SkinSelector.french.php, users_online_today/OnlineToday-Admin.french.php)
* Vade retro, Array.prototype... ;) (wedgedesk/js/helpdesk.js)
* Vade retro, ending tags... Only updated a few language files, from Topic Solved and WedgeDesk.
2953
Archived fixes / Re: Mentions in post are not showing correctly
« on May 25th, 2013, 01:53 PM »
It wasn't a bug actually, only a wrong manipulation on my side...
I'd emptied, a few days ago, the bbcode table to (more easily) integrate my recent changes, and forgot to disable then re-enable the mentions plugin, which added its own tag to the list...
I'd emptied, a few days ago, the bbcode table to (more easily) integrate my recent changes, and forgot to disable then re-enable the mentions plugin, which added its own tag to the list...
2954
Archived fixes / Re: Multiple Same-Name Selection Box When Notifying
« on May 24th, 2013, 11:38 PM »
So... The latest changes:
- using auto-suggest minChars to determine minimum number of chars to type, in the case of wedge.org this is set to 2 characters. (It will, in the future, be set to 3 characters, because we're bound to have more members... I guess? I hope? I hope not..?)
- pressing Backspace while the dropdown is opened and we already were at the minimum number of characters allowed, will close said dropdown. Pressing the Left arrow in the same situation will do the same.
- moving Up in the dropdown will eventually wrap to the last item (previously, it just stopped at the first.)
I hope you like it, guys... ;)
It's not finished yet, but will be soon.
- using auto-suggest minChars to determine minimum number of chars to type, in the case of wedge.org this is set to 2 characters. (It will, in the future, be set to 3 characters, because we're bound to have more members... I guess? I hope? I hope not..?)
- pressing Backspace while the dropdown is opened and we already were at the minimum number of characters allowed, will close said dropdown. Pressing the Left arrow in the same situation will do the same.
- moving Up in the dropdown will eventually wrap to the last item (previously, it just stopped at the first.)
I hope you like it, guys... ;)
It's not finished yet, but will be soon.
2955
Features / Re: New revs
« on May 24th, 2013, 11:10 PM »
rev 2133 -- I really, really wanted to commit all of this now... Even though I'm quite ashamed of how I implemented the first feature in the list... :(
(22 files, 7kb)
+ Added more flexibility to auto-suggest popups, by determining the minimum applicable characters depending upon the number of members of your forum. It may seem like nothing, but on smaller forums, when you're typing 'Nao' and it only suggests me after you type those three letters, it just seems silly... The number of members I determined is arbitrary, feel like to change it. Even the function name, and the way it's used in auto-suggests, can be changed to whatever one feels works best... Really, I'm not fussed. Feel free. Have a drink and tell me what you want. (ManageBans.php, Aeva-Gallery2.php, ManageMedia2.php, Subs.php, ManageBoards/Maintenance/Membergroups/News/Paid.template.php, Media.template.php, PersonalMessage.template.php, Profile.template.php, pm.js, suggest.js)
* Renamed wePersonalMessageSend() to weSendPM()... Seriously, I don't know how it managed to survive with that name for so long... And the object creation also had a left-over unused param. (PersonalMessage.template.php, pm.js)
* Renamed url-no-base64() to raw-url(). While no-base64 is easy to understand for developers, it might not be for themers, so I thought it best to just use plain regular English. Behavior is the same. (Class-CSS.php, Subs-Cache.php, common.css, index.css, index.member.css, mana.css, sections.css)
* Tweaked error box padding. Again. This time it's for the main post page... (sections.css)
* Translation. (index.french.php)
(22 files, 7kb)
+ Added more flexibility to auto-suggest popups, by determining the minimum applicable characters depending upon the number of members of your forum. It may seem like nothing, but on smaller forums, when you're typing 'Nao' and it only suggests me after you type those three letters, it just seems silly... The number of members I determined is arbitrary, feel like to change it. Even the function name, and the way it's used in auto-suggests, can be changed to whatever one feels works best... Really, I'm not fussed. Feel free. Have a drink and tell me what you want. (ManageBans.php, Aeva-Gallery2.php, ManageMedia2.php, Subs.php, ManageBoards/Maintenance/Membergroups/News/Paid.template.php, Media.template.php, PersonalMessage.template.php, Profile.template.php, pm.js, suggest.js)
* Renamed wePersonalMessageSend() to weSendPM()... Seriously, I don't know how it managed to survive with that name for so long... And the object creation also had a left-over unused param. (PersonalMessage.template.php, pm.js)
* Renamed url-no-base64() to raw-url(). While no-base64 is easy to understand for developers, it might not be for themers, so I thought it best to just use plain regular English. Behavior is the same. (Class-CSS.php, Subs-Cache.php, common.css, index.css, index.member.css, mana.css, sections.css)
* Tweaked error box padding. Again. This time it's for the main post page... (sections.css)
* Translation. (index.french.php)