I'm wondering if it is possible to combine several behaviors, which come with their defined fieldsets into one schemata. For example there are Dublin Core fields ICategorization, IPublication, IOwnership and they all come with their own fieldsets, what makes them appear on different tabs in form edit. I would like to have one tab with all of their fields combined. I've tried to overwrite IDublinCore specifying my own fieldset with fields I want, and that gave me everything what I wanted in one tab, however, other tabs were still present.. So I've tried in my own interface to overwrite those as well with:
form.fieldset('ownership', fields=[])
however, Ownership tab was still present.
Related
What would be the best way of creating my own custom view?
I want to have my page do some specific stuff. For example, I am creating a search directory for different names. But, there will be 3 different types of search functions and I would like to toggle between them with 3 different tabs (each tab goes to a different search function). Would this be all in one view with then 3 blocks or multiple views selected by different tabs? What would be the best way of doing this?
One of the search functions will list all of the names alphabetically and there will be an alphabetical directory at the top that will bring the user to the corresponding letter that they select on the page. I believe that this will have to be a custom view that I will need to create, but I have never done anything like this before.
Does anyone have any good advice as to how I would go about doing this? Do I have to create my own module first? Are there any good tutorials out there that would help?
Thanks!
I'd recommend giving https://drupal.org/project/quicktabs a try. I haven't used it myself, but I know of others that have.
The project page sidebar has links to docu and a demo with some screenshots of config.
If you're going to be reusing almost all of the settings between blocks you'd want to create different blocks displays within the same view and override what you need to.
Is there anyway we can define more than one block structure for the pages?
For example... I want to two different block/region setting and that should be page specific...
So I can create literally 2-3 different region settings or page structure
Is there any way I can do that?
P.S: Other than multiblock... I already tried it...
If you are using panels you can create custom panes(like blocks) with specific settings etc and put them everywhere you want and so many times as you want.
Have you looked into Panels?
https://drupal.org/project/panels
Panels allows you to set various page regions and also allows those regions to be enabled/disabled based on sets of matching criteria.
I'm wanting to use Panels to drive a whole bunch of pages for data interaction, but I'm not sure how to get Panels to "interact" with each other. I think the best way to put it is with an example. Say I have one Panel which has a list of nodes (in a view?), and another Panel that I want to display an editor for any node I click. And I have a page that has the first Panel in a block on the left, and the second in a block on the right. So I suppose on click, there'd be some AJAX grab that puts some page in the other Panel. Now, this is a simple example, and I'm going to end up with many different sets of interactions among multiple panels doing all sorts of stuff. But this works as a starting point. The goal is to be able to reuse these Panels in multiple pages that may interact with similar data, but with different operations (maybe there's the above edit page example and also a similarly designed view page also utilizing the left block node selector?).
How much of this can be accomplished with Panels (and maybe supplementary modules?)? Where would I need to code to put it all together? I assume it would need code perhaps in the Panel page that contains things like the data selector panel, data view panel, etc. to "link them together". Are there any good examples floating around on how to do this, since it seems like a fairly bread-and-butter exercise for any sort of web-based data interaction...
The best and probably the simplest way probably would be to do it with some coding but if you prefer using modules there a module families like Context or Rules that should give you some functionality which you are after. I also suggest looking into AJAXification methods and modules.
I am creating a form that needs to have 30 or more fields either disabled or set to be read only. They need to be marked as such if the based on the value of a drop-down box.
This is something that I can do using conditional formating that I know, what I want to know is there a way to either add conditional formatting to multiple controls at once or a rule that I can set that will accomplish the same thing?
One requirement is that I can't use programming code to do this. I realize it would probably be far easier to do that way but that is a requirement given to me by my manager.
EDIT: Forgot to add this there are fields that still need to be edited when the other fields are read only.
One feature in InfoPath 2010 (can't remember if it was in 2007) that reduces the pain of this sort of repetitive work is the ability to copy-and-paste rules. With this you can create your read-only rule once and then just paste it onto each of the 30 controls that need it.
You could put it all in a section but your only option for sections is hide/show (not disable or read only). Otherwise you have to setup all the fields against that one dropdown. Huge pain but at least you only have to do it once.
An alternative, which is just about as much work, is to setup two views. One that is readonly and one that is normal. When the user changes the dropdown just flip the view. This method has a bunch of display nuances but does work.
I am having difficulty navigating to different MXML pages in my Flex application. I checked some other questions on SO about it but they seemed to be to do with tab navigation.
I am trying to navigate from one MXML page to another via Actionscript code. How is this possible?
Cheers
Edit:
I am a real beginner in Flex and I worked out that I actually needed to use States, and have now discovered how to use them. Thanks for your help.
You don't navigate between MXML pages. MXMLs are not pages to begin with. Instead they are components, that are displayed in the application. So if you want to change the current display, then you need to remove the already added components, and add others that should be displayed now.
There are different approaches to do this. The very raw way of manually removing elements is rarely used, instead there are two main methods: ViewStacks and display states. Display states should be used when there are not many different changes in a view, for example when you click a checkbox that adds new options to an existing formular. If you want to change the whole displayed content (this does not have to be the whole application content though, think in components instead), you can use ViewStacks.
ViewStacks are like a stack of paper, where each paper reflects a single view. So if you want to display something else, you move the new view to the top, hiding all others below. Many components, including TabNavigators, are just ViewStacks with an additional menu to select the view that should be displayed. But you can also just use a ViewStack and manually change to what you want to show.
Flex is not sidebased like html.
You have to instantiate or remove classes, components or all this stuff.
i would use the states.
You can register handler to buttons and swap the state.
Then you are able to instatiate or remove components via the tsates.
Which flex version dou you use? The management of the states are changing between flex3 and flex4
Assume, you have one app with two content areas, home and gallery. First you have to create these two areas with project->new->component and named there related.
After that, you instanciate both components in your app.
Define two states, home and gallery and swap these with a button or two.
set the propert excludefrom or include with the name of the states. finally, you have an app with two content areas, but you never swap pages, you instanciate or remove components in runtime.
br
Frank
BR
Frank