kde-quality Digest, Vol 3, Issue 8
Martin Ponce
mjp_ttc at yahoo.com
Sat Apr 10 05:21:16 CEST 2004
Hi men !
Your opinions are really valuable, but i really sorry, to not understand
the full stuff of this issue.
I just have some difficult to understand the Philosophy of how was implemented
the i18n and i10n features, where are the files and directories and so.
¿Have you some references or links about that ?
Another issue is about how to create regional translations from a common
version ( v.gr. British english Besides American English, and Spanish of Mejico
beside Spanish of Spain )
Thanks in advance
Have a nice day
Martin Ponce
Hasta luego amigos
--- kde-quality-request at kde.org wrote:
> Send kde-quality mailing list submissions to
> kde-quality at kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.kde.org/mailman/listinfo/kde-quality
> or, via email, send a message with subject or body 'help' to
> kde-quality-request at kde.org
>
> You can reach the person managing the list at
> kde-quality-owner at kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kde-quality digest..."
>
>
> Today's Topics:
>
> 1. Re: Engineering I.E. Quality (James Richard Tyrer)
> 2. Re: Engineering I.E. Quality (Michael Pyne)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 09 Apr 2004 00:26:26 -0700
> From: James Richard Tyrer <tyrerj at acm.org>
> Subject: Re: Engineering I.E. Quality
> To: "Contributors support and coordination, \ to make KDE rock!"
> <kde-quality at kde.org>
> Message-ID: <40765022.7050604 at acm.org>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Carlos Leonhard Woelz wrote:
> > On Wednesday 07 April 2004 10:34 pm, James Richard Tyrer wrote: <snip>
> >
> > This discussion is clearly off topic here. This list is a place to
> > support new contributors and coordinate work,
>
> This is about coordinating work. Or at least it was till Christian took
> one sentence out of context and wrote a short book about it. You are
> probably correct that I should have simply ignored his OT reply, but I
> don't seem to work that way.
>
> > especially non programming work (that may be considered off topic for
> > kde-devel).
>
> Yes, this is about non-programing work. Non-programing work (non-coding
> work is more accurate) can not occur if it is not valued by the self
> appointed coder class.
> >
> > Discussing the intrinsic problems of the KDE development model is
> > kde-cafe material.
>
> KDE-Cafe was closed. It became a place to discuss how the Jews were going
> to take over the world. :-\ No I am not kidding.
>
> > Or if you have a finished, constructive proposal, you can try posting it
> > to kde-devel.
>
> Unfortunately, I am still at the stage of defining the problem.
> Constructive comments would be appreciated. And, I have no idea as to a
> solution.
>
> Or, the solution is simple. Developers need to drop the arrogance and
> admit that other work has value -- perhaps, in some cases, even more value
> than coding. I would like for them to realize that engineering and design
> is more important than the actual coding. Whether they do the engineering
> and design work themselves or have someone else do it is not the issue.
>
> As long as the importance of engineering and design is denigrated,
> unpremeditated coding will continue to be an accepted practice --
> pejoratively referred to as 'hacking'.
>
> I note that I am not just stating some lofty ideas. I am stating the way
> that I work -- the way that I learned in engineering college. First I
> design a program, and then I write the code. Sometimes this is a cycle:
> Design, Code, Design, Code ... etc. But I always design before I code. I
> do this because it works. It results in better code with less total work.
>
> Like I said on the Dot: Design twice, Code once.
>
> --
> JRT
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 9 Apr 2004 03:54:30 -0400
> From: Michael Pyne <pynm0001 at unf.edu>
> Subject: Re: Engineering I.E. Quality
> To: "Contributors support and coordination, \ to make KDE rock!"
> <kde-quality at kde.org>
> Message-ID: <200404090354.37271.pynm0001 at unf.edu>
> Content-Type: Text/Plain; charset="iso-8859-1"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Friday 09 April 2004 03:26, James Richard Tyrer wrote:
> > First I
> > design a program, and then I write the code. Sometimes this is a cycle:
> > Design, Code, Design, Code ... etc. But I always design before I code. I
> > do this because it works. It results in better code with less total work.
> >
> > Like I said on the Dot: Design twice, Code once.
>
> Well, speaking as a programmer, I would tend to concur about the importance
> of
> design, even if it's just a paper sketch. However, I think you underestimate
>
> the importance of design to the developers. Sure, some programs could have
> used a much better design step (such as practically everything in kdeadmin).
>
> But things like KWallet and the KParts infrastructure are IMO good examples
> of a design process at work.
>
> They certainly don't appear to have UML diagrams or such, but it still
> doesn't
> stink of an overnight hackfest.
>
> Perhaps it would be better to come up a nice beautiful plan covering all the
> contingencies first. That is certainly how we're taught to build projects in
>
> my CS major. I personally find that I quickly lose interest in a program if
> I can't get SOMETHING coded within a few days after planning, however, which
> usually leaves me time for only a cursory design. And that's a problem with
> volunteer effort: If someone loses interest, then we get no contribution at
> all.
>
> I think it's good to emphasize the importance of design (and Havoc P. has a
> good idea going with the Project Utopia use cases IMHO), but I don't feel
> from my observations that the KDE developers are unnecessarily ignoring
> design, even if they don't feel it is as important as you do.
>
> I'm reminded of the example of John Romero, the designer for iD software when
>
> they made Doom. He eventually left the company to found Ion Storm because
> the rest of iD kept letting those pesky technical issues interfere with
> John's vision. The motto of Ion Storm became something to the effect of
> "Design is law", and the company became a spectacular failure, although it
> managed to produce a few noteworthy titles.
>
> It's clear that you're not advocating designing the code with no regard to
> its
> eventual implementation, but (again speaking from my personal experience) I
> find that it's easier to design around a system's peculiarities when you're
> actually sitting there at the system. I use an incremental approach: Design,
>
> code, test, code, test, test, test, code, etc. If it becomes obvious that
> the design isn't working, I overhaul it before I get too much coded.
>
> The initial design always helps, but it's never thourough. And ironically
> enough, my program ends up better for it 9 times out of 10. Of course,
> that's just me. But I suspect more KDE developers pay attention to design
> that you think, even if they don't flesh out the entire structure at first.
>
> Regards,
> - Michael Pyne
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAdla7qjQYp5Omm0oRAuC2AJ9XVTwNahavisLuDmI48wM/qPTBzACgzTLc
> GY/IwrR3RoAXKxg3hbIrd4M=
> =tUxG
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> _______________________________________________
> kde-quality mailing list
> kde-quality at kde.org
> https://mail.kde.org/mailman/listinfo/kde-quality
>
>
> End of kde-quality Digest, Vol 3, Issue 8
> *****************************************
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
More information about the kde-quality
mailing list