Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preffered language should not change #324

Closed
NikitaJain11 opened this issue Jul 24, 2014 · 7 comments
Closed

Preffered language should not change #324

NikitaJain11 opened this issue Jul 24, 2014 · 7 comments

Comments

@NikitaJain11
Copy link

The language selected should be maintained throughout the whole session.

Like if Java is selected by someone, it should be same across the entire test unless user changes it explicitly. But here the language is getting changed itself.

@flytoj2ee
Copy link
Contributor

For user, it has default language.
For each component in each round, it has language setting too.

In current code, if user change the component language setting, and then do some operations such as compile/submit/test. It'll keep the component language in this case.

Does it need to change current workflow? If yes, how to change?

@skyhit
Copy link
Contributor

skyhit commented Aug 3, 2014

For user, it has default language.
you mean like in arena applet, is this default language, take affect?

if yes, can we do like user changes default language, it will update the server side too.

@skyhit
Copy link
Contributor

skyhit commented Aug 3, 2014

In current code, if user change the component language setting, and then do some operations such as compile/submit/test. It'll keep the component language in this case.

what if user close the component, and open another problem?

@flytoj2ee
Copy link
Contributor

It could change the user default language. But what's the workflow in pages? The current language setting is for components.

Close one problem and then open another problem, it's using the default java language.

@skyhit
Copy link
Contributor

skyhit commented Aug 3, 2014

the purpose is to remember user's selection during the whole session (like in the SRM).

in advance, remember in any time, unless, user change it purposely.

@flytoj2ee
Copy link
Contributor

How about the following workflow?

a) User changes the language in editor. It'll change the user default language.
b) While user opening the problem, if it already has code, using the current code language.
If the problem doesn't have code, uses the user's default language.

@skyhit
Copy link
Contributor

skyhit commented Aug 4, 2014

yes, this looks good.

@skyhit skyhit closed this as completed Aug 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants