[wx-discuss] Re: SoC starts...
Francesco Montorsi
f18m_cpp217828 at yahoo.it
Wed May 24 12:46:01 PDT 2006
Julian Smart ha scritto:
> Hi Francesco,
>
> At 11:49 24/05/2006, Francesco Montorsi wrote:
>> Hi all,
>> I've seen that my component manager project for SoC has been
>> accepted :) Thanks!
>
> Congratulations :-) only 3 out of about 23 proposals made it. It's
> great that you're working on this important piece of wxWidgets.
Thanks!
BTW, out of curiosity, which other projects have been accepted ?
>> Before beginning, I'd like to start to ask you a couple questions:
>>
>> 1) where should I host the package manager project ?
>> I think that when complete it should go in wxWidgets\utils but
>> meanwhile should I host it at wxCode ?
>> It does not make much difference to me, provided that I have access to
>> a CVS server...
>
> Good question. If you're happy working in wxCode, then why not,
> otherwise we should give you an area of wxWidgets CVS to play
> in until it's polished enough to be part of the official
> directory structure. The last time I tried creating a module
> in my own CVS server I managed to do it in the wrong order
> and messed it up so we may need to enlist some help to set
> this up. Unless you say otherwise, I'll assume you'll use
> wxCode.
As Vadim remembered me, it also depends how much control you'd like to
have on my work - i.e. if it's more comfortable for you to see my
commits & source status in a CVS folder somewhere at sunsite, I've got
no problems.
At wxCode I have full access and thus it would not be a problem for me
at all to set up a new (transient) component there...
BTW I thought that, assuming wxWidgets\utils will be its final location,
I should use the wx bakefiles for the build system (i.e. not wxpresets
nor wxCode bakefiles but the .bkl in wxWidgets\build\bakefiles), right ?
In order to make integration of the package manager effortless, I mean.
Currently I've checkedout a new clean copy of wx and created a "pkgmngr"
folder in wx\utils...
>
> BTW Daniel has his own subversion repository; but I think
> for the purposes of this project there should be an area
> that only you write to, so we can do the assessment that
> Google requires.
Ok
>
>> 2) should it work also with 2.6 branch ?
>> Or just with CVS HEAD ?
>
> Personally I think it should be 2.6-compatible so others
> can try it out, and for maximum compatibility with apps
> that may wish to use it as a class lib. However, if it's
> a pain to retain 2.6 compatibility, leave it as a separate
> issue to be dealt with after the project is over.
Ok - I asked because I thought to use wxChoiceBook in some points of the
GUI and I don't know if this is present in 2.6 too...
> Best of luck with the project! and do let me know if anything's
> holding you back, e.g. CVS access, uncertainty about project
> scope, etc.
sure - then just another question:
Can the GUI of the program be XRC-based ? Or should I create it
'manually' ? Can I choose what I prefer (XRC even if it increases load
time) ?
Also, since until Sunday I'm going to start writing the main skeleton of
the app, should the app be dialog-based ? I imagine it as a dialog-based
application which has a wxListBox showing installed components and on
the right a wxComponentPropertiesPanel which shows the details of the
selected component. Such panel would contains buttons like e.g. "Compile
this component", "Install this component".
On the bottom I'd put some other buttons: "Download a new component",
"Create a new component", "Help"...
Am I asking too many details ?
I don't know exactly how free I am to choose them... :)
Francesco
---------------------------------------------------------------------
To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org
More information about the wx-discuss
mailing list