On 10-Dec-08, at 10:02 AM, Francesco Romano wrote:
Changing from WOBatchNavigationBar to ERXbatchNavigationBar, now
the bar is visible also if I don't have more than one pages (and
that is good), but... there is no pluralName... sigh...
Plural name is not a binding because it is generated
On 10/dic/08, at 18:50, David Holt wrote:
Hi Francesco,
On 9-Dec-08, at 11:56 PM, Francesco Romano wrote:
I've some problems with the Insert() method of WODisplayGroup.
It adds another row, but if I edit that row and I don't commit the
EditingContext, if I insert another row the previous
Hi Francesco,
On 9-Dec-08, at 11:56 PM, Francesco Romano wrote:
I've some problems with the Insert() method of WODisplayGroup.
It adds another row, but if I edit that row and I don't commit the
EditingContext, if I insert another row the previous is been cleared.
Another thing...
I inserte
I've some problems with the Insert() method of WODisplayGroup.
It adds another row, but if I edit that row and I don't commit the
EditingContext, if I insert another row the previous is been cleared.
Another thing...
I inserted a WOBatchNavigationBar.
I use it in this way:
On 7-Dec-08, at 10:33 AM, Francesco Romano wrote:
On 07/dic/08, at 16:05, Johann Werner wrote:
If I got your idea right you should look at WOSwitchComponent. The
problem I mentioned in the last e-mail is if your condition
evaluates to true (showing your rows) and then you are submitting
On 07/dic/08, at 16:05, Johann Werner wrote:
If I got your idea right you should look at WOSwitchComponent. The
problem I mentioned in the last e-mail is if your condition
evaluates to true (showing your rows) and then you are submitting
changes where during the takeValues phase the condit
I'm very stupid :(
I solved the "in-place modification"... I put a wo:link instead of the
wo:submit...
A part from that I'll wait for your hints...
Francesco
On 07/dic/08, at 15:24, Johann Werner wrote:
Hi Francesco,
Am 07.12.2008 um 14:54 schrieb Francesco Romano:
I can't modify it.
Am 07.12.2008 um 15:44 schrieb Francesco Romano:
On 07/dic/08, at 15:24, Johann Werner wrote:
Hi Francesco,
Am 07.12.2008 um 14:54 schrieb Francesco Romano:
I can't modify it..
This is the code: (inside a form)
"$aLuogo">
On 07/dic/08, at 15:24, Johann Werner wrote:
Hi Francesco,
Am 07.12.2008 um 14:54 schrieb Francesco Romano:
I can't modify it..
This is the code: (inside a form)
"$aLuogo">
aggiungiElemento
Hi Francesco,
Am 07.12.2008 um 14:54 schrieb Francesco Romano:
I can't modify it..
This is the code: (inside a form)
"$aLuogo">
aggiungiElemento
Applica
Annulla
Salva
On 06/dic/08, at 20:30, Ramsey Lee Gurley wrote:
On Dec 6, 2008, at 9:11 AM, Francesco Romano wrote:
That could be an idea...
But... in this way a displayGroup is very similar to a simple
array.. What are the advantages?
Display groups have batching, qualifiers, auxiliary qualifiers, sor
That could be an idea...
But... in this way a displayGroup is very similar to a simple array..
What are the advantages?
By the way... a very simple request...
I want to bind a record attribute with a textfield.
I can do for a "read-only" page.
But is there a way to have a bidirectional bound?
Am 06.12.2008 um 11:56 schrieb Francesco Romano:
Hi...
Looking in the API and in various sites I understand that
WODisplayGroup could be a very useful object for managing a table..
I understand how to create it using WOLips or programmatically (I
think the following rows are right..)
E
Hi...
Looking in the API and in various sites I understand that
WODisplayGroup could be a very useful object for managing a table..
I understand how to create it using WOLips or programmatically (I
think the following rows are right..)
EODatabaseDataSource ds = new
EODatabaseDataSource(
14 matches
Mail list logo