Aha, great, putting into the feature list for nest version.

Cheers, linly

On Mar 2, 5:25 pm, Martin <[email protected]> wrote:
> Even for a SQL you have to prepare the data in a texteditor if you not
> want to type in every piece of data by hand.
>
> I assume you have your data ready in some kind of electronic format.
>
> For preparation I would keep these lists offline and merge them
> together in a master list that takes three parameters: entry english,
> translation, xxx for booksource. With this master list you would be
> able to generate the 26 pages for each starting letter.
>
> Then you could return the result with a template that replaces xxx for
> the full name of the source.
>
> It is all about planning. I think a feature like autocomplete could be
> essential for your application. This would be a good starting point
> even if you plan to add that feature later.
>
> Greetings, Martin
>
> On Mar 2, 1:58 am, Linly <[email protected]> wrote:
>
> > Thanks, Martin.
>
> > It's really a nice idea, but I'm afraid that would far beyond my
> > ability.
>
> > Another consideration is about "relational database". The entries in
> > the database are come from book editors, I should honor that
> > "relation". When an entry is found, there will be an information
> > showing which book is it come from. If I sort the entries
> > alphabetically, I would lost the relation between entry and book.
>
> > Or I have to keep both kinds of files, one are books with entries
> > inside, one are entries alphabetically sorted, and do some kind of sql
> > to connect the relation. That is even more beyond my ability. :
> > ( Anyway, thank for your good idea and all the help long long time
> > since.
>
> > ( The first-app.-talk is just a gossip, please don't take it
> > seriously. :)
>
> > Cheers, linly
>
> > On Mar 2, 2:35 am, Martin <[email protected]> wrote:
>
> > > This looks interesting.
>
> > > Did you think about sorting your entries alphabetically? That means
> > > you have 26 pages, one for each letter of the alphabet.
>
> > > Then you could offer an autocomplete function.
> > > You could start a search or info report after two or three letters are
> > > typed and pull the results with an ajax call into a div or iframe
> > > beneath the input field.
> > > The first letter indicates the page, the next two show some first
> > > results.
>
> > > There are some ready made scripts from scriptaculo.us or jquery.com
> > > which you can adapt for Boltwire.
>
> > > Good luck!
> > > Greetings, Martin
>
> > > P.S. I have a simple homepage using boltwire as CMS in public and a
> > > timetracking application which is only used internally. Both will not
> > > count for the first public boltwire app :)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to