65,211
社区成员
发帖
与我相关
我的任务
分享跪求C++高手写一份Qt toolkit相关程序
RT
因为时间异常紧迫，急需一份Qt相关的作业
请联系：QQ：910985423，MSN：wearwolf001@hotmail.com（MSN隐身，但在线）
相关：
Overview
The “Document Management System” is intended for use by individual librarians,
students, or researchers who wish to build a collection of documents of interest and
subsequently perform key word based searches for documents on specific topics.
The system will permit a user to build up a collection of documents (as plain text
files), with an associated “key word index” structure that maps key words to
documents, and a search system that provides a ranked list of documents that contain
chosen key words (the ranking being based on the frequency with which chosen
keywords appear in the matched documents).
A fully implemented system will accept as input documents taken either from a local
filestore or directly downloaded from the Internet. The system will handle plain text
(.txt), HTML text (.htm/.html), Microsoft Word documents (.doc), and PDF
documents (.pdf). All input documents will be reduced to plain text form in the first
stage of processing.
Documents will be stored, as individual text files, in a directory associated with the
system (the directory will be identified by configuration parameters). The system
allocates its own unique document identifiers; these are used as the basis of the file
names for text storage, and as identifier keys to link all the other data that are to be
held for a document. When a document is added to the document store, the system
will generate two additional records. One record will contain “bibliographic details”
identifying the original source, title, authorship, and other properties of the document
(most of the fields in these records will be optional). The data for the bibliographic
data are to be entered by the user who is registering a document. The second
associated record will contain a key word list with words chosen, semi-automatically,
to characterize the content of the stored document. Bibliographic and key word
record files will be stored in directories associated with the main document files
directory.
The system will be capable of creating a “key word to document” index structure. For
each key word, this index structure will maintain a list of document identifiers and
associated key word frequency. The structure will be held in persistent storage and
loaded, in whole or part, into the program that performs key word searches. The
persistent form of this index will be updated as documents are added to the collection.
This update process may be implemented as an incremental operation, or as a “batch”
operation that is performed after a number of documents have been added to the
collection. A “batch” operation would replace an existing index with a new version
created from all available key word files.
The system will allow a user to enter a set of key words that characterize documents
that are to be retrieved. The “key word to document” index will be used to identify
possible matching documents. These will be ranked according to the cumulative
counts of frequencies of the chosen search key words. The results of a search will be
presented in terms of document identifiers, titles (from the bibliographic records) and
scores. A fully implemented system will enable a user to select any of the identified
matching documents and have the content displayed in a newly opened window.
The system is intended for private use. It makes no provision for “login”, access
permissions etc.
Note: the “Lucene” project at Apache provides a much more sophisticated implementation of many of
the features of the suggested Document Management System. Lucene was originally developed in
Java, but there are now implementations in several languages including C++. If you were really
developing a document system, you would probably exploit the Lucene code base. Lucene isn’t
appropriate for this little exercise – quite apart from the fact that it does have a certain “learning
curve” (like a 300 page book). Don’t use Lucene. This is an exercise, and part of the exercise
involves the design and creation of little classes that have a subset of the features available via
Lucene.
Requirements
Functional requirements
1. The primary requirement is that the system be capable of identifying those
documents in a defined document collection which contain specified key
words. The system will present to the user details of each matching document;
these details will include an allocated document identifier and selected
bibliographic data such as source, title, date of accession etc.
2. The system should rank documents that contain key words; the ranking should
be based on the cumulative frequency of the key words within each document.
3. The system will allow a user to “open” and view a matched document. If the
document was originally sourced from some Internet site, it will be displayed
in a standard browser launched as a sub-process; if the document is only
available in plain text from, a text editor program will be used to display its
contents.
4. The system will maintain text only copies of all documents that have been
registered into its collection.
5. The system will handle documents in a variety of formats including plain text,
HTML text, PDF format, and Word document format.
6. The system will allow documents to be loaded either from local file store or by
being fetched across the Internet from a web site with specified URL.
7. The system will require that the user enter details for a bibliographic record
that is created for each document registered. Bibliographic data are made
available to the user of the system component that identifies documents with
given keywords.
8. The selection of key words used to characterize a document is semi-automatic.
The system will create an initial set of plausible key words (which will
automatically exclude all high frequency content free words). The user will
have the opportunity to amend this list before its use to characterize that
document.
Non-functional requirements
1. The system will be implemented in C++ .
2. The system will run on an Ubuntu Linux OS and will use standard Linux
components (like editors, the wget utility program, browsers) and open-source /
freeware code (such as a “Word document to text converter”, or a “dbm” data
management system such as gdbm).
3. The user interface will be implemented using standard Linux facilities possibly
supplemented by open-source / freeware code (such as the Qt toolkit).
因为时间异常紧迫，急需一份Qt相关的作业
请联系：QQ：910985423，MSN：wearwolf001@hotmail.com（MSN隐身，但在线）
相关：
Overview
The “Document Management System” is intended for use by individual librarians,
students, or researchers who wish to build a collection of documents of interest and
subsequently perform key word based searches for documents on specific topics.
The system will permit a user to build up a collection of documents (as plain text
files), with an associated “key word index” structure that maps key words to
documents, and a search system that provides a ranked list of documents that contain
chosen key words (the ranking being based on the frequency with which chosen
keywords appear in the matched documents).
A fully implemented system will accept as input documents taken either from a local
filestore or directly downloaded from the Internet. The system will handle plain text
(.txt), HTML text (.htm/.html), Microsoft Word documents (.doc), and PDF
documents (.pdf). All input documents will be reduced to plain text form in the first
stage of processing.
Documents will be stored, as individual text files, in a directory associated with the
system (the directory will be identified by configuration parameters). The system
allocates its own unique document identifiers; these are used as the basis of the file
names for text storage, and as identifier keys to link all the other data that are to be
held for a document. When a document is added to the document store, the system
will generate two additional records. One record will contain “bibliographic details”
identifying the original source, title, authorship, and other properties of the document
(most of the fields in these records will be optional). The data for the bibliographic
data are to be entered by the user who is registering a document. The second
associated record will contain a key word list with words chosen, semi-automatically,
to characterize the content of the stored document. Bibliographic and key word
record files will be stored in directories associated with the main document files
directory.
The system will be capable of creating a “key word to document” index structure. For
each key word, this index structure will maintain a list of document identifiers and
associated key word frequency. The structure will be held in persistent storage and
loaded, in whole or part, into the program that performs key word searches. The
persistent form of this index will be updated as documents are added to the collection.
This update process may be implemented as an incremental operation, or as a “batch”
operation that is performed after a number of documents have been added to the
collection. A “batch” operation would replace an existing index with a new version
created from all available key word files.
The system will allow a user to enter a set of key words that characterize documents
that are to be retrieved. The “key word to document” index will be used to identify
possible matching documents. These will be ranked according to the cumulative
counts of frequencies of the chosen search key words. The results of a search will be
presented in terms of document identifiers, titles (from the bibliographic records) and
scores. A fully implemented system will enable a user to select any of the identified
matching documents and have the content displayed in a newly opened window.
The system is intended for private use. It makes no provision for “login”, access
permissions etc.
Note: the “Lucene” project at Apache provides a much more sophisticated implementation of many of
the features of the suggested Document Management System. Lucene was originally developed in
Java, but there are now implementations in several languages including C++. If you were really
developing a document system, you would probably exploit the Lucene code base. Lucene isn’t
appropriate for this little exercise – quite apart from the fact that it does have a certain “learning
curve” (like a 300 page book). Don’t use Lucene. This is an exercise, and part of the exercise
involves the design and creation of little classes that have a subset of the features available via
Lucene.
Requirements
Functional requirements
1. The primary requirement is that the system be capable of identifying those
documents in a defined document collection which contain specified key
words. The system will present to the user details of each matching document;
these details will include an allocated document identifier and selected
bibliographic data such as source, title, date of accession etc.
2. The system should rank documents that contain key words; the ranking should
be based on the cumulative frequency of the key words within each document.
3. The system will allow a user to “open” and view a matched document. If the
document was originally sourced from some Internet site, it will be displayed
in a standard browser launched as a sub-process; if the document is only
available in plain text from, a text editor program will be used to display its
contents.
4. The system will maintain text only copies of all documents that have been
registered into its collection.
5. The system will handle documents in a variety of formats including plain text,
HTML text, PDF format, and Word document format.
6. The system will allow documents to be loaded either from local file store or by
being fetched across the Internet from a web site with specified URL.
7. The system will require that the user enter details for a bibliographic record
that is created for each document registered. Bibliographic data are made
available to the user of the system component that identifies documents with
given keywords.
8. The selection of key words used to characterize a document is semi-automatic.
The system will create an initial set of plausible key words (which will
automatically exclude all high frequency content free words). The user will
have the opportunity to amend this list before its use to characterize that
document.
Non-functional requirements
1. The system will be implemented in C++ .
2. The system will run on an Ubuntu Linux OS and will use standard Linux
components (like editors, the wget utility program, browsers) and open-source /
freeware code (such as a “Word document to text converter”, or a “dbm” data
management system such as gdbm).
3. The user interface will be implemented using standard Linux facilities possibly
supplemented by open-source / freeware code (such as the Qt toolkit).
...全文
请发表友善的回复…
发表回复
xiaohu0238 2009-04-27
- 打赏
- 举报
统一楼上的，
shtianhai 2009-04-27
- 打赏
- 举报
呵呵，LZ不了解这里行情啊，论坛之讨论问题，很少有帮做作业的，有不明天的可以提过来大家相互学习讨论；
这样要作业，而且是“0”分，估计是没有人理会的哦~
这样要作业，而且是“0”分，估计是没有人理会的哦~
Qt 环境配置提示警告Qt Cmake configuration has no path to a C++ compiler set, even though the toolkit has a v
