Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
Re: [yast-devel] WebYaST: Vendor service - Summary + TODO
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Mon, 24 Aug 2009 12:33:42 +0200
  • Message-id: <20090824103342.GC11052@xxxxxxxxxxxxx>
* Ladislav Slezak <lslezak@xxxxxxx> [Aug 21. 2009 11:47]:

Web UI (webclient)
==================
- testsuite
- design the UI (talk to mschmidkunz), may be different for System vs.
Custom
services

The question is if vendors would like to change "Custom Services" to a better
name
(with real service name).

The'll certainly do.

With current implementation they need to change the name directly in
.yml config file. Is that OK?

I'd guess so. But how does this match with translations ?


- show the service status:
- for system services, probably first show list of services, that update
the
status of each one service with AJAX calls

Maybe one AJAX call for all services could be better (I'm not sure about the
overhead, running 30 requests in parallel instead of big one might be too
slow.)

Any idea? I'm not an AJAX expert...

Just don't bother with 'system' services now. Its out of scope for
WebYaST '1.0' currently.


- custom service is expected to be only one currently, so the status
could
be load on loading index page

I'd keep the same functionality, this creates unnecessary complexity. More
over
reading the current status might take long time so the complete page would be
displayed after a (possibly long) delay.

The delay shouldn't be a problem. Getting the patch status is also
taking its time.


Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >