How does one set things so that the cursor will be in the login field waiting, blinking for users to simply type in their name??

i.e. send the browser to the login page and type, no mouse clicking, no tabbing??

lazily,
daddystu

hey jorge, thanks for the input now and continued

I too like the simplisity of the spreadsheet.
Here is a quick first draft.

jenny, I agree 100% if not more that we need this to be presented in a way that others can contribute to. Please don't misunderstand me, I just think that first of all we need to get our direction right and a few of us can generally do that better than many.

Have a look over this excel sheet and post here, thanks.

Stu

no worries, when you can.


I'll see if I can dig up anything on the XOOPS glossary...

I have used the dictionary module, yes, but apparently it has (had) a security vulnerability that I don't really understand. That was v0.9 though, still I digress

Let's bang through an initial list on the admin control panel section ourselves and see where we get to if that's OK with you.

I thought that might be better at first, then when we have the basic list, offer it up to some more people
for opinions, then maybe putting into such a module might be good for continual development. I could probably setup a temp server we could use...I'll have a look for the new one.

Catchyer later

Here are some ideas to get the ball rolling.

I have taken jensclas's offer of help and we will use this board to post updates.
Dave if you caould please add jensclas to the team members, that would be great, thanks.

Here is a starting outline...

I am not used to working in cyberspace so am actually wondering what the best way to collaborate would be..posting here is a good base but if there are screenshots and/or looooong messages?? And versioning of course. Any help on that would be appreicated.

Cheers


**********
XOOPS Quality Assurance team
Date:January 31, 2005

TASK:Action Item#4
Define which areas require 'standard' terms. UI buttons - 'Submit' c.f. 'Send' for example. Next would be translation of these.

Members: daddystu, Japan, jensclas, Australia

**************
TERMS for this ActionItem itself

ADMIN CONTROL PANEL>the administration area where all modules can be administered, the XOOPS admin area

MODULE ICON > the icon/graphic, usually yellow, which represents the module in the admin control panel area

MODULE ADMIN PAGE> each module has one or more admin pages. Access to these pages is by clicking on the module icon in the admin control panel or by clicking on one of the menu items when mousing over one of these module icons.

XOOPS USER INTERFACE>any non-admin area of XOOPS and/or its modules.

*********
ACTION ITEM ROADMAP
1:Pinpoint the elements.
2:Create a list of English language that could be used for these elements.
3:Test and remake the list by comparison with several modules.
4:Translate the list.

*********Start with 1***

1.Pinpoint the elements that are generic to any XOOPS module (or very common - shared among many modules).
1.1:XOOPS CORE TERMINOLOGY
1.2:ADMINISTRATION USER INTERFACE (ADMIN UI)
1.3:USER INTERFACE (UI)

**********************
1.1:XOOPS CORE TERMINOLOGY
A module developer may provide instructions and/or the functionality of their module may refer to core parts of Xoops. The terms used must match that of the XOOPS devs.
Example, the administration Control Panel. Blocks...etc.
There should be a glossary in the XOOPS docs for this, so we should not have to do anything here, it is included for completeness.??? DO WE NEED THIS?

1.2:ADMINISTRATION USER INTERFACE (ADMIN UI)
1.2.1 control panel>> the names of the different module admin pages.

Looking at some modules, grabbing the names of 'generic' terms, we can start to make a list such as...
Preferences
Permissions (Group's permissions|Permissions|Submit/Approve Permissions|Permission Settings)
Config
Settings

1.2.2 module admin pages >> buttons, labels found on individual pages...
commiting button label
Go!
Submit
Send

jenny - this is where I think we should start, how about we both look over some modules and produce a list each, compare them and then check for the generic terms??

Quote:

I didn't assume that, sorry. How about those doing Action #1 submit their preferred choice of module...just in case.
Also then everyone does indeed know
1.that Action #1 has started
2.which module is being worked on.

Quote:
SImple is definitely good, for all the reasons outlined here
BUT
I am thinking that a 3rd party rather than a core module would be easier.
You don't have to upload and unpack a core module (is that the right term? = any module that comes with the XOOPS package?).

Since I am not a coder, I have no idea but it certainly is possible that a core module has certain features that make it core??

Simple is good, familiarity can help there.
I would go for SmartFAQ.

How about a poll>>>Dave?

Action Item #5: Decide on a test module

This should be fairly easy...

Quote:

Gyah!
Sorry guys! So where are we all? hellooooo.

I can look at Action #2..

Action Item #4: List of terminology

Define which areas require 'standard' terms. UI buttons - 'Submit' c.f. 'Send' for example. Next would be translation of these.

I think Dave asked for PMs so I am hoping that people did which is why it might be quiet here??