Date: Wed, 25 Apr 2007 21:03:36 -0700 (PDT) From: L Goodwin <xrayv19@yahoo.com> To: Zhang Weiwu <zhangweiwu@realss.com> Cc: freebsd-questions@freebsd.org Subject: Re: best programming language for console/sql application? Message-ID: <763415.70560.qm@web58109.mail.re3.yahoo.com> In-Reply-To: <1177382049.7382.1.camel@joe.realss.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Zhang (or Weiwu?), I'm surprised there are no good open source bug tracking solutions out there already.
Sorry, I'm not familiar with ncurse, so can't comment on it. The system I developed ten years ago was centered on Informix RDBMS, which included tools for creating character-based forms ("Perform"), reports ("ACE report writer"), and of course queries and stored procs. The shell scripts were used in conjunction with the RDBMS for tasks such as running reports and emailing the results to various individuals and mail groups, and extracting bug regression tests into executable scripts. Overhead was very low -- that's one great advantage of character-based applications (the Windows lovers complained bitterly about it, but we proved it was far more efficient and effective than the junk they were building).
Good luck finding or building a system that meets your needs. I simply don't have time for non-essential activities, as I'm a one-person operation.
Zhang Weiwu <zhangweiwu@realss.com> wrote: If this is a product you developed long time ago, and especially if it's
no longer used or the old company quit this business, it's probably
possible to ask them if they can opensource the old product, and someone
may come up and make it better?
P.S. I was thinking of an ncurse-style interface, so can shell script do
this? I thought shell tools like dialog wasn't powerful enough to
support an user interface required by a bug tracker.
On Mon, 2007-04-23 at 18:07 -0700, L Goodwin wrote:
> I co-developed a UNIX-based multi-product bug tracking system using an
> RDBMS (Informix, ISQL, Perform and ACE), bourne shell scripts, cron,
> and UNIX Mail. This solution also worked on PC clients (we used
> Reflection-X, but I'd recommend XWin32). Our design was selected over
> a PC-only solution that another faction was pushing (we had more UNIX
> clients than PC's at that time).
>
> It had some pretty sophisticated features for the time (some carried
> over from a previous version), including:
>
> Automated email notifications and summaries designed to support our
> software development methodology.
>
> Retrieve and display SCCS deltas to display code changed for a bug
> fix.
>
> Ability to store bug regression tests (manual and automated) in
> several different languages, and automatically generate automated
> regression tests based on several different criteria, including
> Product, Platform, Version Range, and Programming Language. This one
> was my baby (brag).
>
> I've also rewritten HPUX makefiles in bsh to permit execution on
> multiple UNIX platforms (HPUX make has some unique features not found
> in make on other UNIX platforms).
>
> Based on the above experience, I'd recommend shell scripts, though
> this will likely generate some opposition. In any case, if your system
> only needs to run on one platform, I'd use built-in tools.
>
> Since then, I've played around with using perl for CGI scripting
> (hated it), then PHP, which I love for this purpose.
>
> Zhang Weiwu wrote:
> Dear list
>
> This is OT. I am a 4 year php developer and is very familiar
> with
> javascript and awk (familiar = knows and used all functions
> and features
> of the language itself) and I am a 5 year FreeBSD user. Being
> frustrated
> for the lack of a good console-based issue tracking tool (like
> mantis or
> bugzilla), I think I should start to write my own. I'll either
> start
> from scratch or (better) write a frontend for mantis which I
> used for years.
>
> 1. If someone has already started, I should try join him/her
> rather
> than reinventing the wheel. So if someone knows any person who
> is
> starting to work on a slim console-based issue tracker, please
> let
> me know. I already did quit a few searches. I know someone is
> working on a console front-end of G-Forge, but a big software
> like
> G-Forge is not what I am thinking of.
> 2. If I start my own, I think I'll be using a console widget
> library
> (ncurse? because it's famous), an SQL database (no problem)
> and a
> programming language. I never developed console application
> before, so here asking for suggestions on what programming
> language to choose. Non of my known language
> php/javascript/awk
> are suitable so I guess I have to learn a new language anyway.
> The
> language better be easy to learn and work with (C++ is out),
> not
> necessarily have complicated calculation feature (like the
> graphical report mantis makes), not necessarily OOP. I have
> perl
> and tcl in my head now, can you make some recommendations?
>
> Thanks!
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
>
>
>
>
> ______________________________________________________________________
> Ahhh...imagining that irresistible "new car" smell?
> Check out new cars at Yahoo! Autos.
--
Zhang Weiwu
Real Softservice
http://www.realss.com
+86 592 2091112
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?763415.70560.qm>