In any event, I really am very busy. I got a grown-up people's job recently, and it has slowly but surely been sucking the lifeblood out of me. In any event, I have an idea for Parrot 2.0 in my mind's eye, but I lack hours in the day and energy at the end of it to continue some days.
I appreciate your support. While Parrot is non-functional, feel free to peruse any of my competitor's options (SCT, MSBT, Blizzard's FCT) as long as you promise to take a look at Parrot 2.0 when it's done.
Let's try to say something positive about this...
I'm happy that you got a job, and I hope you like it and, even if lifeblood-sucking, I hope you find fulfillment (and a good pay) from it.
About Parrot2, rest assured I'll give it a try. Better: I'll look forward to test it. Even better: if you need some debugging, shout. Best: if you need a code-monkey*, yell.
Cheers,
Arzach
*code-monkey: meaning I code like a [drunk] monkey would do. If any good code comes out of my head, it's just luck.
I'm happy that you got a job, and I hope you like it and, even if lifeblood-sucking, I hope you find fulfillment (and a good pay) from it.
About Parrot2, rest assured I'll give it a try. Better: I'll look forward to test it. Even better: if you need some debugging, shout. Best: if you need a code-monkey*, yell.
Cheers,
Arzach
*code-monkey: meaning I code like a [drunk] monkey would do. If any good code comes out of my head, it's just luck.
I dearly miss Parrot.
Of the three potential candidates to fill in for Parrot until it is updated for 2.4, which more closely matches Parrots functionality.
Very, very sad to see Parrot being shelved for now but I understand real life takes priority.
Unfortunately, nothing has ever run as clean or as smooth as Parrot. I was a rabid SCT fan until the module split and became a bit clunky and never did exactly what I wanted. I'm now using MSBT which is close to Parrot but doesn't seem to run anywhere near as well. Side-arcing scrolls are shaky even at 150fps whereas Parrot was butter smooth.
ck, if you can ever find the time to get back into mods, please make this one the first! As for anyone else willing to take over, it would be greatly appreciated!
ck, if you can ever find the time to get back into mods, please make this one the first!
ck is currently working very hard on mods - rewriting DogTags library for Pitbull, CowTip and other addons. This has priority, because this will fix many addons and not just one addon - Parrot.
Completely understandable. I just figured from his wording he was stopping all mods because things were so busy. Given that, I certainly hope he can find the time to sneak in Parrot sometime down the road. We can all get by on MSBT until then! =)
I love Parrot. Before that I was using SCT, but now that Parrot is gone I miss it so much... :/
The ckknight's works are awesome >_< Now I've tried SCT again, and then the Default Blizzard Combat Text, and then MSBT and I didn't like any of 'em.
But there's sth I wanna ask to Phanx. If the library "LibParser-4.0" is updated according to new system(Don't know whose developing it), could it make Parrot work giving Ck more time if he wants to Develop Parrot 2.0 and make a solution workaround as users ?
LibParser-4.0 was developed by ckknight, and rewriting it to make Parrot function in 2.4 would be much more work than just rewriting Parrot. Not only would you need to replace all of the current string parsing code with code to handle the new raw data, you'd also have to create pointless wrapper functions to feed that data through the existing LibParser-4.0 API. Basically, it would be an ugly mess. Rewriting Parrot is the simplest solution, and the best solution, and pretty much the only solution; there is no "workaround".
ck is currently working very hard on mods - rewriting DogTags library for Pitbull, CowTip and other addons. This has priority, because this will fix many addons and not just one addon - Parrot.
Something else that should be noted here is that the new version of Parrot - which ck has been planning out for quite some time - will be using LibDogTag-3.0 to handle its text display and formatting, which is why DogTag has taken priority. Parrot fans, feel free to drool over the thought of the flexibility and customization offered by this change; keep in mind, however, that it will certainly still have sane defaults so that you don't have to mess with tags unless you really want things *exactly* the way you want them. :)
come back CKK =( I miss you and your amazing addons ;<
Why he has to come back if he is already here all the time?
Check out his profile and you will be able to see when he was last Online, you can also browse his last posts from there.
Who said it wasn't getting updated? From what I understand, ck basically said it will be updated at some point, when he has the time to do so.
Well he said earlier in the thread that he had some ideas for 2.0, so I figured between that and his current reason for not updating it to work for 2.4, and suggesting people try other options meant it would be safe to assume 1.0 wouldn't be seeing any updates.
Well he said earlier in the thread that he had some ideas for 2.0, so I figured between that and his current reason for not updating it to work for 2.4, and suggesting people try other options meant it would be safe to assume 1.0 wouldn't be seeing any updates.
1.0 or 2.0, what's it matter what version it is? There's too much that's changed with the combat log to push out a simple 1.0 fix, so yes, I'm guessing the next version of Parrot released will likely be a 2.0 version/candidate/beta/whatever. Parrot will still be Parrot regardless of version, so I don't quite follow how that implies he's stopping work on it...? I've seen a few places where people have spouted off that Parrot is basically dead, when I haven't personally seen ck mention anything of the sort. But, I think I understand where you're coming from now, at least.
MikScrollingBattleText (MSBT) looks to be pretty similar to Parrot, with user-creatable scroll areas and such, so I'm using that as an alternative to Parrot :(
With all the people affected by this, is there any chance one has the capability to update Parrot in the interrim, or is the author against this?
Let's try to say something positive about this...
I'm happy that you got a job, and I hope you like it and, even if lifeblood-sucking, I hope you find fulfillment (and a good pay) from it.
About Parrot2, rest assured I'll give it a try. Better: I'll look forward to test it. Even better: if you need some debugging, shout. Best: if you need a code-monkey*, yell.
Cheers,
Arzach
*code-monkey: meaning I code like a [drunk] monkey would do. If any good code comes out of my head, it's just luck.
I dearly miss Parrot.
Of the three potential candidates to fill in for Parrot until it is updated for 2.4, which more closely matches Parrots functionality.
Thanks,
- Pahbi
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumProlly MSBT.
Unfortunately, nothing has ever run as clean or as smooth as Parrot. I was a rabid SCT fan until the module split and became a bit clunky and never did exactly what I wanted. I'm now using MSBT which is close to Parrot but doesn't seem to run anywhere near as well. Side-arcing scrolls are shaky even at 150fps whereas Parrot was butter smooth.
ck, if you can ever find the time to get back into mods, please make this one the first! As for anyone else willing to take over, it would be greatly appreciated!
ck is currently working very hard on mods - rewriting DogTags library for Pitbull, CowTip and other addons. This has priority, because this will fix many addons and not just one addon - Parrot.
Thanks for setting me straight!
The ckknight's works are awesome >_< Now I've tried SCT again, and then the Default Blizzard Combat Text, and then MSBT and I didn't like any of 'em.
LibParser-4.0 was developed by ckknight, and rewriting it to make Parrot function in 2.4 would be much more work than just rewriting Parrot. Not only would you need to replace all of the current string parsing code with code to handle the new raw data, you'd also have to create pointless wrapper functions to feed that data through the existing LibParser-4.0 API. Basically, it would be an ugly mess. Rewriting Parrot is the simplest solution, and the best solution, and pretty much the only solution; there is no "workaround".
Something else that should be noted here is that the new version of Parrot - which ck has been planning out for quite some time - will be using LibDogTag-3.0 to handle its text display and formatting, which is why DogTag has taken priority. Parrot fans, feel free to drool over the thought of the flexibility and customization offered by this change; keep in mind, however, that it will certainly still have sane defaults so that you don't have to mess with tags unless you really want things *exactly* the way you want them. :)
Why he has to come back if he is already here all the time?
Check out his profile and you will be able to see when he was last Online, you can also browse his last posts from there.
Well he said earlier in the thread that he had some ideas for 2.0, so I figured between that and his current reason for not updating it to work for 2.4, and suggesting people try other options meant it would be safe to assume 1.0 wouldn't be seeing any updates.
1.0 or 2.0, what's it matter what version it is? There's too much that's changed with the combat log to push out a simple 1.0 fix, so yes, I'm guessing the next version of Parrot released will likely be a 2.0 version/candidate/beta/whatever. Parrot will still be Parrot regardless of version, so I don't quite follow how that implies he's stopping work on it...? I've seen a few places where people have spouted off that Parrot is basically dead, when I haven't personally seen ck mention anything of the sort. But, I think I understand where you're coming from now, at least.
But you will miss the customizable triggers and changing the supressions...
-
View User Profile
-
View Posts
-
Send Message
Curse Premium