Yootil 1.1.2 [Updated: 8th Dec, 2018]

[Peter]

Yootil

Yootil is a utilities library to help speed up development of plugins for developers.

The word "Yootil" was created from the abbreviation "Util".

"Util" is an abbreviation for "utilities" ("Yoo'ti-lu-tee").

---

Plugin Install / Download

Library: www.proboards.com/library/plugins/item/38

Tip: Move the Yootil plugin to the top of your plugin list.

---

Plugin Source / Docs / Updates

Project: github.com/PopThosePringles/ProBoards-Yootil
Docs: pixeldepth.net/proboards/plugins/yootil/

----
1.1.2
- Change encoding / decoding method

1.1.1
- Fixed Queue not nullifying the internal interval property

1.1.0
- Improved some selectors.
- Added yootil.suffix method
- Added yootil.month method
- Added yootil.day method
- Added yootil.get.messages method
- Added yootil.get.user_messages method
- Added yootil.remove.messages method
- Added yootil.remove.user_messages method
- Removed yootil.sound completely now
- Plugin bar has been reworked and no longer relies on the PB Bar. New options to position it.

1.0.0
- Removed updater (shows the admin when there is an update available).
- Removed deprecated call to ProBoards API.
- Changed the way key.set works to match the ProBoards API.
- Notifications class added (see docs on how to use).
- Fixed strict equality due to type changes (mixed types in the hash, they used to be strings).
- Added yootil.forum class (see docs).
- "can_write" and "can_read" returns true for now. These will work automatically again when PB exposes them.
- Sound module has be deprecated, I don't think this is really needed, and there are better libraries out there for sound.
- Added yootil.version().
- Fixed yootil.create.container if "safe" parameter was used. No longer throws an error.
- yootil.element.get added + quite a few methods (yootil.get alias).
- yootil.element.remove added + quite a few methods (yootil.remove alias).
- Key module basically redone plus some new methods.
- yootil.create.ubbc_tab added.
- yootil.location.check is deprecated, it is now an alias for yootil.location.
- Lots of other changes and improvements.
- yootil.ajax is now yootil.event (.ajax is an alias now).
- Some events added (post_liked, user_searched, bookmarked_thread, and a few more).
- Documentation rewrite.

0.9.9
New location checks and small additions

0.9.8
Sound rewrite (HTML 5 only)

0.9.7
Fixed the plugin bar for Forums.net customers

0.9.6
Bug fix - user data null error

0.9.5
Fixed alt / title not showing up for icons in the Yootil Bar

0.9.4
Update message still showing when disabled

0.9.3
Yootil bar not showing

0.9.2
Caching of the route

0.9.1
Bug fix to the updater

0.9.0
All code moved inside plugin
Settings

0.8.17
Queue class
yootil.location.check.profile()
yootil.create.profile_tab()
yootil.create.profile_content_box()

0.8.16
Stats collection

0.8.15
Library plugin wasn't compressed

0.8.14
Updated plugin to match version number

0.8.13
yootil.outer_html added

0.8.12
yootil.form.edit_post_form added

0.8.11
yootil.page.member added

0.8.10
New methods added to the Yootil.bar class

0.8.9
Storage get method bug in Chrome

0.8.8
Yootil.bar now has to 2 params so that you can pass a function and context

0.8.7
Yootil.bar display check bug fixed thanks to Stinky666

0.8.6
Yootil.bar added

0.8.5
pad added to yootil class
user methods added to user class (includes all new user properties from proboards.data("user"))

0.8.4
after_search method added to AJAX class.

0.8.3
page.thread added by Xikeon

0.8.2
Storage changes, docs, and fixes.

0.8.1
Storage class bug fixes

0.8.0
Storage class completely rewrote, now supports session and persistent storage

0.7.3
user.action.created_conversation()
user.action.pmed()
user.action.sent_message()

0.7.2
nav_branch added to create class

0.7.1
read / write methods for keys added

0.7.0
Add page, page.category, and page.board classes

0.6.3
"recent_posts" location check added to "all_recent_posts"

0.6.2
- Couple of new location checks to do with messages / conversations
- New form class added to get specific forms quickly

0.6.1
- Added editing location checks: editing_post, editing_thread, and editing

0.6.0
- Storage object added (yootil.storage)

0.5.0
- yootil.location.check added
- yootil.location added
- yootil.user.action added
- Changed compression to Uglify

0.4.0
- yootil.user object added

0.3.0
- create.page method added

0.2.5
- Removed hijack method, no need for it as we can bind to the "success" event for AJAX lists

0.2.4
- Fixed an issue with yootil.number_format returning an empty string.

0.2.3
- Removed yootil.form (use proboards validated event)
- Fixed some issues with getting values from keys when specifying a user of null / false

0.2.2
- Removed yootil.debug (kept finding myself using console.log anyway)

0.2.1
- Remove extra blank rows and reduced size of comments in header

0.2
- Changed YOOTIL to yootil
- yootil.proboards.create is now yootil.create

[Jordan]

Very nice, I think this is a really good idea and you have a lot of useful methods such as those for ajax callbacks, forms, and key manipulation. I'll start using this.

The name is a little funky, though.

[Peter]

Nov 1, 2012 12:20:13 GMT -8 Jordan said:

Very nice, I think this is a really good idea and you have a lot of useful methods such as those for ajax callbacks, forms, and key manipulation. I'll start using this.

The name is a little funky, though.

Yeah, couldn't think of a name, so shoved some words into my word app relating to "utilities", the app also has the spelling for how you pronounce it, which was "Yoo'ti-lu-tees", so I took the first part of that lol.

It's unique, couldn't find a JS library on the net with it

Though if you have something better and not any bigger, do suggest away

[Jordan]

PBUTIL

[Peter]

Have removed yootil.debug, kept finding myself using "console" anyway.

[Peter]

Updates added to the first post.

"validated" method removed, no need to hook into this now, as we have a "validated" event.

[Chris]

Peter: I haven't had a chance to look through this yet, but I'd like to suggest a few methods (that I'd gladly write). These methods are all state-based in regards to the website.

user.justPosted(): Returns true if the user has just posted at all
user.justCreatedThread(): Returns true if the user has just created a thread
user.justReplied(): Returns true if the user has just replied to a thread

Obviously there are more combinations of these possible, but this allows us to do something like this:
if(user.justCreatedThread()){
// Code here to show an "add label" menu
}

I'd find them useful, and this way we create a globally useful set that all coders can tweak and improve over time.

[Xikeon]

I wouldn't be surprised if Peter has been working on that. His money plugin was basically a prototype test for hooks on form submits after posting, creating threads and editing posts. If I remember correctly he was now using the "ajax hook", to hook to the form's complete.

[Peter]

Nov 3, 2012 18:22:47 GMT -8 Chris said:

Peter: I haven't had a chance to look through this yet, but I'd like to suggest a few methods (that I'd gladly write). These methods are all state-based in regards to the website.

user.justPosted(): Returns true if the user has just posted at all
user.justCreatedThread(): Returns true if the user has just created a thread
user.justReplied(): Returns true if the user has just replied to a thread

Obviously there are more combinations of these possible, but this allows us to do something like this:
if(user.justCreatedThread()){
// Code here to show an "add label" menu
}

I'd find them useful, and this way we create a globally useful set that all coders can tweak and improve over time.

Would you be happy to come on board and become a member of the project?

I will create an SVN rep, and allow you to commit to it.

I know your ability, and feel comfortable having you applying commits to it.

If not, feel free to write your methods, and I'll drop them in.

[Peter]

Nov 4, 2012 2:22:45 GMT -8 Xikeon said:

I wouldn't be surprised if Peter has been working on that. His money plugin was basically a prototype test for hooks on form submits after posting, creating threads and editing posts. If I remember correctly he was now using the "ajax hook", to hook to the form's complete.

You are right, I did start to write similar methods to what Chris suggested, but I ditched them for the moment until we know what's happening with the current ProBoards API, as things will likely get tweaked.

But Chris, feel free to write them, I removed mine, they weren't fully wrote out and tested, so please go ahead

[Chris]

Nov 4, 2012 8:23:01 GMT -8 Peter said:

Nov 3, 2012 18:22:47 GMT -8 Chris said:

Peter: I haven't had a chance to look through this yet, but I'd like to suggest a few methods (that I'd gladly write). These methods are all state-based in regards to the website.

user.justPosted(): Returns true if the user has just posted at all
user.justCreatedThread(): Returns true if the user has just created a thread
user.justReplied(): Returns true if the user has just replied to a thread

Obviously there are more combinations of these possible, but this allows us to do something like this:
if(user.justCreatedThread()){
// Code here to show an "add label" menu
}

I'd find them useful, and this way we create a globally useful set that all coders can tweak and improve over time.

Would you be happy to come on board and become a member of the project?

I will create an SVN rep, and allow you to commit to it.

I know your ability, and feel comfortable having you applying commits to it.

If not, feel free to write your methods, and I'll drop them in.

How do you feel about git? Been using that a lot recently and I think branching might work out nicely for this. With Github, it also lets us do pull requests easily, so we can have other PB members commit.

I'd also look at standard location check methods:

isPostingPage()
isBoardPage()

Even if their code is this right now:

var isPostingPage = function(){
return pb_action == "post";
};

Doing that would make it easy to update if PB changes.

Anyways, yeah, totally interested. Take this to PM maybe?

[Peter]

New details added to the first post.

Includes updated URLs for the project.

[Peter]

Nov 4, 2012 10:10:15 GMT -8 Chris said:

Nov 4, 2012 8:23:01 GMT -8 Peter said:

Would you be happy to come on board and become a member of the project?

I will create an SVN rep, and allow you to commit to it.

I know your ability, and feel comfortable having you applying commits to it.

If not, feel free to write your methods, and I'll drop them in.

How do you feel about git? Been using that a lot recently and I think branching might work out nicely for this. With Github, it also lets us do pull requests easily, so we can have other PB members commit.

I'd also look at standard location check methods:

isPostingPage()
isBoardPage()

Even if their code is this right now:

var isPostingPage = function(){
return pb_action == "post";
};

Doing that would make it easy to update if PB changes.

Anyways, yeah, totally interested. Take this to PM maybe?

Never bothered with GIT, what's the learning curve on it?

I use Subversion, as most of my real work is done through it.

[Chris]

Nov 4, 2012 10:12:49 GMT -8 Peter said:

Nov 4, 2012 10:10:15 GMT -8 Chris said:

How do you feel about git? Been using that a lot recently and I think branching might work out nicely for this. With Github, it also lets us do pull requests easily, so we can have other PB members commit.

I'd also look at standard location check methods:

isPostingPage()
isBoardPage()

Even if their code is this right now:

var isPostingPage = function(){
return pb_action == "post";
};

Doing that would make it easy to update if PB changes.

Anyways, yeah, totally interested. Take this to PM maybe?

Never bothered with GIT, what's the learning curve on it?

I use Subversion, as most of my real work is done through it.

Learning curve from SVN = not too terrible. The git designer intentionally made it different from SVN because he hated SVN.

The way to make the transition easiest is to use their GUI apps instead of the command line.

Anyways, my only reason behind using git is it makes it much easier (as in, push of a button easy) to allow other users to submit "pull requests" (their own modifications to our code) that we review and then can easily merge directly into our code base. That way you can limit those with no-review write access to you and me, but allow everyone else to submit their own "suggestions."

Anyways, I'm fine with SVN. No reason to not open source this, so Google Code maybe?

[Peter]

Nov 4, 2012 10:51:25 GMT -8 Chris said:

Learning curve from SVN = not too terrible. The git designer intentionally made it different from SVN because he hated SVN.

The way to make the transition easiest is to use their GUI apps instead of the command line.

Anyways, my only reason behind using git is it makes it much easier (as in, push of a button easy) to allow other users to submit "pull requests" (their own modifications to our code) that we review and then can easily merge directly into our code base. That way you can limit those with no-review write access to you and me, but allow everyone else to submit their own "suggestions."

Anyways, I'm fine with SVN. No reason to not open source this, so Google Code maybe?

Am liking the idea of code reviewing, but not understanding how that is done when a project is public.

Am reading some stuff about it now, and also installed Git.

Here it is...

github.com/pixelDepth/yootil

I'll give it a try and see. Not sure I get the whole push / pull thing. Seems like an extra step just to get my changes into the rep.

So if you were to commit something to that now, how do I apply your changes to the rep?