Gopala Krishna wrote:
> Sorry to sneak in bits of extra information here but since the topic
> came here first i would like to tell you that we(qucs-qt4) are going
> totally for xmlizing and svgizing the components - if not at the
> backend, atleast the visual representation will be xmlized.
> Onc
Sorry to sneak in bits of extra information here but since the topic
came here first i would like to tell you that we(qucs-qt4) are going
totally for xmlizing and svgizing the components - if not at the
backend, atleast the visual representation will be xmlized.
Once the formats are finalized i'll
Alan Grimes wrote:
Lawrence Shafer wrote:
Heh, I know what you're doing now ;)
Cant wait!
huh?
Actually, I decided to spend the evening going after an old pet peeve of
mine, trying to figure out how a major transmission line of current can
go into one side of a junct
Lawrence Shafer wrote:
> Heh, I know what you're doing now ;)
>
> Cant wait!
huh?
Actually, I decided to spend the evening going after an old pet peeve of
mine, trying to figure out how a major transmission line of current can
go into one side of a junction (ECNode?? Pin???) and come out as only
Heh, I know what you're doing now ;)
Cant wait!
Alan Grimes wrote:
> A. Okay, thanks, that clears some stuff up. I had thought QT was just a
> front end, apparently it cooks and does the dishes too. seems like
> there's no way around it... I'll go look for the book.
>
> B. I tried to put my vecto
A. Okay, thanks, that clears some stuff up. I had thought QT was just a
front end, apparently it cooks and does the dishes too. seems like
there's no way around it... I'll go look for the book.
B. I tried to put my vector class in today but the current codebase
rejected it. I'm going to have to au
Dnia niedziela 18 listopada 2007, Alan Grimes napisaĆ:
> C++ sux.
>
> Here's why.
I'm just a KTechlab user, but I know a fair bit of C++ and Qt, so I think I
might be able to clarify some issues. First and foremost, this is not exactly
C++ that bothers you and it doesn't suck, it's just that you
C++ sux.
Here's why.
You can have a line of code which seems innocuous enough but which
drives other code that may extent across 30 different source files in
ten different packages. =(
Case in point:
Start at the tip of the ice burg:
src/electronics/components
And open up any old EC*, or anyt