Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 30586 invoked by uid 500); 24 Apr 2003 09:42:29 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 30509 invoked from network); 24 Apr 2003 09:42:28 -0000 Received: from outmail5.swisscom.com (HELO sbe3777.swissptt.ch) (138.190.3.48) by daedalus.apache.org with SMTP; 24 Apr 2003 09:42:28 -0000 Received: from sbe2173.corproot.net (138.190.70.55) by sbe3777.swissptt.ch (MX V5.3 AnHp) with SMTP for ; Thu, 24 Apr 2003 11:42:39 +0200 Received: from sxmbx03.corproot.net ([138.190.70.162]) by sxmbx01.corproot.net with Microsoft SMTPSVC(5.0.2195.5329); Thu, 24 Apr 2003 11:42:39 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: XMLForm: view/edit functions Date: Thu, 24 Apr 2003 11:42:39 +0200 Message-ID: <5B093C49F2649B459246944825A267AB0162C98A@sxmbx03.corproot.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XMLForm: view/edit functions Thread-Index: AcMJRJoemC5sqrt3QcKe8rZmLwyYXwAGg5fQADlEY0AAAF/LEA== From: To: X-OriginalArrivalTime: 24 Apr 2003 09:42:39.0802 (UTC) FILETIME=[D88371A0:01C30A45] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Johan, Your Use case B is exactly what I would like to do. Before the change of XMLForm framework to conform better to the W3c = spec., how have you resolved this Use case? Thanks Regards Sylvain (T) -----Message d'origine----- De: Johan Stuyts [mailto:johan@hippo.nl] Date: jeudi, 24. avril 2003 11:28 =C0: cocoon-dev@xml.apache.org Objet: RE: XMLForm: view/edit functions Hi, I have posted a similar use case to this list. Currently it is not likely that this will be addressed, because the XMLForm framework needs to be changed to conform better to the W3C XForm specification. Read about it here: http://marc.theaimsgroup.com/?l=3Dxml-cocoon-dev&m=3D105094230804533&w=3D= 2 Johan Stuyts johan(at)hippo(dot)nl / www.hippo.nl=20 > -----Original Message----- > From: Sylvain.Thevoz@swisscom.com [mailto:Sylvain.Thevoz@swisscom.com] > Posted At: Wednesday, April 23, 2003 8:10 AM > Posted To: Cocoon Dev List > Conversation: XMLForm & JavaScript incompatibility > Subject: XMLForm: view/edit functions >=20 > Hello, >=20 > I'm using XMLForm to implement a web application where data are stored in > a database. > Main "functions" for an application that manage data are: add - delete - > search - view/edit. > The "functions" add, delete and search are (relatively) easy to implement > with XMLForm. >=20 > My problem is how to implement the view/edit functions (from a search > result). >=20 > My goal: >=20 > When I search data the result looks like: >=20 > Id name type > -- ---- ---- > 1 test1 type1 > 3 test5 type3 > 8 test45 type1 >=20 > The idea is to add a link or a button to the result like: >=20 > Id name type > -- ---- ---- > 1 test1 type1 view edit > 3 test5 type3 view edit > 8 test45 type1 view edit >=20 > The view and edit button/link should contain information about the item > (the Id) and allow to view/edit the item (in another view or another > XMLForm application). >=20 > Is anyone has an experience about this? >=20 > Thanks > Sylvain