Hi,
I would add just one more "statement" that represents a my strong beleif:
the single most important thing, to make effective the widespread of a
software toolkit is to have a book available on the subject. By "book" I
mean a stuff that passed the whole production process in a rewarded
publishing company.
The contribution made the editors and other professional figures in
making the material something that is publishable is an
"accept-no-substitute".
What can save, in this sense, Prima is the avaialabilty of the
"Mastering Perl/Tk", that shows many features in common with Prima (ot
that Prima ported) as the geometry manager. For PDL there is nothing out
there that can act in this way.
So if one is looking for a marketing tool, that means creating the
conditions to have a book on the bookshelf.
Fabio D'Alfonso
'Enabling Business Through IT'
cell. +39.348.059.40.22 ***
web: www.fabiodalfonso.com <http://www.fabiodalfonso.com/>
email: [email protected]
<mailto:[email protected]>linkedin:
www.linkedin.com/in/fabiodalfonso <http://it.linkedin.com/in/fabiodalfonso>
twitter: www.twitter.com/#!/fabio_dalfonso
<http://www.twitter.com/#%21/fabio_dalfonso>
fax: +39.06.874.599.581
BlackBerry® Wireless Enabled Address.
** Hidden numbers are automatically rejected by the phone*
On 7/6/2012 11:11 PM, David Mertens wrote:
Yes, I agree. Your posts are targeted at beginners. My comments serve
as footnotes for the interested reader. Please keep up your great
beginner-level posts!
David
On Fri, Jul 6, 2012 at 11:44 AM, Fabio D'Alfonso
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
below it is a copy of a comment I made after David Mertens
commented on one of my posts on Prima.
I would share my think on this, as it relates imo also to PDL.
It is a common issue that any toolkit as Prima or PDL, where no
effort was made by some publisher to make some publishable stuff,
there are two different kinds of actors:
- developers that already know all about the toolkit and are
concerned with internals and upfront problems.
- users that need to start, generally have only reference
material, but no path to navigate.
As it is natural for developers not needing what a user would
need, the effort to make a resource adoptable by users is a
completely different task.
That is what a publisher numerous staff make is directing the
writing of a book, and where the value of the result is.
Meanwhile, I am just trying to writing something roughly going in
this second category.
Any comment to this is welcome.
--
Fabio D'Alfonso
'Enabling Business Through IT'
cell. +39.348.059.40.22 <tel:%2B39.348.059.40.22> ***
web: www.fabiodalfonso.com <http://www.fabiodalfonso.com>
<http://www.fabiodalfonso.com/>
email: [email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>linkedin:
www.linkedin.com/in/fabiodalfonso
<http://www.linkedin.com/in/fabiodalfonso>
<http://it.linkedin.com/in/fabiodalfonso>
twitter: www.twitter.com/#!/fabio_dalfonso
<http://www.twitter.com/#%21/fabio_dalfonso>
<http://www.twitter.com/#%21/fabio_dalfonso>
fax: +39.06.874.599.581 <tel:%2B39.06.874.599.581>
BlackBerry® Wireless Enabled Address.
** Hidden numbers are automatically rejected by the phone*
_______________________________________________
Perldl mailing list
[email protected] <mailto:[email protected]>
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." -- Brian Kernighan
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
