[Moose-dev] Re: dropping eyesee

Hi Chris, Your experience is really important for us. If you can give us a script example on how you are using EyeSee, we can guide you in your migration process.

Alexandre On Apr 24, 2014, at 2:54 PM, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: load each month. We are concerned with keeping the services performing at an optimal level, and so need a way to track trending of the performance. We also noted in the past there there was a correspondence between volume of requests and response time, and so wanted to track that correlation as well. So, I periodically gathered this data, built charts on the data with commentary, and published it internally to relevant folks. sucked it into Excel, manipulated it, and made acceptable graphs to look at the data in a glance. That is, until the latest Office upgrade, where I couldn't figure out how to combine graph types on a chart after several days of trying. I took this as an opportunity to explore eyesee (already being familiar with smalltalk) to see if I could get what I wanted. Turned out the answer was yes, and more that that besides. much each is providing), the lines are response time (color relates to two). The thick black line is the overall average response time - over time. This chart is a combination of 9 separate sub-charts. It probably won't win any prizes for attractiveness, but I certainly find it useful. as-is. That said, I expect any new requirements I have for charting, I will utilize GraphET2 and provide feedback/request (if needed). wrote: Could you give us details about your use case? developers, and it will remain so. It is precisely because we want to keep our tools "well conceived" that we need to drop things along the way. EyeSee was started 7 years ago, and at least in the past years it did not see any significant development. A similar story happened with Mondrian (first built in 2005 and dropped last year) and the same will happen with Roassal (to be replaced by Roassal2). years of effort, Moose still has only 200k lines of code (and it is about 50k too large right now). This quite remarkable if you think about how the capabilities increased dramatically over the last years. The only way we can reach this is by continuously reinventing the core parts to build slimmer and more expressive models. their voice every time they think an analysis is not elegant or not concise enough. I know this takes energy, but Moose has the ambitious goal of redefine development and analysis tools and we have to focus on that goal. It might sound bombastic but I am confident that we are approaching a tipping point. We just have to keep pushing. cunningham.cb(a)gmail.com> wrote: wrote: of Moose, that doesn't mean your users don't use the package. I have approached Moose more as a package of well conceived tools, and use them as needed. EyeSee is one of those that I've used in the past (and still use, in fact, monthly) to build performance reports for distribution to a wide audience. It uses charts made up of multiple bar and line graphs to give an overview of aspect of our poerfomrance, and then I externalize it to a PDF (with Artefact). ago, and I'm not likely to upgrade it any time soon, so removing it (for me) will not be an issue. As you pointed out, I could just reload it if I needed too. not yet provide. wrote: wrote: https://code.google.com/p/moose-technology/issues/detail?id=1058&q=kivi… -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev