On 3/16/10, Markus <markus.wei...@googlemail.com> wrote:
>
> session -> command
>
> Excellent.
Yeah, I like this idea too. Will very probably be the 4.0 syntax.
> 1) I propose to build a library: a collection of code.
>
> library
> library.forms
> library.searches
We have talked about doing this several times. Just need to 1) decided
where to put it, and 2) do it. There are pro's and con's to putting it
in the docs, solutions, and your suggestion--some third location. We
actually already have the solutions.snippets section, but it is
experiencing absolutely no growth. I think having it in the docs would
be the best place. Thoughts?
Also, I wonder if we should generate a tagging system. It would be
really cool if we could scan each snippet, identify the key
functions/commands/conditions etc, and tag them that way,
automatically...
> 2) I propose to create a built-in API. The current help system is for
> programmers. Users need something else:
>
> search:
> * group: Limits search results to a group.
> * count: ...
> * link: ...
Agreed. This was the idea behind the handbook section. All the pages
are setup. We just need people to fill in the documentation. My ideas
was, for each function page in the barn to have all the help
information at the top and then a button at the bottom for a
programmer that wanted to see the actual code. But this is definitely
going to take some time.
Looking at it now, it doesn't seem to even be working quite right.
I'll have to look at it. But probably we'll revisit the docs more
thoroughly after 4.xx as some things will change.
> Config options . . .
Thanks for sharing yours. I'll note them, for future reference... I
don't think mailAddress is used any more as it was replaced with
sitemail. Unless you are using an old plugin or something.
> All others. I would place them in a prominent way on a docs page that
> one can go through to see what settings are available.
When going through the code I intend to simultaneously index all the
existing options and post them somewhere.
> For unused functions and the like I propose you make a list of
> everything you are willing to drop, send it to the list or make a poll
> and see how many of us will complain. I don't think many of us can
> tell you to drop function x, if we don't use it in the first place.
Yes, this is my current plan... Just giving a heads up now.
> Or strip out everything you want and make some funny Russian roulette
> release.
Uh, no--this one is not my current plan. :)
> > My plan is to support both, the Lite and Pro versions, as two separate
> > downloads. Possibly with a small fee for the extra Pro features,
> > perhaps on a suggested donation basis. Both Lite and Pro will run on
> > the exact same basic engine, and the Lite version will not be disabled
> > or weakened in any way, and it will remain, as always, free.
>
> Now, I'm relieved. I was a bit worried when I heard Lite and Pro. Do
> yourself a favor and think again about the naming. Neither one is Lite
> and neither one is Pro. Isn't it more Pro if you program your site
> from scratch? Also Lite users will experience mental trauma and feel
> like second-class users. There is a high chance I would not even be
> writing this if I spotted the evil words Lite and Pro the first time I
> visited BoltWire.com. I always expect Lite versions to be "forgotten"
> sooner or later or to be designed to miss just the one feature you
> can't live without.
Good points. And glad you are relieved. I intend to use the exact same
engine for both--with nothing hokey about the smaller version. I want
a strong user community because it makes the code stronger. And that
requires free, compelling software. And from the beginning, BoltWire
has been a ministry project, never a commercial one. If there is a
paid version it would only be to help defray some of the costs
involved (time mostly) for maintaining the extra feature set.
> What about "BoltWire Scratch"/"BoltWire Core" and "BoltWire
> Box"/"BoltWire CMS". Just keep it neutral.
I think just BoltWire and BoltWire CMS will work fine.
> Users could by the way contribute their own BoltWire editions for
> custom scenarios. Sounds a lot like Linux.
Correct, I'm not really sure how the BoltWire CMS will work. What if
you just want the blog and rss? Will there be an easy way to turn off
the store and forum pages? In some ways it is smarter to just maintain
a bunch of separater plugins. Pick and choose. But in reality, it is
easier for me to maintain them as a group. On my site, I have all
these things (blog, forum, rss, store, email verification, passwords,
etc.). If something breaks I fix it immediately for my site--and don't
go back and patch every plugin involved. If I could run my site off a
"BoltWire CMS", I patch that core and release it. And
bingo--everything is working. So that's part of my rationale behind
it. I'm hoping it will give folks a better user experience than trying
a half dozen plugins that have somehow been outdated.
> Maybe mentioned before. Please improve the search:
>
> * Wildcard asterisk ("bolt*")
Try using words=false as a search parameter. Not sure it will work,
but I think it will. If not, let me know and we can change this
somehow... Ahhh, actually, I see an easy place... I'll put this in
the next release!!! You can now even do: [(search text="one &&
bolt*")]
> * No results found? Please tell me (maybe optionally).
[(template none)] No results found...
> * Limiting results? Please tell me and if there is a way to see more.
in site.config, set:
searchLimit:
or if you want to just turn off the limit in certain situations, add
count=false as a search parameter.
I think in the last release I changed the default from 25 to null like
above, to give full returns unless a count is specified. I'm not sure
which is a better default, but only getting partial returns was
confusing to me! Of course we don't want sites timing out from some
overly ambitious search criteria...
> Maybe search could produce a link to display the next x results.
This is on the agenda. Probably will have automatic prev/next links to
give multipage results. Not sure exactly how to do this, or how to
make it flexible enough for my taste. But we'll get something
eventually.
There is this plugin solution...
http://www.boltwire.com/index.php?p=solutions.search.multipage
Cheers,
Dan
I do plan
Cheers,
Dan
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to boltw...@googlegroups.com.
To unsubscribe from this group, send email to
boltwire+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en.
