phpgtk__legacy/wiki1/wiki.d/PhpGtk.WebIdeas

18 lines
4.6 KiB
Text

version=pmwiki-1.0.5
newline=²
text=List ideas, suggestions, and improvements to the PHP-GTK Web site here.²²*a code repository as php-classes to share code snippets²*a submit form for people to propose tutorials, samples of code ...²*more frequent news²*a download version of the ANNOTED documentation as the notes are often more consistent than the doc itself.²*a community portal for users to find other PHP-GTK developers, resources, etc.²*user forum²*better/updated external resources²*updated logo and header color²*lengthened and more thorough FAQ (especially for newbies)²*(database-driven?) news system that shows this year's posts on home page and archives previous year's posts; generates RSS feed²*Better manual search functionality²²----²perhaps it would be nice to avoid redundancy between the wiki and site section such as FAQ or ressources. what do you prefer move them from wiki to site or from site to wiki? (my vote for the second one as the wiki can be maintain and enhance by everyone) {{~Nathan}}²²Hi all! Hope you don't mind me barging in this way!\\²Related to this item, I think the most important issue here is making sure the info is updated regularly, and is well organized.²I've been dwelling on everything php-gtk2 I could find, and only after a week or so did I find enough info to compile PHP-Gtk on my linux box. For the most part, both the site and wiki look quite messy and incomplete...\\²I think I'll be able to help out where needed in my (little) spare time, so I've started some changes on the wiki (the only part I have access too =P). \\²This is one of the reasons I agree with Nathan, and think the wiki aproach is the best: if there aren't enough people to maintain the site up-to-date, all the help comming straight from the community should be welcome! {{~Jp}}
time=1129256698
diff:1090686255:1090686255:=1,13c1²< List ideas, suggestions, and improvements to the PHP-GTK Web site here.²< ²< *a code repository as php-classes to share code snippets²< *a submit form for people to propose tutorials, samples of code ...²< *more frequent news²< *a download version of the ANNOTED documentation as the notes are often more consistent than the doc itself.²< *a community portal for users to find other PHP-GTK developers, resources, etc.²< *user forum²< *better/updated external resources²< *updated logo and header color²< *lengthened and more thorough FAQ (especially for newbies)²< *(database-driven?) news system that shows this year's posts on home page and archives previous year's posts; generates RSS feed²< *Better manual search functionality²---²> Describe WebIdeas here.²\ No newline at end of file²
author=Jp
author:1090686255=ramsey
host:1090686255=24.53.105.4
name=PhpGtk.WebIdeas
host=85.138.0.3
agent=Mozilla/5.0 (X11; U; Linux i686; pt-PT; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
rev=9
diff:1090780128:1090686255:=14,16d13²< ²< ----²< perhaps it would be nice to avoid redundancy between the wiki and site section such as FAQ or ressources. what do you prefer move them from wiki to site or from site to wiki? (my vote for the second one as the wiki can be maintain and enhance by everyone) {{~Nathan}}²\ No newline at end of file²
author:1090780128=nathan
host:1090780128=82.124.244.245
diff:1129256698:1097504018:=16,22c16²< perhaps it would be nice to avoid redundancy between the wiki and site section such as FAQ or ressources. what do you prefer move them from wiki to site or from site to wiki? (my vote for the second one as the wiki can be maintain and enhance by everyone) {{~Nathan}}²< ²< Hi all! Hope you don't mind me barging in this way!\\²< Related to this item, I think the most important issue here is making sure the info is updated regularly, and is well organized.²< I've been dwelling on everything php-gtk2 I could find, and only after a week or so did I find enough info to compile PHP-Gtk on my linux box. For the most part, both the site and wiki look quite messy and incomplete...\\²< I think I'll be able to help out where needed in my (little) spare time, so I've started some changes on the wiki (the only part I have access too =P). \\²< This is one of the reasons I agree with Nathan, and think the wiki aproach is the best: if there aren't enough people to maintain the site up-to-date, all the help comming straight from the community should be welcome! {{~Jp}}²\ No newline at end of file²---²> perhaps it would be nice to avoid redundancy between the wiki and site section such as FAQ or ressources. what do you prefer move them from wiki to site or from site to wiki? (my vote for the second one as the wiki can be maintain and enhance by everyone) {{~Nathan}}²\ No newline at end of file²
author:1129256698=Jp
host:1129256698=85.138.0.3