wxcode-users

Re: [wxCode-users] Project for a variety of classes?

[Ulrich T. <Ulr...@gm...>]

> I have a project that has a variety of different classes, data
> containers, a spinctrl, a popup combobox for bitmaps, bitmap toggle
> button, etc
> 
> http://www.lehigh.edu/~jrl1/wxwidgets/wxThings/README.txt
> 
> I would hate to add each as their own little one or two file project
> (more maintenance for me),  does anyone have any thoughts on how we
> should approach this? Does it make sense for me to just add this as
> is.

I would propose to add wxThings as is, since you can assign to it all 
categories that wxThings fits in.

Regards,

Ulrich Telle
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341

Re: [wxCode-users] Project for a variety of classes?

[Francesco M. <f18...@ya...>]

Hi,

Ulrich Telle wrote:
>>I have a project that has a variety of different classes, data
>>containers, a spinctrl, a popup combobox for bitmaps, bitmap toggle
>>button, etc
>>
>>http://www.lehigh.edu/~jrl1/wxwidgets/wxThings/README.txt
>>
>>I would hate to add each as their own little one or two file project
>>(more maintenance for me),  does anyone have any thoughts on how we
>>should approach this? Does it make sense for me to just add this as
>>is.
> 
> 
> I would propose to add wxThings as is, since you can assign to it all 
> categories that wxThings fits in.
hmmm, I think that wxThings is really *too* generic; I strongly suggest to split up the 
things in two components: one for data containers and one for controls.

I cannot think to any suitable name for such components, though... :-(

Francesco

Re: [wxCode-users] Project for a variety of classes?

[John L. <jla...@gm...>]

On 11/20/05, Francesco Montorsi <f18...@ya...> wrote:
> >>I have a project that has a variety of different classes, data
> >>containers, a spinctrl, a popup combobox for bitmaps, bitmap toggle
> >>button, etc
> >>
> >>http://www.lehigh.edu/~jrl1/wxwidgets/wxThings/README.txt
> >>
> >>I would hate to add each as their own little one or two file project
> >>(more maintenance for me),  does anyone have any thoughts on how we
> >>should approach this? Does it make sense for me to just add this as
> >>is.
> >
> > I would propose to add wxThings as is, since you can assign to it all
> > categories that wxThings fits in.
> hmmm, I think that wxThings is really *too* generic; I strongly suggest t=
o split up the
> things in two components: one for data containers and one for controls.

That's probably best.

> I cannot think to any suitable name for such components, though... :-(

Heh, my wxThings was originally called wxWidgets when wxWidgets was wxWindo=
ws.

These are pretty generic names, maybe just wxdata and wxcontrols?
They're not taken yet. :)

-John

Re: [wxCode-users] Project for a variety of classes?

[Angelo's G. <ama...@gm...>]

What about wxGizmos? wxExtras?

These are more or less snippets of code that can be used for different
things, and not necessarily all used together. Maybe we should have a
special area called wxSnippets. Though it appears someone had this idea las=
t
year: http://sourceforge.net/projects/snippets/ We could still have a
snippets component I think.

--angelo

On 11/20/05, John Labenski <jla...@gm...> wrote:
>
> On 11/20/05, Francesco Montorsi <f18...@ya...> wrote:
> > >>I have a project that has a variety of different classes, data
> > >>containers, a spinctrl, a popup combobox for bitmaps, bitmap toggle
> > >>button, etc
> > >>
> > >>http://www.lehigh.edu/~jrl1/wxwidgets/wxThings/README.txt
> > >>
> > >>I would hate to add each as their own little one or two file project
> > >>(more maintenance for me), does anyone have any thoughts on how we
> > >>should approach this? Does it make sense for me to just add this as
> > >>is.
> > >
> > > I would propose to add wxThings as is, since you can assign to it all
> > > categories that wxThings fits in.
> > hmmm, I think that wxThings is really *too* generic; I strongly suggest
> to split up the
> > things in two components: one for data containers and one for controls.
>
> That's probably best.
>
> > I cannot think to any suitable name for such components, though... :-(
>
> Heh, my wxThings was originally called wxWidgets when wxWidgets was
> wxWindows.
>
> These are pretty generic names, maybe just wxdata and wxcontrols?
> They're not taken yet. :)
>
> -John
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> Register for a JBoss Training Course. Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Project for a variety of classes?

[John L. <jla...@gm...>]

On 11/20/05, Angelo's Gmail <ama...@gm...> wrote:
> What about wxGizmos?  wxExtras?

Gizmos is already in wxWidgets in the contrib dir and wxExtras, like
wxThings, is probably too vague.

>  These are more or less snippets of code that can be used for different
> things, and not necessarily all used together.  Maybe we should have a
> special area called wxSnippets.  Though it appears someone had this idea
> last year: http://sourceforge.net/projects/snippets/  We
> could still have a snippets component I think.

That is a weird project, the code snippets are for all sorts of
arbitrary things and every conceivable language. Almost all of my
stuff depends on wxWidgets.

It is an interesting idea though. I think it *might* make sense to
create a some components for projects that are at most two source and
header files that would be open to anyone. The problem is that you can
loose control over it easily. By control, I mean that as wxWidgets
changes so too should all the files in these components and if some of
the files stop compiling the whole component is dead. If the original
author disappears, the maintenance falls on the others. Maybe this
wouldn't happen, but if did it could become a headache to have to
maintain others work. To be frank, I'd be wary of it, but it could
work if every member of the component was reasonably active.

Regards,
    John Labenski

Re: [wxCode-users] Project for a variety of classes?

[Francesco M. <f18...@ya...>]

Hi,

John Labenski wrote:
> On 11/20/05, Angelo's Gmail <ama...@gm...> wrote:
>> These are more or less snippets of code that can be used for different
>>things, and not necessarily all used together.  Maybe we should have a
>>special area called wxSnippets.  Though it appears someone had this idea
>>last year: http://sourceforge.net/projects/snippets/  We
>>could still have a snippets component I think.
> 
> 
> That is a weird project, the code snippets are for all sorts of
> arbitrary things and every conceivable language. Almost all of my
> stuff depends on wxWidgets.
anyway the idea of a wxSnippets component is not so bad...


> It is an interesting idea though. I think it *might* make sense to
> create a some components for projects that are at most two source and
> header files that would be open to anyone.
I know that Jorgen has a "code dump" section on the wxForum where this kind of very-small 
snippets can be placed.

I think it's not easy to maintain code in a forum but many people seem to do it:
     http://wxforum.shadonet.com/viewforum.php?f=20
this is also probably because their code doesn't need much maintainance...

I think that to host wxWidgets code one currently can choose among:
1) The Code dump in wxForum for very small pieces of code
2) wxCode for medium components
3) a new SF.net project for large projects

Francesco