Hi,
Huggle 3.4.0 will release in few days I guess and it would be nice to
have some beta testing done before it happens, there is number of
major changes:
== Modular design ==
Huggle is no longer 1 monolithic binary, but a set of libraries, that
is needed for future new designs of apps build on top of huggle core
(bots) or new UI (phones?)
That will not be visible to end users other than that it could cause
some issues with packaging or distribution, so installers need to be
verified if they work properly
== New scripting ==
Python support was removed entirely and replaced with JS extension
system - it's now possible to very easily write JS extensions to
Huggle, I will write more docs on wiki, but for now menu Scripting ->
Manager -> New will show you a template extension, it's possible to
create extensions right in Huggle.
This is a very important and probably biggest change in 3.4.0
== Lot of refactoring of existing code and large amount of bugfixes ==
There was lot of weird old code that was refactored to work better and
many bugs related to this code fixed, but it's also possible that new
bugs were introduced?
== No more Qt4 ==
It's deprecated and no longer supported, shouldn't be a big deal.
== Better support for MacOS ==
Lot of code was refactored to work way better on Macs
== Packaging related: 3rd libraries upgrade ==
New Huggle ships with newer yaml and Qt library versions, will be
probably shipped with Qt 5.10 or 5.11 on most platforms
If you want to help with testing, you can either build huggle from
source code on Linux, or download nightly build for Windows here:
https://petr.insw.cz/huggle/nightly/huggle3.zip
Don't forget to open phabricator task for any issue you may find!
Hello,
Hackathon in Barcelona is coming next month, and there are some things
I would like to get implemented into next major Huggle update:
* Drop for support of Qt4
Qt5 has been around for long time and Qt6 is coming. Nearly every OS
is already supporting Qt5 these days. If there is any substantial need
to still support Qt4, please let me know, but I believe that it's not
really needed.
* Drop existing Python engine
Huggle supports extensions created in Python language, but this
feature was never very popular, or widely used. Let's drop it.
* Implement JS engine through Qt5+ QJSEngine
New scripting backend that could be used to allow people create their
own extensions to Huggle. Qt5 supports quite powerfull scripting
engine that can be easily implemented.
I would like to focus on these 3 things during the hackathon. If you
have any opinions on this topic, please let me know!
Also, if you are attending hackathon this year and want to
participate, you are welcome, just find me there!
Hi,
I just released new version of Huggle, about 2 days since last release
because I found that IRC feed in last version was broken due to update
of libirc. Now it works OK, but version 3.3.4 may stop working when
XmlRcs provider breaks as it falls back to defunct IRC feed.
This seriously impacts the functionality of whole Huggle, this new
version fixes the problem.
Hi,
I just released Huggle 3.3.4, there was about 92 commits made since
last release, mostly very minor changes, like some GCI localization
related tasks and some minor bug fixes.
This release for Windows was compiled using MSVC 2015 unlike previous
builds, which were created using MSVC 2013. That means I also had to
upgrade vcredist packages and I have no idea if it's going to work
without any issues. (I don't know why but my MSVC2013 compiler stopped
supporting c++11 after some updates, so I decided to switch to newer
compiler).
This change made the windows installation packages larger by almost 10MB.
Other OS shouldn't have any issues. Packages for MacOS will be built
by Rich Smith later.
Thank you
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Nov28 to Jan17 and is not only about coding tasks.
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has small design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Also note that "Beginner tasks" (e.g. "Set up Vagrant" etc) and
"generic" tasks are very welcome (e.g. "Choose & fix 2 PHP7 issues
from the list in https://phabricator.wikimedia.org/T120336 ").
Because we will need hundreds of tasks. :)
And we also have more than 400 unassigned open 'easy' tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Would you be willing to mentor some of those in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Check
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and please ask if you have any questions!
For some achievements from last round, see
https://blog.wikimedia.org/2017/02/03/google-code-in/
Thanks!,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Hi,
In order to make life easier for newbies, or people who don't want to
struggle with setup of development environment so that they can
compile Huggle, which is essential for contribution, I created this
portable VM that is based on Ubuntu and has complete dev environment
preinstalled, with all dependencies.
You can try it here: http://tools.wmflabs.org/huggle/files/huggle.ova (3GB)
I am going to prepare some how-to for people who don't know much about
linux, but if you do, you will find it very easy to use. Huggle is
preinstalled together with source code, link is on Desktop.
If you open QtCreator (link in side bar) you can just click open last
project and you will get to preconfigured IDE for Huggle development.
You can simply hit build all to compile everything, run in debug mode
and so on...
Let me know if you had any questions or suggestions. You can also
track this https://phabricator.wikimedia.org/T177145
Hi all,
I would like to announce that Huggle 3.3.0 was just released. This is
again a major update, which most notably comes with support for new
YAML format that we decided to use instead of old custom format.
As of now, YAML format is used for global and project config, example
of new config page is here:
https://en.wikipedia.org/wiki/Wikipedia:Huggle/Config.yaml
Most of wikis except for test and english wikipedia don't have new
format yet, so Huggle will show a warning while logging there, but it
will still work with no issues.
This new format is much better as it comes with syntax checks,
highlighting, is a standard and support many features that old format
didn't support, such as dictionaries, vectors and so on.
Other than that there is lot of less major new features (my most
favorite - auto-relogin in case session becomes invalid), auto-advance
to last revision of currently displayed page in case someone else
modified it, tips and several bug fixes, most notably the one
announced today, that older verrsions of Huggle didn't sign some of
welcome templates. That is fixed now.
It's strongly recommended to update to this version as soon as possible.
MacOS users will need to wait a bit, I need to poke someone who has
Mac and can build the release version.
Thanks
Hi,
There is quite a major pull request:
https://github.com/huggle/huggle3-qt-lx/pull/222/files
If anyone wants to take a look before it gets merged, review, comment
or suggest improvements, now it's your time. If there is no feedback I
will merge it.
Hi,
In future, we will switch to completely new system of on-wiki
configuration. This will be a major change from dev point of view as
we are going to use standardised YAML format for on-wiki
configuration.
I already started drafting new config, you can see
https://test.wikipedia.org/wiki/Wikipedia:Huggle/Config.yaml for
already working version of new config.
This new format will allow for great many new features, most notable
we will finally have ability to properly escape any string, which
wasn't possible as of now. This format has strict parser which will
throw errors in case there are syntax errors and thus making syntax
mistake will no longer be easily unnoticed.
It is also properly supported by syntax highlighter so the config
pages will be easier to read.
Old format will be deprecated, but still supported for some time.
This means, we have a chance to rework completely whole project
configuration page, which is kinda messy right now, and do it right.
Final format and structure is not yet decided, so NOW it is time to
suggest changes and improvements. If you have idea about anything or
don't like how something work with current Huggle project
configuration, now it's time to fix it!