Maximum Page Length

Thank you! I took a look at the discussion. Did you make any decision on allowing larger pages? Is there any chance that we could have control over the maximum page length? I tend to work with larger files and prefer not to split them up.

Thanks Dale!

But, I wonder if you could completely remove the limit. I posted on the "Pages longer than 32K cannot be edited" page this message. It pretty much summarizes my problem. Basically, I am loathe to separate my index page into smaller ones.

------------------

@Julio

Good point. The inner pages link feature would be a great fix for this, except that I have the pages in alphabetical order and would need 26 inner page links. Bladewiki only supports 9. So, there is a limit on it as well.

I've got about 400 pages total of information right now (all but a few much smaller than 32k) and I have one page to index them all (about 67k now and growing). It is difficult to see how I would split up this index page. If I split it up into 26 separate index pages (the most obvious solution) it would be impossible to see everything at one glance, much less print it out on occasion.

Ideally, the size limit on pages would be removed entirely. But, if Dale could give us more innerpage links, that would solve the problem as well.

Several of the .NET classes used internally by the app require a limit to be set.
===>Thanks for explaining this. I was not sure what the rationale was for the limit.

I could just pick some random very-large number, but I'm reluctant to do this... largely because I use this primarily as a mobile app, and I don't want the app to allocate big chunks of memory for handling large strings.
===>That makes sense. I am using this on my netbook (I have an ipod, so cannot use it there) so I have different needs.

I guess I could try and workaround this by providing some way to modify this on the fly - so if you do something that would exceed the limit, modifying all of the runtime classes to set a new maximum. This would be a less trivial piece of work. Something to think about, but not something that I've got time for at the moment, sorry.
===>Understood. My workaround (editing the files in Notepad) will work for now.

It would be nice if there was a setting in the menu so that we could modify it ourselves (like the nested page limit--we can modify this from 0 to 9) to have file sizes ranging from say 32kb to 32mb. That way users could modify it based on the platform they are using.

Alternatively, maybe we could have different versions for the laptop and mobile device, though I suspect this would simply mean more work for you.

Would you be willing to consider increasing the number of nested pages we could include?

I don ́t see here many people needing more than 64 KB per page Chistopher.

IMHO, to not interfere with the general scheme of priorities, it will be a good idea to wait for more opinions.

Besides, I understand that bLADE Wiki is not a commercial application. It is just the generous decision of Dale to share a great piece of software made to satisfy his needs.

It should be nice that all of us don ́t forget this anytime. :)

@Julio

Good points! I probably do not represent a large number of people. And, I would like to stress that I am using a workaround now (editing Notepad outside of BladeWiki) that solves the problem. I would only like to see the option to increase page sizes if it was not too much trouble for Dale.

Perhaps some background is in order. I have tried out dozens of wiki-type programs in the hope of finding an application that functions as well as VoodooPad for Mac. Alas, it does not seem to exist. They all have some kind of flaw (no unicode support, etc.) or less robust features (automatic linking of terms, search capability, etc.). For a while I tried OneNote and was pretty pleased with it, even though it also fell short of VoodooPad. Over time, however, it gobbled up huge chunks of memory and became too large to easily transfer from computer to computer. Specifically, links to PDF / WORD files caused it save those files in a separate cache that quickly grew unwieldy and kept trying to come along with it. Very, very frustrating. It also cost an arm and a leg.

I am a historian and BladeWiki is definitely the best program out there (in my opinion) for my work. I can easily take notes on all the historical source materials, secondary works, and my own ideas in a format that is easily searched and moved about from computer to computer, because this is one of the few programs that saves the files in text format and provides support for unicode. Most of my work is in Chinese and Japanese, and I have no problem using these files. BladeWiki has quite literally revolutionized how I do my work. No longer do I have hundreds of WORD files (the way I did things a few years ago). Now it is all tight, compact, and user-friendly.

I am EXTREMELY grateful to Dale for making this product, and I would gladly pay for it if it were commercially distributed. Thanks Dale!

Before to find bLADE Wiki I was asking myself :

How it can be done that it not exists one application syncronizable between PC&PPC, just able to exploit the essence of the knowledge building tools of this era, let us say: the hypertext ???

And voila! there it is, and yes, bLADE Wiki is really a brilliant work.

As per your comments I see that you also understand the importance off to let this application growing in the way, I guess, he has done till now: as close as possible of the side of the spontaneity and simplicity.

Chistopher, about this 9 nested pages limitation...



let me assure that we are speaking of the same thing: Reading what is in Help about "Protecting against loops" ( see annex), I can be wrong, but I understand, that the limit is referred to the max number of pages nested one iside the other, but it say nothing about wall to wall nested pages in a page, let us say, the limit is referred to ...



Have you tried to put more than nine nested pages, wall to wall, in a page ?

( ... and remember : to check : "Include link to nested page" is also interesting. )

ANNEX _______________________________________________________________

source : http://92.48.117.50/~dalelane/bladewi...

Protecting against loops

If you have PageA, which has a line to include the contents of PageB in it.

And PageB has a line to include the contents of PageA in it.

You could get stuck in a loop.

To protect against this, there is a limit to how many times an included page can itself include other pages. This limit can be modified in Preferences.

Setting the limit to:

0 disables this feature - no page can include other pages
1 a page can dynamically include the contents of another page. but any included page is not allowed to itself include any others (attempts to do this will just be displayed as the plain [^pagename] text)
2 a page can dynamically include the contents of another page. any included page can also itself include another. But no deeper
... and so on

You can play with this by including the contents of a page within itself:

Page: mytestpage

Start of page
[^mytestpage]
End of page

Try this with different values for nested page limits, and see how it works.

Thanks Julio! I had misunderstood the nested features function. I have split the index page into 26 pages (one for each letter) and I have a nested page link for each of them in the index page. I think this will work after all. With the new 64k page limit I doubt any of the sub-pages will have any problems for some time to come.

Congratulations Christopher I am glad to hear it.
;) ... case of you surpass the 16 printed sheet of paper just for one letter of the index, perhaps you should considere to migrate of platform ...