#foswiki 2016-03-14,Mon

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
gac410hey vrurg ... you around? time for a question? [02:10]
............... (idle for 1h13mn)
nixdorkNobody is maintaining debs or rpms anymore? [03:23]
gac410no, only one dev was doing it, and he has left the project
Unfortunately he never contributed the build tools, so we'd have to start over.
[03:24]
nixdorkBummer.
Can someone ask him for them?
[03:25]
gac410We've asked a couple of times. They are intermixed with some proprietary stuff he cannot release. [03:25]
nixdorkOh.
Weird.
[03:26]
gac410yeah, it's disappointing. [03:29]
nixdorkI was thinking it shouldn't be very hard to make a few scripts to package it up but maybe I'm ass-u-me-ing. :) [03:30]
gac410Well it gets pretty complex as you dig into it. building the dependencies, even just packaging foswiki in a way that rpm / dpkg can install and maintain is tough. Foswiki intermixes configuration and user data in with distribution files. [03:31]
nixdorkEasier to just git clone the current branch and run with that huh?
This thing https://github.com/foswiki/distro
[03:33]
gac410well. I'd recommend using our tarball. If you go with the clone, you don't get any compressed javascript or css. [03:33]
nixdorkThat's ok. I don't really want any javascript. :) [03:34]
gac410Can't run foswiki without it. [03:34]
nixdorkI was going to try to do it with components and just include the bare minimum.
Oh crap really?
On the server side? Or just stuff you pass to the client?
[03:34]
gac410well, basic view functionality will work, but it will be a struggle. especially user friendly configure.
client. we use JS for xss protection, default editor is js, bin/configure is heavily dependent on js. jquery. etc.
[03:35]
nixdorkHmmm. [03:36]
gac410you can configure without js, but you'd be using the CLI tools, nothing web usable. [03:36]
nixdorkI see, I think.
Well as long as I don't have to install angular.js or any of that crap on my server I guess I'm ok with a script or two on the client to make the interface better.
[03:37]
gac410We don't run any server side js. purely client, but served by the web server. Foswiki on the server side is pure perl. [03:38]
nixdorkOk that's good.
You had me worried for a second. :)
Now I just have to figure out what's wrong with this server and why I can't get apt-get to install rcs.
[03:38]
gac410hm If you are not migrating from an older foswik/twiki, I think you can skip rcs, if you stick with our default PlainFileStore. [03:44]
nixdorkDoesn't rcs give you faster diffs and stuff?
C implementation instead of perl....
[03:45]
gac410hm I think we use perl tools to compare topics. rcs is used to actually store the old versions. Can be *very* expensive under some conditions.
PlainFile store just saves the old versions as separate files.
[03:46]
.......................................... (idle for 3h28mn)
***jast has quit IRC (*.net *.split) [07:15]
ChanServ sets mode: +o MichaelDaum [07:26]
ChanServ sets mode: +o MichaelDaum_ [07:32]
................ (idle for 1h16mn)
adi64 has left [08:48]
................................................ (idle for 3h57mn)
ChanServ sets mode: +o gac410 [12:45]
.... (idle for 18mn)
ChanServ sets mode: +o Lynnwood [13:03]
................ (idle for 1h16mn)
gac410Hi MichaelDaum_ ... I have a possible solution for jsonrpc and Item13969. Needs a feat request, but wanted your comments/agreements first. [14:19]
FoswikiBothttp://foswiki.org/Tasks/Item13969 [ Item13969: rest and jsonrpc scripts should default the web/topic if -topic query param is not provided ] [14:19]
gac410Foswiki::UI gets the function from SwitchBoard, and the calls _execute() which executes Foswiki::new() and then transfers control to the function. [14:20]
FoswikiBothttp://trunk.foswiki.org/System/PerlDoc?module=Foswiki::UI [14:20]
gac410I'm thinking that we could add an initfunction to SwitchBoard, which would be called *before* calling Foswiki->new() and it could establish the default webtopic by alternate means.
Essentially an early-init for "actions"
[14:21]
MichaelDaumHi George [14:22]
gac410Either UI calls it directly, or passes a function ref to Foswiki->new() for it to call [14:22]
MichaelDaumlet me think about it [14:22]
gac410okay. yeah. It definitely needs a feature request to review the design, but wanted to get "early feedback / support" :D [14:23]
MichaelDaumsounds like a more general feature that could potentially be useful for other stuff as well. [14:23]
gac410y. that was my thought. The earlyInit would add values to the "initialcontext" as a way of passing state to the new session [14:24]
MichaelDaumnice idea [14:24]
gac410right now initialContext just gets the fixed string from the switchboard ie context => { jsonrpc => 1 } [14:24]
MichaelDaumthough the code in Foswiki::new() still primarily looks at path_info trying to read the webtopic location
adding an "if()" around it is in category spaghetti imho
[14:25]
gac410Not really First it checks -topic queryparm, and then path. I would chang it to check initialcontext, then topic, then parser [14:25]
MichaelDaum^then parse^then parse path_info ... you mean? [14:26]
gac410Yes. So if no initialContext{webtopic} and no query_param(topic) then parse query_path()
Parser still needs to be pulled apart and modularized, similar to what Foswiki::Address attempted to do.
[14:27]
FoswikiBothttp://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Address [14:27]
gac410Parser needs to better handle web/subweb/topic/attacment better. but that's a different bug. [14:27]
MichaelDaumI think that should definitely work
now one question: will JsonRpcContrib actually be able to read its postdata at that point?
note we need to keep it backwards compatible
[14:27]
gac410hm. Request has been created, but not the session. Might need to pass the RequestObject as a parameter. Which leads toward having Foswiki.pm make the call, not Foswiki::UI
Right. I figured for backwards compat, the early init just won't be called, so it leaves the ext. no worse than it currently is.
[14:29]
MichaelDaumMichaelDaum going thru Foswiki::Contrib::JsonRpcContrib::Server::dispatch() ... [14:29]
FoswikiBothttp://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Contrib::JsonRpcContrib::Server [14:30]
MichaelDaumah it actually would proceed _before calling the switchboard handler [14:30]
gac410Yes.
Look at Foswiki::UI subroutine _execute() either that would call it before the Foswiki::new() OR it would pass the early init handler reference to Foswiki. I think it needs to be the latter if it needs the request object.
[14:30]
MichaelDaumcurrently the logic to read in the JsonRPC is performed when the switchboard handler is dispatched. it build up a new Foswiki::Contrib::JsonRpcContrib::Request object [14:33]
gac410Ah ... no Foswiki::UI DOES have the Request object, so no need to pass subroutine refs. [14:33]
FoswikiBothttp://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Contrib::JsonRpcContrib::Request [14:33]
MichaelDaumFoswiki::new() asks for cgi->param("topic"), ... jsonrpc asks for jsonRpcRequest->param("topic")
which is then looks at the json payload
(arg my denglisch is awful today)
so Foswiki::new() simply is asking the wrong guy for param->("topic")
[14:34]
gac410hm so if JsonRpccontrib::Request ISA Foswiki::Request, it might even be transparent. if _execute( was passed the JsonRpcContrib request ... [14:37]
FoswikiBothttp://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Request [14:37]
MichaelDaumright [14:37]
gac410which means you don't even need the ealry init.
Just a way in SwitchBoard to say request => Foswiki::Contrib::JsonRpcContrib::Request
[14:37]
MichaelDaumnew Foswiki::Request() should return a JsonRpcContrib::Request in this case [14:38]
gac410exactly [14:38]
MichaelDaum_that_ would be elegant [14:38]
gac410I'm glad we talked. That's a lot cleaner than passing stuff via context. [14:39]
MichaelDaum:) [14:39]
gac410That also says that the parsing of query_path() should be part of Foswiki::Request rather than stuffed into Foswiki.pm [14:40]
MichaelDaumtotally makes sense [14:40]
gac410So Foswiki.pm always asks the request for the web/topic/attachment and the request returns the appropriate values.
The parser you have in xsendfile and the (broken) "hinting" parser that Foswiki::Address has can serve as the basis of the Request query_path() parser
I'll write up a feature request, for 2.2, (It's refactoring more than a wholly new feature) and maybe we can get vrurg's blessing as well, keep it compatible with his thoughts on internal object design.
[14:40]
MichaelDaumcool [14:45]
gac410I also wonder if the SwitchBoard could contain a "hint" of what the query_path should comprise. $web.$topic or $web/$topic/$attachment ie viewfile / xsendfile would say they expect a w/t/a [14:46]
MichaelDaumhm
not sure about that one at all
[14:46]
gac410When testing the Foswiki::Address parser, it was much more reliable on parsing query_param if it "knew" that an attachment was expected.
otherwise it might be confused. Is Main/Something/Foobar.Dat subweb Something/Foobar with topic Dat (dot is our web.topic delimiter) or is Something the topic name.
(dot) can be both a web . topic delimiter and the web/topic/file.name.part delimiter. Really an awful mess IMHO
well anyway ... that's a "different" issue from the jsonrpc issue. gotta run off to the store for a bit. I'll work on a proposal later.
[14:47]
vrurgHi everybody! [15:00]
gac410hi vrurg [15:00]
vrurggac410: I'd like to ask to use my email from foswiki.org profile if something is urgent. Had a crazy last week and will have much less spare time now. [15:01]
gac410no prob. nothing urgent. [15:01]
vrurgvrurg haven't done a line of code for the last 7 days. That's terrible! ;) [15:02]
gac410;)
I'll create a feature proposal later, but thought is to move the parsing of the query_path into Foswiki::Request, so you would ask the Request object for the baseweb, basetopic, attachment, and let it figure it out.
That way jsonRpc could subclass the Foswiki::Request with a jsonrpc request object, and get the baseweb / basetopic from the posted json data.
Anyway, I'll get a proposal written later, and will shoot you an email when it's ready for review. I have to run out.
[15:02]
vrurggac410: I like it. Request is the class to deal with this kind of staff. [15:09]
..... (idle for 21mn)
MichaelDaumMichaelDaum found a guy on github that converted WebService::Solr to Moo + Types::Standard ... yay
unfortunately Types::Standard is n/a on most distros ... nay
... could go into a MooContrib
[15:30]
vrurgMichaelDaum: lets start without typing (except that I have made simple hashref/arrayref/class validation) and see where it all develops later. With plack it would be reasonable to switch to Moose where typing is included. [15:35]
MichaelDaumcan't do much about it wrt WebServices::Solr as https://github.com/ilmari/webservice-solr went that way
Infact I'd be happy to stay on one Moo* and not mix different ones pulled in via plugin dependencies of all sorts
the orig WebServices::Solr was still on Any::Moose ... so good to see somebody took care of that one
[15:37]
vrurgMichaelDaum: Moo integrates transparently into Moose anyway. If it detects that Moose is already loaded then it steps aside and hands over control to Moose. [15:39]
MichaelDaumah ok. nice! [15:39]
vrurgDon't know how well does it work but this behavior is declared. [15:39]
MichaelDaumlet's cross fingers [15:39]
vrurgYeps. [15:40]
MichaelDaumfeels like Moo is snappier than Any::Moose (loading Moose in the background anyway) [15:40]
.................. (idle for 1h27mn)
***JulianLevens has left [17:07]
.................................... (idle for 2h59mn)
dldl-workin foswiki v1.1.9, I want to extract an attachement name/date from a topic
can I do that within a query search?
like, format="'$item'/attachment[0]"
[20:06]
...... (idle for 25mn)
LynnwoodAnyone have recent experience working with either WorkflowPlugin or ApprovalPlugin? [20:32]
..................... (idle for 1h44mn)
***ChanServ sets mode: +o Lynnwood [22:16]
dldl-workcan someone point me to documentation for splitting macros into multiple lines
I'm pretty sure it exists, and I have seen it before, but I can never find it on purpose
oh... foswiki v1.1.9 doesn't support multiline arguements :(
[22:16]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)