deanman | Hi, i would like to make a minor customization on the gui for a demo presentaiton. In detail, i would like to make a small border on the top frame. Any tips ? | 08:04 |
---|---|---|
urulama_ | hi, deanman | 09:23 |
=== urulama_ is now known as urulama | ||
urulama | deanman: we don't really encourage to change the UI, as it's been thoroughly user tested and design carefully considered to be as it is | 09:24 |
urulama | deanman: may i ask what that border would gain you? | 09:24 |
deanman | it's some plain "beautifying" for demo purposes only | 09:26 |
urulama | deanman: and you need the gui to run in a real model? or just build it and run it in sanbox mode, no real models involved? | 09:27 |
urulama | asking as that has implications that you'll also have to build the gui and put it in a charm and deploy it | 09:27 |
deanman | urulama, initially we simply modified a bit the css on a deployed gui charm, then we started considering whether we can tweak it even more and clone the code | 09:32 |
deanman | It was a bit difficult to dig into this framework you are using, so that's why thought asking here, maybe some hints since we simply want a simple dib with a background color on top menu bar. | 09:34 |
deanman | div* | 09:36 |
urulama | antdillon: ^ can you give a quick pointer to deanman here, please | 09:39 |
urulama | deanman: changing deployed gui will be easy, otherwise you'll have to go through whole packaging and charming process | 09:39 |
urulama | deanman: as it's open source you can clone it and create your own charm, of course | 09:40 |
deanman | urulama, Thanks for the chat, well from first look it seems that the HTML is built somehow dynamically and we cannot change it once deploy, we can only customize the CSS. | 09:41 |
deanman | deployed* | 09:41 |
antdillon | deanman, would you be able to add a top border to the html element via the inspector and show that in the presentation? | 09:42 |
deanman | antdillon, well i could but some would be checking the provided link offline so it wouldn't be the same exprience, but anyway, css customization it's fine for now. | 09:44 |
deanman | urulama, Do you plan to update juju-gui for 2.0 ? Or any plans on changing the framework ? | 09:44 |
urulama | deanman: you mean juju 2.0? | 09:45 |
deanman | urulama, yeah! | 09:45 |
urulama | deanman: it's already supported, you can use beta3 or less with it | 09:45 |
urulama | deanman: framework? we use react, it's something we like :) | 09:45 |
antdillon | deanman, if you have access to the deployed HTML you could add a css file to the header as a means to inject css remotely | 09:46 |
deanman | I meant the YUI library | 09:46 |
urulama | deanman: oh, yes :) that is in plan | 09:47 |
deanman | Any clues to which framework are you thiking to switch to ? | 09:49 |
urulama | no final decision yet | 09:52 |
kjackal | Hey everyone, what is the process for removing a charm from the store? eg https://jujucharms.com/apache-zookeeper/trusty/0 that is not deployable anymore | 10:29 |
kjackal | That is revision 0 is not working. https://jujucharms.com/apache-zookeeper/trusty/1 is fine | 10:43 |
urulama | kjackal: we don't remove revisions that are broken, but we do have a better publishing process in place, which will be announce soon | 16:09 |
urulama | kjackal: i mean, if it's revision 0 and you already have revision 1, we don't remove revision 0 ATM | 16:09 |
kjackal | thank you urulama, I assume there is on our roadmap to have a process to remove them at some point, right? Becuse the broken revision is the first hit in a google search | 16:11 |
urulama | kjackal: yes, it is | 16:12 |
=== urulama is now known as urulama|afk | ||
* hatch waves to rick_h_ | 16:45 | |
rick_h_ | :) | 16:45 |
=== urulama|afk is now known as urulama|eow |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!