boa-constructor-users

Re: [Boa Constr] wxText control justification

[Riaan B. <riaan@e.co.za>]

Hi Lynndon,

Lynndon Harnell wrote:
> 
> Hi there. I am trying to find a way to right-justify a text control
> (i.e. for numbers) but cannot seem to find it.

Nope it does not seem to be not supported.

> 
> Any ideas??
> 
> Cheers & beers
> 
> Lynndon Harnell

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Boa CVS 0.0.12

[Lynndon H. <lyn...@ec...>]

Hi again. I just CVS updated to 0.0.12 and downloaded and installed the new 
help docs.

It all seemed to update my CVS version OK, but when I ran it, the program 
load seemed to crash when it got to the help section (as per messages in 
the MS Dos window, but when it crashed the MS Dos window closed). If I try 
to run it from Python IDLE, I get a syntax error c:\Boa\Boa.py, line 378, 
which does not seem to exist.

I am running win98, python21, wxpython 2.2

Any clues would be appreciated.

Regards

Lynndon Harnell

PS I am running netscape, with Eudora as my default email, and sometimes 
(and I suspect anytime I go near the CVS), netscape's composer seems to 
hijack netscape. Strange.......
Lynndon Harnell

[Boa Constr] wxText control justification

[Lynndon H. <lyn...@ec...>]

Hi there. I am trying to find a way to right-justify a text control (i.e. 
for numbers) but cannot seem to find it.

Any ideas??

Cheers & beers

Lynndon Harnell
Lynndon Harnell

[Boa Constr] CVS updated - 0.0.12

[Riaan B. <riaan@e.co.za>]

Hi everyone,

CVS has been updated with nice new features ;)
Major changes:
* NewDebugger branch has been merged. The old Debugger is still 
  available. Choose by changing the 'useDebugger' flag in Preferences 
  to 'old' or 'new'.
  The 'new' Debugger still has some problems, like importing certain
  extensions and handling the wxWindows event loop, but it does pure
  Python very nicely. 
  Big thanks to Shane Hathaway for contributing this!!!
  Anyone with time on their hands who would like to help out with the 
  last problems with the debugger, please contact me!
* New help system, completely replacing the old one.
  You'll have to download the help data files from:
  http://boa-constructor.sourceforge.net/Help/Docs.zip
  or
  http://boa-constructor.sourceforge.net/Help/Docs.tar.gz
  and unzip into the Boa root directory.
  The new help system uses the wxHTMLHelpController and contains help
  for Boa, the Boa Guide, Python, wxPython and CVS.
  Each section has contents and indexes.
* Customiseable preference storage.
  If you have an environment variable HOME and your HOME dir has a
  dir called .boa, all config/preference files that Boa maintains 
  will be copied here and used from here. This is mainly aimed at linux 
  users whose Boas can't update their preferences, but it's useful, 
  and it also works on windows.

Enjoy!
-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] wxgrid

[Riaan B. <riaan@e.co.za>]

Hi Lynndon,

"Harnell, Lynndon" wrote:
> 
> Thanks Riaan I will give this a go.
> 
> I also did note the CaptionOffset property. Is there somewhere I can set a
> default different to the one set by Boa?

You may want to edit the source of the control
bcrtl/user/StaticTextCtrl.py

Also remember copy and pasting a control will preserve the property, 
so you only have to set it once and copy paste it from then.

> 
> Regards
> 
> Lynndon Harnell
> Project Engineer, Oil Company of Australia
> Lyn...@up...
> Mobile 0401 673100
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] wxgrid

[Harnell, L. <lyn...@up...>]

Thanks Riaan I will give this a go.

I also did note the CaptionOffset property. Is there somewhere I can set a
default different to the one set by Boa?

Regards

Lynndon Harnell
Project Engineer, Oil Company of Australia
Lyn...@up... 
Mobile 0401 673100

Re: [Boa Constr] wxgrid control

[Riaan B. <riaan@e.co.za>]

Hello Lynndon,

Lynndon Harnell wrote:
> 
> Hi
> 
> I just got the CVS version of Boa running and would like to use the
> wxgrid control.

Even tho the wxGrid is on the Palette in the CVS version, there is 
still some stability problems when it's used in the Designer.

My advice for the moment is to create and setup wxGrid by hand in the
__init__ method after the call to _init_ctrls.

> 
> Has anyone got any code snippets or hints.
> 
> TIA
> 
> Lynndon Harnell
> 
> PS I do like the new text control with caption. A possible future
> option would be the position of the caption wrt the control, ie left,
> top etc.

There is already a property called CaptionAlignment you may set.
Also look at the CaptionOffset property, it allows pixel offsets for
the caption, one of your original requirements ;)

> Lynndon Harnell

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] wxgrid control

[Lynndon H. <lyn...@ec...>]

Hi

I just got the CVS version of Boa running and would like to use the wxgrid 
control.

Has anyone got any code snippets or hints.

TIA

Lynndon Harnell

PS I do like the new text control with caption. A possible future option 
would be the position of the caption wrt the control, ie left, top etc.
Lynndon Harnell

[Boa Constr] Silly version numbers and road map

[Riaan B. <riaan@e.co.za>]

Hello everyone,

Rest assured, the public release will be the alpha 0.1.0.
After this, version bumps will be on the second digit with major cvs
updates bumping the last digit. Beta will be 0.5.0.
And coinciding with Python 3000 we'll have Boa 1.0.0 ;)

Seriously, I've held back on the version number for various reasons 
explained before. The biggest has always been the unfinished minimal
feature set keeping me from alpha. The second reason has been 
possible incompatible source code generation changes. Something in 
alpha should not do this but how can you complain if 0.0.x pre-alpha
does this ;)

I foresee at least one more change to the generated code.
Because the constructor is called in the _init_ctrls method, it's
impossible to inherit from generated frames and override _init_*
methods as the frame designer is currently doing.
I want to keep the option of eventually supporting frame
inheritance in the Designer open.

I'd like to change this before the alpha, but it's not going to stop
the 0.1.0 release, don't worry.

Just a heads up on other changes I'm hoping for before the alpha:
* New help system
  * HTMLHelpControllers
  * HTML prepared for wxHTML with contents and indexes
    * Boa help & guide, python help, wx help, cvs help (total 16 Meg)
* Installers
* Merge NewDebugger branch (optionally switch between old and new)
* Finish up Explorers

I'd say I'm 75% done with the above so don't stress ;)

About announcements, maybe the lack of public announcements is a 
lure to the mailing list ;)
I do not think it is appropriate to announce CVS updates outside the 
mailing list. 
I'd prefer to continue as is; 
Mailing list for new features, important fixes. 
Important CVS updates are shown as SourceForge news items. 
Releases must be announced here, on wxPython, c.l.py, everywhere!

0.1.0 will be on your doorstep asap!
-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Announcements

[Gordon W. <g_...@cy...>]

Hi,

I think that you could be of service to a number of people if you would also
make announcements on the wxPython list and c.l.py.announce group.

As well, I agree that the alpha number is low and misleading.

Keep up the good work!!

Regards,

Gordon Williams

RE: [Boa Constr] CVS Updated - 0.0.11

[Patrick K. O'B. <po...@or...>]

Very nice. You continually impress me with the enhancements to Boa. I'm
curious to know what it is going to take for you to finally label one of
these releases as version 0.1? I'm starting to think you might be overly
modest. <wink>

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

[Boa Constr] CVS Updated - 0.0.11

[Riaan B. <riaan@e.co.za>]

Hi everyone,

Yet another update of some big internal changes. This was basically a 
refactoring so things don't look too diferent on the outside.
The most noticeable change is the order of items on the toolbar
and the reduced menu on the Source View. Also the 'New' palette is now
available from the Editor's File menu.
On the inside Boa now has explicit Controllers to complete the MVC 
pattern.
One implication is that new model types (usually corresponding to 
file types) can be added without having to change Editor.py or 
Palette.py.

Another cool change is that the way events are connected have been
reworked. When switching between pages in the editor, only the active 
page will have it's events connected, the previous page's events
will be disconnected. This means that Boa does not use idle CPU 
anymore just to process a huge event list and things are more 
responsive when there are a lot of modules open.

The Palette has a new style called 'menu'. This represents the
Palette on a MenuBar instead of on a NoteBook. Useful for lores
situations (resolution or resources).
Settable in Preferences, requires restart.

Unfortunately I have not been able to get Boa compatible with the
newest wxPython 2.3.1.
There is a problem with accelerator keys not traversing to parent 
controls in notebooks. I've been unable to get a workaround going,
but if anyone has the time and need, look at 
Editor.EditorFrame.setupToolBar
This is where the accelerator keys are bound to the window.
Help would be very nice.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

RE: [Boa Constr] Boa's new handling of stdin in ShellEditor

[Patrick K. O'B. <po...@or...>]

Just to clarify, the example I gave only replaced raw_input, but my
suggestion was to replace *both* stdin and raw_input with similar dialogs.
Otherwise, I agree with your points. And while dialogs would be way
different from IDLE, they would be the same as PythonWin. Not that that
matters. Just an observation. On to more important matters. <wink>

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of Riaan
Booysen
Sent: Friday, July 13, 2001 11:32 AM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Boa's new handling of stdin in ShellEditor

Hi Patrick,

"Patrick K. O'Brien" wrote:
>
> Riaan,
>
> This is probably pretty nitpicky,

Yes ;)

> but I'm not crazy about the new way that
> stdin works in the Shell for three reasons. First, the behavior isn't the
> same as other IDEs, such as IDLE. Second, the additional prompt is a
> distraction when most programs that use stdin already display a prompt.
> Third, it is too easy to move the cursor back to a previous command and
copy
> that line down which displays the ps1 prompt instead of ps4, etc.

You mean by moving the cursor up to a previous line and pressing
enter? Why would you want to do this at a stdin prompt?
It would still take the correct input even if the prompt is different.

If you want to implement this, add the concept of a current prompt
to the shell which is prepended to everything copied the the shell line

> For
> examples of what I mean you can type help() or license().

I tested development around help() and licence() so I know how they
behave.

>
> Now, I tried to change this in Boa so that it was still "inline" as
opposed
> to a wxTextEntryDialog but then I ran into problems with the hardcoded
> expectation of a 4 character prompt so I gave up. One alternative is to go
> back to a wxTextEntryDialog and redefine both stdin and raw_input (at the
> __builtin__ level, not locals, which was the problem with the previous
code
> I believe).

No it's not an option to fall back on. Covering one function (raw_input)
instead of ANY function (on stdin) is not a fallback option.

Cool to know that replacing it on built-in level covers most of the
common cases. I never tried it (silly me).

>
> For example:
>
>     def readRaw(self, prompt='Please enter your response:'):
>         dialog = wxTextEntryDialog(None, prompt, \
>                                    'Input Dialog (Raw)', '')
>         try:
>             if dialog.ShowModal() == wxID_OK:
>                 text = dialog.GetValue()
>                 return text
>         finally:
>             dialog.Destroy()
>         return ''
>
> And then wherever appropriate add:
>
>             import __builtin__
>             __builtin__.raw_input = readRaw  # Or the equivalent if
readRaw
> is passed as a parameter.
>             del __builtin__
>
> To do this, though, would require more changes to Boa than I was
comfortable
> making. And I wasn't sure you would agree with these changes.

No you have to work with stdin.

>
> It's not like anything is really broken, I'm just looking for a better
> solution and wanted to jot this stuff down while it was fresh in my mind.
> Feel free to disregard this message entirely. I just felt compelled to
write
> it.
>
> To me the best solution would be something inline that wasn't so fragile.
It
> shouldn't display a prompt but it must be aware of the prompt that might
be
> passed to raw_input(), or that was written directly to stdout (which is
all
> that raw_input does anyway). In a way I think it should be modal, which is
> what you get with the dialog approach. There is also the issue of whether
to
> leave the prompt and response in the output stream, which looks pretty
ugly
> in the case of license(). My readRaw() method basically swallows the
prompt
> and response, which looks better when you call license() but might be
> inappropriate in other circumstances where you want the prompt and
response
> logged.

In most other circumstances yes :)

>
> As you can see, I'm still looking for a solution.

For now I'm comfortable with my solution.
Boa explitly goes into prompt mode. The type of request is very
clear and the input format works easily with the rest of the code.

If you really need to change this, you have to keep track of where
the cursor was when stdin is first read, and the text from there.
I'm currently (automatically) using the normal prompt read code.

I must say that it's kind of a non issue for me as it's not
functionally different (you type the responses) and I liked the
explicit prompt.
And a text entry dialog would be way different than IDLE :)

>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
>
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

Re: [Boa Constr] Boa's new handling of stdin in ShellEditor

[Riaan B. <riaan@e.co.za>]

Hi Patrick,

"Patrick K. O'Brien" wrote:
> 
> Riaan,
> 
> This is probably pretty nitpicky, 

Yes ;)

> but I'm not crazy about the new way that
> stdin works in the Shell for three reasons. First, the behavior isn't the
> same as other IDEs, such as IDLE. Second, the additional prompt is a
> distraction when most programs that use stdin already display a prompt.
> Third, it is too easy to move the cursor back to a previous command and copy
> that line down which displays the ps1 prompt instead of ps4, etc. 

You mean by moving the cursor up to a previous line and pressing 
enter? Why would you want to do this at a stdin prompt?
It would still take the correct input even if the prompt is different.

If you want to implement this, add the concept of a current prompt
to the shell which is prepended to everything copied the the shell line

> For
> examples of what I mean you can type help() or license().

I tested development around help() and licence() so I know how they
behave.

> 
> Now, I tried to change this in Boa so that it was still "inline" as opposed
> to a wxTextEntryDialog but then I ran into problems with the hardcoded
> expectation of a 4 character prompt so I gave up. One alternative is to go
> back to a wxTextEntryDialog and redefine both stdin and raw_input (at the
> __builtin__ level, not locals, which was the problem with the previous code
> I believe).

No it's not an option to fall back on. Covering one function (raw_input)
instead of ANY function (on stdin) is not a fallback option.

Cool to know that replacing it on built-in level covers most of the
common cases. I never tried it (silly me).

> 
> For example:
> 
>     def readRaw(self, prompt='Please enter your response:'):
>         dialog = wxTextEntryDialog(None, prompt, \
>                                    'Input Dialog (Raw)', '')
>         try:
>             if dialog.ShowModal() == wxID_OK:
>                 text = dialog.GetValue()
>                 return text
>         finally:
>             dialog.Destroy()
>         return ''
> 
> And then wherever appropriate add:
> 
>             import __builtin__
>             __builtin__.raw_input = readRaw  # Or the equivalent if readRaw
> is passed as a parameter.
>             del __builtin__
> 
> To do this, though, would require more changes to Boa than I was comfortable
> making. And I wasn't sure you would agree with these changes.

No you have to work with stdin.

>
> It's not like anything is really broken, I'm just looking for a better
> solution and wanted to jot this stuff down while it was fresh in my mind.
> Feel free to disregard this message entirely. I just felt compelled to write
> it.
> 
> To me the best solution would be something inline that wasn't so fragile. It
> shouldn't display a prompt but it must be aware of the prompt that might be
> passed to raw_input(), or that was written directly to stdout (which is all
> that raw_input does anyway). In a way I think it should be modal, which is
> what you get with the dialog approach. There is also the issue of whether to
> leave the prompt and response in the output stream, which looks pretty ugly
> in the case of license(). My readRaw() method basically swallows the prompt
> and response, which looks better when you call license() but might be
> inappropriate in other circumstances where you want the prompt and response
> logged.

In most other circumstances yes :)

> 
> As you can see, I'm still looking for a solution.

For now I'm comfortable with my solution.
Boa explitly goes into prompt mode. The type of request is very
clear and the input format works easily with the rest of the code.

If you really need to change this, you have to keep track of where 
the cursor was when stdin is first read, and the text from there.
I'm currently (automatically) using the normal prompt read code.

I must say that it's kind of a non issue for me as it's not 
functionally different (you type the responses) and I liked the 
explicit prompt. 
And a text entry dialog would be way different than IDLE :)

> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Boa's new handling of stdin in ShellEditor

[Patrick K. O'B. <po...@or...>]

Riaan,

This is probably pretty nitpicky, but I'm not crazy about the new way that
stdin works in the Shell for three reasons. First, the behavior isn't the
same as other IDEs, such as IDLE. Second, the additional prompt is a
distraction when most programs that use stdin already display a prompt.
Third, it is too easy to move the cursor back to a previous command and copy
that line down which displays the ps1 prompt instead of ps4, etc. For
examples of what I mean you can type help() or license().

Now, I tried to change this in Boa so that it was still "inline" as opposed
to a wxTextEntryDialog but then I ran into problems with the hardcoded
expectation of a 4 character prompt so I gave up. One alternative is to go
back to a wxTextEntryDialog and redefine both stdin and raw_input (at the
__builtin__ level, not locals, which was the problem with the previous code
I believe).

For example:

    def readRaw(self, prompt='Please enter your response:'):
        dialog = wxTextEntryDialog(None, prompt, \
                                   'Input Dialog (Raw)', '')
        try:
            if dialog.ShowModal() == wxID_OK:
                text = dialog.GetValue()
                return text
        finally:
            dialog.Destroy()
        return ''

And then wherever appropriate add:

            import __builtin__
            __builtin__.raw_input = readRaw  # Or the equivalent if readRaw
is passed as a parameter.
            del __builtin__

To do this, though, would require more changes to Boa than I was comfortable
making. And I wasn't sure you would agree with these changes.

It's not like anything is really broken, I'm just looking for a better
solution and wanted to jot this stuff down while it was fresh in my mind.
Feel free to disregard this message entirely. I just felt compelled to write
it.

To me the best solution would be something inline that wasn't so fragile. It
shouldn't display a prompt but it must be aware of the prompt that might be
passed to raw_input(), or that was written directly to stdout (which is all
that raw_input does anyway). In a way I think it should be modal, which is
what you get with the dialog approach. There is also the issue of whether to
leave the prompt and response in the output stream, which looks pretty ugly
in the case of license(). My readRaw() method basically swallows the prompt
and response, which looks better when you call license() but might be
inappropriate in other circumstances where you want the prompt and response
logged.

As you can see, I'm still looking for a solution.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

RE: [Boa Constr] Set CVSROOT permanently for a project?

[Patrick K. O'B. <po...@or...>]

Don't I feel stupid. Everything is starting to make sense now. As you can
imagine, I was being "good" and logging out each time. Not any more. Thanks
for the knock on the head. Guess I should read the damn CVS documentation.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of Riaan
Booysen
Sent: Wednesday, July 11, 2001 10:54 PM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Set CVSROOT permanently for a project?

Hi Patrick,

"Patrick K. O'Brien" wrote:
>
> I should have been more specific. I was thinking of the login process. I
was
> thinking it would be nice if I could just select the boa folder, right
> click, Login and boa would know the CVSROOT to login to. I was thinking
that
> maybe it could look for a magic file in the current folder, something like
> __cvsroot__.py that would have the repository info.

There is such a file, it's called .cvspass and it works well!
I think the main point which confuses you is the login process.
When you login to a repository, only the CVSROOT and the password is
stored in the .cvspass file, no actual communication takes place to
the server. Same with Logout, it only removes the entry from .cvspass.

Just don't log out!

>
> Every time I open Boa and do a CVS Login I have to go get the big CVSROOT
> string out of a text file I created and paste it into the dialog. Does
that
> make sense or am I doing something wrong? Do you actually key in the
CVSROOT
> each time you log in?

No, as explained above. I'm permanently "logged in" to about 20 servers.

I access the Boa repository over SSH but it's transparent to Boa.

>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
>
> -----Original Message-----
> From: Riaan Booysen [mailto:riaan@e.co.za]
> Sent: Wednesday, July 11, 2001 10:11 AM
> To: po...@or...
> Cc: Boa Constructor Users
> Subject: Re: [Boa Constr] Set CVSROOT permanently for a project?
>
> Hi Patrick,
>
> "Patrick K. O'Brien" wrote:
> >
> > Is there a way to get Boa to remember the CVSROOT for each project, so I
> > don't have to set it each time?
>
> This is not necessary.
>
> The CVSROOT is now only needed once, when you login.
> Checkout now has a list of logged in servers to choose from.
>
> When you are working in a checked out copy CVS automatically knows
> which CVSROOT you are working in and you don't have to specify it.
>
> >
> > ---
> > Patrick K. O'Brien
> > Orbtech
> > "I am, therefore I think."
> >
> > _______________________________________________
> > Boa-constructor-users mailing list
> > Boa...@li...
> > http://lists.sourceforge.net/lists/listinfo/boa-constructor-users
>
> --
> Riaan Booysen
> ___________________________________________________
> Boa Constructor - RAD GUI building IDE for wxPython
>      http://boa-constructor.sourceforge.net
>
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

Re: [Boa Constr] Reordering Menu Items

[Riaan B. <riaan@e.co.za>]

Hi Gordon,

Gordon Williams wrote:
> 
> Hi,
> 
> Am I able to reorder menu items, or do I need to delete them and then redo
> them in the proper order.  I guess I could also hack the Boa generated code
> to get them in the correct order.

Delete and redo is probably the safest.
If you want to do it in the code by hand, please remember to keep
the window ids consecutive.

I'm not satisfied with window id handling in Boa and will also spend
some time on it as soon as I get a few better ideas ;)

> 
> Regards,
> 
> Gordon Williams
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Set CVSROOT permanently for a project?

[Riaan B. <riaan@e.co.za>]

Hi Patrick,

"Patrick K. O'Brien" wrote:
> 
> I should have been more specific. I was thinking of the login process. I was
> thinking it would be nice if I could just select the boa folder, right
> click, Login and boa would know the CVSROOT to login to. I was thinking that
> maybe it could look for a magic file in the current folder, something like
> __cvsroot__.py that would have the repository info.

There is such a file, it's called .cvspass and it works well!
I think the main point which confuses you is the login process.
When you login to a repository, only the CVSROOT and the password is
stored in the .cvspass file, no actual communication takes place to 
the server. Same with Logout, it only removes the entry from .cvspass.

Just don't log out!

> 
> Every time I open Boa and do a CVS Login I have to go get the big CVSROOT
> string out of a text file I created and paste it into the dialog. Does that
> make sense or am I doing something wrong? Do you actually key in the CVSROOT
> each time you log in?

No, as explained above. I'm permanently "logged in" to about 20 servers.

I access the Boa repository over SSH but it's transparent to Boa.

> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> -----Original Message-----
> From: Riaan Booysen [mailto:riaan@e.co.za]
> Sent: Wednesday, July 11, 2001 10:11 AM
> To: po...@or...
> Cc: Boa Constructor Users
> Subject: Re: [Boa Constr] Set CVSROOT permanently for a project?
> 
> Hi Patrick,
> 
> "Patrick K. O'Brien" wrote:
> >
> > Is there a way to get Boa to remember the CVSROOT for each project, so I
> > don't have to set it each time?
> 
> This is not necessary.
> 
> The CVSROOT is now only needed once, when you login.
> Checkout now has a list of logged in servers to choose from.
> 
> When you are working in a checked out copy CVS automatically knows
> which CVSROOT you are working in and you don't have to specify it.
> 
> >
> > ---
> > Patrick K. O'Brien
> > Orbtech
> > "I am, therefore I think."
> >
> > _______________________________________________
> > Boa-constructor-users mailing list
> > Boa...@li...
> > http://lists.sourceforge.net/lists/listinfo/boa-constructor-users
> 
> --
> Riaan Booysen
> ___________________________________________________
> Boa Constructor - RAD GUI building IDE for wxPython
>      http://boa-constructor.sourceforge.net
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Menu separator

[Riaan B. <riaan@e.co.za>]

Hi Gordon,

Gordon Williams wrote:
> 
> Hi,
> 
> I would like to use a separator in a menu.
> 
> Is it possible to add something like:
> 
> wxMenu.AppendSeparator()

No,

> 
> using Boa, or do I have to insert the separator from the frame __init__ by
> hand?

I wish you could but there is no InsertSeparator, only AppendSeparator.

This is because of a general limitation in Boa. Collection properties 
can only have 1 method in the generated source. In this case it is
wxMenu.Append. When this limitation is removed menu's will support
separators. Hopefully soon...

> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

RE: [Boa Constr] Set CVSROOT permanently for a project?

[Patrick K. O'B. <po...@or...>]

I should have been more specific. I was thinking of the login process. I was
thinking it would be nice if I could just select the boa folder, right
click, Login and boa would know the CVSROOT to login to. I was thinking that
maybe it could look for a magic file in the current folder, something like
__cvsroot__.py that would have the repository info.

Every time I open Boa and do a CVS Login I have to go get the big CVSROOT
string out of a text file I created and paste it into the dialog. Does that
make sense or am I doing something wrong? Do you actually key in the CVSROOT
each time you log in?

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: Riaan Booysen [mailto:riaan@e.co.za]
Sent: Wednesday, July 11, 2001 10:11 AM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Set CVSROOT permanently for a project?

Hi Patrick,

"Patrick K. O'Brien" wrote:
>
> Is there a way to get Boa to remember the CVSROOT for each project, so I
> don't have to set it each time?

This is not necessary.

The CVSROOT is now only needed once, when you login.
Checkout now has a list of logged in servers to choose from.

When you are working in a checked out copy CVS automatically knows
which CVSROOT you are working in and you don't have to specify it.

>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
>
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Reordering Menu Items

[Gordon W. <g_...@cy...>]

Hi,

Am I able to reorder menu items, or do I need to delete them and then redo
them in the proper order.  I guess I could also hack the Boa generated code
to get them in the correct order.

Regards,

Gordon Williams

[Boa Constr] Menu separator

[Gordon W. <g_...@cy...>]

Hi,

I would like to use a separator in a menu.

Is it possible to add something like:

wxMenu.AppendSeparator()

using Boa, or do I have to insert the separator from the frame __init__ by
hand?

Re: [Boa Constr] CVS woes

[Riaan B. <riaan@e.co.za>]

Hi,

"Patrick K. O'Brien" wrote:
> 
> I got the latest CVSExplorer.py from CVS (1.15 2001/07/11 13:41:26 riaan).
> And that *might* have reduced the number of red files, but I still have
> plenty of them. This is based on a fuzzy memory of how many were red before
> I updated from CVS, so I could be completely wrong. I'll try to debug this
> if I get some free time. In the mean time, here are the main files that show
> up as red. (There are plenty more in subfolders.) Maybe you can see a
> pattern:
> 
> Browse.py
> Bugs.txt
> Changes.txt,
> Credits.txt,
> Explorer.msw.cfg,
> GCFrame.py
> HTMLCyclops.py
> README.TXT
> RunCyclops.py
> Search.py
> Todo.txt
> popen2import.py
> Palette.umllay
> 

From the files it doesn't seem as tho this is the case, but you have 
to also remember that if you made a non conflicting change to a file, 
it will still show as modified after an update. Update merges the
repository version with your local copy.

Please mail me the file CVS/Entries and also a directory listing of 
your boa root. e.g. dir > dirlist

> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> -----Original Message-----
> From: Riaan Booysen [mailto:riaan@e.co.za]
> Sent: Wednesday, July 11, 2001 8:44 AM
> To: po...@or...
> Cc: Boa Constructor Users
> Subject: Re: [Boa Constr] CVS woes
> 
> Hello,
> 
> The modified colouring logic is done on filedates, have a look at
> CVSExplorers.cvsFileLocallyModified.
> Turns out with some versions of cvs the file date is sometimes not
> written with a zero padded day.
> I've updated CVSExplorer.py
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Set CVSROOT permanently for a project?

[Riaan B. <riaan@e.co.za>]

Hi Patrick,

"Patrick K. O'Brien" wrote:
> 
> Is there a way to get Boa to remember the CVSROOT for each project, so I
> don't have to set it each time?

This is not necessary.

The CVSROOT is now only needed once, when you login.
Checkout now has a list of logged in servers to choose from.

When you are working in a checked out copy CVS automatically knows
which CVSROOT you are working in and you don't have to specify it.

> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Something funny in Menus

[Riaan B. <riaan@e.co.za>]

Hi Gordon, I think I fixed this in CVS.

Argh, didn't check it in, it's in now.

Thanks.

Gordon Williams wrote:
> 
> Hi,
> 
> Something is happening in menus that I dont understand.  It causes:
> 
> 10:14:17:     AttributeError: 'CollectionItemInitParse' instance has no
> attribute 'class_name'Traceback (most recent call last):
> 10:14:17:     AttributeError: 'CollectionItemInitParse' instance has no
> attribute 'class_name'  File "G:\CVSFIL~1\Boa\boa\Views\CollectionEdit.py",
> line 105, in OnObjectSelect
> 10:14:17:     self.collEditView.selectObject(event.m_itemIndex)
> 10:14:17:       File "G:\CVSFIL~1\Boa\boa\Views\CollectionEdit.py", line
> 310, in selectObject
> 10:14:17:     self.inspector.selectObject(self.companion, false)
> 10:14:17:       File "G:\CVSFIL~1\Boa\boa\Inspector.py", line 207, in
> selectObject
> 10:14:17:     self.statusBar.SetStatusText(compn.GetClass(), 1)
> 10:14:17:       File "G:\CVSFIL~1\Boa\boa\Companions\BaseCompanions.py",
> line 129, in GetClass
> 10:14:17:     return self.textConstr.class_name
> 10:14:17:     AttributeError: 'CollectionItemInitParse' instance has no
> attribute 'class_name'
> 
> when I select one of the items (menu items) in the items window.
> 
> Regards,
> 
> Gordon Williams
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net