Hi all,
wxPython 2.8.7.0 will be coming soon, so if you have any updates to contribs, or new contribs to make, now is the time to get them into the repository or sent to me.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Robin,
I have one small request if is not too late…
could you please make it so that wx.BitmapFromBufferRGBA could take
only width and height and if the bytes are missing create an empty buffer in C++
Or maybe create a wx.EmptyBitmapRGBA that does just that.
your
def EmptyBitmapRGBA((width, height)):
bytes = array.array
(‘B’, [0] * widthheight4)
return wx.BitmapFromBufferRGBA(width, height, bytes)
solution suggested some time back is wonderful, better than manually setting the alpha of every bit BUT the creation of the array is insanely SLOW… i.e. for a buffer of (850, 564), that I need, it take 300 ms…
Thank you in advance.
Peter.
On Nov 13, 2007 8:03 PM, Robin Dunn robin@alldunn.com wrote:
Hi all,
wxPython 2.8.7.0 will be coming soon, so if you have any updates to
contribs, or new contribs to make, now is the time to get them into the
repository or sent to me.–
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail:
wxPython-dev-help@lists.wxwidgets.org
–
There is NO FATE, we are the creators.
Peter Damoc wrote:
Robin,
I have one small request if is not too late...
could you please make it so that wx.BitmapFromBufferRGBA could take only width and height and if the bytes are missing create an empty buffer in C++Or maybe create a wx.EmptyBitmapRGBA that does just that.
your
def EmptyBitmapRGBA((width, height)):
bytes = array.array ('B', [0] * width*height*4)
return wx.BitmapFromBufferRGBA(width, height, bytes)solution suggested some time back is wonderful, better than manually setting the alpha of every bit BUT the creation of the array is insanely SLOW.... i.e. for a buffer of (850, 564), that I need, it take 300 ms...
Does wx.EmptyBitmap(width, height, 32) work? It should create a RGBA bitmap, but the content may not be initialized on all the platforms...
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
It works on Windows so… I’m satisfied
Thank you.
One small curiosity… why was Editra selected to be included ? I never heard of this project until I read about it in the preview description.
Why not PyPE or Peppy?
Peter.
On Nov 15, 2007 3:07 AM, Robin Dunn robin@alldunn.com wrote:
Peter Damoc wrote:
Robin,
I have one small request if is not too late…
could you please make it so that wx.BitmapFromBufferRGBA could take only
width and height and if the bytes are missing create an empty buffer in C++Or maybe create a wx.EmptyBitmapRGBA that does just that.
your
def EmptyBitmapRGBA((width, height)):
bytes = array.array (‘B’, [0] * widthheight4)
return wx.BitmapFromBufferRGBA(width, height, bytes)solution suggested some time back is wonderful, better than manually
setting the alpha of every bit BUT the creation of the array is insanely
SLOW… i.e. for a buffer of (850, 564), that I need, it take 300 ms…
Does wx.EmptyBitmap(width, height, 32) work? It should create a RGBA
bitmap, but the content may not be initialized on all the platforms…–
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
–
There is NO FATE, we are the creators.
Peter Damoc wrote:
Thank you.
One small curiosity... why was Editra selected to be included ? I never heard of this project until I read about it in the preview description.
Why not PyPE or Peppy?
Kevin pointed it out to me, and when I gave it a test run the thought crossed my mind that this is much like what PyAlaMode wanted to be when it grew up, but since it never made it that far Editra seemed to be a good replacement. I then saw how well Editra integrates with OS X (correctly handles files dropped on the icon, can be set as the default editor for supported file types, has a document icon, etc.) and thought that it would be a very good example of how to do these things too.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?
--bb
On Nov 16, 2007 3:37 AM, Robin Dunn <robin@alldunn.com> wrote:
Peter Damoc wrote:
>
>
> Thank you.
>
> One small curiosity... why was Editra selected to be included ? I never
> heard of this project until I read about it in the preview description.
> Why not PyPE or Peppy?Kevin pointed it out to me, and when I gave it a test run the thought
crossed my mind that this is much like what PyAlaMode wanted to be when
it grew up, but since it never made it that far Editra seemed to be a
good replacement. I then saw how well Editra integrates with OS X
(correctly handles files dropped on the icon, can be set as the default
editor for supported file types, has a document icon, etc.) and thought
that it would be a very good example of how to do these things too.--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
The question is could peppy be merged into Editra?
There is soooooo much duplicate effort on these editors… this is silly… and the worst part of it might be that the wxpython community looks highly out of focus.
So Editra has a solid foundation, let’s build on it, let’s make it feature complete.
Peter.
On Nov 16, 2007 1:32 AM, Bill Baxter wbaxter@gmail.com wrote:
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?
–
There is NO FATE, we are the creators.
Bill Baxter wrote:
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?
Does it support multiple Frames???
-CHB
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov
Hi Chris,
Bill Baxter wrote:
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?Does it support multiple Frames???
Try it out and see! You can get it from http://www.editra.org if you don't want to get it from the latest wxPython pre-release.
Anyway, I can't speak for Cody regarding Editra so I hope he'll correct me if I'm wrong, but from my understanding of the project I don't think Editra currently aims to be a Python-based emacs replacement, or at least not one that can do all the things Robin needs to ween him off the "old" emacs. 
From what I understand, Emacs is as much a framework to write text editors in as it is a text editor, so IMHO it probably makes sense to have a project focused just on replicating those capabilities in wxPython. Editra and Peppy actually do share code, too, so I don't feel it's really a 're-invent the wheel' scenario here. Just making two different wheels for two different target groups.
Thanks,
Kevin
On Nov 19, 2007, at 5:16 PM, Christopher Barker wrote:
-CHB
--
Christopher Barker, Ph.D.
OceanographerEmergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main receptionChris.Barker@noaa.gov
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
Hello,
Bill Baxter wrote:
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?Does it support multiple Frames???
Try it out and see! You can get it from http://www.editra.org if you don't want to get it from the latest wxPython pre-release.
Anyway, I can't speak for Cody regarding Editra so I hope he'll correct me if I'm wrong, but from my understanding of the project I don't think Editra currently aims to be a Python-based emacs replacement, or at least not one that can do all the things Robin needs to ween him off the "old" emacs.
Thanks,
Kevin
It would indeed be a surprise to me if it was to be an Emacs replacement as I have honestly spent less than an hour in my entire life using Emacs. I have however received a number of emails from people saying they are glad to have found it to use it as a means to replace Emacs in their daily lives.
Editra at its core is only meant to be a text editor that specializes in editing code nothing more nothing less, or as they say in the Unix world do one thing and do it well. Changing this for those that need more is what the plugin framework is there for, with plugins it can easily be transformed in to a "do more than just edit text" program.
As mentioned peppy already does use a fairly substantial amount of code from Editra so it isn't so much a 're-invent the wheel' scenario. On a side note however I have never understood why so many people cast re-inventing the wheel in negative terms, things have been done, redone, thrown away, reborn and built upon in all aspects of technology throughout the ages, this is how progress is made and new ideas are born. There is a certain level of efficiency that can be gained from reusing the same wheel over and over again but if efficiency in that area is/was the only goal we would likely still be rolling around in vehicles with stone or wooden wheels
Regards,
Cody Precord
On Nov 20, 2007, at 12:07 AM, Kevin Ollivier wrote:
Hi Cody,
IMHO, having a wheel and reinventing it to make it better is a GREAT THING!
Having no good wheel or a broken wheel and having 20 people perpetualy duplicating each others efforts is another thing… not so great…
To give you an example… I thing that a lot of editors started as an extension of PythonSTC class from the Demo. Well at least some of them started that way…
There should have been an editor component inside the wx.stc lib… one that would have taken care of most tasks “reinvented” by some of the editors programmers. An editor component that would have taken care of at least Python language… this way a lot of the effort spent reinventing the wheel would have resulted in patches to wxpython, patches that would have beneffited a larger audience…
Of course… this is only an opinion… personal and maybe wrong… I think that wxpython should encourage a higher level API that will alow beginners to use highly complex components without having to bother with the internals… A beginner should be able to compose an app using components like FileBrowser, Editor or PhotoBrowser or MoviePlayer or something else at this level.
When you start programming you don’t “custom”… you need “working”.
Peter
On Nov 20, 2007 9:24 AM, Cody Precord < codyprecord@gmail.com> wrote:
On a side note however I have never understood why so many
people cast re-inventing the wheel in negative terms, things have
been done, redone, thrown away, reborn and built upon in all aspects
of technology throughout the ages, this is how progress is made and
new ideas are born. There is a certain level of efficiency that canbe gained from reusing the same wheel over and over again but if
efficiency in that area is/was the only goal we would likely still be
rolling around in vehicles with stone or wooden wheels
–
There is NO FATE, we are the creators.
Hi Cody,
Hello,
Bill Baxter wrote:
Ooh, Editra does look interesting. Could it be the python-based emacs
replacement everyone has been looking for?Does it support multiple Frames???
Try it out and see! You can get it from http://www.editra.org if you don't want to get it from the latest wxPython pre-release.
Anyway, I can't speak for Cody regarding Editra so I hope he'll correct me if I'm wrong, but from my understanding of the project I don't think Editra currently aims to be a Python-based emacs replacement, or at least not one that can do all the things Robin needs to ween him off the "old" emacs.
Thanks,
Kevin
It would indeed be a surprise to me if it was to be an Emacs replacement as I have honestly spent less than an hour in my entire life using Emacs. I have however received a number of emails from people saying they are glad to have found it to use it as a means to replace Emacs in their daily lives.
Editra at its core is only meant to be a text editor that specializes in editing code nothing more nothing less, or as they say in the Unix world do one thing and do it well. Changing this for those that need more is what the plugin framework is there for, with plugins it can easily be transformed in to a "do more than just edit text" program.
As mentioned peppy already does use a fairly substantial amount of code from Editra so it isn't so much a 're-invent the wheel' scenario. On a side note however I have never understood why so many people cast re-inventing the wheel in negative terms, things have been done, redone, thrown away, reborn and built upon in all aspects of technology throughout the ages, this is how progress is made and new ideas are born. There is a certain level of efficiency that can be gained from reusing the same wheel over and over again but if efficiency in that area is/was the only goal we would likely still be rolling around in vehicles with stone or wooden wheels
As the saying goes, everything in moderation. There's just too many duplicate efforts going on in open source, and most of them are not for very good reasons. (i.e. many of them don't even explore existing approaches to learn from them) It leads to a glut in programs, most of which aren't really that different from one another and are re-writing basic things like highlighting code, and as the number of projects grows, it becomes obvious that they could benefit from consolidation because you start to see that most of them have fairly simple/obvious bugs in core code. The end result is, and I've done this myself a few times, that people go around downloading a bunch of programs, and find that about 1/3 won't run, 1/3 just aren't far enough along to be useful, and the last third are mired in bugs. That leaves zero viable options, and so I go back to my commercial/freeware editor.
This actually hurts projects like wxPython, though, because we can never get a large enough community together to produce even one good editor that competes with alternatives provided by the native toolkits. Sadly, the conclusion I think many new users will draw from that fact is that wxPython is incapable of producing something as good as the alternatives. That's why I'm hoping that bundling and promoting some of the better tools out there will encourage people to build upon those tools rather than start from scratch (again).
Regards,
Kevin
On Nov 20, 2007, at 12:24 AM, Cody Precord wrote:
On Nov 20, 2007, at 12:07 AM, Kevin Ollivier wrote:
Regards,
Cody Precord
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
The "problem" with open source is there's no boss calling the shots,
no GvR with bdfl capacity calling meetings and directing the action.
There's just a bunch of disparate folks working mostly on our own. We
all do this for fun, after all, and it's more fun to write code than
hash out over email the best way to do something.
Believe me, I enjoy contributing to others' projects. If nothing
else, it saves you the headache of doing all the project management
stuff. A year and a half ago if I had found a project that could do
multilple frames and multiple views of the same file, I would have
contributed to that. But it felt wrong to me to fork someone else's
code with the intent to make major changes in the architecture because
it wouldn't support what I wanted. Forkings always turn into ugly
affairs (see xfree86 vs x.org for a sorta-recent example).
I don't have a problem with different editors and don't see it as a
fracturing of the wxPython community. I would enjoy it if we were
able to write more reusable components, however.
Related to peppy and Editra: as Cody pointed out, we're sharing some
code, and as he also pointed out our target audiences are somewhat
different. For instance, Cody came up with a scheme to relate all of
the stc styles so that highlighting was consistent across the stc
lexers. If you've looked at the scintilla source, you know that
scintilla just haphazardly assigned style values, so that comments in
one language have the same id as keywords in another, so Cody made a
wrapper on top of that to make it consistent. Comments are always
styled the same regardless of language. There's an example of not
reinventing the wheel -- I'll now never have to write that because
he's done a good job with it. It frees me to focus on emacsy things
that won't be a part of Editra.
Rob
On Nov 20, 2007 1:57 AM, Peter Damoc <pdamoc@gmail.com> wrote:
IMHO, having a wheel and reinventing it to make it better is a GREAT THING!
Having no good wheel or a broken wheel and having 20 people perpetualy
duplicating each others efforts is another thing.... not so great...
Hi Rob,
IMHO, having a wheel and reinventing it to make it better is a GREAT THING!
Having no good wheel or a broken wheel and having 20 people perpetualy
duplicating each others efforts is another thing.... not so great...The "problem" with open source is there's no boss calling the shots,
no GvR with bdfl capacity calling meetings and directing the action.
There's just a bunch of disparate folks working mostly on our own. We
all do this for fun, after all, and it's more fun to write code than
hash out over email the best way to do something.Believe me, I enjoy contributing to others' projects. If nothing
else, it saves you the headache of doing all the project management
stuff. A year and a half ago if I had found a project that could do
multilple frames and multiple views of the same file, I would have
contributed to that. But it felt wrong to me to fork someone else's
code with the intent to make major changes in the architecture because
it wouldn't support what I wanted. Forkings always turn into ugly
affairs (see xfree86 vs x.org for a sorta-recent example).I don't have a problem with different editors and don't see it as a
fracturing of the wxPython community. I would enjoy it if we were
able to write more reusable components, however.
That too, though, must come from the community. And herein lies the rub, as they say. Everyone wants to have reusable components, that are general purpose and have their bugs ironed out, but not many people want to invest the time into creating such components because it (apparently) isn't very fun and isn't really a one-person effort, unless that person has a wealth of experience. So how will wxPython get all these things it sorely needs?
To be honest, over the past couple years I've learned to more actively engage the community (and offer my help as well) because I learn so many things through discussions and the experiences of others that I could never have learned simply through trial and error, and I also want to pass what I can on to new users coming in as a way of returning the favor. As a result, I can definitely say that my coding ability has greatly improved, and I'm much more satisfied with the code I write these days. (And by satisfied, I mean I honestly feel I write less bugs thanks to better understanding of MVC, etc. and I catch more of the bugs I do write quicker thanks to automated testing and TDD approaches picked up from looking at others' coding practices and discussing with others.)
So I don't know, while I can see the argument that it might be more fun to hack on something by yourself, I personally find it a hundred times more fun and satisfying to work together with a devoted community of users to build shared solutions that we can all benefit from, and watch the community as a whole improve, even if it means me going the extra mile and doing the tedious stuff. I think that is the true essence of open source (not just "getting the code out there"), in fact.
Regards,
Kevin
On Nov 20, 2007, at 9:22 AM, Rob McMullen wrote:
On Nov 20, 2007 1:57 AM, Peter Damoc <pdamoc@gmail.com> wrote:
Related to peppy and Editra: as Cody pointed out, we're sharing some
code, and as he also pointed out our target audiences are somewhat
different. For instance, Cody came up with a scheme to relate all of
the stc styles so that highlighting was consistent across the stc
lexers. If you've looked at the scintilla source, you know that
scintilla just haphazardly assigned style values, so that comments in
one language have the same id as keywords in another, so Cody made a
wrapper on top of that to make it consistent. Comments are always
styled the same regardless of language. There's an example of not
reinventing the wheel -- I'll now never have to write that because
he's done a good job with it. It frees me to focus on emacsy things
that won't be a part of Editra.Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org