Re: [Wxdevide-devs] Which Help File Format and other questions.

[Tony R. <tb...@gm...>]

The wxHelp idea seems fine to me. I've posted the wiki pages so we can start
to add these specifics to it. I think it's good that we are starting to get
down to the nitty gritty regarding implementation.

I'm not sure I understand the sizer idea. Are you saying that we should use
sizers to implement the IDE? Or, are you saying that the user will be
required to use sizers in the wx RAD? I don't like the latter as it is
completely different from our current wx RAD behavior. I think most novice
users will try to add a wxButton to a wxFrame/wxDialog and get frustrated if
it doesn't immediately work because a sizer hadn't been added first. I
prefer the current behavior where the user has the choice to use sizers or
design "free-form".

As an important aside, I'd like to bring up the topic of developer
conflicts. Although I think we are all reasonable people, it is good that we
have a plan to handle the times where one developer strongly disagrees with
another about how something should work. I've run across this situation in
the past and it can lead to bad blood.

I have a proposal for handling conflicts, but welcome other ideas. I figure
there are 5 core developers right now (me, Nuklear, SofT, Esteban, and Mal).
For major policy/architecture resolutions, we just go with a simple majority
(so, at present, if you can convince 2 other core developers that you are
right, then you've got the 3 votes you need). In the case that the number of
core developers ever changes to an even number and a tie occurs, the tie
breaking vote is the core developer that's been here the longest. For the
present 5 core developers, I'd suggest that Nuklear is the lead developer
since he started the SF page and got the ball rolling. Next in line is SofT
who contributed the initial souce code to SVN. Next is Mal who commited the
first SVN source code. Then, Esteban who produced the first API docs. And
then me because I'm the only one left. So if we ever added/lost developers,
Nuklear would currently have the tie-breaker vote.

Perhaps all of this seems silly to bring up, but I thought we'd get it on
the table for discussion. Does anyone have a better plan?

-Tony

p.s. I think Nuklear and I currently have admin status on the website. It
is, of course, offered to any of the core developers who want it. Just let
one of us know if you want admin status.

On Sun, Sep 28, 2008 at 2:50 AM, Malcolm Nealon <m.n...@wa...> wrote:

> Hi All,
>
> Since we are moving to wxWidgets, should we also move the help file to
> wxHelp format? This has my vote, since we need to generate help for all
> platforms.
>
> Also, assuming we are, I would suggest that the help is written as we go
> along, ensuring that we can correctly link to subjects as we move along.
>
> I assume that we can re-use a lot of information from the old help file,
> replacing screen shots as we go for example. We need to ensure that
> context help works as expected also.
>
> Do we support the "What's this" help under windows? Or do we insist that
> the program works exactly the same on all platforms?
>
> The images for the new look (as used by wxdevcpp) need to be located and
> added to svn. I would also suggest giving this theme a different name
> and allowing the user to select between the images currently within the
> folder "new look" and those we actually use for the new look in wxdev.
>
> Are we going to go the sizer route for dialog design? This gets my vote,
> as well as turning on wxDefaultPosition/wxDefaultSize in the designer,
> it makes the dialogs look better when designed with sizers.
>
> We need to decide on a standard Astyle style for our code. I assume we
> all have a preference as to how we like our code to look, so we need to
> agree on a standard from the beginning.
>
> I have looked at Sof.T's SkinDoc2 project, and it looks as though the
> form designer there could be used to replace our designer. (Ed could you
> tell me the difference between the old designer and the new designer -
> does it suffer from the same problem we do where it grows beyond the
> confines of the screen and becomes unmanageable- need scroll bars for
> example?
>
> Just some food for thought
>
> Mal
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wxdevide-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>