search

instedd / mbuilder

Scalable SMS application builder
http://mbuilder.instedd.org/
6 stars 1 forks source link

Literal entries in tables #27

Closed waj closed 9 years ago

waj commented 9 years ago

If the user clicks on a "new value" placeholder under a table's column, he should be able to type a value.

That typing should immediately create a new step in the list reading: "Create new [table name] with [Literal] as [ColumnName]"

If the table has a selected context, the user should be able to edit the field that contains the "[table name] [column name]" token and replace it with a literal. The step created should read: "Store [literal] as [column name] of [table name]"

When executed, the step should set that field to the literal specified. This should also be reflected on the 'test data realm' and be consistent in the rest of the triggers.

waj commented 9 years ago

When you drop a pill on "new value" it creates a new row.

When you click on "new value" and write something, you are proposing to update the whole table. Shouldn't it just create a new row with that value?

If you filter the table and click on an existing value (the light gray boxes), then you would update those values to the specified literal.

What are you trying to achieve?

(another question: why do we have to speak in English right now if there's nobody else reading this?)

waj commented 9 years ago

This also conflicts with: https://bitbucket.org/instedd/mbuilder/issue/25/allow-user-to-enter-data-manually-in

We need to define a way to create new rows in response to the current trigger, or as fixed values...

waj commented 9 years ago

(we are writing in english for archaeological purposes ;-)

You are very right. Let's assume that as a principle, in-place editing should behave as if that literal was dropped from elsewhere.

I'm editing the description to reflect the change.