https://bugzilla.novell.com/show_bug.cgi?id=401487
Summary: Include all css and images needed into release of OBS Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: BuildService AssignedTo: rlihm@novell.com ReportedBy: dl9pf@gmx.de QAContact: adrian@novell.com CC: abauer@novell.com, mrueckert@novell.com Found By: ---
Some images and css-files get loaded/included from static.opensuse.org in the webfrontend of a local instance. This slows down browsing the local frontend and also requires bandwith. This could also make trouble if the internet-connection is interrupted.
Feature Request: Include these into the deployment.
https://bugzilla.novell.com/show_bug.cgi?id=401487
User mrueckert@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c1
--- Comment #1 from Marcus Rückert mrueckert@novell.com 2008-06-18 14:03:17 MDT --- note for the devs: imho all image/css/js paths should use the asset helpers from rails so we can easily enable/disable static.opensuse.org from within environments.
https://bugzilla.novell.com/show_bug.cgi?id=401487
User martin.mohring@5etech.eu added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c2
Martin Mohring martin.mohring@5etech.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.mohring@5etech.eu
--- Comment #2 from Martin Mohring martin.mohring@5etech.eu 2008-09-02 04:55:43 MDT --- I would classify this as a real bug, since it is intended to run also a local instance of the OBS. If the main OBS is offline or the internet connection is cut, the web ui is not usable anymore. This must also be an internal problem at novell, since there are now also two internal OBS instances. Is the problem fixed there?
https://bugzilla.novell.com/show_bug.cgi?id=401487
Martin Mohring martin.mohring@5etech.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|Enhancement |Normal Priority|P5 - None |P3 - Medium
https://bugzilla.novell.com/show_bug.cgi?id=401487
User martin.mohring@5etech.eu added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c3
--- Comment #3 from Martin Mohring martin.mohring@5etech.eu 2008-09-02 05:03:48 MDT --- Susanne, how did you solv that in your internal OBS like the one for kernel packages? Does that still work when build.o.o is offline?
https://bugzilla.novell.com/show_bug.cgi?id=401487
User froh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c4
--- Comment #4 from Susanne Oberhauser froh@novell.com 2008-09-03 09:55:45 MDT --- (In reply to comment #3 from Martin Mohring)
Susanne, how did you solv that in your internal OBS like the one for kernel packages? Does that still work when build.o.o is offline?
I think this should be cleaned up with robert's upcoming themeability efforts.
Currently my build.novell.com just looks like the obs.
https://bugzilla.novell.com/show_bug.cgi?id=401487
User rlihm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c5
Robert Lihm rlihm@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #5 from Robert Lihm rlihm@novell.com 2008-09-20 08:15:13 MDT --- I'm working on a reorganisation of static.o.o. In this context I will fix it somehow. In the new Webclient we will make it in a cleaner way.
https://bugzilla.novell.com/show_bug.cgi?id=401487
User lrupp@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c6
Lars Vogdt lrupp@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |lrupp@novell.com Info Provider| |froh@novell.com
--- Comment #6 from Lars Vogdt lrupp@novell.com 2009-03-24 04:26:21 MST --- Robert: any news on your reorganisation?
I'm currently patching another buildservice instance manually to get a different theming. Including headaches if we need an update.
And I think it would be annoying for BS-Admins if their theming changes get lost with the next RPM update.
As far as I see with my limited knowledge, the frontend part can also be splitted completely from the webclient part (so someone can install the frontend on another machine than the webclient, right)?
So what about: 1) splitting up obs-api and obs-webclient 2) splitting up obs-api-branding-openSUSE and obs-webclient-branding-openSUSE
From my single point of view, if should be enough for the
obs-webclient-branding-openSUSE package to include the "app/views" folder. Same IMO for the obs-api-branding-openSUSE package. This would allow everybody to create and maintain his own branding packages.
Maybe it's even an interesting option to create new obs-frontend* and obs-webclient* packages and use the old obs-api package as meta package recommend both. This makes upgrades easier...
Susanne, Martin: as you are currently responsible for the obs-packages, what do you think?
https://bugzilla.novell.com/show_bug.cgi?id=401487
User lrupp@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c7
--- Comment #7 from Lars Vogdt lrupp@novell.com 2009-03-24 04:27:55 MST --- Sorry, I forgot: the "public" should also be included in the branding package.
https://bugzilla.novell.com/show_bug.cgi?id=401487
User froh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c8
Susanne Oberhauser froh@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|froh@novell.com |
--- Comment #8 from Susanne Oberhauser froh@novell.com 2009-03-25 04:56:39 MST --- The UI can be either %config files or a seperate package.
I'd prefer a separate package and a requirement of the webclient/api to the css file the config package provides.
then the MBS (Martins build service), the IBS, the NBS, the PBS, the BBS and all the otheres can have their own little config package and the rest is magic.
To do the split, I'll need to know the config file and all other files that make up a theme.
Speaking of "theme", I like "theme" more than the archaic "branding" in the package name; "rpm --grep theme" gives both "branding" and "theme" package names.
For the split 'webclient' vs 'frontend' what's the value of having them split now? there's so much software on my machine that I don't use, what harm does an inactive frontend on the webclient machine?
https://bugzilla.novell.com/show_bug.cgi?id=401487
User mrueckert@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401487#c9
--- Comment #9 from Marcus Rückert mrueckert@novell.com 2009-03-25 05:50:40 MST --- while our CSS part is pretty well prepared for the theme part. the ruby on rails side is not. you would need to duplicate the whole app/view directory.
for the split question. in theory they could be merged. but in our instance the frontend is much more busy then the webclient as e.g. software.o.o is using the same api.
-
bugzilla_noreply＠novell.com