User talk:Flickering19966

Hey mate. I just thought I should mention that I started making noise on Project talk:Namespace regarding development-related pages. I thought you might find it interesting. Bottom of the page. --Mikk 13:37, 26 May 2006 (EDT) (just delete this line when you've read it.)

Comments etc can go here...

Flickering, I just had a question and couldn't figure out if or how to e-mail it off to you... if you'd like please e-mail me at [email protected] Its about a mod im not sure is do'able, from the Functions Listed it my look as though it is. Thank you!

-Chris

Thanks for the updates.

I appreciate you updating the SavedVariables data for me here at WoW Wiki. -- AlexanderYoshi 18:45, 22 Dec 2004 (EST)

Please go ahead.

You can use the Frame:Function() format if you'd like, it sounds like a good change for certain objects.

-- AlexanderYoshi 00:22, 27 Dec 2004 (EST)

Excellent, as I work through things i'll make the change, the API page is a great potential quick reference, hopefully if we have some idea of context and arguments on functions it'll be as useful as possible.

-- Flickering 00:29, 27 Dec 2004 (EST)

Agreed. It has the potential to make life far easier for all of the developers.

-- AlexanderYoshi 00:43, 27 Dec 2004 (EST)

Mapping Functions

Sorry for changing the GetPlayerMapPostion, there were complainments about the wiki beeing false at the official WoW-forums and I changed it reading the "Verified for ... friendly" and missed the "player". Changed it back to the original words (deleting the "maybe"). But I think it would be nice to split this sentence into two, so that people can't misread it.

Meog 16:49, 30 Dec 2004 (EST)

XML UI elements documentation

Hi there, I noticed you are also doing an awful lot of work on documenting the XML elements and the API calls. Let me add a few comments about what I have been thinking about for the future, maybe we can open a discussion on these points.

First you will notice that the XML User Interface page, with regards to widget attributes/elements is currently just a dump. I was thinking for the future for each XML widget to have it's own page with a description of format/attributes/elements etc. E.g. a page like XML_Button, XML_Gametooltip.

Also, a separate page for each widget that discusses it's uses, examples in terms of its use in XML and Lua, and so on. Something like UI_Button, UI_Gametooltip.

I am not totally sure if these pages should be separate or not. I am still thinking about the right design in terms of how the XML pages, the API pages and some kind of description/examples type pages should be related for each of the widgets.

Let me know if you have any comments/ideas.

Nice

The Widget page is looking good, man!

-- AlexanderYoshi 00:33, 6 Feb 2005 (EST)

I have made comments on the Talk:World of Warcraft API and Talk:Widget API pages. Essentially I am hugely in favour of your new page. Please respond to the comments if you like. Lego 19:27, 6 Feb 2005 (EST)

Global function list page

After we have discussed the Global Function List page at length in the past, I know that mostly I have been the one maintaining it. I hope I haven't scared you off and please do not shy back from making comments or suggestions. In particular if your scans indicate something different from what I have put up, please let me know. I understand that you have written a Lua parser just for this purpose, and it would be a shame to let it go to waste. Especially when Blizzard patches WoW, there are bound to be changes. As you said on the Widget API page, it is good if we both check the function lists to make sure we don't miss anything. I appreciate all the hard effort you are also putting into the API pages, and I really like working together with others to make it the greatest WoW resource on the Net. Lego 20:21, 6 Feb 2005 (EST)

New patch on EU

We have a new patch (1.2.3) on EU servers. Time to run the scripts again ;-)

Do you still need FrameXML and WoW.exe? I just saw the comment you posted on my page. If so, I will work something out. Lego 07:19, 16 Feb 2005 (EST)

Patch 1.3.0

Will you be updating the Widget API for the new patch? I have done the parsing 1.3.0 and what I can see is the introduction of IsMovable, IsResizable, SetMovable, SetResizable plus the renaming of CanSave to CanSaveTabardNow. -- Lego 13:26, 25 Mar 2005 (EST)

Yes.. I've gotten the 'CanSave' one done, i'll be doing the others shortly (I got most of the global API, but did make one mistake which I've corrected - UnitIsPlusMob) -- Flickering 13:50, 25 Mar 2005 (EST)

Great, the Widget API page update is done. Do you concur on the Global API page update? Lego 23:04, 25 Mar 2005 (EST)

Question about Item Information

I'm currently trying to make a Character profile system much like Allakhazams but just for my guild. I've figured out most of the UI/Upload stuff but I can't figure out how to get actual item information. Thottbot mentioned that the information for every item in the game is stored clientside but I can't figure out where or how to extract it. Thanks.

-- Finalmjolnir

Patch 1.5.0

Hi, I am not sure if you are still visiting the Wiki or not, so I took the liberty of updating the Widget API pages for patch 1.5.0. If you find any errors do correct it. -- Lego 15:44, 7 Jun 2005 (EDT)

Widget API

I updated your "Current as of ..." line at the beginning of that documentation to reflect the Frame: changes in 1.10.2 . Hope you don't mind. I did a quick skim through the xml widget functions in the ingame enviroment and didn't see anything else new except IsToplevel and SetToplevel. BTW... I bet I can skin ya (In reference from the forums) :P -- Tarog 16:55, 2 May 2006 (PDT)

"Widget API New"?

Heya mate. I'm on a API page cleaning spree and came across Widget API New.. What is it and what's it doing there? =) --Mikk 19:10, 23 May 2006 (EDT)

"UISUMMARY EditBox"?

Like I said.. Cleaning spree =)

I came across this page and went "whoa! that's class!". Though thinking it over again, I'm not sure it's a good idea. If we had all the documentation ready and a revision controlling/linking automated system in place, it'd be a pretty nifty idea, but for the moment I'm not so sure it is; what it means is lots of data duplication. Data that changes. Lots. It'll be outdated in a matter of weeks =(

It might be possible to restructure the pages by using templates so that there's only one place that actually needs editing? Maybe that's the way to go?

--Mikk 19:15, 23 May 2006 (EDT)

Almost all of the widget pages are script generated by me (That does mean I have to back-propagate contributed changes to my source files, but generally that's not too hard). The wiki doesn't have sufficient layout and content processing capabilities to do it properly (that I know of). The actual source files I use are a combination of files created from wow itself, cross referenced with documentation snippets for arguments and descriptions.

-- Flickering 14:18, 2 June 2006 (EDT)

... but Region inherits LayoutFrame?

I saw you moved LayoutFrame:Hide and :Show to Region... but Region inherits them from LayoutFrame? No? I almost moved it straight back but saw that it was you that did it so I wanted to know if you knew something I didn't :-) --Mikk 18:16, 27 May 2006 (EDT)

The new abandoned API page layout ("/Alpha", "/TOC", etc...)

I put it up for a deletion vote. But noone is voting. Umm... let's see, how should I say this... "The democratic process of WoWWiki would value your input! Please Vote!" ;-) Talk:World of Warcraft API/TOC --Mikk 15:04, 2 June 2006 (EDT)

Fleshing out the UISUMMARY pages

I was thinking we could make use of wiki templates to finish your work with the UISUMMARY pages. Something along the lines of shoving the methods for each class into a subpage, that we can pull in as-is in the Widget API page as well as in any needed UISUMMARY pages. That way, texts are updated everywhere at once, and you only need to worry about a single location when generating new widget api pages.

The only catch is that it'll be multiple pages; one per class. How does that work for you? --Mikk 13:21, 17 July 2006 (EDT)

I dont really like that, the only reason I haven't finished the UISUMMARY pages is i've been too busy (lazy) to upload them all or finish my 'upload this wiki page' script. I will agree that making the widget API an assembly of the summaries is a spiffy workaround for the limitations of the mediawiki platform, but I think the resulting headaches of spreading editing everywhere outweighs its usefulness. Flickering 15:02, 17 July 2006 (EDT)

Hmm.. not sure I'm following you here. Spreading editing everywhere? The idea I had was that each class really only has one original page, which means nothing can be out of sync ever. Or are you thinking of something else? I'll try to explain better in case I made a bad attempt the first time around:

• Widget API/UIObject - contains only a list of methods for UIObject, complete with parameters and descriptions
• Widget API/Region - contains only a list of methods for Region, complete with parameters and descriptions
• Widget API/Frame - contains only a list of methods for Frame, complete with parameters and descriptions

etc.. These sub pages are never linked from anywhere; we don't expect people to view them directly.

• Widget API - would have its headings and then pull in all the sub pages in order, i.e. it'd look like it does today, except with all the methods replaced by {{Widget API/UIObject}}, {{Widget API/Region}} etc calls.
• UISUMMARY Frame - same thing; all the methods replaced by three template pulls.

We could possibly do something along the same lines for the script handlers to make sure they're only ever edited in a single place.

--Mikk 17:56, 17 July 2006 (EDT)