Design User interface (XML-XSL)

Hi there,
I am in the process of analyzing the Oracle and XML capabilities.It looks like XSQL page is the great concept.
I have learned alot from the examples especially with Flight-Finder.
I got stuck when i starting developing the style sheets because code to paint a field and other formatting is quite complicated without any tool.
I have to design the style sheet for the Internet Explorer as well as WAP browser and i don't know what is the easiest way to design that ?
If anybody knows any tool which can solve my problem. i will really appreciate that..
Thanx in advance for any pointer, -Vivek

The Member Feedback forum is for suggestions and feedback for OTN Developer Services. This forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions will not be answered. We recommend that you post this thread to the XML forum.
The URL is:
General XML

Similar Messages

Problem in designing user interface

Hi
I am new to weblogic workshop.Please guide me regarding designing user interface.I had tried form weblogic help but i wasn't able to do it .I am giving the whole form below .i need to finish it asap,please reply
" REQUESTOR INFORMATION(with black background)
Date Phone no
Requestor Name Phone NO
Alternate contact name
{all text boxes}
WEB APPLICATION INFORMATION(with black background)
Applicatiion name
Description
{text boxes}
environment A() b()
{check boxes}
INFORMATION OWNERS(with black background)
NAME TITLE
1
2
SSO GROUPS(black backgound)
some more fields)
SUBMIT BUTTON
{SHOW BUTTON}
the following fields are hidden ,they get showed only after i press SHOW BUTTON
RECEIVED BY
TICKET NUMBER(any random number generated)
COMPLETED BY
{all text boxes}
Looking forward for a favorable reponse from your side

Maverick
It is not possible to post the codes for your requirement.Also you have not mentioned whether you want to use this web app for portal application or simple web application which will be running on weblogic server.
If you are using portal application
the JSPs will be the part of JPF(Java Page Flow)
If you are using web application
You have to create jsp in weblogic workshop.
You can use weblogic workshop help to do that
Also you can find help on www.edocs.bea.com
Regards
Bishnu

Graphic Designer / User-Interface Engineer Job Opening

Title:
Graphic Designer/User-Interface Engineer
Job Qualifications:
- Must be an innovative Graphic Designer/User-Interface
Engineer
- Minimum 4 years experience developing web-based user
interfaces
- Expert knowledge of Adobe graphic design applications such
as Flash, Photoshop, and Illustrator or alike products
- Experience with Adobe Flex and ActionScript3
- Has a proven track record designing and documenting
high-quality user interface designs for web-based applications
- Possesses a strong visual design sense and general design
principles
- Has some background in object-oriented design and
programming
- Able to work effectively from a remote home office
- Has excellent interpersonal and communication skills and
collaborates well in person, online, or on the phone
Job Description:
This position offers an opportunity to work on high-end
graphical design projects building rich Internet applications for
Fortune 500 client companies in industries like financial services,
software and consumer products. As a User-Interface Engineer, you
will be expected to:
• contribute strong leadership through all phases of
development including functional requirements development, UI
design and documentation
• analyze and establish functional requirements and
specifications using feedback from clients and other developers
• apply your visual creativity and functional
experience to design elegant and responsive web user interfaces
with Adobe Flash (Flex expertise desired)
• support other developers to ensure successful
implementation of the designs
• create appropriate documentation during development
Candidates will be expected to provide a portfolio of their
graphical design work in zip files or URL links for review.
- Can be based anywhere in the U.S.
- Up to 25 percent travel time required
- Work on-site and from home
- 3 to 6 month engagement with potential for perm placement
If you are looking for a new exciting opportunity, please
reply with your resume attached to [email protected]. Thank
you for your interest and I look forward to hearing from you soon.
Regards,
Kevin Bakhmutsky

Kevin,
Are you only looking for a Graphic Designer or do you have
other openings that could be filled by a Flex person with a J2EE
background?

How to design the user interface for Indesign cs6 plugin ?

Designing user interface using custom c++ library(SDK) for pluging is very tedious work .so when I search the net than i found that we can do it using Adobe Creative Suite Extension Builder but i dont know how to use it to develop user interface for plugin and to how to enable event handling in this UI .I read lots of document regarding this on net but they all created lots of confusion in my mind so can anyone help me to know steps which i must follow to develop plugin using this or whatever technology (action script,java script etc)

If you want to develop Extensions using Creative Suite Extension builder then i think this is not the right forum for you. Please post your specific queries regarding this at the below mentioned link
http://forums.adobe.com/community/creativesuites/cs_sdk
To give a brief of how to develop UI using JS you can use ScriptUI to develop your UI, it is a fast and OS independent approach to UI development. The UI created using JS is native in look. You can refer the following link for some help on ScriptUI
http://www.kahrel.plus.com/indesign/scriptui.html
I don't have much info regarding development in CS SDK, but i can point you to one more direction of dev called as hybrid plugins wherein the UI is created in CS SDK, and appropriate methods are exposed from the C++ plugin(enhancing the script object model) to be called up by the CS code for too and fro communication between these two modules of code.
Hope these pointer help you in getting started.
Thanks,
-Manan

CS5/CS4 GUI User Interface Design

I have always been very unimpressed with the user interface design on Adobe CS4. It's riddled with problems and changes that make no sense and offer no advantages.
For example, there is no longer a normal Windows title bar in many of the CS4 apps. This makes it much more difficult to maximize/restore applications since normally a Windows user could simply throw the mouse to the top edge of the screen and double click the title bar. In fact, doing this with CS4 apps has ZERO function (it doesn't do anything). One would think that by moving the menu commands to the top bar of the window chrome, Adobe would make these menus accessible from the top-most edge of the screen in order to increase usability. Unfortunately this is not so and clicking the top most edge of a maximized window does nothing.
Two other very important parts of an application user interface are the upper left and upper right corners. Normally when a Windows application is maximized, throwing your pointer to the upper right corner and clicking will close the application. Throwing the pointer to the upper left corner and clicking will reveal the application window menu. This happens in ALL applications... EXCEPT for Adobe CS4 programs. These two extremely important application window command locations have been completely disabled in Adobe CS4 apps. Clicking the upper most corner pixels in a maximized Adobe CS4 app does nothing.
Then there's the tabbed document window interface. If you float a document window and maximize that, normally you would expect it to become maximized within the application window as it should. Au contraire, in Adobe CS4, the document window maximizes itself ON TOP OF the application window, thus obscuring and disabling any access to the application window's tools/commands. I did report that as a bug during beta, but obviously it was ignored. Seems kind of obvious to me that the fact that a user could accidentally make the entire application completely unusable by maximizing a document window might be a problem.
It still alludes me as to why Adobe changed the CS4 user interface to something that breaks so many Windows UI conventions. Adobe CS3 was a practically perfect user interface design on Windows. It was very customizable, all of the normal Windows functions were properly in place.
What's the deal with the change?
I thought maybe the file menu was moved in place of the title bar in order to make more room for other UI elements, but it's actually pretty much the same size as the old file menu title bar combination in CS3.
With all these changes and with all the functionality losses, what exactly have we gained in the CS4 GUI? Seriously, I'm asking.
Anyway, I hope Adobe starts reading the Windows User Experience Guidelines (http://msdn.microsoft.com/en-us/library/aa511331.aspx) and brings CS5 back to the way a Windows application should behave. Proper theme adherence would be nice too.
Which brings me to Windows 7. I love love love the way Windows 7 groups application document previews in one taskbar icon and allows aero-peek for open windows. Adobe CS 4 obviously does not support this since it does not have normal document windows. I hope CS5 does because it is a great feature. I also hope Adobe CS5 implements the Windows 7 jumplists and maybe even a more touch/multi-touch friendly interface. I've become pretty good at processing photos in Bridge using the touchscreen, and it's very cool, but it could use some improvements.
For an example of great user interface design, has anyone tried Office 2010 on Windows 7 yet? http://www.istartedsomething.com/20090512/screencaps-office-2010-technical-preview-teched- 2009-keynote/
The faded transparent title bar and tabbed ribbon interface is absolutely gorgeous.

@Adam:
I agree with your comments! So well said!
And there are other issues, too -- by the color of the app window, you don't know if the window is active or inactive (focus or not in focus). Titles of panels which are inactive, are dark text over dark background -- hardly readable at all... And many more.
I really hope Adobe are listening...

Forms 10g Design Rich User Interface

Dear All,
i would link to design rich user interface in forms 10g.
for example : the button shape is circle , not only
rectangle.
Is it possible to do that in forms 10g or import some java object from third party tools.
best regards
borisys

Borisys,
the concept of Pluggable Java Comnponents (PJC) allows you that. PJC only change the UI of a component without affecting its functionality.
The Forms demos that are available on otn.oracle.com/products/forms contain enhanced buttons in teh form of mouse over effects.
Frank

Why hasn't Adobe navigation and user interface design improved as much as it could have over time?

I haven't tried CS6. I'm sure it's great based on what i've seen alone. But as a user of adobe products for a number of years, i have to noticed there are still a lot of stagnant,awkward, stiff, irriating, slowing down elements found in the navigation and user interface on cs3-cs5, that i'm sure could have been eliminated or improved on at least from 2005 or 2007 onwards. I find some of these things inexcusable and unprogressive from bad traits that defined 1980's and 1990's general computer navigation and so on.
CS5.5 has lessned this a bid bit and is more fluid in bits and pieces but for those using cs3-cs5 and in general, i find some things just horrid. As a graphic designer no one is supposed to admit the flaws or irrations of these programs. We must hail them as god, never critisize, and always adjust to new things which i think is a bit fascististic and silly
The way the tools, options are laid out can be improved to be quicker, and easier to find and use. Using your voice as a commanding system would be helpful as well.
A lot of cmds are too complex to remember, they can be simplier or resemble the name of the tool or option. Its makes a chore to follow this system and competition for the smart *** who memormized all the cmds.
The way in which you loose floating side boxes, and the amount of tools or names hidden in the bars sometimes seem random and its always a constant search to find them incase you forget where they are.
The inability to open cs4 or 5 files in cs3 is just beyond extremly annoying. Whey shouldn't you be able to open cs1 or 2 files or photoshop 9 files as well? Every five years work expires as well?
The layering system gets tricky and seems that a lot of things don't work when you normally move things. Its about going back, remembering and clicking on this or that, looking it up to make everything work. Sometimes which leaves you in a rut and wastes a good amount of time. You will always find this even after you've been using it for years.
The use of the fill paint/airbrushing, clone tool, lasso tool, pen tool, history being two steps back can be vastly improved to be much better to use
Masking and tools that have more complex features should find a way be automatically done or sampled. They can also have less complex steps and tha ability to be previewed, automatic or simpler ( in case you can't remember how to do something or aren't getting it)
A lot of the special effects, and blending modes are useless, outdated, super-ugly and don't resemble true darkroom effects ( such as polarization, and bas-relief for example) which they could much more vividly done. There also could be more options that are closer to repro cameras/CTP software for halftoning and more complex digital effects.
Having to press or get used to pressing muliple keys or clicks for the most basic things simultaneously can be reduced to be easier
Adjusting text, new documents, photos should have a smoother, quicker navigational experince where things a lot of room to be , clicked back, re-done, saved in the wrong place etc..
Indesign could use more shapes, include more features that illustrator has, and possibly even photoshop to save time.
There should be a way to remind you of features, complex things you've forgotten, other than history and daily usage/practice of the programs
The help should resemble more of "visual -learners" guide books with voice features.
There are a lot more
Regarding other things:
I think the price encorages more piracy and allows people to not have a concept of what is means to owning software.
The loss of a manual or lessening of them for certain programs is a loss because it's always useful to physical info you can flip through while looking at your program.
I think adobe should make entirely better products for professionals or people in the industry rather than spoonfeeding the same software to all.
They should also make less expensive add-ons like before for graphic software.
What do you adobe could have improved over time and if so what do you think they could have improved on?

You have this wishform to suggest improvements to Adobe products:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
and the Creative Suites forums are here:
http://forums.adobe.com/community/creativesuites
This specific forum is only for discussions on the forums themselves, so you are not very likely to get any change by posting your comments here.

How much do you get paid annually for this job User Interface Designer?

how much do you get paid annually for this job User Interface Designer?

Apple probably will not discuss salaries even for specific jobs other than with applicants. If you wish to discuss salaries, you'll most likely have to apply for a specific position and then get beyond the initial screening.
This issue has nothing to do with Apple Remote Desktop, the topic of this forum, by the way.
Regards.

Designing web user interface

Hi experts,
can anybody tell me something about designing web user interface, like some of the key considerations? I did not successfully find it on our forum.
Thanks.

hi Joey,
do you mean web template ?
check
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/749a4622-0a01-0010-36bf-b6b30a2a3a22
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/a8cd1f71-0a01-0010-4783-f119b6132d25 [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/1a/456a3badc1b315e10000000a114084/frameset.htm
hope this helps.

Extension user interface design

Hi all,
I'm looking into how Adobe can help developers make their extensions look better integrated with the Creative Suite.
Probably the most common request we've heard in the past is for an improved Creative Suite Flex theme SWC.
Do you have any further thoughts/feature requests in this area?
I would be particularly interested to know whether you use CSXSLibrary to get the host application's skin information. If you do, does the API provide sufficient information to customise your extension's appearance effectively? If not, is there anything you'd like to see changed in the API for it to be useful to you? Here are the classes currently available:
AppSkinInfo - accessible through CSXSInterface.getHostEnvironment()
AppReskinEvent - dispatched when a CS app changes its appearance.
All feedback much appreciated.
Thanks
David.

The intention is to make the preloader (that's the generic loading bar that displays for a few seconds when the panel first opens) for your extension to be completely invisible.
That will make it take the colour of the content behind it, which is the default panel colour for the application. You could also change the colour of the preloader, to match the eventual one of the panel, or you could create your own preloader SWF.
You can find more information on preloaders for Flex 3 at http://livedocs.adobe.com/flex/3/html/help.html?content=app_container_4.html and a tutorial on creating your own at http://www.leebrimelow.com/?p=916
Best,
James
From: Adobe Forums <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Date: Mon, 2 Jan 2012 20:25:59 +0000
To: James Boag <[email protected]<mailto:[email protected]>>
Subject: Extension user interface design
Re: Extension user interface design
created by softsign<http://forums.adobe.com/people/softsign> in Creative Suite SDK - View the full discussion<http://forums.adobe.com/message/4114198#4114198

Controlling user interface settings on LiveCycle Designer ES4

How can you control the user interface settings on LiveCycle Designer ES4?

The problem you descibe has nothing to do with the PDF security settings.
If you have added scripts in the fields calculate event or set their access property to readOnly or protected you won't be able to change a fields value.
Ypu can check the current access setting in the Object palette under the Value tab.

'Design Patterns' for Application User Interfaces

I'm currently trying to unstick an architectural mess centred around a relatively simple user interface. The problem is thus:
The application has a number of toolbar buttons and menus, some of which require a specific frame or class of frame to be enabled. Some conditions are quite simple, others more complicated.
(Without going into any more detail, it should be possible to appreciate that this is a fairly common problem.)
For this application, I've created a large listener that accepts events from all over the program, converting them into state changes for UI controls. It feels messy, and (although it isn't finished) I suspect it'll be rather fragile.
JBuilder 4 does it by constant querying of application state - but this results in excessive CPU usage and apparant lag.
TogetherJ does it for menus by checking state immediately before showing the menu. This seemed like a good plan, but it's unsuitable for the Action/Button/MenuItem lashup I like to use.
My question is this:
In your opinion, how should an application be structured to reliably maintain the correct UI state at all times?

Check out the mediator pattern. It is pretty close to what you are describing, maybe the details you dig up on it will give you some new ideas?

FlexCube user interface

Our Client ( Bank ) wanted to implement Oracle FlexCube Direct Banking Solution. We are goint to branding their Screens.
We asked to follow Oracle FlexCube Direct Bannking User Interface Manual to create the screens ( Login page, Transaction page, DashBoard, etc).
The document describes the css used in the design pages.
Initially they (Oracle ) has sent us CSS files, JS Files used in Screens (CSS, JS, amd jsDIR ) explained in the manual.
Later they sent us only XSL files for designing the login page and dashboard ( login.xsl and dashboard.xsl).
We assume that Oracle also should give us the .XML template files for each relevant .XSL files to transorm the XSL into HTML.
But they did not give us such files.
Also we found there is a tool from Oracle called "Oracle Direct Banking WorkBench" to design these pages.
Please adives us
1. Do we need to get XML files from ORacl to do the work
2. Do we need to buy WorkBench Tool
3. Do we need to buy any other tools to design the pages.
Please help us

Hi!
I haven't noticed much - only one strange thing: When pressing the Attachement-button in Mail, nothing happens. I tried it just now, because of your comment, and exactly the same thing happens as in Aperture.
Thank you for showing me that!
But now: How can I fix this?
Best regards

Error while creating a callable object - User Interface

Hello,
When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
Is there any body who allready had somthing like this.
Greetings
Kurt

Hi Raja Akella,
I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
In the visual administrator i get the following errors.
Error 1
Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 2
Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 3
Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
thanks in advance
Kurt

A more successful experiment in creating compositable user interfaces for Config Dialogs

A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
it handles the TAB problem without flickering, something I haven't seen in other attemps
This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
[UPDATE 5/17/2012 - There is an improved version.]
Solved!
Go to Solution.
Attachments:
ConfighThroughCtrlCreation.zip ‏558 KB

Elijah K wrote:
Thanks for posting this Aristos. I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to? The act of switching tabs? In all honesty, I've never noticed...
When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
Attachments:
ComposableUI_LV2009.zip ‏391 KB

Design User interface (XML-XSL)

Similar Messages

Maybe you are looking for