Exactly. Purely technical. From an outsiders perspective it makes
little difference - the feature will still look and behave the same..
To be honest the easiest thing to do would be to package our code and
put it in core, which is what VisualEditor did with oojs ui - but
having two libraries side
I think it is a technical detail Moiz and Dan, no decoupling from the
wikipedia ecosystem.
The idea (I think) is to make Gather more independent of Mobile frontend so
that it can work seamlessly in Desktop when the time comes and in the way
extract valuable common code into library/core so that ot
Given that your target audience for this project right now is Wikipedia
readers, what are the advantages to those users of removing the
MobileFrontend dependency from Gather? I'm unclear on this point right now.
Dan
On 13 April 2015 at 12:10, Jon Robson wrote:
> I did a quick spike [1] to work
I agree with Joaquin. What are the benefits of decoupling?
On Wednesday, April 15, 2015, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:
> I don't see many advantages between the sub-module approach and just
> leaving it in MobileFrontend and have Gather depend passively on a part of
>
I don't see many advantages between the sub-module approach and just
leaving it in MobileFrontend and have Gather depend passively on a part of
MobileFrontend. I mean, the isolation can make us think that they are
decoupled but in reality they will still be highly coupled, and we'll need
to be as c
No. Explicitly not. This would just be folding our code out into a sub
module. The point is to remove dependencies! :)
We dismantled it because code for templating when into core.
On 13 Apr 2015 12:41 pm, "Bahodir Mansurov" wrote:
> Essentially, does that mean we want to re-create Mantle? If so,
Essentially, does that mean we want to re-create Mantle? If so, we should
consider the reasons why we dismantled it.
> On Apr 13, 2015, at 3:10 PM, Jon Robson wrote:
>
> I did a quick spike [1] to work out how Gather could stop depending on
> MobileFrontend.
>
> Essentially problems come into
I did a quick spike [1] to work out how Gather could stop depending on
MobileFrontend.
Essentially problems come into 2 categories:
1) Finding a place for Gather in the desktop skin and addressing
styling issues in desktop skins (I am working on these and don't see
any major blockers here).
I thi
