search

dasho2020 / glossword

Automatically exported from code.google.com/p/glossword
0 stars 0 forks source link

ideas: edit more terms simultaneusly; usability for old people and editors #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please provide any additional information below.

 When working on a dictionary it is important to be able to overview the 
terms also while you are editing one.

Look at the file for an example of such an edit mode.

Explained:
J n **** 
edition 2 by jensl - edited from the letter j - show me all editions
[[=joule]] J (=jxulo)

(commentary):
 this is a comment
-------------
1. often the people who now how to make a dictionary are old. -> keep it 
simple
2. only show the absolute necesary fields by default when editing
3. enable a history (done in GW)
4. enable the user to write in a comment and show autom. the last comment
comments are important to keep consistency, and to socialize a little bit
5. text size should be adjustable and saved via e.g. a cookie.
6. easy printing of ranges of terms should be possible.

what do you think?

Regards
/D

Original issue reported on code.google.com by d.prisk...@gmail.com on 6 Apr 2008 at 10:53

Attachments:

GoogleCodeExporter commented 9 years ago 
oh, forgot one:
7. enable the editor (first thing after login) to continue editing from where 
he 
left -> e.g. save the last url to the database

/D

Original comment by d.prisk...@gmail.com on 6 Apr 2008 at 10:55

GoogleCodeExporter commented 9 years ago 
> J n ****

Sorry, I did't understand it completely.

> 2.

The list of avaliable fields is configurable in dictionary settings.
You can check only "Definition" to get a quite simple HTML-form.

> 4.

It is hard to implement comments into the software.

> 5.

Any user can adjust text size in a browser. 
I made similar controls for glossword.info site, but to made it for Glossword,
it is required to review visual themes, including CSS. Currently, there is 
no place for the controls like "a+ a- a*".

> 6.

Added to the task list.

> 7. 

Will try to implement it for 1.8.8.

Original comment by dmitry.s...@gmail.com on 7 Apr 2008 at 7:32

GoogleCodeExporter commented 9 years ago 
>> J n ****

>Sorry, I did't understand it completely.
No problem, here is another example

the "prop" is just a grammatical marker "proper name" because Moskva is the 
name of
the city in danish.
- this field is nothing special - GW already have this implemented in the 
abbr-field

the **** is also a marker for how often the word is in a danish context. this 
is very
useful when you as a team of dictionary writers _have_ to prioritize the list of
words (100.000 in this ekzample).

Original comment by d.prisk...@gmail.com on 7 Apr 2008 at 7:31

Attachments:

GoogleCodeExporter commented 9 years ago 
>> 2.
>
>The list of avaliable fields is configurable in dictionary settings.
>You can check only "Definition" to get a quite simple HTML-form.
Hmm it might be simple for the two of us, but take a look at the picture and 
imagine
yourself being 60+ years old and unskillful at typing and navigating on a PC.
It is not simple enough in my opinion. 
I think the "date" field show be hide-able, likewise the edit of "alphabetic 
order
1-3" and the "definition edit-toolbar" (the one with formatting-options. The 
old ones
don't need it and will only get confused. They just want to put in text and 
save ->
next term.
>
>> 4.
>
>It is hard to implement comments into the software.
I understand. 
Would it not be possible to make a separate table in the database for the 
comments?
each of them could refer to a termid or something like that.
Or better yet, make them a part OF the term so that you have a comment-field as 
you
have a see-field.
---------------
Furthermore
8. edit more terms at the same time (maybe this could be done via a check-box
solution in the internal-search? "edit the selected terms"

9. (during edit of a term) an option "edit the next term" (in alphabetic order) 
(see
edit.term.png)  AND an option to do this both after making changes and as a 
"discard
changes and go to next" (a previous-link should of course also be added.)
- this should also be sensitive to incomplete terms eg.: I search for incomplete
terms, and start editing the first. i then want to edit the next incomplete 
term -
what do I do?

10. an option to search only in translations.

Original comment by d.prisk...@gmail.com on 7 Apr 2008 at 9:03

Attachments:

GoogleCodeExporter commented 9 years ago 
> 4.
Comments need to be moderated. It is not so difficult to add a comment. But it 
will
take a lot of time to develop the system which allows to manage them.

> 8. edit more terms at the same time
In this case, can you imagine the length of HTML-form? The advantage of editing
several terms at one will be completely destroyed by heavy and endless 
HTML-form.

> 9.
> I search for incomplete terms, and start editing the first.
Then select After posting... "Open last search results".

Previous/next navigation could be added to future releases. However, it would be
version 1.8.9 or later.

Original comment by dmitry.s...@gmail.com on 9 Apr 2008 at 11:58

GoogleCodeExporter commented 9 years ago 
>> 4.
>Comments need to be moderated. It is not so difficult to add a comment. But it 
will
>take a lot of time to develop the system which allows to manage them.
Moderated? Hmm is that really necesary (for internal comments)? 
If you are only a handfuld of people working on a dictionary in the "backend" 
of the
system, then it is not really a problem with moderation of the internal 
comments.
A note: Above 10 collaborators is to my knowledge not unusual in dictionary
creating-teams.
>
>> 8. edit more terms at the same time
>In this case, can you imagine the length of HTML-form? The advantage of editing
>several terms at one will be completely destroyed by heavy and endless 
HTML-form.
I don't quite understand, can you show me an example og explain it in another 
way?

>> 9.
>> I search for incomplete terms, and start editing the first.
>Then select After posting... "Open last search results".
>
>Previous/next navigation could be added to future releases. However, it would 
be
>version 1.8.9 or later.
Very fine.

Thank you for your quick response.

Original comment by d.prisk...@gmail.com on 10 Apr 2008 at 6:45

GoogleCodeExporter commented 9 years ago 
> Moderated?
I see, you are looking for an additional field called Comments. Sorry, but at 
this
time no additional fields could be added. It the beginning, it was Term and
Definition. Lately, fields See also and Source were added. Today the support of
fields become too complicated. I'm looking for a solution which allows to 
create a
custom fields.

> 8. edit more terms at the same time
I hope attached file explains all.

Original comment by dmitry.s...@gmail.com on 13 Apr 2008 at 6:15

Attachments:

GoogleCodeExporter commented 9 years ago 
>> 8. edit more terms at the same time
>I hope attached file explains all.
Hmm. I get the point, but I think that the layout easily could be more 
compressed.

The examples below are not pretty, but I think they illustrate my point. :)

If we remove the menu at right (during this special edit-mode), I think that 
there
are room for 4 terms at once.
1  |  2
--------
3  |  4

About the def-field:
Often when creating a dictionary a definition is not important. I know a lot of
dictionaries without them. Therefore the def-field could be hidden as standard 
as well.
These hide-options could be set in the edit-dict-page eg. via checkboxes (and
remember the explanation between disable and hide).

Regards
Denizo

Original comment by d.prisk...@gmail.com on 23 Apr 2008 at 6:08

Attachments:

GoogleCodeExporter commented 9 years ago 
At this moment it is impossible.

Original comment by dmitry.s...@gmail.com on 23 Apr 2008 at 6:35

GoogleCodeExporter commented 9 years ago 
> 7. enable the editor (first thing after login) to continue editing from where 
he 
> left -> e.g. save the last url to the database

Added to 1.8.8

Original comment by dmitry.s...@gmail.com on 24 Apr 2008 at 7:18