> -----Original Message-----
> From: Stephen Pick [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 13, 2004 10:21 AM
> To: Jez White; perl-win32-gui-users@lists.sourceforge.net
> Subject: RE: [perl-win32-gui-users] Intermediate release of Win32::GUI


<snip />


> Use $progressbar->Change( -foreground => [$r,$g,$b], 
> -background => [$r2,$g2,$b2] ) to change the colour, adding 
> SetColor methods would probably mean doing things I don't 
> really feel comfortable with, like rebuilding Makefile.pl and 
> stuff. I'm not sure of the commands to do that, so I'm not 
> going to do it in case i break it. If anyone knows how to do 
> it, the info would be greatly appreciated.

Cool, that works for me.  Can these be passed in the constructor method, or not 
yet?

> > You are right that the project should be driven by people working
> > on active projects and with all the changes you are making, you
> > must be working on something good!. 
> 
> I'm mostly working on a widget arrangement module called 
> CoolGrid. It behaves like a widget itself, and lets you pack 
> multiple widgets into a grid with various attributes (like 
> hfill, vfill, cell alignment etc). It allows you to size 
> columns and rows with the mouse and all other columns scale 
> accordingly. It's major sexy addition is dockable windows - 
> if you add a dialogbox or window into the grid it becomes a 
> dockable panel that can be dragged out of the grid and then 
> snapped back into it. It'll be released as alpha soon.
> 
> > As another example of the missing methods, I was having an email
> > exchange with someone off the list and we started talking about
> > the status bar and how you split it up like word or explorer.
> 
> Yes, I'd like to be able to do this, but I think it's quite a 
> big project to add all this functionality. I will look into 
> it and see.
> 
> > the toolbar is another control that springs to mind.
> 
> You should consider playing around with the ReBar control if 
> you want draggable IE-style toolbars.
> 
> > I think there is a strong argument for pro-actively finding and
> > creating the missing methods/functions for all available controls.
> > I'm sure most of us have been in the position where we wanted to
> > do something simple and yet when we come to implementing it, we
> > find the method is missing or undocumented.
> 
> Usually if this happens I either use Win32::API to get around 
> the problem nastilly or add the functionality to Win32::GUI 
> myself. From a user perspective, people could say "oh good 
> for you, and what am *I* supposed to do?", but I rarely see 
> feature requests made on the sourceforge site, and if I see 
> nothing there, I generally assume users don't want anything 
> much new. One thing I've been looking into is Japanese 
> character support, I don't speak japanese and thank god that 
> I know Windows 2000 well enough not to have to be able to 
> read, since i've had to change the language settings to 
> japanese in order to fix this bug.

One functionality that I would like to see (It could already be there and I 
just don't know how), is the ability to have a scrollable window.  In other 
words, you create window 50px high, put 5 text box controls on it, each 20 px 
tall and with 5 px between horizontally.  Obviously, this goes below the 
"client" region and It would be good to be able to have a up/down scroll bar to 
scroll the remaining controls into view.  Of course, the size of the window in 
this case is kind of silly and should be increased, but I can see this used for 
example on a tab panel where you may have a large number of fields to display, 
but only on that one tab.  The other tabs may not have enough controls to need 
a scroll bar.  Even if I would have to add a parameter, that would be fine if 
it knew when to scroll and when not.  Again, this may be something already 
there that I do not know about, but if so, there are really not any examples 
detailing this.

> > I'm also sure many newbies have been but off using Win32::GUI for
> > this reason alone. When you add in the issues with the 
> > documentation
> 
> I've been pro-actively updating the documentation in the 
> source code, but I'm not sure of how to generate HTML 
> documentation from the sources. Once again, if anyone knows 
> how to do this (and how to add it to jeb.ca) that would be 
> lovely. I was thinking of PODifying it all.
> 
> > the failing examples
> 
> Which examples fail?
> 
> > the initial image of Win32::GUI can be quite negative, even
> > though (in my view) the product is actually very good.
> 
> I guess you're right here. Win32::GUI put me off for ages 
> just because of the lack of good docs and example code.
> 
> Steve
> 
> 
> ----- Original Message ----- 
> From: Stephen Pick 
> To: perl-win32-gui-users@lists.sourceforge.net ; Jez White 
> Sent: Tuesday, January 13, 2004 1:32 PM
> Subject: RE: [perl-win32-gui-users] Intermediate release of Win32::GUI
> 
> 
> Hi Jez,
> 
> I agree with most of your points about what goes into the 
> project, but I feel that we're in the best position (as 
> people working on active projects) to know what needs to be added.
> 
> To make you extremely happy the commit i'll do thisevening 
> will make progress bars take account of -foreground and 
> -background colour arguments. Rejoice!
> 
> Steve
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] 
> Behalf Of Jez White
> Sent: 13 January 2004 12:16
> To: Levin; perl-win32-gui-users@lists.sourceforge.net
> Subject: Re: [perl-win32-gui-users] Intermediate release of Win32::GUI
> 
> 
> All,
> 
> There have been quite a few additions to the 665-fix build - 
> so perhaps a new build is warranted?
> 
> How would people feel if there are regular new builds - say 
> once a month (during active development)? [Laurent, I 
> apologise for a suggestion that would give you more work!].
> 
> I've been thinking for a while about the problem of missing 
> methods/functions for various controls. Most of below is just 
> me speaking outloud, and does not offer direct solutions. 
> With a bit of luck it may spark a bit of debate. I apologise 
> in advance if this is just a boring monologue:)
> 
> To me the general development process seems quite "selfish"  
> -  i.e., things go into the build that is required for the 
> individual developers project. Using myself as an example, I 
> needed the AddImageList method for the tab strip control, and 
> with a bit of tinkering and struggle I got it working (It 
> went into the latest build, with Laurent graciously adding 
> other missing tab strip methods). In my view, this process 
> isn't a negative thing, but I can't help wondering if there 
> is a better way of managing and dealing with missing 
> methods/functions. As an example, we had a solution presented 
> for setting the colour of the progress control and ideally 
> this should be added as a method to the core.
> 
> I think part of the problem is that most of us on this list 
> (including myself) are using Win32::GUI in an active project, 
> so time and effort is devoted to our own needs and not on 
> gui. So, solutions such as identifying all missing 
> methods/functions, and dishing out the work in a proactive 
> major, can only work if people have the time and inclination 
> to do the work. It would also need someone to own, manage and 
> control that aspect of the development project. I suspect 
> that the hardcore hackers/developers have time constraints 
> and other commitments that would preclude them for getting 
> involved (?). 
> 
> The only solution I can think of is for more developers to 
> get involved - perhaps some of you reading this list?:) 
> Although, in my view, the key is for someone to manage and 
> own. Anyone fancy the job?:) Perhaps other developers can be 
> brought in through sourceforge (through the "help" wanted feature)?
> 
> Thoughts? Comments?
> 
> Cheers,
> 
> "selfish" jez :)
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ----- Original Message ----- 
> From: Levin 
> To: perl-win32-gui-users@lists.sourceforge.net 
> Sent: Tuesday, January 13, 2004 10:50 AM
> Subject: [perl-win32-gui-users] Intermediate release of Win32::GUI
> 
> 
> Laurent, 
> If corrections have enabled to put hooks, it's the good 
> reason to make new PPM release of the module ;) Have you such plan?
> 
> I had failure of all attempts when compiled a package with 
> corrections from CVS Repository :( 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Perl-Win32-GUI-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> 
> 

Reply via email to