Jump to content

Black Pearl

Members
  • Posts

    410
  • Joined

  • Last visited

  • Days Won

    13

Posts posted by Black Pearl

  1. Seems like you were almost running up that hill. When hiking in the mountains, you should not go for the distance but for the elevation.

    With the data from the link you did 600m. Normal speed is 200m per hour. In my best time I did 200 m in about 45 min.

    Also hope you have good boots, as most accidents in the alps happen due to normal streetware.

    One day I was hiking in the swiss alps doing Arosa -> Davos and back on the same day (this is 1.200m up, 800m down and back, total distance about 50 km). It was already late afternoon so I had no time left to take another route, when I faced a very dangerous section. Everything was sliding down 200m and the trail was maybe 20 cm wide. I went crazy and could not walk that path. I ended up crawling on all 4 with closed eyes. Since then I suffer heavily from acrophobia.

    The best I ever did was the Tiger Leaping Gorge in China.

    Felix

  2. You should be able to use the built-in units of the controls. The user can change them by tyoing in mm, in, ft...

    Select visible->Unit Lable and type in mm. You will need to convert your data by cast to unit.

    Felix

  3. About Fogbugz: I really would like to take a try. But I need it 'free' (that seems to ok with Joel/FogCreek) and off-line (and as I read about the free one, they even host it in their servers). Is it possible to install it on my intranet?

    Felix

  4. I use Mantis. I consider the interface a bit ugly (same for bugzilla). But that's ok for internal use.

    The setup I did not do myself but my more IT-focused co-developers. I guess you need to know how to set up a SQL server and things like that. Doesn't seem to complicated, I just try to avoid any code involving text...

    Felix

  5. Just a step in from the side. Is the reverse of a 'WORM' a valid design. I confess, that I use globals as duct tape when I need to fix something 'right now'. So if I go with the WORM design, I reduce the risk of that duct tape falling off after delivery of the code. Is the same ok if I code Write Many Read Once?

    To give a practical scenario: I have various abort conditions (Panel Close, Stop Button, Error) and one measurement routine that monitors the abort flag.

    Ok, it is read 3 times: Init (Default value), Measurment routine and Reset (after routine stopped).

    Or is there a way to make this a reusable 'Abort' classs on it's own...

    Felix

  6. I shouldn't post late sunday night, but I can't resist. I have started to do some reuse vi's in the last half year. Deployment was a copy on the USB stick to my fellow programmers. I'm still in a process to learn the pitfalls on my own. This is mainly about writing them in a way, that I will never break my projects.

    As I'm pretty sure that I won't get a VIPM budget, I also was looking on SCC to at least give my some ways. My idea (it's SVN) was to have a root hierachy of LV versions, below that the trunk/tags and have the user (me at the moment) check them in on the user.lib folder. I only use the trunk for now (it still is a private project for me).

    My own impression is, that I save time against not using any of these (reuse, SCC), but I would be better of having a management tool for that (VIPM Pro). But for me currently the biggest barrier is to get the other developers use such tools (and they do a good job despite it).

    So the biggest pitfall? I threw vi's out of the reusable, other projects did rely on. Very intentionally. And also decided to get some older concepts back in. Was worth the troubles, as I had used OpenG builder to have an llb copy where the originals where in. In fact the problems I did survive with an older concept of having a 'reuse' folder somewhere on my HD which maintains a copy of what is not in the user.lib and SCC.

    But, problem unsolved: how to get my team working with it/benefit from it?

    Felix

  7. I could imagine that you can make some impressive toy for some managers with this, when you map the complete production facility with equipement status, analysis of bottlenecks, material flow ...

    Felix

  8. I did compare both by webcast only. I would use the JKI one, not only due to the price.

    Using the NI UTF gives you support and a 'ripe' product. But it's not counting that much as JKI will also give you support thru LAVA and as it is based on xUnit, the core is rock solid. And work will continue...

    Why I prefer the JKI one is actually that it seems more light-weight. If I do test driven developement, I should (my opinion) code/design for easy testing (which theoretically will make 'good' code). And I want little effort to define the tests.

    Turning the coin, NI UTF seems to give you more features for comparison of actual and required output, as well as to check code coverage.

    Felix

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.