boen_robot

To "read" PHP files, you don't need anything. PHP is processed on the server and returns only (X)HTML for the browser to read.If you need to create or should I say "use" PHP files and use their abilities on a host, that host has to support PHP. If it does, all you need to do is place a file containing PHP scripts. If it doesn't you can't make anything to enable PHP.If you want to turn your own PC into a server so it can process PHP files you need to either download all-in-one server packs such as the above mentioned easyphp or something else such as XAMPP for example, or you can download the server's components (Apache, PHP, MySQL) one by one and assamble them, which is harder, but does give you more control of everything.

Initially I was thinking about not having them, but if they are removed, this means you won't be able to "change your mind" without submitting the form first. Let's say the menus look like this: |Date| |From| |Subject| |Title| The user changes changes From to Date. At that point, the drop down menus should look like this: |From| |Date| |Subject| |Title| Scince Date was already present as a selection to the first drop down menu, the script should look for something else, it may find Subject and see it's avaiable as a selection inside the third menu, and therefore try something else. The same may be repeated for Title. It then finds From, which is not selected anywhere else, therefore it switches the value of the previously repeated Date to From.

I know we are not suppose to request full scripts, but I'm really not good with JavaSciprt at all. Besides, what I want is for a friend of mine's site (though I would probably use this as well).So the issue I have is that, if we have (let's say) 4 drop down menus, each containing the same options. Could JavaScript detect a change in one of the menus and change this option from the other menu if it's the one selected?The idea is to have a script for changing different table columns' order. An example- the options in the drop down menus are Date, From, Subject and Title. Each drop down menu if looked without JavaSciprt contains theese in the same order (or not? If it's a requrement for a smooth work, it could be done). If I would like Date to appear second, I would go to the second menu and select Date from it. The script should detect the change and change all other "Date"s to some option which isn't repeated on other fields. If I go to the other fields and select the Date inside them, this would again change the Date from the second dropdown menu to another option which hasn't been yet selected.PHP would be used to verify the data anyway, so this isn't urgnent nor insecure (if the user has turned JavaScript off). It's all for the sake of user's comfort .

By using CSS. either inline or a separate one. Example for inline one: <a href="#" style="color:red;">link text</a>

I think that's what Different CMS(Content Management System)s are used for. Only to share a lot of information without any more "detailed" needs for desingn, functionality and so on.If you do need to have your own design and functionality, you could use Server Side Scripting to select and include the content of specific HTML inside the current page by using a GET variable to select the proper content.Considering that you just want to share information, it might be better to go with the CMS solution though.

According to the XSL functions description on the PHP home site, the extension is built in, but it requres the libxslt to be installed and to add the argument --with-xsl[=DIR] to my configure line. I downloaded the library, but how do I install it? And where the heck is that configuration line? Is it somewhere in the php.ini file? If so, where?

Try to add <xsl:template match="/"><xsl:apply-templates/></xsl:template> The match of "/" is usually the piece needed to invoke the rest of the templates by the apply-templates elements.If this doesn't help, could you please provide a sample XML. I seem to be unable to get used to your schema, so if you have a sample valid XML file, this would help the investigation .

Normally, a program such as Internet Explorer, MS Word, Windows even or any other kind of application that you can imagine is compiled into files which only the OS can read and manipulate. Their functions and all are predefined by the author and "packed" into the respective files.When a program is Open Source however, the code from which the application was compiled, is avaiable to the public. That way, everyone who has skills in the used language (most often C++) can edit every major and minor aspect of the application and recompile his new version.I personally don't care for open source-nes scince I don't have C++ skills anyway though .[edit] Yes. Linux is oper source. That's why there are so many versions of it, each with it's own specifics. [/edit]

Well, scince we are taliking XML stuff, I guess the XML forum is the right spot, but you already started the topic here, so let's see the issue and if we could solve it. I read XSLT mentioned... I might be able to assist if so. However, I haven't even heared of this eXist though.

Whatever that Line Feed is, I don't think it's any W3C reccomendation. It looks more like some kind of Microsoft's XML specification. So XML files COULD contain such thing it's not something that SHOULD exist in any other XML based file I think.

I saw the DOCTYPEs which the W3C validator supports and guess what- XHTML Mobile is not among them... Use strict instead. Mobile phones support it anyway .

Well no wonder then. Absolute positioning as far as I know places the element on the specified pixels from the screen's top left edge no matter where in the code it is. Make it relative or adjust the pixels properly.

What are the class's properties? We are talking CSS problem here after all.

It would be A LOT easier to understand XQuery if you know XPath scince XPath is part of XQuery's syntax. Tutorials and "try it" examples are avaiable on W3Schools. You will then be perfectly comfortable with XQuery's spesifics, though I presume that you'll ask yourself a lot of questions when you learn them, but that's another thing.Or do you actually already know them but you want to increase productivity? Hmm... I don't know. Perhaps theese tools are the only ones avaiable, scince XQuery is not even a reccomendation yet.

Before seeing this site, I didn't believe things such as Opera being the fastest browser, but now I do .At a resolution of 1280x1024 there is a repetition of the left... um.. navigation, but without the buttons. That's on all browsers.You have used many deprecated HTML attributes and because of that, not only the site looks awful without CSS, but also, the things load a bit funcky...Instead on using JavaScript for the menu, try to use the :hover pseudo class instead and make both images (for idle and on mouse over) be in one image, which would be pushed down (a very frequently used technique). For some text which you have included in pictures could have been done with plain text I think.By the way, one question. How did you made the picture with the guy wearing classes to load backwards (from bottom to top) ?

Perhaps if you rename the XHTML tags to RSS ones?

There is an option to show the results as posts you know... the bottom right corner ?

Shouldn't this be in the browser discussion topic? Merge?Anyway... nice references.

It works fine with me (no CSS attached). Perhaps a <br /> after the <img />?

I'm not sure I understand your point... a site doesn't change the user's resolution after all. It only adjusts itself to the user's resolution. And you can adjust sizes with CSS(width and height properties) and give them absolute values (pixels). However, for the sake of flexibility (editing only one file for all resolutions), try to use more relative sizes (percentages).

I don't see what you need the <xsl:value-of select="." /> scince the picture element is empty, but if it must be like that, so be it. As for the alt text. If it must appear in both the image and below the image: <xsl:template match="picture"> <xsl:value-of select="."/> <xsl:variable name="src" select="@src"/> <xsl:variable name="class" select="@class"/> <xsl:variable name="alt" select="@alt"/> <img src="{$src}" class="{$class}" alt="{$alt}"/> <xsl:value-of select="$alt" /></xsl:template> If it must appear only below the image, you can always remove the variable and place @alt at the last <xsl:value-of /> instead.

That's what the <xsl:comment> is used for: <xsl:template match="comment"> <xsl:comment> <xsl:apply-templates/> </xsl:comment></xsl:template> The difference here is that the <!-- and --> mark the coment inside the XSLT document itself. And <xsl:comment> marks that the content inside it suppose to be outputed as a comment marked with the above.

Those in this forum who know me already know what I'll say, but I'll still say it, because I think of more unprejudiced way of saying it :First come the common things such as (X)HTML, CSS and XML. That's the thing that all interested should know. From then on there are many things that sometimes collide with each other- client side ways and server side ways.Client side ways- This includes client side languages such as JavaScript and VBScript. Between theese two, JavaScript is THE ultimate way to go with. Besides scripting, client side ways also includes XSLT and other XML based languages, each having it's quite interesting in my opinion abilities.Server side ways- Includes SQLs and server side scripting languages. MySQL/MSSQL/Oracle for storing data and server side scripting language(not only PHP but also ASP(.NET), Cold Fusion, JSP, Perl and many others) for not only manipulating that data but also for... well... let's say for everything. Even client side ways have their (possible) eqivalents in server side scripting. Server side scripting is the ultimate tool in a big project.In order to be able to efficiantly create sites, you would need to know the common trio, at least one client side and at least one server side way. I personally don't know any server side language yet, and I'm not at all good with JavaScript either.So I'm a newbie unfortunatly but hey, I started only last summer and I already know a lot more than most of my friends who are also interested and have began sooner then me .

I already know the answer. It won't work, because "<" and ">" are invalid inside elements including atribute values. Replacing them with entities is going to make only plain text.Creating "invalid" XSLT code is what I think we can call the holy grail of XSLT .

Noooo. Data Islands are only supported in IE. It may seem as the easiest method, but it's the worst. They are what I like to call "web mistakes", simillarly to the <font> tag. It seems convinient at first (direct XML to XHTML binding) but then you realize it's drawbacks, such as the lack of conditionals, advanced XPath expresions, etc.As for server side scripting... if you have ASP or Cold Fusion, you may use it to execute the XSLT. This would make the transition between the above method and the new one a lot easier. If php, you would use PHP's XML functions + other PHP functions (in short: a lot of code) for the same purpose that XSLT has and use includes at the proper place. Using XML and XSLT and execute them with a server side scripting language is the best method in my opinion, but please, don't even get started with Data Islands.