When colouring the tables in confluence i feel a bit limited by the 6 available colours on the tables, I want to know if its possible to add aditional colours to the pallette through the adminstration functions. Also is it possible to alter the existing colours.
There's no good way to do this, see the bug report.
Nevertheless, there seems to exist a hack
Related
I'm trying to choose multiple options from one chooser in netlogo. Does anyone know if that is possible and if it is how to do it?
One possibility is to use the eXtraWidgets (xw) extension, which allows you to define multichoosers like this:
A few words of warning:
The extension only allows you to put that kind of widget on a separate interface tab.
The extension is fairly powerful, but there is a bit of a learning curve to it: widgets need to be declared programmatically, you can't just drop them on the interface.
As of today, the 6.x version of the extension is still in beta. The author has had limited time to iron out all the kinks.
I am the author of the extension.
If xw doesn't meet your needs, you can most likely achieve what you want by using a series of switches, like this:
It's not quite as pretty and convenient, but it can get the job done.
I was trying to find a way to manually add data for the said tables but I couldn't find it. I also tried searching in google but I couldn't find a correct answer either.
Do you guys know what table do they represent? Thanks!
You can't create course sites without having defined at least one academic term; if you haven't done so, Sakai leaves you in the cold, and the only way to fix it is to populate the database table in question, CM_ACADEMIC_SESSION_T, manually, by using an INSERT query.
The Sakai documentation doesn't explain how to do this, or whether it really suffices, but you can ask the sakai-dev mailing list or go by the answers to this question provided there in the past (e.g. here or here) and hope they still apply. (This is typical for Sakai.)
An alternative is not to use course sites at all (I didn't trust them after discovering this) and use project sites instead.
How to get to this wizard after my report has been created? When I create a new report I can find this thing, but not when I already have a report.
This is not a great solution, but might be better than starting over with the wizard. You can save the .rdl for the report to your machine and then look into modifying the rdl manually. I can't provide any real guidance here except that I was wondering how to do the exact thing you asked.
Note the Tablix tags as they represent your table(s). It looks like everything could be adjusted by hand here so long as you had a pretty good idea of how you wanted your table to display. I would strongly recommend starting with an rdl where the report already has as many of the elements you need to use. Changing existing values will be much easier than deriving them from scratch.
I know it's not the answer you want. It's not even the answer I want. But...I think this is the only option left aside from deleting the table and recreating via the wizard.
If you're using Report Builder you can launch de Wizard from the ribbon chart, tablix and matrix options.
I'm going crazy trying to get all of the editors to look similarly. It looks like there's a different color editor option for each file type/code type, which means it takes FOREVER to customize the view.
Add to that: each code/file type color option seems to honor the default set in the generic options only if it feels like it (seems buggy).
I'm currently using Eclipse 3.4.1 (Ganymede).
Is there a version that is less buggy or is there a more consistent way to change the text colors?
Barring that, has anyone gotten a Zenburn-like color scheme in Eclipse that would be willing to share?
I'm working on an Eclipse plugin for this:
http://marketplace.eclipse.org/content/eclipse-color-theme
It's by no means complete, but it does work quite well already.
It sounds like there isn't currently a good way of doing this because of the way Eclipse was designed: there's not a good, flexible, inheritable syntax highlight framework to bring consistency to everything.
While you can export & import preferences as Wijnand Warren's answer states, and that does work... kind of... actually going in and editing the preference files to make sure that you're only sharing color information is probably a huge pain in the butt, so not simple. Also, that still leaves the problem of finding someone who has put in the effort & time to create the syntax coloring in the first place.
Also, every time you add a new type of structured text editor (new language per year anyone?), you'll have to go back into settings & edit the highlighting for that language as well.
I have no experience developing for the Eclipse platform, but if someone with more experience would be willing to point me in the right direction (documentation, explanation of how things fit together, etc.), please let me know.
I've searched high and low for an answer to the same question and have all but given up. It is not easy to change the color scheme because, as you said, each language has its own options buried deep in the Configuration tree.
I've read a little about why 'themes' aren't available, and it has something to do with the complexity of Eclipse's XML storage technique. I'm sorry that I can't provide a real solid answer, but I just wanted to let you know that you're not alone in your frustrations.
I've been looking for this too and after a bit of research found a workable solution.
This is based on the FDT editor for Eclipse, but I'm sure you could apply the same logic to other editors.
My blog post: Howto create a color-scheme for FDT
Hope this helps!
Install the color theme plugin from http://eclipse-color-theme.github.com/update. It already consists of some good themes that you can use.
Then just go to menu Window → Preferences → General → Appearance → color theme to apply the themes.
You can download more themes from http://www.eclipsecolorthemes.org.
Just wanted to get an idea for ways (web) developers get round the short fall of (most) WYSIWYG editors, whereby the users that are editing the text aren't always HTML literate enough to produce good/great results.
In the past we have resigned ourselves to either locking down the editor or simply not supplying one.
What are other peoples experiences?
If I understand your question correctly, my advice would be to allow basic text formatting in the editor (bold, italicize, underline, paragraph breaks, etc). Anything beyond that should be handled either by custom fields in your CMS system that talk to the corresponding template, or directly by your designers / front-end people. There really should be no designing going on in your text editor.
Also, using a templating language like Markdown might help editors feel more comfortable formatting their pages.
If you have the resources (as the question implies you do) you get the users to supply copy and designs in what they do know (Powerpoint, Word, Fireworks, etc) and get the people who can do a correct implementation (but who might not be able to write decent prose, etc) to put it into the HTML/CMS/magicthing.
Sometimes it is possible to use something like WYMeditor - it isn't that simple but produces clean semantic code. The other way is using some wiki-like code - Markdown for example. And you can ease editor's life by using some helpers like MarkItUp editor (it also supports original Wiki and Textile).