PDF Editor in Ubuntu

[H.S.]

Dotan Cohen wrote:
>>
>> Finally, if the said project are not portable, being open source one can
>> work to make them so. But with proprietary libs, there is no easy way to
>> do this, if at all possible. So you see where all this going, right?
>>
> 
> Yes. It's turning into the Debian list :)
> (for those not familiar: Debian list members are very anti-proprietary software)
> 

What I had meant was that the onus is on the programmer regarding the
design and implementation of his project. To achieve and maintain
portability, one must take relevant decisions*. Even if the programmer
insists on using a proprietary library, the prerequisite should be to
see how portable it is. And I have already listed the main steps to take
to create a portable program.

Regards.

* The question is, what are those decisions? This is what I had in mind
when I alluded to the specific goal your univ. has in mind in your
course. Perhaps this topic is not in the course outline and hence no
apparent discussions in your class regarding this. But all programmers
hit this question sooner or later.


-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.