Re: [SMW-devel] Header Tabs Revisited
Hi Sal, I believe this is mostly just an issue of perception. Basically, the way I understand browser loading to work, if there's any Javascript linked at the top of the HTML page, it has to get downloaded fully before any of the HTML can be displayed. You can read more about that here (ironically, it's a Yahoo document): http://developer.yahoo.com/blogs/ydn/posts/2007/07/high_performanc_5/ That's one of the things the ResourceLoader, added in MW 1.17, tries to address: it puts all (or most) the Javascript, as well as some of the CSS, at the bottom, so that the HTML can be displayed right away. The downside to that is that it gives the weird effect of the HTML getting displayed before it's fully formatted, so you get things like the tabs showing up as a bulleted list first. People aren't used to that, so they view it as slow loading. (It could be that the YUI library did get loaded faster as well, though I don't think it's a significant difference.) There is actually a way in ResourceLoader to declare that a certain set of Javascript and CSS files (i.e., a "module") should get loaded at the top, instead of the bottom - my understanding when I heard about it was that this wasn't fully implemented yet, but that was in 1.17 - maybe in 1.18 it works. (Or maybe it was always working fully - I should look it up.) Anyway, it's worth looking into for Header Tabs specifically. -Yaron On Fri, Dec 9, 2011 at 11:00 AM, Sal Quintanilla wrote: > Hi Folks, mostly Yaron, > > ** ** > > I’m trying to get our organization to formally move away from Foswiki and > towards Mediawiki / Semantic Mediawiki. I have a compelling MW site that > deals with many of the issues we face daily. > > ** ** > > However, there is a concern regarding performance. Certain page delays > are covered by explaining that the page includes several queries, compared > to our current, similar Foswiki pages that are created by hand. However, > the one problem I can’t get around that people come back to is the speed of > Headertabs. They see what should be a static page in MW that uses > headertabs, and see the pre-tab list of tabs come up first, and interpret > that as performance issues. My MW 1.16 / older SMW install showed the tabs > quickly, and overall load speed is faster. Unfortunately there are new > features I need and I can’t use the older stuff. > > ** ** > > Is there anything that can be done to either lose the bullets, or better > yet use the yui version under MW 1.17 or higher? I know this has been > discussed, and technically it’s clear why it’s a lower priority, but I’m > asking again, because to admin / management decision makers, what they see > affects their interpretation more than how it works. > > ** ** > > Thanks. > Sal > > > -- > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point > of > discussion for anyone considering optimizing the pricing and packaging > model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > ___ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Header Tabs Revisited
Hi Folks, mostly Yaron, I'm trying to get our organization to formally move away from Foswiki and towards Mediawiki / Semantic Mediawiki. I have a compelling MW site that deals with many of the issues we face daily. However, there is a concern regarding performance. Certain page delays are covered by explaining that the page includes several queries, compared to our current, similar Foswiki pages that are created by hand. However, the one problem I can't get around that people come back to is the speed of Headertabs. They see what should be a static page in MW that uses headertabs, and see the pre-tab list of tabs come up first, and interpret that as performance issues. My MW 1.16 / older SMW install showed the tabs quickly, and overall load speed is faster. Unfortunately there are new features I need and I can't use the older stuff. Is there anything that can be done to either lose the bullets, or better yet use the yui version under MW 1.17 or higher? I know this has been discussed, and technically it's clear why it's a lower priority, but I'm asking again, because to admin / management decision makers, what they see affects their interpretation more than how it works. Thanks. Sal -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] "one-to-many" validation
Hi Vlad, The "text with autocomplete" and "textarea with autocomplete" input types both allow multiple values. If you're going to change the code to support it, please note the "delimiter" parameter - by default the delimiter is a comma, but it can be manually set to be a semicolon, newline, etc. instead. Yes, a blank value should be accepted - just like the dropdown input lets the user choose a blank value in addition to all the pre-specified values (unless the field is mandatory). -Yaron On Fri, Dec 9, 2011 at 3:28 AM, Vladimir Kostyukov < vladimir.kostu...@gmail.com> wrote: > Hi Yaron, > > Sorry for delay. > > Regarding fields with multiple values. You are right, its big potential > problem. But I can try to implement it support. Which fields can has > multiple values? > > Regarding mandatory fields. From my point of view this is > correct behavioral. Mandatory - means "required field". Right? Then just in > case: our cobobox is not required (not mandatory) and it has "existing > values only" tag. How we should interpret empty field? Empty string - is > not existing value from category for example. > > Thanks for reply, I am going to thing about fields with multiple values. > > On Fri, Dec 9, 2011 at 1:47 PM, badon wrote: > >> Here is the bug report for the issue being discussed: >> >> https://bugzilla.wikimedia.org/show_bug.cgi?id=26088 >> >> -- >> View this message in context: >> http://wikimedia.7.n6.nabble.com/one-to-many-validation-tp678004p1371217.html >> Sent from the Semantic Mediawiki - Development mailing list archive at >> Nabble.com. >> >> >> -- >> Cloud Services Checklist: Pricing and Packaging Optimization >> This white paper is intended to serve as a reference, checklist and point >> of >> discussion for anyone considering optimizing the pricing and packaging >> model >> of a cloud services business. Read Now! >> http://www.accelacomm.com/jaw/sfnl/114/51491232/ >> ___ >> Semediawiki-devel mailing list >> Semediawiki-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel >> > > > > -- > Thanks, > Vladimir Kostyukov > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] "one-to-many" validation
I agree with Yaron. The "mandatory" parameter should have a limited meaning: something must be entered. The "existing values only" parameter should not require that something be entered. Instead, it only requires that IF something is entered, it must be an existing value. -- View this message in context: http://wikimedia.7.n6.nabble.com/one-to-many-validation-tp678004p1379149.html Sent from the Semantic Mediawiki - Development mailing list archive at Nabble.com. -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] "one-to-many" validation
Hi Yaron, Sorry for delay. Regarding fields with multiple values. You are right, its big potential problem. But I can try to implement it support. Which fields can has multiple values? Regarding mandatory fields. From my point of view this is correct behavioral. Mandatory - means "required field". Right? Then just in case: our cobobox is not required (not mandatory) and it has "existing values only" tag. How we should interpret empty field? Empty string - is not existing value from category for example. Thanks for reply, I am going to thing about fields with multiple values. On Fri, Dec 9, 2011 at 1:47 PM, badon wrote: > Here is the bug report for the issue being discussed: > > https://bugzilla.wikimedia.org/show_bug.cgi?id=26088 > > -- > View this message in context: > http://wikimedia.7.n6.nabble.com/one-to-many-validation-tp678004p1371217.html > Sent from the Semantic Mediawiki - Development mailing list archive at > Nabble.com. > > > -- > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point > of > discussion for anyone considering optimizing the pricing and packaging > model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > ___ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > -- Thanks, Vladimir Kostyukov -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
