Talk:RbxGui: Difference between revisions
>Legend26 →Source Code: new section |
>Legend26 →Source Code: new section |
(No difference)
|
Revision as of 03:21, 6 January 2012
@Blocco
Please post the Contents. I can't download the latest version; it's offline. Thanks. -aboy5643
I always wondered how to use it. Thanks whoever wrote this page. :D
- Are we documenting all the functions in there? They look quite usefull. I guess I won't need to port my GUI library to roblox anymore :)Trappingnoobs (Writer) Have I done something bad? Good? Tell me on my talk page 10:43, 2 August 2011 (UTC)
- We're documenting as many functions possible. Only the ones that are actually in the library, not the local functions that the ones in the library use.
- You're welcome. ;)
Error
I get an 'Unknown exception' when I call LoadRobloxLibrary from a script. Is this meant to happen? It's not locked, so I shouldn't imagine so. :L
- It is locked on the production build as of now. As to the current gametest build, I am not certain whether it is locked or not, as I have not tried using it yet. I'll just plug this code in.
- Try LoadLibrary() jedikacheff said that LoadRobloxLibrary is locked.
Just wondering, but why don't you just list the functions/methods like... A FUNCTION OR METHOD???? Maybe just help a bit... Not to be rude or anything... erm... - Quenty (talk • August 3)
- The current method of documentation only uses the {{method}} template for methods which belong to an instance. AFAIK, RbxGui is not an instance.
- Maybe we should make templates for libraries. It'll get ugly otherwise.Trappingnoobs (Writer) Have I done something bad? Good? Tell me on my talk page 08:20, 4 August 2011 (UTC)
- It shouldn't get ugly provided we don't suddenly put method templates in our pages.
- Maybe we should make templates for libraries. It'll get ugly otherwise.
Merge
Shouldn't this be merged with the "RbxGUI_API" page? - Quenty (talk • December 24)
- Right now we have no plans on how to document libraries, and this page was just a prototype. In the future, we might take on a single form for all library pages, such as documenting the API for each library on the page of the library, and omitting non-library-specific details (such as how to access the library).
Source Code
Why don't you just provide the link to the source code itself? It makes much more sense and stops it from cluttering the page. Legend26 (talk | contribs) 22:21, 5 January 2012 (EST)