What about just the .chm approach ?  It is very time consuming though , and the free help tools out there leave alot to be desired

http://www.accviz.com/?src=hm

Is an OK tool , has .chm plus HTML online browsable stuff.

C

On Tue, 2 Mar 2004 14:07:23 +1100, Matthew <matthew.hat@stlsoft.dot.org> wrote:

>> "C" <dont@respond.com> wrote in message news:opr37vhqidehmtou@localhost...
>> Just my opinion , but I really don't like doxygen, I like the idea of
>> self-documenting code but all the docs I read created by Doxygen are just
>> really hard to read, and especially to navigate.
>
> Do you have a better suggestion? I'm always open to new things.
>
> One thing I should think about doing is tailoring the styles and all that
> stuff, but it's a time thing ...
>
>> Some more examples would
>> be good also ;).
>
> Thanks for the info. I'll bear it in mind
>
> Cheers
>
> Matthew
>
>> On Thu, 26 Feb 2004 13:30:03 +1100, Matthew <matthew.hat@stlsoft.dot.org>
>> wrote:
>>
>> >
>> > "Pablo Aguilar" <paguilarg@hotmail.com> wrote in message
>> > news:c1jj5r$12jl$1@digitaldaemon.com...
>> >> "Matthew" <matthew.hat@stlsoft.dot.org> wrote in message
>> >> news:c1jfi0$shf$1@digitaldaemon.com...
>> >> > Great!
>> >> >
>> >> > FYI, I'm pretty happy with the libs so far, but it's been six 
>> months
>> > since
>> >> > the last major release - 1.6.5. I've been promising 1.7.1 for some
>> >> time,
>> >> > hence the betas available on the downloads page
>> >> > (http://stlsoft.org/downloads.html) - but we're still a little way
>> >> off,
>> >> due
>> >> > to my having too many commitments at the moment. The stuff 
>> available
>> >> in
>> >> the
>> >> > latest beta is largely what will appear, although there are several
>> > things
>> >> > yet to do, including your item-data enumeration. :)
>> >>
>> >> Thanks,
>> >> I've been following the C++ and D newsgroups for a while now, so, I'm
>> > kinda
>> >> up to date with your current activities.
>> >> BTW good luck with your book...
>> >>
>> >> > The main area of weakness at the moment is the documentation, which
> is
>> >> > pretty pants, if I'm honest. I'd be very happy to receive any
>> > criticisms -
>> >> > however negative they might be - or suggestions for improvement you
>> > might
>> >> > have on this.
>> >>
>> >> That's right, the docs kinda s**k, but, I figure it's because you're
>> > trying
>> >> to use a "common" documentation layout, with a library that's not 
>> quite
>> > that
>> >> common... I mean, when something's documented, you usually have no 
>> more
>> > than
>> >> a few overloads for the same name, while in the case of shims you've
> got
>> > the
>> >> same name all over the place, well, that's what I think anyway...
>> >
>> > Yep. It's a big problem. I'm going to have to spend a lot of time 
>> making
>> > it
>> > better, I think. :-(
>> >
>> >> Also, every typedef is documented (i.e. xxx_a, xxx_w and plain xxx),
> you
>> >> could go the way that the Windows PSDK does, and just document once 
>> and
>> >> state somewhere that everything has a '_a' and '_w' variant
>> >>
>> >> > Also, I'm hoping to have a little Users' List on the site, so if 
>> you
>> >> (or
>> >> > anyone else) use
>> >> > STLSoft and want to be mentioned, I'd be happy to hear how/where 
>> so I
>> > can
>> >> > post it.
>> >>
>> >> Fine by me... only, I don't think I qualify as a user yet (since I've
>> >> just
>> >> yesterday started using the libraries, and just a couple of items so
>> > far)...
>> >> Actually, I did download the library (back on version 1.6.3) but was
>> >> kinda
>> >> put off by both the docs, and the fact that what I was most 
>> interested
>> >> in
>> >> (the item data stuff) wasn't in it... and I didn't get around to
>> >> commeting
>> >> on it back then...
>> >
>> > Understood. That's clear evidence that the docs need the attention.
>> >
>> > Thanks for the feedback. Maybe when I do the new item-data classes, 
>> you
>> > can
>> > give me detailed feedback on the docs, and then I can take that and
>> > apply it
>> > elsewhere.
>> >
>> > Cheers
>> >
>> > Matthew
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

I already do use chm, as part of the Doxygen preparation, available in a separate zip from http://stlsoft.org/downloads.html.

I guess this may not be precisely what you want, but there's no way I'm ever going to have the time to devote to preparing all the help files manually. There's only me, you know! ;)

Matthew

"C" <dont@respond.com> wrote in message news:opr375xfneehmtou@localhost... What about just the .chm approach ?  It is very time consuming though , and the free help tools out there leave alot to be desired

http://www.accviz.com/?src=hm

Is an OK tool , has .chm plus HTML online browsable stuff.

C

On Tue, 2 Mar 2004 14:07:23 +1100, Matthew <matthew.hat@stlsoft.dot.org> wrote:

>> "C" <dont@respond.com> wrote in message
>> news:opr37vhqidehmtou@localhost...
>> Just my opinion , but I really don't like doxygen, I like the idea of
>> self-documenting code but all the docs I read created by Doxygen are
>> just
>> really hard to read, and especially to navigate.
>
> Do you have a better suggestion? I'm always open to new things.
>
> One thing I should think about doing is tailoring the styles and all that stuff, but it's a time thing ...
>
>> Some more examples would
>> be good also ;).
>
> Thanks for the info. I'll bear it in mind
>
> Cheers
>
> Matthew
>
>> On Thu, 26 Feb 2004 13:30:03 +1100, Matthew
>> <matthew.hat@stlsoft.dot.org>
>> wrote:
>>
>> >
>> > "Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:c1jj5r$12jl$1@digitaldaemon.com...
>> >> "Matthew" <matthew.hat@stlsoft.dot.org> wrote in message news:c1jfi0$shf$1@digitaldaemon.com...
>> >> > Great!
>> >> >
>> >> > FYI, I'm pretty happy with the libs so far, but it's been six
>> months
>> > since
>> >> > the last major release - 1.6.5. I've been promising 1.7.1 for some
>> >> time,
>> >> > hence the betas available on the downloads page (http://stlsoft.org/downloads.html) - but we're still a little way
>> >> off,
>> >> due
>> >> > to my having too many commitments at the moment. The stuff
>> available
>> >> in
>> >> the
>> >> > latest beta is largely what will appear, although there are several
>> > things
>> >> > yet to do, including your item-data enumeration. :)
>> >>
>> >> Thanks,
>> >> I've been following the C++ and D newsgroups for a while now, so, I'm
>> > kinda
>> >> up to date with your current activities.
>> >> BTW good luck with your book...
>> >>
>> >> > The main area of weakness at the moment is the documentation, which
> is
>> >> > pretty pants, if I'm honest. I'd be very happy to receive any
>> > criticisms -
>> >> > however negative they might be - or suggestions for improvement you
>> > might
>> >> > have on this.
>> >>
>> >> That's right, the docs kinda s**k, but, I figure it's because you're
>> > trying
>> >> to use a "common" documentation layout, with a library that's not
>> quite
>> > that
>> >> common... I mean, when something's documented, you usually have no
>> more
>> > than
>> >> a few overloads for the same name, while in the case of shims you've
> got
>> > the
>> >> same name all over the place, well, that's what I think anyway...
>> >
>> > Yep. It's a big problem. I'm going to have to spend a lot of time
>> making
>> > it
>> > better, I think. :-(
>> >
>> >> Also, every typedef is documented (i.e. xxx_a, xxx_w and plain xxx),
> you
>> >> could go the way that the Windows PSDK does, and just document once
>> and
>> >> state somewhere that everything has a '_a' and '_w' variant
>> >>
>> >> > Also, I'm hoping to have a little Users' List on the site, so if
>> you
>> >> (or
>> >> > anyone else) use
>> >> > STLSoft and want to be mentioned, I'd be happy to hear how/where
>> so I
>> > can
>> >> > post it.
>> >>
>> >> Fine by me... only, I don't think I qualify as a user yet (since I've
>> >> just
>> >> yesterday started using the libraries, and just a couple of items so
>> > far)...
>> >> Actually, I did download the library (back on version 1.6.3) but was
>> >> kinda
>> >> put off by both the docs, and the fact that what I was most
>> interested
>> >> in
>> >> (the item data stuff) wasn't in it... and I didn't get around to
>> >> commeting
>> >> on it back then...
>> >
>> > Understood. That's clear evidence that the docs need the attention.
>> >
>> > Thanks for the feedback. Maybe when I do the new item-data classes,
>> you
>> > can
>> > give me detailed feedback on the docs, and then I can take that and
>> > apply it
>> > elsewhere.
>> >
>> > Cheers
>> >
>> > Matthew
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

On Tue, 2 Mar 2004 20:45:09 +1100, Matthew <matthew.hat@stlsoft.dot.org> wrote:

> I already do use chm, as part of the Doxygen preparation, available in a
> separate zip from http://stlsoft.org/downloads.html.
>
> I guess this may not be precisely what you want, but there's no way I'm ever
> going to have the time to devote to preparing all the help files manually.
> There's only me, you know! ;)

Look into http://python.planetmirror.com/sigs/doc-sig/otherlangs.html. In particular, I've heard good things about Synopsis (though never used it).

Cheers,
Niall

I've just started playing with the clipboard, and thought of an idea you
might be interested in: RAII classes for the clipboard
(OpenClipboard/CloseClipboard pair) and HGLOBAL locking
(GlobalLock/GlobalUnlock pair, maybe something like hg_lock<T>(HGLOBAL hg) )

I just finished writing both, let me know if you're interested

> I've just started playing with the clipboard, and thought of an idea you might be interested in: RAII classes for the clipboard (OpenClipboard/CloseClipboard pair) and HGLOBAL locking (GlobalLock/GlobalUnlock pair, maybe something like hg_lock<T>(HGLOBAL
hg) )

Sure. Great!

Send 'em in. I'll take a look at them, and probably do another beta next week. (I expect to release 1.7.1 before the end of this month.)

I'll send you any changes in private before we agree to incorporate them into the libraries.

:)

Cheers

Matthew

"Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:c28o0n$2bqr$1@digitaldaemon.com...
> I just finished writing both, let me know if you're interested
>
> > I've just started playing with the clipboard, and thought of an idea you might be interested in: RAII classes for the clipboard (OpenClipboard/CloseClipboard pair) and HGLOBAL locking (GlobalLock/GlobalUnlock pair, maybe something like hg_lock<T>(HGLOBAL
> hg) )

Here they are then...
Comments are more than welcome... don't know about portability issues, I
just did 'em in VC6, tested, worked... I'm happy... but, like I said,
comments are greatly appreciated

Here's a small sample of how to use 'em:

void MyWindow::OnSomething()
{
    std::string text;
    {
        clip_lock<CF_TEXT> cl(m_hWnd);
        if( cl )
        {
            hg_lock<LPCTSTR> str(::GetClipboardData(cl.requested_type()));
            if( str.locked() )
                text = str;
        }
    }
}

"Matthew" <matthew.hat@stlsoft.dot.org> wrote in message news:c28qkc$2gbj$1@digitaldaemon.com...
> Sure. Great!
>
> Send 'em in. I'll take a look at them, and probably do another beta next week. (I expect to release 1.7.1 before the end of this month.)
>
> I'll send you any changes in private before we agree to incorporate them into the libraries.
>
> :)
>
> Cheers
>
> Matthew

Does the mfcstl c_str_ptr shim support CListBox?

I'm using stlsoft 1.6.5 and, c_str_ptr works with windows whose GetWindowText function returns the window's text, and CListBox doesn't...

Hi Pablo

The c_str_ptr shim boils down to a call to GetWindowText(). Since the contents of a listbox are not stored in the window text, c_str_ptr will not yield the list box contents. In any case, which one would it return?

However, you've got me thinking now, and maybe I might add a shim that takes an object and an index. This could work for list/combo boxes, list views, as well as completely different types, such as stl containers, COM collections, etc.

It's funny. I've never considered shims having more than one parameter, but there's no reason why they can't.

I'm busy this week, but maybe next week I can add this in, in time for 1.7.1.

Cheers

Matthew


"Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:c2lnp6$1aq0$1@digitaldaemon.com...
> Does the mfcstl c_str_ptr shim support CListBox?
>
> I'm using stlsoft 1.6.5 and, c_str_ptr works with windows whose GetWindowText function returns the window's text, and CListBox doesn't...
>
>

Actually, I was thinknig of it getting the selected item's text, or null (or "", whatever) if nothing was selected, of course this wouldn't work with multiple selection lists, but then the shim with an index you mentioned kicks in (when you know there might be multiple selections)

Did you get a chance to look at the clipboard stuff I posted last week?

"Matthew" <matthew@stlsoft.org> wrote in message news:c2mv10$ch3$1@digitaldaemon.com...
> Hi Pablo
>
> The c_str_ptr shim boils down to a call to GetWindowText(). Since the contents of a listbox are not stored in the window text, c_str_ptr will
not
> yield the list box contents. In any case, which one would it return?
>
> However, you've got me thinking now, and maybe I might add a shim that
takes
> an object and an index. This could work for list/combo boxes, list views,
as
> well as completely different types, such as stl containers, COM
collections,
> etc.
>
> It's funny. I've never considered shims having more than one parameter,
but
> there's no reason why they can't.
>
> I'm busy this week, but maybe next week I can add this in, in time for 1.7.1.
>
> Cheers
>
> Matthew