Go to Page... |
Updated: | 08-27-13 09:19 AM |
Created: | 07-15-13 01:34 PM |
Downloads: | 949 |
Favorites: | 7 |
MD5: |
File Name |
Version |
Size |
Author |
Date |
Type |
0.3.1 |
15kB |
12-02-13 08:48 PM |
Addon |
File Name |
Version |
Size |
Author |
Date |
0.2-beta |
51kB |
Zhevron |
07-15-13 01:34 PM |
![]() |
Comment Options |
Maiiel |
View Public Profile |
Send a private message to Maiiel |
Find More Posts by Maiiel |
Add Maiiel to Your Buddy List |
![]() |
|
Forum posts: 0
File comments: 1
Uploads: 0
|
![]() The flag setting for experience is inaccessible due to the fly out not being interacted with. It flies out beneath the description scroll box.
Settings does not display anything. I can assume it's a WIP section of the add-on at this time. Guild does nothing, same function as Settings - displays a blank page of the add-on interface. Assumed WIP. Other than these issues, this mod is kind of nice and I would like to switch once it's finished. Fav'ed to keep a watch on progressing updates. ![]() |
![]() ![]() |
![]() |
DraconicMiss |
View Public Profile |
Send a private message to DraconicMiss |
Send email to DraconicMiss |
Find More Posts by DraconicMiss |
Add DraconicMiss to Your Buddy List |
![]() |
||
Forum posts: 0
File comments: 2
Uploads: 0
|
Quote:
Compat-wise, Tome and Meri feature full compatibility wherever possible. Tome can read Meri, Meri can read Tome. Running Tome and Meri at the same time is possible, but be aware that Meri has no priority for which data it shows. If it's receiving two sets of data from one user (IE: you running both addons), we don't know how it will display that info, as there are going to be conflicting fields. Tome always prioritises Tome data, providing that Tome data exists, and people running both Tome and Meri also will only see your Tome data. The extended flagging functionality is something we're not likely to add to Tome in any way. As it stands right now, the flags for Tome (IC/OOC, Experience Flag, Tutor) all translate into the appropriate Meri flag, so a user with Meri will still get some of the flags. We intentionally left out the more descriptive flags and the meta field simply because of personal preference. Both me and Zhevron come from a WoW-RP background, where these features weren't around in the addons we used. At a pinch, we feel people can just write "(( Mature Roleplayer ))" in their descriptions and people will understand it just as well. Unfortunately, adding the optional flag system is just another feature that, firstly, we don't really want to add unless the demand skyrockets, for reasons stated above, and secondly, wouldn't be on top of our list of priorities, as we have many core features of Tome still to finish. I hope this addressed some of your questions, and thank you for your feedback. |
|
![]() ![]() |
![]() |
Maiiel |
View Public Profile |
Send a private message to Maiiel |
Send email to Maiiel |
Find More Posts by Maiiel |
Add Maiiel to Your Buddy List |
![]() |
|
Forum posts: 0
File comments: 1
Uploads: 0
|
Thanks for putting up the addon :=)
I like the look and the planned features you have - multi-descriptions is something I used to use heavily in WoW back in the day, and I never realized how much I missed that until you brought it up. Guild functionality made me squee. But, I have some concerns. Merisioux has been the main addon for everyone to use since it came out (Like a year or more ago?), it's something we on Argent recommend everyone to go and get - the arrivial of another and especially if it's not compatible with Merisioux in the crucial areas is going to confuse everyone. I'm especially thinking of new players as well. In WoW you had a billion (well, I knew of four, but it's been 3 years) RP addons and it was a right mess, often ending with you having two or more addons installed to make sure you didn't miss a flag or a description. I don't know how well the compability is now (I'll put both on and see if the world explodes) but I'd urge you to at least make sure they are as compatible as humanly possible. Now, my favorite parts of Merisioux as it is right now, is the extended flagging functionality - You have flags for your IC/OOC status as well as your preferences, which has been a great help at least from what I can tell - it reduces drama lead on by different playstyles. Out of all of them, at least in my guild the Peaceful/Conflict flag and the maturity flag have been very popular. But also the Meta section, to give people a heads up about something you feel as a player they need to know. I use it to state what system I use for fights for example, so people don't get surprised if they end up in a fight with my character. I get that the additional flags potentially confuse and clutter, but I think one thing to remember is that they were heavily desired by the community when seebs was writing the addon and we're all used to it now. The functionality of them is truly great, and I wouldn't go without them if I had the choice. If anything, make it optional for people to show the additional flags and the meta section, but please don't take it away from us. |
![]() ![]() |
![]() |
Tasia |
View Public Profile |
Send a private message to Tasia |
Send email to Tasia |
Find More Posts by Tasia |
Add Tasia to Your Buddy List |
![]() |
|
|
I'll jump over to email to pursue this.
|
![]() ![]() |
![]() |
seebs |
View Public Profile |
Send a private message to seebs |
Send email to seebs |
Find More Posts by seebs |
Add seebs to Your Buddy List |
![]() |
|
|
Yeah, no one likes the people that take their code with them when they leave. Personally, I've released under the GPLv3, so not really hiding anything either.
In order to make LibMerisioux more universal, I think your normal flagging system should be moved into Merisioux itself and be made transparent in the library. That would allow for people to implement their own flagging systems quite easily. Tome was made with simplicity and accessibility in mind when it came to its flags. I really only have a flag that states their roleplaying experience. This is the way most addons in WoW did it and I honestly prefer it that way myself. And I've thought about using the storage API myself for character data. Question is...how limited is it? I assume that one day, some inexperienced developer is going to have an awesome idea to store a lot of data in server storage and not compress it. That could cause some serious issues for addons like Tome and Merisioux if we only use the storage API. I'll consider at least bringing in LibMerisioux for the compatibility provided the resource usage isn't too high. I've noticed that it brings in another 4 dependency libraries. I assume you're in control of all of them? And as a side note, I decided to rely on LibUnitChange as well. I figured it's okay as long as Trion keeps it updated. Well, that and the fact it wouldn't take long to reimplement it inside the addon should they fail to do so. EDIT: I'm not sure you want to implement everything that I'm being asked to implement in LibMerisioux, but if you want to have a look at current feature requests for Tome, you can always check the Github repo issue tracker: https://github.com/zhevron/Tome/issues I've really got a long way to go before I'm even remotely done with an official release.
Last edited by Zhevron : 07-17-13 at 12:09 AM.
|
![]() ![]() |
![]() |
Zhevron |
View Public Profile |
Send a private message to Zhevron |
Send email to Zhevron |
Find More Posts by Zhevron |
Add Zhevron to Your Buddy List |
![]() |
|
|
I'd be interested in hearing more about the flag thing -- I might be able to accommodate stuff. And I've had requests for things like age, height, and weight.
As to the library: LibMerisioux exists specifically with intent that no one has to re-implement the functionality. I could in theory disappear and stop maintaining it, but I have released it under terms such that anyone can always go ahead and take it over. I am not in the "you can't have my toys I'm quitting" camp. So, yes, it's intentionally separate. I'm almost certainly going to add UI to Merisioux for anything that LibMerisioux does, just for maintenance, but the goal is that if other people want to exchange data, they can use the library and then we all (in theory) get guaranteed compatibility. So lemme know if there are fields you'd like LibMerisioux to have added, and I'll see if I can get those in. It's a good time for updates, because the old library (0.15 Merisioux and earlier) won't survive the 2.4-2.5 API updates, so I can sort of push new versions. ![]() The biggest change which might matter to you is that current LibMerisioux is now using the storage API by preference, because that can reduce bandwidth usage. There's another more subtle change, though. Right now, LibMerisioux is doing its own compression/decompression of serialized objects... But it is now also accepting uncompressed strings in some cases. The intent is that once everyone is on at least this version, I will stop doing the compression-decompression in LibMerisioux, and instead take advantage of LibRarian doing that automatically. Feel free to drop by #riftuidev anytime, I'm usually around. And I totally get where you are coming on with the concern about third-party libraries. I think the only one I've been relying on is LibUnitChange, and Zorba has updated that. |
![]() ![]() |
![]() |
seebs |
View Public Profile |
Send a private message to seebs |
Send email to seebs |
Find More Posts by seebs |
Add seebs to Your Buddy List |
![]() |
|
|
In all honesty, I felt that it wasn't all that safe to rely on third-party libraries these days in Rift as most developers here are long gone and I fear quite a few libraries and addons are going to die as soon as the new event system is enforced. Tome was made with the mentality that it would not have to rely on third-party libraries if possible. There's really nothing more to it. Hopefully it all makes sense to you. I made the addon with the new event system in mind and relying on third-party updated could be the death of it.
EDIT: It's also worth mentioning that I did not go with a flag system the way LibMerisioux implements it. I keep a single flag for Tome which I convert to a set of static flags for Merisioux when it responds to a query. I guess you could say that LibMerisioux wasn't flexible enough to be used the way I needed it to for my addon. Should you be interesting in converting LibMerisioux to a more universal format and running that as a separate project, I'd be happy to both use and contribute to it.
Last edited by Zhevron : 07-16-13 at 07:19 AM.
|
![]() ![]() |
![]() |
Zhevron |
View Public Profile |
Send a private message to Zhevron |
Send email to Zhevron |
Find More Posts by Zhevron |
Add Zhevron to Your Buddy List |
![]() |
|
|
Just curious... Looking at the code, I notice that you have re-implemented LibMerisioux. I am wondering why; in particular, I'd been assuming anyone else doing similar addons would use the library so that it would be easy to keep things synchronized if, say, I updated the library to use new communications methods. Which I did...
The intent had been to completely discontinue the old rar_query/rar_datum messages when the old event API goes away, since in principle every version of LibMerisioux which supports the new event API also supports the newer messages. |
![]() ![]() |
![]() |
seebs |
View Public Profile |
Send a private message to seebs |
Send email to seebs |
Find More Posts by seebs |
Add seebs to Your Buddy List |
![]() |