All of XViewer was intended to be extendable, but not much has been done with customization dialog. If there is something that needs to be done to make this possible, it can be.
Wouldn't mind a re-design of the dialog if someone wants to take it on. Just need to keep all the functionality 1) View existing customizations 2) Create new customizations 3) Set customization as default 4) Delete customizations 5) Alter existing customizations 6) Save as local or global The sorting and filtering XML boxes was just a hack way of showing the values, but is not user friendly at all. Should be done through column selections and not just text boxes with xml. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stapleton, Mike Sent: Tuesday, November 23, 2010 1:33 PM To: Nebula Dev Subject: Re: [nebula-dev] XViewer- how to enable save of customizations? Good questions Chris. I also will need to add other options. I haven't looked at it closely yet but you may be able to override some of the parent functions to meet your needs. However, that probably wouldn't hold true for new options? Not sure about the intent of the XML entries other than it appears to be inconsistent? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chris Merrill Sent: Tuesday, November 23, 2010 1:12 PM To: Nebula Dev Subject: Re: [nebula-dev] XViewer- how to enable save of customizations? On 11/23/2010 12:31 PM, Stapleton, Mike wrote: > The code that implements the save operation is in the > MyXViewerCustomizations.java class of the example. When I downloaded > the example it saved to the C drive. This of course throws an > exception in your working on a Linux system so maybe that's why it was > disabled? IF your talking about the button itself being disabled then I'm not > sure since I haven't implemented that part yet. However > MyXViewerCustomizations is a good place to start. Thanks, Mike. I've got it working - saving and loading customizations to/from our preferences folder. Next question - the UI shows the entire XML tag in the value of the sort field, e.g.: <xSorter><id>Name</id></xSorter> while the filter field does not show any XML, e.g. it shows: "3" instead of "<xFilter>3</xFilter>" Is this a bug or a feature? Showing XML doesn't seem like something intended for the end-user to see (and change)...so maybe a bug? Finally, we need to add more things into the customization dialog - additional filters (non text-based) and some other options. Do you know if anyone has gone down this road? Had you envisioned any way to make the customizations dialog extensible? TIA! Chris -- ------------------------------------------------------------------------ - Chris Merrill | Web Performance, Inc. [email protected] | http://webperformance.com 919-433-1762 | 919-845-7601 Web Performance: Website Load Testing Software & Services ------------------------------------------------------------------------ - _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
