Give him a break! He is working smart, not hard.
"Who cares whether the cat is black or white when you want to catch
mice" - Deng Xiaoping.
m christensen wrote:
I wouldn't be THIS hard on him, BUT...
juan perez wrote:
So in a nutshell you are asking the community to do your homework.
What a shame.
Start by analyzing the sqlite3 command line interface, make a GUI that
replicates that (and more, heck its a GUI), contribute it to the
sqlite project, THEN talk about your dissertation.
jp.
But, I'd presume the intent here is 'Experience' a software development
process.
Design and build in a vacuum and see what the users think after it's
done, as suggested above, is an all too common and WRONG
approach IMHO.
I don't think you are INTENDING to 'ask us to do your homework' but I
don't think you have yet done the work you need to
do before asking opinions. Final project or real-world-work the issues
are the same.
Mr. Newby you appear to have failed to do basic research into your
market or users needs.
First assess the need for your project.
It would appear you are under the assumption there are no GUI tools for
sqlite.
A Google search like "sqlite GUI" shows otherwise.
I DO think your general approach of asking people what they need or want
is a good one and could be
quite enlightening although probably not entirely along the lines you
probably first expected.
Do your research, figure out what YOU think the requirements and options
are.
Ask some direct and possibly leading questions but be open to answers
that may not be what you expect.
General open-ended questions may very well not spur any real discussion.
They often indicate you have not done your homework so-to-speak.
This applies even more in the 'Real World'.
I also see such questions in the real world as in indication of a lack
of commitment to the proposed project.
In short if YOU don't have the commitment to do your part FIRST why
should I spend a lot of time and effort on a response
you may or may not even look at before you flitter off to something else.
Just like in the real world some people may support your pet project,
some may be hostile, some couldn't care less and some
people think you 'shouldn't bother them with the details or questions'.
You will need to learn to deal with this too, it's part of the job.
Let's say you take this advice and look at "SQLite Analyzer"
You then come back to this group with an intelligent question such as...
"I noticed SQLite Analyzer has a drag-and-drop qry builder. Is this a
Feature anybody here would actually use?"
Due to the fact most people here are developers I'd ASSume the answer
would be a resounding
"NO. If you can't write a SQL Qry, you'd probably be better off using
Access or something..."
Then someone may chip in "You know I have no need, but the end users for
my app sure COULD use a nice
PDF-Generating GUI Report Builder with a drag-and-drop Qry Builder..."
I'd sure Hope the intent of your project is NOT 'Write a PROGRAM to do
X' but to truly 'Learn how to develop an application
from inception thru needs analysis to development, debugging, and final
release and to provide a usable tool.'
This may not be an answer to the questions you thought you asked, but
IMHO it does provide
"other information 'I' feel would help YOU on YOUR journey"
Marc
John Stanton wrote:
john.newby wrote:
Hi, I am doing my final year project/dissertation on "Creating a GUI to
SQLite"
I am after help for my analysis phase and would like any
comments/help from
members or if you could put me in the right direction as to where I
could
find out this information.
I would like information regarding SQLite for the following if at all
possible:-
Why users use SQLite instead of other SQL databases?
SQLite has two fine features. Firstly it is simple, lives in one
file and doesn't require a server process. Secondly it implements
all the important elements of SQL.
Would a GUI detract users from using SQLite?
There is a wagon load of GUIs to SQLite already. They neither add
nor detract from the DBMS.
Regarding a GUI to SQLite:-
What features a GUI MUST have?
What features you would LIKE a GUI to have?
What features you would NOT LIKE to have?
This is like asking what features are needed in a coat without
specifying its intended usage.
Any help on these questions or any other information you may feel
would help
me on my journey would be greatfully appreciated.
You can contact me at my University email address on
[EMAIL PROTECTED]
Many thanks for your help.
John.
====
This e-mail is intended solely for the addressee. It may contain
private and
confidential information. If you are not the intended addressee,
please take
no action based on it nor show a copy to anyone. Please reply to
this e-mail
to highlight the error. You should also be aware that all electronic
mail
from, to, or within Northumbria University may be the subject of a
request
under the Freedom of Information Act 2000 and related legislation, and
therefore may be required to be disclosed to third parties.
This e-mail and attachments have been scanned for viruses prior to
leaving
Northumbria University. Northumbria University will not be liable
for any
losses as a result of any viruses being passed on.
