Opened 10 years ago

Last modified 9 years ago

#12 assigned defect

US/US2/US3 website changes

Reported by: demeler Owned by: dzollars
Priority: normal Milestone: 1.0
Component: ultrascan3 Version: 1.0
Keywords: Cc:

Description

US3 root screen: Menu font doesn't update when the font is changed. Also, none of the help menu entries work, except "About" and "Credits". "Manage Analyte Sequences" under "Database" doesn't work, and should be renamed "Manage Analytes".

Change History (18)

comment:1 Changed 10 years ago by bdubbs

  • Owner changed from bdubbs to gary

comment:2 Changed 10 years ago by gegorbet

  • Owner changed from gary to gegorbet
  • Status changed from new to assigned

comment:3 Changed 10 years ago by gegorbet

A new "Apply Preferences" menu item below "Preferences" allows immediate update of font and frame color preferences.

The help menu items all work on my system, except for "Ultrascan Home". That is fixed by a change to us_help to add a show_URL() function. When help() does not bring up the manual, it is often because the PATH variable does not point to */ultrascan3/bin. Several of the help menu items bring up the manual but with no contents, since HTML files do not yet exist.

Manage Analytes works on my system. I have changed the menu item to "Manage Analytes".

comment:4 follow-up: Changed 10 years ago by gegorbet

Upon further investigation (build on bcf): Manage Analytes was not working because the executable is now called us_analyte_gui. A fix in us changes "us_analyte" to "us_analyte_gui".

Note that the URL invoked with "Ultrascan Home" shows a page with "Ultrascan II".

The new files needed for the manual are: register.html, download.html, license.html.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 10 years ago by demeler

  • Owner changed from gegorbet to zollars
  • Status changed from assigned to new

Replying to gegorbet:

Upon further investigation (build on bcf): Manage Analytes was not working because the executable is now called us_analyte_gui. A fix in us changes "us_analyte" to "us_analyte_gui".

Thanks for fixing that.

Note that the URL invoked with "Ultrascan Home" shows a page with "Ultrascan II".

What I would like to do here is this:
Since we will have to support US-2 for quite some time to come, mostly because people have data stored in the US-2 databases, we will change the UltraScan? root website at ultrascan.uthscsa.edu to show links to both platforms at the top level. The website will be re-organized, and I will ask Dan to work on this. We will set up virtual domains for ultrascan2.uthscsa.edu and ultrascan3.uthscsa.edu that have platform-specific information, and keep the ultrascan.uthscsa.edu domain name for general UltraScan? information. For now, we should put a stub in the root directory of www.ultrascan3.uthscsa.edu and point the home page for US-3 there, and also have a link to this (us-3) trac site and the new us-3 lims site.

The new files needed for the manual are: register.html, download.html, license.html.

Again, stubs on ultrascan3.uthscsa.edu (already existing) should be added for these files.

Perhaps Dan and Jeremy can set this up and request the new DNS entries as well.

Thanks, -b.

comment:6 Changed 10 years ago by gegorbet

I created the license.body and images/license.png files necessary for license.html. When I finished, I realized that the information presented for this "UltraScan License" menu item is the same as what you would want for "Register Software".

I leave it to Dan, but either one of the two Help menu items should be removed, or the links in the us.cpp program should be to an identical HTML. Or, perhaps, I am wrong about these two being essentially the same documentation.

I have not committed the "license" files pending a decision on whether it should be "register" or if us_win_data.cpp changes should be made.

comment:7 follow-up: Changed 10 years ago by demeler

One additional comment about the root window: why is there a function "Apply Preferences"? Shouldn't that happen automatically when you click on "Save" in the preference menu? Unless I misunderstand the purpose of this function (in which case it should be renamed to be clear), I vote for doing this automatically every time when the preferences are changed/saved.

comment:8 in reply to: ↑ 7 ; follow-up: Changed 10 years ago by bdubbs

Replying to demeler:

One additional comment about the root window: why is there a function "Apply Preferences"?

Would you please clarify what you mean by 'root window' here. I don't see any "Apply Preferences" in the root window.

comment:9 in reply to: ↑ 8 ; follow-up: Changed 10 years ago by demeler

Replying to bdubbs:

Replying to demeler:

One additional comment about the root window: why is there a function "Apply Preferences"?

Would you please clarify what you mean by 'root window' here. I don't see any "Apply Preferences" in the root window.

when you type 'us' you get the root window. The second menu item (Edit) has this entry.

comment:10 in reply to: ↑ 9 Changed 10 years ago by bdubbs

Replying to demeler:

Replying to bdubbs:

Would you please clarify what you mean by 'root window' here. I don't see any "Apply Preferences" in the root window.

when you type 'us' you get the root window. The second menu item (Edit) has this entry.

Sorry, I hadn't updated my instance for the changes Gary made.

comment:11 follow-up: Changed 10 years ago by gegorbet

The reason there is an "Apply Preferences" menu item is that it would be difficult to automatically update after preference changes. The preference dialog is just us_config, launched by the us main. The settings are changed, but for the main to detect that you have completed your settings, it would have to continually monitor the us_config process or there would have to be a new set of signals and slots engineered in both us and us_config.

That seems like an awful lot of hassle for something that would seldom be done. The user just has to click one more menu item to have the settings re-read and applied.

comment:12 in reply to: ↑ 11 ; follow-up: Changed 10 years ago by demeler

Replying to gegorbet:

The reason there is an "Apply Preferences" menu item is that it would be difficult to automatically update after preference changes.

Correct me if I'm wrong: After saving preferences in us_config, all newly launched applications will accept the new preferences *without* the need to click on "Apply Preferences". So this button really only applies to the root window (us itself), correct?

The preference dialog is just us_config, launched by the us main. The settings are changed, but for the main to detect that you have completed your settings, it would have to continually monitor the us_config process or there would have to be a new set of signals and slots engineered in both us and us_config.

Maybe it would be nicer to just connect to us_config's process signal:

void finished ( int exitCode, QProcess::ExitStatus? exitStatus )

and perform this action.

I don't think a polling would be required.

That seems like an awful lot of hassle for something that would seldom be done. The user just has to click one more menu item to have the settings re-read and applied.

Maybe. I am not sure how much hassle it would be to connect to us_config's finished(...) signal and reread the config.

comment:13 in reply to: ↑ 12 Changed 10 years ago by bdubbs

Replying to demeler:

Correct me if I'm wrong: After saving preferences in us_config, all newly launched applications will accept the new preferences *without* the need to click on "Apply Preferences". So this button really only applies to the root window (us itself), correct?

Yes.

Maybe it would be nicer to just connect to us_config's process signal:

void finished ( int exitCode, QProcess::ExitStatus? exitStatus )

Too much work. Just perform the reapplication of US_GuiSettings unconditionally upon return of us_config. If the settings are unchanged, it shouldn't affect the window.

comment:14 Changed 10 years ago by gegorbet

I hadn't realized that the us main already had a strong mechanism for monitoring launched processes. The Preferences us_config process is relative index 0, so in the terminate() process loop, all that was needed was

if ( index == 0 )

apply_prefs();

The Apply Preferences menu item has been removed.

comment:15 in reply to: ↑ 5 ; follow-up: Changed 10 years ago by dzollars

  • Owner changed from zollars to dzollars
  • Status changed from new to assigned

Replying to demeler:

What I would like to do here is this:
Since we will have to support US-2 for quite some time to come, mostly because people have data stored in the US-2 databases, we will change the UltraScan? root website at ultrascan.uthscsa.edu to show links to both platforms at the top level. The website will be re-organized, and I will ask Dan to work on this. We will set up virtual domains for ultrascan2.uthscsa.edu and ultrascan3.uthscsa.edu that have platform-specific information, and keep the ultrascan.uthscsa.edu domain name for general UltraScan? information. For now, we should put a stub in the root directory of www.ultrascan3.uthscsa.edu and point the home page for US-3 there, and also have a link to this (us-3) trac site and the new us-3 lims site.

The new files needed for the manual are: register.html, download.html, license.html.

Again, stubs on ultrascan3.uthscsa.edu (already existing) should be added for these files.

Perhaps Dan and Jeremy can set this up and request the new DNS entries as well.

Looking at the website this all seems relatively straightforward. I'll set up the sites in my sandbox and you can have a look.

comment:16 in reply to: ↑ 15 Changed 10 years ago by dzollars

Replying to dzollars:

Looking at the website this all seems relatively straightforward. I'll set up the sites in my sandbox and you can have a look.

What kind of look and feel should the ultrascan3 site have? We could preserve the existing look, or we could start migrating to a newer, more modern look. I propose using something kind of like the LIMS3 code I've been developing---it can be customized in lots of ways. For instance, a new banner across the top, different colors and dimensions. The left column can be resized and placed either on the left or the right, or you could take it out entirely and use the drop down menus across the top for navigation. Actually, this is the latest thing in web design---one or more rows beneath a banner with different levels of drop-down menus in each of them. The top banner is simple, most likely a solid color, and there is a footer with the same design. In between you now have room for 2-3 columns of main content, perhaps with lists of links to all the places one might go from there.

Another idea is to use the UTHSCSA templates. I find them limiting, however, for a data-oriented site. Dimensions are pre-set, and much of the page is taken up by navigation. I'm comfortable with them, though, if you want to use them.

comment:17 Changed 9 years ago by bdubbs

  • Summary changed from root window changes to US/US2/US3 website changes

comment:18 Changed 9 years ago by bdubbs

  • Milestone changed from alpha to 1.0
Note: See TracTickets for help on using tickets.