it is always better to break the project into smaller modules. Sure, it does
need you to think about interoperatibility; which can be solved thro'
meticulous planning, but then the advantage is that the bugs in the program
are localized....plus things can be worked upon/upgraded independently
without affecting other things and introducing newer bugs in the software.
I feel one big program is more trouble than few small programs.
I recommend modular approach.
ab
> -----Original Message-----
> From: vb4...@li...
> [mailto:vb4...@li...]On Behalf Of Luke-Jr
> Sent: Monday, November 20, 2000 1:35 AM
> To: vb4...@li...
> Subject: [VB4Linux-Dev] Erm... I hate subjects... ;-P
>
>
> Anyway, does anyone have a good reason why we shouldn't do everything
> in VB4Linux (besides VB2C... for now at least)? Because if there's no
> objections, I'd like to get started on the GUI and since we haven't
> really decided on a definate GUI interface (GTK+, GNOME, KDE, etc...),
> making it in VB would leave that open to modification until we get to
> that part of VB2C...
>
> Is there anyone here who has access to a working Visual Basic for
> Windows (VB5 with Wine works I think) who also wants to work on the
> GUI? Until someone else wishes to do some development with the GUI, I'm
> going to keep it to local files... So just email me or the list if you
> want to help develop the GUI... Also, I won't start for at least an hour
> so that ppl have plenty of time to specify reasons why the GUI shouldn't
> be done in VB...
>
> Thx!
>
|
