[SMW-devel] List of SMW professional support
Dear all, I have just cleared https://www.semantic-mediawiki.org/wiki/Professional_support, since it was full of obsolete entries. Please re-add yourself to the relevant section if you are currently providing SMW services. Best -- Jeroen De Dauw | www.EntropyWins.wtf <https://EntropyWins.wtf> Professional wiki hosting and services: www.Professional.Wiki <https://Professional.Wiki> Entrepreneur | Software Architect | Open Source | Longtermism ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] DisplayTitle and Wikibase
Hey Olivier, This is indeed better suited for the Wikibase mailing list, since it is about how to hook into Wikibase. Cheers -- Jeroen De Dauw | www.EntropyWins.wtf <https://EntropyWins.wtf> | www.Professional.Wiki <https://Professional.Wiki> Entrepreneur | Software Crafter | Speaker | Open Souce and Wikimedia contributor ~=[,,_,,]:3 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Need hook for page property changes
Hey Sebastian, I suspect this hook is the most appropriate for your use case: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/6d3ce63cbeb3d2b881dfe6c255375c2b07e1b75d/src/Store.php#L240-L243 Cheers -- Jeroen De Dauw | www.EntropyWins.wtf <https://EntropyWins.wtf> | www.Professional.Wiki <https://Professional.Wiki> Entrepreneur | Software Crafter | Speaker | Open Souce and Wikimedia contributor ~=[,,_,,]:3 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Query result rewrite
Hey all, > I'll be linking the code here as soon as there is something substantial to look at. We're now 6 years later and I finally have something to show! A quick recap: writing result formats for SMW is a big pain due to a number of serious design issues. And testing is (almost??) impossible. That is why I have designed a *new way to create result printers*. This is still very much in draft stage (though perhaps not for long). So you cannot use it yet to write new formats. However you can, and are encouraged to, give feedback on the new design. You can find the code at https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/4313 The linked pull request has examples of registration and implementation, which should give you a quick idea of what the new approach is like to work with. After all, making this important SMW extension point easier to work with is the core goal, so the primary thing *I want your feedback* on. Cheers -- Jeroen De Dauw | www.EntropyWins.wtf <https://entropywins.wtf> | www.Professional.Wiki <https://professional.wiki/> Software Crafter | Entrepreneur | Speaker | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3 On Thu, 24 Oct 2013 at 23:55, James HK wrote: > Hi, > > +1 > > This last time I had to write a unit test for the table format, I had > to bit my hand off to get some sane results. > > If you can make it in time, don't show them "old" interface as this > one is not going to last and it doesn't improve one's understanding in > how to interact with a query format or what that matter with the > result itself. > > Cherrs > > On 10/25/13, Jeroen De Dauw wrote: > > Hey, > > > > While working on my dev workshop for SMWCon, I noticed it is currently > > rather impossible to write a sane unit test for a result format. The > > reasons for this are that the result object, SMWQueryResult and the > objects > > it is composed of, contain a ton of stuff not relevant to those tests, > > including database access to get the actual results. > > > > I figured it'd be good to have a cleaner interface that can be used by > new > > code, and demonstrated in the workshop. So I'm now working on creating a > > fresh implementation of the result objects, that will be available as an > > alternative to the current way of doing things to result printer authors. > > In other words, this will not be a compatibility breaking change, the > > current approach will remain usable for the foreseeable future. > > > > This is just a heads up I'm going to work on this, no real work has > > happened yet. I'll be linking the code here as soon as there is something > > substantial to look at. > > > > Cheers > > > > -- > > Jeroen De Dauw > ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Removing "nameproperty" from SRF "graph" format because of unclear intention
Hey Sebastian, The nameproperty parameter appears to be unused which means it can be removed without changing behavior. Actually on second look the parameter does not even seem to exist, just some code that uses it if it did. Given its name I suspect it was meant to get the name of a printeout to use for some label on the graph. Similar to https://github.com/ProfessionalWiki/ModernTimeline/issues/9#issuecomment-523070103 Cheers -- Jeroen De Dauw | www.EntropyWins.wtf <https://entropywins.wtf> | www.Professional.Wiki <https://professional.wiki/> Software Crafter | Entrepreneur | Speaker | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Question regarding the policy of freezing SMW 3.0 milestone issues
Hey, I am rather unhappy that the volunteer nature of the work keeps being brought up as a reply to the release process not being good. Yes, you cannot reasonably demand that a volunteer invests more of their time, or that they spend it in a certain way. The issue here is a poor release process, which in my view is quite orthogonal. There are also many stakeholders beyond James that are affected, and they are not irrelevant. Most noticeably the users of the software, which are not getting access to long developed features. There are also the other people that contribute to the software. Speaking for myself, I am not enthusiastic at all to contribute to a project if it is not clear my improvements will see the light of day in a reasonable time frame, and things I previously contributed have been sitting in the dark for over a year. Such a situation is also not appealing to potential contributors. Some time ago I started work on adding visual editing to the Maps extension, to be released as version 6.0. At some point I ran out of time having gotten only part of the way there. As there was already useful functionality added, I decided to just release that rather than potentially keeping it unavailable for months. So the users win. And contributors to Maps know that their contributions are likely to be released within a week or two. The same could have been done for SMW 3.0 long ago. Instead, new features have kept being added to the milestone. Now if James does not want to spend time on doing a release that is his decision. Should it also be his decision to block any release form happening because he is the primary contributor, even if that throws all other stakeholders under the buss? I don't think so. And yes, that is what is happening. I have offered spending time on doing a 3.0 release in the past, always getting a "you can't do this and don't rush me" type of reply. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Question regarding the policy of freezing SMW 3.0 milestone issues
Hey David, I share your concerns and the desire to have a 3.0.0 release sooner rather than later without delaying for more features. We had a quick back and forth about this at the beginning of June, see https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/1365#issuecomment-394930906 and the following comments. Sadly enough we do not have any written down policies for when to create new releases. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Issuehunt?
Hey Bernhard, I think it would be very cool to have such a thing and checked out IssueHunt. Apparently this service requires that you give it write access on all public GitHub repositories you have access to. That is an absolute no-go for me. I wrote them explaining how this is a problem. Perhaps there are alternative services that are better? > PS: by the way I was cutoff the smw mailing lists due to reasons unknown to me. had to re-register... Reason: SourceForge is trying to obsolete itself even more Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMWQueryResult mock object for testing SemanticResultFormat
Hey, I concur with James on avoiding using SMWQueryResult in your tests directly. This class has many issues, most notably that it pretends to be some kind of Value Object, while actually not containing the data, but rather depending on services bound to persistence and framework to retrieve the data. I ran into this issue in 2013 and wrote some mails about it [0] and then some rudimentary alternative [1] that might now serve as inspiration. Generally speaking it should be possible to just give your result printer a value object with the data it should display, and then assert that it returns the correct stuff, in a functional manner, without any services being involved, be them persistence services or otherwise. [0] wikimedia.7.x6.nabble.com/Query-result-rewrite-td5015574.html [1] https://github.com/JeroenDeDauw/CheckedTable/tree/master/src/SMW/Query/Result Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate | Developer at Wikimedia Germany ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Modern chat solution as alternative to IRC?
Hey, The IRC log and GIT links on the IRC have been fixed and both Stephan Gambke and I now have admin rights on it. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate | Developer at Wikimedia Germany ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Modern chat solution as alternative to IRC?
Hey, I suppose the IRC could be linked more prominently, and as "SMW chatroom" rather than "IRC", so people that do not know IRC don't get scared from the get-go. One place where it is currently missing is the homepage, in the "User community" section next to Facebook, YouTube, etc. This could be combined with some short documentation (maybe a video) showing how to get the more modern experience via a service such as IRCCloud. Hopefully someone can change the URL in the message >> > > Great, yes, let's find who's to do it :) > https://www.semantic-mediawiki.org/wiki/semantic-mediawiki.org:Services_accounts Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate | Developer at Wikimedia Germany ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Modern chat solution as alternative to IRC?
Hey, Thanks for raising the topic Samuel. I can be lazy and not outline my view on this matter as it is identical to what Stephan already wrote. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate | Developer at Wikimedia Germany ~=[,,_,,]:3 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW working together with extension:Wikibase?
Hey, The conflict of the property namespace is the only issue that I can think of. And I suspect you can get around that by configuring one of the two to use a different name for this namespace. Then again, I've not tried this, so might well be wrong. Beware that Wikibase is nowhere near as ready as SMW for third party usage. See my answer here for more details: https://www.quora.com/To-implement-a-new-easy-to-use-semantic-MediaWiki-based-internal-knowledgebase-should-I-implement-Wikibase-or-Semantic-Mediawiki-Why Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate ~=[,,_,,]:3 -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] using variables set in localsettings in javascript
Hey, Note that this is a MediaWiki question, not really a PHP one. You can be the most brilliant PHP dev out there and still won't know how to do this if you never saw MediaWiki before. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software craftsmanship advocate | Developer at Wikimedia Germany ~=[,,_,,]:3 -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Testing SMW
Hey Daren, What exactly are you trying to achieve? Do you want to verify SMW runs correctly on your system? Do you want to contribute to the project by testing? Something else? We do not have a list of scenarios to manually test, as this is not a maintainable approach. Instead we have several thousand scripted tests which we can run automatically. If you want to contribute to the project, manually testing is not the way to go. With some exceptions, for which which we have a testers group. You can join this group and be notified when one of the developers wants some manual testing to be done, which will include a description of what to do. If you want to join this group, please send me your GitHub username. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [SRF] Semantic Result Formats version 2.3 released
Hey, Thanks to Karsten Hoffmeyer, gesinn.it, Mark A. Hershberger, MW James, bogota, devmania, Stephan Gambke and Translate Wiki for their contributions to this release! Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] src directory
Hey, https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/716 Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] MW 1.25 compatibility issues?
Hey, So to rephrase this: we are not aware of any concrete issues you will run into when using MediaWiki 1.25. However, due to certain annoying changes in MediaWiki, we cannot guarantee stability as we can for earlier MediaWiki versions. That being said, we can still be more confident about using the latest SMW with MW 1.25 than we could be two years back about any SMW version with any other MW version. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW Factbox
Hey John, Thanks for the observation and suggestion. Can you file this on our issue tracker [0] so we do not lose track of it? [0] https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Help us tackle simple style issues
Hey all, Recent improvements in our development infrastructure have lead to a new easy way for people to contribute something back to SMW. There now is now trivial to find code style issues, which typically can be fixed without having to actually understand what the code does. If you can use git, read PHP to some extend and have a few free minutes, you have all you need to make a useful submission. You can find a description of this task and instructions on how to go about it in the tracking issue: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/899 Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Developer at Wikimedia Germany ~=[,,_,,]:3 -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Help wanted with improving Semantic Watchlist
Hey all, I've been looking at what is needed to make a new release of the Semantic Watchlist extension. Unfortunately, this extension has not had a maintainer for quite some time, which leaves us with several open bugs [0]. Most of these are relatively easy to fix, though still need some time spend on them. Similarly, there are some obvious infrastructure enhancements that need some attention [1]. I'm happy to review submitted fixes and enhancements. [0] https://github.com/SemanticMediaWiki/SemanticWatchlist/labels/bug [1] https://github.com/SemanticMediaWiki/SemanticWatchlist/issues?q=is%3Aopen+label%3Aenhancement+milestone%3A1.0.0 Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW in Google Code-In 2014?
Hey Stephan, I'd love to see SMW participate and am willing to help with it a bit (though not pull it). I was also going to point you to the easy label in our issue tracker, but apparently we have nothing much tagged as such: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues?q=is%3Aopen+is%3Aissue+label%3Aeasy Tackling relevant ScrutinizerCI warnings is not a bad idea. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Ask query in extension
Hey,
So you'd have something like
{{#gimmeh_datas_in_a_table: [[Category:Some category]]}}
that results in the same output as the #ask call you posted? If that's all
you're doing you can of course just use a template. Which indeed does not
work if you want to modify the result in certain ways.
Your parser function would hand the query string to the QueryProcessor, get
back the result, and then hand the result over to the formatting thing
(can't recall where this code is). And in between you could try modifying
the result. Be warned though, the result data structure is... odd... So it
might not be trivial to do this.
Cheers
--
Jeroen De Dauw - http://www.bn2vs.com
Software craftsmanship advocate
Evil software architect at Wikimedia Germany
~=[,,_,,]:3
--
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Semantic MediaWiki 2.0 RC3
Hey all, I am happy to announce the third release candidate for Semantic MediaWiki 2.0 is now available. Semantic MediaWiki 2.0 is the next big release, which brings new features and many enhancements. Most notably vastly improved SPARQL store support, including a brand new connector for Jena Fuseki. Preliminary release notes: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/RELEASE-NOTES.md Compatibility tables: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/COMPATIBILITY.md The target for the actual 2.0 release is August 3rd. This release candidate is meant to gather feedback and to provide you with a peak at 2.0 already. If you find any issues, please report them on our issue tracker. https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues ### Upgrading instructions ### If you are using SMW via Composer, update the version in your composer.json to "~2.0@rc" and run "composer update". If you where running dev versions of the 1.9 series using "~1.9@dev" or similar, switch to "~2.0@dev". Note that several extensions to SMW, such as Semantic Maps and Semantic Result Formats, do not yet have any stable release which is installable together with SMW 2.x. If you are also running those, you will likely have to switch them to use a development version. If you are using the tarballs, you can download SMW 2.0 RC3 here: https://sourceforge.net/projects/semediawiki/files/semediawiki/Semantic%20MediaWiki%202.0%20RC3/ More detailed upgrading instructions will be made available for the 2.0 release. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Adding Site Settings support to SMW?
Hey, Perhaps we should move out the existing ones now we are switching to 2.0 anyway? The new mini extensions can be put in the "suggests" section. Or perhaps not, as for those to fully function, you'd first need package definitions of their dependencies as well. Thoughts? Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Adding Site Settings support to SMW?
Hey, > The same thing holds true for Page Schemas, by the way - the code in SMW that hooks into it is somewhat complex, but as far as I know it hasn't required any special maintenance effort on the part of SMW devs. As far as I'm concerned, we (SMW devs) are responsible to not break code in our repo, and to make sure the code we release is working properly. You can create an extension to SMW to avoid the problem. And if you do that, you can specify a compat range, and are not force to keep it working against master the whole time. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Adding Site Settings support to SMW?
Hey, > Unfortunately, there isn't yet a public example of an extension that hooks into Site Settings Just from the description you provided, it is still not clear enough for me to say much about it. The general concern with putting it into SMW is that this forces the people working on SMW to hold it into account. This means making sure it does not get broken when changes are made on the master branch. That is hard to do since it requires the Site Settings extension. If the code is really trivial, then perhaps this is fine. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Adding Site Settings support to SMW?
Hey, Can you give me some idea of what this code you'd put in SMW would look like? Is there already an example somewhere? Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Semantic MediaWiki 2.0
To the developers not actively following the issue tracker: we are now planning the next release to be 2.0 rather than 1.9.3. As excuses for this we are using improved triple store support and handling of subobjects. We are aiming to tag our first RC in two weeks, and do the actual release two weeks after that. The tracking issue for the release can be found at https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/367 Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SMW 1.9.3 and SRF 1.9.2
Hey SMW devs and contributors, It's been two months since the last SMW and SRF releases. It'd be good to get the improvements made in the meanwhile out to our users. Is there any reason to not release SMW 1.9.3 and SRF 1.9.2 next weekend? I have nothing on my radar so far. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Bug tracking
Hey, Bugs on Bugzilla remain valid and will be treated as they have been before. Moving them to GitHub might increase their visibility somewhat though. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] execute #ask query internally
Hey, > I can see the foto 'column' result in the ask query if I var_dump() the result object, but there is no sign of the image file name in there. any ideas? The result object is very deceptive in that regard, and surprised me as well when I first was in a similar situation. It does not contain the actual result. It pretends to by loading the actual data when it's requested from the object. Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] execute #ask query internally
Hey, Note that Markus his email is 6 years old, some things have changed since then :) On a conceptual level, query printers take a query result from an ask query, and create some visualization for that. At least by approximation, the internal code does some odd things at the moment and some printers do further things. This is however where we want to move, and what we will need to do if we want to share result visualization with the Wikibase project. If what you want to visualize is not the query result of an ask query, then using the result printer infrastructure is not the way to go. I suggest you instead create a parser function that has an interface suited for the task at hand. Once it is clear what the inputs of this function are and what you want to get out of it, we can determine what the most efficient way to talk to the SMW store is. At least for me the easiest way to give the feedback/advise you are looking for is if the code is written up to that point, so there is an unambiguous specification of the inputs. Can you post this for review somewhere? Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Planning the 1.9.2 release
Hey, If you are interested in the planning of the 1.9.2 release, please have a look at https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/263 Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SemanticWatchlist moved to GitHub
Hey, I just moved SemanticWatchlist to GitHub: https://github.com/SemanticMediaWiki/SemanticWatchlist The issue tracker here is enabled and now contains the issues about the extension I found at various places: https://github.com/SemanticMediaWiki/SemanticWatchlist/issues Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Patches for composer-managed extensions
Hey, > If no tags for dev versions exist, take latest released and hope for the best. Good luck. If you want to use a dev version, then use the appropriate branch, such as master. "dev-master" as version constraint. Using tags in this context makes little sense. > Ensure all packages are set to install development versions in composer.json Only the one you want to work on - no need to bother with the rest. For the rest the doc looks reasonable enough. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Patches for composer-managed extensions
Hey, It is pretty much the same as for Wikibase - https://www.mediawiki.org/wiki/Wikibase/Contribution_workflow Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Google Summer of Code: SMW projects wanted - Properties Edit-Tables
Hey Hans, This is a much discussed idea actually, which has been talked about on the mailing lists several times. General in-place result editing is practically impossible as far as I can tell. One can do many irreversible computations (ie max) on results, and the input values can be themselves the result of computations, or non-editable values (ie page creation date). It is thus important to clearly identify in which cases such support is feasible and which ones are in scope of the system you will be creating. An additional complication comes from the fact that the SMW query result and query processing code is not in a very good state. It might be difficult to extend it and use it in other contexts as the current ones, which is what I suspect will be needed (or at least very useful) when doing such a project. So yes, I agree this would be great to have, and if we can get the functionality for at least simple cases, that'd be fantastic. You are right in that this would be quite some task, which I hope I underlined with this mail. When moving forward with such a project, I highly recommend * to communicate with the active SMW devs and other interested parties. Work in a public repo, ask for code review, and design review. * to work in incremental steps. Getting a small amount of solid functionality in a release that can then be expanded is much better then writing a pile of half-working things that never reach usable state. * write tests All these steps are essential in making such a project succeed. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Running SMW master via Composer
Hey, Recently some people, including myself, ran into an issue with running SMW master via Composer. One can specify that master should be used using "dev-master". This does however result into a conflict if you also have an extension to SMW, such as Semantic Result Formats, installed via Composer. The conflict is between that extension specifying they need a version of SMW within a specific range, ie 1.9.*, and dev-master not being in this range. One can change "dev-master" to "@dev" or "*", which fixes the conflict, though then gives you the most recent release of SMW, rather than master. We now have a branch alias for master named "1.9.x-dev", which can be used to get master without running into the above described conflict. This can be used immediately and has already been done on SMW wiki: https://semantic-mediawiki.org/wiki/Special:Version Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SemanticMaps and SemanticExtraSpecialProperties repos moved
Hey, Both the SemanticMaps and SemanticExtraSpecialProperties repos are now at https://github.com/SemanticMediaWiki/ The old URLs will continue to work. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW 2.0 or 10.0?
Hey, 2.0 it is. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SMW 2.0 or 10.0?
Hey, It seems there is general agreement on having the next big SMW release have a semver.org complaint version number. However there are two options that have been proposed and both work: 2.0 and 10.0. The former one increments the first number, changing it from "the meaningless 1 at the front" to be the actual MAJOR version. The later drops the "meaningless 1", shifting the current actual MAJOR version "9" to its correct location, and then incrementing it as should be done with each new major release. I'm fine with both, though need to make some decision. So please indicate your preference. So far we have 1 point for 10.0 from Markus and 1 point for 2.0 from Yaron. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Making SMW semver.org compliant
Hey, > Markus: > the next version should be 10.0.0 Good point. +1 to this. > Alexander: > It is also important to tag all extensions. This is very often not the case yet... At least for SMW you can be sure all future releases will be tagged, since Composer essentially requires one to tag in order to create a release. The same is also true for SRF and Maps, and I hope more extensions will follow. > Yaron: > I can't imagine anyone would object to increasing the version number to 2.0, 3.0 etc. if/when it makes sense to do that. A discussion about the same question occurred quite some time back on wikitech. As you can probably guess, the outcome was rather different. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Making SMW semver.org compliant
Hey Yury, In case of MINOR versions, people know no compatibility breaks where made. This means all versions of MediaWiki and PHP that where supported before are still supported. It also means that no features where removed from SMW, and that existing ones where not modified in such a way that old wikitext will break. Those things can only happen in MAJOR versions. This is a big help to people using the software in determining if and when they should upgrade. Development related compatibility is also part of the picture, though since our primary audience are the users, not developers, that really comes second. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Making SMW semver.org compliant
Hey, > increasing the version number to 2.0, 3.0 etc. if/when it makes sense to do that. The thing is that we have not been doing this. Some of our last major releases contained big breaking changes (DataItems, SQLStore3, Composer, etc), and we did not increment the primary number. I do not expect to ever have changes that are significantly more disruptive than those for any future release. > I don't think avoiding a 1.10, 1.11 etc. is by itself a good-enough reason to jump to the next number Agreed. This is a weak argument for picking the next release to make the change if we decide to do so. It is not an argument for making the change itself. (In fact, you cannot reason like that if you stick to semver.) Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Making SMW semver.org compliant
Hey, I think it would be nice if SMW was http://semver.org/ compliant. This means version numbers would look like MAJOR.MINOR.PATCH with a possible stability suffix. This is very close to what we are already doing, except that we are sticking a "1." in front of it. Having this shifted by one might not be confusing to people familiar with the SMW release cycle, though might be surprising to those who are not. How about switching to this schema for out next major release, which would then end up being 2.0? If we make this switch, the next major release seems like the best point to do this. Coincidentally one advantage to picking this release for such a change is that it makes us skip 1.10, which some users might think is smaller than 1.9.0. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] composer questions
Hey, > Where's the most uptodate list of the extensions that have been migrated to Composer? https://packagist.org/packages/list.json?type=mediawiki-extension > Has the entire Semantic Bundle been migrated? Nope. SMW, SRF, Maps, Validator and Semantic Maps. Other extensions such as Semantic Forms can be happily used together with these. Still, it would be nice if the maintainers of the remaining extensions did the little work needed to make them installable via Composer. > I'm wondering if Composer also equally required for installing Wikidata extension(s) too? As of today it is. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW 1.9 - any blockers left?
Hey Phil, We will as always provide a tarball you can download, extract into your extensions dir, and simply include SemanticMediaWiki/SemanticMediaWiki.php. That being said, it is highly recommended you use the Composer approach when you have CLI access, as it is simply superior in many ways. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SMW 1.9 - any blockers left?
Hey all, This is the last call for SMW 1.9 blockers. If nothing is brought up, I will tag SMW 1.9 on Friday the 3rd. The release notes can be found at https://semantic-mediawiki.org/wiki/Semantic_MediaWiki_1.9.0 Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [Video] Semantic MediaWiki 1.9 install using Composer
Hey, Very nice! Love the tagcloud :) Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [SMW Composer] Extension configuration
Hey, > I had assumed that, but I was getting errors with undefined namespaces (SMW_NS constants) that I was referencing after the (removed) require_once statements. Some changes in SMW where made recently that limit usage of the namespace constants in a way that was not present before. This is an exceptional case and should definitely be documented. It might already be, I'm not sure. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [SMW Composer] Extension configuration
Hey, Composer is "just" a dependency manager. It has nothing to do with configuration. So how config is done in MediaWiki remains unchanged :) Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] MessageBuilder interface
Hey, A while back I created a properly segregated interface for turning message keys into messages. Since I've seen someone create almost the exact same thing, and now ended up needing such an interface in another project as well, I decided to put this into its own little library. https://github.com/JeroenDeDauw/i18n At this time, only msgText is exposed in the general interface, as this is the only thing I've needed so far. This can easily be extended for other use cases though. Just released version 0.1 of this library, which is fully tested, and is installable via Composer. Hope this is of use to some people, and of great amusement to those who do not understand interface segregation and IoC. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] ScrutinizerCI reports
Hey, We once again have ScrutinizerCI hooked up to our git repo, to provide code quality reports based on several of the standard tools for obtaining such metrics for PHP code. https://scrutinizer-ci.com/g/SemanticMediaWiki/SemanticMediaWiki/ Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SemanticResultFormats on GitHub
Hey, > Is this a replacement of Gerrit or just another possbile way to contribute? As with the SMW git repo, the on on Gerrit remains operational as before. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SemanticResultFormats on GitHub
Hey, It is now possible to contribute to SemanticResultFormats via GitHub! https://github.com/SemanticMediaWiki/SemanticResultFormats This repo is also used to run the SRF tests against multiple different PHP, database and MW version/type combinations. https://travis-ci.org/SemanticMediaWiki/SemanticResultFormats And it is the repo used by Packagist. (Indeed, it is not possible to install SRF via Composer!) https://packagist.org/packages/mediawiki/semantic-result-formats Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] raising composer features
Hey Lists, ok, as far as I understand > > include_once( __DIR__ . '/vendor/autoload.php' ); > > ...is meant to be... > > require_once( __DIR__ . '/../vendor/autoload.php' ); > > ...and autoload.php will resist in wikiroot/vendor together with additional > packages which are not mediawiki-extensions. > > We do not need multiple autoloader.php. > I'm not following you here. If you think there is a bug somewhere, please file it on bugzilla, with steps on how to reproduce it. Well for example if I want to install an extension locally from disk > (zip-archive) into directory extensions I have to change > If I understand your question correctly, then I already answered this in the last paragraph here: http://www.bn2vs.com/blog/2013/11/24/upgrading-an-extension-that-now-uses-composer/ Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] raising composer features
Hey Lists,
> But some extensions are now in wikiroot/vendor others in
wikiroot/extensions
The idea here is that extensions end up in wikiroot/extensions, and all
other packages end up in wikiroot/vendor. This should already be the case
when doing an SMW install. Though not all my packages have been updated to
use the mediawiki-extension type yet, so some extensions might currently be
ending up in wikiroot/vendor, which will be fixed in due time.
What about:
> include_once( __DIR__ . '/vendor/autoload.php' );
>
> Befor I begin to make my extensions composer compatible I want to make
> clear
> what I have to include.
>
> In the entry point of SMW it tries to include autoload with:
>
> include_once( __DIR__ . '/vendor/autoload.php' );
>
> ...but in extensions/SemanticMediawiki resist no "autoload.php".
>
> ...does...
>
> "autoload": {
> "files": ["MyExtension.php"]
>
> ...mean I'am a substitution of "autoload.php"?
>
If you want to make your package installable via Composer, you just need to
correctly specify things in the autoload section, as I described in my blog
post. If you are writing a MediaWiki extension, you do not need to bother
with the composer autoloader, or even really know it exists.
The autoloader is supposed to be included by the package into which the
Composer install is done. In our case this is MediaWiki core (or the
Extension Installer). You thus can provide support for installing
dependencies into a MediaWiki extension, as SMW has been doing for a while.
This supports an entirely different workflow then the one I'm recommending
MediaWiki users to follow though. It is mainly of use to developers. For
instance, you can include the autoloader from your test bootstarp, so one
can clone a project and just run phpunit, without having to set things up
manually. Example:
https://github.com/DataValues/Geo/blob/master/tests/bootstrap.php
By the way after installing subpages in a second turn SMW was uninstalled!
> ;-). Might be because of my composer.json...I replaced the require
> statements.
>
Well doh! If you remove the package from your package list, Composer will
be helpful and clean it up for you next time you run its updater!
Any ideas how to implement partial updates and different repositories?
>
I'm not sure what you mean by this. Can you detail what this functionality
would entail and why it is useful?
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] New documentation on our Composer usage
Hey, I recently wrote two blog posts filling gaps in our documentation, after noticing people kept asking the same questions. The first one is aimed at developers, and explains how to make extensions compatible with, and installable via, Composer: http://www.bn2vs.com/blog/2013/11/24/introduction-to-composer-for-mediawiki-developers/ The second one is aimed at users, explaining how to upgrade from an extension version where Composer is not used, to one where it is. ie from SMW 1.8 to SMW 1.9 beta. http://www.bn2vs.com/blog/2013/11/24/upgrading-an-extension-that-now-uses-composer/ I hope this helps developers in increasing the amount of extensions that can be installed in a nice way, and helps users to test SMW 1.9 beta. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] raising composer features
Hey Lists, If you are getting an error because git is not installed, we, that sucks. I was under the impression Composer would be smart enough to get the code as tarball in such a case. Though perhaps it normally is, and simply cannot do this in your case, as you are likely specifying dev-master (which refers to the master branch on git) to be installed. Two things I suggest trying, that might get around this issue: * add the --prefer-dist flag at the end of your Composer install command when running it. This will get packages as tarballs when available. * rather then using "dev-master" as version, use "*" In any case, I highly suspect that this will not occur when specifying 1.9 once it has been released. You can try installing version 1.0 the SubPageList extension [0] and see if you run into the same issue or not. [0] https://github.com/wikimedia/mediawiki-extensions-SubPageList Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] List composer packages used within MediaWiki
Hey, I had another idea related to the topic of this thread, though technically quite independent from (virtually all) the implementation needed for the other functionality described already. Have an API module that simply serves the composer.lock file. This can be implemented as trivially as reading the file and serving that, or perhaps doing a json parse in between and feeding the array to the MW API thing. In fact, I'd not go further and add additional things on top here, so it stays as simple as it can be for this use case. And if it is this trivial, it might be feasible to get it into MW core. Be warned, whoever implements this might be forever loved by Jamie Thingelstad (Wikiapiary). Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] List composer packages used within MediaWiki
Hey James, Great work! And you beat me to it! I started working on the exact same thing yesterday. You can currently observe the lack of code in my GitHub repo for this [0]. Though what you are currently going is only a subset of what I had in mind. One can retrieve package info from Packagist (and perhaps the other repositories listed in composer.json), which URLs like [1]. This can be used to enrich the information of installed extensions (and perhaps other packages as well), in particular with what the latest version is. And when we know there is an update, we can actually show an update button, that when clicked, causes the corresponding composer command to be executed. Furthermore, we do not need to limit this to updating. We can display a list of available MediaWiki extensions that are not installed yet. A list of MediaWiki extensions can be obtained from Packagist via [2]. So I'm imagining having a "installed stuff" page, with tow sections: first extensions, then libraries. A second page would be for "stuff that can be installed". Perhaps this can be on the same special page but use tabs? That question is getting a bit to UI for me. At this point there is no way to filter by supported MW version, or to specify this in the page definitions to begin with. I plan to investigate this, though good if someone gets it done before me. The two API urls from Packagist listed [1, 2] I got from the Packagist maintainer after chatting with him. They are not documented, though are supposed to be stable. Furthermore there is no way to get package info in batch now, the .json urls need to be hit one by one. Since MW 1.22 is going to ship with the barest beginnings of Composer > support, I think we should extend Special:Version to support this. > > For now, though, we can add hooks -- do you have any suggestions? > If you go for what I just described, which I think we should (and if people disagree, I'll be hacking up a proof of concept regardless), then putting this all on Special:Version really makes no sense. Special:ExtensionManager is what I came up with. Having an additional list there might be nice, and can be done without to much hassle, at least technically. There are quite some core people screaming murder at libraries like Diff showing up on Special:Credits (though being cynical about it, I'd not be surprised if they where actually just upset about my name being there) already, so I'm with James in thinking that attempting real integration here is likely to result in a lot of wasted time and effort. Perhaps it is more worthwhile to, when a nice little initial implementation of extension management stuff on top of Composer is done, try getting that extension bundled with core by default. In this case I figure putting it in core even makes sense, as it is functionality one almost always desires. That means adding new clean code to core though, which is like locking an insentient person in a jail with some big bloke criminals. Poor code. James: I outlined these ideas here in part so you could go ahead and do more awesome stuff already. I might be able to get to poking more at this tomorrow evening, though quite possibly only on Thursday. In any case, I'd appreciate a heads up if you want to poke at any of the additional stuff described, so we don't end up doing the exact same work there. I'm thinking the functionality should be in the same component/repo, as it has quite high cohesion and makes sense together functionality wise. Even if you already end up implementing all of the things to be done here functionality wise before I can get to it, I'd still like to contribute by improving some things in the code. Like fixing some of those annoying naming issues you currently have in there, mostly without even bothering you about them :D Also, did you steal [3] from [4 and 5], or is this an instance where we where also thinking the same thing, but I won the implementation race? This shows clearly that the lack of decent interfaces in the i18n "component" provides by core is a general issues for anyone working on top of MW. I think a component that does the same for i18n as what WikibaseDatabase did for db interaction is in order. I was planning to create that as soon as I ran into the need of [4], [5] or similar somewhere else, though again, if someone beats me to it, great. [0] https://github.com/JeroenDeDauw/ExtensionManager [1] https://packagist.org/packages/mediawiki/semantic-mediawiki.json [2] https://packagist.org/packages/list.json?type=mediawiki-extension [3] https://github.com/mwjames/composer-packages/blob/master/src/ComposerPackages/TextBuilder.php [4] https://github.com/JeroenDeDauw/WikibaseQuery/blob/master/src/Wikibase/Query/MessageBuilder.php [5] https://github.com/JeroenDeDauw/WikibaseQuery/blob/master/src/Wikibase/Query/MessageTextBuilder.php Chee
Re: [SMW-devel] A list of suggested developments for undergrads to try?
Hey Steve, I've written up the relevant info I could think of for this task, which can be found here: https://semantic-mediawiki.org/wiki/Roadmap/Ask_wikitext_parser_and_formatter Let me know if anything there requires clarification. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SRF JitGraph
Hey Richard, This sounds interesting! The next release of SRF is scheduled for next month, so if this is still to get in before then, we need to be somewhat quick. (And not wait 8 days before replying to an email!) The typical workflow is to submit a patch, as a commit in our code review system [0]. Alternatively I can provide you with a GitHub repository to which you can submit a pull request. Once your changes have been submitted, we can review them, and work with you on any compatibility, or other, issues. [0] https://www.mediawiki.org/wiki/Gerrit Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Ask 1.0 released!
Hey, Hopefully writing result formats will become even easier > and more pleasant task! > Hopefully it will yes! Though this will not be brought with using the Ask library, as the technical issues faced there are mostly disjoint from the Ask language. That being said, having a nicer implementation of the Ask language is likely to help facilitate a new class of result formats, much in line with the AJAX stuff recently written about. What do you think to do with growong number of dependencies of SMW? > These will not bother the users as they currently due, since SMW will be one of the first MediaWiki extensions to support a real dependency manager. More on that will be announced in due time. It seems that by SMW 1.11 we're going to need to install Validator, > DataValues, Ask > SMW 1.9 has been needing all of those, except Ask, already for quite some time. Maybe we should pack SMW tarball with these extensions? We definitely should, and have been doing this since SMW 1.6 or 1.7, I can't quite recall. By the way, are there any other MW extensions that also use Validator > and/or DataValues? > Yes. Validator is used by Maps and SubPageList, amongst others. DataValues is used by Validator, and by many of the Wikibase related components. I'm hoping to have automatically generated lists of these package consumers available in the coming month. This is now possible due to having actual package definitions ans using public package repos. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] How do I get this version
Hey, As the page notes, you need to have SRF 1.9, which has not been released yet. This will happen shortly after or together with the SMW 1.9 release, which is scheduled for next month. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Ask 1.0 released!
Hey John, > Any discussion which version of smw is expected to have this common library There is no discussion about this, as quite some work needs to happen before we can use Ask in SMW. All I can provide is a guess for the first release in which SMW might realistically be using this library, which is SMW 1.11. That is all assuming we manage to stick to our release roadmap this time. > I assume it's the same syntax as before, minus subobjects? This library is a set of entities that represent data and contain some business logic. It does not define syntax. When SMW adopts this library, it can retain its current wikitext parsing and formatting code. Though I hope this code will have been rewritten by that point (without functional changes), as it is very much legacy code as well. A library build on top of this new one provides the serialization and deserialization code for the Ask language that will be used by the Wikidata project. This could be used in SMWs web API instead, or as addition to, the wikitext serialization of Ask. A release announcement of this will follow hopefully soon. https://github.com/wmde/AskSerialization Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Ask 1.0 released!
Hey all, I'm happy to announce the initial release of the Ask library! A small write-up of this release can be found at http://www.bn2vs.com/blog/2013/11/17/ask-1-0-released/ The library itself and its documentation resides at https://github.com/wmde/Ask Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] ajax=true - thinking about new global parameter for all Result Formats
Hey, 2) could such feature be implemented in SMW core, that is: for all > result formats? Or must we add these parameters to every result format > separately? > I'll answer this question from the technical side. Not every format supports this functionality and this is also not going to happen. (Forcing them to do is makes little sense.) Thus having a global parameter that "does not work" for a lot of the result formats is rather awkward. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] A list of suggested developments for undergrads to try?
Hey Steve, Do you need a small writeup of the ask query language parsing task? I'd be happy to create this if it is likely your students will be working on it. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] making result format compatible with more versions of SMW
Hey Yury, If you use the array based syntax currently used by SMW and SRF, then it should be mostly compatible with Validator 0.5 (and thus SMW 1.8). IIRC most result printers in SMW 1.8 already got updated to use this definition style. I can't give you a better answer then that. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] ASK Query for added Special Properties
Hey, Yes, this query is supposed to work on the current version, at least if you add the closing ]]. Are you sure you ran both the schema update and data refresh scripts? Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] A list of suggested developments for undergrads to try?
Hey, With regards to the objective to engage in OO and design pattern > development, Semantic Results Formats does have several design issues > (misuse of inheritance, violation of SRP etc.) which are rather > counter-productive to the stated objective. > I second this. SRF is not suited to learn students how to something well. The same holds for MediaWiki and SMW. We are working on removing the later from the list, though it is not there yet. So, do you have specific ideas that come to mind? > How about creating a fresh implementation of our wikitext ask query parser? This would be fairly self contained and can be done without touching the existing implementation in SMW core. When its ready it could then be used to replace the existing implementation, though this step would likely be out of scope. This can be developed without knowledge of MW or SMW (expect Ask queries), and requires neither to be installed. Implementation would start from scratch, though one can look at the existing one in SMW. The people doing this can thus experiment with several designs, do not have to bother with unrelated code, and work on top of well designed code, rather then the typical example of legacy code. The role of this parser would be to turn an ask query definition in wikitext into the corresponding PHP object definition. The input would thus be something like [0] into a Query [1] object. This is something that needs to happen at some point before we can implement related new functionality. So it'd be very helpful if this item was tackled for us. The item is rather smallish, and perhaps to small to fill the course. Additional things can be done on top however. If this sounds good to you, I'll describe it a bit more on a wiki page and link to the relevant resources. [0] http://pastebin.com/mHNvf3yw [1] https://github.com/wikimedia/mediawiki-extensions-Ask/blob/master/src/Ask/Language/Query.php Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW 1.9 entering beta stage - error
Hey Neill, You probably have a to old version of DataValues. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] RFC: Technical documentation, installation instructions and release notes
Hey, We have been both shipping documentation together with the source code (as text files) and providing it on the SMW wiki since I joined the project. I see some problems with this. If the documentation is at both places, it doubles the maintenance effort. Given we have quite little resources to spend on this already, this does not help the quality of the documentation in question. Looking at the docs bundled with the source code, it seems that a lot of it is quite out of date, incomplete and sometimes plain wrong. A more focused effort seems to be in order. I propose that for the following items are only bundled with the source code and not duplicated elsewhere: * Release notes * Core installation instructions * Technical documentation on our APIs (and no, I' not talking just about our web API) If this is bundled with the source code, we can keep it fully up to date the whole time. If someone adds a new feature, they should also update the release notes. If someone changes an API, they should update the documentation. Relevant buzzword: "Agile documentation". Another advantage comes from the documentation not just being up to date with the latest development, it's also always correct for the version of the code you have. So if you get the previous release, you'll have the correct documentation for it, rather then something that reflects all the development that happened since. Yet another plus of having this together with the source is that people are not forced to hit our wiki. Offline use is possible. And it's just nice to have this in git together with the code, so no additional infrastructure is needed or relied upon. The SMW wiki would not contain a copy of this documentation. It can refer to it, and it can expand on it. Or provide translations. Technical tutorials, full installation guides and so on would also remain on the SMW wiki. What needs to happen to get there? We already made most of the change, just not explicitly. The biggest violators of this policy where the release notes, and our API documentation. The release notes for 1.8 where actually already referenced from the SMW wiki at some point, by embedding the contents of the file from our git repo in the wiki page [0]. And we now have some documentation on our APIs in the "docs" folder, written in markdown format. Making such a change more explicit means that it is clear the documentation bundled with the source should be updated timeline. It also makes it clear no effort should be spend in duplicating it on wiki. I've been following such a practice myself for several other projects and am quite happy with it. Examples: * https://github.com/wikimedia/mediawiki-extensions-SubPageList * https://github.com/wikimedia/mediawiki-extensions-Diff Feedback is welcome. [0] This is no longer the case as this broke due to WMF breaking the URLs via which our source could be accessed. That has been resolved in the meantime, so we can use this model again for the 1.9 release notes. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] SMW 1.9 entering beta stage
Hey all, Semantic MediaWiki 1.9 is now entering the beta stage, in preparation of the actual release somewhere next month. During this period we will mainly be working on making this already awesome release even more shiny, and making sure everything works as expected. No big new features will be added, and no compatibility changes will be made. Now is the time to try out SMW 1.9 on your test system, and to tell us about any issues you run in to that could prevent you from upgrading to this new release. You can get the code via git, by either getting the master branch, or the 1.9beta1 tag. Alternatively you can get one of the tarballs: * https://github.com/SemanticMediaWiki/SemanticMediaWiki/archive/master.tar.gz * https://github.com/SemanticMediaWiki/SemanticMediaWiki/archive/1.9beta1.tar.gz Preliminary release notes can be found at https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/RELEASE-NOTES-1.9 Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] TravisCI build time reduced
Hey, There where some concerns that the TravisCI build time was quite high, and that it would prove to be problematic for reviewing pull requests on GitHub. Looking at our first build for the new GitHub repo, it indeed took nearly 14 minutes for the build to finish. https://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/13407139 (Note how the tasks run in parallel, and the "duration" is the sum of the task running time, not the time passed between build start and end.) After some optimizing this is now down to a bit under 4 minutes. https://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/13465816 Once the TravisCI people tackle the following "issue", we can get it to under one minute: https://github.com/travis-ci/travis-ci/issues/1587#issuecomment-27673516 Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Initial GitHub support arrived!
Hey all, We now have a copy of SMW on GitHub which I'm maintaining and to which you can submit pull requests. https://github.com/SemanticMediaWiki/SemanticMediaWiki This is an additional repo - we do still also support contributions via Gerrit. The GitHub repo will be kept reasonably up to date with contributions submitted on Gerrit, and changes will also be propagated in the other direction. I hope this makes things easier for a lot of you, and helps bring more contributions to the awesome platform that is SMW. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Moving SMW development to GitHub
Hey, > To me it seems that the coordination of two source control tools seems to be a lot of work. We already have multiple copies of the repo. Every clone is a copy of the repo. GitHub will just be another copy. Furthermore there is little difference between changes on a branch on a remote or changes on a branch of your local box. The workflow is nearly identical. You could take the stance that branches are evil and that there should only be a single holy master branch, though then you are doing the git thing wrong. I'm confident enough about this to take ALL of this work on me personally, so its a non issue. > Niklas worried about the delay this could introduce If we sync once a week (and we can easily do more), then this will not be much different then the delay of translations for a branch that exists for more then a week. And the syncing problem is very theoretical at this point. We should pay attention to this if a lot of development happens via the GitHub repo. If we simply accept patches to be submitted there, the number of merges ought to be rather low, and we can easily push to the WMF repo after every merge. So NO delay. > and Nischay worried (like others at SMWCon) about the confusion of having some extensions here and others [there]. Confusion from which perspective? The developer contributing to the code, or the user using it? In either case, I again do not see any real issues if we handle this sanely. The existing support stays as it is for both groups, so no one is forced to change anything. We just add an additional capability. One which can be used by those who ARE (currently, very much non-theoretical) confused by Gerrit and the WMF workflow. > If we had an automated synchronisation of GitHub and Gerrit, then the advantages would combine and the disadvantages would vanish, right? The automated synchronization could save some work at some point. However as I already indicated, I'm quite happy to be this automation for now. I don't think it makes sense to invest a lot of time into additional infrastructure while no clear need for it has been demonstrated. So yes, to some extend this will leave us with the best of both worlds. It's not completely the case we get rid of all disadvantages in the current setup if we use both systems, though those are significantly less important then supporting contributions via GitHub. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Moving SMW development to GitHub
Hey, Thanks all for your feedback. Since there is apparently a good degree of apprehension on changing this workflow, which is not all to surprising, I'll slightly alter and reframe the proposal. Rather then "switching" to GitHub, we'll just have the new repo on GitHub via which we access pull requests. The workflow on the WMF hosted repo does not change. If things go well, we can gradually move more activity to GitHub. Below I'm addressing some raised questions and concerns: > Are there similar plans for the SMW-related extensions? It is really up to the maintainers of those extensions. I'm quite unhappy with the one-size-fits-all attitude that is quite prevalent in the MediaWiki community. In some cases it makes sense to provide support via GitHub, in others only accepting contributions via Gerrit is the better approach. I personally have no concrete plans for extensions such as Semantic Maps at present. If SMW benefits from this change, then I'll of course be considering it. For the Wikidata project, we are moving several PHP libraries to GitHub, some of which are SMW related. > Wouldn't it be confusing if some work is on Gerrit (MW and many other extensions) while SMW work is on Github? The number of potential SMW developers that are using GitHub is significantly greater then the number of MediaWiki developers. And as we have clear empirical evidence by now, the later group is not very eager to contribute to SMW, so why should we throw the former, under the bus? Most interest in SMW is coming from outside the core MediaWiki community, and for them the current workflow is not only confusing, it is a big hassle. > Also worth noting would be Yuvi's Github to Gerrit Bot http://www.mediawiki.org/wiki/User:Yuvipanda/G2G Relying on this mirroring infrastructure strikes me as added complexity and more maintenance hassle. The fewer infrastructure that can break in such a way it seriously obstructs the development process, the better. > Will it speed up the review process in some way? :-))) Not initially. However if we get more people contributing, this situation could improve. That is all very speculative however. > This sounds like a potential for a mess, merging stuff into both directions. Git is a distributed version control system. Distributed. In the end there is little difference between having a branch on a repo hosted on GitHub or a branch on my local box. The kind of merging that will happen will not differ much from what already happens. The tree might get deeper and more complex if people start creating forks and whatnot, though again, this is what Git is made for. I anticipate no hassle whatsoever for i18n updates, as they will still come from one source, which is the same as our current situation. > From my point of view, you would lose visibility of development Ah, this is part of the promise that everything will be so much better if one uses a WMF hosted git repo. As I already implied above, this promise fails to deliver. This is the case for SMW, and for most extensions. There might be exceptions, though that does not help us. pre-testing (some of the extensions) at translatewiki.net as well as > having new releases with fewer translations, because translators have > less or no time to translate new strings. With this scheme it can take > two releases to fix an i18n problem and having a good translation for > it (fix in next release, translations in next+1 release). > Doing a push from one repo to another is not very difficult, so we can frequently update the WMF copy of the code, and not lose the TWN testing. Also note how this proposal does not include extensions. Translations are important and we should certainly not throw them under the bus. Luckily we do not have to do this in any way even if we were to move all development to GitHub. Ideally TWN would directly support repos not hosted on WMF git. There are already many MediaWiki extensions hosted only on GitHub, which are now essentially treated as not being good enough. > rising barriers elsewhere How does SMW doing part of its development via GitHub and accepting contributions via it make things elsewhere more difficult? Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Moving SMW development to GitHub
Hey, After discussions with the active contributors to the SMW project and asking attendees at last weeks SMWCon, I'd like to propose moving SMW development to GitHub. == Details == The canonical git repo would be at https://github.com/SemanticMediaWiki/SemanticMediaWiki Trusted contributors get merged rights and can review pull requests, or directly push to a branch. All other contributors can fork and create pull requests. Pull requests should only be merged when TravisCI reports the tests passed. This is very similar to our current setup. It's different in that we have more autonomy, people can more easily contribute without having to learn gerrit and we do not have to deal with WMF infrastructure that is not of use to us. The current canonical repo would be kept where it is and become a manually updated mirror. If people submit patches against it, we can still review those via gerrit or redirect them to GitHub as we see fit. Since TranslateWiki does not support GitHub at present, we'll have to periodically merge the translation updates from the WMF repo to the GitHub one. People will thus continue to be able to use a clone of the WMF repo, which will at the very least be updated for each release. == Plans == I'll set up the repo and update the configuration of services such as TravisCI, Packagist, Scrutinizer and coveralls.io accordingly. I'll also assign rights and whatnot. If no one of the core contributors screams murder, or someone else points out a real issue with this approach, I suggest we officially switch to this model next week. In case problems occur that cannot easily be dealt with, we can always delay or abort this altogether. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Query result rewrite
Hey, I figured that I do not have enough time to do this nicely integrated with SMW. Both the query result objects and the result printers are best rewritten from ground up to get rid of all the big issues. And while doing this, future interoperability with Wikibase could be achieved. Out of scope for preparing this workshop though. I ended up creating a bunch of simple objects and a converter from SMWQueryResult to those, which will be used during the workshop. https://github.com/JeroenDeDauw/CheckedTable/tree/master/src/SMW/Query/Result An actual rewrite in SMW can presumably continue based on this initial work. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Query result rewrite
Hey, The point of this workshop is not to teach people SMW interfaces. The amount of ground that can be covered in a one hour workshop aimed at beginners is rather small. So however this is done, people will still not know nearly all interfaces. So even if it was the case that this was likely to change, which it is not, I'd not see it make much of a difference. People still get to learn the workflow and they still get to learn how to find things out while creating an SMW extension, which is the whole point. If you have a suggestion for something that is not a result format that could be created as part of the workshop, and that interfaces with code that does not prevent writing tests for the new code, then I'd be happy to hear about it. There is the Ask library, though that is likely to abstract for much of the audience. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Query result rewrite
This will exist when I give the tutorial. Are you saying that it should be in a released SMW version first? Sent from my HTC one X. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Query result rewrite
Hey, While working on my dev workshop for SMWCon, I noticed it is currently rather impossible to write a sane unit test for a result format. The reasons for this are that the result object, SMWQueryResult and the objects it is composed of, contain a ton of stuff not relevant to those tests, including database access to get the actual results. I figured it'd be good to have a cleaner interface that can be used by new code, and demonstrated in the workshop. So I'm now working on creating a fresh implementation of the result objects, that will be available as an alternative to the current way of doing things to result printer authors. In other words, this will not be a compatibility breaking change, the current approach will remain usable for the foreseeable future. This is just a heads up I'm going to work on this, no real work has happened yet. I'll be linking the code here as soon as there is something substantial to look at. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] The future of the SMW query stores
Hey, Wikidata integration. If I'm not mistaken, there was talk of WikiData and > SMW ultimately "joining" together in the indeterminate future. Perhaps, > this could be the start of that process as some of these issues may have > already been considered by the WikiData team. > The actual topic of my email, which got completely ignore so far in favor of discussing MongoDB vs $AlternativeStore, is very much about interoperability with the Wikidata software. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] how to know the validation option for the parameters in SMWResultPrinter::getParamDefinitions( )?
Hey Yury, The docs here where already updated a little: https://github.com/wikimedia/mediawiki-extensions-Validator/#implementation-structure > saw a lot of interesting fields in SMWParamFormat Do not use SMWParamFormat as an example, its using highly deprecated code. Try to stick to using the array definition syntax. Creating actual instances of ParamDefinition is discouraged. Deriving from ParamDefinition (as SMWParamFormat does) should not be done in new code. The array definition schema currently does not support specifying validation callbacks. Validation is typically done by specifying a parameter type, such as integer, which then makes sure the values is valid for that type. You can define your own parameter types, see Validator/config/DefaultConfig.php, which allows specifying a validation callback per type. If the validation is not actually validation but making sure the value can be interpreted, and thus part of the parsing process, then you should specify a parser instead. The basic array definition format is not going to break, and neither is the result object structure you get back from the processor. Other things might well be broken as ParamProcessor moves towards a better (and more stable to the outside) design. So only do the more advanced things if you really need to. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] The future of the SMW query stores
Hey, The last release introduced SQLStore3, a partial rewrite of SQLStore2, improving on the performance of its predecessor. That is not the end of the story for the SMW query stores though. This email was prompted by work MWJames is doing in supporting MongoDB \o/ https://gerrit.wikimedia.org/r/#/c/88534/ For a while now, there have been two items on our Roadmap about utilizing new libraries I created for the Wikidata project, that are both based on, and usable by, SMW components. * https://semantic-mediawiki.org/wiki/Roadmap#Make_use_of_DataValues_library * https://semantic-mediawiki.org/wiki/Roadmap#Make_use_of_Ask_library There now is a third such component, which might enable us to get a nice improvement to our SQLStore without all to much effort. I described this here: https://semantic-mediawiki.org/wiki/Wikibase_QueryEngine This is still quite far off, assuming no one else jumps on it, given that it requires the earlier two items to be finished first. Feedback on the idea is however welcome. And awareness of these preliminary plans, or rather possibilities (I'm not committed to doing this at this point), is good for those doing or planning to do something related to the SMW storage infrastructure. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] how to know the validation option for the parameters in SMWResultPrinter::getParamDefinitions( )?
Hey Yury, This is unfortunately not properly documented, and as with a lot of MW code, the answer is, at least for now, "look at the source". This is certainly not a good answer and something that should be addressed. Rather then answering in detail here, I'll be adding documentation incrementally to the README file of Validator with the aim of having the basics covered there by the time of its 1.0 release, which will be shortly before the SMW 1.9 one. The README can be seen here: https://github.com/wikimedia/mediawiki-extensions-Validator/blob/master/README.md Some quick replies: > What values can I use for the values of the key 'default'? Anything. This is self defined. > Where did these words 'message', 'values', 'default', 'aliases' come from? This is the definition format in array form as defined by Validator. > Are there any other interesting words to use (for example 'mandatory' would be nice or 'type')? There is a type field. A param is mandatory if it does not have a default. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SMW + Selenium
Hey, If these tests are broken and no one is maintaining them, I suggest we remove them from master. They can be resurrected from version history if anyone cares to fix them. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] SFFormLinker::setBrokenLink is doing what?
Hey, There's a setting you can use, $ > sfgRedLinksCheckOnlyLocalProps, that, if you set it to true, makes it so > that setBrokenLink() checks only the properties defined on this page, > instead of all properties across the wiki. It makes the whole thing less > effective, but it should reduce the running time considerably. > So what is the difference in queries that get executed? I'm not sure what is happening exactly, though suspect that even if you do only local props, a decent chunk of the cost is still there. If that is the case, being able to fully disable it might be quite useful for certain people. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Delaying SMW 1.9
Hey, [0] < > https://github.com/wikimedia/mediawiki-extensions-SemanticMediaWiki/blob/master/RELEASE-NOTES-1.9 > > > doesn't really reflect the current status as it lags behind but it has > also the lowest priority in terms of updates > Personally I'd like to see the release notes be kept up to date continuously. It is quite difficult to find all the things that should go in there at the point of release, if some of these things where done a year before. In my experience its easier as a developer to add the things in there either together with the feature, or in a commit soon after. If the file is kept up to date, it also allows users of the alpha to easily check what changed since the last pull they made. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] ArrayAccessor
I'm not against wrapping an array. My concern with the current approach is
that it exposes all lot of not needed methods that replacements will have
to implement. Simply implementing iterator would be better then deriving
from arrayobject. At least when the actual class is being passed around
rather then an interface such as iterator.
Sent from my HTC one X.
On 8 Aug, 2013 4:04 PM, "James HK" wrote:
> Hi,
>
> ArrayAccessor is used in several classes[1] to conveniently access an
> array through object methods. Of course one could make use of the
> ArrayObject directly but one would need to implement the expectation
> handling individually for when an expected element is not accessible.
>
> Accessing an array "blindly" by the means of checking things manually
> like if ( isset( array[$key]) && ... ) {} where ArrayAccessor or
> ArrayObject allows to focus on the task of accessing a value
> $this->has( $key ), $this->get( $key ) instead of checking its
> validity and later try to gain access.
>
> I'm not a fan of having something like array( 'beAKey' => 'beAValue' )
> being transferred beyond an object that invokes the array. An array
> that communicates to the outside of its own instantiation should be
> encapsulate in an object that carries the array.
>
> >> And when one does not need it, it is better to not have it, and stick
> with the simplest implementation possible.
>
> If we don't want to use ArrayObject, I might have to create a similar
> object handler, as I said before doing array( 'key' => 'value' ) by
> "hand" creates all sorts of problems which starts with the validation,
> raising exception, and retrieving of its value.
>
> >> The get method of this class is throwing an InvalidArgumentException
> Fair enough.
>
> [1] Settings, MockObjectBuilder, Collector, ApiRequestParameterFormatter
>
> Cheers
>
> On 8/8/13, Jeroen De Dauw wrote:
> > Hey,
> >
> > I'm not sure what the use for the newly introduced ArrayAccessor class
> is.
> > It seems to not be providing a lot of functionality on top of
> ArrayObject.
> > And I found that one rarely actually needs the functionality ArrayObject
> > provides. And when one does not need it, it is better to not have it, and
> > stick with the simplest implementation possible.
> >
> > The get method of this class is throwing an InvalidArgumentException
> when a
> > non-existing element is requested. This is wrong, as the provided
> argument
> > is not invalid. An OutOfBoundsException would work.
> >
> > Cheers
> >
> > --
> > Jeroen De Dauw
> > http://www.bn2vs.com
> > Don't panic. Don't be evil. ~=[,,_,,]:3
> > --
> >
>
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] RFC: SMWPageSchemas in SMW core (1.9)
Hey, Yaron, I disagree with some of the points you made here. However taking a step back from this, perhaps its not worth bickering about what is really the best thing to do here if all else where perfect already. Though there is room of improvement here, it hardly seems urgent, and quite far down the priority list. So my vote actually goes for leaving it as it is, and concentrating on more critical todos. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] RFC: SMWPageSchemas in SMW core (1.9)
Hey, > I can think of a number of things that SMW does, unrelated to its core goals: SMW core could indeed be more lean. Now, maybe the right solution is to split off all of this extra stuff into > one or more other extensions, as was done with DataValues (and perhaps with > Diff and the rest - I don't know if those started out as SMW code). > Diff is not related to SMW in any way. DataValues is based on SMW code though not yet used directly by SMW. That is something planned though. > Personally, though, I think the better solution is to just view SMW as an extension that does a lot of things, in the back-end and interface, related to the storage of semantic data. It is important to differentiate between the developer and the user views on this. From a development perspective it makes a lot of sense to have these things nicely kept separate. >From a user perspective certain combinations of packages tend to be desired. This is why software tends to have a build process, so the selection of functionality needed by the user can be put into an easy to use bundle that appears to be one piece of software to the user. And since different users have different needs, you'd typically have a few variants of this. For instance "SMW core" with just the core stuff, "SMW plus forms and related stuff", and "ALL of the SMW things". Right now we are not doing an as good job at providing such things as we could. SB is a step in the right direction, though still far from what we could have. >From a dev perspective it is important to keep district things separate, to avoid not needed dependencies creeping in, and to reduce maintenance costs. Since we have not all that much manpower for maintenance, we should be very careful about this. Some factors that are relevant in determining if something should go into SMW core are size and code quality. In case of the Admin Links hook, which is just a few lines of simple code, there is not all that much reason to move it out. There is more PS code though, and it is more complex. Plus it has design issues which combined with the lack of tests make it a liability. In the case of the PS code, I'm not convinced that having a "PSSMW" extension would be to much of an issue even without improving our current build and publishing process. After all, there are many much smaller MW extensions out there. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] RFC: SMWPageSchemas in SMW core (1.9)
Hey, > Wow... I don't know if there's ever been such quick consensus on a topic on this list. Yes, you have won of badge of some sorts :) > I'm not even sure what a "global plan" is. :) Ah, of course you would deny your secret plans to take over the world, and then install SMW everywhere. > But on the other hand, I think changes to the data structure are likely to happen on a much more frequent basis than changes to the Page Schemas API. This might be true. However if you look at what is actually happening, nothing of this nature has changed since the introduction of the class. >From an SMW maintenance perspective, it is not nice to have this code in there. And having this "semi dependency" on PS makes things more fuzzy for both users and devs. A third option is to have a PSSMW extension that depends on both SMW and PS, and contains the code in question. This of course comes with its own set of tradeoffs. Presumably one such extension can be made to hold PS all code for SMW and SMW extensions. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] ArrayAccessor
Hey, I'm not sure what the use for the newly introduced ArrayAccessor class is. It seems to not be providing a lot of functionality on top of ArrayObject. And I found that one rarely actually needs the functionality ArrayObject provides. And when one does not need it, it is better to not have it, and stick with the simplest implementation possible. The get method of this class is throwing an InvalidArgumentException when a non-existing element is requested. This is wrong, as the provided argument is not invalid. An OutOfBoundsException would work. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] RFC: SMWPageSchemas in SMW core (1.9)
Hey, I concur with James on the points he made. The approach taken would make more sense if SMW was a plug in to PS, as this is what the code makes it out to be. I'd rather see the code be part of PS, and have it only be registered there is SMW is loaded. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Coveralls.io support
Hey, Our TravisCI builds [0] now run code coverage and report the result to coveralls.io [1]. This makes it easy for anyone to view the current coverage level, and to keep track of evolution over time. You can even see coverage changes per file per commit. [0] https://travis-ci.org/wikimedia/mediawiki-extensions-SemanticMediaWiki/builds [1] https://coveralls.io/r/wikimedia/mediawiki-extensions-SemanticMediaWiki Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] [SRF] Filtered Format and PHP upgrade
Hey, I'm not using this format and there are no tests for it, so have no idea what the issue is. It is however strange that upgrading to a minor new version of PHP would cause it to break. I suggest you file a bug report on Bugzilla [0] with a description of the issue, how it can be reproduced, the versions of the software you are using, etc. [0] https://bugzilla.wikimedia.org/ Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
