On Mon, May 9, 2011 at 8:05 PM, frescha <fres...@unitedseed.de> wrote:
> Hi Jean,
> First at all, I want to thank you and all other Shinken developers. I'm
> glad to see how Shinken grows.
> I think a own User Interfcae can be a big plus for Shinken. A new interface
> could unify the advantages of Shinken and a modern interface with features
> that a operator/admin/manager realy needs. I agree with you, that the points
> root problems, impacts and criticity are very importent and the focus of the
> new UI must be on simpleness (like the KISS principle).
> I think another important point is that the new UI should be expandable. It
> should be easy to customise or add new features. I try to explain it. A few
> years ago, I used the CMS TYPO3 and I was amazed how expandable this CMS
> was. The TYPO3 Core has a clear focus on the root problems but it was and
> still is quite easy to add new features. The result was that a lot of people
> wrote extentions and shared them with the community. Such a dynamic
> community would be great for Shinken.
> My personal "perfect" UI has an simple UI core, is focused on the business
> and is modularly expandable.
> I think with a elaborate concept of the UI project could be fine.
>
> Hi,
Thanks :)
I think you are right, the UI core should be very small but hugely modular,
like the broker in fact. It should be easy to add new views, and access to
data and user information (should map contacts, it's simple but very
efficient).
I think we can stay on this mailing list for the UI, it should not be a
problem, especially because it will have a strong link with broker modules.
What for the source repository? I think stay on the same is good, because it
will be far easier for users to get only one source and install it. We can
also use the Shinken lib to help us to analyze some objects for example or
solve a bug in livestatus or another broker module or interface and be sure
everyone will got the same global version for both tools.
Like for the core, it should be easy to setup (ok, not too hard :) ) and get
few but useful dependencies. For such web UI, I think about swgi module for
an Apache/nginx presentation, or a CherryPy module for standalone run or an
install behind Apache or nginx. We should take the most easy and efficient
for us. I think CherryPy is quite easy to understand and setup, I'll give it
a try. If someone get a good knowledge about Python web module, it's time to
talk about it :)
I'll push what I worked on the last week, the mockup of the main view I was
talking about and instruction how to install it. It's a check_mk multisite
base with a swgi modification (the vanilla multisite use mod_python but it
make impossible to install under Windows) so it will be very easy to setup
behind an Apache. Don't take it as a "we start with it", but like a real
mockup support and a look at what we can do with wsgi and if we should use
cherrypy or another framework. When the conception phase will be done, we
will see if we keep this as a base or if start from scratch is a better
thing.
If you got some ideas about the theme we can use to show the shinken spirit
it can be a good thing too, I'm very bad in css, so it can help us a lot for
starting :)
I've got such theme in preparation that show a little this in this mockup,
but I'll need a real graphic people for getting a look looking result :p
So let's start. It will be easy for everyone to talk about a real mockup
than with emails, so I'm posting it :)
Jean
> Andreas
>
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
