[twdev] Incompatibility of tiddlywiki with Firefox

2018-01-26 Thread TonyM
Firefox is fine,

The Saving mechanism has changed so "TiddlyFox" addon, no longer works, the 
same is happening to other browsers too, Return to tiddlywiki.com and look at 
the different saving mechanisms you can now use.

Which you choose will depend on how and where you use tiddlywiki.

Also consider tiddlydesktop, tiddleyserver and Marios filesave and more

Raise a thread in the regular TiddlyWiki group for this.

Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/1b42f80c-9128-43db-8b48-841ccdf9a168%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [twdev] Build Process for TiddlyWiki Classic

2018-01-26 Thread Yakov
Hi guys,

ok, from what I understand now, bld.bat creates index.html (for 
classic.tiddlywiki.com) with the following line:

node %TIDDLYWIKI5_DIR%/tiddlywiki.js ./wiki --verbose --load 
./index.html.recipe --rendertiddler 
$:/core/templates/tiddlywiki2.template.html %TIDDLYWIKI_DEST%/index.html 
text/plain

which points to the index.html.recipe which contains

recipe: ../tiddlywiki/tiddlywikinosaver.html.recipe
recipe: ../tiddlywiki/content/split.recipe

and the latter contains the list of tiddlers that are in the same folder (
tiddlywiki/content) which actually constitute content of index.html.

What I still don't understand is how do I get those .tid files updated 
(except for editing them as plain text) from the tiddlywiki.github.com repo 
(and shouldn't we move the content files to that repo instead of the repo 
of TW2 core?). It would be nice to edit a TW (tiddlywiki.github.com 
repo/index.html) and get those files updated..

Any suggestions? Jeremy, where did you get those .tid files from (and how?) 
for making this commit: 
https://github.com/TiddlyWiki/TiddlyWiki/commit/c5d5c85eb7337a4f052f0d0151de0679be72e0ed
 
?

Best regards,
Yakov.

четверг, 25 января 2018 г., 1:31:16 UTC+3 пользователь Yakov написал:
>
> So, regarding classic.tiddlywiki.com..
>
> Is it correct that editing it can be done by just (forking and) cloning 
> the [1] repo and editing TW in a browser? (and pushing back to fork and 
> merging) I mean are recipes at [2] outdated since TiddlySpace is down (so 
> [2] now has nothing to do with [1] and classic.tiddlywiki.com)?
>
> No, wait, this can't be. First, TW version won't be updated this way (as 
> well as the download package). Second, which is more surprising, for now I 
> have only cloned [2] and still got cooked/2.9.1/index.html with 
> classic.tiddlywiki.com's content in it once I've cooked TW.. is content 
> from [1] accounted at all?
>
> Any suggestions? What's the correct workflow? Yeah, the last change was 
> done back in 2013, so it won't surprise me if nobody remembers...
>
> Best regards,
> Yakov.
>
> [1] https://github.com/TiddlyWiki/tiddlywiki.github.com
> [2] https://github.com/TiddlyWiki/tiddlywiki.com/
>
> среда, 24 января 2018 г., 17:56:27 UTC+3 пользователь PMario написал:
>>
>> On Wednesday, January 24, 2018 at 2:09:11 PM UTC+1, Yakov wrote:
>>>
>>> PS is that correct that the upstream name is purely a convention and 
>>> git doesn't do anything different with regard to it, technically?
>>>
>>
>> Yes ... All aliases are just a convention. ... If you use the same schema 
>> for all your local repos, it helps to minify "user errors" 
>>
>> For me "push origin" means ... I can savely write to it. 
>>
>> "push upstream" means ... Be really carefull ... Messing it up, will 
>> cause a lot of work to fix it!
>>
>> -m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6f29491c-ab84-4b9e-8e89-2058cd6a93b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] TiddlyDesktop top unused MenuBar

2018-01-26 Thread Simon Huber
Hello devs,

I've figured out that by commenting out line nr. 66 "this.window_nwjs.menu 
= $tw.desktop.utils.menu.createMenuBar();" in "wiki-file-window.js" hides 
the grey top menubar in TiddlyDesktop

This bar isn't used by anything and takes away some valuable space on 
smaller screens
Is this a necessary feature for something or is it a placeholder for some 
coming features? I'd like to create a pr for this, making it configurable

Simon


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/67fd9031-ab24-4554-9b9c-794282365f0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.