|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|
|vrurg||gac410: Sorry, have no time today. Briefly – not sure it's ready for merge. And I will need help on completing the project.
Hope to get time tomorrow to initiate a discussion.
|gac410||no prob. The merge looked promising though
I think I was supposed to have a release meeting tomorrow. Forgot about it :(
|vrurg||Merge was possible for code which didn't undergo the conversion, I guess. There're a some big changes besides of replacing $Foswiki::Plugins::SESSION with $Foswiki::app. I think a topic with summary would be needed.||[01:13]|
|gac410||There are actually not a lot of changes yet in master, so mostly minor changes seemed to fit fine. Foswiki.pm was major, but mostly deleted code, the actual merge change was only a couple of lines.
anyway, it was an interesting exercise. I'll let it wait.
Release meeting was supposed to be on the 18th. I guess I missed it. ... oops. Next one on calendar is May 2nd.
|vrurg||Let's discuss it tomorrow. Release meeting would suit me the best but it doesn't really matter which way I get help.||[01:19]|
|gac410||okay. I'll be on/around.||[01:20]|
|............................. (idle for 2h22mn)|
|GithubBot||[distro] gac410 pushed 1 new commit to master: https://git.io/vwEta
distro/master 602172b George Clark: Merge branch 'Release02x01'
|***||GithubBot has left||[03:43]|
|......... (idle for 40mn)|
|gac410 has left||[04:23]|
|......... (idle for 43mn)|
|ChanServ sets mode: +o CDot||[05:06]|
|................ (idle for 1h17mn)|
|ChanServ sets mode: +o Lynnwood||[06:23]|
|.............. (idle for 1h7mn)|
|foswiki_irc7||Is there anyway I can set table of contents on for all pages by default (even those that are newly created)?||[07:30]|
|***||ChanServ sets mode: +o MichaelDaum||[07:35]|
|.................................................... (idle for 4h19mn)|
|ChanServ sets mode: +o gac410||[11:54]|
|......... (idle for 40mn)|
|gac410||Hi all ... I screwed up on the release meeting schedule. Calendar called for last week, which I missed, Next meeting is officially May 2nd.||[12:34]|
|***||gac410 sets mode: +v FoswikiBot||[12:35]|
|gac410||vrurg is looking for some assistance, so if you are around, could we meet today to give him a hand?||[12:36]|
|............ (idle for 56mn)|
|MichaelDaum: There are a couple of jquery files in git that are being flagged as missing from the manifest:
I'm going to build 2.1.1 RC2 and get it on Foswiki.org ... I've decided to wait to see the logs rotate (I hope) before releasing 2.1.1
|MichaelDaum||pub/System/JQueryPlugin/themes/foswiki-fontawesome/jquery-ui.uncompressed.css should not be in the repo at all||[13:34]|
|gac410||hm Commit distro:63f671e0c416 is the only log entry for it.||[13:36]|
|FoswikiBot||https://github.com/foswiki/distro/commit/63f671e0c416 [ Item13883: up'ing copyright · foswiki/distro@63f671e · GitHub ]||[13:36]|
|MichaelDaum||pub/System/JQueryPlugin/plugins/masonry/jquery.masonry.init.uncompressed.js is a dev-only file: it is appended to the upstream masonry js as part of jquery.masonry.uncompressed.js ... and this one goes into the zip
I was working on a fontawesome based jquery ui theme replacing the famfamfam-ish foswiki theme ... but did not continue on it
|gac410||okay ... as long as the normal extension build process is doing the right thing, should be okay. I just don't recall seeing either of them flagged by check_manifest before.||[13:38]|
|MichaelDaum||when using fontawesome icons in a new jquery-ui theme, button styles they are on need to change as well ... being more flat-design
the current gradient look and feel does not work out for monochrome icons such as fontawesome ... looks ew
|MichaelDaum||however getting the icon set into jquery-ui was quite a hassle, so I checked it in||[13:40]|
|gac410||no problem ... As long as I know it's not an issue, I can just ignore it. It's just a quality check I run before build. Are all files in git in the manifest, and everything in manifest exists in git.||[13:41]|
|MichaelDaum||new jquery-ui beta comes with a new default l&f: http://jqueryui.com/themeroller/
still far behind say ...bootstrap
which has aged in itself as well
yay, looking forward to RC2 :)
|gac410||I probably should have built 2.1.1 a while ago. But frustrated by the PlainFile log rotate situation. Works on all the tests, but fails on Foswiki.org. I think this last one was due to the + vs - timezone||[13:44]|
|MichaelDaum||yea no problem. it is done when it is done.||[13:45]|
|vrurg||I thought a bit on the assistance. Would be great if somebody joins me but not critical for another week or two. Still a lot of low-level things to be done.||[13:57]|
|vrurg||vrurg doesn't even know what to answer... ;)||[13:58]|
|MichaelDaum||there was no question
|vrurg||BTW, I don't know if my commits are followed, so would duplicate it here: PSGI support may become a part of 3.0 release.
It seems to be easier than I thought. Just a matter of one more engine.
|gac410||Cool. I didn't see that noted in your commits. I do glance at them but not in great detail.||[14:00]|
|vrurg||Aha. Unless I forgot to mention it, it was in explanatory part of a commit message.
Generally, the only major difference between PSGI and CGI is in the way environment is been passed around.
And in/out handlers too.
Ok, I'll be away for ~2hr.
|......... (idle for 41mn)|
|GithubBot||[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vwuWr
distro/Release02x01 61f19e0 George Clark: Item13883: Bump TwistyPlugin version due to doc updates
|***||GithubBot has left||[14:45]|
|FoswikiBot||https://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ]||[14:45]|
|jomo||hi all ;)||[14:55]|
|gac410||hi jomo .||[14:55]|
|jomo||wow - 2.1.1-rc1 ;) nice...||[14:56]|
|gac410||rc2 in process of being built. Just found another typo :(||[14:57]|
|jomo||jomo need read thru the irclogs... - about the FoswikOOO progress...||[14:57]|
|gac410||vrurg making great strides ... And he just commented that PSGI might be part of it as well||[14:58]|
|jomo||really? cool... ;)
hm... just read.. "the only major difference between PSGI and CGI is in the way environment is been passed around. " - this isn't entirely true... :) but, don't want slow down vrurg...
|vrurg||jomo: Sure, I didn't read the whole spec and simplified things a bit.||[15:02]|
|jomo||a lot ;) :)||[15:02]|
|vrurg||Well, what makes it that different from the perspective of a plugin? Or a macro? I mean the way foswiki starts in my model seems to be compatible. All adaptations would be localized within PSGI engine. The rest of the code shall feel no difference.||[15:05]|
|jomo||CGI = forked a process, reads stdin writes to stdout... PSGI coderef, returns arrayref - the PSGI compliant app could be runned as CGI, FCGI, mod_perl, or standalone - e.g. you don;t need any other engine if you one managed the PSGI...
and the last part is the MAJOR difference ;)
ANY PSGI app could be executed as CGI or under any FCGI server or mod_perl... - simply, if you have PSGI app - never need anything other - and COULD deploy the app in ANY environment without any change...
but the redone to natove PSGI isn't easy job - need rid off the CGI libs fully... (incompatible)..
|vrurg||jomo: You're messing up with technical details which are really a lot different. I'm speaking of a model.||[15:08]|
|vrurg||Not every part of CGI is totally PSGI incompatible. For example, cookies aren't based on %ENV and work with abstract strings, so to say.||[15:09]|
|jomo||nah... ok - don't want vrangle... i just joined to refresh my presence... do as you wish and think :) :)||[15:10]|
|vrurg||Anyway, this would be the time to jump in and investigate the current code and see if there are problems with PSGI compatibility.||[15:10]|
|jomo||my point of view is (looks like) is totally different.... once i have an native PSGI app - i don't need any other "engine"... this is the BASIC premise... so, could rid of all other engines. (mainly because theyre redundant and not needed) ;... so, if you call the foswiki as an coderef and returns the needed arrayref (defined by the PSGI specs) - youre mainly ok...
teh PSGI is really simple spec... ;)
the whole thing is based on 3 things: 1.) the web-app is an coderef. 2.) it accepts exactly one arg ($env) 3.) returns an 3 member arrayref (status, headers, body) - THAYS ALL... no magic :)
|vrurg||jomo: We cannot get rid of engines because different environments do behave differently, unfortunately. So, a kind of driver is needed.||[15:16]|
you can execute every PSGI app as CGI script...
or as FCGI
WITHOUT any change...
|vrurg||You shall reed my commits to see what changed. Engines are not what start the app – it's app which uses engine to communicate with the outside world. Driver concept.
jomo: You're talking about a ideal situation. Real world is worse than that, unfortunately. ;)
|jomo||no, im talking about the real world... this is how PSGI works...||[15:18]|
|vrurg||Yes, you can make your code compatible with different nuancees of different environments. But it would overcomplicate it.||[15:18]|
nah - ok...
|vrurg||Check the current engines code and see how much different mod_perl from CGI, for example.||[15:19]|
|jomo||you need manage only PSGI emgine. instead of the CGI + FCGI + mod+perl +.... - so what is simpler? manage one or manage 4?||[15:20]|
|vrurg||jomo: You idealize the situation. :) Even two CGI engvironments may differ from each other simply because of server implementation differences. Sometimes these details become crucial.||[15:22]|
|jomo||vrurg: this is pointless. PLEASE read my topic abut the PSGI. It contains all needed info (basics). Youre simply wrong. If you have PSGI app - you don't need any other "engine". period. and you can run (deploy) the PSGI app as: 1.) CGI app, 2.) as FCGI 3.) as mod_perl and so on..||[15:22]|
|vrurg||You're talking of compatibility. But it cannot be 100% compatible with everything. You will have to take into accound these minor differences which will be braking the whole thing.||[15:25]|
|jomo||no im not talking about the compaibility... im talking about HOW the PSGI is DESIGNED.. This is its main PURPOSE... :)
this is how PSGI works... - please, read something about the PSGI... YOU REALLY need ONLY PSGI app - and the web-app don't need solve any other "engines".... everything is done at deployment time... not at app-level...
|vrurg||I understand you. :) But what you talk about here is how an app starts and communicates with the environment. But life spans a bit beyond that. In my opinion even different PSGI implementations would do some things differently. Event different versions of the same PSGI server would have discrepancies. We must keep this all in mind.||[15:28]|
|gac410||MichaelDaum_: (or anyone). ... I'm seeing a strikeone redirect on Foswiki.org when I use UserRegistration. I don't get that on my test systems. No idea why||[15:29]|
|jomo||OK :) :) - I refreshed my presence, happyly wrangled a bit - and could go offline again for a month or soo... ;) Good luck - and keep up good work. ;)
cu again later.. ;) :)
|***||jomo has left||[15:31]|
|........................... (idle for 2h12mn)|
|ChanServ sets mode: +o CDot||[17:43]|
|...................................................... (idle for 4h28mn)|
|GithubBot||[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vwz98
distro/Release02x01 bdb7ad9 George Clark: Item13883: Typo in InstallationGuide.
|***||GithubBot has left||[22:11]|
|FoswikiBot||https://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ]||[22:11]|
|.................. (idle for 1h26mn)|
|GithubBot||[distro] gac410 pushed 2 new commits to Release02x01: https://git.io/vwzhd
distro/Release02x01 46ae78f George Clark: Item13883: JQueryMasonry.txt contains non-ASCII characters...
distro/Release02x01 d6a2ce4 George Clark: Item000: Build Release 2.1.1-RC2
|***||GithubBot has left||[23:37]|
|FoswikiBot||https://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ]
https://foswiki.org/Tasks/Item000 [ Item000 ]
|GithubBot||[distro] gac410 tagged FoswikiRelease02x01x01_RC2 at 1f5c7d3: https://git.io/vwzhh||[23:38]|
|***||GithubBot has left||[23:38]|
|GithubBot||[distro] gac410 pushed 1 new commit to master: https://git.io/vwzjV
distro/master a3def4d George Clark: Item000: Merge branch 'Release02x01'...
|***||GithubBot has left||[23:45]|
|gac410||Foswiki 2.1.1-RC2 is released on github and running on Foswiki.org.||[23:52]|
|***||gac410 changes topic to: Download foswiki 2.1.1-RC2 at https://foswiki.org/Download/FoswikiRelease02x01x01-RC2. IRC logs: http://irclogs.foswiki.org/bin/irclogger_log/foswiki||[23:53]|
|gac410||And if the logs properly rotate at midnight on the 30th, I'll build 2.1.1 on May 1st.||[23:58]|
|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|