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
2866
Other software / Re: SMF with a different name, huh?
« on June 7th, 2013, 07:55 PM »
I think he meant, "it's SMF, [except for] a few [extra] minor features."
He's not smart, but he's not a troll either. :p
He's not smart, but he's not a troll either. :p
2867
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 07:48 PM »
So...
Ajax version: still getting errors on every page if I attempt to load the entire page (apparently, internal $.each call is broken), but user mini-menus work; if I just request the post list, no JS works, but everything else does.
Iframe version: consistently getting the same cross-origin error when the embedded page also has an embedded iframe. Can't seem to solve it, and it looks like no one has it on google. I tried commenting out the x-frame-origine stuff, to no avail. Other than media embeds, I'm getting it to work without JS errors; it's complicated to remove the surrounding tags, though (and messy), and even when I manage to, I'm stuck with html and body tag stylings that don't match the parent div. So, in addition, I'll have to reset background styling on these tags, and try to make the iframe transparent (I think it's possible). One last (big!) issue is that the iframe's height is calculated after .load(), but even though it's enough to account for images being loaded, it doesn't seem to take iframes into account, or something... Anyway, as a result, sometimes the iframe doesn't have the correct height.
As you can see, I'm quite... stuck, at this point. I don't know which direction to go, and I don't know if it's worth the hassle. I guess it is, but it's frustrating when you managed to cook up an Ajax scroller in a couple of hours, and then you spend the next day rewriting it over and over, without ever managing to get it to run flawlessly.
F*ck.
Ajax version: still getting errors on every page if I attempt to load the entire page (apparently, internal $.each call is broken), but user mini-menus work; if I just request the post list, no JS works, but everything else does.
Iframe version: consistently getting the same cross-origin error when the embedded page also has an embedded iframe. Can't seem to solve it, and it looks like no one has it on google. I tried commenting out the x-frame-origine stuff, to no avail. Other than media embeds, I'm getting it to work without JS errors; it's complicated to remove the surrounding tags, though (and messy), and even when I manage to, I'm stuck with html and body tag stylings that don't match the parent div. So, in addition, I'll have to reset background styling on these tags, and try to make the iframe transparent (I think it's possible). One last (big!) issue is that the iframe's height is calculated after .load(), but even though it's enough to account for images being loaded, it doesn't seem to take iframes into account, or something... Anyway, as a result, sometimes the iframe doesn't have the correct height.
As you can see, I'm quite... stuck, at this point. I don't know which direction to go, and I don't know if it's worth the hassle. I guess it is, but it's frustrating when you managed to cook up an Ajax scroller in a couple of hours, and then you spend the next day rewriting it over and over, without ever managing to get it to run flawlessly.
F*ck.
2868
Other software / Re: SMF with a different name, huh?
« on June 7th, 2013, 07:42 PM »
Hmm... So the guy was Shawn?
I just wanna say... Who cares? You were the only one who ever cared about his forum; after he got into a fight with you (and he threw a tantrum at me for removing him from my Facebook friends long before that, as I was uncomfortable with his political views...), there never was any reason to give him to credit, or attention for that matter.
You're being way too sensitive about that, Pete ;)
Although he's right, we've done nothing more than SMF did in the last 3 years! After all... THEY ADDED A WIKI! We didn't! Hail! Hail!
(But what a wonderful waste of time for us :cool:)
I just wanna say... Who cares? You were the only one who ever cared about his forum; after he got into a fight with you (and he threw a tantrum at me for removing him from my Facebook friends long before that, as I was uncomfortable with his political views...), there never was any reason to give him to credit, or attention for that matter.
You're being way too sensitive about that, Pete ;)
Although he's right, we've done nothing more than SMF did in the last 3 years! After all... THEY ADDED A WIKI! We didn't! Hail! Hail!
(But what a wonderful waste of time for us :cool:)
2869
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 06:42 PM »
This probably won't happen with the iframe version, though.
2870
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 04:50 PM »I was kind of hoping you were building it via the msg skeleton so it could serve arbitrary slices of topics...
- in index.template.php, I added a span with a class, around the 'Next page' link. (You can see it here, too.)
- in QueryString.php, I added a failsafe to disable the AJAX constant if specifically requested from the Ajax caller, (I think I'll keep this one in, regardless of what I choose to do later...)
- then, in topic.js, I'd just do an Ajax request to get the next page, and retool it to just keep the #forumposts content (also removing the form tag if it was in there, although I'm not sure it was necessary.)
That's really all it took, and the second step is not needed in the iframe version.
If you're pulling the full page and manipulating it there and then, surely you can just run any other JS at that point in time?
I dunno, bit pissed off and a bit frazzled from the search crap right now :(
2871
Archived fixes / Re: Thoughts colloring error
« on June 7th, 2013, 04:44 PM »
Ah... Yes, confirmed! Silly-silly-silly-me! :lol:
2872
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 04:33 PM »Yeah, the nesting thing is a security thing to limit people pulling in things they shouldn't. The only way really is not to nest iframes. Or indeed not use iframes if at all possible :/
The advantage of the iframe, is that I really don't have to fear any JavaScript changes in the future will break the feature, and to me that made the deal; hence, my disappointment with the YT thing.
Surely the secondary load (page 2 or whatever) knows it's loaded via AJAX...
The second draft, being done through an iframe, isn't loaded through AJAX at all, it's really just a regular page load... ;) (Which I'm then manipulating afterwards, to remove stuff from it, and update the pagesection area to get the proper page numbers.)
so it just needs to include the code for calling the menu for the items in question...
the menu constructor plus main data (what buttons are available) will already be loaded so it's just a case of submitting the extra menu data and some glue, right?
For instance, let's just think about a per-post non-mini-menu JS snippet that's rendered through a plugin. How do I tell the plugin, "okay I've loaded the next page, now do your thing"...? I can't, not really.
So, the iframe solution, really is the only 'realistic' solution right now.
(Did anyone notice my recent tendency to, ahem, use commas everywhere, even when not needed..? It's an impulse, and I don't now where it came from, please help me, please, really, I'm sick of it, honest.)
,
2873
Archived fixes / Re: Thoughts colloring error
« on June 7th, 2013, 04:25 PM »Should be fixed in r2158. If you'll notice, it's not that the link is not coloured, it is actually pointing to the wrong page entirely. (And because it's the wrong link, it gets the wrong colouring.)
What's happening is that it was pulling the parent thought's owner as the child thought's owner id and building the link off that even though it has the right name to work off (because *that* join is correct)
2874
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 04:16 PM »
Well, as I said, I have a solution, but it's complicated too... I'm now using an iframe (ouch). This is the only way to get scripts to work in both the parent page, and its children. I've tested it to work. Unfortunately, I'm having trouble getting rid of everything outside of the post list (either it works, and I lose scripts again, or I just get an empty iframe, and sometimes even -- a page with everything, BUT the posts :lol:), but it's probably a jQuery issue, rather than something I just can't do. I'm taking my lunch break, and I'll see later.
Also, I'm having trouble with a detail... I'm getting errors with YouTube videos in iframes. Apparently, iframes within iframes... You've got to be careful of what domain you're using. Or something. I don't know how to fix that one, for now... :-/
Posted: June 7th, 2013, 02:06 PM
Also, I'm having trouble with a detail... I'm getting errors with YouTube videos in iframes. Apparently, iframes within iframes... You've got to be careful of what domain you're using. Or something. I don't know how to fix that one, for now... :-/
2875
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 12:03 PM »
Topic list, yeah, I wanted to give it a try too, so I didn't build in in-topic restrictions to my code; but in the meantime, I decided to focus on topics only, and I forgot to add a restriction.
Also, there's a huge problem with this feature, and I'm surprised no one noticed it. I actually didn't reproduce it until a few minutes ago, and I barely slept last night because I kept thinking this must be buggy!, and yes, unfortunately it was...
Thing is, the JS is broken in new posts added through infinite scrolling.
Reason is that the new page's JS is thrown away, instead of added to the current footer. I'm trying to consider things to fix that, but if I can't, it means I can't have both 'optimized-bytesize' mini-menus and infinite scrolling in Wedge, and I'll have to rewrite mini-menus, or something...
Hard day ahead... -_-
So... I tried multiple solutions for this problem, and it didn't work.
Anyway-- I'm currently rewriting the code, nearly from scratch, and this time it should work. It's not as elegant as the current implementation, but what matters is that it works, hell...
Also, there's a huge problem with this feature, and I'm surprised no one noticed it. I actually didn't reproduce it until a few minutes ago, and I barely slept last night because I kept thinking this must be buggy!, and yes, unfortunately it was...
Thing is, the JS is broken in new posts added through infinite scrolling.
Reason is that the new page's JS is thrown away, instead of added to the current footer. I'm trying to consider things to fix that, but if I can't, it means I can't have both 'optimized-bytesize' mini-menus and infinite scrolling in Wedge, and I'll have to rewrite mini-menus, or something...
Hard day ahead... -_-
Posted: June 7th, 2013, 08:31 AM
So... I tried multiple solutions for this problem, and it didn't work.
Anyway-- I'm currently rewriting the code, nearly from scratch, and this time it should work. It's not as elegant as the current implementation, but what matters is that it works, hell...
2876
The Pub / Re: Infinite Scroll
« on June 7th, 2013, 01:43 AM »
Yup, as intended...
Although I'd really like to make it work on mobile.
Okay, I'm over bed time by 2 hours, so it's time to go... Please guys, give some feedback... ;) I'm surprised only Lorenzo is interested in this..?
Although I'd really like to make it work on mobile.
Okay, I'm over bed time by 2 hours, so it's time to go... Please guys, give some feedback... ;) I'm surprised only Lorenzo is interested in this..?
2877
Plugins / [Plugin] Re: Notifications system (1.0)
« on June 6th, 2013, 11:28 PM »
You're talking about e-mails..?
- Color: that's logical, since you rewrote it to use classes for groups, instead of styles. The only way to fix, would be to have an alternate codepath where we do the old-school rewrite, but I don't know if it's worth it...
- We're still sending e-mails in text format, not HTML, so we still have <a ...> links, instead of text links.
- My local install has an alternative version, which at least fixes URLs to prevent them from being cut off (and, of course, goes through ob_sessrewrite in the e-mail parser). I have yet to commit it, because... Well, it's only worth it, if we're sending HTML...
- Color: that's logical, since you rewrote it to use classes for groups, instead of styles. The only way to fix, would be to have an alternate codepath where we do the old-school rewrite, but I don't know if it's worth it...
- We're still sending e-mails in text format, not HTML, so we still have <a ...> links, instead of text links.
- My local install has an alternative version, which at least fixes URLs to prevent them from being cut off (and, of course, goes through ob_sessrewrite in the e-mail parser). I have yet to commit it, because... Well, it's only worth it, if we're sending HTML...
2878
The Pub / Re: Infinite Scroll
« on June 6th, 2013, 11:22 PM »
And... Here we go!! ;)
And it doesn't work, lol. Gimme a minute to check it...
Voilà, should work now!
Posted: June 6th, 2013, 11:21 PM
And it doesn't work, lol. Gimme a minute to check it...
Posted: June 6th, 2013, 11:22 PM
Voilà, should work now!
2879
The Pub / Re: Infinite Scroll
« on June 6th, 2013, 10:17 PM »
So, a bit late, but just to tell you guys -- I've started working on this... ;)
This is only for topics, nothing else.
Right now, what's happenin' is that it's working (yay). I have yet to deal with URLs, though, but it seems to be doing fine otherwise.
It won't work on mobile (for now), because I'm doing my tests on the mousewheel event, rather than scroll. Why? Because the scroll event doesn't trigger if you try to scroll beyond the end of a page, it only triggers if there's movement in the page. The mousewheel event thus allows me to 'cancel' any Ajax loading until a few more wheel attempts, indicating that we 'really' want to load the next page of the topic, and that's it..
Anyway, pretty happy with what I've done, but it's no fun to test when you have a huge debug log at the bottom of the page, it means I don't get to see the effect of adding posts... :lol:
This is only for topics, nothing else.
Right now, what's happenin' is that it's working (yay). I have yet to deal with URLs, though, but it seems to be doing fine otherwise.
It won't work on mobile (for now), because I'm doing my tests on the mousewheel event, rather than scroll. Why? Because the scroll event doesn't trigger if you try to scroll beyond the end of a page, it only triggers if there's movement in the page. The mousewheel event thus allows me to 'cancel' any Ajax loading until a few more wheel attempts, indicating that we 'really' want to load the next page of the topic, and that's it..
Anyway, pretty happy with what I've done, but it's no fun to test when you have a huge debug log at the bottom of the page, it means I don't get to see the effect of adding posts... :lol:
2880
Features / Re: New revs
« on June 6th, 2013, 07:49 PM »
rev 2155
(5 files, 2kb)
! Fixed wrong transparency values on avatars that are uploaded to a custom folder. Another waste of an afternoon... Why are there so many ways to use avatars, uh? (Class-System.php, Load.php)
- Removed unused getIcon() definitions. (notifiers/Likes.php, notifiers/Move.php)
* Small tweaks to notification avatar layout. (index.css)
(5 files, 2kb)
! Fixed wrong transparency values on avatars that are uploaded to a custom folder. Another waste of an afternoon... Why are there so many ways to use avatars, uh? (Class-System.php, Load.php)
- Removed unused getIcon() definitions. (notifiers/Likes.php, notifiers/Move.php)
* Small tweaks to notification avatar layout. (index.css)