- Registered User
Member for 11 years and 22 days
Last active Fri, Oct, 4 2013 14:32:23
- 0 Followers
- 7 Total Posts
- 0 Thanks
Apr 7, 2008LibBabble-Inventory is missing a translation for the word "Weapon", and quite a few other strings as well judging by the length.Posted in: Libraries
If you're a native frenchie you might consider finding the missing translations and posting or mailing them to whoever is responsible for the library, otherwise the error might be there for a while. :)
Apr 6, 2008Posted in: LibrariesQuote from Arrowmaster »
I already did this like last month or maybe it was even earlier than that.
Sounds great, though you've certainly hid it well, so well in fact that I can't find it. :)
EDIT: Nm, I'm dumb.
Quote from tekkub »
The thing about (c) is that it also provides a minimal amount of code to embed, which is the main reason noone wants to do (a).
Indeed, 70k seems an awfully lot to embed just for basic i/o.
Apr 6, 2008Posted in: LibrariesQuote from OrionShock »can anyone provide a VIABLE USE situation for anything that has been presented, that isn't already handled better by another addon (xpt for fubarplugin ofc)
The problem is that fubar has a monopoly and as long as nothing changes, that will continue. Now I don't have a problem with fubar being popular, I use it myself, the problem lies in that every addon under the sun is forced to conform to fubarPlugin. This means it's virtually impossible for anyone else to make use of that information, the only solution is to make an api of their own and hope that others want to port their plugins. How likely do you really think that is at this point?
The other side of this is that we're forced to conform to the wishes of ckknight. He's of course free to use whatever framework he wants, in fact I salute him for rolling his own instead of following the beaten path. However, it pisses me off that I'm forced to follow him just to get some basic i/o in my addon. Everyone's so gung-ho about framework agnosticity, and yet you're telling me that writing a generic i/o library is a waste of time?
The point I'm trying to make is that we have three choices.
a) Everyone includes Rock in their mods to be able to use libFubarPlugin-3.0.
b) Someone ports libFubarPlugin to Ace3.
c) We make a generic addon interface which can work with anything people care to code for.
A is, at least for me, completely out; I refuse to clutter my addons with two frameworks. And yes I realize I already have Rock running with fubar, I just think it's retarded that I should need to use two frameworks for something this simple. B is better, but it's still just a band-aid fix. It means we're still stuck with fubar as the only interface of choice. It's also a waste of developer time if you ask me.
C is imho the only sane solution to this, and it's about time that someone thought of it. We're not even talking that much work for an interface like this. All it needs to do is expose a few bits and bobs, and let implementation take care of the rest. Considering that libFubarPlugin likely needs to be ported in the first place, it should be a relatively small issue to make it talk to an interface instead.
All I'm saying is that this has to be solved some time quite soon. Once ace3 rolls out there needs to be fubar support, and I hope people don't cop out.
- To post a comment, please login or register a new account.