http://blog.gmane.org/gmane.comp.python.wikidpad hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.wikidpad/5097 <pre> Great! This is much better because it allows to create and ship a modified version if tweaks are needed. Additionally it even works with wxPython 2.8.10.1 (the default Windows binary version). Thank you very much. Michael ------------------------------------ </pre> Michael Butscher 2013-05-15T21:27:06 http://permalink.gmane.org/gmane.comp.python.wikidpad/5096 <pre>So I was getting a bit confused as to what this http://xoomer.virgilio.it/infinity77/AGW_Docs/aui.auibook.AuiNotebook.html#aui.auibook.AuiNotebook.SavePerspective was referring to. Then I realised that there is a python implementation of Aui in the Advanced Generic Widgets, which does support saving/loading of perspectives. Just given it a quick test and it works! How about if we use this instead Michael? Ross On 06/05/13 11:37, Ross wrote: ------------------------------------ </pre> Ross 2013-05-15T09:10:11 http://permalink.gmane.org/gmane.comp.python.wikidpad/5095 <pre>For most people none. If you happen to be a vi(m) user then you'll probably find it useful. Its an implementation of a subset of the commands/key bindings and modes present in the vi (or rather vim) text editor. Vi(m) has quite a steep learning curve but once you get used to it, it is (in my opinion) a much more efficient way of editing text. I guess that one of the biggest advantages is that it gives more power to the keyboard - pretty much anything that you need to do can be done with a few keystrokes - speeding things up and removing the need to keep switching to the mouse. I won't go into detail about how it works as there are hundreds of tutorials out there that cover the basics. As to why it get so many updates, this is mostly due to one of two reasons: 1) I find a bug that annoys me enough that I finally decide to fix it. Unfortunately, due to lack of foresight when I started writing the implementation (and just plain incompetence on my part) this does happen. 2) I think of some feature (or learn a new vi command) that I think will be useful and add it. Do I think its worth learning vi(m)? If you have the time to invest I would say yes (bear in mind your productivity will probably drop a bit initially), but it all comes down to personal preference. Some people love it, others hate it - preferring the (evil) that is Emacs. Long story short, if you like the vi(m) way of doing things you may find it useful. If not it has no real bearing on anything else. Ross On 13/05/13 22:15, green_greasy wrote: ------------------------------------ </pre> Ross 2013-05-13T22:24:55 http://permalink.gmane.org/gmane.comp.python.wikidpad/5094 <pre>Hi, I have been intrigued by the amount of work going on over vi mode. What is the benefit of working in vi mode in WikidPad? Graham ------------------------------------ </pre> green_greasy 2013-05-13T21:15:42 http://permalink.gmane.org/gmane.comp.python.wikidpad/5093 <pre>nice, it worked! thanks /bjorn --- In wikidPad-hHKSG33TihhbjbujkaE4pw&lt; at &gt;public.gmane.org, Ross &lt;xkjq&lt; at &gt;...&gt; wrote: ------------------------------------ </pre> bjorn_f_johansson 2013-05-13T19:28:43 http://permalink.gmane.org/gmane.comp.python.wikidpad/5092 <pre>Sorry, I spend pretty much all of my time in vi mode these days (which uses a different search system) and must have missed your email. I think its a wxPython 2.9 issue. A simple fix like https://bitbucket.org/xkjq/wikidpad_svn/commits/a3e74bea2909d6a34c16b64c3cc00a6c5a406e5a should work. Note: the line numbers may be slightly off as I may have made some other changes that aren't in the beta build (its at the end of the setSelectionForIncSearchByCharPos function). Ross On 13/05/13 07:26, bjorn_f_johansson wrote: ------------------------------------ </pre> Ross 2013-05-13T08:43:23 http://permalink.gmane.org/gmane.comp.python.wikidpad/5091 <pre> Hi, I use 2.3beta08 with Sqlite version: 3.7.15.2 wxPython version: 2.9.4.1 Python version: 2.7.4 on Linux-3.8.0-20-generic-x86_64-with-Ubuntu-13.04-raring I have a problem with in Incremental Search, when I search a page and the found string is outside the view, the page does not scroll to see the string. I asked this before, but got no replies so perhaps this is my problem only. /bjorn ------------------------------------ </pre> bjorn_f_johansson 2013-05-13T06:26:35 http://permalink.gmane.org/gmane.comp.python.wikidpad/5090 <pre> On 05/08/2013 09:27 PM, Michael Butscher wrote: Nope - there are no subpages at all. But it seems that the problem stopped occuring -&gt; blacklist works. Since the fix is easy to do and the problem seems to be quite "exotic" I'd consider this case closed. Greetings, Benni I just wanted to ask who'd need something like this... but I won't because I remembered that I started to blacklist several [loremipsum] after copying some logs from a computer to the wiki - so kudos for your foresight :) ------------------------------------ </pre> Benni the Manic 2013-05-09T09:55:23 http://permalink.gmane.org/gmane.comp.python.wikidpad/5089 <pre> I haven't seen this problem yet and can't remember that there were similar reports. There is only a maybe surprising behavior if subpages (pages with slash in it) are used. If you want to suppress e.g. "FooBar" on a page "Page/SubPage" you must enter it as "Page/FooBar" in the blacklist. Sometimes people only want to exclude a CamelCase word but want to use it as [CamelCase] wiki word nevertheless and sometimes they want to exclude special [words in brackets] to show them as plain text instead. Michael ------------------------------------ </pre> Michael Butscher 2013-05-08T19:27:13 http://permalink.gmane.org/gmane.comp.python.wikidpad/5088 <pre>Wikidpad is a great HTML renderer. I can place any HTML or Javascript code into the HTML-body via [body] tag after HTML export. Is it possible to place lines into header as well, eg. links to additional style sheets or javascript files or include meta information? Best regards Dieter ------------------------------------ </pre> dieterst5 2013-05-08T18:09:46 http://permalink.gmane.org/gmane.comp.python.wikidpad/5087 <pre> It should work in the same way in the new beta (and it works for me). Is there a "WikidPad_Error.log" file created in the configuration directory (which can be found by using "Help"-&gt;"About" in the menu and scrolling the info text down to the end)? If so, what is its content (at least the last few 100 lines)? Michael ------------------------------------ </pre> Michael Butscher 2013-05-08T09:39:28 http://permalink.gmane.org/gmane.comp.python.wikidpad/5086 <pre> Fixed with 2.3beta09_02. Fixed with 2.3beta09_02. For an already created wiki you must open options dialog, options page "Headings". Delete the "Heading prefix" entry and set "Heading level" to 2 (or another level you want). Michael ------------------------------------ </pre> Michael Butscher 2013-05-07T20:45:02 http://permalink.gmane.org/gmane.comp.python.wikidpad/5085 <pre>Hi, version 2.3beta09_02 of WikidPad is available as source or with Windows installer (source is identical to revision 406 of the "mbutscher/work" branch of the subversion repository). This is a beta version, so be careful and make backups of important data before using it. If you encounter any problems, you can answer here or mail me. You can download WikidPad from here: http://sourceforge.net/projects/wikidpad/files/ What's new? * New wiki-bound option to set heading level for main title of new pages. Old option to set title prefix is outdated. See [OptionsDialog#*Heading level*] * Bug fixed: Headings in MediaWiki language could span over multiple lines * Bug fixed: Basic formatting (bold, italics, heading) didn't work for MediaWiki syntax Michael ------------------------------------ </pre> Michael Butscher 2013-05-07T20:40:16 http://permalink.gmane.org/gmane.comp.python.wikidpad/5084 <pre>I'm not sure if its a bug or just that you changed this feature or I'm blind and i'm not looking in the correct place for the option. When I wrote + H1, *text* or _italic text_ in the stable version, the text also appears in bold, italic, etc. Thats make the editor more readable In this new beta version I'm not seeing it anymore. Alberto ------------------------------------ </pre> Al 2013-05-06T12:57:20 http://permalink.gmane.org/gmane.comp.python.wikidpad/5083 <pre>Changes are in the last two commits to my repository https://bitbucket.org/xkjq/wikidpad_svn Note: there are also some additional changes to Michaels branch in there. The easiest way to test it would be to do a full checkout, but if you just want to try the AuiNotebook you should only need lib/pwiki/MainAreaPanel.py and the relevant renderer (the one that you use) from lib/pwiki/WikiHtmlView.py lib/pwiki/WikiHtmlView2.py lib/pwiki/WikiHtmlViewWK.py (WikiHtmlView2 is a renderer implemented in using wx.html2 - its a more advanced cross platform preview mode that is only available if you're using the 2.9 series of wxPython.) In other news I figured out a way to sort out the focusing issues I was having without rewriting any of the subcontrol switching code, so it should still be easy to switch between this and the original notebook with a single config option. Ross On 06/05/13 07:24, bjorn_f_johansson wrote: ------------------------------------ </pre> Ross 2013-05-06T10:37:10 http://permalink.gmane.org/gmane.comp.python.wikidpad/5082 <pre>Hi, this sounds interesting! How can I test this for myself? /bjorn --- In wikidPad-hHKSG33TihhbjbujkaE4pw&lt; at &gt;public.gmane.org, Ross &lt;xkjq&lt; at &gt;...&gt; wrote: ------------------------------------ </pre> bjorn_f_johansson 2013-05-06T06:24:32 http://permalink.gmane.org/gmane.comp.python.wikidpad/5081 <pre> Does this really matter? I may be missing something but as far as I can see we can save just as much info as with the current notebook implementation (i.e. the tab order) by making use of the drag events. I haven't done this yet but it should work. If you want to split the screen you'll just have to do it when you open WikidPad - its not perfect but in my opinion its better than not having the feature at all. This can be done by checking the IsShown property for each page (tab). It seems to work fine. I just did a quick test using wxPython 2.8 and it all seems to be working there as well. Ross ------------------------------------ </pre> Ross 2013-05-05T21:21:35 http://permalink.gmane.org/gmane.comp.python.wikidpad/5080 <pre> Unfortunately wxAuiNotebook lacks two important functionalities: 1. Layout can't be saved (wxAuiManager has SavePerspective/LoadPerspective but wxAuiNotebook doesn't have anything like that) 2. It is not possible to detect if a particular tab is currently visible or not (and there are no events fired when this changes). For efficiency some operations in WikidPad are only performed if the respective tab is visible (e.g. in WikiHtmlView most calls to refresh()) Michael ------------------------------------ </pre> Michael Butscher 2013-05-05T19:58:59 http://permalink.gmane.org/gmane.comp.python.wikidpad/5079 <pre>Hi Michael, I've just pushed a patch to my repository that switches the wxNotebook instance to a wxAuiNotebook. This means its possible to display multiple pages side by side. Its mostly a drop in replacement for the original and natively supports a few of the features that were hacked into the original notebook (such as tab dragging). At its current stage its almost fully functional, though as of yet I've only tested on linux with wxPython 2.9.4). Unforutantely I'm having trouble tracking some of the focus events - which causing some issues which switching between editor/preview mode. I suspect the easiest to get around this be to modify some of the SubControl switching functions. How do you feel about switching to the wxAuiNotebook as the main notebook ctrl? or should I try and find another way around this issue so its easy to keep it optional? Ross ------------------------------------ </pre> Ross 2013-05-05T18:55:35 http://permalink.gmane.org/gmane.comp.python.wikidpad/5078 <pre> I will fix this soon This will also be fixed (but may need a bit longer). In MediaWiki a heading must be terminated with the same number of equal signs as it was prefixed: == New Page == The problem with H1 is probably that the terminating equal sign is several lines below the starting equal sign (due to a bug a heading can span over multiple lines, this will also be fixed) I couldn't reproduce this. Michael ------------------------------------ </pre> Michael Butscher 2013-05-05T14:13:24 http://permalink.gmane.org/gmane.comp.python.wikidpad/5077 <pre>Fixed already :-) Awesome. Now the side effects of the new parser :-) The Bold / header &amp; Italics buttons in the UI always use the std syntax, even if the wiki is defined as a mediawiki wiki so do bold &amp; italic keyboard shortcuts .. Something odd about H1 - everything seems to come out bold and newlines aren't honored? New wiki linked pages still use old syntax (++) for header text? New Wiki pages off the top level don't seem to work correctly in terms of formatting (==New Page doesn't render as a header) If you open an old style wiki (in a new window from a new media wiki) - doesn't use correct parser, you have to manually switch it back in the new instance :-) Great start though Graham ------------------------------------ </pre> gf_gollum 2013-05-04T20:37:40 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.wikidpad