465 replies to this topic

[littlesat]

I think it belongs more to a wiki....

Edited by littlesat, 25 February 2018 - 08:31.

[Rob van der Does]

So the circle is round (again) 

 

Apparently you didn't even read what I said.......

Oh well, as I said: never ever ask for 'pushing back' again then.

[littlesat]

Or the Needle jumper back into the wiki groove...

[Rob van der Does]

There's no point in reacting if you don't bother to read.

[IanSav]

Hi Littlesat,

I think it belongs more to a wiki....

Is this an OpenPLi specific or a generic Enigma2, including OE-Alliance, OpenPLi, OpenViX, Beyonwiz, etc, wiki?

 

Regards,

Ian.

Edited by IanSav, 25 February 2018 - 10:18.

[athoik]

I think wiki is open for edit for everyone with OpenPLi account.

If the wiki is not used for advertisement and used only to add informations related with our hobby (or technologies behind), then I guess it's fine.

[Rob van der Does]

Hi Littlesat,

I think it belongs more to a wiki....

Is this an OpenPLi specific or a generic Enigma2, including OE-Alliance, OpenPLi, OpenViX, Beyonwiz, etc, wiki?

 

Regards,

Ian.

It's PLi-specific, see https://wiki.openpli.org/Main_Page

Edited by Rob van der Does, 25 February 2018 - 10:33.

[athoik]

It's PLi-specific, see https://wiki.openpli.org/Main_Page

It is our goal to make this OpenPLi® WikiPedia:Wiki into a OpenPLi® software knowledge base, with all information imaginable about both Enigma based and the OpenPLi® firmware images.

[IanSav]

Hi Athoik and Littlesat,

 

OpenPLi can not blame developers for not wanting to contribute back to OpenPLi if this is the attitude to sharing resources.  It is very obvious that a number of repositories draw directly or indirectly from OpenPLi.  I submitted my document here with the intention and belief that the other repositories that draw from OpenPLi would also get this information.  Instead it now appears that my document is to be redirected to a private OpenPLi resource.  This was not my intention and I don't think that this is fair.  It is not a very good Enigma2 community spirit.

 

I have provided the document to the Enigma2 community so I can't complain that you are choosing to make your copy of it private.  If contributions are accepted they may be redirected to private OpenPLi resources and hence filtered out from the repository feeds.  I will interpret this action as a clear sign that OpenPLi don't really want contributions from outside developers.

 

Regards,

Ian.

Edited by IanSav, 25 February 2018 - 10:58.

[athoik]

Yes it's unfair to have a doc folder and rejecting a commit that belongs to that folder.

If there was no doc folder, it can be different.

If there was a documentation system, it can be different.

If there was a clear instruction how and where to put documentation, it can be different.

Now this has taken too far because nobody wants to press the merge button and then, write the rules, never written till now.

Edited by athoik, 25 February 2018 - 11:05.

[littlesat]

We want to have it on a good location thst’s all

[Huevos]

 

This is the format that works for me:

@MCelliot; What are you expecting will happen?

 

If the object is Button/Label and "key_xxx" is assigned in the Python code the pixmap (PNG) will show. The PNG wil show whether the text is empty or not.

 

In the case of StaticText objects the PNG will disappear if the StaticText string is empty, but for Label and Button objects that is not the case.

Edited by Huevos, 25 February 2018 - 12:29.

[WanWizard]

 

A bit more patience, please.

 

I have limited time until after next weekend, due to personal circumstances.

 

Accepting a pullrequest that doesn't even have to be checked (as it only pulls in a small document) can't take that much time.

 

 

It was a response on making develop available. My Python (and internal Enigma) knowledge isn't good enough to judge this type of PR's.

[WanWizard]

Regaring the "Wiki", there seems to be a bit of confusion going on here.

 

There is https://wiki.openpli.org. This is a support wiki for end-users of OpenPLi, so yes, OpenPLi specific.

 

There is also a new development site in the making, which runs on Redmine, which will be used for all things development, and that includes documentation. It lives at https://devtools.openpli.org/ but isn't operational yet, so please don't use it until you are told you can!

[IanSav]

If the wiki was on the OE-Alliance site then that would be a true Enigma2 resource.  Putting it on an OpenPLi server makes it appear to be an OpenPLi resource.  It is very unlikely that an OpenPLi resource would be accepted as a generic Enigma2 reference.

 

Putting information in a private wiki is unlikely to have that information flow to other builds.  Knowing that other builds pull from the OpenPLi fork means that if the document goes into the /doc directory, as I requested, then the document WILL flow to all those repositories!

[Huevos]

@MCelliotG, Why are you creating multiple templates? The whole point is the button bar just works irrespective of the object type. This is not about hiding PNGs, That is just a bonus that works for StaticText.

[Abu Baniaz]

If the wiki was on the OE-Alliance site then that would be a true Enigma2 resource.

As you have learnt, some OE-A image teams try to keep files as far as possible similar to PLI.

[betacentauri]

Why not just add it to the git (into the already present doc folder) and also put it in the wiki? Both wikis.
Don’t make things too complicated.

Edited by betacentauri, 25 February 2018 - 15:58.

[WanWizard]

That is why I suggested a lot of posts back, just to leave it in the repo, and insert a link or reference in the wiki. imho better that trying to maintain it in two places.

[Abu Baniaz]

So,
step 1 is to merge it.
step 2 is to link to it.