From: Seth C. <se...@eu...> - 2001-09-20 20:38:56
|
> 3. Seth Cohn writes that phpGroupWare has a nice ticket tracking system. > It does. But phpGroupWare is *big* and one of the nicest things about > phpWiki is that it's still pretty simple and small. So here's what I > will do: I will create a small, one page ticket tracker that can be > distributed with phpWiki and that uses its own database table, but I > will also include glue so that phpWiki can optionally call out to the > PHPGW API instead, so that if you already happen to be using PHPGW, > phpWiki will register tickets in it. I've looked at the API, and this > shouldn't be too hard. very cool. I agree with the others, that just for a ticket tracker, WikiBadges would work, on a small scale. The nice thing about doing a PHPGW plugin would be the multiple uses. With a consistent API, adding ToDos, Calendar, Tickets, and dozens of other features would be easy. For instance, let's say a cool module for PHPGW comes out that does double entry accounting. Instead of Wiki having to add a new plugin, the existing plugin just passes the right API commands, and bingo, you get a nice Ledger page in the Wiki, right in your discussion of whatever the ledger is about. > I'm not, however, going to do the work to "embed" phpWiki into a PHPGW > module. I have little interest in forcing the wiki into an even smaller > box on my browser window, surrounded by even more buttons and menus. No, I am not suggesting that. The beauty of the plugin is that you could have some users using a standalone wiki, and it would handle the PHPGW stuff itself. Speaking of modules, I have the PHPWiki module for Php/PostNuke running. It IS embedded into the Nuke, and it looks great. The author, Olle Johansson, is looking into making a few changes based on feedback from myself and Andy Burham, including porting the code to 1.3 (it's 1.1.8 right now). Between plugins and RSS, it should be possible to make the Wiki work really well with Nuke... Seth |
From: Adam S. <ad...@pe...> - 2001-09-20 20:52:55
|
> Speaking of modules, I have the PHPWiki module for Php/PostNuke > running. It IS embedded into the Nuke, and it looks great. The > author, Olle Johansson, is looking into making a few changes based on > feedback from myself and Andy Burham, including porting the code to > 1.3 (it's 1.1.8 right now). Between plugins and RSS, it should be > possible to make the Wiki work really well with Nuke... can you keep us posted on your progress? i'm pretty entusiastic about all this. i got sucked into the c2 wiki from the reference to wiki badges and started reading about the WikiPalm and WikiAsPim pages ... this is what i want ... i want it soooo bad. :) adam. |
From: Seth C. <se...@eu...> - 2001-09-20 22:12:00
|
> can you keep us posted on your progress? Will do. I think the PHP triad of Wiki/Nuke/Groupware will be a killer combo. With it, you will have a complete intranet solution, and also a great community forum. > i'm pretty entusiastic about all > this. i got sucked into the c2 wiki from the reference to wiki badges and > started reading about the WikiPalm and WikiAsPim pages ... this is what i > want ... i want it soooo bad. :) Yeah, I have been telling people that Wiki is the next step. I see more Wikis springing up lately. I think the Wiki idea is reaching critical mass. Seth |
From: Jeb B. <je...@oc...> - 2001-09-21 16:46:49
|
On Thu, Sep 20, 2001 at 03:09:02PM -0700, Seth Cohn wrote: > > can you keep us posted on your progress? > > Will do. I think the PHP triad of Wiki/Nuke/Groupware will be a > killer combo. Yeah, I've been moving in this direction too. (I'm using Wiki actively, have Groupware installed, and might install Nuke shortly.) The one thing that bothers me about many of these tools is the lack of capability for combined registration / authentication. We need some kind of SQL based auth plugin that other packages can use optionally, (instead of their own built in auth table). Ideally, the login ID used should be an email address, per Jacob Nielson's suggestion, because it's guaranteed to be unique, and easy to remember. Does anyone know of a project that is addressing this? If not, perhaps we can think about it for the new auth features of PhpWiki? > With it, you will have a complete intranet solution, and also a great > community forum. Another fairly polished piece of php/MySQL code is phpBB, which I just installed for another site, and of course has its own auth system too. http://phpbb.com I think that kind of forum is useful for sites that don't want to make their home page a rolling weblog of articles and discussion like Nuke/K5/Slashdot. (Instead, they can setup a dedicated discussion area covering persistent topics of their choice...) -jeb |
From: Seth C. <se...@eu...> - 2001-09-21 17:22:11
|
> > Will do. I think the PHP triad of Wiki/Nuke/Groupware will be a > > killer combo. > The one thing that bothers me about many of these tools is the lack of > capability for combined registration / authentication. The Wiki module that Olle wrote uses the existing Nuke login. If not logged in, it's 'anonymous user' (settable), and he's going to implement the suggestion that if desired, you must login to edit. Once logged in, it uses your Nuke login as your userid, so I created a SethCohn login, and it worked fine under RecentChanges. > We need some > kind of SQL based auth plugin that other packages can use optionally, > (instead of their own built in auth table). Ideally, the login ID > used should be an email address, per Jacob Nielson's suggestion, > because it's guaranteed to be unique, and easy to remember. Doesn't need to nearly be so complex or reinvent the wheel. Nuke works fine, and if you wanted to make Wiki a major part, you could always add a check for WikiWord status if you desired that. (Nuke already checks for all sorts of things, like no God/Root/Admin types names...) If you want make something interoperable, look at how Nuke or GW do it, and implement a similar scheme, so that an admin merely has to point the engine to the same database and it'll read the same users. > Does anyone know of a project that is addressing this? If not, > perhaps we can think about it for the new auth features of PhpWiki? I think it's already in the works with Jeff's recent cvs changes. > Another fairly polished piece of php/MySQL code is phpBB, which I just > installed for another site, and of course has its own auth system too. > http://phpbb.com This has been ported/modulized for Nuke. It's a popular Nuke addon. Thanks for pointing another case of the convergence. I myself am running a Wiki with a lot of 'discussion' and feeling that Wiki might be the wrong medium for it. Some users like the ability to edit, some don't. But it's haphazard and not very 'clean' to read. A good discussion board would probably replace those sections of the Wiki. leaving the more Wiki aligned pages to grow. |
From: Adam S. <ad...@pe...> - 2001-09-21 17:38:36
|
> I myself am running a Wiki with a lot of 'discussion' and feeling that > Wiki might be the wrong medium for it. Some users like the ability to > edit, some don't. But it's haphazard and not very 'clean' to read. A > good discussion board would probably replace those sections of the > Wiki. leaving the more Wiki aligned pages to grow. i'd like to see the story as a wiki page where it can slowly be refactored and evolve as comments and more information comes in, with weblog style comments attached because i think most people are more comfortable participating that way. adam. |
From: Seth C. <se...@eu...> - 2001-09-22 00:04:50
|
> > I myself am running a Wiki with a lot of 'discussion' and feeling that > > Wiki might be the wrong medium for it. Some users like the ability to > > edit, some don't. But it's haphazard and not very 'clean' to read. A > > good discussion board would probably replace those sections of the > > Wiki. leaving the more Wiki aligned pages to grow. > > i'd like to see the story as a wiki page where it can slowly be refactored > and evolve as comments and more information comes in, with weblog style > comments attached because i think most people are more comfortable > participating that way. For an interesting take on this, look at: http://www.nbtsc.org/wiki/NBTSWikiWiki Simply put, it's a wiki that has a comment attachment section at the bottom of each page. So either you can edit the page AND/OR put a static comment at the bottom. I'm not sure I like this or not, but it's interesting. I looked at Twiki, what with the new plugin API and all, and it's got some features I think are neat. I think if possible, Standardizing a plugin api would be a good thing. Jeff? Have you looked at Twiki's plugins? If so, what is good and bad about them? Someone should do a feature list of the various wiki clones and make a Wikipage for it. Or is there one? |
From: Adam S. <ad...@pe...> - 2001-09-22 01:45:10
|
> For an interesting take on this, look at: > http://www.nbtsc.org/wiki/NBTSWikiWiki wow, i hadn't found that before. that's a cool wiki, do you know what software they are running? i couldn't find the obligatory "powered by ..." anywhere. > Someone should do a feature list of the various wiki clones and make a > Wikipage for it. Or is there one? there's gotta be one on c2 or meatball but i never could find anything that was even vaguely recent. i got started here when i was trying to decided which wiki to run personaltelco on but got distracted and never finished it. http://www.personaltelco.net/index.cgi/WhyWiki adam. |
From: Gary B. <ga...@in...> - 2001-09-22 02:16:54
|
On Fri, 21 Sep 2001, Adam Shand wrote: > > > For an interesting take on this, look at: > > http://www.nbtsc.org/wiki/NBTSWikiWiki > > wow, i hadn't found that before. that's a cool wiki, do you know what > software they are running? i couldn't find the obligatory "powered by > ..." anywhere. Search for PhpWiki on it -- some of the pages are almost verbatim from pgsrc. Either it is a very, very hacked PhpWiki or the guy started using PhpWiki and then migrated the database over to a new system... |
From: Gary B. <ga...@in...> - 2001-09-22 02:18:32
|
On Sat, 22 Sep 2001, Gary Benson wrote: > On Fri, 21 Sep 2001, Adam Shand wrote: > > > > For an interesting take on this, look at: > > > http://www.nbtsc.org/wiki/NBTSWikiWiki > > > > wow, i hadn't found that before. that's a cool wiki, do you know what > > software they are running? i couldn't find the obligatory "powered by > > ..." anywhere. > > Search for PhpWiki on it -- some of the pages are almost verbatim from > pgsrc. Either it is a very, very hacked PhpWiki or the guy started using > PhpWiki and then migrated the database over to a new system... In fact, http://www.nbtsc.org/wiki/WikiPhilosophy is almost a blow-by-blow account of all the changes the guy made to PhpWiki... |
From: Seth C. <se...@eu...> - 2001-09-22 03:06:05
|
Please forward to whomever is running the NBTSwiki: We're discussing your cool Wiki modifications on the PHPWiki list, and I for one would love to see the code changes you've made, since there are clearly some _really_ cool things you've added... (If you aren't on the PHPWiki list, check the archives to get up to speed and subscribe) http://sourceforge.net/mail/?group_id=6121 What version did you start with, and could you either send me a copy of your current code so I can diff it, or (even better) do you have the patches yourself? I'd love to see some of these mods make it back into the current mix... I can see a few I'd like to have on my own wiki(s). I think this is the true beauty of 'open source' code sharing: Your wiki came from the same 'roots' but ended up different enough that we couldn't even tell at first it _was_ related. It's like discovering a neighboring Galapagos Island with new breeds on it, and learning about evolution. I am sure Steve and all of the rest of us PHPWiki user/owners would love to hear all of the geekly details about what you did, didn't, tried, etc etc. Seth ----- Original Message ----- From: Gary Benson <ga...@in...> To: Adam Shand <ad...@pe...> Cc: Seth Cohn <se...@eu...>; <php...@li...> Sent: Friday, September 21, 2001 7:18 PM Subject: Re: [Phpwiki-talk] Re: User registration (was: PHPGW plugin) > > On Sat, 22 Sep 2001, Gary Benson wrote: > > > On Fri, 21 Sep 2001, Adam Shand wrote: > > > > > > For an interesting take on this, look at: > > > > http://www.nbtsc.org/wiki/NBTSWikiWiki > > > > > > wow, i hadn't found that before. that's a cool wiki, do you know what > > > software they are running? i couldn't find the obligatory "powered by > > > ..." anywhere. > > > > Search for PhpWiki on it -- some of the pages are almost verbatim from > > pgsrc. Either it is a very, very hacked PhpWiki or the guy started using > > PhpWiki and then migrated the database over to a new system... > > In fact, http://www.nbtsc.org/wiki/WikiPhilosophy is almost a blow-by-blow > account of all the changes the guy made to PhpWiki... > > |
From: Steve W. <sw...@pa...> - 2001-09-24 17:04:45
|
Ari maintains the nbstc wiki, and there is a tarball available at: http://phpwiki.sf.net/phpwiki/nbtsc.phpwiki.tar.gz Ari has been using PhpWiki almost from the start. That Wiki is a modified 1.03 version; almost no code remains from 1.03 in the current code base. Ari's been on the team for some time now :-) cheers ~swain On Fri, 21 Sep 2001, Seth Cohn wrote: > Please forward to whomever is running the NBTSwiki: > > We're discussing your cool Wiki modifications on the PHPWiki list, > and I for one would love to see the code changes you've made, since there > are clearly some _really_ cool things you've added... > (If you aren't on the PHPWiki list, check the archives to get up to speed > and subscribe) http://sourceforge.net/mail/?group_id=6121 > > What version did you start with, and could you either send me a copy of your > current code so I can diff it, or (even better) do you have the patches > yourself? I'd love to see some of these mods make it back into the current > mix... I can see a few I'd like to have on my own wiki(s). > > I think this is the true beauty of 'open source' code sharing: Your wiki > came from the same 'roots' but ended up different enough that we couldn't > even tell at first it _was_ related. It's like discovering a neighboring > Galapagos Island with new breeds on it, and learning about evolution. > > I am sure Steve and all of the rest of us PHPWiki user/owners would love to > hear all of the geekly details about what you did, didn't, tried, etc etc. > > Seth > > ----- Original Message ----- > From: Gary Benson <ga...@in...> > To: Adam Shand <ad...@pe...> > Cc: Seth Cohn <se...@eu...>; <php...@li...> > Sent: Friday, September 21, 2001 7:18 PM > Subject: Re: [Phpwiki-talk] Re: User registration (was: PHPGW plugin) > > > > > > On Sat, 22 Sep 2001, Gary Benson wrote: > > > > > On Fri, 21 Sep 2001, Adam Shand wrote: > > > > > > > > For an interesting take on this, look at: > > > > > http://www.nbtsc.org/wiki/NBTSWikiWiki > > > > > > > > wow, i hadn't found that before. that's a cool wiki, do you know what > > > > software they are running? i couldn't find the obligatory "powered by > > > > ..." anywhere. > > > > > > Search for PhpWiki on it -- some of the pages are almost verbatim from > > > pgsrc. Either it is a very, very hacked PhpWiki or the guy started using > > > PhpWiki and then migrated the database over to a new system... > > > > In fact, http://www.nbtsc.org/wiki/WikiPhilosophy is almost a blow-by-blow > > account of all the changes the guy made to PhpWiki... > > > > > > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC |
From: Adam S. <ad...@pe...> - 2001-09-24 19:25:18
|
> Ari has been using PhpWiki almost from the start. That Wiki is a > modified 1.03 version; almost no code remains from 1.03 in the current > code base. any chance of getting the commenting integrated into the alpha branch or is the code so diverged that the nbtsc isn't particularly relevant anymore. adam. |
From: Adam S. <ad...@pe...> - 2001-09-22 03:48:21
|
> In fact, http://www.nbtsc.org/wiki/WikiPhilosophy is almost a > blow-by-blow account of all the changes the guy made to PhpWiki... hrm, very cool. the message board stuff is great, i wonder if it's so hacked that his changes are useless. i'm not sure hwo i feel about the rainbow colors but that's just aesthetics ;) adam. |
From: Adam S. <ad...@pe...> - 2001-09-21 17:36:16
|
> The one thing that bothers me about many of these tools is the lack of > capability for combined registration / authentication. We need some > kind of SQL based auth plugin that other packages can use optionally, > (instead of their own built in auth table). Ideally, the login ID > used should be an email address, per Jacob Nielson's suggestion, > because it's guaranteed to be unique, and easy to remember. > > Does anyone know of a project that is addressing this? If not, > perhaps we can think about it for the new auth features of PhpWiki? i think the stuff that drupal is doing is really cool and would be great if phpwiki supported it. drupal's also written in php so their may even be code that we can rip off to do it. http://www.drop.org/node.php?id=531 it's overkill for what phpwiki needs, but if you want some sort of centralized naming system this is what will hopefully be the "passport killer" (ahhh, dreams). the tricky bit is that it's not designed for wiki's and how do you translate an email adress login name to a HomePage (eg. AdamShand) where we're talking about storing user data. i've been thinking more about WikiAsPim and such things and it solves a lot of the issues i have with heirarchical datastorage. the problem all comes down to how to do you continue to embrace the simplicity and inherent flexibility of a wiki and still provide access to multiple datasources (like maybe ldap for a contact database) in a useful way. everything comes down to ui ... and that's hard to solve. adam. |
From: Gary B. <ga...@in...> - 2001-09-21 17:46:07
|
On Fri, 21 Sep 2001, Adam Shand wrote: > i've been thinking more about WikiAsPim and such things and it solves a > lot of the issues i have with heirarchical datastorage. the problem all > comes down to how to do you continue to embrace the simplicity and > inherent flexibility of a wiki and still provide access to multiple > datasources (like maybe ldap for a contact database) in a useful way. > everything comes down to ui ... and that's hard to solve. Adam, I'd love to hear your ideas about this. I was planning on making something to scrape the phonelist off our company intranet and make homepages for people on my PersonalWiki. Gary [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] |
From: Adam S. <ad...@pe...> - 2001-09-21 18:08:54
|
> Adam, I'd love to hear your ideas about this. I was planning on making > something to scrape the phonelist off our company intranet and make > homepages for people on my PersonalWiki. ramble alert ... well i hate to say it but i don't really have any good ones either. i have my personal wiki (www.spack.org) where i store bits and it works *brilliantly* for geek related stuff. i can stuff articles in there, technical docs etc. it's way better saving emails or text files cause it's inherantly hypertext and searchable and yet i keep all the advantages of text caue it is text on the server (i don't use a sql backend). but i want to take it to the next step. i want to move my palm pilot contact database to it. my plan had been to stuff everything via ldiff into an ldap server adn then find or write a php web frontend to it, but the idea of being able to manipulate this data via a wiki is great, but contact details are inherantly private and structured, i don't want to put my mom's email or phone number up for anyone so it has to be private and starts to deviate meaningfully (imho) from what wiki is all about. so maybe each user would have a personal data subwiki, where they could clutter up the wiki name space as much as they like. with a bit of tweaking international phone numbers (or email addresses) would make good unique page identifiers, and ldap plugin could fairly trivially grab info from an ldap server, format it, maybe even load it into text boxes so it can be changed in a structured mannor via the wiki. hell, maybe you could even create another export function (like the rss/rdf that we've been talking about) for ldiff for export to a palm pilot or ldap database. even better maybe i can sync "my wiki" (or my section of the wiki) with my palm pilot ... and i'd actually start using it for somethign other then off site backups of my contact database again :) what i'm wrestling with is "what is a wiki" and what is it that i want to keep, and what i'm willing to sacrifice for greater functionality. would there be anything gained by embedding a webmail (say squirrelmail which is what i think phpgroupware uses) in a wiki page called WebMail. you preserve the wiki interface to a certain point but what do you really accomplish other then more overhead? i think the marriage with phpgroupware could be quite valuable but i really like the idea (jeff's?) of being able to maintain the wiki interface to it, so instead of the wiki appearing inside groupware, groupware elements appear inside the wiki. however i have no idea how to structure that so it's *easy* and convenient enough that people will use it that way. ... ramble off ... adam. |
From: Gary B. <ga...@in...> - 2001-09-22 20:10:48
|
On Fri, 21 Sep 2001, Adam Shand wrote: > > Adam, I'd love to hear your ideas about this. I was planning on making > > something to scrape the phonelist off our company intranet and make > > homepages for people on my PersonalWiki. > > ramble alert ... [snip] Didn't want this lot to get lost in the archives, so I made a page for it: http://phpwiki.sourceforge.net/phpwiki/index.php?WikiAsPim Gary [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] |