Talk:Dev
[edit] A bunch of ideas...
Maybe the Dev namespace can be organized with several Main Sections that can open to other Sub-Sections, like with the V3 pages.
- Example: 'Slave Development' section, ‘Assistant Development’ section, ‘Translations’ section, ‘Images’ section (for gathering images/editing them etc), ‘Text’ section (where any text could be check for spelling mistakes) and an ‘Idea’ section (where suggestions for new slaves, events etc, can be discussed).
--M.I.A. (Maia Iliana Arina) 17:02, 10 March 2012 (UTC)
Good idea. Also suggest a 'Background' section for all the relevanted facs about this world (thus such infos not could also be somewhere else). The ‘Images’ section would be difficult since this can need some space. And some 'Bug tracking system' would certain be nice, yet if a 'simple' wiki could do this full-fledged. --RFC2795 23:53, 10 March 2012 (UTC)
For the 'Images' section, I was not really thinking about Uploading pictures on the wiki, but more about requests for one/several Images (either for editing, or just because you need it for a slave) that can be uploaded on sharing-files site, like Mediafire. --M.I.A. (Maia Iliana Arina) 00:07, 11 March 2012 (UTC)
- Well, if its to be used for development I wouldn't have too much objection to finalized and/or release candidate images being uploaded here - plenty of space for that. I even envisioned the use of gallery tags. Lay out all of the necessary images in a gallery, and leave missing/still-needed images blank or something. Images that were still WIP (decensoring, coloring, what-have-you) might be better exchanged elsewhere. WikiSysop 03:38, 12 March 2012 (UTC)
I could possible install an Issue Tracker extension ([1]), not sure if that would be overkill. Plus, sounds like it is out-of-date. WikiSysop 03:40, 12 March 2012 (UTC)
- Idk if this is relevant, but I met Ambassador Tachiba in "attend court". Is there any page for her yet?
- No, there is no page but it should be made in the Version 3/Characters/NPC section. --M.I.A. (Maia Iliana Arina) 20:42, 12 March 2012 (UTC)
- Okay, let's talk some formatting, shall we? There's not a lot of structure to wiki talk pages - you can thrown an asterisk in like I did at the start of this block, you can thrown in an opening colon for indentation, but there's no way to "enforce" any of that as-such. That can make things hard-to-read (see exchange directly above). I could activate Liquidthreads ([2]) or DiscussionThreading (([3]) on Dev. For that matter, there are also full forum systems ([4], [5]) - but I don't know if that would just be duplicating anything already going on at FutaPalace or Bloodfer. WikiSysop 03:46, 13 March 2012 (UTC)
- I know nothing about formatting and text structure in wikis, so you can go with anything that could help. --M.I.A. (Maia Iliana Arina) 13:24, 13 March 2012 (UTC)
- I've just take a look at Liquidthreads and DiscussionThreading. Both are great but I kind of like Liquidthreads text/page structure more. --M.I.A. (Maia Iliana Arina) 13:27, 13 March 2012 (UTC)
- Yeah, me too. Might be tricky to get running. I'll mess with it. WikiSysop 23:25, 13 March 2012 (UTC)
[edit] Code formatting
I've installed an extension to make code more readable. Observe:
- XML sample:
<FirstContest>Today is the first of a series of competitions #slaveheshe can enter, competing against other slaves and other people. These contests occur every 8 days from the first day of the year.</FirstContest> <LaterContests>#slave can compete in a contest again.</LaterContests>
- Actionscript sample:
function ShowSexActTitFuck() { if (_root.DickgirlXF > 0) TitsFuckClip.gotoAndStop(2); else if (_root.Lesbian) TitsFuckClip.gotoAndStop(3); else TitsFuckClip.gotoAndStop(1); TitsFuckClip._visible = true; }
XML is a bit more subtle than Actionscript, but its something. WikiSysop 23:25, 13 March 2012 (UTC)
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| SDK fun | 0 | 02:42, 21 March 2012 |
| Hm, now what? | 3 | 23:44, 19 March 2012 |
| Issue Tracker | 2 | 00:13, 15 March 2012 |
| Sample - Wedding Peach | 1 | 00:31, 15 March 2012 |
| Code formatting | 1 | 23:57, 14 March 2012 |
| User agreement | 0 | 23:53, 14 March 2012 |
I've done a raw text dump of the main part of the v8 beta 2 SDK, and made a quick table of contents at User_talk:WikiSysop/WIP. I've begun formatting the Getting Started section, but pretty much everything needs formatting, so if you get bored...
I figure when everything has been wikified I'll move the entire SDK page into Dev as the front page for the SDK section, and fold the prettified table of contents into that.
Still need to put the Daisy Strike sections online. When you need documentation to use your documentation, hurr...
With the Wedding Peach assistant online we have an example and something to mess around with, and that's a good start. I feel like I should be writing documentation as to how to use these pages, and I'm feeling a bit nervous about it.
Clearly, the current version of the SDK is outdated. If there is any documentation as to how to build XML slaves and assistants, it would not appear to be part of the SDK. Somebody may have written such documentation somewhere, but I don't think 100% comfortable with putting it online here without getting the blessing of whoever wrote it. I don't want to step one anyone else's toes.
I'd really like to talk with cmacleod42 about some things, but I don't know how to contact him privately.
Well, Cmac do not give his private email to anyone, so the best way to reach him is either trough a comment in his blog for the game or by sending him a PM in one of the Forums.
Thanks. I PMed him on futapalace.
He got back to me this weekend - says he's going to send me a beta of the new SDK, and that the full SDK can be posted here on this wiki - which is pretty great. I've installed an extension to allow the easy export of selected pages as an OpenDocument or PDF file, so that could make SDK maintenance a LOT easier from here on out.
I've installed the issue tracker, sample on the fron page of Dev - still working out some bugs and kinks. Right now bugs can be assigned to anyone with admin access - meh. I think I can create a "dev" access level, which wouldn't have any special abilities over other users than the ability to have bugs assigned to them - again, not sure if any of that is overkill.
I asked MIA about using Wedding Peach for demonstration purposes. She agreed. I've set it up more-or-less as I envisioned it. There should probably be some sort of template made for the dev projects, but I don't have any experience making templates myself (yet). Under the "using this page" header should probably go some blank gallery examples, some notes on code formatting, etc. Putting it all online got me to thinking about "release versions" versus "work-in-progress" versions. I guess somebody ultimately has to take responsibility for each project and occasionally package everything up and... submit it to Cmac? I'm actually real fuzzy on how new slaves and such get into teh main Slavemaker release, not being a developer myself. I'm downloading the SDK right now to clarify a few things for myself.
I've installed an extension to make code more readable. Observe:
XML sample:
<FirstContest>Today is the first of a series of competitions #slaveheshe can enter, competing against other slaves and other people. These contests occur every 8 days from the first day of the year.</FirstContest> <LaterContests>#slave can compete in a contest again.</LaterContests>
Actionscript sample:
function ShowSexActTitFuck() { if (_root.DickgirlXF > 0) TitsFuckClip.gotoAndStop(2); else if (_root.Lesbian) TitsFuckClip.gotoAndStop(3); else TitsFuckClip.gotoAndStop(1); TitsFuckClip._visible = true; }
XML is a bit more subtle than Actionscript, but its something.
Here's an inevitable scenario - somebody will eventually get butthurt over some petty bullshit and demand their work be deleted or otherwise revoked. That tends not to mesh well with a wiki. Fenoxo of "Corruption of Champions" fame (?) wrote up a sort of user agreement for writing submissions here: [6]. We'll probably need something like that...
