Menu ▾ ▴

#153 priorities

workingwiki
open
Lee Worden
None
6
2013-05-07
2012-01-12
Lee Worden
No

this is a meta-tracker item to discuss what bugs and features should be addressed soonest.

Discussion

  • Lee Worden

    Lee Worden - 2012-01-12

    The problem of not reconstructing project files on historical pages has come to my attention, and it would be good for presenting WW to the outside world: https://sourceforge.net/tracker/?func=detail&aid=3471988&group_id=366300&atid=1527385

     

  • Lee Worden

    Lee Worden - 2012-01-12

    But then there's the problem of standardizing make invocation so that projects can call make in other projects and have it run the same as when WW does it, and also having it be transparent like that in exported project directories. I'm looking for the tracker item(s) relating to that. That may be the top priority.

     

  • Lee Worden

    Lee Worden - 2012-01-12

    And anything that comes up that's needed to get the yushan theobio wikis up and running will take priority. Also if an off-site user has something come up that's urgent for their wikis.

     

  • Jonathan Dushoff

    Jonathan Dushoff - 2012-01-13

    My quick suggestions for high priority are:

    • Get rid of implicit project descriptions
    • the bug where WW includes all of the .mk files twice and generates unnecessarily scary make logs
    • some sort of way to control the default tex rules (possibly by testing and documenting some way of doing it with the existing WW setup)
     

    Last edit: Lee Worden 2012-08-31

  • Jonathan Dushoff

    Jonathan Dushoff - 2012-01-13

    Another important one: improve the prerequisite projects interface. Lots of suggestions, but the really important one is the ability to click through and see if your link is working.

     

  • Jonathan Dushoff

    Jonathan Dushoff - 2012-01-13

    The ghost Makefile problem. Somebody somehow deletes a .mk file from the PD, but it remains in the working directory. These have caused major nightmares on at least 3 occasions. The kind of thing that could make someone give up on WW, IMO.

     

  • Lee Worden

    Lee Worden - 2012-02-06

    I thought there was a conversation about the ghost .mk files but I don't see it here - it must have been in email. WW is supposed to delete files from the working directory when they're removed from the project. It could be leaving them due to buggy programming, or it could be that files are deleted, but they're present in preview or background directories so that they're recreated during the merge.

    Anyway, this would be addressed by WW explicitly naming the source files in each make request rather than leaving it to PE to use "*.mk".

     

  • Lee Worden

    Lee Worden - 2012-02-06
    • some sort of way to control the default tex rules (possibly by testing
      and documenting some way of doing it with the existing WW setup)

    would you say more about what kind of control you want?

     

  • Lee Worden

    Lee Worden - 2012-02-07

    including the .mk files twice is fixed now. (Please tell me if it turns out it isn't!)

     

  • Jonathan Dushoff

    Jonathan Dushoff - 2012-02-07

    What I meant by controlling default .tex rules was the ability to disable .d dependencies when I want to. This could turn out to be as simple as figuring out how to override the right parts of the default rules in my own .mk files -- I will experiment with it when I get the chance.

     

  • Lee Worden

    Lee Worden - 2012-02-07

    right, so we had experimented a little with

    ifeq ($(origin tex_files_for_d), undefined)
    tex_files_for_d = $(patsubst %.tex,%.d,$(wildcard *.tex))
    endif
    include $(tex_files_for_d)

    which would allow a project author to set $(tex_files_for_d) to something else. It crashed the makefile, probably for some trivial reason. I was thinking it might be better to set $(tex_files_for_d) in makefile-before and use it in makefile-after, which is more the pattern I try to use for the rest of the makefile logic, and would allow the project author to set the variable to something else after it's set and before it's used (that's why we have some stuff before the project makefiles and some stuff after).

    Maybe I would like it better if we set $(tex_d_files) to the actual list of .d files and worked with that instead. Would that work for you, do you think?

     

  • Lee Worden

    Lee Worden - 2012-02-07

    "external links for external projects" is closed now.

     

  • Lee Worden

    Lee Worden - 2012-03-09

    I've made the change for .tex files by defining

    tex_d_files = $(patsubst %.tex,%.d,$(wildcard *.tex))

    in makefile-before and placing

    include $(tex_d_files)

    in makefile after. This should work exactly like the single line in makefile-after that was there before, and it seems to, except that your makefiles can change the value of $(tex_d_files) before it's used.

     

  • Lee Worden

    Lee Worden - 2012-05-30

    renaming from "priorities for winter 2012" to "priorities" for ongoing use.

    I hope to come back to here soon and add a list of new items that have come up in the last month or two.

     

  • Lee Worden

    Lee Worden - 2012-07-02

    I was working on getting rid of implicit project descriptions and didn't finish, so I think I'll try to finish that up now.

    [Update: finished.]

     

    Last edit: Lee Worden 2012-08-31

Anonymous
Anonymous

Add attachments
Cancel