seam-gen and flex - seam

I have integrated seam and flex with FlamingoDS
I got html file from mxml file and I stored it in WebContent folder it's fine
then I want to create link named as 'Plan' in menu.xhtml
My aim is to get that html file when i clicked on this button I don't know what to do for that
so, I have created some test.xhtml in that top element is the
for the template attribute this element I have given the template.html
and I used
then for 'Plan' link I gave the view="/test.xhtml"
It's fine when I clicked on that link I am getting the test.seam file which includes our html file but this html file is coming in some fixed area with scroll bars only eventhough there is a lot of space to fit
Please help...... me

First of all, it is very difficult to read your post. Please format it more readable.
Secondly, we can only guess what's wrong when we cannot see any code. But my hunch is that you are using s:decorate that includes some formating you are not aware of. This comes in standard seam-gen. Try removing that s:decorate stuff or point to another style you wish to use.

Related

Correct syntax for file path in background-image:url(''); in a twig file (building template for mautic)

I started to work with mautic (open source email marketing automation).
Im trying to build a template for a landing page and therefore I'm editing "*.html.twig" files. At least I could find out that twig is a PHP engine by Symfony. What I could not find out yet though is something actually totally simple, at least in css/html.
All I want to do is specify the correct file path to an image file as a background-image:url(''); within the style attribute of the body tag. (See example below)
How on earth is this twig working with file paths? It seems to automatically change the file path I specify, but in a way that is not comprehensible to me.
I tried several options, but the only thing that works at least partially is specifying the absolute path. As soon as I start using the template in mautic though and build a page from it and save it, even the absolute file-path gets 'crashed' on the output source code. What the heck?
I did not find much info on file path syntax in twig. What I found sounded so horribly complicated that I can't believe it should really be that complicated to simply put in a file path? Am I wrong?
Here is the example, specifying the absolute path in the actual source code.
<body style="background-image:url('http://sawiya.de/mautic/themes/mautictheme1/img/background.jpg'); background-color:#213E4C;">
When viewing the result in the browser, without adding content to the landing page template, the source code output is the following (path changed, but the result is at least that the image is being shown):
background-image:url(http://1.1.1.2/bmi/1.1.1.5/bmi/sawiya.de/mautic/themes/mautictheme1/img/background.jpg);
After adding content on top of the template in mautic, the file path is being changed even more and reads the following from the source code output (now the background image does not get displayed anymore, so its clearly broken):
background-image: url(http://1.1.1.3/bmi/sawiya.de/mautic/"http://1.1.1.5/bmi/sawiya.de/mautic/themes/mautictheme1/img/background.jpg")
What is this all about? Where can I get the info on how to easily and correctly specify the file path? Is it really that hard?
Ok, now I found out something strange. It might be a bug in mautic here.
When I open the page where I specified the image via the background-image:url() through the https:// -Protocol, instead of http://, it works!
And the resulting source code looks as expected:
background-image: url("http://1.1.1.5/bmi/sawiya.de/mautic/themes/mautictheme1/img/background.jpg")
So, wrong adress here, I think. At least to solve the bug. Hope someone finds this as a solution, until the bug is fixed.
Cheers!
Edit: Of course its better to specify the file path in a relative way, so that when the theme is used on another server, the path is still correct. In twig the best way to do that seems to be this. At least it works perfectly well.
background-image: url('{{ getAssetUrl('themes/'~template~'/img/logo.png', null, null, true) }}';)

How to put pictures in a single row using semantic view?

I'm trying to put these pictures in a single row using semantic view in drupal7. I just created this view named try and put 2 pictures in it.
After that, I'm editing this view->format-format->setting->row (this is asking for class attribute, not mandatory) and I don't know what to write in this class attribute.
How do I put these pictures in a single row?
Make custom template for that view. Open "Advanced settings" on right side of view editing page and at bottom find "Theming information". There you can see template file suggestions. There if you can see the code of default templates (and copy it to clip board) but you can also see naming suggestions for overriding default templates. So copy code from default template, make from it file with some suggested name, save file in your theme...and clear the cache.
Then change the file as you wish, depending on your needs....
The CSS 'display:inline-block' is a good way to make rows. CSS Flexbox is more difficult to understand, but very powerful. Occasionally, the CSS 'float:left' will do what you need, but it has a tendency to 'log jamb' on differing element heights.
I have used Semantic Views to create continuous, wrap-around content from multiple View rows. I removed the View row element by deleting the default 'div' in the 'Format settings'. That way only a continuous stream of fields appears within the '.view-content' tag.
A custom template is also good.

Mageno module idea

I'm working on Magento modules.
After few guides I managed to create module that says "hellow world".
Also I have made some of css code that add simple image border around whole page.
So the problem is: how to combine them together?
I want that when I install my module, image border appears around page.
What should I be looking for? Any tips? I need right path to look for answers
T.y.
You need to to
Create a module
That modifies the global layout such that your CSS is added to the page
Re: number two, there's multiple ways to go about doing this. These days I favor the event/observer method
Add an observer for the controller_action_layout_generate_blocks_after event
Fetch the head block from the layout in your observer method
If you find a head block, add your CSS file to it programtically
The more traditional way is
Configure you module to include an additional layout update XML file
In the default handle of your new layout update XML file, add XML that tells Magento to add your CSS file
That should give you enough to google on and come back with more specific questions. Good luck!

Twitter Bootstrap - Can't get form to display properly

I have a form that I'm making in bootstrap but no matter what I do, I cant seem to get it to look how it looks in the tutorials. The label goes above the text box when it should be beside it, and the whole thing looks like it lacks any css formatting. Thanks for your help.
Here is the site that I'm working on and you can view the source code there:
aerofied.snbw.co/registration.php
bootstrap.min.js returns a 404 error and I believe this is the reason.
This is the URL that returns the error: http://aerofied.snbw.co/js/bootstrap.min.js
You should also read the Bootstrap documentation. You must use some specific classes for your forms.

Do I need to rename vector.js for custom Mediawiki style based on Vector?

My question is simple, do I need to rename vector.js file when I create a skin based on Vector? Let me explain more on how I created my custom skin...
I have created a custom skin for my Mediawiki and its based on Vector. My skin works almost exactly like Vector but with css tweaks and with changes to the html template elements inside the skin template which is basically moving around the elements and displaying a bit different that the way it is done in Vector. I read the following tutorials when creating my template:
https://www.mediawiki.org/wiki/Manual:Skinning/Tutorial
http://blog.redwerks.org/2012/02/28/mediawiki-subskin-tutorial/
These are the things I did when creating the custom skin:
I copied and pasted the Vector folder and then renamed it to 'myskin'.
I then created the 3 files, skins/myskin/myskin.php, skins/myskin/MySkin.skin.php and skins/myskin/MySkin.i18n.php like its mentioned in the tutorial link above.
I then renamed the key, identifier and name of my skin from vector to MySkin or myskin like its mentioned here:
"When building a skin you'll be working with your skin name in three
forms, a lower-cased key, a camel cased identifier, and a localized
skin name. For our skin the key would typically be 'myskin', the
identifier 'MySkin', and the localized name 'My Skin'.
I edited the screen.css and tweaked it to the style I want.
I then edited the skin template. Here instead of using "class SkinMySkin extends SkinVector", I copied the "class MySkinTemplate extends BaseTemplate" section from Vector and re-arranged the templates and tweaked it to create my skin.
After doing all of the above, everything works. However, I noticed that when I copied all the files from Vector to MySkin, there is this "vector.js" file in it too. I dont know if I need to rename this js file to myskin.js or do I leave it like this. Currently I did not rename this javascript file and everything seems to be working fine anyways. So I am not sure what this file does. I read the tutorials and also searched MediaWiki and it doesnt mention anywhere if I need to rename this file to myskin if I am creating a skin based on Vector. I also dont see a link or reference to this file inside my skins/myskin/myskin.php, skins/myskin/MySkin.skin.php and skins/myskin/MySkin.i18n.php files. Can someone please clarify this for me?
I have also created a custom skin with the manual like the OP. I didn't rename vector.js and everything seem to work fine for me.
You could simply rename or move vector.js and check if you notice any missing functions or weird behaviour in either the following functions
Collapsible tabs
Focus search input at the very end
animate drop down menu in and out
or
Always collapse if the "More" button is already shown
Since this is more or less all the .js seems to do + providing some fallbacks.

Resources