Re: Status of PHP-GTK
| From: | Bob Majdak Jr | Date: | Wed, 15 Apr 2009 21:07:11 +0000 |
| Subject: | Re: Status of PHP-GTK | ||
| References: | 1 2 3 4 5 | Groups: | php.gtk.general |
| Request: | Send a blank email to php-gtk-general+get-8376@lists.php.net to get a copy of this message | ||
Even if PHP.NET would allow any of these options, who is going to
implement it? And then who is going to populate it? It might get done
at first, but I would be willing to wager it gets done once and just
like the current docs once it is out of date everyone disappears.
(Actually, I wager it gets half done).
I have no idea what the current system is like, I just know somewhere
someone is making the executive decision to stay with what is there.
- bob
On Wed, Apr 15, 2009 at 4:53 PM, Keith Roberts <keith@karsites.net> wrote:
>
> On Wed, 15 Apr 2009, Benjamin Smith wrote:
>
>> To: php-gtk-general@lists.php.net
>> From: Benjamin Smith <bens@effortlessis.com>
>> Subject: Re: [PHP-GTK] Status of PHP-GTK
>>
>> I offer some counter points, here...
>>
>> On Wednesday 15 April 2009 06:53:48 Bob Majdak Jr wrote:
>>>
>>> Coding is really limping along just fine. Tonnes of people hate the
>>> docs, less than tonnes offer to help, none of them actually do.
>>
>> Sometime ago, I was offered the opportunity to update the docs, and was
>> picturing that it would be something like a fancy wiki or somesuch.
>> Instead, I
>> was introduced to text files with a very complicated tagging system and a
>> steep
>> learning curve. I don't remember what it was, it's been a few years, and
>> I'm
>> sure there are good reasons for choosing it.
>>
>> After struggling for some hours over a few days on it (and even starting a
>> docs editor in PHP-GTK to manage some of the complexity) I threw in the
>> towel
>> and resigned myself to leaving (hopefully helpful) comments.
>>
>> Can this be made simpler? Do you know of some kind of doc-editor manager
>> doohickey to take track all the tagging?
>
> Maybe something like http://en.wikipedia.org/wiki/LyX
>
> would suffice, if only PDF documentation was needed?
>
> Kind Regards,
>
> Keith Roberts
>
> -----------------------------------------------------------------
> Websites:
> http://www.php-debuggers.net
> http://www.karsites.net
> http://www.raised-from-the-dead.org.uk
>
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
> -----------------------------------------------------------------
>
>
>
>
>
>
>
>
>
>>
>>> Granted
>>> extra coders would help but patch writers are easier to come across than
>>> people actually willing to do the docs. And the coders can usually
>>> figure out what to do by knowing GTK in C or by looking at the C GTK
>>> manual.
>>
>> Get_class_methods() and get_object_vars(), and Google are my substitutes..
>> I
>> make it a point to leave notes when I can.
>>
>>> The PHP doc system i am sure is not going anywhere, and personally I
>>> like comments off, it is a manual not a wbe forum. That is one of the
>>> things I hate the most about the actual PHP docs, especally when a new
>>> guy posts a code sample that is horrid and the next 20 posts are people
>>> saying "oh hay i made this better". I am not being bitter. Honest.
>>
>> It's common for me to be baffled by minimalist docs, only to find a
>> comment that
>> makes it all clear... I'm perfectly willing to ignore the crappy,
>> 3-page-long
>> code samples in order to have the nuggets that make my day! And sometimes,
>> even the 3-page-long crappy code gives enough detail about how to use XYX
>> function that it's useful.
>>
>> ...perhaps a moderation system for comments?
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>> --
>> PHP-GTK General Mailing List (http://gtk.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
> --
> PHP-GTK General Mailing List (http://gtk.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>