Re: Test driven programming, was Re: VB to Python migration

2014-10-26 Thread Viorica Gheorghiu
-- https://mail.python.org/mailman/listinfo/python-list

Re: VB to Python migration

2006-02-02 Thread drewdr
On Fri, 27 Jan 2006 23:48:51 GMT, Josh <[EMAIL PROTECTED]> wrote: >We have a program written in VB6 (over 100,000 lines of code and 230 UI >screens) that we want to get out of VB and into a better language. The >program is over 10 years old and has already been ported from VB3 to >VB6, a job wh

Re: Test driven programming, was Re: VB to Python migration

2006-02-02 Thread Grig Gheorghiu
Thanks for the insightful answer, Magnus. I have a lot of stuff to digest from your message :-) Maybe I'll continue the discussion on the mailing list you mentioned. Grig -- http://mail.python.org/mailman/listinfo/python-list

Re: VB to Python migration

2006-02-02 Thread Michael Tobis
An incremental approach and a redesign are not the same thing. It might be insurmountably difficult to acheeve both in a move to another platform. mt -- http://mail.python.org/mailman/listinfo/python-list

Re: Test driven programming, was Re: VB to Python migration

2006-02-02 Thread Magnus Lycka
First of all, while I use TextTest, I'm fortunate to be surrounded by TextTest experts such as Goeff and Johan here at Carmen, so I'm not a TextTest expert by any measure. I probably use it in an non- optimal way. For really good answers, I suggest using the mailing list at sourceforge: http://list

Re: Test driven programming, was Re: VB to Python migration

2006-02-01 Thread Grig Gheorghiu
Magnus, I've been writing TextTest tests lately for an application that will be presented at a PyCon tutorial on "Agile development and testing". I have to say that if your application does a lot of logging, then the TextTest tests become very fragile in the presence of changes. So I had to come u

Test driven programming, was Re: VB to Python migration

2006-02-01 Thread Magnus Lycka
Josh wrote: > As for the testing, that's something we'll need to learn about. I've > read some articles about test driven programming in relation to extreme > programming. Can you give me links to any good sites explaining how this > all works? (Off list may be better for these off-topic links)

Re: VB to Python migration

2006-01-31 Thread Josh
Magnus Lycka wrote: > I suppose that you need to present a lot of differnt kinds of data, > and that you need to provide various search parameters etc for > different data sets, but this sounds like something that might be > very few screens that adapt to some kind of meta-data, perhaps XML > des

Re: VB to Python migration

2006-01-31 Thread Magnus Lycka
Josh wrote: > I understand what you are saying, and I'm sure the tasks our program > does could be made much cleaner. But, implementing an ERP which is > basically what we have, is a large project and the users need (or maybe > just want) access to lots of information. I'm not pretending to kno

Re: VB to Python migration

2006-01-30 Thread Josh
Steven D'Aprano wrote: > I suggest you hire a couple of experienced Python developers, pick half a > dozen screens, say three simple screens and three complex ones, and build > them in Python. That will give you an idea of how much work is involved. > Don't get your VB developers to try to port it

Re: VB to Python migration

2006-01-30 Thread Josh
Magnus Lycka wrote: >> Rewrites are always good and result in smaller code base if features >> are not added. However, I doubt that will make the screens fewer. Lines >> of code? Certainly. > > > That depends on whether you just refactor the implementation > of if you look at the problem domain w

Re: VB to Python migration

2006-01-30 Thread Josh
Magnus Lycka wrote: > mxODBC is probably the best way to talk to Jet in a way (DB API) > that makes it reasonably easy to port the data to another RDBMS. > Writing multi RDBMS applications is a whole chapter in itself, > if not a subject for a whole book. > > Whether to use an ORM such as SQLObj

Re: VB to Python migration

2006-01-30 Thread Josh
Thomas Ganss wrote: > You haven't specified where your main pains are. > Do you have at least rudimentary architecture ? > How often do you have code reviews / refactored your code ? > Have you been striving for good code ? Is it a total mess ? Umm... We have been striving for good code, but being

Re: VB to Python migration

2006-01-30 Thread Josh
DH wrote: > see vb2py to help the conversion > http://vb2py.sourceforge.net/ > or if you want to convert vb6 to vb.net instead, there are tools from > microsoft and others to help with that, such as: > http://www.microsoft.com/downloads/details.aspx?FamilyId=10C491A2-FC67-4509-BC10-60C5C039A272&di

Re: VB to Python migration

2006-01-30 Thread Josh
Jon-Pierre Gentil wrote: > I would look into Qt, PyQt, and the Qt Designer. It'll provide one of the > easiest ways of porting your existing GUI dialogs into Python. Start > building and componentizing your code. In VB6, all classes are flat under > a single branch of a project tree, whereas in

Re: VB to Python migration

2006-01-30 Thread Josh
Nicolas Kassis wrote: > Josh wrote: > > >>We have a program written in VB6 (over 100,000 lines of code and >>230 UI screens) that we want to get out of VB and into a better >>language. The program is over 10 years old and has already been >>ported from VB3 to VB6, a job which took over two years.

Re: VB to Python migration

2006-01-30 Thread Magnus Lycka
Ravi Teja wrote: > Rewrites are always good and result in smaller code base if features > are not added. However, I doubt that will make the screens fewer. Lines > of code? Certainly. That depends on whether you just refactor the implementation of if you look at the problem domain with a different

Re: VB to Python migration

2006-01-29 Thread Ravi Teja
Magnus Lycka wrote: > Ravi Teja wrote: > > 230 UI screens is a lot. An app of that nature is not something people > > commonly do in Python (although I would be happy to see people show me > > wrong). > > Maybe not, but I don't doubt that it's reasonable to replace a > VB app with 230 UI screens wi

Re: VB to Python migration

2006-01-29 Thread Magnus Lycka
Ravi Teja wrote: > 230 UI screens is a lot. An app of that nature is not something people > commonly do in Python (although I would be happy to see people show me > wrong). Maybe not, but I don't doubt that it's reasonable to replace a VB app with 230 UI screens with Python code. A code of that s

Re: VB to Python migration

2006-01-29 Thread Magnus Lycka
Josh wrote: > We currently use a MS Access back end and need to migrate to a proper > SQL server. We need to leave options open for SQL Server (for customers > who want to use existing infrastructure) and something like MySQL or > PostgreSQL. But in the mean time, we need to be able to access an

Re: VB to Python migration

2006-01-28 Thread John M. Gabriele
Josh wrote: > We have a program written in VB6 (over 100,000 lines of code and 230 UI > screens) that we want to get out of VB and into a better language. The > program is over 10 years old and has already been ported from VB3 to > VB6, a job which took over two years. We would like to port it t

Re: VB to Python migration

2006-01-28 Thread Thomas Ganss
Josh schrieb: You haven't specified where your main pains are. Do you have at least rudimentary architecture ? How often do you have code reviews / refactored your code ? Have you been striving for good code ? Is it a total mess ? Guessing only from the number of screens, you probably have more t

Re: VB to Python migration

2006-01-28 Thread DH
see vb2py to help the conversion http://vb2py.sourceforge.net/ or if you want to convert vb6 to vb.net instead, there are tools from microsoft and others to help with that, such as: http://www.microsoft.com/downloads/details.aspx?FamilyId=10C491A2-FC67-4509-BC10-60C5C039A272&displaylang=en or if

Re: VB to Python migration

2006-01-28 Thread Luis M. González
I second the suggestion of using Boo for this case. Why use Delphi or VB when you have a more "pythonic" first class .NET language? You already have a very good IDE for creating your project (SharpDevelop), which is free, open source and already has the Boo bindings included (download here the late

Re: VB to Python migration

2006-01-27 Thread Steven D'Aprano
On Fri, 27 Jan 2006 23:48:51 +, Josh wrote: > We have a program written in VB6 (over 100,000 lines of code and 230 UI > screens) that we want to get out of VB and into a better language. The > program is over 10 years old and has already been ported from VB3 to > VB6, a job which took over

Re: VB to Python migration

2006-01-27 Thread Ravi Teja
230 UI screens is a lot. An app of that nature is not something people commonly do in Python (although I would be happy to see people show me wrong). You are building a GUI app that likely need not run anywhere except on Windows and perhaps most what of what is does is edit and report on data from

Re: VB to Python migration

2006-01-27 Thread Nicolas Kassis
Josh wrote: > We have a program written in VB6 (over 100,000 lines of code and > 230 UI screens) that we want to get out of VB and into a better > language. The program is over 10 years old and has already been > ported from VB3 to VB6, a job which took over two years. We would > like to port it t

VB to Python migration

2006-01-27 Thread Josh
We have a program written in VB6 (over 100,000 lines of code and 230 UI screens) that we want to get out of VB and into a better language. The program is over 10 years old and has already been ported from VB3 to VB6, a job which took over two years. We would like to port it to Python, but we ne