Author Topic: [WIP] Breeze (Read 31573 times)

Marcus Forsberg · « **Reply #40 on:** April 08, 2012, 11:58:01 AM »

Btw, are you planning to provide any fallbacks for users with JS turned off (aka idiots)? It just hit me and I had to try it out, and it doesn't work very well at all. Now, I fully support you *not* providing fallbacks since anyone with JS turned off should burn to death anyhow. I'm just curious

Suki · « **Reply #41 on:** April 08, 2012, 12:12:11 PM »

That's an interesting question and I haven't thought about it.

I guess I am already excluding a lot of users who don't use php 5.3 or even SMF 2.0, I suppose excluding those with JS off is just another stripe on the tiger

The issue with including a fallback is that I already wrote a lot of php code around jQuery instead of the other way around $:-\$

Marcus Forsberg · « **Reply #42 on:** April 08, 2012, 12:17:18 PM »

I see what you mean. I really wouldn't worry about it at this point. When I was working on SimpleNetwork I first wrote a non-AJAX version and then added AJAX on top of it but eventually it became a PITA to manage. That was a clear mistake, it's better to do it JS-only like you do; no use dwelling in the past.

Suki · « **Reply #43 on:** April 08, 2012, 12:28:09 PM »

It may be worth to include some kind of message or just disable the entire mod if js is off, the problem is to find a good way to be able to detect when js is off, maybe with a cookie but that's not 100% effective.

Perhaps just provide the very basic functionality, to post new status/comments and that's it.

Marcus Forsberg · « **Reply #44 on:** April 08, 2012, 12:34:02 PM »

Yeah, and it should be fairly simple to include that basic functionality. You could even reuse the function you have (accessed through ?action=breezeajax, is it?). Just have it check if $_REQUEST['js'] is set, and if it is, keep going just as usually, and if it's not, do the posting and then redirect back to the profile instead of outputting the post body and all that. I dunno, just the first thing that came into my mind.
You obviously know exactly how to handle it without my help

Suki · « **Reply #45 on:** April 08, 2012, 12:40:20 PM »

Oh, that's a pretty good and simple solution

To pass a new var with jQuery, if that var doesn't exists then it means JS is off or something happen while loading jQuery, either way, it means we have to do it the good old way.

Cool, gonna implement that, thanks.

Marcus Forsberg · « **Reply #46 on:** April 08, 2012, 01:15:18 PM »

Do have fun

Labradoodle-360 · « **Reply #47 on:** April 08, 2012, 01:59:38 PM »

That is the nice thing about AJAX in general, it shouldn't be that hard to make a work-around for non-JS users.

ahrasis · « **Reply #48 on:** April 16, 2012, 08:33:09 PM »

Nice work Suki. It sure feels like a breeze. Keep it up.

Suki · « **Reply #49 on:** May 11, 2012, 01:38:23 PM »

OK, this isn't dead yet, I just haven't have any desire to do anything lately.

I'm working on it right now, mostly tweaks here and there, changing the hard coded stuff with vars, naming stuff and putting all together so it can really be OOP instead of a bunch of independent classes.

Is going to take a while, thats for sure, but I guess is OK, it appears that this is something not that popular/acclaimed so I can work on it at my own time and take as much time as needed

Labradoodle-360 · « **Reply #50 on:** May 11, 2012, 02:01:54 PM »

I was actually just wondering about this yesterday

Marcus Forsberg · « **Reply #51 on:** May 12, 2012, 01:26:58 AM »

I do think this will be quite popular, it's just that people don't really look at this board that much.

Looking forward to the updates.

GQCritic · « **Reply #52 on:** May 12, 2012, 04:10:15 AM »

I agree.

This will be a wonderful modification.

Keep up the good work!

emanuele · « **Reply #53 on:** May 17, 2012, 08:15:16 AM »

I noticed that on your site the urls of the pages are wrong.
Wall homepage:

Code: [Select]

http://missallsunday.com/profile/suki_1/current link to second page:

Code: [Select]

http://missallsunday.com/profile/page.2/correct link to the second page:

Code: [Select]

http://missallsunday.com/profile/suki_1/page.2/don't know if you already fixed it.

HTH!

Suki · « **Reply #54 on:** May 17, 2012, 10:14:05 AM »

Yeah, is the pagination class and it's hard-coded base url. Haven't had the time to fix it, been busy breaking what was already done

emanuele · « **Reply #55 on:** May 17, 2012, 12:58:11 PM »

lol

I are not supposed to learn from me!

Groovystar · « **Reply #56 on:** May 17, 2012, 02:13:03 PM »

*tracks*

This is something very similar to a custom job I'm looking to get done. Will keep an eye on it!

Suki · « **Reply #57 on:** July 13, 2012, 10:52:14 PM »

OK this isn't forgotten, far from that.

I've been busy doing lots of commits lately, I haven't really added any new feature but I did re-write this thing from scratch, now that I'm happy with how things are I can finally concentrate on new features.

I hope I can have a beta with full notification support sometime soon, then I can work on the general wall and some other interesting stuff.

Suki · « **Reply #58 on:** August 09, 2012, 05:30:41 PM »

OK, finally done with the whole mention and notification thing...

Pretty much works as follows: somebody types {username} for example: {Suki}

When saving the message, it gets preparsed, the name goes from this: {Suki} to this: {245528,Suki,Suki}

Where:

245528 is the user ID
Suki is the displayed name
Suki is the real name do note that a lot of users don't have the same displayed name this was done this way to actually allow using both names for mentions.

Now the message gets stored and the parser class can build a link to the user's wall without having to query the database everytime the message get's parsed.

I also implemented a basic buddy system with approval/reject, this is tided up with the notification system, when some user marks you as his/her buddy, a notification will be created and you will decide if you want to approve this or not, if this gets approved, a pm to the user is sent to let her/him know about it.

It is stable enough to be used on a test site, however, it is far from finished, there are a lot of stuff, mostly UI stuff, that I need to implement.

I want to write a plugin/hook system to easily add user settings without having to rewrite the BreezeUser file.

Need to do a lot of testing, some things were coded to just work (the permission system, the admin settings, the admin page) without taking in consideration any details.

I also want to change how the stuff gets loaded (should be very easy to do, now is when OOP really shows its potential), it currently loads a huge array with all the data, I just discovered that it is faster to just split the data by user and build a cache for every user.

I really need to finish this, on next September this mod will be 1 year old, it's been nice but at the same time I need to focus on other things as well. So, the general wall, gallery, like system and extending the notification system to other parts of the forum will just have to wait for a next version.

So, anyway, if anyone is interested on Beta testing, feel free to download the zip at https://github.com/MissAllSunday/Breeze (Master branch), it should be ready to install and use but be aware, this is not ready for a production site yet!

If anyone is interested on helping out, the develop branch is where I do all the development, keep in mind this branch has unstable code and lots of errors/bugs, only when the code is stable enough it gets merged to Master branch.

Oh, I already know the codename for the 1.0 version: Windmill

Mstcool · « **Reply #59 on:** August 11, 2012, 11:59:32 AM »

Can you make it more into the one like VB
Like the view convo between these 2 kind of stuff?

News:

Author Topic: [WIP] Breeze (Read 31573 times)