Jen
Under those considerations you are totaly right.

The remove & delete example is an excelent ilustration to your point.

Look at the "install" a module procedure:

You upload the folder of the module you want to install into the modules folder.
(How is this action called?)

You select the module and install it using the
System:Modules:(sencond half of the pannel)
(to fancy may be to describe this way.... all because no title there)

Then you can deactivate (with a very extrange procedure because you click on a check mark), or you re-install with a symbol on the rigth, or you uninstall with a new icon that appears only after it has been deactivated)

This is a "core" procedure to any XOOPS user
ant i find it very hard to describe (even to understand).

So Jen you are righ

What do you think about the color strategy?

Jorge Barrero

Hello

This an idea that may help to start "hunting" terms

take a look and let me know what you think

http://www.virtualpeople.com.ve/xoops/Example/XoopsTerminology.doc

About the wysiwyg editors.

Usually I end up editing html on dreamweaver, copy & paste on th html mode for several reasons.

1. I can not use theme css styles, (I had to use a triki way just to se the same styles of the theme on the SPAW editor I imagine the kiovi editor has the same problem)

2. There is no way to edit the css form the editor.

3. There should be a better way to create folders for images. I think all images shoul be placed in only one folder (and folders with in) instead of puting them just anyware.

4. It would be a killer app if it could write Math notations (But this is may be to much to ask.

5. Table manegament is really difficult.

I have a mailing program and uses a simple strategy. Every time you need to edit an html field on the data base. the editor apears on a blank window. Just the editor, with every function needed.

I think that is really nonsense to have somthing different to a full fetuared HTML editing software if what you need is to edit html. Other wise let people just write plain text.

a separate window can have major advantages.

You can use any editor you like (and select it form the XOOPS Adm Panel).

You do not need to display a bunch of icons if you are editing other fields and no html area is involved.

I would like to help with the project. I think is a very good idea.

Tks

Jorge Barrero

Sorry I put the old address on example 2

this is it

http://www.virtualpeople.com.ve/xoops/Example/index2.htm

Jorge

I made a dummy No 2 on this address

http://www.virtualpeople.com.ve/xoops/Example/index.htm

see if this fits your expectations

Ok

I will make another dummy with your suggestions to see how it looks.

I will make a clone to compare.

I will sugest away to select the module saving space ad displaying the icon at te same time.

About the language selection I agree.

About turn on/of the help text (wonderful this is team work you know).

The breadcrum, probably turn on/of also is a good idea.

As soon as I have the changes made... I will put them on the web

On the other hand take a look to this uncomplete file and comment it.

http://virtualpeople.com.ve/xoops/Example/SystemModuleTerminology.xls

The idea is to complete this with the other two spread sheets posted before

thanks

Jorge Barrero

Ok

With all this Ideas, lets start with the System Module. Lets go deep into standard terminology. Lets take each and every piece of it and work it out.

We cah have an Excel sheet with all used terms (actua), the ones sugested, then the definition and the comments.

This is a good module to start with. All modules should follow this one.

I will make a spreadsheet with all terms and post it here.

Take a look at this dummy page (NOTE: It does nothing, is just to ilustrate the idea)

http://www.virtualpeople.com.ve/xoops/Example/index.htm


I am considering to start a series of recomendations on look and feel including the terms to be used, how to mantain consistency of language among modules.

The first sugestions is to change the way that modules are selected (I placed a Menu)

The second is to include a name below each module (so that when you change a module's name you can remember the used one.

The third is to include a big title with ne name of the module (When you select the name at the left, this is the exact name that sholud appear)

The forth is to include a breadcrum & the language used.

The fifth is to arange the options in a "Menu style" acording to logical groups.

The sixth is to display the "pannel", with tags on the left and variables on the right. But, any explination is at the rigth side (not at the left). This is a good idea borrowed from Noah Module.

What do you think?

This is nice work.

I checked both work sheets, It woul be ideal if we could do this online in some way.... I am not a good programer but Let me try something

I think this is the way

Terminology is a very important issue. Is the basis and the core of the system.

Two problems arrive:
Consistency between modules
Consistency between languages

I sugest matrix in excel. colum 1 is the english term, colum 2 is the definition and then on one colum for eact translation.

Eventualy we can make this structure work for a data base system so ypu can "borrow" terms from other modules, and increase consistency.

A good example has been the User Interfase Guidelines that Apple released (early begining)

just an idea, I woul like to help on this topic.

Jorge Barrero