I don't really know where to start. I am a win32 programmer and have used HTTP components a little as well as HTTPS components a little (I have found some JSON components). I am looking at the quick way of getting my hello world application running. I don't currently have a PHP, Ruby .. IDE, but if there is a consensus as to the best way to go, then I'll install whatever.
Things I want to do:
- Parse the WIKI to read our uplinks (the current pages logical parent) to build a logical TOC page. - I know I can probably do this with standard HTML scraping.
- Add a header to each page that uses the TOC as its source (e.g. Frontpage > SIPP Administration > Entering a new SIPP on the system).
- Be able to embed a link and get a quote from that page in this page and make it so that I can run process and it will update the quote if the source has changed.
- Have checkboxes on each page so users can say the understand the page and are happy with the contents, this will need to get persisted somehow. They can view a list of all pages they haven't checked and also ones that have changed since the last check.
- ..
With no budget (just me wanting to make the WIKI really work for the users), I need a foot in the door to get some productivity to show the users what is possible.
Any help greatly appreciated. E.g. You need x,y & z and the look at example.. Or You have all you need, just look at example... Haven't you read.. .yet!
Our main WIKI is V1, but have some tests in V2. Would prefer to be able to tackle both until the upgrade tool is fully functional and we move to WIKI 2 for our main on.
> I don't really know where to start. I am a win32 programmer and have used
> HTTP components a little as well as HTTPS components a little (I have found
> some JSON components). I am looking at the quick way of getting my hello
> world application running. I don't currently have a PHP, Ruby .. IDE, but
> if there is a consensus as to the best way to go, then I'll install
> whatever.
> Things I want to do:
> - Parse the WIKI to read our uplinks (the current pages logical
> parent) to build a logical TOC page. - I know I can probably do this with
> standard HTML scraping.
> - Add a header to each page that uses the TOC as its source (e.g.
> Frontpage > SIPP Administration > Entering a new SIPP on the system).
> - Be able to embed a link and get a quote from that page in this
> page and make it so that I can run process and it will update the quote if
> the source has changed.
> - Have checkboxes on each page so users can say the understand the
> page and are happy with the contents, this will need to get persisted
> somehow. They can view a list of all pages they haven't checked and also
> ones that have changed since the last check.
> - ..
> With no budget (just me wanting to make the WIKI really work for the users),
> I need a foot in the door to get some productivity to show the users what is
> possible.
> Any help greatly appreciated. E.g. You need x,y & z and the look at
> example.. Or You have all you need, just look at example... Haven't you
> read.. .yet!
> Our main WIKI is V1, but have some tests in V2. Would prefer to be able to
> tackle both until the upgrade tool is fully functional and we move to WIKI 2
> for our main on.
> I don't really know where to start. I am a win32 programmer and have used
> HTTP components a little as well as HTTPS components a little (I have found
> some JSON components). I am looking at the quick way of getting my hello
> world application running. I don't currently have a PHP, Ruby .. IDE, but
> if there is a consensus as to the best way to go, then I'll install
> whatever.
> Things I want to do:
> - Parse the WIKI to read our uplinks (the current pages logical
> parent) to build a logical TOC page. - I know I can probably do this with
> standard HTML scraping.
> - Add a header to each page that uses the TOC as its source (e.g.
> Frontpage > SIPP Administration > Entering a new SIPP on the system).
> - Be able to embed a link and get a quote from that page in this
> page and make it so that I can run process and it will update the quote if
> the source has changed.
> - Have checkboxes on each page so users can say the understand the
> page and are happy with the contents, this will need to get persisted
> somehow. They can view a list of all pages they haven't checked and also
> ones that have changed since the last check.
> - ..
> With no budget (just me wanting to make the WIKI really work for the users),
> I need a foot in the door to get some productivity to show the users what is
> possible.
> Any help greatly appreciated. E.g. You need x,y & z and the look at
> example.. Or You have all you need, just look at example... Haven't you
> read.. .yet!
> Our main WIKI is V1, but have some tests in V2. Would prefer to be able to
> tackle both until the upgrade tool is fully functional and we move to WIKI 2
> for our main on.
> also... I've got a c# wrapper for the pbwiki api, if that would be
> useful for you.
> On Jun 16, 4:48 am, "Jason Chapman" <ja...@jac2.co.uk> wrote:
> > Hi,
> > I don't really know where to start. I am a win32 programmer and have used
> > HTTP components a little as well as HTTPS components a little (I have found
> > some JSON components). I am looking at the quick way of getting my hello
> > world application running. I don't currently have a PHP, Ruby .. IDE, but
> > if there is a consensus as to the best way to go, then I'll install
> > whatever.
> > Things I want to do:
> > - Parse the WIKI to read our uplinks (the current pages logical
> > parent) to build a logical TOC page. - I know I can probably do this with
> > standard HTML scraping.
> > - Add a header to each page that uses the TOC as its source (e.g.
> > Frontpage > SIPP Administration > Entering a new SIPP on the system).
> > - Be able to embed a link and get a quote from that page in this
> > page and make it so that I can run process and it will update the quote if
> > the source has changed.
> > - Have checkboxes on each page so users can say the understand the
> > page and are happy with the contents, this will need to get persisted
> > somehow. They can view a list of all pages they haven't checked and also
> > ones that have changed since the last check.
> > - ..
> > With no budget (just me wanting to make the WIKI really work for the users),
> > I need a foot in the door to get some productivity to show the users what is
> > possible.
> > Any help greatly appreciated. E.g. You need x,y & z and the look at
> > example.. Or You have all you need, just look at example... Haven't you
> > read.. .yet!
> > Our main WIKI is V1, but have some tests in V2. Would prefer to be able to
> > tackle both until the upgrade tool is fully functional and we move to WIKI 2
> > for our main on.
-----Original Message----- From: pbwiki-api@googlegroups.com [mailto:pbwiki-api@googlegroups.com] On
Behalf Of Tim Sent: 17 June 2008 19:27 To: PBwiki API Hackers Subject: [PBwiki API] Re: Newbie win32 programmer - a thread to start pulling at.
also... I've got a c# wrapper for the pbwiki api, if that would be useful for you. [JAC] That would be great. As I said I am a W32 programmer, but I should have VS (2008) installed after the weekend, so onto MSVS's .NET world!
+
I think that you've bitten off quite a lot. [JAC] Thoughts are cheap / free, actually delivering any of it is more taxing.
if you were to tackle these one at a time starting with the highest priority, which would you start with? [JAC] Well, I think using good old W32 and html parsing, I can build an in memory model of pages and up links, giving me a Table Of Contents, which I can spit out as static HTML, so I will probably tackle this by parsing a backup.
So I guess my current is: 1) Connect to WIKI 2) Open a page 3) Edit the page 4) Save it away.
This will allow me to inject certain headers into a pages.
I am currently working on linking my application into the WIKI so every screen has a help button and the users can edit the list of links that the help button links to, i.e. links into the WIKI.
Thanks for your time, Jason Chapman.
On Jun 16, 4:48 am, "Jason Chapman" <ja...@jac2.co.uk> wrote: > Hi,
> I don't really know where to start. I am a win32 programmer and have used > HTTP components a little as well as HTTPS components a little (I have found > some JSON components). I am looking at the quick way of getting my hello > world application running. I don't currently have a PHP, Ruby .. IDE, but > if there is a consensus as to the best way to go, then I'll install > whatever.
> Things I want to do:
> - Parse the WIKI to read our uplinks (the current pages logical > parent) to build a logical TOC page. - I know I can probably do this with > standard HTML scraping.
> - Add a header to each page that uses the TOC as its source (e.g. > Frontpage > SIPP Administration > Entering a new SIPP on the system).
> - Be able to embed a link and get a quote from that page in this > page and make it so that I can run process and it will update the quote if > the source has changed.
> - Have checkboxes on each page so users can say the understand the > page and are happy with the contents, this will need to get persisted > somehow. They can view a list of all pages they haven't checked and also > ones that have changed since the last check.
> - ..
> With no budget (just me wanting to make the WIKI really work for the users), > I need a foot in the door to get some productivity to show the users what is > possible.
> Any help greatly appreciated. E.g. You need x,y & z and the look at > example.. Or You have all you need, just look at example... Haven't you > read.. .yet!
> Our main WIKI is V1, but have some tests in V2. Would prefer to be able to > tackle both until the upgrade tool is fully functional and we move to WIKI 2 > for our main on.
Hey Jason...
if you're going to be using .net, here's a little sample for you using
the pbwiki.dll
it's using CLR/C++ (Managed C++) so that it easily iteroperates with
the C# dll.
the source includes a completely trivial example as well as a non-
trivial example of how to use the system.
> Thanks for the 3 replies tim, I have merged two here. Please see below,
> -----Original Message-----
> From: pbwiki-api@googlegroups.com [mailto:pbwiki-api@googlegroups.com] On
> Behalf Of Tim
> Sent: 17 June 2008 19:27
> To: PBwiki API Hackers
> Subject: [PBwiki API] Re: Newbie win32 programmer - a thread to start
> pulling at.
> also... I've got a c# wrapper for the pbwiki api, if that would be
> useful for you.
> [JAC] That would be great. As I said I am a W32 programmer, but I should
> have VS (2008) installed after the weekend, so onto MSVS's .NET world!
> +
> I think that you've bitten off quite a lot.
> [JAC] Thoughts are cheap / free, actually delivering any of it is more
> taxing.
> if you were to tackle these one at a time starting with the highest
> priority, which would you start with?
> [JAC] Well, I think using good old W32 and html parsing, I can build an in
> memory model of pages and up links, giving me a Table Of Contents, which I
> can spit out as static HTML, so I will probably tackle this by parsing a
> backup.
> So I guess my current is:
> 1) Connect to WIKI
> 2) Open a page
> 3) Edit the page
> 4) Save it away.
> This will allow me to inject certain headers into a pages.
> I am currently working on linking my application into the WIKI so every
> screen has a help button and the users can edit the list of links that the
> help button links to, i.e. links into the WIKI.
> Thanks for your time,
> Jason Chapman.
> On Jun 16, 4:48 am, "Jason Chapman" <ja...@jac2.co.uk> wrote:
> > Hi,
> > I don't really know where to start. I am a win32 programmer and have used
> > HTTP components a little as well as HTTPS components a little (I have
> found
> > some JSON components). I am looking at the quick way of getting my hello
> > world application running. I don't currently have a PHP, Ruby .. IDE,
> but
> > if there is a consensus as to the best way to go, then I'll install
> > whatever.
> > Things I want to do:
> > - Parse the WIKI to read our uplinks (the current pages logical
> > parent) to build a logical TOC page. - I know I can probably do this with
> > standard HTML scraping.
> > - Add a header to each page that uses the TOC as its source (e.g.
> > Frontpage > SIPP Administration > Entering a new SIPP on the system).
> > - Be able to embed a link and get a quote from that page in this
> > page and make it so that I can run process and it will update the quote if
> > the source has changed.
> > - Have checkboxes on each page so users can say the understand
> the
> > page and are happy with the contents, this will need to get persisted
> > somehow. They can view a list of all pages they haven't checked and also
> > ones that have changed since the last check.
> > - ..
> > With no budget (just me wanting to make the WIKI really work for the
> users),
> > I need a foot in the door to get some productivity to show the users what
> is
> > possible.
> > Any help greatly appreciated. E.g. You need x,y & z and the look at
> > example.. Or You have all you need, just look at example... Haven't you
> > read.. .yet!
> > Our main WIKI is V1, but have some tests in V2. Would prefer to be able
> to
> > tackle both until the upgrade tool is fully functional and we move to WIKI
> 2
> > for our main on.
