WiiLi.org

luis_villase · Posted: Tue Jun 19, 2007 3:57 pm Post subject: Feature Request

OK, READ THIS FIRST please:

1. Please go easy on your requests, OK? We're not doing this as a job and certainly don't have as much time as we would like to, so new features might and will take some time.

2. Please be patient. Refer to number 1 for details.

3. Don't ask for things that may be too farfetched (or at least, be very clear on what you want)

4. Understand this: At the very begining, OpenPIE Project will provide GlovePIE's scripting and button mapping functionality. The idea is to implement some other sweet things, basically anything you can think of (that's why it will be open source). There is no current release, we are in a pre-alpha stage at the moment, but will keep you posted on any advancement. (check Release Status thread every now and then)

Thank you.
_________________
Not all mexicans enjoy tamales and piñatas, and tacos aren't really made that way!
Luis V.

luis_villase · Posted: Tue Jun 19, 2007 4:01 pm Post subject:

Mienaikage · Joined: 13 Dec 2006 Posts: 54 Location: London, UK

Hmm... if it's possible a way to choose which controller is 1, 2, 3 and 4? In GlovePIE it was done in reverse order of the way they were installed :S

TiagoTiago · Joined: 20 Jan 2007 Posts: 710 Location: Brasil

I wouldn't be able to make any sense of the code, but I'll take a look at the license, anythign I should keep and eye on?
_________________
please put the scripts on the wiki so they dont get lost as new stuff is posted!
phpBB doesnt like me,somtimes it will forget to warn me about new replies to threads I asked it to,if you see a thread I should have responded, could please email me?

TiagoTiago · Joined: 20 Jan 2007 Posts: 710 Location: Brasil

the only references about license I found said the libraries are under the GNU license aparently, and guessing from the file extension it was coded in pascal ( .pas )

ps: the link on the FreeTrack page points to http://camil.dyndns.org/freetrack/trunk/Sources/ for the code
_________________
please put the scripts on the wiki so they dont get lost as new stuff is posted!
phpBB doesnt like me,somtimes it will forget to warn me about new replies to threads I asked it to,if you see a thread I should have responded, could please email me?

fortunzfavor · Joined: 13 Jun 2007 Posts: 95

Just something to keep in mind for the distant future.

A GUI debug. Instead of testing your code on a memo like in glovepie, pull open the GUI debug and see pictures of a Wiimote, Mouse and Keyboard--when you press a button, it lights up that wiimote button and the keyboard key (or mouse button) that it's assigned to and displays the command referenced (ie key.a = wiimote1.one) in a text box at the bottom.

This tab could also be drawn from for a Novice mode. People who are frightened by scripts could still use them and get a quick look at what does what without ever seeing any code. No text editor or menus visible, just the Mode toggle (Novice/Not Novice) button and the GUI debug described above.

A GUI command list. Instead of depending on script writers to make their code readable and organize comments, the Gui Command List reviews the code and generates a Plain-english list of wiimote buttons and equivalents (A wiimote column with each button listed next to a column with it's equivalent). To begin with, that's worth having. If it were developed further, those scripters that wanted to could code (using HTML say) a visual command list far more precision, giving not just key codes but the specific function in a particular game (ie Wiimote B = missiles) of task, or even replacing the text list with a gif or Jpeg (included in their script's zip file) that shows the keys visually*. This would allow a lot of leeway for those using wiimotes for a variety of diverse tasks to clearly explain those tasks, and for those using motion controls in specific ways to demonstrate them to users clearly.

I know, you said take it easy. I'm not making any demands, just throwing out a couple of ideas. Use what you like. Forget what you don't.

*Openpie would scan a script for GCL (GUI command list) code, and if none were present, it would generate the default text columns. GCL code be present in the primary file, but would be marked off with a comment-like marker (ie ##, only visible if the .openpie file were viewed in a text editor), and all such lines wouldn't be visible in the main script editor, but only in the code mode of the GCL tab. When scripters want to modify that GCL code, they go to the GCL tab, hit the source button which would show the new GCL editor. If HTML were used, they could code it where ever they chose (even using some wysiwyg editor) and then copy the markup there. They toggle back from Source mode to Display mode and see what it looks like.

kiddo7 · Joined: 05 Feb 2007 Posts: 42

I know you guys are already doing as much as you can and that you are getting more requests than you will probably be able to implement in the first release, so I have been very hesitant to post this.

The only thing I can think of that i would really like to see in openpie would be custom functions. Basically, code that accepts an imput and gives an output and can be called upon from any other code using a predifend syntax e.g.

"function"{x,y,z,} where function would be the name of the function and X, y, and z would be the input(s)...