On Thursday, 15 November 2018 10:25:17 GMT Ralph Corderoy wrote:
> > When you talk about rows, do you mean rows in the spreadsheet
>
> You can assume that, and the question still stands. :-)
I hadn't envisage multiple rows in the spreadsheet since we are currently
simply typing in the value fre
Hi Terry,
> > So if you've five widgets, two of them Condition=rusty, is that two
> > rows? What columns come together to make a unique row rather than
> > one that should be merged into another? I'd group those together
> > rather than slot Quantity in between, say.
>
> I had to think about thi
On 14/11/2018 13:25, Terry Coles wrote:
On Wednesday, 14 November 2018 12:40:46 GMT Ralph Corderoy wrote:
So if you've five widgets, two of them Condition=rusty, is that two
rows? What columns come together to make a unique row rather than one
that should be merged into another? I'd group thos
On Wednesday, 14 November 2018 12:40:46 GMT Ralph Corderoy wrote:
> So if you've five widgets, two of them Condition=rusty, is that two
> rows? What columns come together to make a unique row rather than one
> that should be merged into another? I'd group those together rather
> than slot Quantit
Hi Terry,
> The current spreadsheet has a total of five columns; Item, Condition,
> Quantity, Location and Comment. We would probably want to add a
> Supplier record and maybe two or three others too.
So if you've five widgets, two of them Condition=rusty, is that two
rows? What columns come to
On 13/11/2018 09:27, Stephen Wolff wrote:
Hi,
Once you've written the requirements, you can look at how you could
implement them. From what you've said so far, I'd be looking at a Flask
app (or, if you'd prefer to spend nine months learning the platform,
Django).
Shouldn’t take 9 months with
On Tuesday, 13 November 2018 09:27:57 GMT Stephen Wolff wrote:
> > As mentioned earlier, my hosting provider includes MySQL as part of my
> > package, and Stephen Wolff has suggested off list that the hosting
> > provider
> > might also provide access to PHPMyAdmin. It does; so I am looking
> > in
Hi,
Once you've written the requirements, you can look at how you could
implement them. From what you've said so far, I'd be looking at a
Flask
app (or, if you'd prefer to spend nine months learning the platform,
Django).
Shouldn’t take 9 months with Django unless you had absolutely no
know
On Monday, 12 November 2018 19:37:17 GMT Keith Edmunds wrote:
> Start by writing your requirements. The hard part: do NOT include any
> implementation details in the requirements. Focus on what, not how.
Before I say anything else, I feel that I should point out that before I
retired, a large par
Start by writing your requirements. The hard part: do NOT include any
implementation details in the requirements. Focus on what, not how.
For example, "The database should be hosted on a website somewhere" is not
a requirement. It is a way of achieving an unstated requirement; there may
be other,
On Monday, 12 November 2018 14:24:05 GMT Patrick Wigmore wrote:
> Last year, I used [Kexi](http://kexi-project.org/) to record an
> inventory of my personal hoard of electronic components.
So far so good.
> But Kexi does not fulfil your requirements, in that the database would
> not be hosted on
Hi Terry,
Last year, I used [Kexi](http://kexi-project.org/) to record an
inventory of my personal hoard of electronic components.
But Kexi does not fulfil your requirements, in that the database would
not be hosted on a website somewhere, and that it would not run on Mac
or Windows (support f
12 matches
Mail list logo
