"Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:caatjt$2blm$1@digitaldaemon.com...
>> I'm pleased (and very relieved) to announce that STLSoft version 1.7.1 is
>> released.
>>
>> Now that this very major hurdle is behind us, I'm in the market for new
> feature
>> requests and submissions, so please don't hold back. I hope to release
> 1.7.2 in a
>> few weeks, and intend to do another big step with 1.8.1 before the end of
> the
>> year - there are a lot of new features planned for that. :-)
>
> module_directory, great
> clipboard stuff starting to appear
> window_visible_scope, great
>
> still missing insert/SetItemData for list/combo boxes

I'm willing to have a play with this (as mentioned in other post) if you can remind me what you wanted. (Alternatively, you could contribute a version, and leave me the lazy task of criticising it and putting into the library! <g>)

> you asked me to remind you about process_sequence

Ah, yes. That'd be nice. I will put a skeleton into the inprogress/winstl dir right now, which'll remind me

> you think auto_destructor could be policied with the destruction function (I asked about this before but talking about smart pointers) ?

That's something that might fall out of the smart pointers discussions going on elsewhere. I'll add you to that list now.

> winstl::resource_string isn't documented

And it still isn't! I'm going to have a go at this right now.

> comstl::safe_array_sequence also not documented

This one'll have to wait. ;)

"Pablo Aguilar" <paguilarg@hotmail.com> wrote in message news:cad1n1$2b8a$1@digitaldaemon.com...
>> > clipboard stuff starting to appear
>>
>> Keep making those requests.
>
> clipboard_lock and read/writing are missing still... all I saw for now was clipboard_format_sequence

I've just written clipboard_scope, which has does scoping and has various methods for getting and setting data in different formats.

>> > still missing insert/SetItemData for list/combo boxes
>> > you asked me to remind you about process_sequence
>>
>> Remind me again in a while
>
> Sure...

We'll need to kick start this debate, as I've forgotten all about it.

>> > you think auto_destructor could be policied with the destruction
> function (I
>> > asked about this before but talking about smart pointers) ?
>>
>> I don't remember. Can you explain what you mean?
>
> That 'delete' could be made into a policy... so instead of deleting you could have, for example, ->Release, or something alike... I know there's a special ptr for COM, but that's not the point... say you're dealing with objects created by factories, and destruction isn't a plain delete but some special function... that's where the policy class would kick in...

Maybe. Let's see how the smart-pointers article series takes off.

For my part, I tend to steer clear of policy based classes wherever possible, as they're plain harder to use without having to consult documenation every time. (And they're less efficient, portable, etc.)

>> still missing insert/SetItemData for list/combo boxes
>
> I'm willing to have a play with this (as mentioned in other post) if you can remind me what you wanted. (Alternatively, you could contribute a version, and leave me the lazy task of criticising it and putting into the library! <g>)

Already answered...

>> you asked me to remind you about process_sequence
>
> Ah, yes. That'd be nice. I will put a skeleton into the inprogress/winstl dir right now, which'll remind me

I'd been wondering why so silent as of lately! You've been REALLY busy...

Ok, before you spend more time on this, give me today to post (when I get home) my version of this. I hadn't done so, 'cuz I thought I'd take a shot at doxygen before posting it, but, now that you seem to be in a programming rush, I guess I'll have to speed this up.. ;-)

I did it based not on the EnumProcesses API, but rather the ToolHelp32 API, which allows for easier enumeration, IMO. And, since the ToolHelp32 API also enumerates modules, threads and heaps, all of those are done as well...

>> you think auto_destructor could be policied with the destruction function
>> (I
>> asked about this before but talking about smart pointers) ?
>
> That's something that might fall out of the smart pointers discussions going on elsewhere. I'll add you to that list now.

Thanks!

>> winstl::resource_string isn't documented
>
> And it still isn't! I'm going to have a go at this right now.

Cool...

>> comstl::safe_array_sequence also not documented
>
> This one'll have to wait. ;)

No hurry, it's been long since I used it (code I used it with is working, so there's no need to touch it right now..)


Pablo

[snip]
> > still missing insert/SetItemData for list/combo boxes
>
> I'm willing to have a play with this (as mentioned in other post) if you
can remind me what you wanted. (Alternatively,
> you could contribute a version, and leave me the lazy task of criticising
it and putting into the library! <g>)

That's an interesting twist... do work, rather than ask for it... ;-) I'll have to consider it...

Seriously though, I might take a shot at it, but not at the moment. Here's
my current list of pending projects:
1) Process/Thread/Module/Heap sequences, which I'll e-mail in a while
2) Check and suggest improvements for the docs as you requested on the other
thread
3) The ruby (or python) script to invert the current header/forwarder status
of most of the libraries
4) A tool to help set up fresh installs of boost & stlsoft for work with
popular (read "the ones I use, VC & BCB") IDEs on Windows. It's feature set
would be:
    - Registering include/library paths
    - Registering tools for direct access to each libraries help
    - Building libraries when required (in boost's case of course) allowing
the selection of compiler and target configurations
(threading/linking/debug)

Then I might have a go at this...


Pablo

> Seriously though, I might take a shot at it, but not at the
> moment. Here's
> my current list of pending projects:
> 1) Process/Thread/Module/Heap sequences, which I'll e-mail in a
> while

Got it. Will digest in a few days, but looks good at first blush. (Be surprised if it doesn't get into 1.8.4)

> 2) Check and suggest improvements for the docs as you requested on
> the other
> thread

Thanks. I think you've done #2. (Not sure if I sent you #1)

> 3) The ruby (or python) script to invert the current
> header/forwarder status
> of most of the libraries

You might want to hang fire on this awhile, or at least email me before you go ahead.

I also need to write one that will move all the unit-testing code out of the main file and into the xyz_unittest_.h file (a la ACESTL as from 1.8.3).

These can probably be done independently, but the desire to do the second might mean I'll need to do the first, and don't want you to waste your time on it in that case.

> 4) A tool to help set up fresh installs of boost & stlsoft for
> work with
> popular (read "the ones I use, VC & BCB") IDEs on Windows. It's
> feature set
> would be:
>    - Registering include/library paths
>    - Registering tools for direct access to each libraries help
>    - Building libraries when required (in boost's case of course)
> allowing
> the selection of compiler and target configurations
> (threading/linking/debug)

Now _this_ sounds like a wonderful tool. Will this be an SF.NET tool? If so, sign me up!!

> Then I might have a go at this...

He he. No pressure

"Matthew" <admin@stlsoft.dot.dot.dot.dot.org> wrote in message news:d7bf2o$1rts$1@digitaldaemon.com...
> > Seriously though, I might take a shot at it, but not at the
> > moment. Here's
> > my current list of pending projects:
> > 1) Process/Thread/Module/Heap sequences, which I'll e-mail in a
> > while
>
> Got it. Will digest in a few days, but looks good at first blush. (Be surprised if it doesn't get into 1.8.4)

Cool!

> > 2) Check and suggest improvements for the docs as you requested on
> > the other
> > thread
>
> Thanks. I think you've done #2. (Not sure if I sent you #1)

Haven't made any suggestions yet... I've made it as far as downloading all the latest versions of ORJ, recls & SS, and gone through the docs you mentioned. But haven't actually come up with suggestions.

> > 3) The ruby (or python) script to invert the current
> > header/forwarder status
> > of most of the libraries
>
> You might want to hang fire on this awhile, or at least email me before you go ahead.

Ok

> I also need to write one that will move all the unit-testing code out of the main file and into the xyz_unittest_.h file (a la ACESTL as from 1.8.3).
>
> These can probably be done independently, but the desire to do the second might mean I'll need to do the first, and don't want you to waste your time on it in that case.
>
> > 4) A tool to help set up fresh installs of boost & stlsoft for
> > work with
> > popular (read "the ones I use, VC & BCB") IDEs on Windows. It's
> > feature set
> > would be:
> >    - Registering include/library paths
> >    - Registering tools for direct access to each libraries help
> >    - Building libraries when required (in boost's case of course)
> > allowing
> > the selection of compiler and target configurations
> > (threading/linking/debug)
>
> Now _this_ sounds like a wonderful tool. Will this be an SF.NET tool? If so, sign me up!!

I *hope* it will. I submitted it, but got rejected, as apparently I didn't
give an accurate enough description of the project. I'll let you know
when/if it gets accepted.
Also, the guys at boost didn't seem particularly thrilled about it, maybe I
am really not giving a good enough description... I'll set up the UI and see
if that helps communicate the idea better...

> > Then I might have a go at this...
>
> He he. No pressure

None taken.


Pablo