2017-10-16 21:45 GMT+09:00 Gustavo Sverzut Barbieri :
> > +function Efl.Ui.Format_Func_Cb {
> > + [[Function pointer for format function hook]]
> > + params {
> > + @in str: ptr(Eina.Strbuf);
> > + @in value: Eina.Value;
>
> I'd use const(generic_value), there is
On Mon, Oct 16, 2017 at 01:34:10PM +0900, Carsten Haitzler wrote:
> On Mon, 16 Oct 2017 13:10:54 +0900 Jean-Philippe André
> said:
> > Those engine-specific headers exposed structures containing data that
> > should have been kept internal, and bind the applications to a
On Mon, 16 Oct 2017 17:33:06 + Andrew Williams said:
> Thanks for that - does anyone have access to make these changes in Phab?
>
> In the meantime I just installed StyleBot in Chrome so I could save that
> override locally...
it's all locally installed on the machine
On Mon, 16 Oct 2017 09:25:20 + Andrew Williams said:
> Hi,
>
> Unfortunately dokuwiki is not markdown -
Well... it is markdown AND markup with an eclectic mix of both. there isn't a
single markdown format. every wiki has it's own which is slightly different,
but
> +function Efl.Ui.Format_Func_Cb {
> + [[Function pointer for format function hook]]
> + params {
> + @in str: ptr(Eina.Strbuf);
> + @in value: Eina.Value;
I'd use const(generic_value), there is no need to use `Eina.Value`
since it's a "native" eolian type... and you don't want to
Hi,
while at these helpers... would you implement the non-locale (LANG=C)
version? what happens in real life is that to parse/generate floats and
dates people often assume it's generating in English... then you run it in
a pt-BR or other locales where stuff are different and everything breaks :-)
Hi,
Unfortunately dokuwiki is not markdown -
https://www.dokuwiki.org/wiki:syntax , what I was proposing moves us to the
php extended markdown which is well known and supported by most php based
apps if not more.
By changing to a standardised format we can have better interoperability
and also