[twdev] Re: page background goes to nirwana with fullscreen button

[Simon Huber]

Am Dienstag, 23. Januar 2018 07:02:32 UTC+1 schrieb Simon Huber:
>
> Hello, what is the reason that the pagebackground gets unset with the 
> fullscreen button?
>
> BurningTreeC
>

edit: I got it, it's the tc-body background color that hides background 
attachments

I made a pr and cross fingers,

have a nice day @all 

-- 
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/a523cb90-d8b3-4619-912d-f26002396408%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] page background goes to nirwana with fullscreen button

[Simon Huber]

Hello, what is the reason that the pagebackground gets unset with the 
fullscreen button?

BurningTreeC

-- 
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/044e253c-0496-4648-986a-8ad28502e5cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[twdev] Re: An "errors and warnings" display for tiddlers?

[Evan Balster]

Hey, Tony —

My suggestion for simple logging would be to build an "append" action, 
which could be made in WikiText with action-setfield and some macros, as a 
JavaScript macro, or as a widget similar to action-setfield.

Again, that's a different mechanism from what I have in mind for the 
feature described in the OP, which would be much more like IntelliSense 
warnings in an IDE.  (Like spell check but for code and markup instead of 
proper spelling and grammar.)

On Friday, 19 January 2018 22:16:52 UTC-6, TonyM wrote:
>
> From the user perspective I would like an action widget That I can add on 
> buttons etc.. where I can write something to a log Tiddler, global or 
> <> so I can build an action history even on a single Tiddler 
> and with size limits for safety.
>
> I plan to develop a plugin something like this but if we could leverage a 
> generic log mechanism it would save code space and allow performance focus.
>
> 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/10155525-91c2-4613-af36-720027b0ba89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [twdev] Build Process for TiddlyWiki Classic

[PMario]

Hi Yakov,

Along with fixing tests and issues I'll probably be learning using git 
> rebase: looks like it is an exact tool to deal with this mess 
> . If there are any 
> suggestions regarding this, let me know (as well as suggestions of how to 
> merge on GitHub in a proper way or other things regarding git/github 
> workflow).


I do use the following workflow (for TiddlyWiki5), which never caused merge 
conflicts for me. 

I'm using 2 aliases for my local git repos: 

 - origin ... points to my github account, where I do have write access.
 - upstream ... points to the "main project" account ... which only merges 
to master with pull requestes, even if I have write access!

The most important rule for me is: 

 - Never, ever *commit and push* to *origin remote master *branch!

Except for 

 - git status ... if working tree is clean I can go on. If not I need to 
commit to a "feature-branch" or I simply do a "git stash"
 - git checkout master
 - git pull upstream master
 - git push origin master    to update origin repo.

 
*My local workflow looks like this: *

 - git status ... if working tree is clean I can go on. If not I need to 
commit to a "feature-branch" or I simply do a "git stash"
 - git checkout master
 - git pull upstream master
 - git checkout -b new-feature-branch
 - git add .
 - git commit -m "detailed info"
 - git push origin new-feature-branch

 - Create a PR with github web UI. 
 - Once the PR is merged start over with git status ... 

have fun!
mario




-- 
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/dfcb5225-f37f-495b-91a0-2dc7acdd271a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.